How To Guide The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)

[mingkee]

As soon as ROM dump is done, I unlocked the bootloader and applied root.
The first time was a failure, but it worked after another wipe.

 

[endsoftimesuffice]

Does anyone know if its possible to bypass the unlock code without 7Day waiting period?

 

[PopCaps1996]

Does anyone know if its possible to bypass the unlock code without 7Day waiting period?

No! just wait the 7 days like everyone else. patience is the key when it come to rooting an unlocking bootloaders

 

[ttar ttar]

Does any one know why I got an error message when I tried "fastboot flash cust-unlock unlock_code.bin"?? Need help. Thanks so much in advance!
(I did receive the email from Oneplus for the download link for the approval device unlocking application)


C:\Users\alank\Downloads\Adb\Root\platform-tools_r29.0.6-windows\platform-tools>fastboot flash cust-unlock unlock_code.bin
Sending 'cust-unlock' (0 KB) OKAY [ 0.008s]
Writing 'cust-unlock' FAILED (remote: 'Error - Verify Failed ! (-1)')
fastboot: error: Command failed


UPDATE: Never mind. Guess the first download has some issues. Re-downloading and it works now. Thanks!
C:\Users\alank\Downloads\Adb\Root\platform-tools_r29.0.6-windows\platform-tools>fastboot flash cust-unlock unlock_code(1).bin
Sending 'cust-unlock' (0 KB) OKAY [ 0.009s]
Writing 'cust-unlock' (bootloader) Device is unlocked.
OKAY [ 0.007s]
Finished. Total time: 0.026s

 

[AiM2LeaRn]

once in fastboot make sure your window drivers are working, i had to install them manually AGAIN using the .inf and selected "Android Bootloader Interface"

 

[edale1]

once in fastboot make sure your window drivers are working, i had to install them manually AGAIN using the .inf and selected "Android Bootloader Interface"

Erm, yes, I did point out the phone had to be connected and in fastboot mode when you manually installed the fastboot drivers... What exactly was your issue?

You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.

The PC is gonna use one of several drivers for the phone, depending on what mode the phone is in. It uses different drivers in fastboot mode than it does in recovery mode, which are different from the drivers when it's running normally.

 

[AiM2LeaRn]

Erm, yes, I did point out the phone had to be connected and in fastboot mode when you manually installed the fastboot drivers... What exactly was your issue?

The fact i had to load the drivers manually AGAIN (as in more than once).. normally windows doesnt forget the drivers once loaded. Just figured it might help someone that had similar issue.

 

[edale1]

The fact i had to load the drivers manually AGAIN (as in more than once).. normally windows doesnt forget the drivers once loaded. Just figured it might help someone that had similar issue.

That probably meant the phone wasn't in fastboot mode when you manually installed the drivers the first time. That, or your PC has more pressing issues than an odd driver reversion.

 

[DeadDjembe]

Do you know which specific app to uninstall removes the OEM unlock restriction? I want to unlock the bootloader, but would rather keep the other preinstalled software.

This is the command/app:

adb shell pm uninstall --user 0 com.qualcomm.qti.uim

 

[edale1]

This is the command/app:

adb shell pm uninstall --user 0 com.qualcomm.qti.uim

So that one command, with no others needed, will remove the OEM Unlock restriction?

Can someone verify?

 

[DeadDjembe]

So that one command, with no others needed, will remove the OEM Unlock restriction?

Can someone verify?

yes, correct. I've ran it numerous times now to re-enable OEM unlock after MSM restore. Trying to permanently edit init.rc and keep borking my phone

 

[jilebi]

yes, correct. I've ran it numerous times now to re-enable OEM unlock after MSM restore. Trying to permanently edit init.rc and keep borking my phone

Thank you for sharing! Very helpful. How did you end up figuring out that it was this specific uninstall out of all 50+ in the debloat script?

 

[edale1]

This is the command/app:

adb shell pm uninstall --user 0 com.qualcomm.qti.uim

I have added this info to the guide. Thanks for narrowing that down for us!

 

[DeadDjembe]

Thank you for sharing! Very helpful. How did you end up figuring out that it was this specific uninstall out of all 50+ in the debloat script?

I figured it out by trial and error. I was tired of having to reinstall a keyboard every time I ran the debloat script. As the script was running, I repeatedly kept trying to OEM unlock the phone. When I was able to successfully, the script was still running so I noted which app the script was currently removing. I then worked backward manually from that app the next time I needed to restore and OEM unlock - I was lucky because the first package I tried allowed me to unlock!

 

[elliwigy]

I got a tmb n200 but unfortunately within 5min seemed to have bricked it already lmao.. didnt even put a sim in it yet haha.. i basically connected to wifi then selected dsu loader and it loaded but when i reset device it says it is corrupt and will not start lolol

 

[jilebi]

I figured it out by trial and error. I was tired of having to reinstall a keyboard every time I ran the debloat script. As the script was running, I repeatedly kept trying to OEM unlock the phone. When I was able to successfully, the script was still running so I noted which app the script was currently removing. I then worked backward manually from that app the next time I needed to restore and OEM unlock - I was lucky because the first package I tried allowed me to unlock!

Very nice way to narrow it down. Nice job!

I agree adding the keyboard was a pain after the debloat script. Your work has helped others avoid that pain point.

 

[jilebi]

I got a tmb n200 but unfortunately within 5min seemed to have bricked it already lmao.. didnt even put a sim in it yet haha.. i basically connected to wifi then selected dsu loader and it loaded but when i reset device it says it is corrupt and will not start lolol

As @summersofar has correctly said above, DSU does not yet work with bootloader locked, which is why you got the brick. Fortunately, since you have the TMobile version, it can be easily fixed - just put the phone in EDL mode by pressing both Vol+ and Vol- at power up, and then use the MSMDownload tool for TMobile version that has been released, to unbrick it and restore to factory.

 

[edale1]

This thread has the MSMDownload Tools for the T-Mobile variant N200, as well as instructions as to its use:

[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS

Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...

forum.xda-developers.com

 

[elliwigy]

As @summersofar has correctly said above, DSU does not yet work with bootloader locked, which is why you got the brick. Fortunately, since you have the TMobile version, it can be easily fixed - just put the phone in EDL mode by pressing both Vol+ and Vol- at power up, and then use the MSMDownload tool for TMobile version that has been released, to unbrick it and restore to factory.

i figured as much but thought what the hell.. i thought for some reason itd fail to load and would boot the other slot and continue to boot but apparently this was not the case lmao.. either way, sweet theres a msm tool to restore it.. i got phone into edl mode but didnt have any luck then i read this thread and now i will be good to go..

question, is there a thread talking about the unlock bin? anyone tried to figure out how they are created?

 

[jilebi]

i figured as much but thought what the hell.. i thought for some reason itd fail to load and would boot the other slot and continue to boot but apparently this was not the case lmao.. either way, sweet theres a msm tool to restore it.. i got phone into edl mode but didnt have any luck then i read this thread and now i will be good to go..

question, is there a thread talking about the unlock bin? anyone tried to figure out how they are created?

Please see the first post in this thread on how to get the unlock.bin from Oneplus for Tmobile version. It has detailed steps. Basically, you have to get a code from your OEM unlocked phone, submit a form on Oneplus website, and then wait 7 days for them to send unlock code to you. However, keep in mind, you cannot do so until you unbrick your phone with the MSMDownload tool.