Develop Bugs

Unlocking bootloader HTC Tattoo -Spain

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?

[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.

[Q] htc one x flashing issue , going mad at fixing it

Hello All,
need urgent help on this issue. I am a so called novice is posting to forums , so please excuse me if I have inadvertently done or not done something important.
Following are the device details , can't provide a screenshot so typing all info -
-------------------------------------
****unlocked****
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.103.14
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure Boot: enabled
MODEM PATH : OFF
Apr 11 2012,02:27:11
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SHOW BARCODE
IMAGE CRC
--------------------------------
Used fastboot from a windows 7 command prompt and flash the recovery few times , I see the following
E:\fastboot>fastboot flash recovery recoverycwm.img
sending 'recovery' (8832 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
E:\fastboot>fastboot flash recovery recoverycwm.img
sending 'recovery' (8832 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
E:\fastboot>fastboot flash recovery recoverycwm.img
< waiting for device >
sending 'recovery' (8832 KB)...
OKAY [ 1.073s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.245s
E:\fastboot>fastboot flash recovery recoverycwm.img
< waiting for device >
sending 'recovery' (8832 KB)...
OKAY [ 1.159s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: (0000000a))
finished. total time: 1.390s
E:\fastboot>fastboot flash recovery recoverycwm.img
sending 'recovery' (8832 KB)...
OKAY [ 1.071s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 1.276s
Initially I had Viper ROM , then I have tried to update my HTC One X with the following ROM
SkyDragon v 2.0 HOX
but failed to do so , then I tried to recover from the Stock Rom , also failed to do it successfully.
I have tried using adb commands to transfer the rom onto the sdcard too , but fails to transfer with error
Earlier I could go to recovery mode and see the rom zip files on my storage , but now I can access the storage too.
I am in a kind of fix which I am not sure if I can come out of , so all help would be appreciated.

Hboot is to low for newer roms. They don't run on that. What's the outcome of :
Fastboot getvar version-main
Sent from my HTC One X using XDA Premium 4 mobile app

E:\fastboot>fastboot getvar version-main
version-main: 1.28.708.10
finished. total time: 0.006s

http://androidruu.com/getdownload.p...Radio_2.1204.122.17_release_268338_signed.exe
Here is a ruu for you.
Sent from my HTC One X using XDA Premium 4 mobile app

seems to be the wrong ruu , I hit the following error

The ruu is correct
Did you relock the bootloader if it's unlocked ? Did you put the phone in the bootloader/fastboot usb mode ? Did you run the ruu with admin rights ?
Sent from my HTC One X using XDA Premium 4 mobile app

yes, I did put the phone in the bootloader/fastboot usb mode and all the activity was run with admin rights.
However I am not sure how do I do this relock the bootloader if it's unlocked.
Can I unlock it or relock it as many times I need?
what is the command please? I will re-run the whole sequence again once I am able to charge the phone beyond 30%.

Charge the phone to 100% if you can. Go for safe !
Fastboot oem lock
That's the command.
Sent from my HTC One X using XDA Premium 4 mobile app

Thanks much , now I am back to stock rom and booted
I guess now I have to update HBOOT , turnback to unlocked status and try to update the ROM to some other version if I wish to ?

Yes now you have to do all official ota's you can get. After those updates you unlock the bootloader and make a nandroid backup with the custom recovery and then you start flashing other roms
Sent from my HTC One X using XDA Premium 4 mobile app

Need help returning to stock

Hey guys, so I recently got an S6 but was going to sell my m7 for a little extra cash. It had the purple camera issue tho so I was going to return it to stock and send it in for repair. I attempted to follow the return to stock thread but something went wrong. I started out bootloader unlocked via HTCdev and S-off. I thought I had successfully flashed the RUU and proceeded with command to go back to S-on. Well now I can only get to the bootloader. When I try to reboot it always brings me back to the bootloader. Currently it says Tampered, Locked, S-on and I can only do stuff through fastboot. I haven't been able to successfully flash anything from here. Anybody know if there's anything else I can do to get this phone running again? Appreciate any help

What firmware is the phone on? While in fastboot, it will tell you hboot version as well as the os version. If that doesn't work, do fastboot getvar all and post it here with imei and serial removed.

Thanks for the reply. It was on the latest firmware that Santod had posted. OS is 5.28.605.2

If you are on 5.28, the 4.4.3 ruu might work for you.
http://forum.xda-developers.com/showthread.php?t=2919442
EXE RUU VZW M7 4.4.3 S-on users
Sent from my HTC6500LVW using XDA Free mobile app

Uzephi said:
If you are on 5.28, the 4.4.3 ruu might work for you.
http://forum.xda-developers.com/showthread.php?t=2919442
EXE RUU VZW M7 4.4.3 S-on users
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Whenever I try to use the EXE file I get a connection error. I'm not sure why, the phone's connected and I can still use fastboot. I have the latest HTC sync manager installed so the drivers should be good. If I try to just flash the RUU I get a signature error. Any other ideas that might work?
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.036s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot flash zip DOTTA
T_VZW_M7_4.4.3_FUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1439606 KB)...
OKAY [ 51.053s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 236.104s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.036s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>

Rpowers308 said:
Whenever I try to use the EXE file I get a connection error. I'm not sure why, the phone's connected and I can still use fastboot. I have the latest HTC sync manager installed so the drivers should be good. If I try to just flash the RUU I get a signature error. Any other ideas that might work?
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.036s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot flash zip DOTTA
T_VZW_M7_4.4.3_FUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1439606 KB)...
OKAY [ 51.053s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 236.104s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.036s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>
Click to expand...
Click to collapse
Dude first you have to extract the zip file then run the .exe file just read the instructions in the thread of that RUU. Happy Flashing

OK, I feel like an idiot. I've been trying so many different things to get this to work I copied the section of the command window that I knew wasn't right., however it is still not working. What I have done is extracted the zip from that thread and tried to flash the rom.zip file that was included in it. Unfortunately I still get a signature fail. When I try to use the exe program in that thread I get a USB connection error every time. Thank you both for your replies. It seems that thread is my only shot so I'm going to take my questions over there.

Can't get bootloader unlocked

Trying to unlock the bootloader, got my Unlock_code.bin file, but when I try to use it I get this error message:
C:\Users\Will\Desktop\fastboot>fastboot flash unlocktoken unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.007s]
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.082s
And of course when I reboot into bootloader it says it is locked. Tried moving the file with fastboot and the unlock_code file to a couple different places and nothing helped, and rebooting both phone and PC. Any ideas?

willfill said:
Trying to unlock the bootloader, got my Unlock_code.bin file, but when I try to use it I get this error message:
C:\Users\Will\Desktop\fastboot>fastboot flash unlocktoken unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.007s]
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.082s
And of course when I reboot into bootloader it says it is locked. Tried moving the file with fastboot and the unlock_code file to a couple different places and nothing helped, and rebooting both phone and PC. Any ideas?
Click to expand...
Click to collapse
Did you enable unlocking in dev options?
If so, many others who have had an issue with their unlock tokens reported that using a different browser worked for them. Search the forum, there's at least one thread on about it.

Also the error message says your unlock token is 0KB. Are you sure the file is complete?
Maybe try redownload it and verify it with an MD5 hash.

I figured it out, it was just that I copied the code to get the unlock file improperly when I was in CMD. I had to copy it, but I had to turn off "enable line wrapping selection" in the cmd properties, when I tried before to copy it I ended up copying a bunch of extra info that I edited out in notepad, and I think that caused an extra space or error to be somewhere in the code, even though it worked on the HTC site. Anyway thank you for the tips guys!

willfill said:
Trying to unlock the bootloader, got my Unlock_code.bin file, but when I try to use it I get this error message:
C:\Users\Will\Desktop\fastboot>fastboot flash unlocktoken unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.007s]
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.082s
And of course when I reboot into bootloader it says it is locked. Tried moving the file with fastboot and the unlock_code file to a couple different places and nothing helped, and rebooting both phone and PC. Any ideas?
Click to expand...
Click to collapse
Maybe your computer automatically extracted the file or something
Sent from my 2PS64 using XDA-Developers mobile app

I had to request unlock multiple times and use different browsers until it finally worked. I believe it finally worked when I completed the process with the MS Edge browser.
Sent from my HTC 10 using Tapatalk