Yesterday I was playing around and almost bricked my phone, had to do a RUU restore and for this I had to Relock the bootloader, after bringing my phone back to life and trying to unlock it again I just can't achieve it.
I follow the same instructions from HTC Dev, used the same code and got an error, then got a new code and I get this error:
Code:
C:\fastboot (android root)>fastboot flash unlocktocken Unlock_code.bin
sending 'unlocktocken' (0 KB)...
OKAY [ 0.022s]
writing 'unlocktocken'...
FAILED (remote: not allowed)
finished. total time: 0.229s
Any ideas?
Thanks!
Try spelling "token" correctly not tocken
sent from my One X using xda venom premium
bogfather said:
Try spelling "token" correctly not tocken
Click to expand...
Click to collapse
I've never been so ashamed in my entire life.
Thanks hahaha
Related
when i get to the last step on htcdev.com to unlock the bootloader. i type "fastboot flash unlocktoken Unlock_code.bin" but when i got back to my phone i dont have the disclaimer to unlock the phone. im following directions correctly and everything says on computer that it went through. any ideas??
C:\android>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ -0.000s]
finished. total time: 0.156s
i get this but nothing on my phone....
Same problem.
This is also happening to me. I unlocked my own Evo 3D with this method and had no problems, but ran into this same issue trying to unlock my son's, which he just got for Christmas. I've confirmed Hboot version is 1.5. Any help with this would be much appreciated.
*Update* Fixed!
I did some research and found the solution! I've confirmed that this works for me. Basically, you have to install the old RUU version 2.08.651.2 because something in 2.08.651.3 borks the HTC unlock. Here is the original post I found:
http://htcevohacks.com/htc-evo-3d-cheat-sheet/#comment-31513
...and here is a link to a thread with the RUU 2.08.651.2 download:
http://forum.xda-developers.com/showthread.php?t=1225737
OK this is not the answer but I can confirm that htc dev unlocking method is working perfectly for hboot 1.53.0007
Hello!
I am looking for help with rooting my HTC EVO 3D phone (HBOOT 1.5 with software 2.08.651.3), which went successfully all way through step 12 per HTC DEV unlock instructions, however, as described in step 13, the phone has never prompted for YES/NO to confirm unlock. I am getting the "FAILED (status read failed (Too many links))" error pretty much for every fastboot command. The good thing is that phone boots and works properly otherwise.
Factory Reset or Removing battery did not help.
Could someone advice on how to clear this error and successfully root the phone from this point.
Below is the log of commandes:
1. C:\rootevo3dnew>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
************************************
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.065s]
finished. total time: 0.066s
2. Got email from HTC DEV with UNLOCK_CODE.BIN file.
3. C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.159s
But as described in STEP 13, PHONE has never asked to confirm UNLOCK!
NOW I AM GETTING:
C:\rootevo3dnew>fastboot oem get_identifier_token
...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.005s
What hboot version are you on?
Sent from my PG86100 using XDA App
it is HBOOT 1.5 with software 2.08.651.3.
I can't link as I'm on the phone bit if you go to the cdma development section for the EVO 3d there is a few good guides to walk you through rooting and flashing with 1.5 you will still have s-on but be able to flash. My opinion would be go with twrp its in the stickies
Sent from my PG86100 using XDA App
MTEEZEY,
Thank you for the advice. Found post advising to run the 2.08 RUU and then retry the HTC unlock. Worked for me!
http://forum.xda-developers.com/showthread.php?t=1239821
Best Regards,
RangeMaster
Nice. Glad you got. Now on to the fun stuff. LOL
Sent from my PG86100 using XDA App
HTC Driod Incredible 2 with 2.3.4
Can not downgrade the system to 0097 instead of the 0098
failed message
FAILED (remote: 43 unknown fail
(before root)
failed message
FAILED (remote: 99 unknown fail
(after root)
HBOOT still 0098
s-on still
orginal message
C:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
... OKAY [ 0.156s]
finished. total time: 0.172s
C:\vwhk-12102011-c>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 0.234s]
finished. total time: 0.234s
C:\vwhk-12102011-c>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.
605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
sending 'zip' (292817 KB)... OKAY [ 50.188s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 55.969s
C:\vwhk-12102011-c>fastboot reboot
rebooting...
finished. total time: 0.156s
C:\vwhk-12102011-c>
pls help
If you already have Fastboot enabled on your computer then you need to make sure Fastboot is enabled via Bootloader.
You can test this by rebooting into Bootloader, enabling Fastboot, and then typing into your console
fastboot devices
If your device shows up you are good to go.
Then reboot into system and start attn script. It works a charm!
Oh, also, make sure the proper boot image is located within your ADB environment (unless you have a global setup)
Good luck.
Did you follow this:
http://forum.xda-developers.com/showthread.php?t=1298990
I just used it myself. The only problem I had was not putting usb in debug mode.
Once I did that it work flawlessly.
I was doing this this weekend and ran into problems because I had unlocked the bootloader using HTCdev. I was also using a long USB cable and ran into what I think was signal degradation causing some commands in that script to fail.
Once I relocked the bootloader and switched to the stock cable that came with the phone the downgrade script worked perfectly.
phufford said:
I was doing this this weekend and ran into problems because I had unlocked the bootloader using HTCdev. I was also using a long USB cable and ran into what I think was signal degradation causing some commands in that script to fail.
Once I relocked the bootloader and switched to the stock cable that came with the phone the downgrade script worked perfectly.
Click to expand...
Click to collapse
U screwed yourself with HTC unlock I believe.. relock it then try again
Sent from my Incredible 2 using Tapatalk 2
faehsemc said:
U screwed yourself with HTC unlock I believe.. relock it then try again
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
U would be correct there sir. Relock the bootloader and then run the downgrade tool.
Sent from my Incredible 2 using XDA
+1 on the relocking tip, relock and then everything will work, revolution tool relocks it if you were wondering
I ran into the same issue and relocked the bootloader with "fastboot oem lock" command and then i was able to downgrade properly. Leasson learned. Thanks everybody for their replies.
if all fails, just copy RUU...zip file to sdcard, rename to PG32IMG.zip and do upgrade. It will work without problems
2 yrs to late haha
Sent from my One using xda app-developers app
chillybean said:
2 yrs to late haha
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
There are a lot of noobs lol
Sent from my VS840 4G using Tapatalk
I got back my phone yesterday from HTC and the device sais "Locked" rather than "Relocked".
I tried to unlock my phone again, but I can't.
If I type fastboot devices I get response that my phone is connected, however if I type "fastboot oem get_identifier_token" or anything else I get an error:
E:\androidflash\Fastboot>fastboot oem get_identifier_token
... FAILED (remote: (00000008))
finished. total time: 0.002s
Click to expand...
Click to collapse
or
E:\androidflash\Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.009s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.220s
Click to expand...
Click to collapse
Can anyone help me?
Sil
Don't laugh, but try plugging into a different USB. It could be that simple.
requiem11 said:
Don't laugh, but try plugging into a different USB. It could be that simple.
Click to expand...
Click to collapse
Oh wow, it really worked. Thanks!
Silgrond said:
Oh wow, it really worked. Thanks!
Click to expand...
Click to collapse
I know, crazy. Glad it worked out.
hello,
I own a 32 GB HOX and I need to completly stocked my phone using the RUU
I just dont know which one I have to choose
my CID is : HTC_044
Thank you !
Stop making threads with different stories. Its confusing.
Who wins a hox that does not work. Return it and get a new one !!!
http://forum.xda-developers.com/showthread.php?t=2374320
Mr Hofs said:
Stop making threads with different stories. Its confusing.
Who wins a hox that does not work. Return it and get a new one !!!
http://forum.xda-developers.com/showthread.php?t=2374320
Click to expand...
Click to collapse
I meant 'own'
I just noticed it .
That clears things up !
Fastboot getvar version-main
That will tell you the number of the ruu you need
Mr Hofs said:
That clears things up !
Fastboot getvar version-main
That will tell you the number of the ruu you need
Click to expand...
Click to collapse
Ok than
I already used the right RUU and Run it
Now after using in the RUU the HOX immediately boots into bootloader
I tried to flash a new boot with no success
C:\Users\Shavit\Desktop\One_X_All-In-One_Kit_v2.3\Data>fastboot flash boot boot.
img
sending 'boot' (5200 KB)...
OKAY [ 0.651s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.854s
Click to expand...
Click to collapse
But what is now exactly your goal, i see so many different things everywhere....
But to answer this question :
A boot.img (the kernel) can't be flashed with a locked/relocked bootloader, after you ran the ruu your bootloader is either locked or relocked and you need to unlock it first to be able to flash anything !
Mr Hofs said:
But what is now exactly your goal, i see so many different things everywhere....
But to answer this question :
A boot.img (the kernel) can't be flashed with a locked/relocked bootloader, after you ran the ruu your bootloader is either locked or relocked and you need to unlock it first to be able to flash anything !
Click to expand...
Click to collapse
First of all thank you !
my goal is just to be able to use the DAM PHONE
Currently my bootloader is LOCKED and I can't manage to unlock it
C:\Users\Shavit\Desktop\One_X_All-In-One_Kit_v2.3\Data>fastboot flash unlocktoke
n Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.130s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Unknown error))
finished. total time: 4.747s
Click to expand...
Click to collapse
THis happens after choosing the 'YES' option in the HOX
And it stays relocked after a reboot ?
Then get a new code at the HTC dev site ....maybe that helps
Mr Hofs said:
And it stays relocked after a reboot ?
Then get a new code at the HTC dev site ....maybe that helps
Click to expand...
Click to collapse
Even after a reboot it stays ***LOCKED***
I tried to get a new code
A different error this time
C:\Users\Shavit\Desktop\One_X_All-In-One_Kit_v2.3\Data>fastboot flash unlocktoke
n Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.011s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 3.501s
Click to expand...
Click to collapse
I tried agagin with another Unlock_Code.bin and I get a different every time
FAILED (status read failed (Unknown error))
FAILED (status read failed (Too many links))
every time a different one
Any help with that ?
Well actually no ! If the token get flashed to the phone and you see the unlock screen its all correct. If it stays unlocked like yours do then i can't do anything unfortunately