Question What is the simplest way to convert LE2127 (US T-Mobile) to non-TMO image?

[Nowaker]

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:

1. What is the simplest way to convert LE2127 (US T-Mobile) to non-TMO image with Magisk root?
2. 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?

 

[Appreciative]

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:

1. What is the simplest way to convert LE2127 (US T-Mobile) to non-TMO image with Magisk root?
2. 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?

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

 

[dctinc12]

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.

 

[Nowaker]

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.

It is advised to unlock bootloader on Android 11 before updating to any other version.

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.

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.

Why is it important? What are the consequences of losing?

 

[Appreciative]

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?

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/)

 

[Nowaker]

Thanks again, @Appreciative!

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.

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?

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.

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?

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.

Ah. The SafetyNet, ctsProfile, and all that stuff. I didn't know it also goes by L1 DRM name. Thanks for clarifying.

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/

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?

 

[Appreciative]

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?

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

 

[Nowaker]

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.

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)

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'.

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.

 

[Appreciative]

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.

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

 

[Appreciative]

OK, cool. So after following the guide, I still should look "secure" for everything, right?

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

 

[Nowaker]

Either way, you should install USNF magisk module and clear cache of google apps to get or stay device certified.

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?

 

[Appreciative]

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?

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

 

[Nowaker]

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

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.

 

[Appreciative]

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.

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

 

[o muerte]

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'.

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.