Develop Bugs

Unlocking boot loader issues

So finally received my htc 10 and whelp im unable to unlock the bootloader.
sending 'unlocktoken' (0 KB)...
OKAY [ 0.016s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.047s
yes oem unlocking is enabled and this is the factory unlocked one preordered from HTC. Has anyone seen similar issues with their unit?

Sunderwear said:
So finally received my htc 10 and whelp im unable to unlock the bootloader.
sending 'unlocktoken' (0 KB)...
OKAY [ 0.016s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.047s
yes oem unlocking is enabled and this is the factory unlocked one preordered from HTC. Has anyone seen similar issues with their unit?
Click to expand...
Click to collapse
Try a different browser

Sunderwear said:
So finally received my htc 10 and whelp im unable to unlock the bootloader.
sending 'unlocktoken' (0 KB)...
OKAY [ 0.016s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.047s
yes oem unlocking is enabled and this is the factory unlocked one preordered from HTC. Has anyone seen similar issues with their unit?
Click to expand...
Click to collapse
i had the same issue and used Microsoft Edge browser and it worked as per suggestion from somebody here

I'm having the same issue. Can't figure it out
Different browser did not work for me.

Think I had this issue once when I didn't copy the code into the box properly, copy it exactly as they do first line to last, I tend to have to remove some leading text from each row.

I was getting this error too but didn't realize I generated the code before checking the OEM Unlocking option dialog. The code changes once you do so.
Pasting this code in will just give you an unlock code that fails with that error message. Make sure you did not accidentally do it backwards.
Not sure how browser would be an issue.

Using the Microsoft Edge browser worked for me, but I have no idea why

I've got the same problem. OEM unlocking is enabled and I've regenerated my unlock_code.bin after doing so. I've made sure there's no leading or trailing spaces in the oem token code thing I paste in. I've tried downloading the unlock_code.bin through Microsoft Edge. Exact same error as OP. Any clues?

Took me 3 tokens
Sent from my HTC 2PS6200 using XDA-Developers mobile app

Can't unlock bootloader

Hi all.
Buyed today my new HTC 10.
Now I want to unlock bootloader and entering the command in download mode I receive this message:
C:\adb>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.177s]
finished. total time: 0.178s
Anyone can help me? Thanks

steno66 said:
Hi all.
Buyed today my new HTC 10.
Now I want to unlock bootloader and entering the command in download mode I receive this message:
C:\adb>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.177s]
finished. total time: 0.178s
Anyone can help me? Thanks
Click to expand...
Click to collapse
Did you enable developer options and toggle allow oem unlock there yet?

Allow oem unlock was not activate. Thanks now works
Sent from my HTC One_M8 using XDA-Developers mobile app

hi how i do it?
Did you enable developer options and toggle allow oem unlock there yet?
Click to expand...
Click to collapse

husharon said:
hi how i do it?
Click to expand...
Click to collapse
Settings > Info > Software Information > More > Tap 7 times on your Build number.
Go back to settings and at the bottom you can see now "Developer Options"

dottat said:
Did you enable developer options and toggle allow oem unlock there yet?
Click to expand...
Click to collapse
I have the Verizon Model and OEM Unlock is not in the Developer options.... is there an ABD command to disable the lock?

b.a.miller26 said:
I have the Verizon Model and OEM Unlock is not in the Developer options.... is there an ABD command to disable the lock?
Click to expand...
Click to collapse
you can't. Verizon has us blocked. Only option at the moment is to mail off to get it done (you will end up s-off too).

Also blocked
dottat said:
you can't. Verizon has us blocked. Only option at the moment is to mail off to get it done (you will end up s-off too).
Click to expand...
Click to collapse
To where do you mail off??? US mail or Web mail???
Thanks

Chucktr said:
To where do you mail off??? US mail or Web mail???
Thanks
Click to expand...
Click to collapse
He means per US-Mail to a service with a XTC Clip or Java Card to get s-off and unlock bootloader don't know if there is a professional service in the US but here in Europe you can send your device to Russia to handle this kind of a problem

Is there any possible way to unlock the OEM?

Is there any possible way to unlock OEM without going to developers option? Why i ask that? because I factory reset my HTC One M9 and im stuck on Google account login and I forgot what gmail i used to it. So i dont have access to my phone's settings to go to developer's setting and unlock the OEM there. And now i tried to unlock my bootloader with the help of Htcdev i follow all the steps until step 5 when I try to put the fastboot oem get_identifier_token i got this message appeared on my cmd
C:\adb>fastboot oem get_identifier_token ...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
and i tried this commands fastboot erase userdata and fastboot erase frp and this is the result
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.031s
So is there a possible way to unlock oem without going to developer's settings/option? I's still hoping there's a way to fix my phone. btw im S-ON

Help! My HTC One M9 is bricked and not sure what to do!

Hello everyone,
My phone boots straight into bootloader and I only have access to bootloader and download mode (no recovery). My phone is S-ON and Re-locked. Unlocking again doesnt seem to work and I get this error message when I try:
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.015s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
Any help on how to get S-OFF as well would be awesome!
I cannot find an RUU that matches my phone. My details are:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226065287278
(bootloader) version-main: 2.10.61.6
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG001
Any help would be greatly appreciated so thank you in advance! :good :

PlumpPanda said:
Hello everyone,
My phone boots straight into bootloader and I only have access to bootloader and download mode (no recovery). My phone is S-ON and Re-locked. Unlocking again doesnt seem to work and I get this error message when I try:
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.015s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
Any help on how to get S-OFF as well would be awesome!
I cannot find an RUU that matches my phone. My details are:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226065287278
(bootloader) version-main: 2.10.61.6
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG001
Any help would be greatly appreciated so thank you in advance! :good :
Click to expand...
Click to collapse
Factory Reset Protection is stopping the unlock. You should have removed your google account before messing with it.
Now you're locked out of your OS which is preventing you from flipping the bootloader unlock switch.
I honestly don't know how to get around that. I'm not sure an ruu flash will help either..
S-off, you need to run an app called "sunshine" and pay $25 or buy an xclip or the likes.
Beamed in by telepathy.

shivadow said:
Factory Reset Protection is stopping the unlock. You should have removed your google account before messing with it.
Now you're locked out of your OS which is preventing you from flipping the bootloader unlock switch.
I honestly don't know how to get around that. I'm not sure an ruu flash will help either..
S-off, you need to run an app called "sunshine" and pay $25 or buy an xclip or the likes.
Beamed in by telepathy.
Click to expand...
Click to collapse
It's true that this is a security feature but the google account has nothing to do with it. It's the option "OEM Unlock" in the developer options that seems to be inactive in this case. And yes, a RUU could fix this issue.
@PlumpPanda: That usually happens if the phone gets relocked although it's not completely stock. Security checks notice that the software isn't original (e.g. if TWRP is installed) and prevent the phone from booting so that it doesn't get "damaged" by the "faulty" software. (The software actually isn't faulty in reality but the security checks only distinguish between original software and not-original=faulty software if the bootloader is locked or relocked.) There seems to be no publicly available RUU for your firmware so all you can do is contacting Llabtoofer's RUU service and ask whether he can help you out. (Chances are high that he can.) Sunshine is no alternative since you have no booting system and java cards or xtc clips are way more expensive than the RUU service (unless you have friend that already owns one ).

Note the red highlight.. Frp = factory reset protection. If you have seen this error before then ignore me, I'm talking rubbish but as far as I can tell it wouldn't have frp if it was just the unlock killswitch stopping it. Would it?.
It does say that "enable unlock" then rejects it, probably due to the frp?.
Something tells me that this rabbit hole may go deeper if you keep digging but one thing is for sure.. Bye bye data.
Beamed in by telepathy.

shivadow said:
Note the red highlight.. Frp = factory reset protection. If you have seen this error before then ignore me, I'm talking rubbish but as far as I can tell it wouldn't have frp if it was just the unlock killswitch stopping it. Would it?.
It does say that "enable unlock" then rejects it, probably due to the frp?.
Something tells me that this rabbit hole may go deeper if you keep digging but one thing is for sure.. Bye bye data.
Beamed in by telepathy.
Click to expand...
Click to collapse
Yeah, I noticed the part that you highlighted in red. And it is a factory reset protection since it prevents the factory reset that gets triggered by a bootloader unlock. However, it has nothing to do with google accounts and it doesn't prevent you from flashing RUUs. But you're right, since a RUU completely wipes the phone the currently saved data (e.g. contacts, pictures, messages, etc.) is lost.
That error is not new. It exists since the M9 received firmware 2.x. You can't unlock the bootloader unless OEM Unlock is activated in the developer options. The oldest threads which deal with this problem got started around august 2015.
Edit: Wait a minute. I missed that part:
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
Click to expand...
Click to collapse
If OEM Unlock was disabled the output would be the following:
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
Click to expand...
Click to collapse
@PlumpPanda did you maybe try to use your old unlock token? Can you try to get a new one, please?

Flippy498 said:
Yeah, I noticed the part that you highlighted in red. And it is a factory reset protection since it prevents the factory reset that gets triggered by a bootloader unlock. However, it has nothing to do with google accounts and it doesn't prevent you from flashing RUUs. But you're right, since a RUU completely wipes the phone the currently saved data (e.g. contacts, pictures, messages, etc.) is lost.
That error is not new. It exists since the M9 received firmware 2.x. You can't unlock the bootloader unless OEM Unlock is activated in the developer options. The oldest threads which deal with this problem got started around august 2015.
Edit: Wait a minute. I missed that part:
If OEM Unlock was disabled the output would be the following:
@PlumpPanda did you maybe try to use your old unlock token? Can you try to get a new one, please?
Click to expand...
Click to collapse
Yeah I used the 'htcdev' website to get a new unlock code after my old one didn't work and it still doesn't unlock it. Thank you for all your help so far guys :good:
Edit:
@Flippy498 I've just got an email back saying Llabtoofer's RUU service can flash my phone so I'll let you know when all is said and done Thanks!
Phone is now fixed!! I used the Llabtoofer's RUU service and it worked perfectly. Highly recommended as it took roughly half an hour and now it works perfectly!!!! Thanks for you rhlpe guys!

Restoring to stock *LOCKED*

ok i have tried searching but im a bit dumbfounded i restored my phone back to stock via a ruu , then i set s-on back via command fastboot oem writesecureflag 3 now i need to set it back to locked , would really appreciated being pointed in right direction if possible please ?
** edit tried C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.021s
htc_fastboot finished. total time: 0.179s
C:\Android\com>
C:\Android\com>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Android\com>

tonnytech said:
ok i have tried searching but im a bit dumbfounded i restored my phone back to stock via a ruu , then i set s-on back via command fastboot oem writesecureflag 3 now i need to set it back to locked , would really appreciated being pointed in right direction if possible please ?
** edit tried C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.021s
htc_fastboot finished. total time: 0.179s
C:\Android\com>
C:\Android\com>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Android\com>
Click to expand...
Click to collapse
Use SunShine again and choose S-OFF/Locked. Afterwards go S-ON again, just like you did before.
You need to have flashed an RUU intended for your original model, not just stock.

errikosd said:
Use SunShine again and choose S-OFF/Locked. Afterwards go S-ON again, just like you did before.
You need to have flashed an RUU intended for your original model, not just stock.
Click to expand...
Click to collapse
thanks for the reply i sorted it as you suggested already appreciate reply thou