[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!

Search This thread

Zure

Senior Member
Dec 11, 2011
63
14
after converting to EU. If i need to msm in the future would i use tmobile files cause my phone is orignally kb2007 or would i use EU msm files for KB2005?
 

craznazn

Senior Member
Nov 12, 2009
769
1
472
OnePlus 8T
Samsung Galaxy S22 Ultra
my 5g is horribly slow after converting, did I do something wrong
Doubt it. OOS11 or 12? Try going to Global instead of EU and see if it helps.
after converting to EU. If i need to msm in the future would i use tmobile files cause my phone is orignally kb2007 or would i use EU msm files for KB2005?
You can use tmo's MSM to go back to stock, or the conversion MSM to EU. From EU you can go to any other variant other than tmo.
 

JayTheKid

Senior Member
Jul 18, 2016
61
4
Doubt it. OOS11 or 12? Try going to Global instead of EU and see if it helps.

You can use tmo's MSM to go back to stock, or the conversion MSM to EU. From EU you can go to any other variant other than tmo.
Oos11 but after local upgrading to latest global it's working fine.

Also question, I installed your magisk module to fix the about phone but it's saying 2003 phone model. Anyway to change it to say 2005? I know it's trivial
 

craznazn

Senior Member
Nov 12, 2009
769
1
472
OnePlus 8T
Samsung Galaxy S22 Ultra
Oos11 but after local upgrading to latest global it's working fine.

Also question, I installed your magisk module to fix the about phone but it's saying 2003 phone model. Anyway to change it to say 2005? I know it's trivial
Open the zip file and modify system.prop to 2005.

Hi @craznazn I got my T-Mobile 8T today and tried to msm my edited ops from global and getting this error "unsupported target tmo" any idea what can be cause?
Not sure, check the target section towards the end of the xml but I can't really provide .ops modification support
 

The Fume

Member
Dec 30, 2019
42
8
i had the same issue and i couldnt mess with it to much due to work and needing the phone. i ended up going back with the msm tool then to global again

any advances getting dual sim back working on 12 yet? i was tempted to order a backup phone because i have to be able to get calls on the one i have and cant have it down to long.
 

robbin_banks

Member
Nov 3, 2012
5
0
I keep getting super img to super failed. Any idea why? Edit: NVM switched to usb 3.0 and worked perfectly. Got TMO to EU and upgrading to OOS 12 right now thanks so much for the guide
 
Last edited:

craznazn

Senior Member
Nov 12, 2009
769
1
472
OnePlus 8T
Samsung Galaxy S22 Ultra
i had the same issue and i couldnt mess with it to much due to work and needing the phone. i ended up going back with the msm tool then to global again

any advances getting dual sim back working on 12 yet? i was tempted to order a backup phone because i have to be able to get calls on the one i have and cant have it down to long.
only way to get dual sim on A12 is to use custom rom
 

jabe78

Senior Member
Nov 21, 2013
140
34
44
Poplar Bluff
OnePlus 8T
Hello @craznazn, thank you for your diligent work.

Ok. This may be a silly question, I have read thru the entire thread multiple times and cant really find a place that this is addressed. I am downloading the MSM tool linked in the OP and after 5 downloads, the MD5 still doesn't match what is listed. All 5 attempts match each other perfectly, but it is not what he has written it should be. Is this ok to use or what is my problem. I have used, Firefox, Chrome, and Edge browsers to download. Also, it downloads from Adroidfilehost; another question... Does anything for OnePlus 8T, work for the 8T+5G (KB2007)? I've had this device now for a couple months, and coming straight from Apple for the last 7 years, I haven't quite figured out the naming scheme of Oneplus yet or what is compatible with what when it comes to flashing.

Thanks in advance.
 

jcsww

Senior Member
Hello @craznazn, thank you for your diligent work.

Ok. This may be a silly question, I have read thru the entire thread multiple times and cant really find a place that this is addressed. I am downloading the MSM tool linked in the OP and after 5 downloads, the MD5 still doesn't match what is listed. All 5 attempts match each other perfectly, but it is not what he has written it should be. Is this ok to use or what is my problem. I have used, Firefox, Chrome, and Edge browsers to download. Also, it downloads from Adroidfilehost; another question... Does anything for OnePlus 8T, work for the 8T+5G (KB2007)? I've had this device now for a couple months, and coming straight from Apple for the last 7 years, I haven't quite figured out the naming scheme of Oneplus yet or what is compatible with what when it comes to flashing.

Thanks in advance.
It's the same device essentially. The only differences are the bands supported, which don't change when cross-flashing and that the KB2007 has dual-SIM disabled in the firmware but is enabled after flashing to a non-KB2007 firmware. The KB2007 only has a single IMEI, so when dual-SIM is enabled, both SIM's have the same IMEI.
 

jabe78

Senior Member
Nov 21, 2013
140
34
44
Poplar Bluff
OnePlus 8T
Well I don't really know what I'm doing wrong.

I have the 8t+5G (KB2007), Sim unlocked, OEM Toggled but no Token yet so Bootloader locked.

I have downloaded umpteen times, I've updated my Quallcom drivers and it is recognized instead of displayed as bulk in Device Managers. I have the latest ADB and Fastboot tools.

All I get when I run and start the MSM tool is Com3, and waiting for device indefinitely. It isn't connecting. Any advice or ideas as to why I can't connect? I'm missing something. I've read this and other threads over multiple time thoroughly.
 

jcsww

Senior Member
Well I don't really know what I'm doing wrong.

I have the 8t+5G (KB2007), Sim unlocked, OEM Toggled but no Token yet so Bootloader locked.

I have downloaded umpteen times, I've updated my Quallcom drivers and it is recognized instead of displayed as bulk in Device Managers. I have the latest ADB and Fastboot tools.

All I get when I run and start the MSM tool is Com3, and waiting for device indefinitely. It isn't connecting. Any advice or ideas as to why I can't connect? I'm missing something. I've read this and other threads over multiple time thoroughly.
Enable USB debugging in Developer Options and plug your device in to a USB port. Open the command prompt in Windows and type, adb shell and hit enter. Then type, ADB reboot edl, and press enter. You should already have the MSM Tool open and ready to start before running the adb command to reboot to edl mode.
 

jabe78

Senior Member
Nov 21, 2013
140
34
44
Poplar Bluff
OnePlus 8T
Enable USB debugging in Developer Options and plug your device in to a USB port. Open the command prompt in Windows and type, adb shell and hit enter. Then type, ADB reboot edl, and press enter. You should already have the MSM Tool open and ready to start before running the adb command to reboot to edl mode.
I'm sorry I didn't include those steps, but I have done those things also. My apologies.

What I mean is, I took those steps also, but I failed to include them in my question. Sorry for any confusion, I have followed everything I could find, and I'm still falling short somewhere.
 
Last edited:

The Fume

Member
Dec 30, 2019
42
8
leave oem lock on when using the msm tool you do not need to disable it. it caused me issues. start the msm toom leave it alone when it says com3. it should be waiting. now on the phone unlplug the usb cable. next on the phone hold volume up AND volume down keep holding them while you plug back in the phone. the msm tool should start going after that
 

jabe78

Senior Member
Nov 21, 2013
140
34
44
Poplar Bluff
OnePlus 8T
leave oem lock on when using the msm tool you do not need to disable it. it caused me issues. start the msm toom leave it alone when it says com3. it should be waiting. now on the phone unlplug the usb cable. next on the phone hold volume up AND volume down keep holding them while you plug back in the phone. the msm tool should start going after that
Thanks for the reply. Between that, and using my original cable, it finally worked. Thank You!
 

The Fume

Member
Dec 30, 2019
42
8
i went back to 11 after a few days of trying out 12. just to many small things i did not like. of course now my phone on 11 is telling me to upgrade. im hoping they do something about this color os thing i really did not like it very much
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Can someone please explain why my TMO>EU won't recognize a European sim? It's still Android 11, just like the guides say to. It recognizes my NA Sim on either slot, but never both.
    Also I don't get a second IMEI, for whatever reason.
    PS. I've tried the second SIM magisk module
    It seems to be simlocked, as converting TMO to EU doesn't remove simlock.
    1
    It seems to be simlocked, as converting TMO to EU doesn't remove simlock.
    To add to that. The SIM lock can only be removed using the T-Mobile firmware.
  • 22
    *** Use this at your very own risk.
    *** You will lose all data
    *** Backup your working modem and persist, just in case
    *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. Screenshots and MSM logs will be best.



    !!! I have officially retired my 8T, and can no longer provide additional support on this device !!!


    It's finally here! A MSM tool that will convert your T-Mobile OnePlus8T+5G to EU KB05BA. From here you can local upgrade to any OOS flavor you want. This gives you Local Upgrade option, faster upgrades, open betas, dual SIM, and more! In fact, after conversion, you can unlock the bootloader without the unlock token (still need to be SIM unlocked, but in case you don't want to wait for the unlock token or if OnePlus's website is broken)!

    If you are still SIM locked, you lose the Unlock app for when your device becomes unlocked, it's only available in the stock TMO ROM. If you want to go back to TMO ROM at any point, flash back with the TMO MSM: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/

    Steps:
    1. Download the MSM Conversion package:
      • AFH
        MD5: 5ddb543c8a5e7587e0b2ad24d2025e77
    2. Run MsmDownloadTool V4.0.exe (Windows 7 users may need to run the win7 version included)
    3. Select User type: "Other" and press Next.
    4. Press "Start". Don't mess with the default settings.
    5. Put your phone in EDL mode.
      Code:
      adb reboot edl
      or completely turn off your device, hold vol up + vol down and plug in the cable.
    6. Wait about 5 minutes while it works.
    7. Done! If you keep the bootloader locked and run it stock, the About Phone page will be missing some fields.
    If you run into any MSM tool issues, most likely you have a driver problem. See the FAQ in @Some_Random_Username's post


    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


    Old fastboot method

    *** Know how to use the MSMTool, Don't start before figuring it out.
    *** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH THE STEPS DESCRIBED IN THIS GUIDE

    * The steps in this guide will convert your TMO KB2007/KB05CB to Global 11.0.5.6.KB05AA, or EU 11.0.3.4.KB05BA
    * NR and LTE bands are flashed in nvRAM, 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.
    * Instructions are the same as running any other MSM unbrick tool.
    * You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. See manual instructions towards the end.
    * Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools, https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445. DO NOT USE MINIMAL ADB, it has not been updated for years and will cause a crash where you'll need to MSM back to stock.
    * Make sure your drivers are up to date. This guide will not walk you through setting up platform tools or updating drivers. When encountering fastboot issues, make sure to include the output of fastboot --version in your post.
    * Do not ask for OTAs, MSMs, or anything else not related to the steps described herein. There are plenty of threads around for those.
    * This guide does not pertain to Cyberpunk conversion. See other threads.
    * This guide converts you to an older firmware so you can take a FULL OTA via Oxygen Updater. Do not skip this step if you want a stable build.

    Steps to convert your device to Global or EU
    As simple as possible:
    1. You need your device bootloader and SIM unlocked. Follow the instructions here (It says 6T, but applies to all OP devices): https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-(t-mobile-edition)
    2. Download and unzip the conversion package:
    3. Boot to fastbootd.
      • From adb:
        Code:
        adb reboot fastboot
      • From fastboot/bootloader:
        Code:
        fastboot reboot fastboot
      • If you are having trouble booting into fastbootd, and have a FC number at the bottom of the bootloader screen, you'll need to MSM to factory first.
    4. [*]You should be at a screen that says "fastbootd" on top. DO NOT CONTINUE IF YOU ARE NOT HERE. SEE HIDDEN FOR AN EXAMPLE.
      bJDcOTg.jpg
    5. Execute "flash_all.bat" for Windows, or "flash_all.sh" for Linux, from the unzipped directory from step 2 as cwd.
    6. Optional: Flash magisk'd boot
      Code:
      fastboot flash boot boot_magisk_patched.img
    7. Reboot into recovery, and wipe everything.
    8. Once fully booted, download Oxygen Updater, set your device to OnePlus 8T of your regional choice and local upgrade to the latest OTA of your regional choice.
    9. Optional: You can re-lock your bootloader at thois point. DO NOT TRY before the full OTA upgrade above, or you'll have to MSM.

    Manually:

    1. Unlock bootloader
    2. Download the full OTA of your choosing
    3. Extract the OTA payload with https://github.com/vm03/payload_dumper or https://androidfilehost.com/?fid=818070582850510260
    4. With the output of the payload as your cwd, execute:
      Code:
      fastboot flash product product.img
      fastboot flash abl abl.img
      fastboot flash aop aop.img
      fastboot flash bluetooth bluetooth.img
      fastboot flash boot boot.img
      fastboot flash cmnlib cmnlib.img
      fastboot flash cmnlib64 cmnlib64.img
      fastboot flash devcfg devcfg.img
      fastboot flash dsp dsp.img
      fastboot flash dtbo dtbo.img
      fastboot flash featenabler featenabler.img
      fastboot flash hyp hyp.img
      fastboot flash imagefv imagefv.img
      fastboot flash keymaster keymaster.img
      fastboot flash logo logo.img
      fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
      fastboot flash modem modem.img
      fastboot flash multiimgoem multiimgoem.img
      fastboot flash odm odm.img
      fastboot flash qupfw qupfw.img
      fastboot flash recovery recovery.img
      fastboot flash spunvm spunvm.img
      fastboot flash storsec storsec.img
      fastboot flash system system.img
      fastboot flash system_ext system_ext.img
      fastboot flash tz tz.img
      fastboot flash uefisecapp uefisecapp.img
      fastboot --disable-verity flash vbmeta vbmeta.img
      fastboot --disable-verity flash vbmeta_system vbmeta_system.img
      fastboot flash vendor vendor.img
      fastboot flash xbl xbl.img
      fastboot flash xbl_config xbl_config.img
    5. Replace boot.img with your magisk'd boot if desired
    6. Reboot to recovery and wipe everything


    Troubleshooting

    • Error: "remote: no such file or directory"
      You are not in the correct cwd. Fastboot needs to be accessible from the same directory as the .img files, so fix your PATH or make a copy fastboot.exe in the same directory as the .img files
    • Error: "remote: Flashing is not allowed for Critical Partitions"
      You are not in fastbootd. Check step 4.
    • Error: "Invalid sparse file format at header magic"
      Ignore this message, not an error

    Special thanks to:
    @jwarrior319 for the initial linux script
    @cammykool and @awr128 for helping debug some of the steps and clarifying pain points

    @radiohead7778580 for a better Global conversion

    Fixing the About Phone page

    These steps are optional, and will fix the "About Phone" page. There are no performance differences.
    1. You need to rooted with Magisk
    2. Download the fix: here
    3. In the Modules page in MagiskManager, Install the downloaded zip file via "Install from storage"
    4. Reboot, the About Phone page is filled out.


    Issues so far (please post if you run into more):
    • In OOS11, "About phone" page does not work properly.
      • Use the magisk module above to fix it.
    • In OOS12, Dual SIM is not supported.
      • A11 based A12 ROMs support Dual SIM after conversion, use my enable_dsds module.
    • Unlocked bootloader without unlock_token must be done while in OOS11, as OOS12+ ABL will check that a token is needed
    6
    I'm glad that the global version is working for everybody!!! For my next trick I'll be trying to mod the MSM Tool for a straight conversation without the need to unlock, stay tuned. I'm going to be needing testers let me know if you're interested.
    5
    MSM conversion tool is uploaded.
    Guide updated, no more fastboot flashing needed!
    4
    Thank you for all the people willing to participate. I will keep everybody posted on my progress!!
    4
    You only get 1 IMEI but it's been working. I've been dailying dual SIM since conversion so long ago. However, I use Mint (T-Mobile MVNO) and T-Mobile postpaid, so that could explain why it works flawlessly.

    I just put in an ATT SIM card side-by-side with TMo and both works.