I have repeated the process to unlock the bootloader on my HTC EVO LTE, but after reboot it still says "LOCKED". I successfully submitted the token and even got the prompt on the phone whether I wanted to unlock, and I selected the first option "Yes". But, it's still locked upon reboot. Any ideas???
thambikutty said:
I have repeated the process to unlock the bootloader on my HTC EVO LTE, but after reboot it still says "LOCKED". I successfully submitted the token and even got the prompt on the phone whether I wanted to unlock, and I selected the first option "Yes". But, it's still locked upon reboot. Any ideas???
Click to expand...
Click to collapse
Anybody?
You simply must follow instructions exactly, not overlooking anything.
First go to htcdev-dot-com
Then click on the "Unlock Bootloader" link.
Follow the instructions exactly, submitting a valid email address with registration, and receive your unlock code file.
There are many more instructions on this forum for using this information to successfully unlock your bootloader.
I have had to use the same methods several times within the past few hours, just to perform a successful S-OFF
on my device. You can even stay at the htcdev website, submitting new device IDs as neccessary, until you
achieve your goal.
There may be other methods to unlock the bootloader, but I have no knowledge of them.
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
I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
elijahkan14 said:
I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
Click to expand...
Click to collapse
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Kienan said:
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Click to expand...
Click to collapse
I can't get any of these methods to work
elijahkan14 said:
I can't get any of these methods to work
Click to expand...
Click to collapse
1. Make sure you are on the latest software: 2.17.605.2
2. Factory reset your phone
3. Slowly go through the manual instructions here: [Script] Automated Unlock/SuperCID/Temp-Root scripts for Windows and Linux
So, I've unlocked this phone before.
Just got a replacement.
EVERYTIME I put the token code in and summit I get failed!
screenshot of the error:
http://s28.postimg.org/z8obp6h58/Untitled.jpg
I tired a few different codes and nothing.
HELP?
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
BlowUpTheOutsideWorld said:
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
Click to expand...
Click to collapse
I was having difficulty with the SuperCID hack, and it appears that it was due to an OTA update. I was able to following the directions prescribed here, but I had HBOOT 1.15 and not 1.16. The basic idea is to
1. Gain "temp-root" access using the loop-restore trick together with the fake_backup.ab file.
The next steps were failing for me. I was able to verify that mmcblk0p4 had been copied over correctly, with the "modded" version, but each time the boot loader was rebooted, it would be replaced with the original version containing VZW__001, and not 11111111. However apparently all that needed to be done to reach S-OFF status was:
2. Run Rumrunner after obtaining temp-root status. The Rumrunner binary unlocks the phone and places it in S-OFF status.
I just bought a att htc one off Craig's list and it is tampered/relocked. The phone boots straight into fastboot and there is no operation system on phone. I tried to use ruu to get it back to stock but it freezes at checking hash 5percent. I also tried to fastboot the ruu zip but it had an error verify 12 signatures. Are there any other suggestions that I could try to get an os back on this phone or is this phone pretty much bricked?
Unlock bootloader, install twrp recovery, sideload a rom zip.
There are numerous existing threads that describe how to do each step, just spend a little time reading first.
cschmitt said:
Unlock bootloader, install twrp recovery, sideload a rom zip.
There are numerous existing threads that describe how to do each step, just spend a little time reading first.
Click to expand...
Click to collapse
I don't think I can unlock the relocked bootloader without the token correct? Is there any other way to unlock a locked bootloader without the htcdev token?
crazyfied said:
I don't think I can unlock the relocked bootloader without the token correct? Is there any other way to unlock a locked bootloader without the htcdev token?
Click to expand...
Click to collapse
Yes, you'll need an unlock token.
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...??
BBEgo said:
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
Click to expand...
Click to collapse
Wonders_Never_Cease said:
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...
Click to expand...
Click to collapse
That's weird.... I thought I posted this in the Q&A forum. I was just in there looking for it and I thought it'd gotten deleted or something. Oh well.
Mods, please feel free to correct my goof.
I didn't use HTCDev to unlock. I just did Sunshine and it handled everything. S-off, unlock, and root - Talk about painless! After that I installed a custom recovery (Philz) and I was off to the races.
So I decided to SuperCID my phone so I can install whatever I want. No problem.
Then I tried to install 5.0.1 firmware (4.16.1540.8) so I could run SkyDragon, but the firmware posted on page 1 in the thread would not install- 4.16.1540.8
Kept giving me "FAILED (REMOTE:24 parsing android-info fail)"
I was able to install 4.16.401.9 with no major headaches, once I found a sensible upgrade path. That one is working fine, but I don't understand why 4.16.1540.8 would not install.
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
So now I'm S-off, locked bootloader, PhilZ recovery (put it back on with Flashify), SuperCID, on Lollipop, and I guess everything is ok. But I still don't understand why the phone wouldn't take the firmware.
Any ideas? Thanks in advance.
If you ran sunshine on it,you can run it again i believe on that same device. It should unlock it again,if not then can try htcdev as it also uses fastboot to unlock as long as you can get adb to show needed code.
BBEgo said:
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
Click to expand...
Click to collapse
In the past (at least on my One X EVITA) my understanding was that s-off meant that all security was bypassed. Meaning that bootloader check was effectively bypassed.
This isn't the case for the M8. From what I can tell a LOCKED bootloader still prevents you from flashing anything that isn't signed (anything "unofficial") even if s-off.
However, having an UNLOCKED bootloader doesn't seem to affect anything while s-off. Meaning you can do things like RUU when UNLOCKED (which normally needs to be LOCKED or RELOCKED if s-on).
In short, I don't ever recommend relocking the bootloader if s-off on this device. There isn't any reason to, as far as I can tell. Meaning, having an UNLOCKED bootloader doesn't prevent you from doing anything. However, a RELOCKED bootloader does (even when s-on) prevent some things.