so i was updating my friends rezound to the latest firmware and when it got timee to unlock again we realized htcdev.com was down for maintenance...are the unlock tokens created specifically for a certain device or can i use the unlock token from my phone on his phone also?
thanks
The token is device specific. However... If you still have the original token used to unlock the phone in the first place, you should be able to use that.
Sent from my ADR6425LVW using XDA
socal87 said:
The token is device specific. However... If you still have the original token used to unlock the phone in the first place, you should be able to use that.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Just further confirmation to your post; you WILL be able to use the old token to unlock again.
You can totally use the token you originally generated to unlock the same phone it was generated for. If it's a different phone you'll need a new token to state the obvious.
Related
Hi,
I am quite new to Andriod and just trying the rooting for the first time.
I have HTC Amaze 4G on Mobilicity in Canada.
I was trying to root my phone. My attempt was failed in the stage of unlocking the bootloader,
I was following the instruction on HTCDev site
I successfully retrieve the token code. However, When I enter this token to HTCDev site it gives me following error.
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.
I checked everything...token was copied properly, I checked there is no additional space.
Can anyone suggest me any other procedure to root my phone?
You asked the same question on another thread so I guess I just paste my answer here too.
I'm a total noob so take my reply with 2 grains of salt...
But I read on the rooting thread that aparently the problem is (at least with Telus users) that since HTC Dev added the Tmo amaze to the list now the Telus get CID errors since they are in the "wrong" country.
May be that is what is happening to you too????
You can read more about it in that thread http://forum.xda-developers.com/show...324177&page=25 just look around there and see if it applies to you too...
the link doesnt work ferincr
ferincr said:
Telus get CID errors since they are in the "wrong" country.
Click to expand...
Click to collapse
Hmmm....if we log in using a proxy located in the U.S. would that fool htc into unlocking our bootloaders?? Just a thought.
P.S. I think its the rest of you who are in the wrong country. LOL
Mobilicity and WIND haven't given HTC the thumbs up to allow bootloader unlocking apparently (What I garnered from an HTC reply email)
rbaruch said:
Mobilicity and WIND haven't given HTC the thumbs up to allow bootloader unlocking apparently (What I garnered from an HTC reply email)
Click to expand...
Click to collapse
You can see my struggles with htc to find out why the telus bootloader cant be unlocked HERE
can you do it again because same problem happened to me yesterday but maybe was something about the site because today I did without a problem
ruur said:
can you do it again because same problem happened to me yesterday but maybe was something about the site because today I did without a problem
Click to expand...
Click to collapse
Tried again today. Still no go. Address bar indicates "not allowed"
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
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: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
diablo2jz said:
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
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: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
Click to expand...
Click to collapse
no, you can unlock it once it's relocked. Most of us that have taken the OTA by RUUing had to unlock and relock . So, I would go through the process again , just check and double check the steps. I had an issue where it failed 8 straight attemtps and it turned out I was actually copying a space in the code..once I removed the space it went right through.
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
It has let me redo the HTC Dec steps with my phone multiple times. I finally figuired out once you get the unlock.bin file you can always reuse it. I do what is stopping you. :/
Sent from my ADR6425LVW using XDA App
Yeah I googled the heck out of everything I could think of and searched XDA and found almost nothing.
Guess I'm just lucky
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
Maybe a dumb question, but your not including "please cut the following " part in it when you submit are you ?
Nope only pasted what I have highlighted in post 3.
Not to mention I have purposely copied them or some stuff out, and get a normal error to the extent of "You're token is to long, or to short" ect.
Same issue
Error Code: 173.
Error Reason: Check Rule Fail with exception
Anyone else getting this?
diablo2jz said:
Nope only pasted what I have highlighted in post 3.
Not to mention I have purposely copied them or some stuff out, and get a normal error to the extent of "You're token is to long, or to short" ect.
Click to expand...
Click to collapse
Sorry, no idea then ..
So wait, where did you get this phone? Is it possible the old owner unlocked it, relocked it, then sold it? If so, anybody know if he will be able to unlock since he probably doesn't have the original key?
Comicazy said:
Is it possible the old owner unlocked it, relocked it, then sold it?
Click to expand...
Click to collapse
That is correct. I had no idea but that's what I realized.
If I can't I'm going to sell this damn thing for a Nexus.
Unlocking Bootloader Failed! 173
I am getting the same error. I just activated the phone yesterday and have tried the process on a PC and a Mac now. Are the token identifiers supposed to change every time? I noticed that every time I type the command fastboot oem get_identifier_token I get a different token. I read some other posts where they were having problems and it ended up being a hardware issue. Any thoughts?
timothydye79 said:
I am getting the same error. I just activated the phone yesterday and have tried the process on a PC and a Mac now. Are the token identifiers supposed to change every time? I noticed that every time I type the command fastboot oem get_identifier_token I get a different token. I read some other posts where they were having problems and it ended up being a hardware issue. Any thoughts?
Click to expand...
Click to collapse
I have unlocked and relocked my phone 2 times now, and got a different token and identifier every time, so it shouldn't matter if he has the original unlock token or not.
mjh68 said:
I have unlocked and relocked my phone 2 times now, and got a different token and identifier every time, so it shouldn't matter if he has the original unlock token or not.
Click to expand...
Click to collapse
but if you want to re-unlock you can re use the same unlock bin file without generating a new token. If you make a new token your bin file is invalidated.
https://twitter.com/#!/Jmz_Software/status/164817446841221120
known issue now
diablo2jz said:
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
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: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
Click to expand...
Click to collapse
if you've bought a used rezound, that means the person
who sold probably unlocked the phone first.
why not ask that person for the unlocked token he used?
con247 said:
but if you want to re-unlock you can re use the same unlock bin file without generating a new token. If you make a new token your bin file is invalidated.
Click to expand...
Click to collapse
Ah, gotcha .. I had already deleted the first token so didn't have a choice hehe
This is an issue with the website, not the phone. I'm dealing with the same bull****.
I had the same problem. I relocked to get the update and could not unlock. I don't know what the fix is. Fortunately I saved the file from the first time I unlocked and it worked fine.
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
You know, I don't know if that's sensitive info but you may want to black some of that out just in case since it pertains to your particular device. Probably doesn't matter but I always opt for the safe route since I'm a paranoid android.
EDIT: Looks like HTC fixed the issue and people are getting their unlock codes now.
http://forum.xda-developers.com/showthread.php?t=1475864&page=2
Done (http://forum.xda-developers.com/showthread.php?t=2158836)
Can you explain me what is this? Unlocking your htc phone? Unlocking what bootloader, kernel or network restrictions?
i don't need google, my wife knows everything
uglyjohny said:
Can you explain me what is this? Unlocking your htc phone? Unlocking what bootloader, kernel or network restrictions?
i don't need google, my wife knows everything
Click to expand...
Click to collapse
it's unlock code to unlock bootloader for your HTC Android phone.
After unlock bootloader, you can root your HTC phone.
And after that you can install any custom rom you want.
And do many many amazing things.
I tried this but got error 170
Error Code: 170.
Error Reason: CID Not Allowed.
You havn't by any chance had it repaired have you? cause if the motherboard is changed you cant unlock it.
Perhaps this will help me, I just got a new 3vo yesterday and the damn site wont send the email.
<<<< Identifier Token Start >>>>
800F6B84A62EB5D2F49B887A9FD1F717
DAF1D2A8838398E2701D53834D31F72A
3B487DF4547332B2078777E30A144D0E
F9AE9ED1DAB94CF6A8D3AB09F8A803BF
6657E6F616F1524D8BF0ECD91C24761E
BB52054503862229E87EC441E230A367
BC94914C2AA99EED63317B856FFBF96F
8C7F5103E4355900FCD35F4396BCA7F6
EE22270F75521ABF60EA405B527B2B26
61A9B8E398DA1794D61ABEAAC0FAAAB3
B48931C70FFA87680EB8D35200FF326E
0D5F859269F9B9F41C8A2E701272D732
99043D4BA83DE4966D80674EE36D7D87
00C814BB6E22B3A6E5AAB0DA4017B172
C6144604EA396B14111BB58B0FEA2D90
9653BA8E88C0D807D893EB0D1CDCE755
<<<<< Identifier Token End >>>>>
Please and thank you [=
This new code worked no problem. the previous one is giving error
Edit: I've zipped the file because it wasn't allowing me to upload .bin file
BUT
EM|NEM said:
This new code worked no problem. the previous one is giving error
Edit: I've zipped the file because it wasn't allowing me to upload .bin file
Click to expand...
Click to collapse
do it work with all CID?
spritz2o said:
do it work with all CID?
Click to expand...
Click to collapse
As long as you provide the correct cid for your phone it should. word of caution it doesnt like spaces so make sure there are no spaces before or after any of the text.
crimsy wrote an excellent guide to unlock root and soff your phone check it out: http://forum.xda-developers.com/showthread.php?t=1813818 :good:
spritz2o said:
do it work with all CID?
Click to expand...
Click to collapse
You have to use your OWN unlock code. the one i posted was only for Shponglized.
Its very easy to get your own token but sometimes htcdev doesnt send the code to an email or you may be experiencing problems with the site. In that case post your Identifier token here so that someone else can generate the unlock code for you.
Hey guys,
i need a downgrade without using htcdev.com.
Why without?
The Unlock_token.bin, that they send, wasn't correct. I tried to flash the token and every time it said " remote:"Unlock Token check failed"".
The Phone was rooted and unlocked, but then i have bricked it and send it to repair @ htc.
After they reinstall a new "mainbord", htvdev never work...
It's Hboot 1.53.0007... -> so, revolutionary doesn't work...
It's there a chance to downgrade without unlocked Bootloader?
Or unlock the Loader without htcdev?
First yeas, look in this section for e.g. Juopunut Bear.
Second, this is developer section, not Q&A!
cheater2 said:
Hey guys,
i need a downgrade without using htcdev.com.
Why without?
The Unlock_token.bin, that they send, wasn't correct. I tried to flash the token and every time it said " remote:"Unlock Token check failed"".
The Phone was rooted and unlocked, but then i have bricked it and send it to repair @ htc.
After they reinstall a new "mainbord", htvdev never work...
It's Hboot 1.53.0007... -> so, revolutionary doesn't work...
It's there a chance to downgrade without unlocked Bootloader?
Or unlock the Loader without htcdev?
Click to expand...
Click to collapse
are you developing a new downgrade way?
orlox said:
are you developing a new downgrade way?
Click to expand...
Click to collapse
wrong section, reported
i am getting ready to send my device back for a warranty exchange. in following the steps, like i have done twice before, i accidentally jumped ahead....
I did the Fastboot oem writesecureflag 3 BEFORE i flashed the lock bootloader zip. The phone still boots and functions normally, but i can't flash the lock bootloader zip, it fails, even though it says unlocked tampered.
Anyone have any suggestions?? I am at a loss, and not sure if there is a command i can run to revert this all back.
My wife was nagging me and i scrolled down and jumped ahead like a total noob. thanks for any help!
And yes everything is accessible still, cwm, adb, the phone itself, etc etc. it functions fine...
Run s-off. After that follow guide in order
Since you're unlocked still face palm should work. Just follow after the point you unlock.
If not any new method will work
Unlocking the bootloader automatically voids your warranty....
thayl0 said:
Unlocking the bootloader automatically voids your warranty....
Click to expand...
Click to collapse
Thank you for an incredibly unhelpful reply.
thayl0 said:
Unlocking the bootloader automatically voids your warranty....
Click to expand...
Click to collapse
Ehhh. It says may. Plus there is a way to get it back to an s-on **LOCKED** state. HTC's unlock tool doesn't log your device ID and IMEI and remote void your warranty like Asus' unlock util does.
Sent from my HTC6435LVW using XDA Premium 4 mobile app