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

Search This thread

TDS.XDA

Member
Jun 2, 2012
17
5
Device not match image means your target ID differs from the target ID MSM that your using. If you already converted to EU then use the MSM I posted above to convert EU to Global. If you didn't convert yet, then you need to go back to page 1 and use the tmobile to EU converter listed there by the OP.
I used that TMO>EU from the 1st page and shows like i said: do not match. See the figure below. How could this possible?
 

Attachments

  • IMG_20221231_191612.jpg
    IMG_20221231_191612.jpg
    2.9 MB · Views: 68

TDS.XDA

Member
Jun 2, 2012
17
5
Just for the case: Bootloader already unlocked with Token from Oneplus. By now im on stock OOS12. Need Downgrade first? Backups Persist e Modem1st 2st done.
 

Attachments

  • Screenshot_2022-12-31-19-55-18-30.jpg
    Screenshot_2022-12-31-19-55-18-30.jpg
    271.9 KB · Views: 46

TheSayaMan

Senior Member
Sep 12, 2016
1,044
430
OnePlus 9 Pro
Just for the case: Bootloader already unlocked with Token from Oneplus. By now im on stock OOS12. Need Downgrade first? Backups Persist e Modem1st 2st done.
You don't need to have bootloader unlocked or rooted to use MSM. Did you try putting a check next to sha265 check? After MSM suceeds, your bootloader will be re-locked anyway. If that doesn't work, try not using litefirehose.
 
  • Like
Reactions: TDS.XDA

Appreciative

Senior Member
Mar 6, 2015
239
133
Just for the case: Bootloader already unlocked with Token from Oneplus. By now im on stock OOS12. Need Downgrade first? Backups Persist e Modem1st 2st done.
I saw this same thing somewhere on xda I'm pretty sure (or reddit if not). They claimed reinstalling adb and fastboot and qualcomm drivers, disabling driver signature and using a better cable worked for them.

It didn't sound possible that it would detect in edl mode fine but fail target ID with param preload and be a driver or cable issue but that's what they claimed, perhaps the driver signature disabling part. I don't remember the post or thread but if I find it, I will link to it. Until then, maybe try triple checking the driver situation and disabling driver signing.

When I did the Tmo->Eu flash using the msm tool from page one (I have le2127), I did not have to change any of the checkboxes and it went smooth.

I enabled developer mode on the phone and turned on usb debugging, plugged device in and accepted/allow mac on phone. Made sure adb and fastboot were working and recognizing my device in both.

I opened MSM, pressed F8, and backed up efs, modemst1/2, modem_a and persist partitions (password is oneplus), then I verified they were all written to C:\. I shut my phone down again, opened MSM tool again, held volume and plugged in phone to get to edl mode with MSM tool open and ready.

I pressed Enum (I don't think this is required) and it detected the device. Then pressed Start. Everything was done in a few mins and I was on oos11 EU.

The person who had the same issue and resolved it might be somewhere in this thread a few pages back but is your device detected fine in both adb and fastboot? Good quality usba->usbc data cable?
 

TDS.XDA

Member
Jun 2, 2012
17
5
Eu vi a mesma coisa em algum lugar no xda, tenho certeza (ou reddit, se não). Eles alegaram que a reinstalação dos drivers adb e fastboot e qualcomm, a desativação da assinatura do driver e o uso de um cabo melhor funcionaram para eles.

Não parecia possível que ele detectasse bem no modo edl, mas falhasse no ID de destino com o pré-carregamento de parâmetros e fosse um problema de driver ou cabo, mas foi o que eles alegaram, talvez a assinatura do driver desativando a parte. Não me lembro do post ou tópico, mas se eu encontrar, vou linkar para ele. Até então, talvez tente verificar três vezes a situação do driver e desabilitar a assinatura do driver.

Quando fiz o flash Tmo->Eu usando a ferramenta msm da página um (tenho le2127), não precisei alterar nenhuma das caixas de seleção e tudo correu bem.

Ativei o modo de desenvolvedor no telefone e ativei a depuração usb, conectei o dispositivo e aceitei / permiti o mac no telefone. Certifiquei-me de que adb e fastboot estavam funcionando e reconhecendo meu dispositivo em ambos.

Abri o MSM, pressionei F8 e fiz backup das partições efs, modemst1/2, modem_a e persist (a senha é oneplus), depois verifiquei que todas foram gravadas em C:\. Desliguei meu telefone novamente, abri a ferramenta MSM novamente, mantive o volume e conectei o telefone para entrar no modo edl com a ferramenta MSM aberta e pronta.

Pressionei Enum (acho que isso não é necessário) e ele detectou o dispositivo. Em seguida, pressionou Iniciar. Tudo foi feito em poucos minutos e eu estava no oos11 EU.

A pessoa que teve o mesmo problema e o resolveu pode estar em algum lugar neste tópico algumas páginas atrás, mas seu dispositivo foi detectado bem no adb e no fastboot? Cabo de dados usba->usbc de boa qualidade?
I will check everything e come back here with the results. THANKS A LOT
 

TDS.XDA

Member
Jun 2, 2012
17
5
You don't need to have bootloader unlocked or rooted to use MSM. Did you try putting a check next to sha265 check? After MSM suceeds, your bootloader will be re-locked anyway. If that doesn't work, try not using litefirehose.
Hi!!!
Thanks everyone! it works when i uncheck Lite Firehose and check Sha256. My phone now is OOS11 but LE2127 yet on settings. Can i ignore it? when i use the MSM EU>GLO by TheSayaMan i got MD5 Failed. I need to do a new download???
 

TDS.XDA

Member
Jun 2, 2012
17
5
It will put you on A11 EU then you can take local upgrade with oxygen updater to A11 Global. From there, you can use the built in system update to update to A12 where you will lose phone service. Just update to A13 with wifi and you will be good to go. Learn to READ!!!! I don't like repeating myself. This was mentioned above, I answered already.
When you say OXYGEN UPDATER you talking about the 3rd app, right? How can i use it securely to do that to A11 Global? It shows a LE2123_11_F.72 FULL update. Can i do this update? The MSM EU>GLO is getting error on MD5.
 

TheSayaMan

Senior Member
Sep 12, 2016
1,044
430
OnePlus 9 Pro
Hi!!!
Thanks everyone! it works when i uncheck Lite Firehose and check Sha256. My phone now is OOS11 but LE2127 yet on settings. Can i ignore it? when i use the MSM EU>GLO by TheSayaMan i got MD5 Failed. I need to do a new download???
Using my app, you need to uncheck sha265 check and check use lite firehose and it will only work if you converted to EU with the instructions in OP. The MSM I posted is converting EU to GLO. If your target is TMobile, it won't work. And it sounds like it is, if your model is reporting as LE2127
 
  • Like
Reactions: semdoc

TDS.XDA

Member
Jun 2, 2012
17
5
Using my app, you need to uncheck sha265 check and check use lite firehose and it will only work if you converted to EU with the instructions in OP. The MSM I posted is converting EU to GLO. If your target is TMobile, it won't work. And it sounds like it is, if your model is reporting as LE2127
Yes i did that conversion like you said to EU with MSM TMO>EU. At this point (OOS11 by MSM TMO>EU LE15BA) can I use oxygen updater app to go to full OTA GLOBAL LE2125 F.17 ROM (OOS13)? Local upgrade with that zip fails. Or not, I have to use the MSM EU>GLO first of all (look the error in attached file)? What I can do by now to upgrade to global OOS13?

It seems to be a LE2123 EU ROM (LE15BA) OTA 22.E.05_GLO VERSION on a LE2127 US DESCRIPTION.... reading the forum, a update to oos13 can fix that issue.
 

Attachments

  • Screenshot_20230104-100510.jpg
    Screenshot_20230104-100510.jpg
    481.3 KB · Views: 54
  • Screenshot_20230104-101513__01.jpg
    Screenshot_20230104-101513__01.jpg
    481.4 KB · Views: 55
Last edited:

TheSayaMan

Senior Member
Sep 12, 2016
1,044
430
OnePlus 9 Pro
Yes i did that conversion like you said to EU with MSM TMO>EU. At this point (OOS11 by MSM TMO>EU LE15BA) can I use oxygen updater app to go to full OTA GLOBAL LE2125 F.17 ROM (OOS13)? Local upgrade with that zip fails. Or not, I have to use the MSM EU>GLO first of all (look the error in attached file)? What I can do by now to upgrade to global OOS13?

It seems to be a LE2123 EU ROM (LE15BA) OTA 22.E.05_GLO VERSION on a LE2127 US DESCRIPTION.... reading the forum, a update to oos13 can fix that issue.
Your on EU now. You can use oxygen updater to go to GLO. If you use my MSM, It will put you on 11 GLO. So either option will work.
 

TDS.XDA

Member
Jun 2, 2012
17
5
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.
same problem, how to solve?
 

TDS.XDA

Member
Jun 2, 2012
17
5
You can't go from 11 straight to 13. You need to take the next update in the oxygen updater app
Ok but the the app shows the LE2125 F.17 ROM and this cause an error. This is the OOS13?. Can I do this incrementals by app or system? Because the incremental on app shows F.18, so this won't work. I've updating thought the system until A12. If the system shows the OOS13 UPDATE will I have to use de app to convert to GLOBAL? By now in the System My device shows LE2123 A12 unit so Can i use your MSM to convert to A11 GLOBAL even with the IMAGE MD5 CHECK ERROR (Verify button)?
 
Last edited:
  • Like
Reactions: faithhh

TheSayaMan

Senior Member
Sep 12, 2016
1,044
430
OnePlus 9 Pro
Ok but the the app shows the LE2125 F.17 ROM and this cause an error. This is the OOS13?. Can I do this incrementals by app or system? Because the incremental on app shows F.18, so this won't work. I've updating thought the system until A12. If the system shows the OOS13 UPDATE will I have to use de app to convert to GLOBAL? By now in the System My device shows LE2123 A12 unit so Can i use your MSM to convert to A11 GLOBAL even with the IMAGE MD5 CHECK ERROR (Verify button)?
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.
 

faithhh

Senior Member
Nov 2, 2010
217
27
istanbul
LE2125_11_F.18
Ok but the the app shows the LE2125 F.17 ROM and this cause an error. This is the OOS13?. Can I do this incrementals by app or system? Because the incremental on app shows F.18, so this won't work. I've updating thought the system until A12. If the system shows the OOS13 UPDATE will I have to use de app to convert to GLOBAL? By now in the System My device shows LE2123 A12 unit so Can i use your MSM to convert to A11 GLOBAL even with the IMAGE MD5 CHECK ERROR (Verify button)?
Same problem here... App show f18 and I can't see in local update.
 

faithhh

Senior Member
Nov 2, 2010
217
27
istanbul
This is the last message I'm sending. USE THE MSM I POSTED ABOVE TO CONVERT YOUR EU TO GLOBAL AND YOU WONT NEED OXYGEN UPDATER!!!!! SMH!!
Thank you for help. But I'm having a problem with edl mod. the phone switches to edl mode, but after 5-10 seconds, it exits edl mode and the system turns on again.that's why i try with the updater application.
 

TDS.XDA

Member
Jun 2, 2012
17
5
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.
 

TheSayaMan

Senior Member
Sep 12, 2016
1,044
430
OnePlus 9 Pro
Thank you for help. But I'm having a problem with edl mod. the phone switches to edl mode, but after 5-10 seconds, it exits edl mode and the system turns on again.that's why i try with the updater application.
If you need to use MSM in the future, press start on MSM before you enter edl mode. That will solve that problem. If your not hard bricked, that's what happens.
 
  • Like
Reactions: faithhh

faithhh

Senior Member
Nov 2, 2010
217
27
istanbul
This is the last message I'm sending. USE THE MSM I POSTED ABOVE TO CONVERT YOUR EU TO GLOBAL AND YOU WONT NEED OXYGEN UPDATER!!!!! SMH!!
for your msn uncheck sha256
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.
Did you install eu c17 and install global?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Can someone help a noob out here? lol

    I have a TMO im trying to move to global via EU like here:

    Bootloader is unlocked, got the TMO stuff all done.

    Now I am trying to use MSM and get the firmware etc changed. This is all new to me.


    Downloaded the msm tool and the files from the first post...

    Opening MSM under "other" and I am not getting the phone to be seen. just "n/a".
    usb debugged, drivers etc, running msm from same folder as adb... cmd gets me to see the device and it follows commands.

    Can someone spell out step by step what I need to do next. (like im 5 because apparently I cant follow adult directions).

    TIA for any help
    Make sure you have the Qualcomm QDLoader 9008 Driver installed. And set test signing to on - Google is your friend.
    1
    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 !
    1
    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
    1
    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.
    1
    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 ! You may be able to find the F.18 file somewhere and install it. Mine runs great on F.18 with no network issues. Here's a link to the fastboot rom F.18 https://androidfilehost.com/?fid=4279422670115718722
  • 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.