[GUIDE] Complete Step-by-Step Convert T-Mobile to Global (or other) firmware

Search This thread

iMogul

Senior Member
Aug 27, 2007
102
17
Chicago
Sorry, I did not get any of the errors you both had. For me it shows as follows

fastboot flashing unlock
...
OKAY [ 0.038s]
finished. total time: 0.038s

The issue that I am having after Step 2 , the phone is not Dual SIM and model is IN2017. I have two working SIMs from T-mobile in the dual SIM Tray when I did all the steps. I will roll back and give it another shot.

Edit : Can someone please confirm after the second step , Dual SIM shows up without flashing Fastboot ROM and other OTA zips ?
 
Last edited:

iMogul

Senior Member
Aug 27, 2007
102
17
Chicago
I was able to get Dual SIM working after flashing Fastboot ROM and using the above zip in the local upgrade. Is this Global version?

I see the Model shows as IN2015 and the Build Number : Oxygen OS 11.0.9.9.IN21DA , Android version 11.

Is it possible to update to 12 or 13 without losing Dual SIM ? Thanks for your help.
 
Last edited:
I was able to get Dual SIM working after flashing Fastboot ROM and using the above zip in the local upgrade. Is this Global version?

I see the Model shows as IN2015 and the Build Number : Oxygen OS 11.0.9.9.IN21DA , Android version 11.

Is it possible to update to 12 or 13 without losing Dual SIM ? Thanks for your help.
if the model number shows IN2015 then ur good to go. Update to Oxygen OS12/13 or even ColorOS, dual sim will be working
 
  • Like
Reactions: keesh_x and iMogul
EDIT so you can ignore the rest: Somehow I manage to continue with the process, but I´m stuck on the Fastloader section. I´m on the screen with the big START button, but when I run the adb commnad (fastloader devices), no response.

I made sure to turn on OEM Unlocking before preceding, and now the "FAILED (remote: 'Flashing Unlock is not allowed (THW.)')
fastboot: error: Command failed" message appears. Also, "adb devices" doesn´t show anything, yet "fastboot devices" show one device.




Original Message: Hi! I stumbled upon this amazing post but I´m having issues, so I was wondering if anybody could help.

Little backstory of why I´m here: So, I bought my phone two years ago, IN2015 and was working fine until two weeks ago when the screen turned green and had it replaced. The new screen´s fingerprint wasn´t working, so I contacted the technician and said I had to factory reset the phone, so the new finger print could be recognized. Not sure of how true is that, but I went on ahead and did that. Last night he gave me the phone back, but as soon as I started checking it, I noticed it was now IN2017 (I´m not too faithful with whatever he did to my "phone", if it is still mine). When I tried to restore my phone´s backup, the system gave me the warning that the backup was made using a newer software than my current one (made with 13 and now I have 12). So, that´s basically the reason of my visit here. I want to restore my phone to Global (for better updates) and restore my settings.

Now the issues. So, since starting the post, some stuff are expected to be known by users (and yes, I get it, *this is not a common-guy-like-me sruff*). For example, turning on Test Mode, disabling device driver signing and that, was something I had to Google and modify several aspects of my PC to get it to work (if it is even working, as I read that in Test Mode, there is a huge watermark and I´m not seeing it).

Then, when starting the MSM Tool, no devices show up. I´ve selected Other, my phone is connected and has USB Debugging enabled, yet, nothing shows up.

I´m still at step 1 and already having lots of issues :( Is there a video tutorial using *this* guide I could refer to? Seemed straight enough, but guess I´m having a really hard time (also the stress factor of losing my stuff and/or bricking the phone).

Sorry, but if anyone could assist, I´d be thankful.
use cmd/powershell to boot to test mode and disable driver signing. Also double check device manager if the device connected is showing
 

iMogul

Senior Member
Aug 27, 2007
102
17
Chicago
Yes i am using 2 sim tray and its working in android 11 and i am using global rom... But when i take android 12 or 13 OTA it automatically becomes single sim again.. it shows only one imei
I am having the same issue now , when it did a self update all the way to Android 12 .. the Model changed from IN2015 to IN2011 and lost the dual SIM capability. The ROM I used after fastboot ROM must have been a Indian ROM. Will revert and try again.

Update : Finally got the Dual SIM working on Global ROM and updated all the way to Android 13. One thing I noticed is that the IMEI numbers are now same for both SIMs and it still works. Tried with two TMO SIMs and one TMO and one International SIM. I have no idea how this is possible, I thought the IMEIs need to be different for dual SIM to work.
 
Last edited:
  • Like
Reactions: thattechguy_69

iMogul

Senior Member
Aug 27, 2007
102
17
Chicago
The device shows up on Device Manager as Android Device. I have the Qualcomm Drivers and still nothing. Thanks for the reply, by the way.
You should see the device when you go to the EDL mode - follow this video as well as the description for the links to the required driver. To test it , open device manager on your pc and then put the OnePlus in EDL Mode. To go to EDL mode , turn the device off , press Vol Up and down button together, then plug in the USB cable.

You will see in the video below how it shows up .


I followed this guide to install Qualcomm drivers.

 
Mar 24, 2014
13
1
29
You should see the device when you go to the EDL mode - follow this video as well as the description for the links to the required driver. To test it , open device manager on your pc and then put the OnePlus in EDL Mode. To go to EDL mode , turn the device off , press Vol Up and down button together, then plug in the USB cable.

You will see in the video below how it shows up .


I followed this guide to install Qualcomm drivers.

unfurl="true"]https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
I'm currently away from my PC, but I'll try this.

However, my phone doesn't boot to anything except the screen with the green START button (and Reboot Bootlader, Recovery Mode, Show Barcode, Power Off). No matter what I try (be it "fastboot reboot edl"), it always boots to that green text. I've yet to see the video you posted (will watch it in a couple of minutes), so sorry if my doubt is answered there.

Thanks again for the reply. I'm not losing hope yet thanks to you.
 

hassaan786

Member
Feb 5, 2023
8
1
please help me my phone is locked in crash dump mode after flashing android 10 following first step after that my phone booted into crash dump mode and its not booting into fastboot mode and I cant turn on edl mode by force power off and then pressing volume up and down buttons simaltaneusly please help!!!!!!
 

hassaan786

Member
Feb 5, 2023
8
1
and I tried to install pixel experience after flashing fastboot rom and without locking bootloader but my phone doesnt boot into recovery mod then I tried booting into recovery using adb command then there is not any flashing option available I am tottally noob so sorry for that and I apperciate you for kindness ; (
 
and I tried to install pixel experience after flashing fastboot rom and without locking bootloader but my phone doesnt boot into recovery mod then I tried booting into recovery using adb command then there is not any flashing option available I am tottally noob so sorry for that and I apperciate you for kindness ; (
Ok is your phone working? What OS? And what are you planning to do with it?
 
Mar 24, 2014
13
1
29
You should see the device when you go to the EDL mode - follow this video as well as the description for the links to the required driver. To test it , open device manager on your pc and then put the OnePlus in EDL Mode. To go to EDL mode , turn the device off , press Vol Up and down button together, then plug in the USB cable.

You will see in the video below how it shows up .


I followed this guide to install Qualcomm drivers.

Thank you! This guide really unbricked my phone!

Now I have Android 10 again, and ready to continue. I have checked that OEM Unlocking is active and USB Debugging as well (since that appeared to be the issue). {Do I need to activate USB Debugging or only OEM Unlocking?} Any other thing to check before I try again?

Thanks again! I had lost hope, but now I'm here again.

EDIT: Are the next steps just for double SIM? If yes, can I just skip to Part 3?
 
Last edited:
Thank you! This guide really unbricked my phone!

Now I have Android 10 again, and ready to continue. I have checked that OEM Unlocking is active and USB Debugging as well (since that appeared to be the issue). {Do I need to activate USB Debugging or only OEM Unlocking?} Any other thing to check before I try again?

Thanks again! I had lost hope, but now I'm here again.

EDIT: Are the next steps just for double SIM? If yes, can I just skip to Part 3?
You have to do Part 3 as I believe T-Mobile ROM does not recognize Dual SIM
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    So going from In2017 to in2015, does that radio change as well? So it has the same CA combos and such as the in 2015? Or no matter what I do the T-Mobile radio is still flash and it's still in the end of T-Mobile device with T-Mobile bands?
    Bands will still same as T-Mobile because bands are saved in modern partition which is different than system partition which we convert.
    There's some ways to flash and edit midem files to get other bands
  • 30
    *** Use this at your very own risk.
    *** You will lose all data
    *** Backup your working modem and persist, just in case.
    *** USE USB 2.0 Port and Windows Machine



    !!! BEFORE YOU CONTINUE, POST #3 CONTAINS AN IMPORTANT MESSAGE SPECIFICALLY FOR THIS THREAD !!!





    Part 1: Return to T-Mobile Stock Firmware via MSM TOOL

    Turn on Test Mode, Disable Device Driver Signing via Powershell and set Time Date to 2017, then restart PC
    Code:
    bcdedit.exe /set nointegritychecks off
    bcdedit.exe /set testsigning off

    1. Launch MsmDownloadTool V4.0.exe.
    2. On the login prompt select "Other" in the dropdown menu and click on Next.
    3. Click on Target button and select TMO.
    4. Press Start button so that it waits for your device to be connected
    5. Power off your device
    6. Put your phone in EDL mode
    • by completely turning off your device, hold vol up + vol down and plug in the cable
    OR
    • via ADB command
    Code:
    adb reboot edl
    7. Once phone is in EDL Mode, immediately Click ENUM button and then START button

    Wait approximately ~250-300 seconds.
    Device will reboot afterwards.



    Part 2: Unlock Bootloader with no code and apply Dual SIM​

    After reboot, Turn on OEM Unlock in Developer Options before proceeding with the steps

    1. Rename and move “instantnoodlet_15_O.16_201001.ops” from MSM Tool directory to somewhere else (e.g., Documents Folder)
    2. Download "unlock.ops" and rename it to instantnoodlet_15_O.16_201001.ops
    3. Move the "renamed unlock.ops" to MSM Tool directory
    4. Launch MSM Tool and proceed using the steps from Part 1


    MSM Tool will finish flashing in under 15 seconds and the device will reboot with the message,
    "<!> The device is corrupt.."


    5. Unplug phone from PC and Force Shutdown device by simultaneously press and holding Power and Vol buttons till the device reboots
    6. Let go of all buttons once you see device reboot with the logo FASTBOOT MODE, the big START logo will appear afterwards
    7. Open SDK Platform Tools folder and launch Powershell/CMD from there
    8. Copy and paste this command to check if device is recognized in FASTBOOT
    Code:
    fastboot devices
    9. Once device isrecognized by terminal, copy and paste this other command
    Code:
    fastboot flashing unlock
    10. A confirm bootloader prompt will appear, use Vol buttons to hover on UNLOCK THE BOOTLOADER and to confirm, simply press Power button

    Once confirmed, device will reboot back to T-Mobile Firmware but now with Dual SIM and an unlocked bootloader. To use the MSM Tool again without the "unlock.ops", move the unlock.ops to a different place and put back the original ops.



    Part 3: Converting to other regions (e.g., Global, EU, Indian) and lock Bootloader​

    *** Cannot lock bootloader after flashing Fastboot ROM. Will corrupt device

    *** As of right now, Dual SIM doesn't work on OOS12/13 Indian Firmware

    1. Download this Fastboot ROM
    2. Open Fastboot ROM Folder, click flash-all.bat and type and enter "y" to the terminal
    Code:
    Do you want to wipe all the data ( Reccomended )[Y/N]?y
    < waiting for any device >

    3. Reboot phone to FASTBOOT MODE and plug the phone back to the PC
    4. Once the process is done, find an OTA ZIP from this thread to update to and download it

    (You can use ota.zips from any region whether it be EU/India/Global, e.g., OxygenOS 11 Global 11.0.11.11)
    Screenshot (10).png


    5. put the OTA ZIP in the phone, update it and reboot
    Manually-Install-OxygenOS-OnePlus-8-Pro-02.jpg

    Install-OnePlus-6-6T-OxygenOS-10-Update-using-Local-Upgrade-02.jpg


    After rebooting, you can either lock bootloader or stay unlocked to root

    6. To lock bootloader, reboot to FASTBOOT and plug phone in to PC
    7. Open platforms-tool and open a terminal from the folder
    8. Copy, paste and enter this command:
    Code:
    fastboot flashing lock

    9. Confirm the prompt LOCK THE BOOTLOADER and the phone will perform a factory reset and reboot.

    There you go! What you can do at this point is stay and daily drive OxygenOS 11 or update to OxygenOS 12/13 or even ColorOS. Dual SIM will work on any Firmware Region. The phone's model will also permanently change to IN2015=OnePlus 8 Global Version Model unless you go back and use MSM Tool again with the original ops.
    11
    I tried again, MSM to 10.5.7, unlocked bootloader, rebooted to bootloader, flash-all.bat, and I'm still getting errors on the critical partitions. And I can't figure out how to unlock the critical partitions (probably not allowed in TMo firmware).

    I'm going to MSM to 10.5.22 and see if that makes any difference.

    EDIT: No dice. 10.5.22 made no difference. The issue is the locked critical partitions. If anybody has any solutions please tag me.
    Sorry for spamming the board today, but I think I figured it out.

    Thanks to @thattechguy_69 for all the work here so far. This is just to help anybody who is having issues like I did.

    The "critical partitions" issue appears to be a DRIVERS issue, not a fastboot version issue or anything else with the actual phone or ROM files. I had installed all of the drivers that every guide said to install, but I stumbled upon this post by @FoxyDrew that solved my issue.

    Here's how I finally got into 10.5.12.IN21AA (Global ROM) on my IN2017:

    1. Just to be safe (not sure if it's necessary) boot into TEST MODE on your Windows machine. I did all of this from Test Mode.
    2. Download the files from the zip attached at the bottom of the first post on this thread. Install both files (OnePlus USB Drivers and QDLoader HS-USB Driver).
    3. At some point I THOUGHT I installed the Fastboot drivers, but maybe I messed that part up or maybe it was before I was in Test Mode. Regardless, download the Google fastboot driver zip in this post. Unzip it to your desktop.
    4. Open the extracted folder and then the usb_driver folder inside, then right-click on the android_winusb.inf file and select Install. Confirm the installation.
    5. Plug in your phone.
    6. Open Device Manager. Your phone should show up under "Universal Serial Bus controllers" as "IN2017" when it is in CHARGING ONLY mode, and under Portable Devices when in File Transfer mode or PNP mode. If not, you'll need to fix your USB drivers from step 2 above.
    7. Make sure you can get adb commands to work, then reboot to the bootloader ("adb reboot bootloader" should get you to the FastBoot Mode menu with the big green "START" banner at the top) and make sure fastboot commands also work ("fastboot devices" will show you if your phone is detected properly).
    8. Check Device Manager again while in bootloader mode - your phone should now show up under "Android Phone" as "Android Bootloader Interface." If it shows up as IN2017 with an exclamation mark, you need to fix the issues with the fastboot driver in step 4 above. I actually did this step while at the "waiting for device" message while flashing the Global ROM and it kick-started the installation's second phase.
    9. I also followed some steps from this post by @awsan - I copied the entire platform-tools folder that I downloaded from his post (r31.0.2) into the 10.5.12-GLOBAL folder, replacing all duplicate files. I don't think booting into fastboot like he says to do (language selection splash screen) worked, I had to boot into the bootloader from there to get the flash-all.bat to start.
    10. From here, I think I just double-clicked the flash-all.bat and everything worked properly - with the note that I was stuck at "waiting for device" after the first reboot command in the middle of the installation. The process in step 4 got me through this.
    This fixed my issues with not being able to flash critical partitions (because I suspect they re-lock when fastbootd switches into bootloader if you manually do it). Now it doesn't hang at all. I am going to play around with this to make sure I didn't miss anything and see if it works with other TMo firmware versions and the newer 11.0 Global ROM.

    I have not tried locking the bootloader yet.

    Oh, and 5G and VoLTE both appear to be working.
    6
    Dear OnePlus 8 community,

    This is my last time visiting y'all. Thank you for all the support and help you guys have gave me throughout the past year. You guys were the first community that I was a part of. I have now retired my OnePlus 8. This device is what entered me into the realm of XDA in the first place. This place will always be a part of my heart and I will cherish the memories I have experienced with it. This guide will be a step-by-step summary of all the guides scattered in the OnePlus 8 Guides Section. A reminder to the next OnePlus 8 users, don't let this community die and keep the old OnePlus Never Settle spirit, alive!

    Sincerely, Aaron
    22 November 2022​

    Credits to these amazing people for making this possible:
    4
    I managed to successfully convert my OP8 to the global version this morning.

    Here are a few things I can confirm:

    - 5G and VoLTE are working on my device (Rogers network in Canada)
    - Banking apps work as expected
    - Widevine certification is exactly as it was prior (L1), meaning I can stream in full HD/HDR with Netflix
    - I was able to OTA update to the latest 11.0.10.10 without any issues at all

    My first attempt trying this was a month ago. I was lazy and didn't roll the phone all the way back to Android 10 using the MSM tool. So I tried using "flash-all" with a newer global package and it did not work (crashdump error). Figured it was worth a shot... for whatever reason it just doesn't work. Ended up restoring with the MSM tool.

    This time, I did this:
    1. Reverted back to official T-Mobile Android 10 using the MSM tool
    2. Unlocked my bootloader using the all-in-one tool + my unlock token
    3. Used the all-in-one tool to flash the global fastboot ROM (Android 10) linked in the original post
    4. Manually flashed the EU update from the device (also linked in original post)
    5. Locked the bootloader using the all-in-one tool
    6. Used the Oxygen Updater app to download the latest global full release (11.0.9.9) and installed it from my device
    7. Performed an OTA update, bringing me to 11.0.10.10
    Sorry for the long post. I thought it might help someone else out since I modified a few steps from the original post and found success with this approach.
    3
    Thanks for the guide!! I just submitted my request to T-Mobile to unlock my boot loader so now I play the waiting game... 😴
    In the meantime, can someone please clarify what does converting from IN2017 to International achieve? Ultimately my goal is to flash a custom ROM - not sure if I can do this directly after unlocking my boot loader.
    IN2017 is Tmobile version of the phone and updates are late and you cant sideload an update because it is not available on carrier versions of the phone. Converting it to International version gives access to the latest updates, and some other features that weren't available to Tmobile version. If you do this method, you will lose Safetynet which is the ability to use bank apps and etc. So after converting you have to lock the bootloader if you wish to do anything related to banking.