Related
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.
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
XTZY23 said:
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]droid:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
Click to expand...
Click to collapse
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
htc one v_commands
heavy_metal_man said:
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
this is what it returned:
C:\Fastboot>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) lock
(bootloader) writesecureflag
(bootloader) readsecureflag
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) read_sandisk_fw
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Fastboot>
XTZY23 said:
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
Click to expand...
Click to collapse
I would use these 2 sets here. First make a nandroid backup, just incase
Then issue these fastboot commands one after another and copy the results.
Fastboot oem readcid
Fastboot oem readsimlocktype
All good? Now first we want to change your cid to super. So issue this command
Fastboot oem writecid 11111111
Fastboot reboot bootloader
Fastboot oem readcid
Your cid should now show up as 11111111, that's 8 1's
All good? Lastly we issue these commands.
Fastboot oem clearsimlocktype
Fastboot reboot
Now just check your simcard and all should be well you can now flash any ruu for any carrier without issue, but always check its compatible with your model type first!
Sent from my HTC Desire S using Tapatalk
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
XTZY23 said:
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
Click to expand...
Click to collapse
Did it simunlock OK?
Sent from my Nexus 7 using Tapatalk
Hmm, maybe yes maybe not
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
************update***************
1.last night i put s-on on my phone...but
2.even on s-off i could not unlock the bootloader after installing the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.22.401.1_Radio_20.76.30.0835U_3831.19.00.120_release_273801_signed
3. no bootloader unlock->no root->no s-off->no simlock
4. the message header is ****Relocked**** and the error the i receive when i try to unlock the bootloader again is:
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.640s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.650s
***********fixed this one*************
HTC ONE toolkit 2.0-Squabbi-- saved me fro a lot o work! great thanks to squabbi!
XTZY23 said:
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
Click to expand...
Click to collapse
http://www.sieempi.eu/blog/2011/09/22/universal-sim-unlock-for-s-offed-htc-devices-536 ok give this a bash pal. will hopefully fix the issue.
GSM problem/hardware problem
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
XTZY23 said:
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
Click to expand...
Click to collapse
The back cover for these kinds of phones usually have "antenna boosting" pads. My htc sensation gets no signal without the back cover on.
For anyone else I would recommend trying the linked website solution from sieempi before fastboot commands
Sent from my Nexus 7 using Tapatalk
I've got this phone for a while now but since i updated it to official marsmallow it's been stuck into bootloader. The phone is stock, still locked and S-ON. I've tried to unlock it so i can use a custom rom but when i do the official bootloader unlock from htc it goes all okay until it should promp me on the phone screen to confirm bootloader unlock, i can't find a way to make it work. I also tried to use the RUU but when it's rebooting my phone into bootloader (witch it is already) it doesn't reboot the phone goes stand by and the program stops. I the tried to get the zip RUU into an SD but the CID doesn't match since i got the Vodafone UK one so my cid is VODAP001 and i can't find the right RUU for this version. Can someome please help, i'm desperate.
I've tried to use the RUU.zip file from cmd using comand fastboot oem rebootRUU bur it gives me this message:
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.058s]
finished. total time: 10.058s
BlackMambo90 said:
I've got this phone for a while now but since i updated it to official marsmallow it's been stuck into bootloader. The phone is stock, still locked and S-ON. I've tried to unlock it so i can use a custom rom but when i do the official bootloader unlock from htc it goes all okay until it should promp me on the phone screen to confirm bootloader unlock, i can't find a way to make it work. I also tried to use the RUU but when it's rebooting my phone into bootloader (witch it is already) it doesn't reboot the phone goes stand by and the program stops. I the tried to get the zip RUU into an SD but the CID doesn't match since i got the Vodafone UK one so my cid is VODAP001 and i can't find the right RUU for this version. Can someome please help, i'm desperate.
I've tried to use the RUU.zip file from cmd using comand fastboot oem rebootRUU bur it gives me this message:
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.058s]
finished. total time: 10.058s
Click to expand...
Click to collapse
same issue here
did you find the solution?
skierr said:
same issue here
did you find the solution?
Click to expand...
Click to collapse
Yeah I had to send it to support since it had a hardware problem with the memory ( I've pinpointed the problem to the ROM) if you your warranty is expired maybe you should try replacing the motherboard
skierr said:
same issue here
did you find the solution?
Click to expand...
Click to collapse
You have the same sector/emmc errors? Of you just have the problem of stuck in bootloader? Those are two very different things. With the second one being quite possibly fixable.
You need to be specific if you want any meaningful help. Saying you have the "same issue" is never sufficient for folks to give help; and is just going to end up confusing you and others.
Assuming it is not a hardware emmc failure, and you want some direction, please provide the following:
- If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
- If you don't know how to do fastboot, what OS number and radio number does it say on the phone's bootloader screen?
- Bootloader locked or unlocked?
- Any other mods (TWRP, custom ROM, etc.).
- What events led to the current condition? Did you try to flash something, or update OS? Or just happened spontaneously?
- Exact names/version numbers of files you installed, or tried to flash.
The more detail you can give, the better.
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
I got an HTC One (M9) from a friend that no longer uses it and when you boot up it does ask for the last email registered to this device. It will not allow me to do anything in RUU mode or command line without repeating the same message over and over.
Code:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
C:\Users\rbgCO\Desktop>fastboot flash firmware.zip
unknown partition 'firmware.zip'
error: cannot determine image filename for 'firmware.zip'
C:\Users\rbgCO\Desktop>fastboot flash zip firmware.zip
target reported max download size of 800000000 bytes
sending 'zip' (33033 KB)...
OKAY [ 2.726s]
writing 'zip'...
(bootloader) HOSD CL#669662
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8 RU_SIGNATURE_FAIL )
finished. total time: 5.717s
C:\Users\rbgCO\Desktop>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.016s]
finished. total time: 0.016s[CODE]
[/CODE]
Now doing some research I see the spot that was not checked was by pressing the build number 6 times and it is a checkbox allowing you to enter the mode to flash different roms or even to flash this back to stock but I do not know how I could change that.
If changing that checksum is not possible, is there a way I could contact google or HTC to see which email is associated with the lock so that I can bring it back to the guy I bought it from and have him enter that email and password allowing me to change that checkbox then reset the phone again?
Any help would be greatly appreciated.
Any help would be appreciated!
rbgCODE said:
Any help would be appreciated!
Click to expand...
Click to collapse
Does it have a recovery?
my htc m9 verizon
show unlocked s-off what do i do next should i just flash or still need to do something else. please am new to rooting and all