Strange message with almost every fastboot command - One (M9) Q&A, Help & Troubleshooting

I keep noticing this message every time I issue some sort of modifying fastboot command, doesnt matter if im using fastboot getvar all or flash unlock token etc etc, I always get this message at the beginning, does anyone know what it means or is it anything to be concerned about: (see below in bold)
C:\ADB>fastboot flash unlocktoken unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.011s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) unlock token check successfully
OKAY [ 0.030s]
finished. total time: 1.043s
Never seen this before with other HTCs ive unlocked etc, but regardless of that message, it seems to have done the job, I was just a little worried about if I should proceed to flash bigger files like rom's etc, I want to flash TWRP, root and then S-off so I can flash the stock 401 WWE rom.

Are you talking about the max dowload size or the KillSwitch message? (I'm asking because you highlighted the latter.)
The max download size equals around 762 MB. That's why you can use fastboot for flashing TWRP but not for flashing RUUs (as explained in the ReadMe thread).
The KillSwitch message on the other hand appears because you didn't activate OEM Unlock in the developer options of your phone. That's the FRP (Factory Reset Protection) Google introduced with android 5.1. It prevents you from unlocking the bootloader since that unlock triggers a factory reset.

Flippy498 said:
Are you talking about the max dowload size or the KillSwitch message? (I'm asking because you highlighted the latter.)
The max download size equals around 762 MB. That's why you can use fastboot for flashing TWRP but not for flashing RUUs (as explained in the ReadMe thread).
The KillSwitch message on the other hand appears because you didn't activate OEM Unlock in the developer options of your phone. That's the FRP (Factory Reset Protection) Google introduced with android 5.1. It prevents you from unlocking the bootloader since that unlock triggers a factory reset.
Click to expand...
Click to collapse
I was on about the killswitch message, however, OEM unlocking and USB debugging is activated in developer options along with unknown sources.

And your bootloader is unlocked now? That's more than strange. The message should only appear if OEM Unlock isn't activated.
Sent from my HTC One S using XDA Labs

Flippy498 said:
And your bootloader is unlocked now? That's more than strange. The message should only appear if OEM Unlock isn't activated.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Yes bootloader is unlocked, and phone reset itself as expected, all set back up again now, just need to root and s-off it, I was just concerned about that message.

Related

M9 Unlock Token Verify Fail?

Not new to the scene here, just getting back into it. My M9 is giving me trouble; I've been through all the threads Google knows about in English and other languages.
** This is a "One M9 Unlocked" GSM phone; not developer version or carrier-specific **
[KillSwitch] Last Byte is 0X01, enable unlock - I enabled the bootloader unlock option in developer settings.
Using Download mode, as this is the new correct way. fastboot devices works and get_identifier_token works.
I tried several unlock codes from HTCDev.
Tried rebooting and all combinations of rebooting + getting new code.
Tried HTCDev fastboot.exe and android platform tools fastboot.exe.
Tried cmd and powershell.
Tried different folder locations (desktop and C:\Android)
Note that every time I get_identifier_token, the token is different. I don't remember if that's normal.
I've used HTCDev to unlock many devices, never had problems.
Output of every attempt to flash unlocktoken:
Code:
C:\Android>fastboot.exe flash unlocktoken Unlock_code.bin
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.035s
What am I screwing up here?
xfinrodx said:
** This is a "One M9 Unlocked" GSM phone; not developer version or carrier-specific **
Click to expand...
Click to collapse
I am confused. Why are you trying to unlock a phone that is already unlocked?
Thanks for your question: It is the factory carrier unlocked version. It works with any GSM card without needing a carrier unlock code - however, the bootloader is still locked. Whereas it's nice to not be tied to a carrier, I'd also like to get involved with cyanogenmod again.
For whomever else finds themselves in this situation: Good luck, I have no idea what happened.
I tried and retried this process several times. Finally gave up in exasperation and tried later on a different machine because that makes no sense but why not... Here's my winning magic combination (that I already tried, but on a different machine)
Front panel USB port.
Complete HTCDev unlock procedure with caveats:
I used the Google Bootloader Interface driver; HTCSync has never been on this machine.
I used the Google platform tools fastboot application.
Everything else exactly as HTCDev prescribes.
Do this on two totally different machines; it might help to be exasperated the second time. Did literally nothing different... on to the roms now.

FAILED (remote: UnlockToken Verify Fail!!)

hi
i am trying to unlock the bootlaoder for my new htc m9
after i got the unloch_code, i receive this msg in cmd
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
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.038s
please help
what is missing ?
This does not belong in development.
@osamaxosama
In developer options, you have an option called OEM unlocking. This should be checked.
skodann said:
@osamaxosama
In developer options, you have an option called OEM unlocking. This should be checked.
Click to expand...
Click to collapse
i will check it and update this.
skodann said:
@osamaxosama
In developer options, you have an option called OEM unlocking. This should be checked.
Click to expand...
Click to collapse
didn't work
still the same, same msg also
i receive on my phone that download is 100%
and at the botoom of the screen " under flash "
it didn't take me to the bootloader next screen.
Pretty sure the token has to be obtained after OEM unlocking is checked, try a second token.
osamaxosama said:
didn't work
still the same, same msg also
i receive on my phone that download is 100%
and at the botoom of the screen " under flash "
it didn't take me to the bootloader next screen.
Click to expand...
Click to collapse
Activate the OEM unlock, obtain the unlock code.bin after that, make sure that you are using htc_fastboot, not other thing, and (I am not 100% sure, but other members can help) go into download mode, not into bootloader when you flash the unlock code.bin
Tirofog said:
Pretty sure the token has to be obtained after OEM unlocking is checked, try a second token.
Click to expand...
Click to collapse
i guess this might help, i am still using same token , the one i obtained before unlocking oem.
i'll try this
thanks
skodann said:
Activate the OEM unlock, obtain the unlock code.bin after that, make sure that you are using htc_fastboot, not other thing, and (I am not 100% sure, but other members can help) go into download mode, not into bootloader when you flash the unlock code.bin
Click to expand...
Click to collapse
dear
you mean i have to obtain the token when i am at fast boot not download mode ?
flashing is on downlaod mode yeah, but getting the token is from fastboot ?
Tirofog said:
Pretty sure the token has to be obtained after OEM unlocking is checked, try a second token.
Click to expand...
Click to collapse
didn't work, same msg
skodann said:
Activate the OEM unlock, obtain the unlock code.bin after that, make sure that you are using htc_fastboot, not other thing, and (I am not 100% sure, but other members can help) go into download mode, not into bootloader when you flash the unlock code.bin
Click to expand...
Click to collapse
i did this exactly. but to let you know, i couldn't get the token when on fastboot, but after entering download mode, i was able to get the token.
also, i tried to flash the token on fastboot, but didn't flash, only on download mode i was able to get the token and flash it.
on cmd i still get the same msg, but on my htc screen i see this " attached picture " " download 100% "under flash
ad everytime i press the power button, i see another " under flash " msg.
help please
osamaxosama said:
help please
Click to expand...
Click to collapse
What happens if you press the power button.. try adb to reboot recovery/bootloader??
solved
i tried on another pc.
the issue seemed to be from th sdk folder.
i tried 15 seconds installer, i knew it was the problem, because it runs from everywhere, i think it doesn't recognize flash commands or the file destination.
thank you all

unlocking bootloader help

i am getting this error please help
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.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: 1.059s
why you don't go to http://www.htcdev.com/bootloader to open it
I don't know if work or not cuz I not get the phone and never use htc before
Sent from my iPad using Tapatalk
double check you have entered your serial number etc correctly on the htc dev site, any mistakes will generate the wrong unlock code.
DinarQ8 said:
why you don't go to http://www.htcdev.com/bootloader to open it
I don't know if work or not cuz I not get the phone and never use htc before
Click to expand...
Click to collapse
That is the website I am getting my unlock, I am a long time HTC user and I have done this hundreds of times, the thing is just not working out for me this time, but thanks for trying to help
Doesnt HTC 10 also have option in developer options to block bootloader unlocking?
Here on mine M9
OEM unlocking
Allow the bootloader to be unlocked (unchecked by default)
alexp999 said:
double check you have entered your serial number etc correctly on the htc dev site, any mistakes will generate the wrong unlock code.
Click to expand...
Click to collapse
Will try again tomorrow...
I'm having the same problem. Allow unlocking is ticked
rampage101 said:
I'm having the same problem. Allow unlocking is ticked
Click to expand...
Click to collapse
Did you allow unlocking before you tried?Or after it failed u tried ticking it on?
Because if u allowed bootloader unlocking you need to generate new unlock token all over!
Before. I've tried several times, still can't get it
rampage101 said:
Before. I've tried several times, still can't get it
Click to expand...
Click to collapse
Well try contacting HTC support than.
Just got it to work. Not sure what exactly solved it. Did another reboot of the laptop, used Chrome instead of Microsoft Edge. Waterfox (Firefox) didn't work properly with HTC Dev, so not sure what was going on.
No OEM unlock on the Verizon 10 in developer settings
rampage101 said:
Just got it to work. Not sure what exactly solved it. Did another reboot of the laptop, used Chrome instead of Microsoft Edge. Waterfox (Firefox) didn't work properly with HTC Dev, so not sure what was going on.
Click to expand...
Click to collapse
not sure that was reason but used Microsoft edge and it worked Thanks!!!!!!!!!!!!!!
Surprisingly, I am running into this issue as well. I have done this several times before and never had this issue. I am doing it on Linux and I have done it from Linux before. The developer option for unlock is enabled.
I have tried several times now, with different browsers, and the same result.
Does anybody know how to get out of the download mode? I can't even reboot this device at this time. Holding power does not power off - fastboot reboot helps.
yes I was in the same boat. I had to generate 4 unlock.bin files till it finally accepted it.
Looks like 4th time is the charm... It finally did unlock it.
Power button and vol down held down for a while will reboot it. Also, "fastboot reboot" will do it too.
Sent from my HTC 2PS6200 using Tapatalk
JEANRIVERA said:
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.059s
Click to expand...
Click to collapse
I had the same thing happen to me. I rebooted the phone, went into developer settings to verify OEM Unlocking was checked (it was). Powered off the phone, held down volume down, took it into download mode and tried again. This time it worked. I only ever got one Unlock_code.bin file, so I know it was good even when it was failing.
Make sure you are including the <<< >>> lines, both above and below? Off the top of my head I cannot remember what they say, but there are lines of texts before the code begins and after it ends.
Same here, it was the third time for me, but I did notice each time I'd run the get_identifier_token, that the token would come out differently each time. Eventually submitting through Edge got me the proper unlock.bin
First time Firefox said invalid error
Second Chrome said success, but unlock bin did not work
Third used edge, Success, unlock bin worked.
This was not this much of a pain on both Motorola Moto X and Moto MAXX

Error while unlocking phone

I just bought an HTC One M9 - Developer edition. I wanted to unlock it and followed all of the directions from the HTCDev site. The only difference was that I used the fastboot program from my Android Studios instead of their fastboot zip. When I run the command fastboot flash unlocktoken Unlock_code.bin, I get an unusual response:
C:\Users\Ben-Desktop\AppData\Local\Android\sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.005s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) Device is unlocked
OKAY [ 0.013s]
finished. total time: 0.020s
Click to expand...
Click to collapse
When this happens I am stuck on a screen that says "download 100%" and "Start downloading" highlighted in blue. The HTCDev site says that I should get a pop-up that says whether I want to unlock the bootloader, but I just get stuck here. I know how to get out of this screen using the up arrow and power button. What I'm trying to figure out is how to actually unlock my phone.
Any thoughts?
P.S. It may be worth noting that I fully updated my phone beforehand so I don't know if its setup to work for an easier version, but fails for 6.0
ganeran said:
I just bought an HTC One M9 - Developer edition. I wanted to unlock it and followed all of the directions from the HTCDev site. The only difference was that I used the fastboot program from my Android Studios instead of their fastboot zip. When I run the command fastboot flash unlocktoken Unlock_code.bin, I get an unusual response:
When this happens I am stuck on a screen that says "download 100%" and "Start downloading" highlighted in blue. The HTCDev site says that I should get a pop-up that says whether I want to unlock the bootloader, but I just get stuck here. I know how to get out of this screen using the up arrow and power button. What I'm trying to figure out is how to actually unlock my phone.
Any thoughts?
P.S. It may be worth noting that I fully updated my phone beforehand so I don't know if its setup to work for an easier version, but fails for 6.0
Click to expand...
Click to collapse
If u got a dev edition it's already unlocked.
It says u are unlocked.
If not, check the oem unlock in the developer settings.
Good luck!
Fain11 said:
If u got a dev edition it's already unlocked.
It says u are unlocked.
If not, check the oem unlock in the developer settings.
Good luck!
Click to expand...
Click to collapse
Okay, I guess I'm trying to turn the machine to S-OFF then. I still don't have root access (or at least that's what titanium backup says). Do you know of a place with instructions for that?
ganeran said:
Okay, I guess I'm trying to turn the machine to S-OFF then. I still don't have root access (or at least that's what titanium backup says). Do you know of a place with instructions for that?
Click to expand...
Click to collapse
Start reading here:
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133

Security status stuck at S-DBG

Hello everyone,
(was trying to ask this questions to dev thread but my "clearance" is not high enough
I recently played with my HTC10 - unlocked bootloader, did S-OFF, changed CID, etc - well, all that normal usual things
At some point later I decided to go back so I removed root, changed CID back and was trying to put security back to S-OFF when I accidentally used command
fastboot oem writesecureflag 2 (instead of 3).
At the next boot the phone showed me some strange window with some Chinese text, asking me for a password. I put 0000 and the phone told me that the password was Ok, but my data could not be decrypted. It formated everything and that was Ok, but now my security status says "S-DBG".
Now I can't change CID or MID, when I try it tells me:
[email protected]:~/phone# fastboot oem writecid HTC__621
...
FAILED (remote: WRITE CID PERMISSION ERROR)
finished. total time: 0.022s
If I try to change security level to anything, it gives me:
[email protected]:/home/alexr# fastboot oem writesecureflag 0
...
(bootloader) HTC KEY CARD VERSION: 7
FAILED (remote: PERMISSION DENY (NOT_FIND_SMART_IO))
finished. total time: 0.013s
[email protected]:/home/alexr# fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_PASS (0)
(bootloader) Partition verify pass
FAILED (remote: PERMISSION DENY (NOT_FIND_SMART_IO))
finished. total time: 0.974s
[email protected]:/home/alexr#
I tried to use SunShine to reset that but the program told me my phone already had "S-OFF" whereas in fact it does not
Does anybody know what that "S-DBG" mean and more importantly - how to go back to either S-OFF or S-ON??
Thank you!
@beaups
He is one of the Sunshine devs and I'm mentioning him here so that he sees this post. No need to PM him
AlexFlooter said:
Hello everyone,
(was trying to ask this questions to dev thread but my "clearance" is not high enough
I recently played with my HTC10 - unlocked bootloader, did S-OFF, changed CID, etc - well, all that normal usual things
At some point later I decided to go back so I removed root, changed CID back and was trying to put security back to S-OFF when I accidentally used command
fastboot oem writesecureflag 2 (instead of 3).
...
Click to expand...
Click to collapse
I assume you are the same user that opened a support ticket with us. SunShine wasn't written to work with devices in this state. If you want to change your security status you'll need to use another (hardware) solution.
--beaups
beaups said:
I assume you are the same user that opened a support ticket with us. SunShine wasn't written to work with devices in this state. If you want to change your security status you'll need to use another (hardware) solution.
--beaups
Click to expand...
Click to collapse
Yeap, it was me.
Ok, thank you for the answer

Categories

Resources