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

Search This thread

bilalbls

Member
Mar 13, 2015
15
1
Friends dual sim is working in OOS 13 beta 1. I have installed it directly on OOS 11 with local update. And OOS13 beta 1 us very stable and smooth. I have not found any bugs yet.
 

raven911

Senior Member
Aug 17, 2009
62
1
Friends dual sim is working in OOS 13 beta 1. I have installed it directly on OOS 11 with local update. And OOS13 beta 1 us very stable and smooth. I have not found any bugs yet.
Has anyone who converted T-mobile to Global Rom, upgraded to OOS 13 Stable (F.13) had any issues? I'm running the EU rom, and was recently given the option to upgrade. With OOS12, I lost the ability do dual-sim...and seems like OOS13 also disables dual-sim, but just wondering if there are any other bugs to be aware of or anything else that might make it not good to upgrade?

On reddit there have been some folks saying that their contactless NFC payment stopped working (with google pay), but then another post said this was only an issue for people who use multiple user profiles on their 8T?
 
Last edited:

element51

New member
Dec 14, 2022
1
0
Upgraded to OOS12 this morning.. everything seems to be working fine, but colors seem to be washed out, especially with the new Monet color palette. Has anyone found a solution to getting the colors back to the vibrancy OOS11?

Also, big thanks to all that wrote the guides to convert the T-Mobile KB2007 to EU firmware. It solved many bugs for me.
 

superpotion

New member
Dec 21, 2022
1
2
Hey, I had a heck of a time trying to get all the proper drivers installed to get the MSMDownloadTool to work on a fresh install of Windows 10. Hopefully this helps someone else with a similar issue.
——
T-Mobile to EU XDA thread:
https://forum.xda-developers.com/t/...m-unlock-or-bootloader-unlock-needed.4188491/
(We are here)

MSMDownloadTool:
https://www.androidfilehost dot com/?fid=2188818919693805454
——
PRE-REQUISITES
Install ADB/fastboot tools (if you don’t have already):
XDA user fawazahmed0 - “Latest ADB Installer”

Install OnePlus drivers properly:
1. !!! REBOOT windows into unsigned drivers mode !!!

2. XDA user Mbektic - “fix device not showing up in fastboot mode” guide
https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/ (skip to Step 3)
2a. OnePlus drivers:
oneplususbdrivers dot com/latest (8T download page points here)

3. Make sure “unsigned” or “unverified” windows popup appears when installing, select “allow”

4. After installing OP drivers properly, move onto actually converting.
——
QUSB or QHUSB:
1. Connect phone to computer
2. In CMD, type “adb reboot edl” > Enter

3. IF YOU SEE QUSB or QHUSB instead of “Qualcomm 9008” WHEN CONNECTED:
XDA user gamingdoggo’s compressed .cab file (9/7/21 - #1246)
https://forum.xda-developers.com/t/...r-unlock-needed.4188491/page-63#post-85594511

3a. Download .zip file + extract to somewhere findable, windows + x > device manager
3b. Right click QUSB/QHUSB > properties > update driver > browse my computer for drivers > browse > go to where you extracted > select fe24…259d folder > should say “installed Qualcomm 9008 drivers”
3c. Restart computer

4. Connect phone to computer (if not already)
5. adb devices > make sure phone shows up like “XYZ362 Device”

6. Open MSMDownloadTool
7. In CMD, type “adb reboot edl”
8. Switch to MSMDownloadTool
9. COMX Device > Click Start (X will be a number)
10. Wait for progress bar to start moving (took me ~2-3 minutes)
11. Will boot to initial setup screen

To unlock bootloader:
1. Skip through setup (we will be factory resetting)
2. Enable developer options, enable USB Debugging
3. Make sure phone is connected to computer with ADB enabled (“adb devices” to check)
4. adb reboot bootloader

5. Windows + x > device manager
devices? (Someone please take a screenshot of this part, I forget what Windows exactly says) > Android
6. Update driver > browse my computer for drivers > browse > OnePlus Android Bootloader interface (i believe from OnePlus USB Drivers (c:\Program Files x86\OnePlus USB Drivers\OnePlus_android_winusb.inf) > 7. Install

8. adb > fastboot oem device-info (to verify BL lock status)
9. fastboot oem unlock > Enter
10. Volume key > volume down to highlight “YES” > power button to confirm
 

mattwheat

Senior Member
Oct 25, 2012
1,175
590
BIRMINGHAM
Has anyone who converted T-mobile to Global Rom, upgraded to OOS 13 Stable (F.13) had any issues? I'm running the EU rom, and was recently given the option to upgrade. With OOS12, I lost the ability do dual-sim...and seems like OOS13 also disables dual-sim, but just wondering if there are any other bugs to be aware of or anything else that might make it not good to upgrade?

On reddit there have been some folks saying that their contactless NFC payment stopped working (with google pay), but then another post said this was only an issue for people who use multiple user profiles on their 8T?
I had an original KB2007 TMobile version. I used this to flash it to LB2005. I had no issues. I flashed back when I was on Android 12. I took the over the air update for the KB2005 Android 13 and had no issues. I will say that I did have an issue taking the updates when I had TWRP installed. But once I flashed the stock recovery back to it the updates went through just fine. Now my phone shows that it is a KB2005. On the latest Android 13 OS.
 

Lost Dog

Senior Member
Can someone who went from T-moble KB2007 to global or EU test USB-C video? The T-Mo version lost the ability for many people after the update to Android 12. I have a monitor with USB-C input and it works fine with my Samsung phone but not my KB2007 (and reading online, this is a common occurrence).

I'm thinking of going to the EU version but would like to have both the US 5G bands as well as USB-C video out.
 

jcsww

Senior Member
Can someone who went from T-moble KB2007 to global or EU test USB-C video? The T-Mo version lost the ability for many people after the update to Android 12. I have a monitor with USB-C input and it works fine with my Samsung phone but not my KB2007 (and reading online, this is a common occurrence).

I'm thinking of going to the EU version but would like to have both the US 5G bands as well as USB-C video out.
Flashing does not change the available bands for the device. Your Kb2007 will have the same bands it came with regardless of the firmware you flash.
 

jcsww

Senior Member
I thought in the past there were issues with no longer getting T-Mo 5G after a flash to global or EU. Maybe I was mistaken! If that's the case, I don't see any downside to going to EU.
I have tried them all and my KB2007 is still running the KB2001 beta 1 for India so I have dual-SIM. 5G has worked fine on every firmware I have used for T-Mobile.

Flashing via the MSM Tool doesn't touch the modem firmware.
 
  • Like
Reactions: Lz3807775t

ianruto

Member
May 3, 2016
42
3
LG V35
I have just unlocked my bootloader using this method. I need Magisk, so i need the boot image however i dont know the exact version to download from the repo. Kindly advise
1675586072692.png
 

gdfajkldfkwfj

Senior Member
Sep 28, 2008
98
9
KB2007 on LOS 20, conversion went fine
but reboot after first OTA (OOS 11.0.13.13.KB05BA) I got "system update failed"

I went ahead with the next OTA (KB2003_11_C.33) and did not have any problem
 
Last edited:

fitrockx

Senior Member
Jul 31, 2013
50
16
Can someone who went from T-moble KB2007 to global or EU test USB-C video? The T-Mo version lost the ability for many people after the update to Android 12. I have a monitor with USB-C input and it works fine with my Samsung phone but not my KB2007 (and reading online, this is a common occurrence).

I'm thinking of going to the EU version but would like to have both the US 5G bands as well as USB-C video out.
Did someone tested the video output to an external display? Going through the same issue after updating to A12 T-mobile version.

Update:
I have tested it. Doesn't work. Only works on Oxygen OS 11. Once you go up, you'll loose it. I ended up rolling back to OOS11 after testing OOS 13.
 
Last edited:

Top Liked Posts

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