Does anyone here recieved android 12 for oneplus 9 pro 5G LE2120?
Sheikhoo007 said:
Does anyone here recieved android 12 for oneplus 9 pro 5G LE2120?
Click to expand...
Click to collapse
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.
Flying Fox said:
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.
Click to expand...
Click to collapse
you can download and install this system update apk from oneplus and it gives you the options to rollback. But be aware rolling back will wipe your device.
https://www.getdroidtips.com/downgrade-oxygenos-12-to-11/
You can you the apk on ColorOS to rollback also.
Flying Fox said:
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.
Click to expand...
Click to collapse
Which bugs are you facing?
Yup, and i've been using it for a month now.
I updated to A12 in Dec when the first OTA was pushed. I had too many issues even after the first 2 patches, downgraded back to OOS11 and never been happier.
I'm waiting for 10pro to launch so I can update to OOS12 then
Time of Awakening said:
Which bugs are you facing?
Click to expand...
Click to collapse
I played around so much, that I don´t remember everything now. Some apps didn´t work. I think, but I´m not sure, I had problems with Viper4Android. Or it was Youtube vanced. Sorry, I really forgot.
Certain setting options had been missing for me or were no longer where you would have expected them to be. I also missed the local upgrade, but that problem has been solved in the meantime (I was not well informed). I was also not happy with the UI, but that is not a bug but a matter of taste.
In sum, not so dramatic, but my evaluation has coincided with those of other forum members. Does not mean that I am right. I'm happy to be corrected.
How is the general satisfaction with A12 here?
A few months back when they started pushing Android 12 I was eager to try it and so I used "Oxygen Updater" from the play store to download a full stable version of android 12 but i accidentally downloaded the Indian version. I had so many bugs on it, but then I used the same app (oxygen updater) to switch to the EU version and my phone worked perfectly with no bugs or anything. I have now switched to Pixel Experience rom and wifi is not working so I may go back to Oxygen 12. But yeah if you have bugs on Oxygen 12 then use Oxygen Updater and download a new version to flash and your bugs may vanish.
Enjoy
I was curious about A12 and gave it a second try after cleaning up everything.
Does Viper4Android work? Just trying with a fix but not sure if it will work.
The next thing is that file manger doesn´t appear in Magisk, when u want to install a module from internal storage.
At least Youtube Vanced is working now.
BTW, post above is ColorOS 12
mrcrazy11 said:
you can download and install this system update apk from oneplus and it gives you the options to rollback. But be aware rolling back will wipe your device.
https://www.getdroidtips.com/downgrade-oxygenos-12-to-11/
You can you the apk on ColorOS to rollback also.
Click to expand...
Click to collapse
Another question: how to us the "OnePlus 9/9Pro Rollback APK". It´s a zip file. Unpacking shows now apk file. Flashing through kernel manager of course not possible. Sorry, don´t find a way to install.
Second try of A12 was not satisfying. When I use the MSM Tool I´ve to re-root again....
Edit: renamed the file to apk at the end. Did it once without success, don´t know why. Now it works
Hope you figured it out. If you haven't.
- download appropriate downgrade package and move it to the root folder of your phone.
- download and install https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
on your devices... this allows you to access local upgrade... if your phone doesn't install a shortcut you can keep reinstalling it every time you need it
- open OPLocalUpdate_For_Android_12.apk click gear in top left corner and install the downgrade package you put in the root directory
You can also use the local update to install other OxygenOS12/ColorOS12 packages. I just went from C.36(Global) -> C.38(EU) -> C.46(ColorOS12) then rolled back because MMS is broken at C.44 all variants of both OSs and above... at least for me.
mrcrazy11 said:
Hope you figured it out. If you haven't.
- download appropriate downgrade package and move it to the root folder of your phone.
- download and install https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
on your devices... this allows you to access local upgrade... if your phone doesn't install a shortcut you can keep reinstalling it every time you need it
- open OPLocalUpdate_For_Android_12.apk click gear in top left corner and install the downgrade package you put in the root directory
You can also use the local update to install other OxygenOS12/ColorOS12 packages. I just went from C.36(Global) -> C.38(EU) -> C.46(ColorOS12) then rolled back because MMS is broken at C.44 all variants of both OSs and above... at least for me.
Click to expand...
Click to collapse
Thanks, my problem was that I didn´t know that I have to rename the files. Many thanks!
Personally, I'm pretty satisfied with the C44 update for OxygenOS 12, stable and smooth, as intended. But yes, the first updates were messy.
For having given a try to ColorOS 12 too, OxygenOS 12 gave me a better experience on the OnePlus 9 Pro: less throttling in games and less bloated.
If we get a ColorsOS C44 EU (which should be far more debloated than its Chinese counterpart) that isn't making games throttle, then I'll surely jump into the wagon, but for now, OxygenOS 12 remains the better option if you want an Android 12 official experience for your phone.
Related
Need to rollback, or be advised of any custom ROMS that work..
Try Elite ROM from ROM section. it should work fine.
I personally would not recommend installing Elite ROM as it is more hassle than it is worth when you try to switch ROMs. It re/debrands your device and even after restoring a nandroid your audio will not work nor will your camera function properly. What files have bad keys? I put a lot of those up and the keys should work fine....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
@ghostair is your device bricked? IMO none of the ROMs for this phone are worth installing on a main phone because there is too much functionality lost, no disrespect to the devs. Elite ROM does have the least amount of bugs but it is a hassle as I mentioned earlier. My main gripe about it is when installing and uninstalling apps you must restart the device in order for the apps to be added or removed from the app drawer....its a major annoyance.
BLN-L24C567B110 Thanks to @Dazed No More
boot - https://mega.nz/#!ceRkHQoA!L8MECn8Ul...8JwO7ZuVEEr8mk
recovery - https://mega.nz/#!sOZAUJTZ!QKKROoWkI...UPNDwL79ZI1yQI
BLN-L24C567B360 Thanks to @Dazed No More
boot - https://mega.nz/#!hDQB3RCT!YTH2j1IhJ...y_prJHEgHdSrxg
recovery - https://mega.nz/#!Fa4DBbxS!XDIczpXcr...TApUtNvcOMEDnc
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
ghostair said:
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
Click to expand...
Click to collapse
Is your device bricked? You say you want to rollback, but have you started the process....what firmware are you on?
Dazed No More said:
....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
.
Click to expand...
Click to collapse
Let me check mate. Thanks for pointing that out.
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
ghostair said:
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
Click to expand...
Click to collapse
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Im assuming you did not make a full backup in TWRP before flashing any ROMs, in which case you have learned a valuable lesson....always have a backup. But since you dont we will get you back to EMUI which I assume is what you mean when you say roll back.
Dazed No More said:
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Click to expand...
Click to collapse
I understand, I probably should have just used, "go back," to EMUI. Since LOS 13 isn't usable in the least, as I can't make calls, and it drops LTE.
If they work then how? I followed everything, flashing vendor.img with fastboot, then flashing the respective zip?
I'd rather not go back to EMUI, it's why I haven't been able to actually "use it as a phone," since purchase.
Why would you not want to go back to EMUI? Its smooth and everything works. EMUI is the reason you havent been able to use it as a phone?? There is not one single ROM for this device that works entirely and has full functionality. You're always going to be missing something whether its the camera, LTE, calls, etc.
You're going to have to go back to EMUI so you can update to Anrdoid 7.0 (be sure to make a full backup) and then flash away all the ROMS you like and you will see they are all broken in some way. This is most definitely not the phone to use if you are looking for polished ROMs.
My last tip before departing......download the flashable vendor zip if you still want to mess around with the ROMs, it makes life much easier. Its in one of the threads in that forum I think AOKP
Hello All,
It has been a while since I have been around the XDA forums, needless to say I needed a new user! haha. I used to run custom ROMs on older Samsung devices, but got out of the game when I could never pass safetynet. Needless to say, I have now stepped into the world of OnePlus, and so far I am impressed! I managed to snag a 9 Pro for a good price, but it is the Chinese version (Needed dual-SIM), meaning it came with Color OS.
I have already managed to "Downgrade" the Color OS to Oxygen OS using another thread here. Worked flawlessly other then the IEMI...It's currently on 11.2.2.2DA.
Is there anyone that has managed to swap from 11.2.2.2DA to BA? I don't really want to root at this moment (maybe ill get into that at a later date)
I do have an OTA file for 11.2.2.2BA but when I use the local update, it just says it can't upgrade to a lower version.
Any ideas?
Natester769 said:
Hello All,
It has been a while since I have been around the XDA forums, needless to say I needed a new user! haha. I used to run custom ROMs on older Samsung devices, but got out of the game when I could never pass safetynet. Needless to say, I have now stepped into the world of OnePlus, and so far I am impressed! I managed to snag a 9 Pro for a good price, but it is the Chinese version (Needed dual-SIM), meaning it came with Color OS.
I have already managed to "Downgrade" the Color OS to Oxygen OS using another thread here. Worked flawlessly other then the IEMI...It's currently on 11.2.2.2DA.
Is there anyone that has managed to swap from 11.2.2.2DA to BA? I don't really want to root at this moment (maybe ill get into that at a later date)
I do have an OTA file for 11.2.2.2BA but when I use the local update, it just says it can't upgrade to a lower version.
Any ideas?
Click to expand...
Click to collapse
You have to wait for the next version.
excute this command and you can install the BA vesion package on DA 11.2.2.2
Q: How do I switch to Europe or Global OS?
A: Wait for the new version, download the #Full package and Local Update it. If you have Magisk installed, you can try to Local Update after entering the following command (need ROOT access).
resetprop ro.build.date.utc 1400000000
resetprop ro.system.build.date.utc 1400000000
Wait for coloros to oxygenos step
Thanks for the quick replies,
It appears everything ColorOS wise always points towards the Indian Edition. Not that it isn't stable or anything, I think the UK Version covers more radio bands which may work better here in NA. I was under the impression once I am on OOS, I am no longer tied to anything COS...
I see that 11.2.3 is available as an OTA update, but I don't see any links yet. My history with rooting and roms was that I could always change to the same version or higher, just never lower. I'm doing this in my case, but maybe that is changed with Oneplus where it wants to see higher only.
I will just wait till a link for 11.2.3 is available from OTA and go from there!
Thanks.
Hello all,
As the 11.2.3.3 OTA update came out for BA today, I tried to perform a local update to get it to BA.
Looks like everything went great. IEMI is still broken due to the COS to OS swap, but it isn't really concerning to me at the moment. I have backups of the original so I should be good.
Just posting to let anyone who reads know!
Actaurian said:
excute this command and you can install the BA vesion package on DA 11.2.2.2
Q: How do I switch to Europe or Global OS?
A: Wait for the new version, download the #Full package and Local Update it. If you have Magisk installed, you can try to Local Update after entering the following command (need ROOT access).
resetprop ro.build.date.utc 1400000000
resetprop ro.system.build.date.utc 1400000000
Click to expand...
Click to collapse
Do you mean going into fastboot, and entering these commands, and then subsequently rebooting into system, and then try and local upgrade? Please be clear with these steps and descriptions.
Actaurian said:
执行此命令，即可在DA 11.2.2.2上安装BA vesion软件包。
问：如何切换到欧洲或全球操作系统？
答：等待新版本，下载#Full软件包并对其进行本地更新。如果安装了Magisk，则可以在输入以下命令（需要ROOT访问权限）后尝试进行本地更新。
resetprop ro.build.date.utc 1400000000
resetprop ro.system.build.date.utc 1400000000
Click to expand...
Click to collapse
Ťthanks!
Natester769 said:
Hello All,
It has been a while since I have been around the XDA forums, needless to say I needed a new user! haha. I used to run custom ROMs on older Samsung devices, but got out of the game when I could never pass safetynet. Needless to say, I have now stepped into the world of OnePlus, and so far I am impressed! I managed to snag a 9 Pro for a good price, but it is the Chinese version (Needed dual-SIM), meaning it came with Color OS.
I have already managed to "Downgrade" the Color OS to Oxygen OS using another thread here. Worked flawlessly other then the IEMI...It's currently on 11.2.2.2DA.
Is there anyone that has managed to swap from 11.2.2.2DA to BA? I don't really want to root at this moment (maybe ill get into that at a later date)
I do have an OTA file for 11.2.2.2BA but when I use the local update, it just says it can't upgrade to a lower version.
Any ideas?
Click to expand...
Click to collapse
Hi, I have an OP9 Pro China version with Color OS and I also want to flash it to Oxygen OS. The Color OS version of my OP9 Pro was upgraded to A.04 version. Please advise if I can flash my phone to 11.2.2.2DA. I am not sure if 11.2.2.2DA is the higher version or not (compared with Color OS A.04). Please also advise if you followed the instructions from the post on OP Chinese forum to flash your 9 pro to 11.2.2.2DA, then use the same method to flash it to 11.2.2.3BA. Have you tried to flash your 9 pro to the AA global version? Sorry for so many questions. I haven't flash ROM since OP3T and I forget how it works. Thanks.
waiwaifong said:
Hi, I have an OP9 Pro China version with Color OS and I also want to flash it to Oxygen OS. The Color OS version of my OP9 Pro was upgraded to A.04 version. Please advise if I can flash my phone to 11.2.2.2DA. I am not sure if 11.2.2.2DA is the higher version or not (compared with Color OS A.04). Please also advise if you followed the instructions from the post on OP Chinese forum to flash your 9 pro to 11.2.2.2DA, then use the same method to flash it to 11.2.2.3BA. Have you tried to flash your 9 pro to the AA global version? Sorry for so many questions. I haven't flash ROM since OP3T and I forget how it works. Thanks.
Click to expand...
Click to collapse
I basically followed this guide on getting COS to OOS. https://www.oneplusbbs.com/thread-5895784-1.html. I believe I was on version A.03 when I did the update, but I could have been on A.04. It was as easy as downloading the right firmware and applying it via a local update. It brought me right to 11.2.2.2DA. *This does seem to break IEMI*
I then used the 11.2.2.3BA version downloaded right from XDA, and applied it via a local update.
I have not gone to global as I need dual SIM. So I can't help you there....
Natester769 said:
I basically followed this guide on getting COS to OOS. https://www.oneplusbbs.com/thread-5895784-1.html. I believe I was on version A.03 when I did the update, but I could have been on A.04. It was as easy as downloading the right firmware and applying it via a local update. It brought me right to 11.2.2.2DA. *This does seem to break IEMI*
I then used the 11.2.2.3BA version downloaded right from XDA, and applied it via a local update.
I have not gone to global as I need dual SIM. So I can't help you there....
Click to expand...
Click to collapse
Thanks for your detailed reply. Will try soon.
How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...
Hi, so I recently got a pre-owned OnePlus 7T (Android version 12) and looking to root it. Not looking to do anythig mega fancy with it, basically spoof pokemon go.
I have never had a samsung before so I know none of the lingo (roms, roots, apks, flash etc). I've tried watching videos but a lot of people specifically mention 7T Pro or don't specifically mention Android version 12, which I'm guessing if it's like iOS then the version is important.
I was wondering if anyone could point me in the right direction on how to root the phone to do what I want to do with it. I've got as far as developer mode with it. I have a windows PC handy if that helps too?
Thanks
Is it so hard to search?
https://forum.xda-developers.com/t/guide-android-11-how-to-root-oneplus-7t.4253183/
Extract boot from here:
https://forum.xda-developers.com/t/oneplus-7t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.3997037/
This is XDA.
So members are expected to be proactive.
Hi, thanks for the response!
The first link says android 11, not 12, so like I had mentioned, I have no idea how it works with androids and whether the two are interchangeable.
The second link doesn't mention any android version and I can't see a mention of android 12 in the comments, thus I wouldn't have followed through with the guide as I can't clearly see it will work for OnePlus 7T Android 12.
So, having searched the site which I'm not used to, and having asked in discords and only being told to go ask here, I did what I was told and went and asked here. I apologise for how repetitive the question may be, but I'm just hoping some kind soul will have a little pitty and put me on the right path.
1.Guide is the same for Android 12
2.
E.g.
HD1903_11_F.17 (delivered to OOS 11 users): HD1903_11.F.17_3170_202210120443
MD5: c0efb9eacc32eac171fccd6cd306ecaa
is Android 12 for Europe
So all the last entries are A12.
Or download with Oxygen Updater App
Use this for extraction of the boot.img
https://forum.xda-developers.com/t/...and-other-img-files-from-payload-bin.4442149/
Tomcar said:
1.Guide is the same for Android 12
2.
E.g.
HD1903_11_F.17 (delivered to OOS 11 users): HD1903_11.F.17_3170_202210120443
MD5: c0efb9eacc32eac171fccd6cd306ecaa
is Android 12 for Europe
So all the last entries are A12.
Or download with Oxygen Updater App
Use this for extraction of the boot.img
https://forum.xda-developers.com/t/...and-other-img-files-from-payload-bin.4442149/
Click to expand...
Click to collapse
Hi again,
I've taken what you said and reflashed the phone and upgraded to OOS 11.0.9.1 (latest available).
The links you sent are super useful now I know they work for any version, though following it broke my phone last night (my fault), likely during the patched_boot.img stage as the lingo started confusing me.
Does the below youtube offer an alternative method to root the phone? I've found the software build for 11.0.9.1 and hoping if that guide works then I'll follow that and ideally not need to bother you more
It's not an alternative, it's the same only as a video
However, better use the payload-gui.exe for extracting the payload bin.
Much easier.
Good luck
I am currently on HD1905_11_F.20 (Android 12) and still having the network data issues.
Does anyone know if I can use one of One Plus's rollback packages to downgrade (there isn't one provided for the HD1905). If so, global variant I assume?
I am unable to use the MSM tool to downgrade because I don't have a window's PC with admin permission.
If that's not an option, can I go from my current build to a custom ROM to fix the data issues? I'd prefer Pixel Experience as banking, netflix, and camera seemed to work well for me with little effort in the past. I know with PE the networks issues would continue previously; they still have it was one of the install notes but was hoping this might have been fixed.
Any other options? I just want a working phone.
rspear said:
I am currently on HD1905_11_F.20 (Android 12) and still having the network data issues.
Does anyone know if I can use one of One Plus's rollback packages to downgrade (there isn't one provided for the HD1905). If so, global variant I assume?
I am unable to use the MSM tool to downgrade because I don't have a window's PC with admin permission.
If that's not an option, can I go from my current build to a custom ROM to fix the data issues? I'd prefer Pixel Experience as banking, netflix, and camera seemed to work well for me with little effort in the past. I know with PE the networks issues would continue previously; they still have it was one of the install notes but was hoping this might have been fixed.
Any other options? I just want a working phone.
Click to expand...
Click to collapse
Ok to rollback using glo or Indian rollback package and ota update
HueyT said:
Ok to rollback using glo or Indian rollback package and ota update
Click to expand...
Click to collapse
thanks guy! worked well.
Now I can wait for a good deal on a phone.