T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!

Search This thread

Superboy58

Senior Member
Jun 3, 2010
140
60
Clermont-Ferrand
Here is a patched MSM download tool for TMobile OP7T.
It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the privilege to unlock). It will NOT sim unlock the phone.

1) Download the patched MSM download tool: https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing

2) Run the tool, connect your phone in EDL mode (see below how to do it if you don't know), ensure the "sha256 check" is NOT checked, click the Start button and wait until it's completed.

3) The phone will show a red warning saying "device is corrupt", just ignore that and wait some time. It will fallback in fastboot because it's not able to boot. Now run the following fastboot command:
Code:
fastboot flashing unlock_critical

4) Bootloader is now unlocked. Update your fastboot executable, otherwise you'll encounter errors and modem issues. Download it here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip. Then boot the phone in fastboot mode, and follow the steps 7, 8 and 9 of this nice guide : https://forum.xda-developers.com/oneplus-7t/how-to/guide-t-mobile-brand-conversion-to-t4019495


How to enter EDL mode:
[...] Getting into EDL mode took me a while because I'd never had to do that on any previous phone way back when I used custom ROMs. Note that in EDL mode the screen is blank, and apparently it times out after 10 seconds. So the way to do it is to power off the phone and disconnect the USB if it's connected. Then press both volume UP and DOWN at same time, then while holding those buttons down, insert the USB which should already be connected to your computer. The best way would be to have the MSM program already open on your PC, then put phone into ELD mode. I had my left hand holding the volume buttons on the phone (press hard with two fingers to be sure), used right hand to plug in USB, then right hand on the mouse to work MSM. Once the USB is plugged in, watch the MSM window and look for it to say "Connected". Then just click the Start button. You can then release the volume buttons on the phone and let MSM do its thing. [...]
 
Last edited:

Superboy58

Senior Member
Jun 3, 2010
140
60
Clermont-Ferrand
Tested, 100% working.
No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.
 
  • Like
Reactions: jmkarnai01

jmkarnai01

Senior Member
Oct 10, 2010
543
231
44
Middlesex, NJ
OnePlus 7
OnePlus 7 Pro
Tested, 100% working.
No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.

Confirmed! Presently bootloader unlocked and global rom installed. Will receive my unlock token on Friday......hee hee.
Wanted to say thank you for putting this together and making it dummy proof.
 

warlord2045

Member
Jul 15, 2012
11
2
when i do a fastboot oem get_unlock_code, i get the following error message
FAILED (remote: Unknow command)
finished. total time: 0.006s

May I know where did i went wrong?

---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------

step 8 flash-all.bat, i got the following error messages, is it serious?

< waiting for any device >
Finished. Total time: 8.649s
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.005s]
Sending sparse 'system_a' 1/5 (523144 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 17.884s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 17.760s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
Press any key to continue . . .

---------- Post added at 02:13 AM ---------- Previous post was at 01:52 AM ----------

I tried flash-all.bat again, there is no error message but the fastboot oem get_unlock_code, i get the following error message
FAILED (remote: 'Unknow command')
fastboot: error: Command failed

I checked the Build Number, it is indeed the version i downloaded.
Anyone can help?

---------- Post added at 02:26 AM ---------- Previous post was at 02:13 AM ----------

Guys, my dual sim is working and I no longer see the T-mobile locked. Is that all i need?
 

ANDROIDRAZRM

Senior Member
Jun 5, 2013
174
49
Brilliant. If anyone is attempting this on Linux, I'd recommend getting the latest platform-tools straight from Google. Even the fastboot version from 2019 available in my repository was too old to perform a lot of the steps.
 
  • Like
Reactions: warren_gump

Superboy58

Senior Member
Jun 3, 2010
140
60
Clermont-Ferrand
I wonder who'll be the first to convert a McLaren to International??

We are on the 7T forum.
That being said, I made the same kind of tool for McLaren, but it only allows to unlock it's bootloader. There's no international firmware for McLaren. Unfortunately, there is no hardware equivalent for the McLaren sold as an international phone (it was easy for the 7T to convert because it's the same hardware, or at least very very close).
 

SALHERO

Member
Jul 29, 2012
18
3
maybe is a dumb question but what firmware i need download and install because, when i try the process all is ok. but the wireless is deactivated, not turn on (automatically turn off and not detect any signal). when i return to stock tmobile 1.0.3 all is working fine

edit----

something is wrong with the conversion...

c:\adb\OnePlus 7T T-Mobile 10.0.3\10.0.12-GLOBAL-OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_cce2fc-FASTBOOT>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.118s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: a431573c-e970-11ea-899c-8f976991a228
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (4616 KB) OKAY [ 0.110s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.307s
Sending 'boot_a' (98304 KB) OKAY [ 2.126s]
Writing 'boot_a' OKAY [ 0.485s]
Finished. Total time: 4.778s
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.628s
Sending 'modem_a' (165396 KB) OKAY [ 4.820s]
Writing 'modem_a' OKAY [ 0.720s]
Finished. Total time: 7.672s
Sending 'reserve' (250136 KB) OKAY [ 9.648s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.539s]
Writing 'recovery' OKAY [ 0.477s]
Finished. Total time: 5.811s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.063s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.042s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.035s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.012s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.072s
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.190s
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.021s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.008s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.171s]
Writing 'dsp' OKAY [ 0.394s]
Finished. Total time: 3.617s
Sending 'hyp' (480 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.010s]
Writing 'imagefv' OKAY [ 0.003s]
Finished. Total time: 0.062s
Sending 'keymaster' (248 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.294s]
Writing 'LOGO' OKAY [ 0.034s]
Finished. Total time: 0.576s
Sending 'multiimgoem' (16 KB) OKAY [ 0.007s]
Writing 'multiimgoem' OKAY [ 0.003s]
Finished. Total time: 0.050s
Sending 'odm' (912 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.064s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.175s
Sending 'opproduct' (586912 KB) OKAY [ 19.483s]
Writing 'opproduct' OKAY [ 2.505s]
Finished. Total time: 31.632s
Sending 'qupfw' (72 KB) OKAY [ 0.014s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.063s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3092 KB) OKAY [ 0.077s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.068s
Sending 'xbl' (3120 KB) OKAY [ 0.080s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.012s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'system' (2292492 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.115s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.167s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
 
Last edited:

Superboy58

Senior Member
Jun 3, 2010
140
60
Clermont-Ferrand
maybe is a dumb question but what firmware i need download and install because, when i try the process all is ok. but the wireless is deactivated, not turn on (automatically turn off and not detect any signal). when i return to stock tmobile 1.0.3 all is working fine

edit----

something is wrong with the conversion...

c:\adb\OnePlus 7T T-Mobile 10.0.3\10.0.12-GLOBAL-OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_cce2fc-FASTBOOT>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.118s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: a431573c-e970-11ea-899c-8f976991a228
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (4616 KB) OKAY [ 0.110s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.307s
Sending 'boot_a' (98304 KB) OKAY [ 2.126s]
Writing 'boot_a' OKAY [ 0.485s]
Finished. Total time: 4.778s
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.628s
Sending 'modem_a' (165396 KB) OKAY [ 4.820s]
Writing 'modem_a' OKAY [ 0.720s]
Finished. Total time: 7.672s
Sending 'reserve' (250136 KB) OKAY [ 9.648s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.539s]
Writing 'recovery' OKAY [ 0.477s]
Finished. Total time: 5.811s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.063s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.042s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.035s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.012s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.072s
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.190s
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.021s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.008s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.171s]
Writing 'dsp' OKAY [ 0.394s]
Finished. Total time: 3.617s
Sending 'hyp' (480 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.010s]
Writing 'imagefv' OKAY [ 0.003s]
Finished. Total time: 0.062s
Sending 'keymaster' (248 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.294s]
Writing 'LOGO' OKAY [ 0.034s]
Finished. Total time: 0.576s
Sending 'multiimgoem' (16 KB) OKAY [ 0.007s]
Writing 'multiimgoem' OKAY [ 0.003s]
Finished. Total time: 0.050s
Sending 'odm' (912 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.064s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.175s
Sending 'opproduct' (586912 KB) OKAY [ 19.483s]
Writing 'opproduct' OKAY [ 2.505s]
Finished. Total time: 31.632s
Sending 'qupfw' (72 KB) OKAY [ 0.014s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.063s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3092 KB) OKAY [ 0.077s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.068s
Sending 'xbl' (3120 KB) OKAY [ 0.080s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.012s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'system' (2292492 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.115s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.167s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s

I don't know why you were not able to boot into fastbootd (it says "Failed to boot into userspace fastboot" which means failed to boot into fastbootd).
But it's because of this error that all the warnings "Flashing is not allowed for Critical Partitions" are appearing.

If your fastboot executable is too old, the command "fastboot reboot fastboot", which allows you to boot in fastbootd, will not work. So I suggest you download the latest platform tools zip from Google, so you'll be using the latest adb and latest fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then ensure that in the terminal, the right version of fastboot is used (pay attention to the existing environment variables which might make your terminal use the old fastboot executable in another location).
Then run again the script flash-all.bat.
Please update,
Thanks
 
  • Like
Reactions: rob420p

jmkarnai01

Senior Member
Oct 10, 2010
543
231
44
Middlesex, NJ
OnePlus 7
OnePlus 7 Pro
Congrats!
 

Attachments

  • Screenshot_20200830-193703.jpg
    Screenshot_20200830-193703.jpg
    179.1 KB · Views: 671

Shortychance

New member
Feb 20, 2017
2
0
Umm would this by any chance work on a sim locked OnePlus 7t with an unpaid balance?? I bought one and got scammed cause when I called TMobile to unlock the phone they said they can't because it has money owned on it which the seller never told me. I geus would just be really nice if I could still do something about it and get it to work.
 

gonzalezb

Senior Member
Aug 13, 2012
165
79
Bentonville
Thank you allowed me to unlock the bootloader on my wifes 7t and convert to global firmware then i relocked the bootloader the global firmware and software just runs so much smoother than the T-Mobile software not sure why.
 

floopidze

New member
Aug 26, 2020
3
3
Hello,
is anybody know can this guide somehow help me to get my OnePlus 7T unlocked? I mean Network unlocked...
Please if somebody can help me with that I would really appreciate it. Thank you!
 
  • Like
Reactions: giusseppe_c

Superboy58

Senior Member
Jun 3, 2010
140
60
Clermont-Ferrand
Umm would this by any chance work on a sim locked OnePlus 7t with an unpaid balance?? I bought one and got scammed cause when I called TMobile to unlock the phone they said they can't because it has money owned on it which the seller never told me. I geus would just be really nice if I could still do something about it and get it to work.

It will work on a simlocked device, but it will not sim unlock the phone.
Please read the first post.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    Here is a patched MSM download tool for TMobile OP7T.
    It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the privilege to unlock). It will NOT sim unlock the phone.

    1) Download the patched MSM download tool: https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing

    2) Run the tool, connect your phone in EDL mode (see below how to do it if you don't know), ensure the "sha256 check" is NOT checked, click the Start button and wait until it's completed.

    3) The phone will show a red warning saying "device is corrupt", just ignore that and wait some time. It will fallback in fastboot because it's not able to boot. Now run the following fastboot command:
    Code:
    fastboot flashing unlock_critical

    4) Bootloader is now unlocked. Update your fastboot executable, otherwise you'll encounter errors and modem issues. Download it here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip. Then boot the phone in fastboot mode, and follow the steps 7, 8 and 9 of this nice guide : https://forum.xda-developers.com/oneplus-7t/how-to/guide-t-mobile-brand-conversion-to-t4019495


    How to enter EDL mode:
    [...] Getting into EDL mode took me a while because I'd never had to do that on any previous phone way back when I used custom ROMs. Note that in EDL mode the screen is blank, and apparently it times out after 10 seconds. So the way to do it is to power off the phone and disconnect the USB if it's connected. Then press both volume UP and DOWN at same time, then while holding those buttons down, insert the USB which should already be connected to your computer. The best way would be to have the MSM program already open on your PC, then put phone into ELD mode. I had my left hand holding the volume buttons on the phone (press hard with two fingers to be sure), used right hand to plug in USB, then right hand on the mouse to work MSM. Once the USB is plugged in, watch the MSM window and look for it to say "Connected". Then just click the Start button. You can then release the volume buttons on the phone and let MSM do its thing. [...]
    3
    so I'm gonna write my own summary hoping it fills any gaps. thanks to everyone else for providing very useful information and thanks to OP for putting in the work for figuring this out.

    1. first and foremost, make sure all of your drivers are correct. this is a must. boot into fastboot and EDL modes and check your device manager to make sure their drivers are properly installed. I had issues with getting the fastboot driver to work on my desktop but was picked up easily on my laptop. i still ended up pursuing fixing the driver on the desktop but no drivers from anywhere would work. i ended up going into windows update and installing the optional driver updates--some of these might be named samsung, but install any that sound related to android. this finally fixed the fastboot driver error on my desktop. the fastboot driver on my device manager was called "kedacom USB device">android bootloader interface

    2. I used the "all in one tool" available on this forum to get into EDL mode but you can do it manually too, it's not hard. as mentioned before, you will need to hold down the buttons then click start in MSM. If you release the volume buttons early it will kick you out of EDL--well at least for me. you can release the buttons once MSM starts. MSM took me about 130 seconds. This was over USB 3.0 port. I had no issue with USB 3.0 ports throughout the process but YMMV. At the end, it will give you a bootloader unlock menu and ask whether to unlock it or not. no one mentioned it before, but you have to manually click yes to unlock it. you will be kicked back into fastboot mode with the bootloader status as unlocked.

    3. I downloaded 10.0.9 global rom package, because i'm planning to relock the bootloader after. if you plan to keep bootloader unlocked just update to latest zip available. if you're planning to relock, make sure the zip isn't the latest version as you won't be able to OTA update from the OS if it's latest version (until there's another update). Copy the contents of the global rom zip into your ADB folder. The ADB tools inside the global rom zip might be older so I decided to keep the files in the ADB folder as is (i.e. the ones linked in OP) and not overwrite with the ADB files from the global rom zip. I went to CMD into the adb folder and ran the flash bat command. The first time it went to the "waiting for device" stage but did not go back into fastboot mode to continue, instead went to pink TMO bootscreen and eventually into the OS. I manually went back into fastboot mode via recovery mode and tried again. This time it went through it all (ignore the errors as mentioned in the CMD screen)

    You're done here if you want to keep the bootloader unlocked

    4. If you plan to relock bootloader, go into settings menu and look for update. you should get one, download it and install it. Once installed, factory reset and let it boot into OS. Then go into fastboot mode and relock bootloader with commands below

    check to make sure phone is being picked up by bootloader

    Code:
    fastboot devices

    command to relock bootloader

    Code:
    fastboot oem lock

    I went back into the fastboot menu to make sure it's locked and did another factory reset

    I can confirm that play store shows as certified and google pay cards can be added but I have not confirmed anything beyond that or checked netflix

    i hope this helps somewhat, good luck!
    2
    Tested, 100% working.
    No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
    This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.

    Confirmed! Presently bootloader unlocked and global rom installed. Will receive my unlock token on Friday......hee hee.
    Wanted to say thank you for putting this together and making it dummy proof.
    2
    Did you reopen another cmd to do this? When I restart my phone into fastboot, Powershell continued to do its thing until my phone restarted and it got stuck.

    I'll have to find another computer to try if that's not the case

    No, I did not.

    From what I understand, in some cases, you need to do the flash-all.bat twice, not sure if it's a bug or a feature. Long store short, use flash-all.bat command to flash the rom into the phone, then the phone restart into the pink T-Mobile screen, shut down the phone, restart it into fastboot, then use Flash-all.bat command again, and this time the phone will restart into the fastbootd mode(not sure what it's called) basically a screen looks like this "简体中文 繁體中文 English", if you see this screen, you're half way done, wait here until the CMD/powershell flash all the ROM into the phone, then the phone will restart, and voila.

    PS: if you want to relock the bootloader, you need to flash the 10.0.8 or early version, then use the OTA update to update to the latest version, then do a factory rest, and then use command to lock the phone, otherwise, you will face a software brick, which you have to redo every steps.

    I used CMD to do everything, powershell should do the same, and I was unable to pass the pink screen as you in my Desktop running Windows 10 LTSC, but I was able to flash my phone in an old ThinkPad laptop running windows 7 pro.

    So, in your case, I assume it's system related issue, if you did every steps correct. and the only solution would be try it in other computer.

    Hope this helps
    2
    I'm not sure. In my case, I had a driver that appeared to be correct but the MSM tool would just hang. If you have the phone running in edl mode you could check the driver version in device manager but I'm not sure how to verify which one is the correct one.

    This is the driver I ended up using.

    https://drive.google.com/file/d/0B0Fg_uwj-hWoYndYTTMwQUZ2RlU/view

    In addition, you'll need these drivers for windows too, in order for the phone to be recognized when it reboots into fastbootD.


    FastbootD is when the phone reboots for the firsttime after you run flash-all.bat, you get the screen saying hold the power button to pause booting, and then it brings you to the screen with the oneplus logo, and 3 language choices. Without these drivers it never gets recognized and can't continue.

    Between the OPS instructions and the ones posted by Vallan, i was able to do this yesterday on the Tmobile unlocked sim phone that b&h had for 299 on Black friday, works great and it auto updated itself to the latest OTA from oneplus. After doing that update, do a factory reset on it and then you can re-lock your bootloader if you want to.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone