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

Search This thread

Scholeggo

Senior Member
Sep 27, 2017
327
32
Hey guys. I have used this guide before on the op9 t-mo version. But I face 2 problems with using the convert tool to unlock the bootloader: any time i unlock the bootloader after converting, I ota and manually try to upgrade to 12, and either it fails to upgrade or, if I'm successful, I cannot boot the system. If I convert, keep my bootloader locked and ota to 12 then try to unlock, it will ask me for the code.

I traded my op9 to get a op8T+ (for unrelated reasons), and I'm gonna try to do this again because I want to flash a custom rom right away and not wait 1 to 2 weeks to get a code from the OnePlus site, and that rom requires that I'm on oos12 beforehand. Can somebody help me out so I know what to do when I get the 8T+ so I'll be on the rom immediately? I would very much appreciate it. Thanks.
 

jace90

New member
Feb 28, 2022
4
0
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
 

Rootk1t

Senior Member
Jun 2, 2013
1,817
763
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.
 

jace90

New member
Feb 28, 2022
4
0
It seems to be simlocked, as converting TMO to EU doesn't remove simlock.
I don't think that's problem, I'm not using a TMO Sim.
I originally used the sim unlock guide in the OP, but I have tried it again using the official wait a week token method. Nothing.
I have also tried using a friend's EU card and it's same
 

MevishL

Member
Sep 6, 2021
34
4
Samsung Galaxy S21
Screenshot_2022-11-15-11-03-04-08_fc704e6b13c4fb26bf5e411f75da84f2.jpg
can i convert to eu from this version? it ask for unlock token when i unlock my bootloader , so i want to convert
 

jcsww

Senior Member
View attachment 5761771can i convert to eu from this version? it ask for unlock token when i unlock my bootloader , so i want to convert
The EU version isn't currently available and is still in development. Once available, you can convert to the EU from the NA (Global) using Local Updater with the full update image to update as long as what you are updating to is newer than what you currently have on your device. If you have a KB2007, I would be interested to know if you have working dual-SIM enabled after updating.
 
The EU version isn't currently available and is still in development. Once available, you can convert to the EU from the NA (Global) using Local Updater with the full update image to update as long as what you are updating to is newer than what you currently have on your device. If you have a KB2007, I would be interested to know if you have working dual-SIM enabled after updating.
So far, the International and the Indian released version of OOS13 disables Dual SIM on T-Mobile/KB2007 devices, just like OOS12. This is from reports on Reddit.

I doubt the EU version will be different, as the OOS12 for EU disabled it.
 

Angelmendez056

New member
Nov 13, 2022
1
0

  1. ¡Agradable! Gracias. Entonces, aparte de que la información "Acerca del teléfono" no se muestra correctamente, ¿entiendo que todo lo demás parece estar funcionando? Mis disculpas si me perdí algo, leyendo esto desde el móvil en XDA Labs.

    Editar: tengo SIM desbloqueada y tengo mi token de desbloqueo del cargador de arranque, así que debería estar bien (simplemente no he desbloqueado mi cargador de arranque TODAVÍA). Creo que es posible que desee mencionar esos requisitos en el OP, con suerte para ayudar a evitar preguntas innecesarias. Parece obvio, pero ya sabes... es internet.

    Enviado desde mi OnePlus 8T usando XDA Labs
Cees que funcione en oneplus8T+5G kb2007 ?
 

kevinco1

Senior Member
Aug 28, 2013
467
162
Los Angeles
Project Treble
OnePlus 8T
So I've had a KB2007 for two years now and held off on doing this because I figured by the time OOS12 arrived there would be a similiar method in place and didn't want to do this twice. But...this hasn't happened so I'm looking to take the time this go through this process even if it downgrades me to OOS11.

The question is - can I still do this while I'm on OOS12, C.43? After reading extensively it seems I can by MSM but I'm confused on what exact version of MSM to currently use and the best way to go about it.

Have no problem doing a search, but it's confusing to me based on the current state of MSM and how it's now locked for regular users not to mention the exact RAM configuration for KB2007 to use. Thanks in advance
 

craznazn

Senior Member
Nov 12, 2009
770
1
472
OnePlus 8T
Samsung Galaxy S22 Ultra
Clarified that OOS11 is the only place where you can unlock bootloader without unlock_code.bin.

So I've had a KB2007 for two years now and held off on doing this because I figured by the time OOS12 arrived there would be a similiar method in place and didn't want to do this twice. But...this hasn't happened so I'm looking to take the time this go through this process even if it downgrades me to OOS11.

The question is - can I still do this while I'm on OOS12, C.43? After reading extensively it seems I can by MSM but I'm confused on what exact version of MSM to currently use and the best way to go about it.

Have no problem doing a search, but it's confusing to me based on the current state of MSM and how it's now locked for regular users not to mention the exact RAM configuration for KB2007 to use. Thanks in advance
You can run MSM from any version, it uses EDL and doesn't even boot into any part of regular boot chain. Only the 10Pro and 10T have the new OPPO EDL JIT encryption. Unfortunately, I can't answer your question regarding LPDDR4x vs LPDDR5, as mine was LPDDR4x. I hope someone can clarify that for you.
 

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.