How To Guide Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!

Search This thread

petchportgach

Member
Oct 10, 2022
9
2
Thailand
  1. Download and unzip the conversion package:
    • EU 11.2.3.3
      MD5: cb949816fa80d5f0d984359b819426c3
  2. Boot to bootloader.
    • From adb:
      Code:
      adb reboot bootloader
    • From fastboot/bootloader:
      Code:
      fastboot reboot bootloader
  3. Execute "flash_all.bat" from the unzipped directory from step 2.
  4. Reboot into recovery, and wipe everything.

Where is this rom (EU 11.2.3.3) with that .bat file?
I don't see the flash_all.bat neither
 

TinkerNerd

Member
Sep 29, 2022
10
5
For anyone having trouble with the MSM tool, there's another way to do this. The following steps assume you have adb and fastboot installed and your SIM and bootloader are unlocked.
1) Using the Oxygen Updater app, download the latest (full) global firmware, then copy the zip file to your adb/fastboot folder. Rename the zip file to firmware.zip
2) Download the TWRP recovery, rename the file to twrp.img and copy it to your adb/fastboot folder
3) Place your phone into fastboot mode
4) Using fastboot, boot the TWRP recovery image (fastboot boot twrp.img)
5) Once your phone has booted the TWRP image, select Advanced, then select ADB Sideload
6) Use ADB to sideload the downloaded firmware (adb sideload firmware.zip)

Remember to flash your NON-HLOS.bin onto your phone so you can get service

DISCLAIMER: This is just what worked for me after a fair bit of trial and error and experimentation. I only tried this because I couldn't get the MSM tool to work for me. If the MSM tool works for you, you should probably use that instead
 
  • Like
Reactions: handydandy

petchportgach

Member
Oct 10, 2022
9
2
Thailand
I tried to use the msm method but it kept saying "unsupport_device_in". When I got this phone, it had indian rom (DA) le2127 and I bricked it once. However the mobile repair store managed to unbrick it and restore it to (ACB) and now I am trying to convert it to EU but i don't know how to fix the "unsupport_device_in". Maybe I should try #402's method?
 

TinkerNerd

Member
Sep 29, 2022
10
5
I tried to use the msm method but it kept saying "unsupport_device_in". When I got this phone, it had indian rom (DA) le2127 and I bricked it once. However the mobile repair store managed to unbrick it and restore it to (ACB) and now I am trying to convert it to EU but i don't know how to fix the "unsupport_device_in". Maybe I should try #402's method?
I ended up reverting to the T-Mobile firmware because I had connectivity issues. Though I used Global instead of EU when I did it. You still did better than me, I couldn't get my phone into EDL mode
 

petchportgach

Member
Oct 10, 2022
9
2
Thailand
I ended up reverting to the T-Mobile firmware because I had connectivity issues. Though I used Global instead of EU when I did it. You still did better than me, I couldn't get my phone into EDL mode
I saw a thread that says after update to android 13 beta 2 (from global firmware) and then perform a factory reset, the connectivity issues are gone. https://forum.xda-developers.com/t/...onverted-to-global-le2125-oos-13-ob2.4512829/
I get to EDL via cmd(adb reboot edl), could not combo keys to EDL neither.
How do you revert it to T-Mobile firmware btw?
 

GuyInDogSuit

Senior Member
Jan 4, 2009
5,879
1,334
40
Sacramento, CA
Nintendo Switch
OnePlus 7T
I saw a thread that says after update to android 13 beta 2 (from global firmware) and then perform a factory reset, the connectivity issues are gone. https://forum.xda-developers.com/t/...onverted-to-global-le2125-oos-13-ob2.4512829/
I get to EDL via cmd(adb reboot edl), could not combo keys to EDL neither.
How do you revert it to T-Mobile firmware btw?

The MSM tools. Specifically the ones for T-Mobile. There's a few threads with links.
 

Helio0

Senior Member
May 2, 2019
60
5
OnePlus 8 Pro
Hi,

Yesterday I restored my phone from Custom Rom vía MSM, and I updated to OOS13. Now I'm trying to come back to OOS11 with the same MSM tool, but my PC doesn`t recognize the phone.

Maybe any OOS13 restrictive software or something? Has anyone tried to downgrade from OOS13 stable?
 

GuyInDogSuit

Senior Member
Jan 4, 2009
5,879
1,334
40
Sacramento, CA
Nintendo Switch
OnePlus 7T
I have tried the T-mobile 11.2.3.3, 11.2.6.6, EU, Global none of them work for me, they kept saying "unsupported_device_in". What If I convert mine to indian firmware first then OTA to global?

I don't think that is a good idea, maybe a last resort. You could try the method @TinkerNerd described in their post (#402) as you'd asked before. It could be that when the repair store unbricked it, the device is no longer shown as an LE2127? Just a guess. But if you have access to fastboot, there's still a lot you can try to fix things.
 

petchportgach

Member
Oct 10, 2022
9
2
Thailand
I don't think that is a good idea, maybe a last resort. You could try the method @TinkerNerd described in their post (#402) as you'd asked before. It could be that when the repair store unbricked it, the device is no longer shown as an LE2127? Just a guess. But if you have access to fastboot, there's still a lot you can try to fix things.
It had the "unsupported device in" issue even before I bricked it lol. But I don't know how did the store unbrick my phone. I had tried using MSM with the T-mobile 11.2.6.6 package (210707). I saw him using the same repo website with me and they did not work neither. I only know that he used MSM with 210707 but don't know which exact one he got from or anything else he did to make it work. My device was showing as 2127 indian rom until I OTA it to oos12.c60+ (maybe 63) when I got to oos12 the le2127 became 2125 not sure what the rom was(maybe AA global) then I got connectivity issues so I tried to revert to oos11 and then I bricked my phone. Now my device is 2127 with acb rom(T-mobile). Thank you for the advice.
 
  • Like
Reactions: GuyInDogSuit

GuyInDogSuit

Senior Member
Jan 4, 2009
5,879
1,334
40
Sacramento, CA
Nintendo Switch
OnePlus 7T
It had the "unsupported device in" issue even before I bricked it lol. But I don't know how did the store unbrick my phone. I had tried using MSM with the T-mobile 11.2.6.6 package (210707). I saw him using the same repo website with me and they did not work neither. I only know that he used MSM with 210707 but don't know which exact one he got from or anything else he did to make it work. My device was showing as 2127 indian rom until I OTA it to oos12.c60+ (maybe 63) when I got to oos12 the le2127 became 2125 not sure what the rom was(maybe AA global) then I got connectivity issues so I tried to revert to oos11 and then I bricked my phone. Now my device is 2127 with acb rom(T-mobile). Thank you for the advice.

Yeah, if you've got the T-Mobile FW on it, it should be showing as an LE2127. As far as the error goes, I have not heard of that before now. Sorry I can't be more help on this matter. I think the method above is likely to work, though. I might be able to answer questions on other matters. Good luck and I hope you figure it out.
 
  • Like
Reactions: petchportgach

Appreciative

Senior Member
Mar 6, 2015
215
122
It had the "unsupported device in" issue even before I bricked it lol. But I don't know how did the store unbrick my phone. I had tried using MSM with the T-mobile 11.2.6.6 package (210707). I saw him using the same repo website with me and they did not work neither. I only know that he used MSM with 210707 but don't know which exact one he got from or anything else he did to make it work. My device was showing as 2127 indian rom until I OTA it to oos12.c60+ (maybe 63) when I got to oos12 the le2127 became 2125 not sure what the rom was(maybe AA global) then I got connectivity issues so I tried to revert to oos11 and then I bricked my phone. Now my device is 2127 with acb rom(T-mobile). Thank you for the advice.
I believe this is because of the Indian variant (in/IN). There is a known issue when you flash IN (or have IN) firmware, it causes an issue for MSM tools. @EtherealRemnant made a thread and released a modified tool that may help you at least get back to a condition where you can use other MSM tools?

That thread is https://forum.xda-developers.com/t/...-for-indian-variant-flashing-as-well.4454357/

I have tagged him as he's still active and knows more about this than I do
 

EtherealRemnant

Senior Member
I believe this is because of the Indian variant (in/IN). There is a known issue when you flash IN (or have IN) firmware, it causes an issue for MSM tools. @EtherealRemnant made a thread and released a modified tool that may help you at least get back to a condition where you can use other MSM tools?

That thread is https://forum.xda-developers.com/t/...-for-indian-variant-flashing-as-well.4454357/

I have tagged him as he's still active and knows more about this than I do
Unfortunately my tool wouldn't work on a 9 Pro as it's made for the 9 and the T-Mobile 9 Pro is so finicky that I never even bothered trying to make a mod for it after all the headaches I had trying to make one for the regular 9 T-Mobile model. People need to just start shipping those POS devices back.
 
  • Like
Reactions: Appreciative

Appreciative

Senior Member
Mar 6, 2015
215
122
Unfortunately my tool wouldn't work on a 9 Pro as it's made for the 9 and the T-Mobile 9 Pro is so finicky that I never even bothered trying to make a mod for it after all the headaches I had trying to make one for the regular 9 T-Mobile model. People need to just start shipping those POS devices back.
Man that sucks. I haven't had any issues with my tmo 9 pro but that's partially thanks to guys like you who put up several warnings across the forum about not flashing any IN variant msms. It's really easy to make that mistake. And I guess having IN beats a brick but it sucks that it's so problematic for those who are on IN
 
Right, that will convert it to Global but now it was updated to a13 and works without the data retain module.
It says "System update installation failed" when I tried this method. To be specific, I first used the Oxygen Updater to download the full global OTA (by setting my phone to the global ver, despite it's currently flashed by MSM tool to EU ver). Then I used the system's local upgrade to install it, got the error msg above.
 

TheSayaMan

Senior Member
Sep 12, 2016
913
382
OnePlus 9 Pro
It says "System update installation failed" when I tried this method. To be specific, I first used the Oxygen Updater to download the full global OTA (by setting my phone to the global ver, despite it's currently flashed by MSM tool to EU ver). Then I used the system's local upgrade to install it, got the error msg above.
Do not use the built in system updater. You need to use Oxygen updater. Change your device in settings to the global version then install the next full version through the local update only. Also make sure you are on latest A11 before you try updating to a12 or it won't work. Once your on Global you can then use the automatic system update to update all the way to a13. You will need wifi to update from a12 to a13 because you won't have phone service.
 
  • Wow
Reactions: handydandy
For anyone having trouble with the MSM tool, there's another way to do this. The following steps assume you have adb and fastboot installed and your SIM and bootloader are unlocked.
1) Using the Oxygen Updater app, download the latest (full) global firmware, then copy the zip file to your adb/fastboot folder. Rename the zip file to firmware.zip
2) Download the TWRP recovery, rename the file to twrp.img and copy it to your adb/fastboot folder
3) Place your phone into fastboot mode
4) Using fastboot, boot the TWRP recovery image (fastboot boot twrp.img)
5) Once your phone has booted the TWRP image, select Advanced, then select ADB Sideload
6) Use ADB to sideload the downloaded firmware (adb sideload firmware.zip)

Remember to flash your NON-HLOS.bin onto your phone so you can get service

DISCLAIMER: This is just what worked for me after a fair bit of trial and error and experimentation. I only tried this because I couldn't get the MSM tool to work for me. If the MSM tool works for you, you should probably use that instead
This helped me. Those following this method, if your phone can upgrade to Android 13, you don't need to flash the T-mobile modem module - it's taken care of by the new ver.

Also, when you're sideloading the global rom, the progress in your CLI may stop at some point less than 100%, but says "no error". This is a known issue of the tool and means the sideloading IS successful.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    select EU target and you will be fine
  • 16
    *** Use this at your very own risk.
    *** You will lose all data
    *** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people).
    *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. If you just ran a bunch of unknown commands, I would tell you to MSM.
    *** Know how to use the MSMTool, Don't start before figuring it out. https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-glo-in.4272549/
    *** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH ANY STEP DESCRIBED IN THIS GUIDE


    General notes:
    • NR and LTE bands are read only and not modifiable, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
    • If you wish to unlock the bootloader without unlock_code.bin, you MUST do it from OOS11. If you upgrade to OOS12/OOS13, you will need the unlock_code.
    • The T-Mobile NON-HLOS is no longer necessary as of OOS13 release. If you must stay on OOS11 or OOS12, make a backup of the T-Mobile modem partition for the OOS version you want to stay on.
    • Dual-SIM does not work.

    Prerequisites:
    • This conversion will not SIM unlock you. You can only SIM unlock on a T-Mobile ROM, meaning if you want to do that in the future, you must go back to a TMO ROM (and wipe)
    • Familiarity with MSMDownload tools. If the regular MSM tool doesn't work for you, turn back now.
    • Back up all data, it will be wiped.

    Download:

    Steps:
    1. Run the MSM file normally.
    2. Unlock your bootloader if necessary. Now is the time if you don't have unlock.bin
    3. Patch up to Android 13 while on Wifi if your mobile data doesn't work. Use this time to go to another variant (GLO, IN, etc) as needed.

    Fastboot method:
    * The steps in this guide will convert your TMO LE2127 to EU 11.2.3.3. This is intentionally not the latest version to force you to take a FULL OTA.
    * You must already have the bootloader unlocked with an unlock_code.bin
    * You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. No support will be given if you choose to manually do it.
    * Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools. DO NOT USE MINIMAL ADB, it has not been updated for years.
    * Fastboot can't see your device? https://forum.xda-developers.com/t/...stboot-mode-windows-10.4194491/#post-84943553
    * Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
    * When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.

    Steps to convert your device to EU
    1. You need your device bootloader and SIM unlocked. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
    2. Download and unzip the conversion package:
      • EU 11.2.3.3
        MD5: cb949816fa80d5f0d984359b819426c3
    3. Boot to bootloader.
      • From adb:
        Code:
        adb reboot bootloader
      • From fastboot/bootloader:
        Code:
        fastboot reboot bootloader
    4. Execute "flash_all.bat" from the unzipped directory from step 2.
    5. Reboot into recovery, and wipe everything.
    6. Once fully booted, connect to WiFi and download Oxygen Updater and take the FULL OTA (11.2.4.4 as of this writing)
    7. Do a regular reboot, don't reboot to fastbootd, bootloader, recovery, etc. Reboot to system.
    8. Reboot into bootloader or fastbootd, and flash the T-Mobile modem.
      Code:
      fastboot flash modem NON-HLOS.bin
    9. After each Full OTA you take in the future, you will need to repeat step 7 & 8

    FAQ
    • Q: The most recent version is 11.2.4.4, why is this guide converting to 11.2.3.3?
      A: You didn't read the full post.
    • Q: Why is there no conversion to Global?
      A: Global variant uses the Google incremental OTA server, and full OTAs are not always provided. There's no functional difference, and EU has better privacy requirements anyways. You can do it manually by extracting payload.bin and running the same flash script. No support will be provided if you choose to flash to Global.
    • Q: Can I re-lock the bootloader after conversion?
      A: While you can go ahead lock your bootloader after conversion, I don't recommend it as you will not be able to take incremental OTA due to modem changes, and lose connectivity if you take a full OTA. To fix it, you need to unlock the bootloader and end up wiping.
    • Q: Where is the Linux guide?
      A: Too lazy, if you're using Linux, you can make your own bash script from the Windows batch script.
    • Q: Help, I see is 'fastboot' is not recognized as an internal or external command.
      A: Your fastboot.exe is not in your $PATH. You can either drop fastboot into the same folder as flash-all.bat, or you can fix your $PATH
    • Q: Help, I cannot boot to fastbootd because previous flashes messed things up.
      A: MSM
    • Q: Help, "not enough space to resize [system, product, system_ext]"
      A: MSM. If the error is on Vendor, it might still work and boot with a generic Android boot logo. If so, take the full OTA as described in the guide.
    • Q: Help, something went wrong!
      A: Post in here the starting state of your device (Device model, ROM version, etc), all steps you've taken since unlocking bootloader, and the output of whatever is causing you trouble. Chances are, the answer is MSM, but read my MSM warning.
    • Q: Help, I see "Invalid sparse file format at header magic"
      A: Ignore this message, not an error


    Fixing the About Phone page

    These steps are optional, and is only applicable for OOS11. It will fix the "About Phone" page. There are no performance differences. All that's done is change build.prop to reflect the correct model.
    1. You need to rooted with Magisk
    2. Download and install the magisk module: here
    3. Reboot, the About Phone page is filled out.


    Instructions to Bootloader Unlock a SIM locked device:

    1. In ADB:
      Code:
      adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
    2. Reboot
    3. Go to dev settings and enable OEM Unlock
    4. Reboot to bootloader
    5. Code:
      fastboot oem unlock
      No unlock.bin needed


    Issues so far (please post if you run into more):
    • If your mobile data doesn't work on OOS13, PM me details including HW Revision in About Phone.
    What appears to work:
    • Everything else.

    Much appreciation for everyone that help develop and test
    @razercortex
    @retryfail
    @amaroney55
    5
    Due to OnePlus's incompetence on running a website, the MSM conversion is released today to enable bootloader unlocking for folks who are SIM unlocked but can't download an unlock.bin
    3
    Link to the tg group I'm willing to help or find a fix for this also my Bluetooth will randomly disconnect then reconnect my Garmin watch. I did notice it disconnected my airpod before once but haven't had that happen yet just happens more often with my Garmin watch.
    If you don't have root or unlocked bootloader backup using MSM tool. When in the screen where you would normally flash the rom, press F8 key. You will see list of partition, password is oneplus to use backup.
    3
    Yes you need to do incrementals. F17 is the latest version and you can't go straight to that. Just use the EU to GLO MSM I posted above if you don't know how to use oxygen updater local uograde, that will put you on a11 GLO then you won't need oxygen updater, you can just do regular system updates to f.17 GLO.
    Thanks! That's what i did. By the way i used the system LE2123 to do updates until A12 and stopped. Dowloaded the One+ local update app for A12 and used the Zip Full LE2125 F17 from OxygenUpdater app. Now i am on A13 GLOBAL and doing OTA updates normally. Thanks for all your quick support, it was very important to me conquer the aim.
    2
    Thank you for all the help it helped me convert my first oneplus device Im glad I did it.