I was going to follow the steps of using Revolutionary... but it asks for my hboot version either 1.3 or 1.4... but I have 1.5... should I just pick 1.4?? will that mess anything up?
Yeah it won't work with yours. You need to use the HTC unlock method on the htcdev site. And don't even try the revolutionary method as it will most likely fry your phone.
http://htcdev.com/bootloader/
Sent from my Premium XDA app
lexusmike said:
Yeah it won't work with yours. You need to use the HTC unlock method on the htcdev site. And don't even try the revolutionary method as it will most likely fry your phone.
http://htcdev.com/bootloader/
Sent from my Premium XDA app
Click to expand...
Click to collapse
what's the link to that site bro?
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
ShawnGotBANDZ said:
what's the link to that site bro?
Click to expand...
Click to collapse
nevermind when I quoted you it came up lol
This thread should help you out too.
http://forum.xda-developers.com/showthread.php?t=1239821
[GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash Ur Ass Off! [9.11.11]
Sent from my Premium XDA app
lexusmike said:
This thread should help you out too.
http://forum.xda-developers.com/showthread.php?t=1239821
[GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash Ur Ass Off! [9.11.11]
Sent from my Premium XDA app
Click to expand...
Click to collapse
yo, I tried that and it wouldn't accept my code... I made sure there were no spaces and everything... the error was
"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 think you need to be on the latest ota to use the HTC unlock or atleast the version they say on the site. I used the unrevoked method so I'm not exacltly sure how that one works.
Sent from my Premium XDA app
ShawnGotBANDZ said:
yo, I tried that and it wouldn't accept my code... I made sure there were no spaces and everything... the error was
"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."
Click to expand...
Click to collapse
if you had not figured it out already, I had the same error and I realized I copied the blank spaces just after the token codes. I re-copied and it worked fine after
theboz1419 said:
if you had not figured it out already, I had the same error and I realized I copied the blank spaces just after the token codes. I re-copied and it worked fine after
Click to expand...
Click to collapse
Nah I tried that too, didn't work... but I just unplugged/restarted my phone and started over again... It gave me a new code and worked fine
Sent from my PG86100 using xda premium
good info for troubleshooting
theboz1419 said:
if you had not figured it out already, I had the same error and I realized I copied the blank spaces just after the token codes. I re-copied and it worked fine after
Click to expand...
Click to collapse
thanks alot this help fixed the error
this should be a main thread for htcdevunlock errors
Related
i sent my phone away for warranty im on telus, i had it unlocked cause i was lucky enough to unlock beofre they made it impossible. i still have the identifier token from htc if i redo the unlock usuing that token will it maybe work? and the htc dev site dosent seem to be responding anyone klnow what i should do?
Unlock code.bin is good for that specific phone. So I do not know what to tell you. Sorry.
i still have the unlock code bin and its still the same phone
tombeach22 said:
i still have the unlock code bin and its still the same phone
Click to expand...
Click to collapse
They just fixed the phone and not replace it? If that is the case, you can still use it and unlock the bootloader.
they had just repaired it and it came back locked up. i tried having it in fast boot then fastboot flash unlocktoken unlock_code.bin and it said it didnt work, ideas? or am i doin it wrong?
tombeach22 said:
they had just repaired it and it came back locked up. i tried having it in fast boot then fastboot flash unlocktoken unlock_code.bin and it said it didnt work, ideas? or am i doin it wrong?
Click to expand...
Click to collapse
That depends on what was repaired, like if they replaced any internal hardware. Do you know what exactly they did to ur phone?
Sent from my NRGized Amaze...
via xda premium
the chargin port thingy was ****y. wouldnt charge unless it was help at the perfect position. not sure what they replaced but what i heard from a telus employee i know was that they put a whole new chip in so idk what would be changed
From what I know, some phones have the charging port onto the motherboard. So if it doesn't work, they have to replace the whole motherboard.
bawls, so htcdev site says my new id token is invalid
From what ur sayin it seems they replaced something that is effecting you unlocking it. If it is saying invalid, i would write them, or try sending them a message on twitter, htcdev has a twitter and most of the time they respond. If u dont have a twitter write them and tell them ur situation and that its saying its invalid...
Now that i think about it, it may be saying its invalid because u already used it when you unlocked it the first time. This happened to me when i relocked my phone and was trying to unlock it again. I would type in the toiken, and it would say it was invalid, because i had already used it. But i still had and used the Original file, i believe its a .bin fine, that i unlocked it with the first time, to unlock it again
Sent from my NRGized Amaze...
via xda premium
what do you mean "beofre they made it impossible"? Can you just requrest to unlock from htcdev site again? I just got my unlock bin file my telus last Thur or Fri .
and2cs said:
what do you mean "beofre they made it impossible"? Can you just requrest to unlock from htcdev site again? I just got my unlock bin file my telus last Thur or Fri .
Click to expand...
Click to collapse
Well he said 2 posts before that he went to htc dev and it said invalid, so i think that his original thought of it now being impossible was a misinterperatation.. but it coming up as invalid is because he already used the toiken once before. I kno this from experience trying to re-unlock myself
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
From what ur sayin it seems they replaced something that is effecting you unlocking it. If it is saying invalid, i would write them, or try sending them a message on twitter, htcdev has a twitter and most of the time they respond. If u dont have a twitter write them and tell them ur situation and that its saying its invalid...
Now that i think about it, it may be saying its invalid because u already used it when you unlocked it the first time. This happened to me when i relocked my phone and was trying to unlock it again. I would type in the toiken, and it would say it was invalid, because i had already used it. But i still had and used the Original file, i believe its a .bin fine, that i unlocked it with the first time, to unlock it again
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
What exactly did you do?
Sent from my HTC Ruby using xda premium
and2cs said:
what do you mean "beofre they made it impossible"? Can you just requrest to unlock from htcdev site again? I just got my unlock bin file my telus last Thur or Fri .
Click to expand...
Click to collapse
Telus amazed is no longer on the list. I was under the impression HTC made Telus amazes perm locked
Sent from my HTC Ruby using xda premium
tombeach22 said:
Telus amazed is no longer on the list. I was under the impression HTC made Telus amazes perm locked
Sent from my HTC Ruby using xda premium
Click to expand...
Click to collapse
so have you tried the entire unlock process again from the start? tokens can't be reused, but an unlock.bin file can, assuming they didn't change anything major on your phone...
either way, use hasoon's all in one tool to help you get unlocked, it pretty much automates the whole process, then report back
Try creating a new account from htc dev..
i try to pull my identifier token and i get this
INFO<<<< Identifier Token Start >>>>
INFO68E3DEA8D53E6E3045F3DC1394658F53
INFOEC4F0317BB6473F24DFB774503A77BFB
INFOEF48F446945AC0A43CBD5EE1CB1C22CD
INFO7A52633C4D4E829CCE17E10807A55147
INFODE3C96A89E3BBDE0FECAF2A779A65CC1
INFOD94481AB5C93D793750F2F3739D83856
INFOE3BFEC2E6DBC2487DF83142646231FBB
INFOE06B76C376F950A7E6FDB93CEA6F09F6
INFO9F622B67028D77ED6755CF7E5D009EF7
INFOB401257F47A6E4ABFE47807A3F0777C1
INFO597C0DE6E85D51565D3D148E0359B5C3
INFOAD4D6C71E51E2A3BA386C5FE422CE090
INFO4084FD5B2DD07CB9E5D97359FCA9A217
INFOD84DA1D3286DDAA0565AC48F1016F1F0
INFOE9A06AC4F3C0D3D8E6AC28C25AEEFEAC
INFOA999D11493EFA4E6E2C2A7FF4266F30F
i dont think its supposed to say info at the start of every line?? and it says
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.
removed all the ifos and it says
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: 141.
Error Reason: Token Decryption Fail (Can not generate result).
No, it's supposed to - the instructions say to just copy the entire token, including INFO, so I'm assuming that they just filter the first 4 characters off of each line.
And if you're using a Telus Amaze4G, you're SOL. You can't generate new unlock codes as there's no option for Telus Amaze's... and the IMEI's do have some sort of way to identify which carrier they were bought from.
ok ok i got it! i thought they made it so telus amazes cant be unlocked but i did the htcdev method, i removed all the infos and it worked!
Accophox said:
No, it's supposed to - the instructions say to just copy the entire token, including INFO, so I'm assuming that they just filter the first 4 characters off of each line.
And if you're using a Telus Amaze4G, you're SOL. You can't generate new unlock codes as there's no option for Telus Amaze's... and the IMEI's do have some sort of way to identify which carrier they were bought from.
Click to expand...
Click to collapse
you fail... misinformation like that can only hurt this community...
tombeach22 said:
ok ok i got it! i thought they made it so telus amazes cant be unlocked but i did the htcdev method, i removed all the infos and it worked!
Click to expand...
Click to collapse
i'm glad to see you got it working again, sometimes it just takes a few tries and some patience lol, now go enjoy modding it once again
http://rootzwiki.com/news/_/article...der-unlock-is-now-available-for-the-dna-r1250
http://www.androidpolice.com/2012/11/24/exclusive-how-to-unlock-the-droid-dnas-bootloader/
I hope you guys have insurance because this sounds risky.
cdmoore74 said:
http://rootzwiki.com/news/_/article...der-unlock-is-now-available-for-the-dna-r1250
http://www.androidpolice.com/2012/11/24/exclusive-how-to-unlock-the-droid-dnas-bootloader/
I hope you guys have insurance because this sounds risky.
Click to expand...
Click to collapse
I promise you, if you follow the directions, it's fine. It's been done around 30 times with no issues in testing.
And everybody should know by now, these sorts of hack are always a risk.
We assume that risk all the time.
D
.
PS - It's posted here in the Original Dev section.
After unlock can we follow the root instructions in the other threads? And does this allow ROMs ?
Sent from my HTC6435LVW using xda app-developers app
Dri94 said:
After unlock can we follow the root instructions in the other threads? And does this allow ROMs ?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes, you flash recovery, the a root package.
D
.
I followed the directions and I now have an Unlocked and rooted DNA so it works very well just follow the instructions
welp...i bricked mine.. D: sad day
Hard brick here also
If you have problems or errors or it doesnt feel right, you need to come ask for help before continuing.
What was this posted again? I posted this in the proper subforum, where activity is being monitored and support is being given.
These bricks are likely recoverable, join #unbrick on freenode and get my attention. You will need linux
HTCdev still no luck
jcase said:
If you have problems or errors or it doesnt feel right, you need to come ask for help before continuing.
What was this posted again? I posted this in the proper subforum, where activity is being monitored and support is being given.
These bricks are likely recoverable, join #unbrick on freenode and get my attention. You will need linux
Click to expand...
Click to collapse
Just got done running everything. It all appeared to work just right, phone restarted just fine no bricks or anything. Got to the end on HTCdev and it said (Error 160, MID not allowed). Any idea what may have gone wrong?
renegadeone8 said:
Just got done running everything. It all appeared to work just right, phone restarted just fine no bricks or anything. Got to the end on HTCdev and it said (Error 160, MID not allowed). Any idea what may have gone wrong?
Click to expand...
Click to collapse
run
fastboot getvar cid
and paste results
jcase said:
run
fastboot getvar cid
and paste results
Click to expand...
Click to collapse
C:\Android>fastboot getvar cid
cid: VZW__001
finished. total time: 0.002s
I'm getting an error at adb restore backup.ab
All the steps leading up to that were fine. But it looks like adb restore isn't a recognized command. My phone isn't prompting me for a restore.
largeselection said:
I'm getting an error at adb restore backup.ab
All the steps leading up to that were fine. But it looks like adb restore isn't a recognized command. My phone isn't prompting me for a restore.
Click to expand...
Click to collapse
go to the official thread
renegadeone8 said:
C:\Android>fastboot getvar cid
cid: VZW__001
finished. total time: 0.002s
Click to expand...
Click to collapse
Doesnt look like you ran the exploit successfully, go post any errors in teh official thread
Ok thanks
jcase said:
Doesnt look like you ran the exploit successfully, go post any errors in teh official thread
Click to expand...
Click to collapse
I will try it again and post whether I have any trouble or not
Never mind. Figured out the issue. Now it's just hanging at full restore. There's no password right? I selected restore my data and nothing happens.
---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------
Ok moved to official thread. My bad
largeselection said:
Never mind. Figured out the issue. Now it's just hanging at full restore. There's no password right? I selected restore my data and nothing happens.
---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------
Ok moved to official thread. My bad
Click to expand...
Click to collapse
there is no progress bar and it does take a bit just let it sit for a bit. at least it did for me and it eventually said it was done
Let's lock this thread in keep it in one place. Sorry!
Sent from my Galaxy Nexus using xda app-developers app
Locked.
Let's keep discussion in one place guys. There is one in general by jcase, and one in the dev section too.
Sent from my EVO using Tapatalk 2
Been trying to unlock bootloader for two days now. Keep getting the error Invalid Bootloader Token Length or Check Rule Fail with exception when it actually doesn't time out. I am pasting as I should w/o any spaces anywhere. Is there some other method I can use to get my TWRP backup restored to my phone? Running HBOOT 1.19.0000 S-ON.
Thanks for your time.
Dave
Pretty sure HTC dev is essential for rooting our phone. A lot of people seem to be having trouble with token length. Unfortunately I don't have any advice, I personally never had a problem with token length
Sent from my EVO using xda premium
If it's a problem with token length check that it's copied from arrow to arrow. HTC Dev does not like spaces at all. Pasting the token does not show if there are spaces either.
om4 said:
If it's a problem with token length check that it's copied from arrow to arrow, no spaces. HTC Dec does not like spaces at all.
Click to expand...
Click to collapse
i quadruple checked the token. I even pasted it in notepad to ensure I wasn't copying some weird formatting.
This is what I'm pasting, maybe I'm still missing something. The formatting looks funny below but it's perfectly square in notepad.
<<<< Identifier Token Start >>>>
774CDA2AC310CA56D0A8E870F4BF7763
C45B2AA3E0F31BBB65413C6F01C23E55
C93DAFB948802F8EEDC7857D76AF7AA3
CAE3D3E6DF8D6612B7C7944A23EF95AA
08532B78F54127C95937FB7A9103306E
F5682985C107312E28F56534AD3BB842
63A40542C6146C0765706E94564907BE
659A4A388B5E45278580AD0FB5736AB0
5FBF4DE5B565E5499BA93272CC8D9903
5F5B76914F0D9D00F05CA499AAF770DE
4B5BB297E70BBA4C424674A8BC0788AD
5E77F51D3B7EF1175EF0E5FABADB061B
EAC2E167546BCC60823ECE7FE920EA52
5368A2B9148240A944B00747F9BFB405
AC0B5DBFE8B1F5A56FE16ABB4C52808A
CD376242534ABADB2314F87FE9EDC45A
<<<<< Identifier Token End >>>>>
Odd, it seems like the right formatting. It may be an issue with HTC Dev. Has the phone been unlocked before? You can use the same unlock.bin as last time
htcdev is having issues at the moment
bigdaddy619 said:
htcdev is having issues at the moment
Click to expand...
Click to collapse
Which is why I want to find an alternative to htcdev. Cannot root therefor all my titanium backup data is useless to me.
Dave
Try Textpad , make sure no hidden characters etc.
Sent from my EVO using xda app-developers app
waterbound said:
Try Textpad , make sure no hidden characters etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
It was their site. Worked today however I've still not gotten the token 3 hours later. An email to them just gets me a generic reply that they are doing maintenance.
Dave
Same here. It finally worked but I am still waiting on the email.
om4 said:
You can use the same unlock.bin as last time
Click to expand...
Click to collapse
Could you do this if you want to S-off?
buddahj said:
Could you do this if you want to S-off?
Click to expand...
Click to collapse
Using htcdev.com to unlock your bootloader is part of the DirtyRacun exploit
bigdaddy619 said:
Using htcdev.com to unlock your bootloader is part of the DirtyRacun exploit
Click to expand...
Click to collapse
Gotcha...thanks
HTCDev
Try today HTCDev for a different device.
I have been told that I got an e-mail sent ... but received nothing.
Looks like something's wrong on HTCDev.
Same problem here. 24 hours + with htcdev down for the count.
Just tried again and was able to get the bin file in case anyone else was waiting.
I was working on getting s-off and despite using a 64 bit windows, everything went well. I have read many topics and the solutions on the issues of the token identifier not work when trying to get the unloc bin, and here I am stuck. It always says the code is not long enough, I check to make sure I copy exactly as they say, no paste, I have sync manager and the drivers are the proper ones. I even tried disabling my virus protection for a few hours, and yet I remain stuck and unable to get the unlock code bin sent to my email.
You should try to copy & paste it to see if it solves the issue.
#Root-Hack_Mod*Always=LTE
I always do, I even considered typing it but for some strange reason, it just refuses to work
Have you tried this ??
http://forum.xda-developers.com/showthread.php?t=1690919
Edit-Oh ok. When you had posted "no paste" I thought you weren't copying & pasting it. Also have you tried using a different pc/laptop??
#Root-Hack_Mod*Always=LTE
Probably an issue with htc dev
Sent from my PoS MoPho
bigdaddy619 said:
Probably an issue with htc dev
Sent from my PoS MoPho
Click to expand...
Click to collapse
I tried using my friends laptop and it didn't work...I ran a ruu and got my phone back to stock with s-on still attached...However I'm trying to root, and not even regawmod's rooting program is unable to get the identifier token.
Most likely it's an issue on HTC's end, not yours. Only advice I have is to keep trying
The advice is free....the bandwidth, not so much
laie1472 said:
Have you tried this ??
http://forum.xda-developers.com/showthread.php?t=1690919
Edit-Oh ok. When you had posted "no paste" I thought you weren't copying & pasting it. Also have you tried using a different pc/laptop??
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
still having issues with the token
dvill1 said:
still having issues with the token
Click to expand...
Click to collapse
Have you tried that link ?? Or tried to get the token from a different pc ??
#Root-Hack_Mod*Always=LTE
laie1472 said:
Have you tried that link ?? Or tried to get the token from a different pc ??
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
I helped him, he's good now
Sent from my EVO using Tapatalk 2
thatotherguy.. said:
I helped him, he's good now
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Cool
#Root-Hack_Mod*Always=LTE
i have relocked my bootloader to s-off my evo 3d .. as this thread says (http://forum.xda-developers.com/showthread.php?t=1535987) and at the end it says "YOU MIGHT HAVE TO RE-DO THE ENTIRE PROCESS OF HTCDEV WAY OF UNLOCKING AGAIN AT THIS POINT. WORKS 100% OF THE TIME" but every time i try to re-unlock it in the command screen i got : " FAILED (remote : unlock token check failed) " and its still re-locked , what should i do ?
Are you using your original token or a new one. Also make sure you copy the correct parts of the token.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
Are you using your original token or a new one. Also make sure you copy the correct parts of the token.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
i used the original one ( i didn't submit another unlock token to htcdev ) ... can't use a new one because htcdev.com didn't send me a verification code to my account , so i borrowed an account and unlocked it .