*** Use this at your very own risk.
- Local Upgrade
- About screen, if steps are followed above
Tweet the T-Mobile Help page, I was in your same situation with the customer service line until I tweeted the help page explaining that I was a developer and needed a sim unlock. Replies came within minutes and they were super helpful. I only needed to provide the IMEIthey wont budge since i dont have an account with them. im using an mvno
Ok once i make global and flasher zip via magisk to fix missing about but after relock BL and stock boot its back to missing again and 2nd thing now even after flash FB rom device stuck on 900E mode not booting why?
T-Mobile will only remove the SIM lock on a device for customers that meet their SIM Unlock Policy criteria. More than 40 days use on the network for postpaid and a year of refills for prepaid. You might want to look into a third party unlocking service. The device needs to be on the T-Mobile firmware to remove the SIM lock.Hi Team,
I just bought OP 8T from OnePlus directly 2 days back. I wanted to make it sim Unlock ( tried contacting T mobile and OP both attempts were unsuccessful). I came across this xda post. Spent several hours for the phone to get detected in EDL mode ( fixed drivers) flashed EU ROM successfully Was able to see Dual Sim. Tried putting Cricket mobile, not able to see any network. The main intention of the device is to use it in India, Any thoughts on how to proceed further.
Thanks
Hi thank you for the reply. I believe that policy is for devices bought from t mobile on contract? This device was bought in full from OP. I was parsing through the comments on this thread, audience reported it worked on at and T or any other GSM carrier. Is this because cricket is CDMA? Currently don't have another major GSM carrier to test out.T-Mobile will only remove the SIM lock on a device for customers that meet their SIM Unlock Policy criteria. More than 40 days use on the network for postpaid and a year of refills for prepaid. You might want to look into a third party unlocking service. The device needs to be on the T-Mobile firmware to remove the SIM lock.
The policy is for any T-Mobile device, whether paid in full at the time of purchase or paid monthly through EIP, purchased directly from T-Mobile, the manufacturer, or third party retailer, etc.Hi thank you for the reply. I believe that policy is for devices bought from t mobile on contract? This device was bought in full from OP. I was parsing through the comments on this thread, audience reported it worked on at and T or any other GSM carrier. Is this because cricket is CDMA? Currently don't have another major GSM carrier to test out.
Sir can you guide why on oneplus 8 tmobile variant dual sim doesn't work even after converting it to global variant even I have changed imei on second slot it detects sim but no signal.*** 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.
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:
If you run into any MSM tool issues, most likely you have a driver problem. See the FAQ in @Some_Random_Username's post
- Download the MSM Conversion package:
- AFH
MD5: 5ddb543c8a5e7587e0b2ad24d2025e77- Run MsmDownloadTool V4.0.exe (Windows 7 users may need to run the win7 version included)
- Select User type: "Other" and press Next.
- Press "Start". Don't mess with the default settings.
- Put your phone in EDL mode.
or completely turn off your device, hold vol up + vol down and plug in the cable.Code:adb reboot edl
- Wait about 5 minutes while it works.
- Done! If you keep the bootloader locked and run it stock, the About Phone page will be missing some fields.
Instructions to Bootloader Unlock a SIM locked device:
- In ADB:
Code:adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
- Reboot
- Go to dev settings and enable OEM Unlock
- Reboot to bootloader
No unlock.bin neededCode:fastboot oem unlock
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:
- 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)
- Download and unzip the conversion package:
- 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.
- [*]You should be at a screen that says "fastbootd" on top. DO NOT CONTINUE IF YOU ARE NOT HERE. SEE HIDDEN FOR AN EXAMPLE.
![]()
- Execute "flash_all.bat" for Windows, or "flash_all.sh" for Linux, from the unzipped directory from step 2 as cwd.
- Optional: Flash magisk'd boot
Code:fastboot flash boot boot_magisk_patched.img
- Reboot into recovery, and wipe everything.
- 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.
- 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:
- Unlock bootloader
- Download the full OTA of your choosing
- Extract the OTA payload with https://github.com/vm03/payload_dumper or https://androidfilehost.com/?fid=818070582850510260
- 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
- Replace boot.img with your magisk'd boot if desired
- 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.
- You need to rooted with Magisk
- Download the fix: here
- In the Modules page in MagiskManager, Install the downloaded zip file via "Install from storage"
- Reboot, the About Phone page is filled out.
Issues so far (please post if you run into more):
What appears to work:
- None
- 5G
- Dual SIM
- AOD
- Fingerprint sensor
- Wildvine L1
- Local Upgrade
- About screen, if steps are followed above
Hey, I responded to your comment a while ago. I found a different fix that allows bootloader unlock without a sim unlock. There is a tool that can ungrey OEM unlocking option. Go into system options, run the tool, open developer options, and enable OEM unlocking.they wont budge since i dont have an account with them. im using an mvno
You can do it via "adb shell pm uninstall --user 0 com.qualcomm.qti.uim" command.Hey, I responded to your comment a while ago. I found a different fix that allows bootloader unlock without a sim unlock. There is a tool that can ungrey OEM unlocking option. Go into system options, run the tool, open developer options, and enable OEM unlocking.
![]()
32.38 MB file on MEGA
mega.nz
Yeah I know. The tool does exactly that but has a couple other useful gadgets installed. Any idea if I could use this to unlock my Verizon pixel 2xl?You can do it via "adb shell pm uninstall --user 0 com.qualcomm.qti.uim" command.
No 3rd party tools needed.
Yeah, I would assume. I'm not really even looking to root it or anything because it's so old at this point. I've moved on to my OnePlus 6t, 8t, and 9 for my android modding.No, you are generally fk'd because you got a verizon device. There was an exploit for a verizon pixel (could've been for the 2), but it's not just an adb command.
It is. The instructions to convert to EU are in the OP. Once you are on the EU firmware, which is what I am personally using on T-Mobile USA. You can use a full image to update to the NA/Global, if you wish, through the Local Update option under System Updates.Excuse my ignorance... but, this is the best process to make the 8t T-mobile a global version right...?? It's just that I don't want to be left without a phone since I'm not an expert in this...!Thank you
This is one shady looking app lol, but at least the source seems legit enough. I did run it and it seems successful, going from OOS12 KB2005_11_C.16 to OOS11 11.0.11.11.KB05AA. It forced a wipe like other downgrade flashes, so be careful if you decide to use it.Thanks for the update !!!
Actually I am not worried about second sim at all I am not using that. Yes in OOS12 local upgrade is removed. like in ColorOS12, may I ask you try one more thing, sorry I am not in US and want to ask my brother get one TMO version for$349 that's why asking this much questions. Can you use this link to downgrader apk https://oxygenos.oneplus.net/English_20220225101104.apk
and downgrade to this KB2005 NA firmware https://oxygenos.oneplus.net/OnePlus8TOxygen_15.O.29_OTA_0290_all_2110091944_downgrade
If that will be successful than I will go ahead and ask brother to buy for me and send to my country, again I really appreciate your support and help. Thanks again !!!
Because US carriers force OnePlus to add bullshit and remove features. One of the features removed is the "local upgrade" option in software updates where you can specify your own OTA, so regular OTAs you end up taking must be the TMO firmware.Hi @craznazn I would ask you something regarding Oneplus 8T TMO version, is there any idea why it is not possible to clearly convert this model to other models? Why it is only possible via MSM but not other method? What is different with TMO firmware?
No, the MSM will take the manifest.xml in the .ops will check params on your device against it, and if the project or model tgt doesn't match, it will not work. The MSM executable itself doesn't actually change between the various models, just the .ops fileOk I agree with all that, but in this case quick question can I use MSM tool but replace msm firmware from EU to Global and flash it? or the file in your package has modified .ops file? Or in another words can use MSM tool for Global version but run it on TMO version phone?
Yes, the ops file is modified to allow the conversion. I have not tested OOS12 while I had the 8T, because I went to AOSP almost immediately after testing conversion and dual SIM.So the tmo eu conversion ops file has been modified correct, I mean the one that is in your zip file. Also did you tested after upgrading to OOS12 the about page still has that wrong model picture and info missing?
Open the zip file and modify system.prop to 2005.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
Not sure, check the target section towards the end of the xml but I can't really provide .ops modification supportHi @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?
adb reboot edl
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
fastboot oem unlock
adb reboot fastboot
fastboot reboot fastboot
fastboot flash boot boot_magisk_patched.img
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