Convert T-Mobile to International (with Bootloader Re-LOCK)

Search This thread

blair.sadewitz

Senior Member
Dec 24, 2014
246
53
First I need to make sure the update works. The Global rom comes directly from the OnePlus website for the 8. The video I linked most likely will not work with US branded phones. With an unlocked bootloader, you cannot receive updates from Android updates. I am going the fastboot route when I get my unlocked token.

My question is can I simply flash the global rom via fastboot straight across via Android SDK platform tools without reverting to an Android 10 rom.

The Android 11 Global rom is newer than the latest T-Mobile Android 11 rom.
You most certainly can receive updates in the usual way. It won't do incremental updates, but it will download the full ones instead.

No, you can't just flash the global ROM outright, I don't think. Most of them will end up in crashdump mode. I recommend starting with 10.5.7 T-Mobile and then flashing 10.5.7 global with fastboot. After that, take all the updates the system offers you. After it's up-to-date, relock the bootloader if you wish.
 

Two Sheets

Member
Jan 11, 2022
36
7
You most certainly can receive updates in the usual way. It won't do incremental updates, but it will download the full ones instead.

No, you can't just flash the global ROM outright, I don't think. Most of them will end up in crashdump mode. I recommend starting with 10.5.7 T-Mobile and then flashing 10.5.7 global with fastboot. After that, take all the updates the system offers you. After it's up-to-date, relock the bootloader if you wish.
Ok, so the youtube video I posted should be possible for people who do not want to risk bricking their phone. If the bootloader is unlocked, sim is unlocked. Then the Global Rom should load without issue. The global rom on the oneplus website is newer than the latest T-mobile rom.
 

jasonring

Member
Mar 23, 2011
15
0
Can someone help me to verify if global firmware can connect to t-mobile 5g SA network?

To verify that, dial *#*#4636 #*#* in dialer and navigate Testing > Phone Information >

Look for these 2 fields, if it connect to 5g SA, it should show NR_SA. Thanks.

1. Data Network Type:
2. Voice Network Type:
 
Can someone help me to verify if global firmware can connect to t-mobile 5g SA network?

To verify that, dial *#*#4636 #*#* in dialer and navigate Testing > Phone Information >

Look for these 2 fields, if it connect to 5g SA, it should show NR_SA. Thanks.

1. Data Network Type:
2. Voice Network Type:
from @emowing
- No TMobile NR SA (5G Standalone)
- TMobile NR NSA works fine
 

dlhxr

Senior Member
May 26, 2011
544
508
New York City
OnePlus One
OnePlus 3
Tried here to change IMEI for sim 1 and sim 2 by Miracle, but dual sim still doesn't work. card 2 can be recognized, but can't search for networks. There may be some other triggers, but not duplicate IMEI causing the issue. Just a FYI for who's trying to work on it as well.
 

PavelPerm

Senior Member
Dec 19, 2011
301
30
Tried here to change IMEI for sim 1 and sim 2 by Miracle, but dual sim still doesn't work. card 2 can be recognized, but can't search for networks. There may be some other triggers, but not duplicate IMEI causing the issue. Just a FYI for who's trying to work on it as well.
I also came to this conclusion, the problem is not 1 IMEI For two SIM cards, the problem is something else.
 

Two Sheets

Member
Jan 11, 2022
36
7
I rolled my OnePlus 8 back to Android 10 and it relocked the bootloader. The problem, when I go into cmd prompt and unlock my bootloader. It says

target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.010s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.005s]
finished. total time: 0.017s

The problem is the fastboot menu still says "device state locked". I enabled OEM unlock and the debugging tool. My Sim is permanently unlocked. I did everything right.

I fixed it "fastboot oem unlock" I thought I could unlock the bootloader without needing to wipe the phone again.

I have a who cares attitude with this OnePlus 8. I have already bricked it once.



Edit: I bricked it 2x now. There is a problem with the OP flashing method. It starts fine with the global rom. flash all.bat works but it hangs with waiting for device. I am thinking that 7 zip could be a problem. I unlocked the bootloader, enabled OEM unlock and debugging. 2x failure with waiting for device message after about a minute. The 2nd attempt I let it sit for 30 minutes, no progress.

Is there another method to get the Global rom on the One Plus 8? The MSM tool is great once you figure it out. Works every time without any issues.
 
Last edited:

dlhxr

Senior Member
May 26, 2011
544
508
New York City
OnePlus One
OnePlus 3
I rolled my OnePlus 8 back to Android 10 and it relocked the bootloader. The problem, when I go into cmd prompt and unlock my bootloader. It says

target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.010s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.005s]
finished. total time: 0.017s

The problem is the fastboot menu still says "device state locked". I enabled OEM unlock and the debugging tool. My Sim is permanently unlocked. I did everything right. What is going on here?

Hello myself, I fixed it "fastboot oem unlock" I thought I could unlock the bootloader without needing to wipe the phone again.

I have a who cares attitude with this OnePlus 8. I have already bricked it once.



Edit: I bricked it 2x now. There is a problem with the OP flashing method. It starts fine with the global rom. flash all.bat works but it hangs with waiting for device. I am thinking that 7 zip could be a problem. I unlocked the bootloader, enabled OEM unlock and debugging. 2x failure with waiting for device message after about a minute. The 2nd attempt I let it sit for 30 minutes, no progress.

Is there another method to get the Global rom on the One Plus 8? The MSM tool is great once you figure it out. Works every time without any issues.
After flashing your unlock bin, type fastboot oem unlock or fastboot oem unlock-critical
 

Two Sheets

Member
Jan 11, 2022
36
7
How do I turn on test mode on my phone? How do I turn off Driver signature?

1st Step: (Make sure Test Mode is ON and Driver Signature is OFF)
First install the Drivers of the phone and the Qualcomm Drivers inside the attached file after downloading it at the bottom of this guide.
 

blair.sadewitz

Senior Member
Dec 24, 2014
246
53
Can someone help me to verify if global firmware can connect to t-mobile 5g SA network?

To verify that, dial *#*#4636 #*#* in dialer and navigate Testing > Phone Information >

Look for these 2 fields, if it connect to 5g SA, it should show NR_SA. Thanks.

1. Data Network Type:
2. Voice Network Type:
It can. I am connected to it.
 

blair.sadewitz

Senior Member
Dec 24, 2014
246
53
After flashing your unlock bin, type fastboot oem unlock or fastboot oem unlock-critic

I rolled my OnePlus 8 back to Android 10 and it relocked the bootloader. The problem, when I go into cmd prompt and unlock my bootloader. It says

target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.010s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.005s]
finished. total time: 0.017s

The problem is the fastboot menu still says "device state locked". I enabled OEM unlock and the debugging tool. My Sim is permanently unlocked. I did everything right.

I fixed it "fastboot oem unlock" I thought I could unlock the bootloader without needing to wipe the phone again.

I have a who cares attitude with this OnePlus 8. I have already bricked it once.



Edit: I bricked it 2x now. There is a problem with the OP flashing method. It starts fine with the global rom. flash all.bat works but it hangs with waiting for device. I am thinking that 7 zip could be a problem. I unlocked the bootloader, enabled OEM unlock and debugging. 2x failure with waiting for device message after about a minute. The 2nd attempt I let it sit for 30 minutes, no progress.

Is there another method to get the Global rom on the One Plus 8? The MSM tool is great once you figure it out. Works every time without any issues.
Use msmdownloadtool to revert to 10.5.7 T-Mobile ROM. Unlock the bootloader, then put it in fastboot mode and flash the 10.5.7 global ROM. Next, boot it and take at least one update. After you've verified that update boots, you can relock the bootloader. That's all there is to it.

This is a VERY SIMPLE process. The original instructions make it seem like it's more complex than it is because of the way the post is structured. It is not incorrect; it just jumps around a lot, etc. I have a feeling people are getting tripped up by this.

I have never tried using msmdownloadtool with the global firmware, as I assumed that it wouldn't work. After all, why would people be doing this in the first place if it did? ;-) I'm tempted to try it now, haha.

7zip is not the problem. Are you flashing it on a windows box? Which fastboot executable are you using? When does it hang with "waiting for device", when you first try to flash, or after the flash script reboots to fastbootd?

To me, this seems like a problem with fastboot on your machine. I need more information (like which OS you are using) to say anything else. Again, I must emphasize: this is EXTRAORDINARILY SIMPLE. Don't overthink it.

If you have access to another machine, try that, also.

At some point, I am going to try to roll my own firmware package for qfil and/or the qdl (see GitHub) tool to do this in one step because people keep having issues. I could be wrong, but I don't think there is any reason why one should even have to use fastboot at all to do this. The issue is getting the tool to just flash the @#$ global image.
 
  • Like
Reactions: dlhxr

Two Sheets

Member
Jan 11, 2022
36
7
Use msmdownloadtool to revert to 10.5.7 T-Mobile ROM. Unlock the bootloader, then put it in fastboot mode and flash the 10.5.7 global ROM. Next, boot it and take at least one update. After you've verified that update boots, you can relock the bootloader. That's all there is to it.

This is a VERY SIMPLE process. The original instructions make it seem like it's more complex than it is because of the way the post is structured. It is not incorrect; it just jumps around a lot, etc. I have a feeling people are getting tripped up by this.

I have never tried using msmdownloadtool with the global firmware, as I assumed that it wouldn't work. After all, why would people be doing this in the first place if it did? ;-) I'm tempted to try it now, haha.

7zip is not the problem. Are you flashing it on a windows box? Which fastboot executable are you using? When does it hang with "waiting for device", when you first try to flash, or after the flash script reboots to fastbootd?

To me, this seems like a problem with fastboot on your machine. I need more information (like which OS you are using) to say anything else. Again, I must emphasize: this is EXTRAORDINARILY SIMPLE. Don't overthink it.

If you have access to another machine, try that, also.

At some point, I am going to try to roll my own firmware package for qfil and/or the qdl (see GitHub) tool to do this in one step because people keep having issues. I could be wrong, but I don't think there is any reason why one should even have to use fastboot at all to do this. The issue is getting the tool to just flash the @#$ global image.
Agree with most of what you are saying. I have a handful of machines that I could use. I have followed every step in the process. On 10.5.7 T-mobile stock rom. Here is what it says when I flash the global rom.

Do you want to wipe all the data ( Reccomended )[Y/N]?y

Erasing 'userdata' OKAY [ 0.275s]



F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)



Info: Disable heap-based policy

Info: Debug level = 1

Info: Trim is disabled

Info: Set conf for android

Info: Segments per section = 1

Info: Sections per zone = 1

Info: sector size = 512

Info: total sectors = 210903704 (102980 MB)

Info: zone aligned segment0 blkaddr: 512

Info: add quota type = 0 => 4

Info: add quota type = 1 => 5

[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000

[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000

[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c000 0 200 at offset 0x00114688

[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c601, 0001c602

[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114689

[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c603, 0001c604

[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114690

[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00

[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001c600

Info: Overprovision ratio = 0.620%

Info: Overprovision segments = 645 (GC reserved = 330)

[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200

[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201

[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202

[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203

[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204

[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205

[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe

[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400

[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405

[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000

Info: format successful

Sending 'userdata' (85 KB) OKAY [ 0.009s]

Writing 'userdata' OKAY [ 0.002s]

Erasing 'metadata' OKAY [ 0.001s]

Erase successful, but not automatically formatting.

File system type raw not supported.

Finished. Total time: 6.233s

Sending 'boot_a' (98304 KB) OKAY [ 2.271s]

Writing 'boot_a' OKAY [ 0.413s]

Finished. Total time: 2.780s

Sending 'dtbo' (8192 KB) OKAY [ 0.191s]

Writing 'dtbo' OKAY [ 0.043s]

Finished. Total time: 0.253s

Sending 'modem_a' (524288 KB) OKAY [ 12.122s]

Writing 'modem_a' OKAY [ 1.955s]

Finished. Total time: 14.523s

Sending 'recovery' (102400 KB) OKAY [ 2.361s]

Writing 'recovery' OKAY [ 0.392s]

Finished. Total time: 2.857s

Sending 'vbmeta' (8 KB) OKAY [ 0.008s]

Writing 'vbmeta' OKAY [ 0.001s]

Finished. Total time: 0.021s

Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]

Writing 'vbmeta_system' OKAY [ 0.001s]

Finished. Total time: 0.023s

Rebooting into fastboot OKAY [ 0.002s]

< waiting for any device >
 

blair.sadewitz

Senior Member
Dec 24, 2014
246
53
I just wish that someone would actually make a proper modded msm tool for everyone thats on tmobile to convert to global without any issues of losing sim functionality or wait 7 days for the unlock code. Makes everyone's life easier and the fact that OP8T already has one which means that it is possible to make one and that we just need that person to help us. BE THE SAVIOUR!
What exactly are the issues trying to use the global msm package? What do you mean by "lose SIM functionality"? I'm not some expert, so I can't think of a reason why that would happen (that doesn't mean much because I don't know much haha).

The tools we should be using to do this, I think, are either qfil or the open-source "qdl" tool you can find on GitHub (the user is 'bkerler" or something like that). Msmdownloadtool is hella lame.
 

blair.sadewitz

Senior Member
Dec 24, 2014
246
53
Agree with most of what you are saying. I have a handful of machines that I could use. I have followed every step in the process. On 10.5.7 T-mobile stock rom. Here is what it says when I flash the global rom.

Do you want to wipe all the data ( Reccomended )[Y/N]?y

Erasing 'userdata' OKAY [ 0.275s]



F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)



Info: Disable heap-based policy

Info: Debug level = 1

Info: Trim is disabled

Info: Set conf for android

Info: Segments per section = 1

Info: Sections per zone = 1

Info: sector size = 512

Info: total sectors = 210903704 (102980 MB)

Info: zone aligned segment0 blkaddr: 512

Info: add quota type = 0 => 4

Info: add quota type = 1 => 5

[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000

[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000

[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c000 0 200 at offset 0x00114688

[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c601, 0001c602

[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114689

[f2fs_write_default_quota:1223] Writing quota data, at offset 0001c603, 0001c604

[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c000 0 200 at offset 0x00114690

[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00

[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001c600

Info: Overprovision ratio = 0.620%

Info: Overprovision segments = 645 (GC reserved = 330)

[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200

[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201

[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202

[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203

[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204

[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205

[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe

[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400

[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405

[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000

Info: format successful

Sending 'userdata' (85 KB) OKAY [ 0.009s]

Writing 'userdata' OKAY [ 0.002s]

Erasing 'metadata' OKAY [ 0.001s]

Erase successful, but not automatically formatting.

File system type raw not supported.

Finished. Total time: 6.233s

Sending 'boot_a' (98304 KB) OKAY [ 2.271s]

Writing 'boot_a' OKAY [ 0.413s]

Finished. Total time: 2.780s

Sending 'dtbo' (8192 KB) OKAY [ 0.191s]

Writing 'dtbo' OKAY [ 0.043s]

Finished. Total time: 0.253s

Sending 'modem_a' (524288 KB) OKAY [ 12.122s]

Writing 'modem_a' OKAY [ 1.955s]

Finished. Total time: 14.523s

Sending 'recovery' (102400 KB) OKAY [ 2.361s]

Writing 'recovery' OKAY [ 0.392s]

Finished. Total time: 2.857s

Sending 'vbmeta' (8 KB) OKAY [ 0.008s]

Writing 'vbmeta' OKAY [ 0.001s]

Finished. Total time: 0.021s

Sending 'vbmeta_system' (4 KB) OKAY [ 0.010s]

Writing 'vbmeta_system' OKAY [ 0.001s]

Finished. Total time: 0.023s

Rebooting into fastboot OKAY [ 0.002s]

< waiting for any device >
Try this:

Open up the flash-all.bat or whatever it's called in a text editor. Split the file into two different ones: the first one will have the commands at the beginning (you can strip out the wipe and the other flow control stuff in the batch file, we just want to flash, keep it simple) up until the line "fastboot reboot fastboot". Remove that line. The second file should have all the fastboot commands that happen AFTER that one. Now, try running the first one. After it is done, type "fastboot reboot fastboot" yourself. Does it go into fastbootd mode? If not, reboot the phone to the bootloader again, then try "fastboot reboot fastboot" again. If that is not working, it might be some issue with the fastboot version you are using or something (?). Anyway, once you get it into fastbootd mode by hook or by crook, then run the second script to flash the rest of the partitions. If you have problems still, try unplugging the phone and plugging it back in again, rebooting it to fastboot again, etc. Screw around with it.
 

blair.sadewitz

Senior Member
Dec 24, 2014
246
53
from @emowing
- No TMobile NR SA (5G Standalone)
- TMobile NR NSA works fine

Check it out. I think this qcn thing might be what we should be backing up.
 

Two Sheets

Member
Jan 11, 2022
36
7
Try this:

Open up the flash-all.bat or whatever it's called in a text editor. Split the file into two different ones: the first one will have the commands at the beginning (you can strip out the wipe and the other flow control stuff in the batch file, we just want to flash, keep it simple) up until the line "fastboot reboot fastboot". Remove that line. The second file should have all the fastboot commands that happen AFTER that one. Now, try running the first one. After it is done, type "fastboot reboot fastboot" yourself. Does it go into fastbootd mode? If not, reboot the phone to the bootloader again, then try "fastboot reboot fastboot" again. If that is not working, it might be some issue with the fastboot version you are using or something (?). Anyway, once you get it into fastbootd mode by hook or by crook, then run the second script to flash the rest of the partitions. If you have problems still, try unplugging the phone and plugging it back in again, rebooting it to fastboot again, etc. Screw around with it.
I have no issues with the MSMTOOL, bricking my device and unbricking it. The video on page one, he gets into fastboot mode using the menu on his phone. There is another guy on youtube who gets into fastboot by using a fastboot bootloader in the command prompt. I use the volume up and down buttons plus the power button to get into fastboot mode.

I hear your suggestion on the flash all bin file. I am going to try a different machine, different unzip tool and different USB ports and cables.

I was assuming there is no right or wrong way to get the phone in fastboot mode. Is this assumption true?
 

dlhxr

Senior Member
May 26, 2011
544
508
New York City
OnePlus One
OnePlus 3

Check it out. I think this qcn thing might be what we should be backing up.
yes, you should backup these things. But it tried this method to change IMEI, but it's not working. Only a tool called Miracle helped. But never mind, IMEI is not the trigger for dual sim
 
  • Like
Reactions: ac2br

zulisjutt

Member
Nov 19, 2020
6
0
i have also converted my tmo to global changed the imei but second sim signal not showing dose any one know the solution
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Just an update on the OOS 12... I ended up rolling back using the rollback app and OOS 11 zip provided by Oneplus...

    OOS 12 lost the ability to output from USBC to HDMI/DVI and I was unable to use it with a monitor at work. Probably not a feature that many uses, but for me it was a big deal. The only issue was what I mentioned earlier with using it with visible as a carrier. Looks like even if you got it connected, restarting the phone will lose the carrier again and you had to switch sim card in order to get the signal back which is a pain if your phone restarted unexpectedly while you're out.

    Hope this is useful for others...
    2
    unless you are having issues with the phone, i dont think you need to reset it. C.16 seems to be super stable with respect to battery life and performance. I see only minor bugs like Processor name showing incorrectly (865 reported as 855), battery % not showing in status bar on swipe down etc.
    In short, you should be fine without a factory reset
    I couldn't help myself. I factory reset the phone. It works better after the factory reset. Android 11 didn't run all that well on the OnePlus 8. It drained the battery much faster than Android 10. I am happy to have Android 12 on it now.
    1
    so far so good. mine has stayed on the latest A10 without forcing update to 11. it still annoys me with notifications though even though i tried to block them. so far working very smooth,
    1
    I have oxygen updater but I dont see IN2017 as a supported device. It suggests to me IN2015 update. Any thoughts?
    yeah use IN2015 since IN2017 is basically just IN2015 but locked on TMOBILE
    1
    Do you do the incremental updates or the full update. Oxygen Updater suggests doing incremental updates but what did you do?
    Full, incremental is only for a handful of people. If you do incremental, you must be on beta of oxygen os i believe. I switched to oos 12 incremental using oos 11 beta
  • 11
    The required files will be attached in the end of this guide.
    OnePlus 8 TMobile to Global Fastboot ROM
    MSM TOOL for IN2017

    Alternatives from the files above, if you get errors every time you are trying to flash like "NO SIM INSTALLED"
    (THIS IS WHAT I PERSONALLY USE):
    MSM TOOL for IN2017 Alternative
    OnePlus 8 Fastboot ROM Alternative

    1st Step: (Make sure Test Mode is ON and Driver Signature is OFF)
    First install the Drivers of the phone and the Qualcomm Drivers inside the DRIVERS.zip attached to this thread.

    2nd Step: Make sure your OnePlus 8 IN2017's bootloader is unlocked- unlocking bootloader will result to factory resetting your phone. Please backup your phone before doing this process. Instructions on how to unlock

    3rd Step: After the bootloader is unlocked, you have to enable "USB Debugging" and reboot your device to Fastboot Mode.

    4th and Last Step: Unzip the ZIP file and Open the Global Rom (10.5.12 OnePlus 8 Global Rom). Find flash-all.bat and double click on it. Type and enter Y when it asks to and just let it do its Terminal Process.

    **After the batch file is done, your phone should automatically boot to Global Rom Oxygen OS and no more of that T-Mobile
    splash screen.

    This is a YouTube walkthrough video on how to do it: Credits to Fizzy Apps on YouTube


    DO NOT LOCK YOUR BOOTLOADER YET, TO LOCK BOOTLOADER (THIS WILL WIPE EVERYTHING):
    -Download the latest OxygenOS 11 ROM
    -Move the downloaded ROM from "Downloads" folder to "Internal Storage"
    -Go to settings and find System Update, then press Local Update and choose the downloaded ROM
    -After its done installing, click REBOOT/Restart the device
    -After rebooting, go into FASTBOOT MODE and when you are in FASTBOOT MODE, type "fastboot oem lock"
    -Press the volume buttons to select LOCK BOOTLOADER and there you go, LOCKED Bootloader!

    IF SOMEHOW YOU GOT "QUALCOMM CrashDump Mode" during the 4th step or you locked Bootloader right after flashing ROM and it got corrupted.

    1) Enable Test Mode and Disable Driver Signature Verification on Windows PC.

    2) On your phone, simultaneously press and hold Volume Up (+) and Power Button and when the screen shuts down, IMMEDIATELY release both buttons. This means you forced shutdown the device.

    3) Set year date on your PC to 2017 and Turn off WIFI for MSM Tool to work and after doing this, open MSM TOOL folder you downloaded at the top of this guide and click MsmDownloadTool V4.0.exe

    4) On Login, set user type to "OTHER" and click next. at the top left side find "TARGET" and set it to O2/TMO

    5) While simultaneously holding both the volume buttons, connect the phone to the PC. As soon as the phone is connected, a COM# like COM3, etc. will appear on the MSM Tool and immediately click ENUM, then click COM#, then Start. (If COM# doesn't show up just continue to click the ENUM button during process and it should show up)

    <A YouTube Video walkthrough of this process> Credits to Shahin Shaan for this.

    **This should start the process of restoring your phone back to OxygenOS 10 and you have to start back to square 1 in order to flash Global ROM again. So, USB Debugging>Fastboot Mode>Unlock Bootloader>Enable USB Debugging Again>Boot again to Fastboot>Double Click on flash-all.bat on Global ROM folder. Also, I added TOOL ALL IN ONE which should make unlocking bootloader, booting to Fastboot faster.



    Credits to these amazing people for making this possible:

    @matteosaeed and his Guide.
    •Ms. user_ajusee's Guide
    •Mr. gregoryaul (@Aulgreg38) from HighOnAndroid Forums
    •THE MAN HIMSELF: Mr. Max Lee himself of HighOnAndroid Forums; link to his YouTube channel.
    9
    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
    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.
    3
    I am confused between this guide and the old one " Covert to Global ( WIP ) . Which one is best guide to convert OP8 TMO Android 11 to Global ?
    Should I back up/ change modem with this guide ?
    Is there diff between EU and Global ROM/modem/etc. to use 5G in USA and other oversea countries ?
    I want Always On Display ( AOD ) , which ROM EU or Global will have it ?
    TIA

    Yeah, it's not entirely clear to me, either.

    This is what you should do:

    (1) Put your phone back on Android 10 TMobile firmware using one of the packages with msmdownloadtool. I used 10.5.7

    (2) Unlock bootloader.

    (2*) Get TWRP boot image. Put phone in fastboot mode, type:

    fastboot boot twrpimage.img

    After TWRP boots, take a backup of your persist and modem partitions (I recommend using dd to do it, here's an example: dd if=/dev/block/boot device/by-name/persist of=/sdcard/persist.img.ext4). You could probably use TWRP to do the backup, but that's on you. Transfer them off of the phone and safeguard them.

    Now reboot from TWRP to fastboot mode. Unlock the bootloader, reboot to fastboot mode, and flash a 10.x euro or global ROM with fastboot. The guide says Euro, but I suspect you could use global, also. The goal is to have it running 10.x firmware (that's not for a carrier variant). After that boots, download the latest global OTA zip onto your internal sdcard. Open the updater in Settings, then select the file. After it updates, reboot to see if everything is OK. If it is, boot to fastboot and relock the bootloader.

    The