During the process, and after this output, Nothing happens on my phone and the remain locked even though it says it's unlocked...
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.159s
whats going on here.
treopro408 said:
During the process, and after this output, Nothing happens on my phone and the remain locked even though it says it's unlocked...
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.159s
whats going on here.
Click to expand...
Click to collapse
I had an evo 3d I ended up having to take back and get another one that nothing I did worked to unlock it, tried on windows, mac, tried it like 50 times and nothing worked....not sure of a fix when that happens but in searching on some evo 3d's with certain ruu's it's just not working for i'm sure/hope someone helps ya
Yea same here...this is a Replacement through Asurion...my original the Vibrate motor went out...now im SOL...or Iphone Bound....UGH
Did you flash CWM recovery and then superuser after you unlocked?
JayDaKissEP said:
Did you flash CWM recovery and then superuser after you unlocked?
Click to expand...
Click to collapse
I think he means that it isn't actually unlocking. It says that it's sending the unlock token, but the unlock process that should then start on the phone was never initiated..
(if this is what he's talking about, the same thing happened here.. I had to backtrack myself and do everything over from the start before it would finally unlock it)..
Good luck
Did you run the latest OTA to ensure you are on hboot 1.5? I hust got a replacement phone from Sprint over the weekend and it came out of the box with hboot 1.4. I don't think the official HTC unlock method will work unless you are on hboot 1.5. If you are on hboot 1.4 then you can unlock using the revolutionary tool.
First, this doesn't belong in this section, you should have posted in Q&A.
Second, this has been answered before in the thread about unlocking hboot 1.5. I believe you have to flash the 2.08 RUU an then unlock. I'm on my phone now so I can't link you, but I think it's the first thread linked in the Sticky Rollup thread.
If you aren't on 1.5 as another member mentioned, then don't take the OTA an update your hboot to 1.5. Go to Revolutionary website an unlock that way. It's much easier in the long run as you'll be able to flash radios since you'll be s-off with 1.4, an you'll still be s-on with 1.5 even after unlocking.
Good luck
Sent from my PG86100 using xda premium
Hi..
I had the same problem. I fixed it by first doing all OTA updates (I had to do this twice to completely update the phone) and then using this:
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.exe
And installing right OVER the v2.17.651.5 that the phone currently had. Strange to have to do this, but when done, the HTC unlock worked like a charm.
EDIT:
This is it:
http://www.filefactory.com/file/c19...216_NV_NV_spcs_1.42_release_233304_signed.exe
In looking for a download link to your ROM, but I don't see anything. Or a change log, is this ICS????
Sent from my PG86100 using Tapatalk
stanglifemike said:
First, this doesn't belong in this section, you should have posted in Q&A.
Second, this has been answered before in the thread about unlocking hboot 1.5. I believe you have to flash the 2.08 RUU an then unlock. I'm on my phone now so I can't link you, but I think it's the first thread linked in the Sticky Rollup thread.
If you aren't on 1.5 as another member mentioned, then don't take the OTA an update your hboot to 1.5. Go to Revolutionary website an unlock that way. It's much easier in the long run as you'll be able to flash radios since you'll be s-off with 1.4, an you'll still be s-on with 1.5 even after unlocking.
Good luck
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Listen to this guy. If you have HBOOT 1.4, DON'T TAKE THE OTA UPDATE! Use Revolutionary. If you have 1.5 already, I can confirm that installing the RUU should fix the problem.
Sent from my lean, mean 2.17.651.5 machine using Tapatalk
Right. My post is assuming you are on v1.50, which is why you had to go the HTC unlock route in the first place (like I did). Obviously if you are on 1.30/1.40, you do NOT want to do it this way. Use Revolutionary if on less than 1.50, use the method I posted if on 1.50.
Downloading that new Rom Now...When I woke up this morning I did the HTC update and then it downloaded a 9mb system update...then when that was done I did it again and got a 29mb update...now the Phone is at v2.17.651.5 which was now more updated than I had before.. and downloading the rom link that was posted. It should work after that in theory correct?
I already have the BIN unlock I received from HTC. would the same file work again or do I need to get a new one because of the new updates I flashed to the phone.
Thank You XDA For your Help..
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
treopro408 said:
Downloading that new Rom Now...When I woke up this morning I did the HTC update and then it downloaded a 9mb system update...then when that was done I did it again and got a 29mb update...now the Phone is at v2.17.651.5 which was now more updated than I had before.. and downloading the rom link that was posted. It should work after that in theory correct?
I already have the BIN unlock I received from HTC. would the same file work again or do I need to get a new one because of the new updates I flashed to the phone.
Thank You XDA For your Help..
Click to expand...
Click to collapse
I would get a new one just to be on the safe side (that is what I did). It should work fine after using the RUU update over the updates you already have performed, so yes, it should work fine.
When I run the Rom Update with the Rom Posted earlier in the thread I get an
Error 132 Rom Signature Error...Any Advice?
treopro408 said:
When I run the Rom Update with the Rom Posted earlier in the thread I get an
Error 132 Rom Signature Error...Any Advice?
Click to expand...
Click to collapse
Not sure. Try redownloading?
treopro408 said:
When I run the Rom Update with the Rom Posted earlier in the thread I get an
Error 132 Rom Signature Error...Any Advice?
Click to expand...
Click to collapse
If your running and RUU.exe, you should relock your bootloader "fastboot oem lock". After that run the RUU.exe from your PC to bring your phone back to factory. Then you can install the OTA's. I did this the other day.
treopro408 said:
Downloading that new Rom Now...When I woke up this morning I did the HTC update and then it downloaded a 9mb system update...then when that was done I did it again and got a 29mb update...now the Phone is at v2.17.651.5 which was now more updated than I had before.. and downloading the rom link that was posted. It should work after that in theory correct?
I already have the BIN unlock I received from HTC. would the same file work again or do I need to get a new one because of the new updates I flashed to the phone.
Thank You XDA For your Help..
Click to expand...
Click to collapse
Same Unlock_code.bin will work
Sent from my lean, mean 2.17.651.5 machine using Tapatalk
Well I called Asurion and told them that my phone is not working..."Wont Unlock" and the had me do some trouble shooting...long story short I called them 11am pst on Wednesday and they apologized and said they will send out another replacement for the replacement..got that around 2pm today (They fed ex overnight) was able to Unlock Via HTC. And Flash CWM and reload my Rom..like you all said...it took was a simple exchange...
Related
Hey everyone, I am unable to unlock my bootloader after accepting this OTA. I just got an EVO 3D yesterday and I updated it as soon as I got it. I first checked to see if it was an HBOOT below 1.5, it wasn't so I went ahead and updated. However when i get to step 12 i believe on the htc dev site, I flash the unlock_code.bin and nothing happens just sits there. I read around and found people saying you need to take the 2.08 RUU, I tried that and when it gets to the black HTC screen I get an error 140. I was so excited to get this phone and already downloaded the rom i wanted before owning it. If someone can please help me out I would appreciate it. Thanks
No one? Dam..
Sent from my PG86100 using XDA App
majid25 said:
No one? Dam..
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Did you try factory reset or battery pull then give it another go? Also did you follow all the steps anyways give her another go.
frustrated
majid25 said:
Hey everyone, I am unable to unlock my bootloader after accepting this OTA. I just got an EVO 3D yesterday and I updated it as soon as I got it. I first checked to see if it was an HBOOT below 1.5, it wasn't so I went ahead and updated. However when i get to step 12 i believe on the htc dev site, I flash the unlock_code.bin and nothing happens just sits there. I read around and found people saying you need to take the 2.08 RUU, I tried that and when it gets to the black HTC screen I get an error 140. I was so excited to get this phone and already downloaded the rom i wanted before owning it. If someone can please help me out I would appreciate it. Thanks
Click to expand...
Click to collapse
Same here.
The same RUU I used to revert to the .2sw update to unlock two other evo3d's with hboot 1.5, will not work. Im unbelievably frustrated right now as Ive been sitting at this computer for over three hours. Please, if you find a way to downgrade your software, please let me know. thanks
not sure why you wanted to be on hboot 1.50. but shouldnt be a problem to unlock the bootloader, since it was just minor updates and still on hboot 1.50. id just try doing the process again.
i unlocked mine with unlock_code.bin that i used when i rooted my evo 3d for 1st time.....it worked fine.
Tried 5 times and failed..
Sent from my PG86100 using XDA App
evoRomz said:
not sure why you wanted to be on hboot 1.50. but shouldnt be a problem to unlock the bootloader, since it was just minor updates and still on hboot 1.50. id just try doing the process again.
Click to expand...
Click to collapse
I didn't want to be on hboot 1.5, I wanted to be below it. But when I first got my phone I checked the bootloader and was already at 1.5. If it was below that I would've been rooted right now...
to be a bit more clear it was hboot 1.5 with an OTA 2.08 when I first received the phone.
Sent from my PG86100 using XDA App
majid25 said:
I didn't want to be on hboot 1.5, I wanted to be below it. But when I first got my phone I checked the bootloader and was already at 1.5. If it was below that I would've been rooted right now...
to be a bit more clear it was hboot 1.5 with an OTA 2.08 when I first received the phone.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
1st Check you bootloader .What it says at the top .(locked/unlocked/relocked) if it says unlocked you do not need unlock_code.bin.
Try these from step 13:
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
You can flash another recovery in step 18 .....
mnomaanw said:
1st Check you bootloader .What it says at the
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
Click to expand...
Click to collapse
That's the guide I used to HTC Unlock. Video helped. There is a post somewhere about needing to Re-flash the stock RUU.exe or Ruu.zip (renamed to PG86IMG.zip) to get the phone past the "nothing happens" step where you're supposed to get the "unlock" option screen on the phone. I haven't seen the 651.5 released as a complete RUU, but you could probably flash the 651.3 RUU, finish the HTC unlock and then run the 651.5 update. Heck, the unlock would probably work after the update, idk for sure.
I have some links and my issue with this below.
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12) http://forum.sdx-developers.com/?topic=18852.0
Evo3d Useful Links(md5's): http://forum.sdx-developers.com/?topic=18827.0
Edit: Here's where I saw the info about flashing the RUU to get a good unlock:
(XDA) JTniggle's [GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash!! [9.11.11] (All via ADB)
http://forum.xda-developers.com/showthread.php?t=1239821
Says locked.
mpgrimm2 said:
That's the guide I used to HTC Unlock. Video helped. There is a post somewhere about needing to Re-flash the stock RUU.exe or Ruu.zip (renamed to PG86IMG.zip) to get the phone past the "nothing happens" step where you're supposed to get the "unlock" option screen on the phone. I haven't seen the 651.5 released as a complete RUU, but you could probably flash the 651.3 RUU, finish the HTC unlock and then run the 651.5 update. Heck, the unlock would probably work after the update, idk for sure.
I have some links and my issue with this below.
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12) http://forum.sdx-developers.com/?topic=18852.0
Evo3d Useful Links(md5's): http://forum.sdx-developers.com/?topic=18827.0
Edit: Here's where I saw the info about flashing the RUU to get a good unlock:
(XDA) JTniggle's [GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash!! [9.11.11] (All via ADB)
http://forum.xda-developers.com/showthread.php?t=1239821
Click to expand...
Click to collapse
Thank your for all the help. However I tried doing what is said in these links, I ran the 2.08.651.3 RUU and at the black HTC screen I get the error 140. Can I downgrade OTA's or no? Cuz that what it looks like I have to do here.
majid25 said:
Thank your for all the help. However I tried doing what is said in these links, I ran the 2.08.651.3 RUU and at the black HTC screen I get the error 140. Can I downgrade OTA's or no? Cuz that what it looks like I have to do here.
Click to expand...
Click to collapse
I could before the .5 update. Had to get a new phone last night and it will not downgrade to the .2 software so I can then unlock. Frustrating to say the least. Actually, I'm pissed about it.
Sent from my Google Nexus S 4G via XDA Premium
How did you get a new phone, through Sprint? And yea this sucks, hope there is a solution soon I've been posting everywhere like an idiot haha
majid25 said:
How did you get a new phone, through Sprint? And yea this sucks, hope there is a solution soon I've been posting everywhere like an idiot haha
Click to expand...
Click to collapse
Yeah, returned it. Dead pixel. Now I'm stuck with this bs bloat on here cause I can't downgrade and unlock.
Sent from my Google Nexus S 4G via XDA Premium
Edit: I cant even get a damn temp root! Stuff is pissing me off. Bout to go iphone so I dont have to nerd it up and waste my damn time, which isnt even that valuable.
I say you try to just wait it out a bit. Give it a week...but don't go iPhone!!!
majid25 said:
I say you try to just wait it out a bit. Give it a week...but don't go iPhone!!!
Click to expand...
Click to collapse
At the rate devs are dropping off, a week is an eternity. And I'm new to the evo3d. Sad face.
Sent from my Google Nexus S 4G via XDA Premium
tailsthecat3 said:
Yeah, returned it. Dead pixel. Now I'm stuck with this bs bloat on here cause I can't downgrade and unlock.
Sent from my Google Nexus S 4G via XDA Premium
Edit: I cant even get a damn temp root! Stuff is pissing me off. Bout to go iphone so I dont have to nerd it up and waste my damn time, which isnt even that valuable.
Click to expand...
Click to collapse
What method did you try for temp root?
Crackanug said:
What method did you try for temp root?
Click to expand...
Click to collapse
Frevo.
Sent from my Google Nexus S 4G via XDA Premium
tailsthecat3 said:
Frevo.
Sent from my Google Nexus S 4G via XDA Premium
Click to expand...
Click to collapse
I have some tools and files for you to use that will give you temp root and allow a downgrade to 2.08.651.2 rom, hboot will still be 1.50 though. However from there you should be able to unlock via HTCdev method. I gotta upload the files and write the code which I will post up here in a second. I hope you are ok with using adb and fastboot.
Running Cleanrom right now and would like to install the updates for the radios from HTC..could i just flash stock RUU or do i also have to relock?
liquidraven said:
Running Cleanrom right now and would like to install the updates for the radios from HTC..could i just flash stock RUU or do i also have to relock?
Click to expand...
Click to collapse
As far as I know yes
Sent from my ADR6425LVW using Tapatalk
Yes you do have to relock.
I did not relock my phone and it updated without a problem. Just went back to stock rom and stock recovery then checked system updates and was suprised when it worked since everyone was saying that you had to relock.
Sent from my ADR6425LVW using XDA App
Can you get the radios from a ROM that has them baked in, or is that not how it works?
snowride20 said:
I did not relock my phone and it updated without a problem. Just went back to stock rom and stock recovery then checked system updates and was suprised when it worked since everyone was saying that you had to relock. And would be more appropriate if posted in general.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Same for me. No relocking, just reverted to stock image & recovery.
A2Aegis said:
Can you get the radios from a ROM that has them baked in, or is that not how it works?
Click to expand...
Click to collapse
I believe we would need S-OFF for that little trick.
kewl thanks, glad i can do this without re locking as i got rid of the folder with all the files;(
No worries you can find them in the dev section if you need them again.
Sent from my ADR6425LVW using xda premium
Caladus said:
I believe we would need S-OFF for that little trick.
Click to expand...
Click to collapse
That's unfortunate. Hopefully someone can get S-OFF one of the days.
liquidraven said:
kewl thanks, glad i can do this without re locking as i got rid of the folder with all the files;(
Click to expand...
Click to collapse
I've attached what you need, courtesy of MrSmith317. If you ever do need to relock you'd just need to get another unlock token from HTCdev to unlock again.
But you will most likely end up needing this for some sort of flashing at some point.
I think you only have to relock to run the ruu. You shouldn't have to with the updates since they are flashed in the stock recovery. The ruu being flashed through hboot requires relock.
Sent from my ADR6425LVW using XDA App
feralicious said:
I've attached what you need, courtesy of MrSmith317. If you ever do need to relock you'd just need to get another unlock token from HTCdev to unlock again.
But you will most likely end up needing this for some sort of flashing at some point.
Click to expand...
Click to collapse
If you still have your unlock token from HTC you can reuse it.
Sent from my ADR6425LVW using xda premium
feralicious said:
I've attached what you need, courtesy of MrSmith317. If you ever do need to relock you'd just need to get another unlock token from HTCdev to unlock again.
But you will most likely end up needing this for some sort of flashing at some point.
Click to expand...
Click to collapse
thanks for the tools..i have the recovery image on my desktop along with the tools..a lil confused on how to start the process as cmd promp isnt working for me?
getting this error
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Lynkdev>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
actually im guessing i was supposed to flash stock recovery before this right?
so i accidently locked my phone..now stuck at hboot..went to htcdev,com and i select my phone and click submit to start the unlock process and nothing happens?? help pls.
nvm got my device unlocked again and back at step 1 lol..
liquidraven said:
so i accidently locked my phone..now stuck at hboot..went to htcdev,com and i select my phone and click submit to start the unlock process and nothing happens?? help pls.
nvm got my device unlocked again and back at step 1 lol..
Click to expand...
Click to collapse
So you have an unlocked phone and you want to get the OTA, correct? What ROM and kernel are you running?
That error you got, was that trying to run the RUU? Which one? 1.x or 2.x?
running cleanrom ICSE 2.3
kernal 3.0.13-gaf15497-dirty
i flashed stock recovery, relocked device and was stuck at hboot..couldnt get past it rebooting or anything..unlocked device and tried running the RUU exe..started up but error out saying it couldnt complete and my screen was left on HTC till i pulled battery...
liquidraven said:
running cleanrom ICSE 2.3
kernal 3.0.13-gaf15497-dirty
i flashed stock recovery, relocked device and was stuck at hboot..couldnt get past it rebooting or anything..unlocked device and tried running the RUU exe..started up but error out saying it couldnt complete and my screen was left on HTC till i pulled battery...
Click to expand...
Click to collapse
What version RUU did you use? 1.x or 2.x? Did you try running it while the phone was locked? It needs to be locked when you run RUU. But you also can't go back to an older mainver and some ICS ROMs are on 3.x
Also can you check what mainver your phone is on? In fastboot type:
fastboot getvar all
running 2.0.1 and wrong RUU i guess since its 1x
Yeah, you need to run 2.x RUU. Get it from link in this post:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
That should fix you up. Then after you run that and get the OTA, unlock, flash Amon Ra (there's a new version posted to that thread today), go to the developer menu in Amon Ra and install su and you will be stock OTA rooted.
i know there is already a link [ multiupload,com/KT9WTYGBZE ] but its broken..anyone have a working link? also im trying to fix the problem of not being able to get past
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.161s
anyone have any ideas? i have been looking around the web and the best think i can find is to use the ruu..but it wont let me go from 2.17 to 2.8..effing sucks balls right now
Anyone? Anything? Anyone get past the unlock token check fail?
Noticed your unlock_code.bin says 0kb (mine is about 4kb on disk). You may need to get a new unlock code or redownload it from your email. If you still have problems & you're stuck at HTC's step 13, you'll have to rerun the RUU and try the unlock again. With S-On, there isn't a way to run the 2.08 RUU if you've already done the 2.17 update.
I have a guide/flashing notes in my signature that may clear some things up if you want to have a look.
thanks for the reply..i tried those and nothing...i emailed htc they "say" they are working on an update to fix the unlock problem..idk how long that it will take..hopefully a dev will come up with a better way then the htc way
I'm also having the same problem with my friends phone. I get like three different outputs when I try doing the last command to unlock. It goes from saying it's successful and writing to unlock failed to something else then loops over again (trying the same command over and over). Tried running the 2.08 RUU but it won't accept it. Does anyone have a link to the 2.17 RUU? Or is there any way to downgrade to 2.08? This is really bugging me, I hate how much HTC has complicated things compared to the one click root days
See the link in my signature to get the 2.17 Ruu
Sent from my PG86100 using Tapatalk
Did you copy Unlock_code.bin over to the rootevo3dnew folder?
MistakenUtopia said:
Did you copy Unlock_code.bin over to the rootevo3dnew folder?
Click to expand...
Click to collapse
Idk about the OP, but I did. I did everything exactly the same as when I rooted my phone except my friends has the 2.17 software and mine had 2.08. Does the HTC unlock not support 2.17 or what?
you need to downgrade the ruu software number to 2.08.651.2 otherwise you wont be able to do it
http://www.multiupload.com/09NOXKCUN0
Efrencalvario said:
you need to downgrade the ruu software number to 2.08.651.2 otherwise you wont be able to do it
http://www.multiupload.com/09NOXKCUN0
Click to expand...
Click to collapse
That link doesn't appear to work. And I tried using the 2.08 RUU and it failed to work. Something about version mismatch or authentication failed. And I heard a few other users say the HTC unlock worked for them with 2.17.
I was having the same problem and i did use tgus one try to find it typing the ruu mumber with elchupacabras you will find it
Sent from my PG86100 using XDA Premium App
U can't run a lower Ruu version than whats on ur phone already with HTC's unlock & S-On.
Sent from my PG86100 using Tapatalk
im going to try the 2.17 ruu and see what happens
well everything went smooth running the ruu EXCEPT!!! i still get remote : token check failed...WTF?
tried zedomx method and even htc method both failed like 5 times..so i guess htc said **** you to anyone having 2.17.651.5..THANK YOU HTC!! bastards!!
muffinman5323 said:
tried zedomx method and even htc method both failed like 5 times..so i guess htc said **** you to anyone having 2.17.651.5..THANK YOU HTC!! bastards!!
Click to expand...
Click to collapse
Read carefully. I unrooted since i have hboot 1.50 and rerooted after taking the update just fine.
Sent from my PG86100 using xda premium
muffinman5323 said:
tried zedomx method and even htc method both failed like 5 times..so i guess htc said **** you to anyone having 2.17.651.5..THANK YOU HTC!! bastards!!
Click to expand...
Click to collapse
Read carefully. I unrooted since i have hboot 1.50 and rerooted after taking the update just fine.
Sent from my PG86100 using xda premium
muffinman5323 said:
well everything went smooth running the ruu EXCEPT!!! i still get remote : token check failed...WTF?
Click to expand...
Click to collapse
you likely copied the token incorrectly. No Spaces along the left edge.
htv dev gives: said:
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
HTC UNLOCK INSTRUCTIONS said:
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
(Note: Only copy the highlighted sections above.DO NOT COPY ANY SPACES/BLANKS! Do not copy the INFO or (bootloader) prefix)
Click to expand...
Click to collapse
This is quoted from my (extracted) official HTC Dev Unlocking instructions that have been stickied and are linked in my signature.
steve97ta said:
Read carefully. I unrooted since i have hboot 1.50 and rerooted after taking the update just fine.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
yea it still doesnt work..
muffinman5323 said:
yea it still doesnt work..
Click to expand...
Click to collapse
Downgrade the hboot. See the link in my signature.
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
I had the same thing happen. No clue how to make it work. Earlier hboot maybe...
Sent from my PG86100 using xda premium
Did you take the OTA?
Even if you didn't, I had the same problem.
What I had to do to fix it is run the RUU.
http://forum.xda-developers.com/showpost.php?p=30106576&postcount=20
Then do the HTC unlock crap again. It will then work.
You'll know because your phone will display a pop-up asking you if you want to unlock or not.
Didn't take the ota..
Sent from my PG86100 using xda premium
I would try it anyways. Can't hurt.
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
Click to expand...
Click to collapse
Have you tried the 2.89 RUU that was linked in post #3 above? I flashed it after using virus's firmware upgrade and taking the Sprint ICS OTA and it still ran fine for me. It should be the same as the OTA, but I have more confidence in the RUU.
ramjet73
halfaddict said:
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
Click to expand...
Click to collapse
FOUND SOLUTION..............
You have to download the RUU that matches the HTC Software on your phone. Go to settings > about > scroll down to Software Version and google search the RUU that matches.
Enable USB Debugging and let phone sit at home screen.
Run the RUU exe from withing windows on your PC wait for it to finish and and it will wipe phone in the process.
After it is done, boot to fastboot and run the HTC Unlock Token command again and this time you will get the prompt on the cell phone screen.
I spent 6 hours plus trying to root my wife phone wile tetherd from my Epic Touch GS2.
Samsung side of the world is a WHOLE lot easier. Everything is done within Oden for Samsung devices.
Anyway, there you go guys!
hypersonicx said:
FOUND SOLUTION..............
Click to expand...
Click to collapse
That's what I was recommending, except you don't have to relock your bootloader before running the RUU and unlock it after if you are S-OFF. And here's the downloads for the current RUU so others don't have to Google it.
Glad it worked for you.
ramjet73
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
htcdev.com said:
HTC has identified a known issue that may be experienced by some users with a Sprint EVO 3D that shipped with version 2.08.651.2, even if it was updated to a newer software version via FOTA. When attempting to unlock, a blank screen appears on the device after step 12 in the instructions and the process does not complete. As a workaround for users who experience this issue, we suggest you upgrade the ROM to 2.17.651.5 first via OTA then download and install the RUU from the table below to fix the issue before attempting the unlock process. This issue will also be fixed in the ICS update scheduled for EVO 3D.
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
ramjet73 said:
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
Click to expand...
Click to collapse
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
Click to expand...
Click to collapse
t3project said:
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
Click to expand...
Click to collapse
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
ramjet73 said:
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
Click to expand...
Click to collapse
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
The firmware updates don't update you 100% to the 2.89 build. You need to flash the 2.89 RUU to do that, as has already been pointed out in this thread, and for some reason the HTC unlock appears to work after that. I really don't know what the difference is between taking the OTA and flashing the RUU is, but they should be the same.
For someone like you that is already S-OFF, you could always flash the JuopunutBear 1.58.5858 bootloader if you need to run the 2.89 kernel and get most of the benefits of the ENG bootloader. However, that bootloader will not work properly with GB and AOSP ROM's.
ramjet73
i know this man!!! lol
t3project said:
i know this man!!! lol
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's good. Now you also know that flashing the 2.89.651.2 RUU.exe will let you do the HTC unlock with the 1.58 bootloader.
ramjet73
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
I concur. I'm not a novice when it comes to unlocking bootloaders & rooting phones. I've unlocked more bootloaders through htcdev.com than I can count & this gentleman is absolutely right! HTC really needs to get it together! Samsung devices are so much easier to work with. You don't run into these stupid little problems with Samsung phones. Usually, what goes for one Samsung device goes for all!
I digress, but anyhow, I'm well aware that reinstalling the operating system on an EVO 3D via an RUU will allow the token that you get from htcdev.com to work, and I have used this fix several times in the past on the last Gingerbread OS (Software version 2.17.651.5), but here's my issue. I have an EVO 3D with S-ON & a LOCKED bootloader that was updated over the air to ICS & when I go to unlock the bootloader via htcdev.com, nothing happens & HTC claimed that this issue would be fixed with the ICS update, but guess what? It wasn't!
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
So what I did from here is requested for someone from the XDA community to create a PG86IMG for me so that I could see about reinstalling the ICS OS on the phone through the bootloader (Shout outs to Karl! He came through on this right away. Karl you are the man!). Unfortunately, when I go to use the PG86IMG file, it does all of this loading & appears as if it's going to work but ultimately goes back to the HBOOT home screen & doesn't give me an option to install the f'n operating system! This sh*t blows & I am all out of ideas as to what to do from here. I am basically stuck.
On anther note, I tried to use the ICS RUU that I have on another EVO 3D with no success, but I was successfully able to reinstall the ICS operating system on this same EVO 3D via the PG86IMG file that Karl provided. What in the world is going on here?! If anyone can offer any helpful advice, I'd certainly appreciate it. Thanx in advance. (On a side note this other EVO 3D that I was able to reinstalled the ICS OS on via the PG86IMG file has an UNLOCKED bootloader & is S-OFF. I don't know if this makes any difference, but I thought I'd share this anyway.)
RioSoul said:
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
Click to expand...
Click to collapse
The 170 error means that the RUU.exe can't find your phone. Make sure the phone is in "fasboot USB" mode in the bootloader, then try running "fastboot devices" from the PC directory you used to root your phone. It should come back with a serial number that starts with "HT". If it doesn't, you may have a problem with the USB port on your phone, although it probably won't go into fastboot USB mode in the bootloader if that is the case. If you get the serial number, try running the RUU.exe again from there. If you get a 17x error with the RUU.exe, usually restarting it will get past that error as long as you have the proper connectivity to the phone.
ramjet73
achppr who
Confirmed, this worked for me. Thanks for your help! :good:
Help! My DNA isn't working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldn't mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Edit: Phone is now fixed, I went to IRC and a guy named Beaups took remote control and fixed it. Im not sure if thats his XDA username or not but if you guys see him make sure to give him a thanks Night everyone
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Its ok its very fixable, at this point. Just be very careful and very patient.
The worst thing you can do with something like this is get in a hurry or try to fix it while you're still very stressed out.
I'm passing on this advice because I almost screwed up yesterday because I made a boo boo and was in a huge hurry.
I'm going to wait for someone who knows more about this particular issue to chime in, but you have my word, I will help you resolve it after I do some more research while I wait for someone with more information or experience to post some info.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
In the original unlock downloader thread, there is a link to an irc chatroom, I would suggest you go there as well as look for help here, and be patient waiting for some one to respond ...
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Click to expand...
Click to collapse
Thats pretty much what I did but I keep getting that error:178 image file problem when its trying to finish (I am using the RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe RUU) Also my phone is recognized as 2.04 when I haven't flashed anything
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Re-Unlock your bootloader with your Unlock token (Unlock_code.bin) then do a fastboot flash recovery recovery.img and use the CWM recovery that is 6.0.2.8 (i believe is the most recent version) and you should be able to sideload your rom ... or if sideloading doesnt work just do an adb push rom.zip /sdcard/rom.zip and that will put the rom that you want to use on the root of the sdcard and then you can flash that there...
This should hopefully get you working again...
beasleyj62 said:
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Click to expand...
Click to collapse
I keep getting this when I flash the hboot
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.205s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.274s
and when I flash the Radio I get
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
error: cannot load 'PL83IMG.zip': Unknown error
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
beasleyj62 said:
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
Click to expand...
Click to collapse
I can unlock it at anytime....
see if you can flash after you unlock again
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
All I needed to run the RUU was the ENG Hboot. Flash it then you should be able to install the RUU provided you have the correct drivers installed.
Sent from my HTC6435LVW using xda app-developers app
He is still s-on.
Sent from my HTC Droid DNA
Andro X said:
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
How would I go about doing that?
beasleyj62 said:
see if you can flash after you unlock again
Click to expand...
Click to collapse
I didnt work. This is my 2nd DNA so I have done this before and it worked successfully(The first one had a screen problem)
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Halcyon7 said:
How would I go about doing that?
Click to expand...
Click to collapse
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
beasleyj62 said:
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I only found 1 link on my computer doctors forum but that link wasn't it
.torrented said:
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
Click to expand...
Click to collapse
No I haven't. I used the s-off facepalm method and I did everything as it said and now when I went into recovery nothing will mount and my device when trying to use the RUU says its a 2.04. So I didnt take the ota but thats what it is recognized as