Develop Bugs

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

Htc m9 soft bricked

Hi everyone i hope I put this in the right area I'm new to forums and if not I'm sorry and could the admin please put me in the right place so I known for next time we'll here's my problem I have an AT&T m9 bootloader locked rooted and s-off with twrp recovery 2.8.6.0 well I tryed flashing the viperone rom on it with the bootloader locked I assumed sence i rooted it the bootloader was unlocked well it was not and so its now soft bricked it I can still get in to recovery but it hangs on the logo screen if I try to boot it up and I've tryed the ruu for it that another post told me to use but every time I try I get error code 150 unknown error and when I go to download mode it says at the bottom file /mnt/media_rw/ext_sd/opjaimg.zip file not found and the memory card I have is 64 gigs if that makes a difference if any one can help me that would be much appreciated and thanks for any help anyone can give
me

Unlock the bootloader via htcdev and flash viperone via twrp

htc m9
degerli43 said:
Unlock the bootloader via htcdev and flash viperone via twrp
Click to expand...
Click to collapse
hi iv tried what you said but i dont get that long list like im suppose to iget this
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>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.012s]
finished. total time: 0.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>
and when im in the bootloader i dont have a fastboot option do i not have fastboot poperly installed mabe

OEM unlocking should be ticked in Settings>developer options

side_flip15 said:
OEM unlocking should be ticked in Settings>developer options
Click to expand...
Click to collapse
It should all ready be off because the guy I paid to get the frp off checked oem unlocking to be able to get the s-off and I can't get to settings anyway cause it's soft bricked

Well based on the fastboot command output it seems like its not.
Please run fastboot getvar all and post the output here. remove the SN and IMEI

side_flip15 said:
Well based on the fastboot command output it seems like its not.
Please run fastboot getvar all and post the output here. remove the SN and IMEI
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Owner>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: 11111111
all:
finished. total time: 0.046s
i all so made sure fastboot was properly installed

Looks like you have a dev edition.
Two options for you...
1. Since you are s-off already you can try to unlock bootloader without htcdev. check this link for instructions. After unlock you can flash latest TWRP here. You're still in LP firmware so latest Viper ROm will not work for you. You will need to flash MM dev edition firmware, dl here.. After flashing you can install the latest Viper Rom via TWRP.
2. You can find the MM RUU or ROm.zip here. Run RUU or flash Rom.zip. This will already upgrade your M9 to MM.
good luck!

side_flip15 said:
Looks like you have a dev edition.
Two options for you...
1. Since you are s-off already you can try to unlock bootloader without htcdev. check this link for instructions. After unlock you can flash latest TWRP here. You're still in LP firmware so latest Viper ROm will not work for you. You will need to flash MM dev edition firmware, dl here.. After flashing you can install the latest Viper Rom via TWRP.
2. You can find the MM RUU or ROm.zip here. Run RUU or flash Rom.zip. This will already upgrade your M9 to MM.
good luck!
Click to expand...
Click to collapse
Now it's saying that adb server is out of dare then says killing all I did was Uninstall adb and reinstall it yesterday

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!

HTC 10 stuck in download mode

Hey,
After a series of mess ups on my HTC-10, i am now stuck in bootloader mode, S-on with relocked. When i try to unlock my bootloader using flash unlocktoken, i get this:
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
I cant boot into the system so cant toggle oem unlocking. I was running LOS (9.0). any solutions?
Edit: if i try to flash anything from download mode, i get: "9 RU_Security_Fail zip from usb command in download mode"

Khizar Amin said:
Hey,
After a series of mess ups on my HTC-10, i am now stuck in bootloader mode, S-on with relocked. When i try to unlock my bootloader using flash unlocktoken, i get this:
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
I cant boot into the system so cant toggle oem unlocking. I was running LOS (9.0). any solutions?
Edit: if i try to flash anything from download mode, i get: "9 RU_Security_Fail zip from usb command in download mode"
Click to expand...
Click to collapse
Why didn't you answer me here
https://forum.xda-developers.com/ht...atch-error-t3894789/post78787393#post78787393
I tried to help you there but instead you wandered off and got yourself in a really bad situation. S-on and relocked......for heaven's sake why did you relock it, that's the dumbest thing ever and a 100% not needed for anything !!!
Maybe you can put your device back to stock if you find a ruu.exe that matches your original OS and firmware, but since you didn't followed my directions i have no clue where to start and frankly i am afraid you can't fix this anymore.