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

Search This thread

brineshrimp

New member
Dec 4, 2020
2
0
Yup, that's exactly what I did last night (didn't post about it as it was too late)! Except I updated to 10.0.14 manually (OTA updates weren't triggering). Found the ROM somewhere on XDA (the official ROM on OnePlus' website was 10.0.15 and I really want OTA updates to work -- so holding out for that. I'm guessing OTA didn't work from 10.0.8 as it's too far back?)

In any case -- installed 10.0.14 manually, rebooted into the phone, factory reset it, rebooted again, and turned off at the start/setup screen. Restarted in fastboot mode, ran fastboot oem lock, used the volume key to select "lock my bootloader" and hit the power button to select -- the phone restarted, wiped again, and finally rebooted into the phone setup screen! So yes, it seems that if you flash an official ROM, factory reset, and finally lock bootloader, it's able to go through without corruption.

dont usually comment on stuff but i finally got everything working (make sure drivers/etc all updated) so hopefully this is helpful wrt OTA updates:

Last night when flashing my phone, I extracted the global ROM and used the ADB platform tools that came with the ROM. After getting my phone working, the system update feature would say my phone would say it was up to date despite running an old version (ex: it would say 10.0.8 as version and that phone was up to date). This morning when I extracted an older rom (10.0.8) in to the most recent platform tools folder (without replacing/copying over pre-existing files) and then flashed it, my phone said it was eligible for an immediate update.
 

joel5321

New member
Dec 4, 2020
4
0
dont usually comment on stuff but i finally got everything working (make sure drivers/etc all updated) so hopefully this is helpful wrt OTA updates:

Last night when flashing my phone, I extracted the global ROM and used the ADB platform tools that came with the ROM. After getting my phone working, the system update feature would say my phone would say it was up to date despite running an old version (ex: it would say 10.0.8 as version and that phone was up to date). This morning when I extracted an older rom (10.0.8) in to the most recent platform tools folder (without replacing/copying over pre-existing files) and then flashed it, my phone said it was eligible for an immediate update.
Do you remember which drivers you used in specific?
 

brineshrimp

New member
Dec 4, 2020
2
0
Do you remember which drivers you used in specific?

Not exactly. I'm definitely not an expert at this so take anything I say with a grain of salt, but I think the best bet to make sure everything goes smoothly was driver issues, which you can generally tell will be a problem by looking at the device manager and if there's a yellow triangle or the phone isn't being properly detected. I went through stuff in this thread and the other thread and switched between computers so I'm hesitant to give an -exact- answer.

For the first step, the MSM tool wasn't picking up my phone until I updated the qualcomm usb drivers (https://www.droidviews.com/qualcomm-hs-usb-qdloader-9008-drivers/). For the second step in fastboot I had to get the some android usb drivers. I tried https://oneplususbdrivers.com/ but I'm not sure those did anything.

All the drivers ended up properly installing when I looked at the windows update in my settings and adding them via optional updates. (I had previously been messing around with adding them manually). You'll know they're working because you can read the phone in your device manager.

Just as a note, I was a bit worried I'd destroy my phone but it seems pretty robust since you can always re-run the MSM tool to restart process at beginning.
 

Granch

New member
Dec 4, 2020
1
0
Friends, for the last 24 hours I have experienced the same pain as many. FedEx delivered yesterday the 7T purchased from B&H. Success achieved this afternoon, maybe my observations can help others. For context, no past experience, no technical skills, some luck for sure.

The first 3 steps from the guide here worked consistently for me to unlock the boot loader.

However, the flash-all stage was problematic. The flashing would stall, indefinitely waiting for device and the phone would reboot showing the T-mobile splash. Looking at Device Manager in Windows, I found that a driver was missing for HD1907. First I tried the OnePlus driver installer app available from the phone, Installed something but it did not seem to help. Then I tried to find the driver using Windows update. The driver is not updated automatically, you need to click down from the Updater Interface to find optional updates and check the box next the driver. The name was odd, like LeMobile ... Anyways i had the Updater install it, and I think this may have been the fix. However, also tried another driver from another tool. Using the ALL IN ONE tool, it will force install a driver from Google. Since it is an option available in the tool, I tried it.

Next I used that tool to do the flashing. This is more of a convenience than a requirement. Easiier for me to click a button than using the command line interface. The tool installed the 10...9 global rom successfully. Phone worked fine and ato updated, and can even lock the boot loader again using the ALL IN ONE. Easy to find in the 7T forum.

The 10...13 global rom did not ever work properly for me. Maybe stay away from that in case it is another problem. Updates work fine for older versions.

Good luck to those still trying.
 

joel5321

New member
Dec 4, 2020
4
0
Friends, for the last 24 hours I have experienced the same pain as many. FedEx delivered yesterday the 7T purchased from B&H. Success achieved this afternoon, maybe my observations can help others. For context, no past experience, no technical skills, some luck for sure.

The first 3 steps from the guide here worked consistently for me to unlock the boot loader.

However, the flash-all stage was problematic. The flashing would stall, indefinitely waiting for device and the phone would reboot showing the T-mobile splash. Looking at Device Manager in Windows, I found that a driver was missing for HD1907. First I tried the OnePlus driver installer app available from the phone, Installed something but it did not seem to help. Then I tried to find the driver using Windows update. The driver is not updated automatically, you need to click down from the Updater Interface to find optional updates and check the box next the driver. The name was odd, like LeMobile ... Anyways i had the Updater install it, and I think this may have been the fix. However, also tried another driver from another tool. Using the ALL IN ONE tool, it will force install a driver from Google. Since it is an option available in the tool, I tried it.

Next I used that tool to do the flashing. This is more of a convenience than a requirement. Easiier for me to click a button than using the command line interface. The tool installed the 10...9 global rom successfully. Phone worked fine and ato updated, and can even lock the boot loader again using the ALL IN ONE. Easy to find in the 7T forum.

The 10...13 global rom did not ever work properly for me. Maybe stay away from that in case it is another problem. Updates work fine for older versions.

Good luck to those still trying.
This worked like a charm ! Here's the funny thing too, I've been attempting for the past 24 hours and your analysis showed up exactly at the 24th hour. Thank you so much for this! That tool works great.
 

eigen

Senior Member
Nov 30, 2010
88
29
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!
 
Last edited:

Xetsu

Member
Jan 11, 2014
12
1
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 zip into your ADB folder (make sure you're using the latest ADB tools as mentioned in OP). The ADB tools inside the zip might be older so I decided to keep the files in the ADB folder as I've downloaded them. 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!


These are the steps that have got me far, but I'm still running into problems. I just want to make sure beforehand that I can ignore the errors shown here . When my phone rebooted again, it's stuck in the Tmobile screen. And right before that, I'm unable to connect to any wifi (it wouldn't detect it) and my SIM card (does not detect either). Any help is appreciated. Ty


Edit: I managed to run MSM Tool, but I have no idea how to proceed from here. I tried the method a few times over and in the end, my phone gets stuck at the Tmobile screen
 
Last edited:

klaymaniaf

Senior Member
Nov 27, 2011
156
39
These are the steps that have got me far, but I'm still running into problems. I just want to make sure beforehand that I can ignore the errors shown here . When my phone rebooted again, it's stuck in the Tmobile screen. And right before that, I'm unable to connect to any wifi (it wouldn't detect it) and my SIM card (does not detect either). Any help is appreciated. Ty


Edit: I managed to run MSM Tool, but I have no idea how to proceed from here. I tried the method a few times over and in the end, my phone gets stuck at the Tmobile screen


When in CMD with connected phone run "fastboot reboot fastboot" to get into fastboot d, and after run all fastboot images install commands.

You should check if when in fastboot d (screen will show like oneplus recovery, with some chinese words) your phone is correctly connected to pc by going to - right click My computer-manage- and you should look if Android adb something is displayed. If not reinstall drivers.
 

eigen

Senior Member
Nov 30, 2010
88
29
These are the steps that have got me far, but I'm still running into problems. I just want to make sure beforehand that I can ignore the errors shown here . When my phone rebooted again, it's stuck in the Tmobile screen. And right before that, I'm unable to connect to any wifi (it wouldn't detect it) and my SIM card (does not detect either). Any help is appreciated. Ty


Edit: I managed to run MSM Tool, but I have no idea how to proceed from here. I tried the method a few times over and in the end, my phone gets stuck at the Tmobile screen
i think at this point you don't need to do MSM. You're at flashing the global ROM. just go back and try to flash through fastboot again. Make sure your fastboot/ADB drivers are up to date (OP has link to latest)
 

Xetsu

Member
Jan 11, 2014
12
1
i think at this point you don't need to do MSM. You're at flashing the global ROM. just go back and try to flash through fastboot again. Make sure your fastboot/ADB drivers are up to date (OP has link to latest)

Hmm I don't think I was able to flash through fastboot without unlocking the bootloader and the only way to do that was with the MSM. Unless I'm terribly misunderstanding this right now...
 

a9udn9u

New member
Oct 6, 2010
1
0
My SIM is unlocked, am I supposed to follow a different guide? I always get the "Sahara Communication Failed" error.

Tried different cables, ports, etc.

UPDATE
I was able to fix the error by boot to fastboot (vol up + vol down + power), power off, wait for a few seconds then retry.
 
Last edited:

eigen

Senior Member
Nov 30, 2010
88
29
Hmm I don't think I was able to flash through fastboot without unlocking the bootloader and the only way to do that was with the MSM. Unless I'm terribly misunderstanding this right now...

if you go into fastboot and it says bootloader unlocked then you're done with MSM
 

Xetsu

Member
Jan 11, 2014
12
1
if you go into fastboot and it says bootloader unlocked then you're done with MSM

Oh, yes. So here's what happened...
1. I unlocked my bootloader with the patched MSM
2. I "flash-all.bat"
2. Device wipes and reboot while Powershell says <waiting for any device"
3. Device boots up and asks me to set up this and that. I manually went back to developer settings to enable fastboot through restart
4. Powershell continues with fastboot: error: failed to boot into userspace fastboot and continues with other errors before stopping
5. Devices restarts and becomes stuck at Tmobile logo

I've updated my drivers already unless the error indicates otherwise. After I run the intial "flash-all.bat", I'm unable to execute any other commands too..
 

soonleaf

New member
Dec 6, 2020
2
2
These are the steps that have got me far, but I'm still running into problems. I just want to make sure beforehand that I can ignore the errors shown here . When my phone rebooted again, it's stuck in the Tmobile screen. And right before that, I'm unable to connect to any wifi (it wouldn't detect it) and my SIM card (does not detect either). Any help is appreciated. Ty


Edit: I managed to run MSM Tool, but I have no idea how to proceed from here. I tried the method a few times over and in the end, my phone gets stuck at the Tmobile screen
I stuck in the same steps yesterday, and then I switch to another PC that solve the problem.

As for the Pink T-Mobile screen, when I do the flash-all.bat, the phone first boot into T-Mobile screen, and Then I restarted the phone to fastboot, re do the "flash-all.bat", and this time, the phone is restarted in the "Chinese/Chinese/English screen" and was able to flash the international ROM
 

Xetsu

Member
Jan 11, 2014
12
1
I stuck in the same steps yesterday, and then I switch to another PC that solve the problem.

As for the Pink T-Mobile screen, when I do the flash-all.bat, the phone first boot into T-Mobile screen, and Then I restarted the phone to fastboot, re do the "flash-all.bat", and this time, the phone is restarted in the "Chinese/Chinese/English screen" and was able to flash the international ROM

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
 

Xetsu

Member
Jan 11, 2014
12
1
When in CMD with connected phone run "fastboot reboot fastboot" to get into fastboot d, and after run all fastboot images install commands.

You should check if when in fastboot d (screen will show like oneplus recovery, with some chinese words) your phone is correctly connected to pc by going to - right click My computer-manage- and you should look if Android adb something is displayed. If not reinstall drivers.

Does it necessarily have to show up as Android adb? I'm looking around I see HD1907, which I assume is the phone. Thanks!

Edit: I think I fastboot correctly this time...I see LeMobile Android Device and, underneath it, Android Bootloader Interface

Edit 2: I did some research and followed this guide to show Android Device instead of Lemobile https://www.reddit.com/r/Nexus6P/comments/5nc64z
Edit 3: I attempted to do as you instructed, but I still get this message, "Failed to boot into userspace fastboot; one or more components might be unbootable."
 
Last edited:

turk.17

Member
Apr 27, 2015
43
6
Montreal
So I'm not 100% sure as I'm not familiar with this tool outside of my experience yesterday. But I did run into these issues as well. I resolved it by connecting the phone in EDL mode and uninstalling all the Qualcomm drivers. I had a mess of manually installed + qualcomm EXE installed drivers. Unplug the phone. Re-install the Qualcomm drivers, and reconnect the phone in EDL mode, hit Enum on the MSM tool (just keep this tool open in the background) and you should see the state "Connected." Hit "start" and hopefully this time it will walk past the stage it was getting in earlier.

Another note: try a different cable if the above doesn't work. So, in order:

1. get a clean slate of drivers. if this doesn't work:
2. try a different USB cable (less likely as USB cables are fairly robust). on failure:
3. try a different USB port, or a different computer altogether (this time with clean drivers)

Again, I'm no expert: last night was my first time doing anything like this (actually the last time I did something like this was jailbreaking my iPhone 3GS back in late 2008). But hopefully these processes/steps help. Obviously we're messing with core systems within the phone and we're not the engineers that designed these products or these tools -- so we're going to run into issues. We've also all accepted the omnipresent risk (as unlikely as it is) that something may go awry. But I've noticed the EDL mode to be fairly robust (as long as you're able to trigger it) and the MSM tool to be fairly robust too. As long as the driver/cable/USB stuff is working well.

Thank you so much! Seems like trying anew with my laptop instead of my desktop with fresh drivers and more experience did the trick.
 

0x0null

Senior Member
Mar 31, 2018
122
30
Lagos, NG
For all those having issues booting to fasbootd.

At the point the flashall.bat file attempts to reboot to fastboot but boots into what appears to be recovery mode, immediately go to your device manager on windows and locate the one plus 7t device. Manually install the drivers and immediately the process will continue successfully.

Even though on the gui it appears to be in recovery mode, it actually on fastbootd
 

Criston

Senior Member
Nov 19, 2014
941
161
Guys I have purchased a tmobile unlocked variant and I was wondering if after conversion I could use dual sim using a dual sim tray?😅

I know the tmobile variant will come with a single sim tray
 

rockrolll

New member
Oct 23, 2010
1
0
Your flow works perfectly! Ran into the same issue of booting into T-Mobile with no wifi with 10.0.9-GLOBAL-xxxxx-FASTBOOT. But repeat the process of running the batch file fixes the issue.
 

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