I have repeated the process to unlock the bootloader on my HTC EVO LTE, but after reboot it still says "LOCKED". I successfully submitted the token and even got the prompt on the phone whether I wanted to unlock, and I selected the first option "Yes". But, it's still locked upon reboot. Any ideas???
thambikutty said:
I have repeated the process to unlock the bootloader on my HTC EVO LTE, but after reboot it still says "LOCKED". I successfully submitted the token and even got the prompt on the phone whether I wanted to unlock, and I selected the first option "Yes". But, it's still locked upon reboot. Any ideas???
Click to expand...
Click to collapse
Anybody?
You simply must follow instructions exactly, not overlooking anything.
First go to htcdev-dot-com
Then click on the "Unlock Bootloader" link.
Follow the instructions exactly, submitting a valid email address with registration, and receive your unlock code file.
There are many more instructions on this forum for using this information to successfully unlock your bootloader.
I have had to use the same methods several times within the past few hours, just to perform a successful S-OFF
on my device. You can even stay at the htcdev website, submitting new device IDs as neccessary, until you
achieve your goal.
There may be other methods to unlock the bootloader, but I have no knowledge of them.
I'm trying to unlock the bootloader on my dna that's on 2.06 firmware. Please do not tell me to use moonshine, I have to unlock my bootloader first before trying. I've already had issues with it.
I unlocked my bootloader on earlier firmware (1.xx - I forget the exact version) so I have an old Unlock_code.bin from HTCDev. I already have SuperCID (all 1's), so I figured I didn't need to use jcase's newer method, which said it only worked on devices on 1.x anyway. I went through HTCDev anyway to make sure I could still unlock, but when I put in my device identifier token, I got error 160: MID not allowed.
As I said, I could just use the old Unlock_code.bin, but I want to do this the right way. Do I have to run jcase's exploit (even though it's only supposed to be for 1.x), or should I just use my old unlock code?
SOLVED
The answer is yes, you can use your old Unlock_code.bin, and you may have to. This will only work if you previously unlocked the bootloader and got SuperCID.
I just bought a att htc one off Craig's list and it is tampered/relocked. The phone boots straight into fastboot and there is no operation system on phone. I tried to use ruu to get it back to stock but it freezes at checking hash 5percent. I also tried to fastboot the ruu zip but it had an error verify 12 signatures. Are there any other suggestions that I could try to get an os back on this phone or is this phone pretty much bricked?
Unlock bootloader, install twrp recovery, sideload a rom zip.
There are numerous existing threads that describe how to do each step, just spend a little time reading first.
cschmitt said:
Unlock bootloader, install twrp recovery, sideload a rom zip.
There are numerous existing threads that describe how to do each step, just spend a little time reading first.
Click to expand...
Click to collapse
I don't think I can unlock the relocked bootloader without the token correct? Is there any other way to unlock a locked bootloader without the htcdev token?
crazyfied said:
I don't think I can unlock the relocked bootloader without the token correct? Is there any other way to unlock a locked bootloader without the htcdev token?
Click to expand...
Click to collapse
Yes, you'll need an unlock token.
OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile network; and a Windows PC, where a PC is used (though I imagine the Mac/Linux commands are quite similar). This is more to gather the info in one place than to provide step-by-step instructions.
SIM/NETWORK UNLOCK
Before you can unlock the bootloader, the N200 needs to be SIM unlocked. The option to Enable OEM Unlock won't even show up in the developers options until then. A temporary SIM unlock won't work, it needs to be a permanent SIM unlock.
If your N200 is the T-Mobile variant, you can get it SIM unlocked free here (be sure to read the first post thoroughly to be sure you qualify):
[CLOSED][T-Mobile USA] Free SIM Unlocking Service - [OnePlus/Samsung/Google/LG/Moto]
Hello XDA, I am back at it again with the free T-Mobile network unlocks. Yep, you heard that right... 100% FREE. This service will allow you to go into your Settings and perform a network unlock. I've been doing this for over 3 years now with...
forum.xda-developers.com
@mobbdeep had my SIM unlocked within 24 hours of sending him the required info.
You MUST have an active T-Mobile network (not Sprint or Metro) SIM card in the N200 for at least 3 full days before sending your SIM Unlock request in.
---
*edit-
An alternate is to use this debloat script:
Found a chink in the armor... Just enabled OEM unlocking after 11 update...
I haven't got a lot of time to get this out before heading out on a job, so here's the nitty gritty. A few days ago I flashed over "OnePlus_Nord_N10_5G_Metro_by_T-Mobile_OxygenOS_10.5.8" to get a clean start. I then allowed 10.5.14 to install...
forum.xda-developers.com
Which should unlock the OEM Unlock option in the developer options.
This should work with non-T-Mobile variants of the N200 as well.
Thanks to @PopCaps1996 for pointing this option out.
---
*edit2-
Thanks to user @DeadDjembe we now know the specific command from the debloat script which enables OEM Unlocking.
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
Running this ADB command on a stock T-Mobile variant N200 should enable the greyed-out Allow OEM Unlock option in the developers settings, without needing to run the full debloat script.
---
Once your N200 is SIM Unlocked, the Enable OEM Unlock option will show up in the developers options.
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
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.
UNLOCK CODE/TOKEN
Once you can access your phone in fastboot mode, you can try:
'fastboot oem unlock'
But, you'll just get a message asking for an unlock token. Doesn't hurt to try, just in case, though.
What you need to do now, is type:
'fastboot oem get_unlock_code'
This will display both the phone's serial number, plus a 64 digit unlock code. (you might not be able to select the code to copy it, but a ctrl-a / ctrl-c should work, then just paste it in notepad)
Now, on your phone (still in fastboot mode) hit up/down on the volume buttons, until you see "Show Barcode", then tap the power button to select it.
This will bring up a barcode, as well as listing you devices IMEI number. (there are other ways to get the IMEI, but this is quick, and you're already right there)
Copy the IMEI down.
Now go to:
https://www.oneplus.com/unlock_token
You'll need to create an account.
In that form, you'll need to select the phone's model, and then enter the serial number, 64 digit unlock code (no spaces), the IMEI, and your email, as well as checking a box that you acknowledge that you void the warranty by bootloader unlocking the phone.
If all goes well, It should take about a week from submission for them to send you the unlock token.
------
I've just sent in my info an hour or two ago, and am now waiting for my unlock token.
I'll update this with what you need to do with the token once I've gotten mine and figure it out myself, lol.
------
Exactly 7 days (nearly to the minute) after sending the request in, I received the unlock code. So here's the update:
APPLYING THE UNLOCK CODE
You can use this URL to check the status of your Unlock Coed request:
unlock token - OnePlus (United States)
www.oneplus.com
Once your Status is listed as "Finished", there will be a download button at the lower right corner.
Download the "unlock_code.bin" file to your PC.
Place 'unlock_code.bin' in:
C:\Users\[user name]\AppData\Local\Android\Sdk\platform-tools\
Or where ever you have your fastboot.exe file.
If you don't know where it is, the command:
Code:
fastboot --version
will give your it's location.
Now in command line, navigate to the folder "fastboot.exe" and "unlock_code.bin" are located in. Get your phone connected via USB, and in fastboot mode, and use the following command:
Code:
fastboot flash cust-unlock unlock_code.bin
(Thanks to @lentm for posting this command)
After checking the output, to be sure it worked, use this command:
Code:
fastboot oem unlock
Follow the on-screen instructions on your phone to finish the bootloader unlock.
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
PopCaps1996 said:
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
Click to expand...
Click to collapse
OK, that's neat.
I can't personally test it, as I'm already SIM unlocked; but all comments in the thread seem to indicate it working.
It'd be quite interesting if someone could narrow down exactly which of the removed apps enables the OEM Unlock option (as an uninformed guess: adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth).
I'd need to research what all those different apps do, but at a glance I see at least 2 or 3 on that list I'd want to keep. At any rate, I'd rather wait until after I get TWRP Recovery on my phone (once we get a release for the N200) before debloating it, just to be safe. I'm far more knowledgeable about computers than phones, which gives me just enough knowledge to seriously screw up my phone by doing the wrong thing, lol.
edale1 said:
OK, that's neat.
I can't personally test it, as I already have that unlocked; but all comments in the thread seem to indicate it working.
It'd be quite interesting if someone could narrow down exactly which of the removed apps enables the OEM Unlock option (as an uninformed guess: adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth).
I'd need to research what all those different apps do, but at a glance I see at least 2 or 3 on that list I'd want to keep. At any rate, I'd rather wait until after I get TWRP Recovery on my phone (once we get a release for the N200) before debloating it, just to be safe.
Click to expand...
Click to collapse
i can confirm it works that's the method i used to unlock my bootloader for my n200
Using the debloater worked beautifully to get ability to enable OEM Unlocking. Now it's just the week wait to get the code.
Really wish they'd speed that up; I've had to do this for four devices through them. Major benefit to buying direct from OnePlus, IMO. The last one I did was unlocked moments after getting home...(and is now running crDroid which I really hope comes to the N200)
PhoenixPath said:
Using the debloater worked beautifully to get ability to enable OEM Unlocking. Now it's just the week wait to get the code.
Really wish they'd speed that up; I've had to do this for four devices through them. Major benefit to buying direct from OnePlus, IMO. The last one I did was unlocked moments after getting home...(and is now running crDroid which I really hope comes to the N200)
Click to expand...
Click to collapse
you will not be able to modify anything anyways once you get the bootloader unlocked because oneplus has not released stock rom for the N200 on their website yet. so there for we do not have stock boot.img to be able to patch an root but i heard they will be uploading the rom soon. unless we can figure out how to back up boot img through fastboot but don't think that's possible
Yes, but to my knowledge unlocking the bootloader is the only part of the entire process of installing a custom recovery and rooting that wipes the device. So it's best to get that out of the way ASAP, before the phone's loaded with stuff you don't want to lose.
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
lentm said:
View attachment 5377289
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
Click to expand...
Click to collapse
can you send me the extracted payload.bin pm me please
PopCaps1996 said:
can you send me the extracted payload.bin pm me please
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/2c0d5671fc9a0f7829ab54b08139378afc295f46.zip
lentm said:
https://android.googleapis.com/packages/ota-api/package/2c0d5671fc9a0f7829ab54b08139378afc295f46.zip
Click to expand...
Click to collapse
the payload bin that you extracted? can you zip up the extractred imgs from payload . bin. an send them to me?
lentm said:
View attachment 5377289
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
Click to expand...
Click to collapse
Maybe it's because the ota is just an update, not a full zip?
PopCaps1996 said:
the payload bin that you extracted? can you zip up the extractred imgs from payload . bin. an send them to me?
Click to expand...
Click to collapse
I can get you the boot.img, not every img files. Check the attached.
lentm said:
I can get you the boot.img, not every img files. Check the attached.
Click to expand...
Click to collapse
When trying to patch the boot.img file with Magisk Stable version 23.0 (23000) (21) and Canary version f822ca5b (23001) (21), I get "Unsupported/Unknown image format. Installation failed".
dragonnightx said:
When trying to patch the boot.img file with Magisk Stable version 23.0 (23000) (21) and Canary version f822ca5b (23001) (21), I get "Unsupported/Unknown image format. Installation failed".
Click to expand...
Click to collapse
Yea, that's what I get too.
How long does OnePlus usually take in processing the bootloader unlock request?
TheLoonyRebel said:
How long does OnePlus usually take in processing the bootloader unlock request?
Click to expand...
Click to collapse
7 days
PopCaps1996 said:
you will not be able to modify anything anyways once you get the bootloader unlocked because oneplus has not released stock rom for the N200 on their website yet. so there for we do not have stock boot.img to be able to patch an root but i heard they will be uploading the rom soon. unless we can figure out how to back up boot img through fastboot but don't think that's possible
Click to expand...
Click to collapse
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
jilebi said:
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
Click to expand...
Click to collapse
I tried it and even I set it manually to N200, but no full ROM available
PopCaps1996 said:
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
Click to expand...
Click to collapse
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.