Develop Bugs

Unrooted, Stock HTC One X dead

hi, my htc one x is dead, i cannot on it. heres what happened.
i was facebooking
then the app keep crashing
then after that everything started crashing, like got this google processor thing
and aft that my whole phone just shut down
then when i hold the power button, got this weird thing come out
like some weird numbers
then got option HBOOT, REBOOT, REBOOT something loader, and POWER DOWN
after that i managed to got into recovery and hard resetted it but it got stuck at the htc one logo. help!

If you never unlocked the bootloader ....send it in for warranty. Nothing we can do about that !

D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem readcid
... INFODEBUG: cid: VODAP001
OKAY [ 0.035s]
finished. total time: 0.035s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot getvar version-m
version-main: 3.14.161.27
finished. total time: 0.035s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem RebootRUU
... INFO[ERR] Command error !!!
OKAY [ 0.020s]
finished. total time: 0.021s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.152s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem RebootRUU
... INFO[ERR] Command error !!!
OKAY [ 0.128s]
finished. total time: 0.129s
D:\Tel\one x\soft\Fastboot\Fastboot>
i can't run rebootRRU i want return to stock rom .i not have backup from 3.14.161.27 what can i do ? thx

Type fastboot oem rebootRUU (Not RebootRUU)

thank you very mutch you right can you help me more ?
firmware111.zip is OTA_ENDEAVOR_U_JB_45_S_Vodafone_UK_3.14.161.27-2.17.161.4_release_299172atv1b11ychs0d2fs
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem readcid
... INFODEBUG: cid: VODAP001
OKAY [ 0.012s]
finished. total time: 0.012s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.141s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem rebootRUU
... INFOSave data from original MSC...
INFOSave data from SIF...
INFOUpdate partition data to SIF partition
INFOUpdate partition data from original MSC...
INFO[MSG] OKAY
OKAY [ 0.206s]
finished. total time: 0.207s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot flash zip firmware.zip
sending 'zip' (12876 KB)... OKAY [ 1.676s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[boot] unzipping & flushing...
INFOFormat partition LNX done
INFO[RUU]WP,boot,100
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]WP,hboot,50
INFOsignature checking...
INFOstart image[recovery] unzipping & flushing...
INFOFormat partition SOS done
INFO[RUU]WP,recovery,100
INFOERASE backup cid
OKAY [ 4.825s]
finished. total time: 6.503s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot flash zip firmware111.zip
sending 'zip' (374962 KB)... OKAY [ 48.630s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 65.465s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot erase cache
erasing 'cache'... OKAY [ 0.186s]
finished. total time: 0.186s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem rebootRUU
... INFOSave data from original MSC...
INFOSave data from SIF...
INFOUpdate partition data to SIF partition
INFOUpdate partition data from original MSC...
INFO[MSG] OKAY
OKAY [ 0.193s]
finished. total time: 0.194s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot flash zip firmware111.zip
sending 'zip' (374962 KB)... OKAY [ 48.869s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 65.693s
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot getvar version-main
version-main: 3.14.161.27
finished. total time: 0.006s

Well you flashed your firmware. What else do you need? What are you even trying to do?

I guess a custom recovery and a brand new JB Rom

Mr Hofs said:
I guess a custom recovery and a brand new JB Rom
Click to expand...
Click to collapse
I installed custom ROM, based on the 3.14 stock, I had the working device but without cellular network (no signal / no service) and with WiFi whish is working incorrectly (it couldn't detect my home wireless network, for example)
but i prefer to install the stock rom (vodafone UK) . i don't no what i did wrong

Did you flash the correct boot.img file ?

TToivanen said:
Well you flashed your firmware. What else do you need? What are you even trying to do?
Click to expand...
Click to collapse
my firmware not was completed when i flash
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot flash zip firmware111.zip
sending 'zip' (374962 KB)... OKAY [ 48.869s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 65.693s
---------- Post added at 12:07 AM ---------- Previous post was at 12:02 AM ----------
Mr Hofs said:
Did you flash the correct boot.img file ?
Click to expand...
Click to collapse
yes the boot from custom rom , afther erase cache , install rom , i switch on the phone same problem everithing ok but network signal and wifi doesn't work , after this ncx_317_v14-RENOVATE , boot.img and update zip ...

your main version number tells me you have an updated JB hboot ! did you do a FULL wipe in the recovery before installng the new rom ?

yes i did every time , i think all i need is a compatible karnel with mods , i try a lot but i didn't find.
can you help me with OTA_ENDEAVOR_U_JB_45_S_Vodafone_UK_3.14.161.27-2.17.161.4_release_299172atv1b11ychs0d2fs.exe ??

What do you mean.....the kernel delivered with the rom is in 99% the right boot.img. except for some aosp roms.
Flash the delivered boot.img from the desired rom, perform a full wipe and install the rom ....must work !
Dont know what you tried ?
I bet your ruu has not been released
Btw you need to full wipe that means, cache, dalvik cache, data, system before you install the new rom......dalvik cache is forgotten a lot

Hey this thread is going in the wrong direction. Lol! This isnt even about my question..

PokMahPok said:
Hey this thread is going in the wrong direction. Lol! This isnt even about my question..
Click to expand...
Click to collapse
You've been highjacked mate.... so what about your problem ?
Edit : and i never got a answer from you regarding your question !

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

WLAN does not work after 4.4 Update

Hey Guys,
i wanted to upgrade my HTC One M8 to the newest T-Mobile Germany Firmware. My HTC One was rooted and I had the TWRP Recovery with ViperRom.
I installed a Nandroid Backup with the 1.12.111.18 (4.3) Firmware. After that i installed the 1.57.111.2 Stock Recovery, than I relocked the Bootloader and after the Root was gone, I updated my Phone to the 1.57.111.2 (4.4.2), and now my WiFi is not working. I even upgraded to a newer Version of the Stock Recovery, but it still not working.
Here are some Information about my Phone.
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
OS-
CIDNUM: T-MOB101
If you guys, need some other Information. Just let me know.

lepush said:
Hey Guys,
i wanted to upgrade my HTC One M8 to the newest T-Mobile Germany Firmware. My HTC One was rooted and I had the TWRP Recovery with ViperRom.
I installed a Nandroid Backup with the 1.12.111.18 (4.3) Firmware. After that i installed the 1.57.111.2 Stock Recovery, than I relocked the Bootloader and after the Root was gone, I updated my Phone to the 1.57.111.2 (4.4.2), and now my WiFi is not working. I even upgraded to a newer Version of the Stock Recovery, but it still not working.
Here are some Information about my Phone.
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
OS-
CIDNUM: T-MOB101
If you guys, need some other Information. Just let me know.
Click to expand...
Click to collapse
Are you S-Off? You can't revert to older firmware while you are S-On.

xunholyx said:
Are you S-Off? You can't revert to older firmware while you are S-On.
Click to expand...
Click to collapse
I'm on S-On, but I want to install a newer Firmware not downgrade to an older one.
This is what I get when I try to install the OTA Update
Code:
xxx-imac:~ x$ cd Desktop
xxx-imac:Desktop xxx$ cd adb
xxx-imac:adb xxx$ ./fastboot devices
HT459WM15609 fastboot
xxx-imac:adb xxx$ ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.010s
xxx-imac:adb xxx$ ./fastboot flash zip OTA_M8_UL_K44_SENSE60_SECURITY_TMO_DE_1.70.111.1-1.57.111.2_release_383280.zip
target reported max download size of 1830612992 bytes
sending 'zip' (253074 KB)...
OKAY [ 9.223s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 9.713s
And when I try to get to the Stock Recovery, I get the HTC One Icon with the red triangle
This is what I get, when my Bootloader is relocked
Code:
xxx-imac:adb xxx$ ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.010s
xxx-imac:adb xxx$ ./fastboot flash zip OTA_M8_UL_K44_SENSE60_SECURITY_TMO_DE_1.70.111.1-1.57.111.2_release_383280.zip
target reported max download size of 1830612992 bytes
sending 'zip' (253074 KB)...
OKAY [ 9.539s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 19.701s
xxx-imac:adb xxx$

TWRP flash failing on Moto-Z Play unlocked

I unlocked the moto-z play. In fastboot it says 'flashing_unlocked'. I tried flashing twrp 3.1.1-addison and I get:
[email protected]:/mnt/hgfs/vmshare# fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (23452 KB)...
OKAY [ 1.613s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.618s
[email protected]:/mnt/hgfs/vmshare
I then tried:
[email protected]:/mnt/hgfs/vmshare# fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16198 KB)...
OKAY [ 1.115s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.313s]
finished. total time: 1.429s
[email protected]:/mnt/hgfs/vmshare#
I downloaded the image three times and all three times I got not signed or corrupt.
Any help here is appreciated.
Y-

use moto fastboot https://forum.xda-developers.com/attachment.php?attachmentid=2427667
The Next time post in Q&A not in development forum

TeamMex said:
use moto fastboot https://forum.xda-developers.com/attachment.php?attachmentid=2427667
The Next time post in Q&A not in development forum
Click to expand...
Click to collapse
Thanks but it failed for me.
[email protected]:/mnt/hgfs/vmshare# ./linux-fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
target max-sparse-size: 256MB
sending 'recovery' (16198 KB)...
OKAY [ 1.164s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.310s]
finished. total time: 1.474s
[email protected]:/mnt/hgfs/vmshare#

The message that it is not signed out corrupt may be one you need to get used to. As far as I understood: Only Motorola would be capable of signing. But Motorola does not publish any signed does, they only release OTA. At least until now.
Does it work if you just take the message as success?

YileKu said:
Thanks but it failed for me.
[email protected]:/mnt/hgfs/vmshare# ./linux-fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
target max-sparse-size: 256MB
sending 'recovery' (16198 KB)...
OKAY [ 1.164s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.310s]
finished. total time: 1.474s
[email protected]:/mnt/hgfs/vmshare#
Click to expand...
Click to collapse
More easy
Do
fastboot boot twrname.img
Copy the recovery and flash from the recovery
Note:
If you flash via fastboot you can get these lines but the flash works
Sent from my Motorola Moto Z Play using XDA Labs

tag68 said:
The message that it is not signed out corrupt may be one you need to get used to. As far as I understood: Only Motorola would be capable of signing. But Motorola does not publish any signed does, they only release OTA. At least until now.
Does it work if you just take the message as success?
Click to expand...
Click to collapse
I am unable to access twrp after rebooting the phone, so I assume it didn't actually flash.

Problem flashing gpt.bin with fastboot

Hello, just tried to "downgrade" my phone back to stock firmware after using some custom ROM's after some time. Started following various guides online, but I seem to fail at this bit when flashing the stock firmware
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.073s
Click to expand...
Click to collapse
Any tips or help? Currently my phone just bootloops in fastboot, and after quickly flashing TWRP to check the phone, my system and data partitions seem to be messed up, they are unable to be mounted in TWRP.