Hi All,
I've just tried to use the new HTC tool and got an error message from the web tool after submitting the device ID token, error as follows:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 170.
Error Reason: CID Not Allowed.
I have a stock UK Vodaphone Sensation and followed the HTC instructions to the letter (Honest ;-0).
Any help or advice welcome
Its saying your cid (carrier id) is not allowed. Your cid= vodafone's cid. Looks like vodafone had not agreed to have their branded phones unlocked, unless you entered in something wrong. Expect this from most carriers though (especially tmobile here in the states) as they DO NOT want unlocked bootloaders.
Time to do it the XDA way xd
Sent from my HTC Sensation Z710e using XDA Premium App
Why not use revolutionary
najeebmirza said:
Hi All,
I've just tried to use the new HTC tool and got an error message from the web tool after submitting the device ID token, error as follows:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 170.
Error Reason: CID Not Allowed.
I have a stock UK Vodaphone Sensation and followed the HTC instructions to the letter (Honest ;-0).
Any help or advice welcome
Click to expand...
Click to collapse
Same Problem here... i think i go with the xda-noobproof-guide
+1 for doing it the XDA way, no need for official HTC unlocker
revolutionary.io
Swyped from my HTC Sensation
Thanks
Thanks for the info, I had a sneaking feeling it was Voda raining on my parade.
I'll check out the noob guide
I'm totally speculating here but its possible that HTC is only allowing unbranded (CID: HTC__001) units in the first stage of the rollout.
Hi all,
When I try and obtain an unlock key from HTCDEV for my desire s, I get the following......
Error Code: 173.
Error Reason: Check Rule Fail with exception
any ideas ? I doubled checked the procedure, and I'm cutting and pasting the right part. confused.com
tangerine0072000 said:
Hi all,
When I try and obtain an unlock key from HTCDEV for my desire s, I get the following......
Error Code: 173.
Error Reason: Check Rule Fail with exception
any ideas ? I doubled checked the procedure, and I'm cutting and pasting the right part. confused.com
Click to expand...
Click to collapse
Wasn't your phone revolutionary S-off'ed?
What were you doing at the HTCDev site?
different phone, that got bricked !
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
chuaniyang said:
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
Click to expand...
Click to collapse
Well it's still gonna show relocked if that's what your talking about bcuz you unlocked it then relocked so it isn't gonna show tampered with unlocked at the bottom that's only for the first time you unlock it that it says tampered with unlocked at the bottom, but if you unlock it again it's just gonna say relocked not unlocked. Hopefully this answers your question.
Sent from my samsung galaxy player
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
chuaniyang said:
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
Click to expand...
Click to collapse
Yea that is strange but I don't think it would be considered a problem unless you have the phone stuck in Bootloop or something strange is going on with the phone like apps.not working or battery draining fast. I can see what your worried about and it is strange but I wouldn't worry too much about it but you should look up somewhere in the forums about that but I wouldn't know much about the international version I'm on the US version. Good luck with your problem
Sent from my samsung galaxy player
I checked this thread
http://forum.xda-developers.com/showthread.php?t=1671643
seems I need to wait someone can S-OFF this device
superCID can install any RUU, but can't unlock, root, install custom ROM without S-OFF
I've managed to change my cid and install a new Rom then unlock it and root so it's possible
Sent from my HTC One S using Tapatalk 2
the other reason maybe user just can unlock/relock limited times. ?
does any one change CID and unlock/relock over 3 times ?
I've relocked about 4 time's now changed cid once
Sent from my HTC One S using Tapatalk 2
My default cid is HTC_203, i changed to HTC__102, HTC__001 and 11111111.
Everytime cid changed, I will lock/unlock again. When changed to 11111111, I can't unlock anymore.
Sent from my HTC VLE_U using xda app-developers app
Mate, the CID is in the partition that gets summarized together with the other partitions when calculating the Unlock Token.
So, if you change this or any other relevant partition by for example changing the CID, you will invalidate your old unlock token.
After changing CID, please re-lock bootloader, then go "fastboot oem get_identifier_token" and go to HTC-Dev and unlock again.
After that, you can proceed with everything else as usual.
If you cannot unlock with CID 11111111 this is NOT normal. Everyone else can.
So either you did something wrong in the above process or you somehow half-bricked your phone.
Yes, everytime I changed cid, I got a new unlock code. if not, fastboot will give me error message during unlock process.
I think my situation is not normal, and I'm trying to find out why then fix it. Now, I still can install any RUU , if they have the same HBOOT version.
Sent from my HTC VLE_U using xda app-developers app
I'd guess it's a half brick because if you can't unlock something is wrong. There is no unlock counter because no-one has had it yet. I've unlocked about four or five times now too and don't have that problem. You should consider sending it in for repair. As long as there's no S-OFF you'll have no chance to force an unlock I guess. If the security is as complex as on the HOX, it's likely the situation couldn't even be resolved by a jtag programmer or such.
sent from the tip of my finger
Thanks, no one have the same question as me. I will try to call HTC service.
CID 11111111 Issue
Hello there,
I want to install an older RUU (actually installed is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed )
my intention is to downgrade the Basbeand Version with this Procedure to get rid of this "HomeButton-Jumparound-Whatever" Issue which occures when i am in GSM (2G) Mode.
when i get this phone brandnew there was no Problem, just after updating to 1.78 this ****** began.
When i changed my CID from HTC__102 to 11111111 the first time everything went fine and i was able to install every RUU
Now i tried to change my Radio to an older Version by install an older RUU, but it won't work no more, i allways get an Error 140 or 131.
if there is another method to change the radio version, I'd appreciate any council
relock Bootloader, turn off virus scanners, run ruu as admistrator, I've done of course
I would be grateful for any help
ERROR 140 : bootloader error
ERROR 131 : cid error
are you install T-MOBILE 1.84 RUU ?
this will chane HBOOT version from 1.08 to 1.09
if you can unlock, try to find some way change your HBOOT version back to 1.08.
then you can insall RUU_Ville_U_HTC_Europe_1.78.401.2.
RUU_Ville_U_HTC_Europe_1.78.401.2 can be installed only with the other it does not work
i've got HBOOT 1.13.000 (shown in bootloader)
i just want to downgrade the Radio..
edit: when try to install RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed
or
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed
i get Error 155
we have some thing different. but you are lucky then me. I just can install T-MOBILE 1.84 RUU, if I try to install another version. always got HBOOT version error
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-main: 1.84.531.2
(bootloader) commitno-bootloader: e964c535
The HTC srevice center(tw) call back. they say they find some motherboard error on my device.
I don't think change cid and unlock will cause it happen.
I have just had this phone which i tried to S-off at the HTCdev. But it showed an error message saying:"We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work"
I used CMD and copied exactly but seemed not working...using desire s running on 2.3.5 with HBoot 2.00.0002 and software 2.15x.......can anyone help me with this??
First, you're trying to unlock the bootloader, not S-OFF. You won't get S-OFF by what you're doing. Read the other thread that's at the top, "S-OFF versus unlocking the bootloader via HTCDev", to understand what does what and what are the limitations of the method you're trying to follow.
Second, you failed copying the code correctly. Most likely you misunderstood the instructions that say where to start copying, from which line.
Jack_R1 said:
First, you're trying to unlock the bootloader, not S-OFF. You won't get S-OFF by what you're doing. Read the other thread that's at the top, "S-OFF versus unlocking the bootloader via HTCDev", to understand what does what and what are the limitations of the method you're trying to follow
Click to expand...
Click to collapse
read: don't use the htcdev.com method man
Ok... I will try... Sorry s little noobie here
Sent from my HTC Desire S using xda premium
Hello everyone. I've been following XDA since I first laid hands on a Nexus One. Thanks to all of you, I've been able to hack, mod, customize, etc. with only a few close calls. My ATT One X has proven to be a little more tricky and unforgiving. Long story short, I'm stuck in fast boot with an incorrectly changed CID (HTC_621) and a relocked bootloader. I was hoping to get another unlock token from HTC but I think they've abandoned the link. My only other hope was to edit the CID of the "android-info" file in the rom.zip of the RUU, but WinRAR says corrupt archive error when I change the text file. WinZIP won't even open the package--says its invalid. Bottom line, I've exhausted all resources as far as recovering from bad flashes and boot loop. My problem is that damn CID. Any bright ideas guys?
Official ROM zips are signed.
The signature makes the zip non standard so some apps wont open them and most everything else will not modify the file.
Even if you could modify you would make the signature invalid so it would not flash unless you had s-off.
By "Abandoned link" do you mean HTC will not send you an unlock token because the CID is invalid?
Have you tried your previous unlock token?
Without getting a valid unlock token I am unsure if what you can do.
Just out of curiosity, what were you trying to do exactly and what CID is that?
he was probably trying to flash the international jelly bean =)
redpoint73 said:
Just out of curiosity, what were you trying to do exactly and what CID is that?
Click to expand...
Click to collapse
It's an Endeavour CID for HTC Asia in Taiwan. And we wonder why HTC locks bootloaders and write-protects system partitions.
To the OP: This would not have worked anyway because you were trying to install software for a completely different phone.
Your original unlock token should still work. Trying unplugging and powering off your phone, rebooting your computer, and try flashing it again.
I thought unlock tokens were locked to the current CID?
If you change CID you need a new unlock token?
That is how my phone worked
twistedddx said:
I thought unlock tokens were locked to the current CID?
If you change CID you need a new unlock token?
That is how my phone worked
Click to expand...
Click to collapse
It's worth a shot. If it doesn't work, I don't see any way out. He can't run the RUU, he can't boot up, and he can't unlock. There might be some low-level fix via Linux. Try the unbricking Evita thread.