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

Search This thread

keesh_x

Senior Member
Mar 15, 2023
53
11
OnePlus 3T
OnePlus 7T
maybe restart the procedure from step 1
Tried the process altogether from step 1, did step 2 via unlock.bin file from oneplus.

Flashed european fastboot rom, initial steps succeeeded like before, but then it said rebooting to fastboot, it rebooted to recovery instead, from there i selected fastboot after that errors started popping up in the flash all script majorly, "flashing is not allowed for critical partiitions", "partition not found" and eventually device rebooted, but i dont have any cellular signals or wifi, sound etc. Kindly have a look at the attached screenshots, what exactly am i doing wrong, i really dont understand, please help
 

Attachments

  • error.png
    error.png
    92.7 KB · Views: 18
  • success.png
    success.png
    116.3 KB · Views: 19

arslanejaz33

Senior Member
Sep 14, 2013
71
22
Internet
Tried the process altogether from step 1, did step 2 via unlock.bin file from oneplus.

Flashed european fastboot rom, initial steps succeeeded like before, but then it said rebooting to fastboot, it rebooted to recovery instead, from there i selected fastboot after that errors started popping up in the flash all script majorly, "flashing is not allowed for critical partiitions", "partition not found" and eventually device rebooted, but i dont have any cellular signals or wifi, sound etc. Kindly have a look at the attached screenshots, what exactly am i doing wrong, i really dont understand, please help
Sorry for the late reply you should not do anything when it restarts again and the terminal says "waiting for device" the flashing process with resume automatically when it boots up again and goes to recovery mode
 

TechForEver

Senior Member
Sep 2, 2017
88
14
Unlocked bootloader, now Using the fastboot rom mentioned by OP, the european rom, but now i cant flash fastboot rom, after running flash_all.bat in fastboot mode, it did a few steps formatting etc then says on the cmd, rebooting to fastboot but it went to crash dump mode, am i doing something wrong?
You used Europe fastboot rom (which is in this thresd) to convert?
 

Mostafahemad

Member
Jun 29, 2019
25
1
I don't have T-Mobile sim and not in the US. How would I go about this?
You not need t.moblie sim neither to be in US
Oh my friggen god, so super duper incredibly happy! Thanks to OP and people on here I now not only have EVO X 7.5 with dual sim on my TMO OP8 but I unbricked what I thought was a hard bricked OP8.

For anyone who had the absolute misfortune of a crashdump due to misflashing the wrong .ops file, there's hope. I had that, the DIAG 900E only driver, alongside zero fastboot and recovery. It seemed hopeless, but being desperate and in lieu of the advice above and from other sites I kept trying and finally the following revived my phone:

1) I had to use a usb 2.0 port. It can be inbuilt or it can be from a hub but you really need usb 2.0.
2) I had to use a different cable than the one from oneplus. I ended up using the one used to charge my wireless headphones.
3) You should try windows 10 and above. Others may have had luck with windows 7 and native usb 2.0 but not in my case.

I had both the msm download and device manager open and ready. I kept the usb port in the system, then while holding down both volume buttons and power, quickly connected the usb C end into the phone. You can try without the power button but regardless you need to see 9008 pop up under ports in device manager. If the phone under device manager still remains as 900E then you have to start the process over again until it shows EDL (9008). If it shows bulk you need to reinstall your drivers.
On MSM immediately ENUM and Start.

If the above doesn't work, look for resources as if it showed issues only after msm there's still a good chance you can save it.
This is a reference for anyone unbrick his device as l want to write what happened to me but l found someone wrote his story like me
 

keesh_x

Senior Member
Mar 15, 2023
53
11
OnePlus 3T
OnePlus 7T
Sorry for the late reply you should not do anything when it restarts again and the terminal says "waiting for device" the flashing process with resume automatically when it boots up again and goes to recovery mode
thank you for your reply, i tried waiting for it for about a two minutes or more, it felt like it wasnt proceeding at all. should i wait more? kindly let me know if thats the case or whatever i am doing wrong, any help is appreciated
 
Last edited:

keesh_x

Senior Member
Mar 15, 2023
53
11
OnePlus 3T
OnePlus 7T
You used Europe fastboot rom (which is in this thresd) to convert?
Yes, i used the europe rom mentioned by OP in this thread, version was 10.5.9, yet still its not working, crash dump is not occuring now but when i run flash all, it does some flashing and says rebooting to fastboot and then never reboot to fastboot, it just reboots to stock recovery and stays there, and if i reboot to fastboot manually from there, flash all script starts giving errors, "flashing is not allowed for critical partition", I have literally no idea where i might be going wrong
 

Attachments

  • error.png
    error.png
    92.7 KB · Views: 2

TechForEver

Senior Member
Sep 2, 2017
88
14
Yes, i used the europe rom mentioned by OP in this thread, version was 10.5.9, yet still its not working, crash dump is not occuring now but when i run flash all, it does some flashing and says rebooting to fastboot and then never reboot to fastboot, it just reboots to stock recovery and stays there, and if i reboot to fastboot manually from there, flash all script starts giving errors, "flashing is not allowed for critical partition", I have literally no idea where i might be going wrong
Try one of these OnePlus fastboot roms
Must working
Unzip file and tun flash all bat

Some others faced like you dump error
but with one of these roms its working

 

Mostafahemad

Member
Jun 29, 2019
25
1
right, but i used the europe fastboot rom linked by OP, yet still it went to crashdump mode, any idea why?
Why you not follow the steps just confirmall drivers installed then start from step 1 with msm A10 not A11 then step two then use eu 10.5.9 fastboot rom not use eu 11 i as A11 always above 95% get crash dump
 

Mostafahemad

Member
Jun 29, 2019
25
1
Another thing during flashing eu fastboot rom when it reboot to fastboot , it reboot to fastbootd it looks like recovery but it not so not retains to fastboot manually as critical partitions flashes in fastbootd not in fastboot so start again with msm with A10
 
Last edited:

keesh_x

Senior Member
Mar 15, 2023
53
11
OnePlus 3T
OnePlus 7T
Why you not follow the steps just confirmall drivers installed then start from step 1 with msm A10 not A11 then step two then use eu 10.5.9 fastboot rom not use eu 11 i as A11 always above 95% get crash dump
i followed every step as mentioned. I have drivers installed and i am using msm 10 not 11, but with step two i couldnt unlock bootloader with the method mentioned so used unlock.bin from oneplus and used that to unlock bootloader but with step three, used eu 10.5.9 not 11, but i am not encounterring crashdump now, it probably went to crashdump because i updated my system a bit from wifi.
 

keesh_x

Senior Member
Mar 15, 2023
53
11
OnePlus 3T
OnePlus 7T
Sorry for the late reply you should not do anything when it restarts again and the terminal says "waiting for device" the flashing process with resume automatically when it boots up again and goes to recovery mode
tried again, even tried waiting for 10 minutes or so but nothing, until i manually go to fastboot mode myself and then it starts saying "flashing is not allowed for critical partition"

I read in another forum regarding the unlock_critical:
Code:
fastboot flashing unlock_critical
Running the above command gives "Device Already : Unlocked !"

As of right now i have tried a lot of possibilities, even used differnet roms, 10.5.12 global as well but every rom just after an inital flashing goes to fastbootd and never progresses afterwards
 
Last edited:

Mostafahemad

Member
Jun 29, 2019
25
1
tried again, even tried waiting for 10 minutes or so but nothing, until i manually go to fastboot mode myself and then it starts saying "flashing is not allowed for critical partition"

I read in another forum regarding the unlock_critical:
Code:
fastboot flashing unlock_critical
Running the above command gives "Device Already : Unlocked !"

As of right now i have tried a lot of possibilities, even used differnet roms, 10.5.12 global as well but every rom just after an inital flashing goes to fastbootd and never progresses afterwards
Simple step put the device in fastbootd and show if pc recognizes it or no ,then tell me
 
  • Like
Reactions: keesh_x

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    use nameless rom search on xda or google
    thanks, i tried it, and successfully installed. I never thought i can use custom rom on this phone. very nice custom rom.
    1
    I successfully converted 2 phone by this method but my 3rd phone is getting stucked in bootloop by this process ( it is unlocked at oem unlocking enabled) when I flash unlockops it starts to reboot to fastboot mode ( device is corrupted is not showing) when I run fastboot flashing unlock is say it is not allowed any solution or other way to unlock bootloader
    some phones do this you need their unlock token from oneplus
  • 23
    *** 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.
    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
    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:
    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.