[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware

[DuckMySick98]

Hi,

I flashed the firmware GLOBAL 10.0.13, I'm from France. I have no wifi, no SIM detected or it is but i can't have network or something.
And when I try to flash 10.0.8. I have only fail in cmd and bootloop to fastboot. :'(

edit: Rebooting into fastboot (the one before Invalid Sparse file format at header magic) I get waiting for any device and doesn't boot into fastboot mode

edit2: any firmware wifi doesn't work pls help me


Do you want to wipe all the data ( Reccomended )[Y/N]?y Erasing 'userdata' OKAY [ 0.120s] mke2fs 1.44.4 (18-Aug-2018) Creating filesystem with 25477509 4k blocks and 6373376 inodes Filesystem UUID: af040874-40cf-11eb-8b84-850b49798eb1 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.023s] 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: 0.608s Sending 'aop' (200 KB) OKAY [ 0.010s] Writing 'aop' OKAY [ 0.005s] Finished. Total time: 0.041s Sending 'bluetooth' (828 KB) OKAY [ 0.007s] Writing 'bluetooth' OKAY [ 0.006s] Finished. Total time: 0.040s Sending 'boot_a' (98304 KB) OKAY [ 0.291s] Writing 'boot_a' OKAY [ 0.484s] Finished. Total time: 1.071s Sending 'dsp' (65536 KB) OKAY [ 0.194s] Writing 'dsp' OKAY [ 0.178s] Finished. Total time: 0.597s Sending 'dtbo' (16384 KB) OKAY [ 0.056s] Writing 'dtbo' OKAY [ 0.072s] Finished. Total time: 0.209s Sending 'LOGO' (6540 KB) OKAY [ 0.027s] Writing 'LOGO' OKAY [ 0.028s] Finished. Total time: 0.099s Sending 'modem_a' (161700 KB) OKAY [ 0.486s] Writing 'modem_a' OKAY [ 0.743s] Finished. Total time: 1.722s Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.017s] Writing 'oem_stanvbk' OKAY [ 0.011s] Finished. Total time: 0.062s Sending 'qupfw' (72 KB) OKAY [ 0.011s] Writing 'qupfw' OKAY [ 0.003s] Finished. Total time: 0.037s Sending 'storsec' (24 KB) OKAY [ 0.008s] Writing 'storsec' OKAY [ 0.002s] Finished. Total time: 0.037s Sending 'multiimgoem' (16 KB) OKAY [ 0.009s] Writing 'multiimgoem' OKAY [ 0.002s] Finished. Total time: 0.036s Sending 'uefisecapp' (124 KB) OKAY [ 0.010s] Writing 'uefisecapp' OKAY [ 0.003s] Finished. Total time: 0.038s Sending 'reserve' (266244 KB) OKAY [ 0.781s] Writing 'reserve' FAILED (remote: '(reserve_a) No such partition') fastboot: error: Command failed Sending 'recovery' (98304 KB) OKAY [ 0.295s] Writing 'recovery' OKAY [ 0.379s] Finished. Total time: 0.984s Sending 'vbmeta' (8 KB) OKAY [ 0.005s] Writing 'vbmeta' OKAY [ 0.002s] Finished. Total time: 0.030s Sending 'vbmeta_system' (4 KB) OKAY [ 0.011s] Writing 'vbmeta_system' OKAY [ 0.002s] Finished. Total time: 0.032s Sending 'opproduct' (578900 KB) OKAY [ 1.705s] Writing 'opproduct' OKAY [ 2.817s] Finished. Total time: 6.167s 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 'system' (2296784 KB) FAILED (Write to device failed (Invalid argument)) fastboot: error: Command failed < waiting for any device >


WTF data network is working but not wifi ??

I configured my phone still no wifi, can't update it says "installation problem" and can't relock bootloader it says the phone IS corrupted. I'm in 10.0.3

 

[DuckMySick98]

Sorry for monopolizing the discussion.

Anyway I finally success to flash.
I will resume what I did maybe it will helps someone else:

I was following this tuto: https://xdaforums.com/t/t-mobile-7t...thout-unlocked-bootloader-sim-unlock.4153943/

then I came here and followed steps:7, 8 and 9.
But I had some problem after launching the Flash-all.bat, it was showing me T-Mobile screen and no wifi or data working. Just go in your settings and enable adb debugging then reboot on bootloader and just reflash your rom. It will work.

And if you want to relock your bootloader, for me, I had to do OTA update from 10.0.8 to 10.0.15 if no it was showing "device corrupted".

And note that I didn't root.

 

[oneplus7t00]

Sorry for monopolizing the discussion.

Anyway I finally success to flash.
I will resume what I did maybe it will helps someone else:

I was following this tuto: https://xdaforums.com/t/t-mobile-7t...thout-unlocked-bootloader-sim-unlock.4153943/

then I came here and followed steps:7, 8 and 9.
But I had some problem after launching the Flash-all.bat, it was showing me T-Mobile screen and no wifi or data working. Just go in your settings and enable adb debugging then reboot on bootloader and just reflash your rom. It will work.

And if you want to relock your bootloader, for me, I had to do OTA update from 10.0.8 to 10.0.15 if no it was showing "device corrupted".

And note that I didn't root.

Hello,

I keep on getting the following errors while running flash-all.bat. It fails to flush tmobile rom and installing global version. Any idea why this is happening? thanks for your help

Sending 'reserve' (250164 KB) OKAY [ 7.975s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
and FAILED (remote: 'Flashing is not allowed for Critical Partitions

 

[oneplus7t00]

First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile Stock 10.0.8 to Rooted Global Firmware.

Please take the time to read every step carefully. It'll explain a little bit as to the why behind some of the steps. PM me if I've missed anything.

This has been revamped as some of the steps are no longer required. Devices coming from 10.0.6 and below might have to try a different set of steps. Click here for the post with the old instructions

Requirements:
ADB setup and working
Global Fastboot ZIP Grab the latest version (10.0.8 as of 3/20)
For Root:
Magisk Canery apk
Modded-Boot.img From here or make your own pulling your own boot.img and using magisk to create a modded boot.img file


=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
This group of instructions are going to walk you through on how to unlock your bootloader. This is the first general step in converting your device into a global device.

1. Either follow the rules via T-Mobile (paid off and 40 days on the network) or visit this thread and get the hook up from our friend (send him some cash, for real I did this and it worked hopefully he keeps up with this for a while!). This will allow you to use the Unlock App to permanently unlock your phone.
2. Open the "Unlock" app that's preinstalled on your phone and click on Permanent Unlock. If you have completed Step One correctly, it'll congratulate you and ask you to reboot your phone.
3. Reboot your phone and Enable Developer Settings. Check out the OEM Unlock button is now able to be switched off. Switch it off.
4. Be sure to also tick USB Debugging.
5. You'll now need to submit a request for an unlock_code.bin (could also be labeled unlock_token.bin) file from OnePlus via this link. It takes a week. Seriously almost down to the second. There's no avoiding this. I've read several people try (myself included) all met with the same fate. Wait. 7 whole days. You'll get an email from OnePlus containing the unlock_code.bin file. Download this file and save it to your ADB folder.

5a. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.​

Mine would be--​

cd c:\adb\

6. Reboot your phone into fastboot--

adb reboot bootloader

fastboot flash cust-unlock unlock_code.bin

fastboot oem unlock

This will unlock your bootloader and wipe your device
=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=

Now that you've unlocked your bootloader, lets get to flashing the Global Rom--

7. Extract the contents of the Global Fastboot Rom zip folder directly into your ADB folder.

a. If you did this correctly your ADB folder will be filled with a bunch of new .img files. Like boot.img​

8. Open CMD (with admin rights) and navigate to your ADB folder. I've heard users try to use Powershell and while it works mostly, ymmv. I stick with CMD and haven't had any issues.
Mine would be--

cd c:\adb\

This will also wipe your data, be sure to save anything that you need prior to running the following command.​

flash-all.bat

9. If you've never flashed via fastboot before, this is going to spit a bunch of information to you that might look like garbage. Your phone will boot a few different times including into FastbootD (link for explanation) But it's telling you what it's flashing and how fast it's doing it. There's a common looking error that happens every time you do this. It says "Invalid sparce file format at header magic". This is normal, just ignore it and keep waiting. Once everything settles, the device will reboot by itself. If it doesn't, like bootloops to the bootloader, start over and go back to Step 8 and try again.
10. You've now fully converted to the Global Firmware. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post).

You're done! Continue on if you want to root your device...

=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=

If you're interested in root:

11. Boot the device from the modded-boot.img file to give your self temp root. Once this is done, boot the device.

adb reboot bootloader
fastboot boot modded-boot.img

12. Install Magisk Manager Canary from here
13. Check in the middle of the screen for "advanced options" and make sure Preserve force encryption and preserve avb 2.0/dm-verify are checked.
14. Now look under the first Magisk check and make sure that it's telling you there's an update to "Magisk" and run through that update via direct install.
15. Once that finishes it'll have you reboot the phone.
16. You've now fully converted to the Global Firmware and Rooted. Confirm this by going to settings > about phone and look at Build Number. Should say 10.0.8(as of the time of this post)

=-=-=-=-=-=-=-=-=-=-=-=
Shoutouts will go here soon.

Hello,

I keep on getting the following errors while running flash-all.bat. It fails to flush tmobile rom and boots to tmobile version. Any idea why this is happening? thanks for your help

Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.506s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: 6511628a-4281-11eb-863d-3d063907c683
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' (544 KB) OKAY [ 0.022s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.007s
Sending 'boot_a' (98304 KB) OKAY [ 3.080s]
Writing 'boot_a' OKAY [ 0.494s]
Finished. Total time: 3.643s
Sending 'dtbo' (16384 KB) OKAY [ 0.517s]
Writing 'dtbo' OKAY [ 0.081s]
Finished. Total time: 0.670s
Sending 'modem_a' (165396 KB) OKAY [ 5.295s]
Writing 'modem_a' OKAY [ 0.807s]
Finished. Total time: 6.134s
Sending 'reserve' (250164 KB) OKAY [ 7.975s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed

Sending 'recovery' (98304 KB) OKAY [ 3.166s]
Writing 'recovery' OKAY [ 0.448s]
Finished. Total time: 3.661s
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta' OKAY [ 0.016s]
Finished. Total time: 0.097s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system' OKAY [ 0.000s]
Finished. Total time: 0.062s
Rebooting into fastboot OKAY [ 0.000s]
< 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.049s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.010s]
Writing 'aop' OKAY [ 0.000s]
Finished. Total time: 0.070s
Sending 'bluetooth' (828 KB) OKAY [ 0.030s]
Writing 'bluetooth' OKAY [ 0.010s]
Finished. Total time: 0.070s
Sending 'cmnlib' (384 KB) OKAY [ 0.015s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.025s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.020s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 1.971s]
Writing 'dsp' OKAY [ 0.194s]
Finished. Total time: 2.196s
Sending 'hyp' (480 KB) OKAY [ 0.022s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.000s]
Writing 'imagefv' OKAY [ 0.000s]
Finished. Total time: 0.038s
Sending 'keymaster' (248 KB) OKAY [ 0.016s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.207s]
Writing 'LOGO' OKAY [ 0.047s]
Finished. Total time: 0.285s
Sending 'multiimgoem' (16 KB) OKAY [ 0.000s]
Writing 'multiimgoem' OKAY [ 0.000s]
Finished. Total time: 0.047s
Sending 'odm' (912 KB) OKAY [ 0.031s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.077s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.147s
Sending 'opproduct' (586912 KB) OKAY [ 19.203s]
Writing 'opproduct' OKAY [ 2.697s]
Finished. Total time: 21.931s
Sending 'qupfw' (72 KB) OKAY [ 0.016s]
Writing 'qupfw' OKAY [ 0.000s]
Finished. Total time: 0.038s
Sending 'storsec' (24 KB) OKAY [ 0.000s]
Writing 'storsec' OKAY [ 0.000s]
Finished. Total time: 0.053s
Sending 'tz' (3092 KB) OKAY [ 0.100s]
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.016s]
Finished. Total time: 0.078s
Sending 'xbl' (3120 KB) OKAY [ 0.108s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.016s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784708 KB) OKAY [ 25.748s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 24.928s]
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) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Press any key to continue . . .

 

[handydandy]

Hello,

I keep on getting the following errors while running flash-all.bat. It fails to flush tmobile rom and boots to tmobile version. Any idea why this is happening? thanks for your help

Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.506s]
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: 6511628a-4281-11eb-863d-3d063907c683
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' (544 KB) OKAY [ 0.022s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.007s
Sending 'boot_a' (98304 KB) OKAY [ 3.080s]
Writing 'boot_a' OKAY [ 0.494s]
Finished. Total time: 3.643s
Sending 'dtbo' (16384 KB) OKAY [ 0.517s]
Writing 'dtbo' OKAY [ 0.081s]
Finished. Total time: 0.670s
Sending 'modem_a' (165396 KB) OKAY [ 5.295s]
Writing 'modem_a' OKAY [ 0.807s]
Finished. Total time: 6.134s
Sending 'reserve' (250164 KB) OKAY [ 7.975s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed

Sending 'recovery' (98304 KB) OKAY [ 3.166s]
Writing 'recovery' OKAY [ 0.448s]
Finished. Total time: 3.661s
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta' OKAY [ 0.016s]
Finished. Total time: 0.097s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system' OKAY [ 0.000s]
Finished. Total time: 0.062s
Rebooting into fastboot OKAY [ 0.000s]
< 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.049s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.010s]
Writing 'aop' OKAY [ 0.000s]
Finished. Total time: 0.070s
Sending 'bluetooth' (828 KB) OKAY [ 0.030s]
Writing 'bluetooth' OKAY [ 0.010s]
Finished. Total time: 0.070s
Sending 'cmnlib' (384 KB) OKAY [ 0.015s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.025s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.020s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 1.971s]
Writing 'dsp' OKAY [ 0.194s]
Finished. Total time: 2.196s
Sending 'hyp' (480 KB) OKAY [ 0.022s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.000s]
Writing 'imagefv' OKAY [ 0.000s]
Finished. Total time: 0.038s
Sending 'keymaster' (248 KB) OKAY [ 0.016s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.207s]
Writing 'LOGO' OKAY [ 0.047s]
Finished. Total time: 0.285s
Sending 'multiimgoem' (16 KB) OKAY [ 0.000s]
Writing 'multiimgoem' OKAY [ 0.000s]
Finished. Total time: 0.047s
Sending 'odm' (912 KB) OKAY [ 0.031s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.077s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.147s
Sending 'opproduct' (586912 KB) OKAY [ 19.203s]
Writing 'opproduct' OKAY [ 2.697s]
Finished. Total time: 21.931s
Sending 'qupfw' (72 KB) OKAY [ 0.016s]
Writing 'qupfw' OKAY [ 0.000s]
Finished. Total time: 0.038s
Sending 'storsec' (24 KB) OKAY [ 0.000s]
Writing 'storsec' OKAY [ 0.000s]
Finished. Total time: 0.053s
Sending 'tz' (3092 KB) OKAY [ 0.100s]
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.016s]
Finished. Total time: 0.078s
Sending 'xbl' (3120 KB) OKAY [ 0.108s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.016s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784708 KB) OKAY [ 25.748s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 24.928s]
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) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Press any key to continue . . .

I have the exact same issue. Seems it has to do with the recovery partition. I'm not sure how to flash in the recovery partition though.

Edit: So far I've narrowed down the issue to be that TWRP is unable to mount the system partition.
Should I try another recovery img instead of TWRP?

 

[glenb77]

i like many had same problem. reading along other thread may have been something to do with the fact i was using amd based laptop. but basically it is not going into fastbootd on the rebooting to fastboot after the vbmeta img gets flashed. for me i solved it by doing it in linux. i took flash-all.bat and made it linux script and it worked. for some reason i had to flash it twice before network (wifi and sim) worked. but very happy w/phone now. if you are desperate you could use live linux usb, boot with usb, get android-tools pkg installed and open up command prompt and make script from other or just type commands in bat file one at a time or maybe try on an intel based windows machine and most recent fastboot.exe

 

[BS20]

WOW THANK YOU!!! I went through the trouble of extracting an OTA from the OnePlus website, hooking up Py3, extracted the .bin using payload_dumper. and trying to flash each .img file. that is not the way to go.. Flash-all.bat is whats up. Is there a way to make a Fastboot zip out of any OTA? and how do you get fastboot to flash and re size system.img and find and write different sections of one partition? Thanks again, My OP7T is now T-mobile free. Merry Christmas!

Everything ran smooth on my Envy x360 AMD Ryzen5, just make sure you add "platform tools" to the PATH in your environmental variables.

 

[GuyInDogSuit]

WOW THANK YOU!!! I went through the trouble of extracting an OTA from the OnePlus website, hooking up Py3, extracted the .bin using payload_dumper. and trying to flash each .img file. that is not the way to go.. Flash-all.bat is whats up. Is there a way to make a Fastboot zip out of any OTA? and how do you get fastboot to flash and re size system.img and find and write different sections of one partition? Thanks again, My OP7T is now T-mobile free. Merry Christmas!

Everything ran smooth on my Envy x360 AMD Ryzen5, just make sure you add "platform tools" to the PATH in your environmental variables.

The "flash-all.bat" file almost never works as there's one file it can never seem to flash, and iirc it just stops the batch file process entirely, so it's usually best just to copypasta the commands one-by-one.

 

[prakhar26]

Hey Guys. I am very new in this and i am not even a developer. I almost tried for 9-10 hours and finally was able to Accomplish the task. I went trough all the possible failure, learnt it and overcome it. If any one need any help , i can explain in layman term. Thanks for all the help. CHeers.

PS- I was able to unlock the device first and change it from Tmobile to Global firmware.

 

[Irkath]

So i'm stuck as well.. Not sure what to do.

Oneplus 7T
Build-10.0.3 HD63CB


I came here from the other forum
( https://xdaforums.com/t/t-mobile-7t...thout-unlocked-bootloader-sim-unlock.4153943/ )
I was able to use the stuff on the other guide and the phone's bootloader is currently unlocked and now......
Was told from the guide to do steps 7,8,9

I downloaded- (10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT )

Platform-tools

I extracted the files into a folder then i extracted platform-tools into the same folder and let it overwrite existing files.

Loaded cmd with admin rights.

did flash-all.bat

c:\adb>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.528s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: 56b20520-4973-11eb-ba15-15fa0f18ecc8
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.007s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.194s
Sending 'aop' (200 KB) OKAY [ 0.011s]
Writing 'aop' OKAY [ 0.004s]
Finished. Total time: 0.038s
Sending 'bluetooth' (828 KB) OKAY [ 0.023s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.050s
Sending 'boot_a' (98304 KB) OKAY [ 2.122s]
Writing 'boot_a' OKAY [ 0.329s]
Finished. Total time: 2.577s
Sending 'dsp' (65536 KB) OKAY [ 1.407s]
Writing 'dsp' OKAY [ 0.197s]
Finished. Total time: 1.692s
Sending 'cmnlib' (384 KB) OKAY [ 0.014s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.017s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.007s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dtbo' (16384 KB) OKAY [ 0.359s]
Writing 'dtbo' OKAY [ 0.105s]
Finished. Total time: 0.504s
Sending 'LOGO' (6540 KB) OKAY [ 0.150s]
Writing 'LOGO' OKAY [ 0.022s]
Finished. Total time: 0.200s
Sending 'modem_a' (161892 KB) OKAY [ 3.508s]
Writing 'modem_a' OKAY [ 0.637s]
Finished. Total time: 4.410s
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.061s]
Writing 'oem_stanvbk' OKAY [ 0.017s]
Finished. Total time: 0.103s
Sending 'qupfw' (72 KB) OKAY [ 0.015s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.039s
Sending 'storsec' (24 KB) OKAY [ 0.008s]
Writing 'storsec' OKAY [ 0.002s]
Finished. Total time: 0.033s
Sending 'multiimgoem' (16 KB) OKAY [ 0.005s]
Writing 'multiimgoem' OKAY [ 0.002s]
Finished. Total time: 0.030s
Sending 'hyp' (480 KB) OKAY [ 0.017s]
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.033s
Sending 'keymaster' (248 KB) OKAY [ 0.019s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.009s]
Writing 'uefisecapp' OKAY [ 0.002s]
Finished. Total time: 0.034s
Sending 'recovery' (98304 KB) OKAY [ 2.102s]
Writing 'recovery' OKAY [ 0.430s]
Finished. Total time: 2.663s
Sending 'vbmeta' (8 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.033s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.033s
Sending 'opproduct' (208380 KB) OKAY [ 4.470s]
Writing 'opproduct' OKAY [ 1.041s]
Finished. Total time: 5.727s
Sending 'tz' (3092 KB) OKAY [ 0.071s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
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.
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 17.376s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785581 KB) OKAY [ 17.547s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785464 KB) OKAY [ 17.410s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.004s
Press any key to continue . . .

T-mobile loading screen still comes up and camera,wifi doesn't work now.


which is the correct files i should be using?

 

[GuyInDogSuit]

So i'm stuck as well.. Not sure what to do.

Oneplus 7T
Build-10.0.3 HD63CB


I came here from the other forum
( https://xdaforums.com/t/t-mobile-7t...thout-unlocked-bootloader-sim-unlock.4153943/ )
I was able to use the stuff on the other guide and the phone's bootloader is currently unlocked and now......
Was told from the guide to do steps 7,8,9

I downloaded- (10.0.3-HD65AA-OnePlus7TOxygen_14.I.05_OTA_005_all_1909252229_1be2cbaa2-FASTBOOT )

Platform-tools

I extracted the files into a folder then i extracted platform-tools into the same folder and let it overwrite existing files.

Loaded cmd with admin rights.

did flash-all.bat

c:\adb>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.528s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: 56b20520-4973-11eb-ba15-15fa0f18ecc8
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.007s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.194s
Sending 'aop' (200 KB) OKAY [ 0.011s]
Writing 'aop' OKAY [ 0.004s]
Finished. Total time: 0.038s
Sending 'bluetooth' (828 KB) OKAY [ 0.023s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.050s
Sending 'boot_a' (98304 KB) OKAY [ 2.122s]
Writing 'boot_a' OKAY [ 0.329s]
Finished. Total time: 2.577s
Sending 'dsp' (65536 KB) OKAY [ 1.407s]
Writing 'dsp' OKAY [ 0.197s]
Finished. Total time: 1.692s
Sending 'cmnlib' (384 KB) OKAY [ 0.014s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.017s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.007s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dtbo' (16384 KB) OKAY [ 0.359s]
Writing 'dtbo' OKAY [ 0.105s]
Finished. Total time: 0.504s
Sending 'LOGO' (6540 KB) OKAY [ 0.150s]
Writing 'LOGO' OKAY [ 0.022s]
Finished. Total time: 0.200s
Sending 'modem_a' (161892 KB) OKAY [ 3.508s]
Writing 'modem_a' OKAY [ 0.637s]
Finished. Total time: 4.410s
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.061s]
Writing 'oem_stanvbk' OKAY [ 0.017s]
Finished. Total time: 0.103s
Sending 'qupfw' (72 KB) OKAY [ 0.015s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.039s
Sending 'storsec' (24 KB) OKAY [ 0.008s]
Writing 'storsec' OKAY [ 0.002s]
Finished. Total time: 0.033s
Sending 'multiimgoem' (16 KB) OKAY [ 0.005s]
Writing 'multiimgoem' OKAY [ 0.002s]
Finished. Total time: 0.030s
Sending 'hyp' (480 KB) OKAY [ 0.017s]
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.033s
Sending 'keymaster' (248 KB) OKAY [ 0.019s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.009s]
Writing 'uefisecapp' OKAY [ 0.002s]
Finished. Total time: 0.034s
Sending 'recovery' (98304 KB) OKAY [ 2.102s]
Writing 'recovery' OKAY [ 0.430s]
Finished. Total time: 2.663s
Sending 'vbmeta' (8 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.033s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.033s
Sending 'opproduct' (208380 KB) OKAY [ 4.470s]
Writing 'opproduct' OKAY [ 1.041s]
Finished. Total time: 5.727s
Sending 'tz' (3092 KB) OKAY [ 0.071s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
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.
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 17.376s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785581 KB) OKAY [ 17.547s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785464 KB) OKAY [ 17.410s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.004s
Press any key to continue . . .

T-mobile loading screen still comes up and camera,wifi doesn't work now.


which is the correct files i should be using?

There is some speculation that certain chipsets (ie, AMD vs Intel) that seem to mess with the flasth-all batch file. But try running each command one at a time, rather than running the bat itself. Just be sure to wipe first. I think you have to be in fastbootd, too, iirc.

 

[Irkath]

There is some speculation that certain chipsets (ie, AMD vs Intel) that seem to mess with the flasth-all batch file. But try running each command one at a time, rather than running the bat itself. Just be sure to wipe first. I think you have to be in fastbootd, too, iirc.

i'm on a intel based pc I tried doing to one by one and got this far.

PS C:\Windows\system32> cd c:\adb
PS C:\adb> .\fastboot -w
Erasing 'userdata' OKAY [ 0.517s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: d9c800ee-49dd-11eb-b8b3-b3b8c02a81e2
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.103s]
Writing 'userdata' OKAY [ 0.006s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.026s
PS C:\adb> .\fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.093s]
Writing 'boot_a' OKAY [ 0.454s]
Finished. Total time: 2.782s
PS C:\adb> .\fastboot flash dtbo dtbo.img
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.068s]
Finished. Total time: 0.458s
PS C:\adb> .\fastboot flash modem modem.img
Sending 'modem_a' (165396 KB) OKAY [ 3.533s]
Writing 'modem_a' OKAY [ 0.731s]
Finished. Total time: 4.466s
PS C:\adb> .\fastboot flash reserve reserve.img
Sending 'reserve' (250164 KB) OKAY [ 5.311s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
PS C:\adb> .\fastboot flash recovery recovery.img
Sending 'recovery' (98304 KB) OKAY [ 2.089s]
Writing 'recovery' OKAY [ 0.361s]
Finished. Total time: 2.567s
PS C:\adb> .\fastboot --disable-verity flash vbmeta vbmeta.img
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.030s
PS C:\adb> .\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.007s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.026s
PS C:\adb> .\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 8.567s
PS C:\adb> .\fastboot flash abl abl.img
Sending 'abl' (1164 KB) OKAY [ 0.034s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')

 

[14christ]

Once a t-mobile phone has been bootloader unlocked and flashed with global ROM, is it practically considered a "unbranded / factory unlocked" version? I mean, can I directly use OOS ROMs "not meant for t-mobile variant"? I guess I'm not sure why we need to boot into modded-boot.img first and then install magisk. Why can't we flash the modded boot image directly?

I think the main reason why people recommend this is to make sure the modified boot img will boot first. Then once its proven to boot, do a direct install. If your sure that your patched boot img is good then I dont see why you cant just flash through fastboot. There are so many patched boot img files floating around and sometimes people download the wrong one, flash it, and have all kinds of issues. Just make sure your boot.img file came from your specific ROM

 

[guliver365]

Well I flashed the magisk_patched 10.0.8 international.img after reboot I installed the app-debug.apk (magisk canary installer) but now it does not pass safety net.
Also how come I do not see the option to hide magisk neither navigation menu with modules install?
EDIT
The problem is if you use the magisk_patched-10.0.8-international.img it worked but the manager made me upgrade from 20.3 to 6db88d8ad(21201)
and after that it broke not sure why? I think I di direct install maybe shoud it be done on the inactive slot

EDIT
Never mind probably to much beer at new year I did again everything is cool.

 

[guliver365]

And regarding Netflix my solution is : since I was rooted was to update Netflix with Titanium as user application from that app store upgraded with no problem

 

[hypercoyote]

Just to be clear, if you get this error, it's not an issue, right? I'm seeing it in several people's outputs but nobody seems to be talking about it:


fastboot flash reserve reserve.img
Sending 'reserve' (250164 KB) OKAY [ 5.863s]
Writing 'reserve' FAILED (remote: '(reserve_b) No such partition')
fastboot: error: Command failed

I've written up a more detailed set of steps on this that I'm not sure if I should start a new thread on or just post it here, but the main guide is missing a lot of crucial info, although it did get me to this point at least.

 

[hypercoyote]

nolimit78 pieced together a lot of good info and I just wanted to post a revision on that with some clarification for those who may not be too familiar with this process. The link to this is at the bottom.

For the record, I performed this on a OnePlus 7T (Model HD1907), Build 10.0.12.HD63CB, Android Version 10 and used Windows 10 to connect to the phone via USB.

1. Update System Software
Ensure the phone is on the latest system software (which should be at least 10.0.6) to make the conversion easier. This will keep you from having to step through an intermediate firmware version:

1. In the Settings, go to System > System Update and click 'Check for update' or resume/install an ongoing update

2. SIM Unlock (Carrier Unlock)
This requires putting in a request with T-Mobile and took about 3 days for me.

1. Request SIM unlock from T-Mobile on Facebook (message them from here: https://www.facebook.com/TMobile/)
   1. They will ask for your IMEI and phone number, then verify that you are not on a contract.
   2. I've heard results may vary with this, but I didn't have any issue and I did two phones
2. Once they confirm it is unlocked, performed the following to unlock on the phone:
   1. In Settings, go to Wi-Fi & internet > SIM & network > Network Unlock.
   2. Choose unlock type: Permanent Unlock

3. Boot Unlock (Bootloader Unlock)

1. Enable Developer Settings:
   1. Go to Settings > About Phone
   2. Tap on "Build Number" 7 times and you will see a message at the bottom of the screen the developer options are enabled
2. Use Developer Settings to enable OEM Unlock:
   1. Go to Settings > System > Developer options
   2. Enable "OEM unlocking" (shown disabled below)
3. Get IMEI by dialing *#06# or in Settings > About Phone > Status
4. Enter fastboot mode to get the unlock code:
   1. If you haven't already, install the OnePlus 7T USB Drivers by connecting it to your PC while the phone is powered on normally. It will mount a drive for "OnePlus Drivers" from which you can run the driver installation. Note: For me, the installer got stuck at the 'executing commands' step and I had to restart the PC and reinstall, then it installed quickly.
   2. Download “fastboot_windows.zip” and unzip it on your computer.
   3. Power off the OnePlus 7T.
   4. Press and hold the “Volume +” and “Volume -” and then "Power" keys until the “fastboot mode” menu appears
5. With this menu open on the phone, connect the phone to your computer via USB
6. Open a command prompt (not Powershell) on Windows, switch to the fastboot directory and run it using the following commands:
   Note: If it says 'waiting for device', then you need to install the OnePlus USB drivers or determine why the driver isn't working
   

   cd <fastboot directory>
   fastboot.exe oem get_unlock_code

7. Submit the the information found above at this link and wait 7 days for them to send you the unlock file: https://www.oneplus.com/unlock_token
8. THESE NEXT STEPS WILL WIPE YOUR USER DATA! BE SURE YOU HAVE BACKED UP YOUR DATA BEFORE DOING THIS!
   After receiving the unlock_code.bin file from OnePlus, put them in the fastboot directory and run the following commands:
   

   fastboot flash cust-unlock unlock_code.bin
   fastboot oem unlock

9. A warning will appear on the screen after the last command explaining that once the boot loader is unlocked and a custom OS is installed, they cannot verify the integrity of the system. Use the “Volume +” and “Volume -” buttons to highlight the unlock the bootloader option, then press "Power" button to select it. The phone will wipe your user data and then reboot. It may take a while to reboot while it displays the "T-Mobile" loading screen. Let it sit at least 10 minutes before trying to reboot.
   Note: Your device will display a warning at boot until you re-lock the bootloader. Many have recommended not re-locking the bootloader due to various issues with it.

4. Installing Global Firmware
For this step, you *might* need adb tools installed. I think that everything you need is contained in the ROM archive from step 1 below, but if you get an error, download SDK Platform Tools for Windows from this link and install it.

1. Download the newest *GLOBAL-OnePlus7TOxygen*.zip from this link: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T/
2. Extract the contents of the zip file for use later.
3. Return to the fastboot menu on the phone:
   1. Power off the OnePlus 7T.
   2. Press and hold the “Volume +” and “Volume -” and then "Power" keys until the “fastboot mode” menu appears
4. Connect your Phone to the PC via USB.
5. Open a command prompt and change into the directory for the *GLOBAL-OnePlus7TOxygen*.zip
6. From the command prompt, run the flash-all.bat file
   Note: At one point, the phone will reboot and mine showed a menu with a language selection screen instead of the normal Fastboot menu. DON'T TOUCH THE PHONE, BE SURE TO STAY AT THE LANGUAGE SELECTION SCREEN. I clicked through it and went back to the fastboot menu and that made everything else fail.
   FYI, I received the following errors, but it seemed to work:
   

   # Error 1D:\Downloads\OnePlus 7T Unlock\Global Fastboot ROM (Latest)\10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT>fastboot flash reserve reserve.img
   Sending 'reserve' (250164 KB) OKAY [ 5.863s]
   Writing 'reserve' FAILED (remote: '(reserve_b) No such partition')
   fastboot: error: Command failed
   
   # Error 2
   D:\Downloads\OnePlus 7T Unlock\Global Fastboot ROM (Latest)\10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT>fastboot flash opproduct opproduct.img
   Invalid sparse file format at header magic
   Sending sparse 'opproduct_b' 1/1 (391796 KB) OKAY [ 9.447s]
   Writing 'opproduct_b' OKAY [ 3.180s]
   Finished. Total time: 14.376s
   
   # Error 3
   D:\Downloads\OnePlus 7T Unlock\Global Fastboot ROM (Latest)\10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT>fastboot flash system system.img
   Invalid sparse file format at header magic
   Resizing 'system_b' OKAY [ 0.005s]
   Sending sparse 'system_b' 1/5 (523136 KB) OKAY [ 12.658s]
   Writing 'system_b' OKAY [ 3.076s]
   Sending sparse 'system_b' 2/5 (523148 KB) OKAY [ 12.544s]
   Writing 'system_b' OKAY [ 3.071s]
   Sending sparse 'system_b' 3/5 (523640 KB) OKAY [ 12.597s]
   Writing 'system_b' OKAY [ 3.074s]
   Sending sparse 'system_b' 4/5 (524256 KB) OKAY [ 12.526s]
   Writing 'system_b' OKAY [ 3.083s]
   Sending sparse 'system_b' 5/5 (197932 KB) OKAY [ 4.786s]
   Writing 'system_b' OKAY [ 1.364s]
   Finished. Total time: 77.293s
   
   # Error 4
   D:\Downloads\OnePlus 7T Unlock\Global Fastboot ROM (Latest)\10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT>fastboot flash vendor vendor.img
   Invalid sparse file format at header magic
   Resizing 'vendor_b' OKAY [ 0.005s]
   Sending sparse 'vendor_b' 1/2 (523681 KB) OKAY [ 12.737s]
   Writing 'vendor_b' OKAY [ 3.065s]
   Sending sparse 'vendor_b' 2/2 (427876 KB) OKAY [ 10.438s]
   Writing 'vendor_b' OKAY [ 2.626s]
   Finished. Total time: 32.395s

7. Once the phone reboots, you should see the OnePlus boot-up screen instead of the T-Mobile one and all should be working.

References
Retrieve unlock token: https://www.oneplus.com/unlock_token

Unlocking bootloader: https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone

Install process: https://xdaforums.com/t/guide-wip-t-mobile-brand-conversion-to-rooted-global-firmware.4019495/

 

[Kediil]

CRUD MONKIES. So, I did the process. Everything was fine. Then I relocked the bootloader. And now it just keeps saying
Your device is corrupt. It can't be trusted and will not boot.

And I can't re-unlock it.. The all in one tool is not detecting it... Really hoping someone is around to help.

 

[SuperEsteban]

CRUD MONKIES. So, I did the process. Everything was fine. Then I relocked the bootloader. And now it just keeps saying
Your device is corrupt. It can't be trusted and will not boot.

And I can't re-unlock it.. The all in one tool is not detecting it... Really hoping someone is around to help.

The first time that I did it, it happened to me something similar, I unintended relock the bootloader (because I'm an idiot), so, I had to reflash it with the All In One Tool, that let me boot again, then I followed the instructions to unlock it again.

 

[Kediil]

Six hours later and I managed to unbrick it. All sorts of errors and driver fits and sahara and smt. Not to mention my pc deciding it was time to blue screen on me multiple times.
But I got it.
That T-mobile logo has never looked so sweet.