Unlocking bootloader HTC Tattoo -Spain - Upgrading, Modifying and Unlocking

I've an HTC Tattoo and I'm trying to unlock the bootloader with the HTCdev bootloader unlocking. I do everything they say to do, but when it's time to put this command:
fastboot oem get_identifier_token
I get this error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
I've removed and inserted the battery lots of times, reinstaled the drivers, searched information, but I couldn't find any solution.
I've S-On. I suppose it's not a trouble.
Thank you in advance!, you'll help me a lot!

I have the same issue with my HTC desire Z.
It shows following error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
Is there another way to find identification token?

Related

HTC EVO 3D - fastboot TOO MANY LINKS Error

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

[Q] HELP! Bricked One X - Bootloader refuses to be unlocked!

My HTC One X's bootloader refuses to be unlocked. No matter how many times I get the Unlock_code.bin, the result is the same. I see the screen prompting you to unlock, the phone restarts, but the bootloader is still locked! It always says "FAILED (status read failed (Too many links))", as shown in the "code" below, and when I try to go into recovery, I just end up in the bootloader again.
I've tried rebooting, powering off, and unlocking the bootloader at least 20 times.
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
D:\HTC One X>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 2C6261A412B90AF806C0BDD95F2A1CB2
(bootloader) 75CAF463BABBCA2DAD2B1EBDAFF1CAB4
(bootloader) CB757550B386C7148C7F1F61F35FB5AF
(bootloader) 0D4B4EF1473822FE61C44AF698F6F2FD
(bootloader) EEEF310F863F70FCD8747CDFDDFC3767
(bootloader) E80A8A002299933710DFC2B88401C088
(bootloader) 971871160D1601CBCB357046D3B4300A
(bootloader) 2A4E22919F7721BA2C1C51EC5EE44723
(bootloader) 30D0BF14E712C66AC7A9482E531CF842
(bootloader) B62A495E488E65BAA00DE50EC3421C76
(bootloader) 9345B2D69CFD147B259839CBE4616243
(bootloader) AFCFD491EA624DDD430F70938F049671
(bootloader) 5DB1E6AB6EF47F5610CFE6BE2494FDC8
(bootloader) A148E48F09BC14F3E826DF09283C2B13
(bootloader) 7872CC6058FBED6FEB027E5504AF3F9B
(bootloader) B5A52E18A91329CB37E2D815888D5E97
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.234s]
finished. total time: 0.234s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 4.263s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.095s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 3.437s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.091s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 1.998s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 2.124s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 3.677s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.090s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 1.659s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 7.561s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 3.676s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 2.391s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 2.893s
D:\HTC One X>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) A1357F49A66FA2B5F2BD2240BE3A32CB
(bootloader) 7F826B1092B683A0F2CAD514167CB06B
(bootloader) 725F76699BDE34D14D85FAB8F5C14AA1
(bootloader) 1D9EFB62716F04A9E313827E39C3FC48
(bootloader) 64C1F57F10D920363085DB0B1B3DCCC0
(bootloader) 7CB29BA5929B32FB0EE18D89AC262B11
(bootloader) 4E3DE75ED63222216BBFEBBFA1AE496C
(bootloader) E8B7FD515A4B33E9402138E6FD7066AE
(bootloader) 6DAC913C4C0DD50A1C12301D4D246CD8
(bootloader) 9DADD21DDB4601F04B0445DE92F2403B
(bootloader) A7972080B6AAA59DFFA01735634C45CF
(bootloader) B7060CE776C431A8504B84666CC9E11F
(bootloader) 6082610118D4A260E42D4CF6DBA3460C
(bootloader) C4D011E3AAFABAA7FFC90BF58B833621
(bootloader) 99FAD9FE4E48B5F4BA91C2EF5311F8E5
(bootloader) 82E78B2345D8EC9A207EB9CAB358C119
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.326s]
finished. total time: 0.326s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.014s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 4.279s
D:\HTC One X>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 59E7825FF98683D67F3338CFB7E13290
(bootloader) 5280E10892C14C9FF40FEB5E144A549C
(bootloader) 61047CB4E62D463D822CBD37A36AFEE7
(bootloader) D87A1DD345F3E2D2D23B804D715BFABB
(bootloader) 68EA61C9F9F073C2D0857D513D2632A6
(bootloader) 398D11246FF704DA2FF08B06C529EC5F
(bootloader) CE7B359C6430D37ED1CFDAE949448075
(bootloader) 7D7AA0E0CFD0C935574BABD45A805BC3
(bootloader) 5494A7DF083C20E8A57FAACD25932F71
(bootloader) 8B22666946FEFCF8E1C592CC3E73DCE9
(bootloader) 12C38C6622BC24FD5DBFEB83C18D1B88
(bootloader) 5CD68044DB72958F27FB16286C0E75C0
(bootloader) 2BE0A60B592A6B545EBFBC47531C9FC9
(bootloader) 6026E6CAB792205B2469EBD90C71CAD5
(bootloader) 453CDAF0A0E59994C1AFBEB4E398B57C
(bootloader) CBAEB79C62FCDE59D28CF767E4FC3F1B
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.321s]
finished. total time: 0.322s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.068s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 4.570s
D:\HTC One X>
Please help!!
UPDATE: The HTC One X is now stuck in APX mode. I've installed NVFlash drivers and got the NVFlash tool, but executing "nvflash --sync" gets me this:
Code:
D:\HTC One X>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
D:\HTC One X>
The too many links error is normal.
When you flash the unlock token and the unlock prompt appears
You are pressing volume up to confirm yes then pressing power button?
And also was you unlocked before then the phone magically became locked again?
Sent from my HTC One X using xda app-developers app
Try a different cable, too. I have a USB cable that's quite long, and I can't flash anything with it and get the same error. Tried a different, shorter one and it was all good.
Harrysoon said:
Try a different cable, too. I have a USB cable that's quite long, and I can't flash anything with it and get the same error. Tried a different, shorter one and it was all good.
Click to expand...
Click to collapse
he is not receiving any error, as i previously said (too many links) is normal
the important line is the one above it "(bootloader) unlock token check successfully"
which shows that the unlock token was flashed and checked successfully
there are 2 likely reasons behind it
1. the op has not pressed volume up before pressing power which he needs to do to confirm that he wants to unlock
2. his device has a hardware failure which prevents the bootloader from unlocking (this is quite rare and i have only seen cases of it happening with already unlocked bootloaders magically becoming locked again, then its impossible to re-unlock it)
bagofcrap24 said:
he is not receiving any error, as i previously said (too many links) is normal
the important line is the one above it "(bootloader) unlock token check successfully"
which shows that the unlock token was flashed and checked successfully
there are 2 likely reasons behind it
1. the op has not pressed volume up before pressing power which he needs to do to confirm that he wants to unlock
2. his device has a hardware failure which prevents the bootloader from unlocking (this is quite rare and i have only seen cases of it happening with already unlocked bootloaders magically becoming locked again, then its impossible to re-unlock it)
Click to expand...
Click to collapse
I have pressed volume up before pressing power, confirming that I want to unlock. I'm pretty sure it wasn't unlocked before, thus needing to be unlocked.
UPDATE: The HTC One X is now stuck in APX mode. I've installed NVFlash drivers and got the NVFlash tool, but executing "nvflash --sync" gets me this:
Code:
D:\HTC One X>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
D:\HTC One X>
APX is a brick. You need a new mainboard. There is no 100% solution for this as of now. If you get out of apx it probably won't be long before it kicks back in
Mr Hofs said:
APX is a brick. You need a new mainboard. There is no 100% solution for this as of now. If you get out of apx it probably won't be long before it kicks back in
Click to expand...
Click to collapse
Thanks for letting me know. Now I don't have to try anymore, because now I know it would become wasted effort. I will send it to HTC, see if they can get me a replacement.
So it was the second. Have yet to see it happen on a boot loader that had not yet been unlocked but i suppose most of xda posters will already have had theirs unlocked
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
So it was the second. Have yet to see it happen on a boot loader that had not yet been unlocked but i suppose most of xda posters will already have had theirs unlocked
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yep
It's still in APX mode...
Just knowing that there is still a slim chance of saving it is KILLING ME!!
I'm having the same problem trying to re-unlock my boot loader. If press up then power it reboots the phone?? Should I have HBOOT, REBOOT, REBOOTBOOTLOADER OR POWERDOWN highlighted before pressing up then power?
vantt1 said:
Yep
It's still in APX mode...
Just knowing that there is still a slim chance of saving it is KILLING ME!!
Click to expand...
Click to collapse
i have the same problem, but before my phone was ulocked, then it became locked magically and now i'm stuck in bootloader with this issue too, howerver i'll return it to htc
I have the same proplem
first my bootloader change from unlocked to locked
second my htc goes to apx and stuck at there
after 3 months my hox work and out of apx but with same proplem locked bootloader ?
what can i do ?
nothing at all as you can see
please any idea to fix this problem ...
ahmedaljaf said:
please any idea to fix this problem ...
Click to expand...
Click to collapse
Did you ever resolve this issue, I have the same problem and have been told by the HTC repair centre (not HTC) that it is a software fault but they will not repair/replace as its out of warantee. The only way of resolving it (as told by them) is to have a new motherboard . I am waiting to get it back and then will decide on my next course of action.
I am pretty [email protected] off as this is no fault of my own and have never bricked a device in my life, let alone through normal use!!
I had orginally unlocked the bootloader, relocked it but it is now showing locked rather than re-locked.
I don't mind openning it up and direct flashing if this is possible!
If it says locked instead of relocked then i think you don't have to worry about warranty, if it still applies within the warranty period (2 years EU).
vantt1 said:
My HTC One X's bootloader refuses to be unlocked. No matter how many times I get the Unlock_code.bin, the result is the same. I see the screen prompting you to unlock, the phone restarts, but the bootloader is still locked! It always says "FAILED (status read failed (Too many links))", as shown in the "code" below, and when I try to go into recovery, I just end up in the bootloader again.
I've tried rebooting, powering off, and unlocking the bootloader at least 20 times.
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
D:\HTC One X>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 2C6261A412B90AF806C0BDD95F2A1CB2
(bootloader) 75CAF463BABBCA2DAD2B1EBDAFF1CAB4
(bootloader) CB757550B386C7148C7F1F61F35FB5AF
(bootloader) 0D4B4EF1473822FE61C44AF698F6F2FD
(bootloader) EEEF310F863F70FCD8747CDFDDFC3767
(bootloader) E80A8A002299933710DFC2B88401C088
(bootloader) 971871160D1601CBCB357046D3B4300A
(bootloader) 2A4E22919F7721BA2C1C51EC5EE44723
(bootloader) 30D0BF14E712C66AC7A9482E531CF842
(bootloader) B62A495E488E65BAA00DE50EC3421C76
(bootloader) 9345B2D69CFD147B259839CBE4616243
(bootloader) AFCFD491EA624DDD430F70938F049671
(bootloader) 5DB1E6AB6EF47F5610CFE6BE2494FDC8
(bootloader) A148E48F09BC14F3E826DF09283C2B13
(bootloader) 7872CC6058FBED6FEB027E5504AF3F9B
(bootloader) B5A52E18A91329CB37E2D815888D5E97
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.234s]
finished. total time: 0.234s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 4.263s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.095s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 3.437s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.091s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 1.998s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 2.124s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 3.677s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.090s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 1.659s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 7.561s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 3.676s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 2.391s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 2.893s
D:\HTC One X>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) A1357F49A66FA2B5F2BD2240BE3A32CB
(bootloader) 7F826B1092B683A0F2CAD514167CB06B
(bootloader) 725F76699BDE34D14D85FAB8F5C14AA1
(bootloader) 1D9EFB62716F04A9E313827E39C3FC48
(bootloader) 64C1F57F10D920363085DB0B1B3DCCC0
(bootloader) 7CB29BA5929B32FB0EE18D89AC262B11
(bootloader) 4E3DE75ED63222216BBFEBBFA1AE496C
(bootloader) E8B7FD515A4B33E9402138E6FD7066AE
(bootloader) 6DAC913C4C0DD50A1C12301D4D246CD8
(bootloader) 9DADD21DDB4601F04B0445DE92F2403B
(bootloader) A7972080B6AAA59DFFA01735634C45CF
(bootloader) B7060CE776C431A8504B84666CC9E11F
(bootloader) 6082610118D4A260E42D4CF6DBA3460C
(bootloader) C4D011E3AAFABAA7FFC90BF58B833621
(bootloader) 99FAD9FE4E48B5F4BA91C2EF5311F8E5
(bootloader) 82E78B2345D8EC9A207EB9CAB358C119
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.326s]
finished. total time: 0.326s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.014s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 4.279s
D:\HTC One X>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 59E7825FF98683D67F3338CFB7E13290
(bootloader) 5280E10892C14C9FF40FEB5E144A549C
(bootloader) 61047CB4E62D463D822CBD37A36AFEE7
(bootloader) D87A1DD345F3E2D2D23B804D715BFABB
(bootloader) 68EA61C9F9F073C2D0857D513D2632A6
(bootloader) 398D11246FF704DA2FF08B06C529EC5F
(bootloader) CE7B359C6430D37ED1CFDAE949448075
(bootloader) 7D7AA0E0CFD0C935574BABD45A805BC3
(bootloader) 5494A7DF083C20E8A57FAACD25932F71
(bootloader) 8B22666946FEFCF8E1C592CC3E73DCE9
(bootloader) 12C38C6622BC24FD5DBFEB83C18D1B88
(bootloader) 5CD68044DB72958F27FB16286C0E75C0
(bootloader) 2BE0A60B592A6B545EBFBC47531C9FC9
(bootloader) 6026E6CAB792205B2469EBD90C71CAD5
(bootloader) 453CDAF0A0E59994C1AFBEB4E398B57C
(bootloader) CBAEB79C62FCDE59D28CF767E4FC3F1B
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.321s]
finished. total time: 0.322s
D:\HTC One X>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.068s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 4.570s
D:\HTC One X>
Please help!!
UPDATE: The HTC One X is now stuck in APX mode. I've installed NVFlash drivers and got the NVFlash tool, but executing "nvflash --sync" gets me this:
Code:
D:\HTC One X>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
D:\HTC One X>
Click to expand...
Click to collapse
Dude Please make sure your only using:
<<<< Identifier Token Start >>>>
A1357F49A66FA2B5F2BD2240BE3A32CB
7F826B1092B683A0F2CAD514167CB06B
725F76699BDE34D14D85FAB8F5C14AA1
1D9EFB62716F04A9E313827E39C3FC48
64C1F57F10D920363085DB0B1B3DCCC0
7CB29BA5929B32FB0EE18D89AC262B11
4E3DE75ED63222216BBFEBBFA1AE496C
E8B7FD515A4B33E9402138E6FD7066AE
6DAC913C4C0DD50A1C12301D4D246CD8
9DADD21DDB4601F04B0445DE92F2403B
A7972080B6AAA59DFFA01735634C45CF
(B7060CE776C431A8504B84666CC9E11F
6082610118D4A260E42D4CF6DBA3460C
C4D011E3AAFABAA7FFC90BF58B833621
99FAD9FE4E48B5F4BA91C2EF5311F8E5
82E78B2345D8EC9A207EB9CAB358C119
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
THAT IS ALL YOU NEED.
Make sure your not copying the (bootloader)
and also DONT include:
< Please cut following message >
Wilks3y said:
Dude Please make sure your only using:
(...)
THAT IS ALL YOU NEED.
Make sure your not copying the (bootloader)
and also DONT include:
< Please cut following message >
Click to expand...
Click to collapse
Of course I wouldn't copy that stuff. The following screenshots are from the HTCDev website. I think it's clear enough to anyone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It also says this:
When copying the token, start with this line:
Code:
<<<< Identifier Token Start >>>>
And end with this line:
Code:
<<<<< Identifier Token End >>>>>
Stripester said:
Did you ever resolve this issue, I have the same problem and have been told by the HTC repair centre (not HTC) that it is a software fault but they will not repair/replace as its out of warantee. The only way of resolving it (as told by them) is to have a new motherboard . I am waiting to get it back and then will decide on my next course of action.
I am pretty [email protected] off as this is no fault of my own and have never bricked a device in my life, let alone through normal use!!
I had orginally unlocked the bootloader, relocked it but it is now showing locked rather than re-locked.
I don't mind openning it up and direct flashing if this is possible!
Click to expand...
Click to collapse
Well phone back, says locked do I have to resign myself to having an expensive paperweight??
HTC/Vodafone will not even consider mending or looking it as it, as it has a slight (hairline) crack in the case above the usb connection, apparently any cosmetic damage is a "Get out Clause" very disappointed
Stripester said:
Well phone back, says locked do I have to resign myself to having an expensive paperweight??
HTC/Vodafone will not even consider mending or looking it as it, as it has a slight (hairline) crack in the case above the usb connection, apparently any cosmetic damage is a "Get out Clause" very disappointed
Click to expand...
Click to collapse
Are you sure, have you tried it at HTC/Vodafone? Cause the body can show hairline cracks after a while, so maybe they also replace your case under warrenty.

[SOLVED] Won't boot and random fastboot errors after upgrade attempt

Hi,
Short story:
My One X won't boot to Android anymore. I can only enter boot / fastboot modes.
And when trying to apply modifications (fastboot flash or fastboot unlock), it shows various errors, not always the same.
Long story:
I bought this phone second hand quite a while ago, soon after its market launch. It was already unlocked and rooted, but I don't know what method had been used.
RUU says it runs release 1.28.
Boot says:
- S-On
- HBoot-0.94.0000
- Radio 1.1204.103.14
- Apr 11 2012,02:27:11
Given that it was unlocked / rooted it never received an OTA.
I recently decided to perform a full wipe, and by the way a full upgrade.
So:
- I did a CWM Recovery backup
- I flashed a «semi-stock» image, the stock de-odexed 4.18.401.3 from android-revolution (URL forbidden here, I'm a newbie!) .
- I performed a full wipe / factory reset / cache cleaning / Dalvik cache cleaning.
It didn't boot, and I learnt about the ICS / JB hboot incompatibility.
I tried to flash the boot from the android-revolution page, with no improvements.
So, I decided to revert to my Nandroid backup, from the recovery.
Didn't boot either.
Then I found a Windows computer, relocked the bootloader, and tried RUUs (3.14 and 1.26) with no success.
CID is HTC__203, so I used .401 RUU or OTA files.
RUU application stops each time at a different moment, either for usb connexion error, wrong RUU for my phone, not enough battery, or unknown error.
I read about a battery charge issue, and tried this method to charge it:
Code:
while : ; do fastboot getvar battery-voltage; fastboot reboot-bootloader; sleep 6; done
(as you may see, my main workstation is running Linux)
After a 9 hours long night:
Code:
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
It seems that it couldn't go farther than 3.6V.
But if I tried to unlock my phone after that:
Code:
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]#
You can see error message is not always the same.
Same for my firmware.zip flash attempts:
Code:
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (remote: unknown command)
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 5.928s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
OKAY [ 1.419s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 1.629s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]#
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
hervenicol said:
Hi,
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
Click to expand...
Click to collapse
Give me result from command fastboot getvar version-main
Download this fastboot.zip and extract it to a folder fastboot rename the file fastboot-linux to fastboot. The file fastboot only is for windows and if you want to keep it rename fastboot to fastboot-windows
Thant said:
Give me result from command fastboot getvar version-main
Click to expand...
Click to collapse
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
hervenicol said:
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
Click to expand...
Click to collapse
1. Charge your phone
2. Download this RUU 1.28.401.9
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Thant said:
1. Charge your phone
2. Download RUU 1.28.401.9 (link removed from quote)
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Click to expand...
Click to collapse
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
hervenicol said:
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
Click to expand...
Click to collapse
Good to hear that:good:
All upgrades applied, works like a charm
I set the title for this answer with [SOLVED], I hope it applies to the thread as well.
Now let's look for a way to root this rom!

HTC Desire 816G cyanogenmod fastboot oem unlock issue

When i issue
sudo fastboot oem unlock
I am getting this error message
...
FAILED (remote: unknown command)
finished. total time: 0.002s
How to solve this issue?

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

Categories

Resources