i've been entering the correct token identifier on htcdev and it keeps telling me it's the wrong length. i've tried the instructions, adding "please cut the following" to the top, and with and without spaces in front of each line. what do i do next?
EDIT: nevermind. it worked on about the 8th try. i just kept pasting the same thing and yelling at it in my head.
Related
I have searched but couldn't find anyone with the exact same problem as mine.
This is the message I got from HTCDev.com
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 173.
Error Reason: Check Rule Fail with exception.
I have all the requirements (HTC Drivers, adb and fastboot files, JRE) and I am 100% sure I copied the code correctly as I have helped friends unlock their HTC phones before.
Also its definitely not the carrier disallowing me to unlock.
Can anyone help me figure out what's wrong here?
Servers down !?
http://www.isitdownrightnow.com/htcdev.com.html
More info here
Help.
I need help unlocking my bootloader, I can type adb devices while the device is powered on & my unique I.D number comes up in cmd, but whenever I boot into bootloader, the device doesn't come up in cmd what gives? All my drivers are up to date & installed correctly, though I get an MTP driver issue, could that be causing this? This is my second M8 (T-Mobile this time), first one was the dev edition s-off & converted to GPe.
You never said what command you used in the bootloader ?
It's :
Fastboot devices (not adb devices)
adb devices for adb wile phone is booted in OS
fastboot devices in fastboot/hboot mode
Oops never mind, another thing - I keep getting an error while trying to submit my code to HTC Dev after getting the identifier token.
EternalAndroid said:
Oops never mind, another thing - I keep getting an error while trying to submit my code to HTC Dev after getting the identifier token.
Click to expand...
Click to collapse
Please state the error if you would [emoji12]
After reading the opening post here, I get the impression that the code you get for the token is more an issue on your side(You messed up somewhere).
That being said, it doesn't help alot saying "I keep getting an error" but you don't tell us what the error is.
Taking a wild guess, it has to do with the actual token. Make sure you don't have any spaces in the selection of the code. Select it with the <<<<< >>>>> included. Do NOT include the <bootloader> parts next to it and again make sure there are NO spaces in the selection.
Comparison pictures of the code how it SHOULD and SHOULD NOT look.
If that is not your problem then give more information as to the error you're receiving. Doesn't help to phone an IT dept for help and you don't tell them what the problem is either, does it? Same here...
jball said:
Please state the error if you would [emoji12]
Click to expand...
Click to collapse
Sorry guys just frustrated & keep forgetting, "error reason token decryption fail (cannot generate result)."
But I think I figured out my issue, so my computer's internet is off right now & I'm trying to do all this from my N5. I'm typing the code on my phone, reading it letter for letter, number for number.
BerndM14 said:
After reading the opening post here, I get the impression that the code you get for the token is more an issue on your side(You messed up somewhere).
That being said, it doesn't help alot saying "I keep getting an error" but you don't tell us what the error is.
Taking a wild guess, it has to do with the actual token. Make sure you don't have any spaces in the selection of the code. Select it with the <<<<< >>>>> included. Do NOT include the <bootloader> parts next to it and again make sure there are NO spaces in the selection.
Comparison pictures of the code how it SHOULD and SHOULD NOT look.
If that is not your problem then give more information as to the error you're receiving. Doesn't help to phone an IT dept for help and you don't tell them what the problem is either, does it? Same here...
Click to expand...
Click to collapse
Oh wow I see
Copy the text to notepad. Copy it to your phone. Open it in your phone using any file manager. Copy and paste .
Hiya guys,
I've been pulling my hair out as to why sometimes (ahem, most of the time when I really really need it) the unlocktoken.bin doesn't flash successfully, when trying to do a new token from HTC. Everything seems fine from there end, it spits me out out a key, but I kept getting that darn FAILED (remote: UnlockToken Verify Fail!!) error.....
After ages of slowly going through the process, pulling apart each step meticiously, I found that word wrap selection was turned on in my command prompt. I have a fresh install on this PC, so it's a default setting now, where I don't think it used to be enabled....
To get here, right click the top bar of the command prompt window, and click properties...and make sure the "enable line wrapping selection" option is UNTICKED. I had a picture handy but I can't post outside links due to a lack of posts here, sorry guys.
I think this adds hidden whitespaces somewhere in the copy paste buffer, and throws off HTC's keygen. Everything worked perfectly after disabling that option, after hours of trying to recover my phone...
Hope this helps someone!
if you're reading this thread, you're likely tearing out your hair in apt frustration because you're just trying to unlock your bootloader and its a no-go. If you're coming from a One M7 or M8, just be aware that HTC's switched up the game since then. Also, everything mentioned below is indirectly applicable to HTC 10 owners as well.
Writing up this thread as that was me, and I scoured pretty much every link pulled from variations of google keyword searches; and as I was successful in finally unlocking the damn thing, here is my braindump:
[in no particular order], and YMMV, much of this is a compilation of things that saved other people experiencing such errors, every rock unturned is a rock unturned.
There's a new "download mode"---the ol' white backgrounded fastboot that you used to know and love, that's sidelined, you must run fastboot on the black backgrounded Download mode format.
you CANNOT use the standard Google/Android SDK's fastboot. I know, wtf. you MUST use HTC's fastboot (the one they provide on HTCdev.com; note that their's is missing an ADB, you can pluck the ADB portion from the standard Android SDK).
If you are experiencing a fail, I recommend immediately wiping the whole device (reset all data), and then starting anew: from there, be sure to: --get Developer, and check the: allow OEM unlocking + allow USB debugging boxes. also, while you're in settings, might as well: increase the screen off time, put 'no lock screen', allow unknown sources installations, etc. then after all that's set, then try and run the fastboot.
for whatever reason, the Gmail web client might not work happily with your unlock_code.bin that you get sent---and/or you're getting weird HTCdev login errors even though you put in the right password---eff that noise; start anew: create a new account, don't use a Gmail email (I used a live.com email to get the unlock_code.bin that ended up being the golden goose egg). yeah, for reasons unknown, there's some RNGmagic mojo crap going on here, so if you're experiencing errors, there's really nothing to lose by going new routes.
don't use Chrome to go to the HTCdev website; I used Edge (no deliberate Microsoft plug or anything here, fyi)
the HTCdev website won't accept your fastboot paste of oem unlocking info if its not the right number of characters, I tested this, so that's not the problem if you thought it was; I recommend opening up a Notepad and just copying and pasting it there and then double-checking that, and then pasting it onto the HTCdev site.
Dont mean to burst your bubble.. Thats all old news.
Beamed in by telepathy.
title. i keep getting errors saying Failed to write to pipe followed with some letters and numbers