Related
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...
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.
Hi,
I am unable to unlock my HTC EVO 3D.
It's currently running : RUU_Shooter_U_hTC_Asia_WWE_1.22.707.2_Radio_10.55.9020.00_10.13.9020.29_M_release_207422_signed
I've gone to the htcdev site, submitted the identifier token; received the unlock_code.bin file; followed their instruction and got this :
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s
-------------------------------------------------------------------------
I've also tried using a GoldCard thinking I could load another region's RUU but didn't work either
I've tried almost everything and so I am turning to the xda gurus. Please help
mainboardnya prnah diganti?
Not sure if the motherboard has been changed. (Tak pasti jika motherboardnya pernah diganti)
Sent from my HTC EVO 3D X515m using XDA
mine cant be unlock again after htc replaced the board. many user had this problem too.
I am facing the same problem. Any other solution?
You can try to run the RUU first and then try to unlock it again. It solves most problems
I'm having the same problem HBOOT versiyon 1.49.0018 Do not have a solution ?
Did you managed to unlock it ? Mine also came back from HTC repair (after bricking it ), and I cannot unlock it for the same reason : 'unlock token check failed'
Why are u trying it the way use rev.io
Sent from my HTC EVO 3D X515m using XDA Premium App
It's so easy to get s-off now that you should just do that really. It also allows for more reliable flashing of ICS ROMs than s-on.
Sent from my PG86100 using Tapatalk 2
geordie 34 said:
Why are u trying it the way use rev.io
Sent from my HTC EVO 3D X515m using XDA Premium App
Click to expand...
Click to collapse
Thank (button used) you. It worked fine
kitarolivier said:
Thank (button used) you. It worked fine
Click to expand...
Click to collapse
u got the supported hboot by rev ??? mine was 1.49.00011
I am having the same problem, i have my board replaced because of Frequent BOOT LOOPS
after that i am not able to unlock the boot loader. Even i tried to install the Latest Asian RUU in my phone it gave me error. 131 Customer Code do not match
Then i went to fastboot and just gave command
for changing the cid, and it worked! without evan unlocking the bootloader
before my cid was 038, now in CID Getter it shows 001, So hopefully that worked
and after that again i tried to run the RUU but still the same error!
So dont know now what to do ?
skchokshi said:
I am having the same problem, i have my board replaced because of Frequent BOOT LOOPS
after that i am not able to unlock the boot loader. Even i tried to install the Latest Asian RUU in my phone it gave me error. 131 Customer Code do not match
Then i went to fastboot and just gave command
for changing the cid, and it worked! without evan unlocking the bootloader
before my cid was 038, now in CID Getter it shows 001, So hopefully that worked
and after that again i tried to run the RUU but still the same error!
So dont know now what to do ?
Click to expand...
Click to collapse
which tutorial you used for changing the cid mate? and where i can find the latest asian ruu? tks
klebengan said:
which tutorial you used for changing the cid mate? and where i can find the latest asian ruu? tks
Click to expand...
Click to collapse
I used this guide to crack the bootloader
http://forum.xda-developers.com/showthread.php?t=1471246
In this guide it says first we have have to bootloader but, just skip that part.
Temp Root your phone with automated scripts (HTC Super Tool V3)
And then you do as the guide says. It is working
My bootloader was locked too. After downgrading your phone, just unlock the bootloader with Revolutionary Method.
Then install 4EXT Recovery. And then you can install custom Roms.
Solution for your problem?
kitarolivier said:
Did you managed to unlock it ? Mine also came back from HTC repair (after bricking it ), and I cannot unlock it for the same reason : 'unlock token check failed'
Click to expand...
Click to collapse
Have you solved the problem with unlock the bootloader? I have the same problem at the moment. So if you know how to fix it.........
Same problem
sgremmen said:
Have you solved the problem with unlock the bootloader? I have the same problem at the moment. So if you know how to fix it.........
Click to expand...
Click to collapse
Already a solution how to unlock the bootloader?
Hi, i recently bought a replacement EVO 3D and i am having trouble unlocking it. I was able to unlock my first 3D which had the exact same software versions with no problem.
I have HBOOT 1.58 and the latest Sprint OTA ICS update.
When i go through the CMD part and enter the following:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
nothing happens.
CMD shows the following:
C:\sdk-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.160s
Click to expand...
Click to collapse
but I don't receive an option to accept on my phone it just stays in the bootloader menu. Has anyone had this issue? Thanks
I know this doesn't help but I did have the problem with one EVO 3d I had with hboot 1.5 so I returned it and luckily got another with 1.4...spent 8 hours trying to unlock that one and never did get answers
Sent from my PG86100 using Tapatalk 2
Well first is the code.bin in it folder were it shud be?
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Jmurphy8367 said:
Well first is the code.bin in it folder were it shud be?
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Click to expand...
Click to collapse
Yes, it is sitting in the main folder with the other files. I followed the same steps i used before which worked on my old EVO 3D, but are not working on this one. Thanks.
All drivers and HTC sync good to go?
EVO 3DIZZLE
S-Off
hboot 1.58
Jmurphy8367 said:
All drivers and HTC sync good to go?
EVO 3DIZZLE
S-Off
hboot 1.58
Click to expand...
Click to collapse
Yes, I also tried uninstalling and reinstalling the drivers..and I tried a second computer. I have no idea what could be wrong, Is there an official RUU out yet from sprint for the new OTA ICS that I should install on it?
Here's my s-off folder put it on it hardisk its got fast boot adb and recovery put the code.bin in there and try it
EVO 3DIZZLE
S-Off
hboot 1.58
---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------
http://db.tt/T6eecDpL
EVO 3DIZZLE
S-Off
hboot 1.58
The same thing happened. Command Prompt returns the following:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
But nothing happens on my phone screen. Still stuck at the screen that says Fastboot USB in red. The window asking me if i want to unlock bootloader does not come up.
Robot818 said:
Hi, i recently bought a replacement EVO 3D and i am having trouble unlocking it. I was able to unlock my first 3D which had the exact same software versions with no problem.
I have HBOOT 1.58 and the latest Sprint OTA ICS update.
When i go through the CMD part and enter the following:
nothing happens.
CMD shows the following:
but I don't receive an option to accept on my phone it just stays in the bootloader menu. Has anyone had this issue? Thanks
Click to expand...
Click to collapse
Did you get a new token file for your replacement phone?
I would submit the file you capture from your phone and get a new token again just in case something went wrong the first time.
I "re unlocked" my phone after 1.58 using the same binary file I had from when I previously unlocked it.
sonza said:
Did you get a new token file for your replacement phone?
I would submit the file you capture from your phone and get a new token again just in case something went wrong the first time.
I "re unlocked" my phone after 1.58 using the same binary file I had from when I previously unlocked it.
Click to expand...
Click to collapse
Thanks for your reply, I just tried getting a new token again and still haven't been able to get the unlock bootloader option to pop. I've actually requested a new token three times now and and still nothing.
Just to let anyone else know that might have this same problem, i was able to fix this by running the RUU found here: http://forum.xda-developers.com/showthread.php?t=1827712
My phone is finally unlocked!
Robot818 said:
Thanks for your reply, I just tried getting a new token again and still haven't been able to get the unlock bootloader option to pop. I've actually requested a new token three times now and and still nothing.
Click to expand...
Click to collapse
Ok, the fact that is says sending with 0KB would seem to me that it is not actually reading the darn .bin file.
Now this might seem stupid, but we are shooting totally in the dark here.
First, I have my folder that has adb and all the other files in the root of the hard drive. It is called rootevo, just to keep the folder name short. While it usually should not matter, I knew we would be running adb from a command box, and that can sometimes cause issues with folder and file names longer than 8 characters.
If the phone is booted, plug it in and you should be able to type "adb reboot bootloader" and the phone should reboot to the bootloader screen. If this works, I would try and do the unlock process again. Make sure you are typing in the name exactly as it is named in the folder.
The other option would be to boot straight to bootloader after a battery pull. Again, not sure why it would matter, but you have a strange one here, so the fix could end up being equally strange.
Good luck! :laugh:
i guy's can you help us
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.172s
what is the solution of this error.???
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: