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

Search This thread
yes the device manager port shows up as Android Bootloader device.

driver booster I'm unfamiliar with. I'll have to look that up when I get back.

I missed your previous post but the PC is updated.

At this point I'm having trouble even getting the cmd to see it, nevermind msm.
Android Bootloader device is not correct it needs to show Qualcomm QDLoader 9008 when phone is plugged in and you connect cable. Install the Qualcomm QDLoader 9008 driver. Now with phone powered off open Msmdownload tool hold down volume up volume down button on phone and plug usb cable in phone and phone will show connected in Msmdownload tool. If you follow those instructions to the T in the order I prescribed you will have success !
 
  • Like
Reactions: bigd2442

bigd2442

Senior Member
Oct 2, 2010
181
17
Thank you dude! 🙏🙏
Finally back on the road to getting this thing fixed!
20230316_170320.jpg
 

bigd2442

Senior Member
Oct 2, 2010
181
17
Rock on to get to Le2125 just follow the rest of my guide you can install stable F.16 or F.17 in place of OB2 update to F.18 and do a factory reset do not update to F.20 or you will have network issues.
I downloaded OB2.. will that not work?

Also it updated once and now keeps saying successful but keeps saying the next update is the same one.. le2525_11.F17_2170

So where do I go from here?

I still need the firmware flash or no?

Factory reset needed?
 
I downloaded OB2.. will that not work?

Also it updated once and now keeps saying successful but keeps saying the next update is the same one.. le2525_11.F17_2170

So where do I go from here?

I still need the firmware flash or no?

Factory reset needed?
No you can keep updating when you get to f.18 do a factory reset
 
  • Like
Reactions: bigd2442
odd that it keeps saying the same update is the new update though, no?

I'll keep going though. thank you for all the help!
Yes this is normal that is the eventual update that will be coming they don't give you the in-between updates just how they do it when there are so many.
 
  • Like
Reactions: bigd2442

bigd2442

Senior Member
Oct 2, 2010
181
17
Yes this is normal that is the eventual update that will be coming they don't give you the in-between updates just how they do it when there are so many.
got it. f.17 was the Android 13.
f.20 is the next one so I'm factory resetting now.

Will I need to go back through and unlock bootloader again?

planning to find a good custom ROM next.

Truly appreciate your help.

I haven't rooted or done adb since the original oneplus days! lol
 
got it. f.17 was the Android 13.
f.20 is the next one so I'm factory resetting now.

Will I need to go back through and unlock bootloader again?

planning to find a good custom ROM next.

Truly appreciate your help.

I haven't rooted or done adb since the original oneplus days! lol
NP I think you'll enjoy how OOS 13 F.18 runs, it is smooth as butter ! I leave mine stock I got tired of always playing with it it runs great the way it is. Enjoy !
 
  • Like
Reactions: bigd2442

bigd2442

Senior Member
Oct 2, 2010
181
17
Thanks so much.

My biggest issue wanting root/rom changes was to avoid the mandatory updates.

Looks like that won't be an issue anymore though even with F.18 right?

You're a wizard with this stuff man. outstanding work!
 
Wait. Are you saying that Global F.20 loses mobile data, just like EU F.74? WTF is going on with Oneplus?
The F.16 F.17 F.18 and F.20 are all updates for the Le2125 not the T-Mobile conversion the F.18 just so happens to run the best on it although after conversion the F.20 update should see Le2125 but it breaks the network again, so you got me ?
 

Maseleg

Member
Jun 10, 2014
5
1
I'm trying to convert my newly acquired LE2127 to EU (purchased from OPPO's official store on aliexpress.)
Basic setup has been done (SIM unlocked, USB debugging on, Developer Mode and OEM Unlocking is enabled) bootloader is still locked (waiting for code from oneplus as well.) It's still on OOS 11. Using wifi and no SIM is installed.

I've installed the Qualcomm drivers and am using this thread's version of the MSM tool. My win11 PC is in Test Mode to run the drivers too.

I open the MSM tool, see my COM devices (I've tried multiple USB ports,) hit start on the tool and it's stuck on "Waiting for device" even after I've tried booting it into edl, both via button combinations/replugging and via .\adb reboot edl. (Using latest platform-tools too)

After doing either method, my Device Manager shows RELINK HS-USB QDLoader 9008 for roughly 15 seconds before the phone reboots normally. After that, it shows as a LAHAINA MTP in the USB devices in Device Manager. The MSM tool makes no progress and is stuck on Waiting even after a decent amount of time.

I'm not sure if I'm missing something which is making my MSM not see my device too. Nothing is progressing at all.
 
Last edited:

ChrisFeiveel84

Senior Member
Jun 29, 2017
743
254
38
Germany
OnePlus 11
I'm trying to convert my newly acquired LE2127 to EU (purchased from OPPO's official store on aliexpress.)
Basic setup has been done (SIM unlocked, USB debugging on, Developer Mode and OEM Unlocking is enabled) bootloader is still locked (waiting for code from oneplus as well.) It's still on OOS 11. Using wifi and no SIM is installed.

I've installed the Qualcomm drivers and am using this thread's version of the MSM tool. My win11 PC is in Test Mode to run the drivers too.

I open the MSM tool, see my COM devices (I've tried multiple USB ports,) hit start on the tool and it's stuck on "Waiting for device" even after I've tried booting it into edl, both via button combinations/replugging and via .\adb reboot edl. (Using latest platform-tools too)

After doing either method, my Device Manager shows RELINK HS-USB QDLoader 9008 for roughly 15 seconds before the phone reboots normally. After that, it shows as a LAHAINA MTP in the USB devices in Device Manager. The MSM tool makes no progress and is stuck on Waiting even after a decent amount of time.

I'm not sure if I'm missing something which is making my MSM not see my device too. Nothing is progressing at all.
Worng edl Driver and all oneplus goes after 10-15 secend out from edl when you Not hold pressed vol+ and vol-
 
  • Like
Reactions: Maseleg

Maseleg

Member
Jun 10, 2014
5
1
Worng edl Driver and all oneplus goes after 10-15 secend out from edl when you Not hold pressed vol+ and vol-
Did you mean wrong Qualcomm drivers? onepluscommunityserver doesn't have the qualcomm drivers. I've downloaded ones from gsmusbdrivers and installed it with the ETHERNET-DHCP as I've found other threads saying to use that option on installation. (The other option didn't show my device at all in the MSM tool)
 

ChrisFeiveel84

Senior Member
Jun 29, 2017
743
254
38
Germany
OnePlus 11
Did you mean wrong Qualcomm drivers? onepluscommunityserver doesn't have the qualcomm drivers. I've downloaded ones from gsmusbdrivers and installed it with the ETHERNET-DHCP as I've found other threads saying to use that option on installation. (The other option didn't show my device at all in the MSM tool)
When you have the corekt driver installed (this you can i mean install over windows 11 Updates)
Than you see an devices manager an QHUSB_BULK 9008
 

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    *** 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.