Related
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Andrew8578 said:
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Click to expand...
Click to collapse
Same here, was literally just googling for help.
vibrantliker said:
Same here, was literally just googling for help.
Click to expand...
Click to collapse
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
You may not want to hold your breath on that one. For whatever reason, oneplus does not release full OTA zips for AA half the time. (WTF ONEPLUS). Because of this, I long since started flashing BA over my global phone. As the gentleman said up above, it works absolutely perfectly.
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
can I just flash the BA version on top of my current rom (AA) and not lose anything? I just got done reinstalling everything, and it was a pain. I don't want to do this a 3rd time, if I can avoid it.
I never had any issues with rooting/being unlocked and updating on my previous OnePlus phones... this is a new one for me.
On 8t I had to use EU..google is who releases OTAs for all variants except EU, which is still directly from oneplus. Rooting broke OTAs for me as well on any other rom besides EU...also I have 9pro, which I local updated to EU zip b4 flashing magisk_boot.img and I already received new update since rooting and all is good.
I just flashed BA on top on my current rom via system update (you have to click the cog wheel top right and put the OTA zip on your root directory)
Nothing changed and the navigation bar in split screen is indeed fixed, meaning this is the latest version.
Thanks again for letting me know about this!
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
zoman7663 said:
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Click to expand...
Click to collapse
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
bulletbling said:
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
Click to expand...
Click to collapse
Noted, thanks for the info.
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
What I want to know too!
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
bulletbling said:
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
Click to expand...
Click to collapse
geez, I hope we don't have to relock and unlock for every update. I guess for the time being, there's no reason to be unlocked, but when custom ROM's start rolling out, that's going to be a major headache. I wonder if/when the updates are posted on One Plus website, will the updates work, or will root/unlock still prevent it?
I really want that update as I'm reading it made the battery much better. What to do!
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
TPXX said:
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
Click to expand...
Click to collapse
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
vibrantliker said:
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
Click to expand...
Click to collapse
My last rooting experience was on an S7. Afraid I can't help you with this one.
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Fatmonk8 said:
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Click to expand...
Click to collapse
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
TheKnux said:
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
Click to expand...
Click to collapse
To de-bloat.
But if that's the only positive this go around then it's probably not worth me doing since I have been de-bloating more with ADB lately. But if others have any input on other benefits then I may do it again.
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
TheKnux said:
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
Click to expand...
Click to collapse
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Fatmonk8 said:
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Click to expand...
Click to collapse
So I spent a week figuring this out. I realized a few days ago that I mistakenly flashed the Indian firmware for the OnePlus 9 PRO. I have the regular 9. I tried to flash every other msm I could find and download. Nothing seems to work except the Indian OnePlus 9 PRO msm... Problem is, the camera, flash and fingerprint scanner didn't work. I was able to toggle the unlock oem button by running an adb command line then I did oem unlock in fastboot. After that, I followed the instructions for installing StagOs 12.1, which involves installing lineage recovery then flashed the rom. Everything works flawlessly! Love this rom.
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
My TMo OP9P LE2127 had updated to OOS12 before I had a chance to root it. I hadn't read enough about it to worry about trying to block the update. Well, I hated OOS12 and I eventually downgraded back to Stock OOS11 and then converted it EU with the MSM tool. Currently running a rooted OOS11.2.10.10 on both slots.
Not once did I have to touch the modem and my 5G works just fine. Everything worked out of the box (aka conversion MSM). My phone is even still SIM locked. I believe others have experienced the same thing with a LE2127 that updated to the stock TMo OOS12 firmware. The modem seems to stick after that upgrade, even after downgrading it back to OOS11.
I've blocked my phone from manually checking for updates and I'm perfectly happy with my phone for the time being. That said, I have not tried updating my phone to any EU versions of OOS12 (C.48 being the latest, I think?).
So, that's my experience, but your mileage may vary.
SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
razercortex said:
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
Click to expand...
Click to collapse
Yeah, that could work. Does build.prop need to be updated after each OTA update?
SmartMart92 said:
Yeah, that could work. Does build.prop need to be updated after each OTA update?
Click to expand...
Click to collapse
Shouldn't need to be updated.
Also, you could try unlocking bootloader, rooting, modifying build.prop, unrooting, then relocking bootloader if you're ok with testing. It may/may not work. If it works, then you don't need to modify ever again, at least until a future update touches that file.
If I have no sims detected am I able to flash something to regain sim detection and data?
Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.
Which phone version do you have?
luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.
skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing
I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!
TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,
I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.
I read multiple threads about converting LE2127 to EU/NA, and there appears to be many ways to do it, but I don't understand why I would take one way or another. And which steps are required and in what circumstances. All guides cover "how" but barely ever "why" or "when". Therefore, please help me here, and help in my very specific case:
Circumstances:
SIM is already unlocked
I will have unlock.bin in a couple days
I'm on LE2127_11_C.21
I want the latest OnePlus-provided OxygenOS
Given these circumstances:
What is the simplest way to convert LE2127 (US T-Mobile) to non-TMO image with Magisk root?
Does it matter whether I go for LE2123 / EU image, or LE2125 / global image? If it does, what are the consequences of going for one or the other?
Nowaker said:
I read multiple threads about converting LE2127 to EU/NA, and there appears to be many ways to do it, but I don't understand why I would take one way or another. And which steps are required and in what circumstances. All guides cover "how" but barely ever "why" or "when". Therefore, please help me here, and help in my very specific case:
Circumstances:
SIM is already unlocked
I will have unlock.bin in a couple days
I'm on LE2127_11_C.21
I want the latest OnePlus-provided OxygenOS
Given these circumstances:
What is the simplest way to convert LE2127 (US T-Mobile) to non-TMO image with Magisk root?
Does it matter whether I go for LE2123 / EU image, or LE2125 / global image? If it does, what are the consequences of going for one or the other?
Click to expand...
Click to collapse
Sim unlock is not a requirement for this device but it's good you have it already.
Using the Tmo->Eu conversion bypasses the need for unlock.bin but again, it's good that you have that coming as well.
The simplest way is to use the Tmo->Eu MSM conversion tool and then Oxygen Updater over to global if you want to do that instead of stay on Eu. Either way, using the conversion tool is the way.
From my current understanding, the only real functional difference from Eu vs Global is the latest update speed. I've read that Global was getting the latest updates first. Others report they're available on Eu also and the app was caching old results. I can't be sure on that as I stayed on Eu and I stay on Android 11 (11.2.10.10) but that's what I've read. Hopefully someone else will have additional information on any technical differences. I've been fine using Eu on Tmo/USA.
Since you're interested in going to the latest version, Oos13, you won't need to flash the modem back in as that was fixed for oos13.
You should definitely backup your efs and modemst1/2 partitions before you do anything else.
Open MSM, press F8, select the partitions you want to backup, password is "oneplus". Press read back and they will be stored in C:\ root.
It is advised to unlock bootloader on Android 11 before updating to any other version. I unlocked bootloader and rooted with Magisk on A11 right away. Using the MSM tool to readback boot_a and adb push it onto device. Then having magisk apk patch that boot_a. In my case, by unlocking bootloader and then taking OTA, I retain L1 drm. If I take OTA and then unlock bootloader, I lose L1 drm.
Temp unroot, take the OTA, magisk install to inactive slot, repeat until you're at the firmware you want. Check replies at the back end of this thread: https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/
for which OTA route others are taking to get to oos13
To convert your physical T-Mobile sim to an e sim
Go to the home screen. to open the menu, swipe up on the screen.
scroll to the right, choose settings
scroll down choose connections.
choose a sim card manager.
choose sim 1.
choose convert to eSIM
chooses OK.
Thank you @Appreciative for explaining this. I'm very appreciative of your help.
Global/EU thing is now clear to me. Speaking of unlocking the bootloader, I have more to ask.
Appreciative said:
It is advised to unlock bootloader on Android 11 before updating to any other version.
Click to expand...
Click to collapse
So I'm already on LE2127_11_C.21 which is the latest version available to me. I'm actually unsure what OxygenOS version it is. "About device" says Android 12, security update November 5, 2022. There is no indication what OOS version it is anywhere in the settings. Is it OOS 12 or OOS 13?
Anyway, I upgraded all the way to LE2127_11_C.21 after I received the phone. Should I downgrade to the original OOS11 ? And how, given full OTA images for LE2127 are nowhere to be found?
Should I follow the instructions in OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)? Like I said before, all guides cover "how" but barely ever "why" or "when", and that one is no different.
Appreciative said:
In my case, by unlocking bootloader and then taking OTA, I retain L1 drm. If I take OTA and then unlock bootloader, I lose L1 drm.
Click to expand...
Click to collapse
Why is it important? What are the consequences of losing?
Nowaker said:
Thank you @Appreciative for explaining this. I'm very appreciative of your help.
Global/EU thing is now clear to me. Speaking of unlocking the bootloader, I have more to ask.
So I'm already on LE2127_11_C.21 which is the latest version available to me. I'm actually unsure what OxygenOS version it is. "About device" says Android 12, security update November 5, 2022. There is no indication what OOS version it is anywhere in the settings. Is it OOS 12 or OOS 13?
Anyway, I upgraded all the way to LE2127_11_C.21 after I received the phone. Should I downgrade to the original OOS11 ? And how, given full OTA images for LE2127 are nowhere to be found?
Should I follow the instructions in OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)? Like I said before, all guides cover "how" but barely ever "why" or "when", and that one is no different.
Why is it important? What are the consequences of losing?
Click to expand...
Click to collapse
Android 12 shipped by OnePlus is oos12. Same for 11/13 and any other. All oos12 is android 12 but not all android 12 is oos. For all OnePlus devices, it's OOS (or ColorOS).
(To make this more confusing, OnePlus for some reason, labels the oos12 packages as _11_C.xx but it's not Android 11. That is why most of the forum mentions them by C.xx and for oos13, F.xx)
You are on oos12.
Follow the conversion thread, you won't need that thread you posted unless you brick and want to go back to stock Tmo firmware to start over again clean. The one I posted is the one you'll use.
When you use the MSM tool, you'll automatically go back to Android 11 early version. It's advised to unlock bootloader from Android 11 for two reasons. One is what I mentioned about my situation. I lose L1 drm by unlocking right after the msm conversion tool but I regain L1 drm after taking the OTA to 11.2.10.10. The other reason is for people without their unlock token. You've already submitted to OnePlus website so this may not affect you. For those who converted to Eu to bypass the unlock.bin token from OnePlus, they NEED to unlock the bootloader on A11 because the bypass is gone/fixed in Android 12/13. They require the unlock.bin if they didn't unlock bootloader in A11.
After you do the MSM Eu->Tmo tool (https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/), you will be on Android 11, OOS11, 11.2.3.3 - You can unlock the bootloader there without the token or wait for your token and unlock it later.
After you MSM, you'll start in a clean Android/OOS 11 state. Then you get oxygen updater from play store and update to oos12 and then oos13.
Looking in the back pages of the thread above, you will see which route people take to get there. I BELIEVE it is to take the local upgrade to C.65 (oos12) and then F.16 (oos13).
Losing L1 drm is typically from losing Device Certification. When that happens, google pay, Netflix, Disney+ and other apps that require certification may not work at all or diminished.
If you get to oos13 and have lost L1 drm, do not panic, you have some options to get it back since you'll be rooting along the way. The standard approach is using USNF (universal safetynet fix) module in Magisk. There is a thread a few posts down that's labeled wrong, it's labeled as a question but it's a how-to GooglePay/cts passing (https://forum.xda-developers.com/t/oos13-gpay-cts-profile-fix-for-unlocked-bootloader.4525423/)
Thanks again, @Appreciative!
Appreciative said:
When you use the MSM tool, you'll automatically go back to Android 11 early version. It's advised to unlock bootloader from Android 11 for two reasons.
Click to expand...
Click to collapse
So by you saying that, it means I can use the MSM tool you linked without having to unlock the bootloader beforehand. Is that correct?
Appreciative said:
After you MSM, you'll start in a clean Android/OOS 11 state. Then you get oxygen updater from play store and update to oos12 and then oos13.
Click to expand...
Click to collapse
And then I should be able to pick NA or EU, and it won't really matter, right? Since after I MSM the phone, it identifies itself as LE2125 while previously it was LE2127?
Appreciative said:
Losing L1 drm is typically losing Device Certification. When that happens, google pay, Netflix, Disney+ and other apps that require certification may not work at all or diminished.
Click to expand...
Click to collapse
Ah. The SafetyNet, ctsProfile, and all that stuff. I didn't know it also goes by L1 DRM name. Thanks for clarifying.
Appreciative said:
Temp unroot, take the OTA, magisk install to inactive slot, repeat until you're at the firmware you want. Check replies at the back end of this thread: https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/
Click to expand...
Click to collapse
I think everything is clear to me to the point of MSMing the phone, which turns it into LE2123 (EU). Can you confirm these are the steps to get there?
1. Starting from LE2127_11_C.21 (current firmware - OOS12 / Android 12 / T-Mobile)
2. Use the MSM TMo->EU conversion tool which downgrades the phone to Android 11, OOS11, 11.2.3.3, identified as LE2123 (EU)
3. Unlock bootloader.
But now what? When and how exactly do I do things with Magisk? I did the extract-boot.img-patch-and-flash process multiple times on OnePlus 8, OnePlus 8T, OnePlus 9 Pro (Global). It's easy. But it appears things get tricky here on OP9P LE2127 T-Mobile version, so I'd like some clarification.
Am I supposed to patch boot.img with Magisk App? But what do I extract the boot.img from at this stage?
Nowaker said:
Thanks again, @Appreciative!
So by you saying that, it means I can use the MSM tool you linked without having to unlock the bootloader beforehand. Is that correct?
And then I should be able to pick NA or EU, and it won't really matter, right? Since after I MSM the phone, it identifies itself as LE2125 while previously it was LE2127?
Ah. The SafetyNet, ctsProfile, and all that stuff. I didn't know it also goes by L1 DRM name. Thanks for clarifying.
I think everything is clear to me to the point of MSMing the phone, which turns it into LE2123 (EU). Can you confirm these are the steps to get there?
1. Starting from LE2127_11_C.21 (current firmware - OOS12 / Android 12 / T-Mobile)
2. Use the MSM TMo->EU conversion tool which downgrades the phone to Android 11, OOS11, 11.2.3.3, identified as LE2123 (EU)
3. Unlock bootloader.
But now what? When and how exactly do I do things with Magisk? I did the extract-boot.img-patch-and-flash process multiple times on OnePlus 8, OnePlus 8T, OnePlus 9 Pro (Global). It's easy. But it appears things get tricky here on OP9P LE2127 T-Mobile version, so I'd like some clarification.
Am I supposed to patch boot.img with Magisk App? But what do I extract the boot.img from at this stage?
Click to expand...
Click to collapse
To be clear, L1 drm is a separate thing from Safetynet and CTS. L1 dropping to L3 is a result of "insecure device". When you unlock the bootloader, the device is detected as modified. That state fails safetynet. A byproduct of that is DRM drops down to L3. L3 means apps like Netflix will only work in SD quality, if at all. Some apps won't even open or show up in play store when device is not certified. L1/L3/Safetynet/cts aren't exactly interchangeable even tho I kinda made it sound that way. Just in the context that when you are not passing safetynet, a byproduct is you lose L1 drm, because of the device certification not passing.
Yes, you can use the MSM conversion tool without the bootloader being unlocked.
MSM Tmo->Eu conversion tool.
Unlock bootloader.
Download Oxygen Updater in play store.
Root with Magisk.
I pull my boot image using the MSM tool readback as mentioned above, after the conversion and before I take the OTA.
MSM->F8->boot_a and see it in C:
Then I adb push C:\boot_a.img to /sdcard/
Magisk patch the just-pushed boot image.
Temp boot that boot image with:
fastboot boot boot magisk-patched-boot.img
That will temporarily boot you with root. You have to finish the magisk install from here.
Then I reboot and ensure phone is rooted properly.
I download the OTA and let it install. Do not let it reboot after the OTA is finished. You need to go back to magisk and temp unroot by pressing "uninstall magisk" and choose "restore images". Then choose the option for 'flash to other slot OTA'.
This information is based on me going from 11 early to 11 later. There may be some changes for 12/13 that someone else can chime in on.
Alternatively, you can wait to root until later.
Things really aren't tricky on this model. It's actually pretty smooth with the conversion tool. * At least for 11 in my experience. Someone else will have to help you more for 12->13 as I haven't done that. My oxygen updater currently shows release version LE2123_11_F.72 (Eu) or LE2125_11_F.17 (global)
Both of which are oos13. I don't know if it's possible to jump from 11 to 13. I've only read reports of going to 12 and then 13 but I don't read much of 12/13 as I'm staying on 11
Appreciative said:
To be clear, L1 drm is a separate thing from Safetynet and CTS. L1 dropping to L3 is a result of "insecure device". When you unlock the bootloader, the device is detected as modified. That state fails safetynet. A byproduct of that is DRM drops down to L3. L3 means apps like Netflix will only work in SD quality, if at all. Some apps won't even open or show up in play store when device is not certified. L1/L3/Safetynet/cts aren't exactly interchangeable even tho I kinda made it sound that way. Just in the context that when you are not passing safetynet, a byproduct is you lose L1 drm, because of the device certification not passing.
Click to expand...
Click to collapse
OK, cool. So after following the guide, I still should look "secure" for everything, right? On my old OnePlus 9 Pro LE2125, I'm passing SafetyNet, and my GPay works - even though I have Magisk and root. (And use my old phone via `scrcpy` because I broke its display lol)
Appreciative said:
I pull my boot image using the MSM tool readback as mentioned above, after the conversion and before I take the OTA.
MSM->F8->boot_a and see it in C:
Then I adb push C:\boot_a.img to /sdcard/
Magisk patch the just-pushed boot image.
Temp boot that boot image with:
fastboot boot boot magisk-patched-boot.img
That will temporarily boot you with root. You have to finish the magisk install from here.
Then I reboot and ensure phone is rooted properly.
I download the OTA and let it install. Do not let it reboot after the OTA is finished. You need to go back to magisk and temp unroot by pressing "uninstall magisk" and choose "restore images". Then choose the option for 'flash to other slot OTA'.
Click to expand...
Click to collapse
OK, sounds good. Thank you.
Just to clarify: by saying "download the OTA", do you mean using the system-provided update tool, or are we talking about downloading LE2125_11_F.16 from Oxygen Updater?
You also made me learn about "install to inactive slot" - https://topjohnwu.github.io/Magisk/ota.html. I wasn't aware it existed. I applied any OTA updates in the past manually. Download full OTA, extract boot.img, patch it with Magisk, flash OTA and patched boot. Like a fresh install. Also explains why I barely ever upgraded.
Nowaker said:
OK, cool. So after following the guide, I still should look "secure" for everything, right? On my old OnePlus 9 Pro LE2125, I'm passing SafetyNet, and my GPay works - even though I have Magisk and root. (And use my old phone via `scrcpy` because I broke its display lol)
OK, sounds good. Thank you.
Just to clarify: by saying "download the OTA", do you mean using the system-provided update tool, or are we talking about downloading LE2125_11_F.16 from Oxygen Updater?
You also made me learn about "install to inactive slot" - https://topjohnwu.github.io/Magisk/ota.html. I wasn't aware it existed. I applied any OTA updates in the past manually. Download full OTA, extract boot.img, patch it with Magisk, flash OTA and patched boot. Like a fresh install. Also explains why I barely ever upgraded.
Click to expand...
Click to collapse
Well that's where we can both be unsure. I've read that you should go to 12 (c.xx) and then 13 (f.xx) using Oxygen Updater. However, I used the built in system updater ota to get from 11.2.3.3 to 11.2.10.10 myself. I believe you are supposed to use the oxygen updater apk from play store to get to 13 but for that ... someone else will have to clarify exactly which way to get to 12/13. It is for sure covered in this forum, I just have no reason to remember it as I'm staying on 11.
Even if you decide to root later instead of earlier on and Magisk uninstall each time, you can use MSM to readback the boot image and send it over for patching. It's not a big hassle.
After the conversion, you won't have mobile service until you either get to oos13 or flash the modem (modem_a/b not modemst1/2) back in . Don't panic if you see no signal right after Eu conversion is my point
OK, cool. So after following the guide, I still should look "secure" for everything, right?
Click to expand...
Click to collapse
Either way, you should install USNF magisk module and clear cache of google apps to get or stay device certified. That is outlined in the thread I linked above for oos13.
This device has a lot of pros. We can have root and unlocked bootloader, pass safetynet and retain L1 drm, doesn't require sim unlock to unlock bootloader (only needs minor bypass for the OEM unlocking the toggle), unlock.bin bypass with Crazazn's conversion tool, ability to flash over to other firmware regions, and good custom rom and mod support
Appreciative said:
Either way, you should install USNF magisk module and clear cache of google apps to get or stay device certified.
Click to expand...
Click to collapse
For the record - my current One Plus 9 Pro LE2125 (not the new one LE2127 I just purchased) has Android 11, OOS 11.2.7.7.LE15AA. It's rooted and passes all SafetyNet and stuff, and I don't have any extra Magisk modules.
Are you saying it's upgrading to newer versions of Android / OxygenOS that enhances security, and requires us to use extra Magisk modules to hide the fact our bootloader is unlocked?
Nowaker said:
For the record - my current One Plus 9 Pro LE2125 (not the new one LE2127 I just purchased) has Android 11, OOS 11.2.7.7.LE15AA. It's rooted and passes all SafetyNet and stuff, and I don't have any extra Magisk modules.
Are you saying it's upgrading to newer versions of Android / OxygenOS that enhances security, and requires us to use extra Magisk modules to hide the fact our bootloader is unlocked?
Click to expand...
Click to collapse
I'm not saying that but it's probably a fair deduction. I had the same experience as you when I took OTA to 11.2.10.10, I was certified still. Prior to that (11.2.3.3.), I was not certified when bootloader unlocked. I keep usnf module installed just for extra assurance. Although, in some cases on our devices, it will be required to pass safetynet. There's a whole thread-in-thread on the hit&miss nature of some people losing certification and others keeping it, supposedly on the same exact set ups. Then I experienced it myself on the 10T. It sounds like it's more necessary on oos13 but I can't be sure.
As a side note, I'm still very tempted to try oos13. I've heard it's really smooth on this phone. Please let me know how you feel about it. Especially in comparison to oos11
Appreciative said:
As a side note, I'm still very tempted to try oos13. I've heard it's really smooth on this phone. Please let me know how you feel about it. Especially in comparison to oos11
Click to expand...
Click to collapse
I will. I'm collecting information on all the steps, before I start doing it. I think I'm ready but it's also a matter of available time to sit down and do it. With busy life, I don't know if it's going to be tomorrow, or some evening next week.
Note however I'm a pretty non-standard Android user. I keep thing my way. I always use Nova Launcher - which automatically keeps a lot of new features away for me. I may not really experience any difference once my things are in. All I really care about is AdAway and Vanced for stress-free experience, a fully functional Android Auto for driving, Google Photos and Nextcloud for photo backups, and that's about it.
Nowaker said:
I will. I'm collecting information on all the steps, before I start doing it. I think I'm ready but it's also a matter of available time to sit down and do it. With busy life, I don't know if it's going to be tomorrow, or some evening next week.
Note however I'm a pretty non-standard Android user. I keep thing my way. I always use Nova Launcher - which automatically keeps a lot of new features away for me. I may not really experience any difference once my things are in. All I really care about is AdAway and Vanced for stress-free experience, a fully functional Android Auto for driving, Google Photos and Nextcloud for photo backups, and that's about it.
Click to expand...
Click to collapse
I've read Android Auto is broken after Android 11, not sure what fixes are available however. I've read tons of people having issues with AA after upgrade to 12. Not OnePlus specific, I've read about samsung, Realme, asus rog and others all not connecting after Android 11. I think it might be something to do with AA going away. May be something to look into before heading to 13 if it's a must-have for you.
I have AA set up as well. The only issue is when I do screen2auto, to get the icon in my headunit to open s2a, I must uninstall AA update, connect to my car, then upgrade back to latest AA. Then I'm able to cast/mirror my screen to my navigation screen. The kids like to watch youtube videos and whatnot while we are on the road. Or, if they bring their tablets, I use VPN Hotspot for bypassing the Tmo throttle of 600kbps on hotspot connected devices. They can youtube their choice for the rest of the ride. (Playing iSpy, find the colored car, count the diesel trucks etc only lasts for about 15 mins)
I also use Vanced. I tried ReVanced but it started glitching my screen out. I'll give them some time to fix their bugs before I head over to it. It's kinda cool because you can (must) patch in/out the features you want on whatever youtube apk you want. It's still a bit early based on the bugs I experienced but I am sure it'll get better over time
Appreciative said:
That will temporarily boot you with root. You have to finish the magisk install from here.
Then I reboot and ensure phone is rooted properly.
I download the OTA and let it install. Do not let it reboot after the OTA is finished. You need to go back to magisk and temp unroot by pressing "uninstall magisk" and choose "restore images". Then choose the option for 'flash to other slot OTA'.
Click to expand...
Click to collapse
I'm not sure if this works for the 9 pro (I'm researching conversion of a t-mo model that I'm thinking of ordering ATM) but on my 7T I always take the option to download the full update image (usually like ~2GB) and install to the inactive slot, then you just inatall magisk to the inactive before rebooting. That lets you skip the uninstall bit and allows you to roll back to the current rooted state if there're any problems with the update. It's a bigger download than an OTA patch but it's fewer steps altogether.