Related
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:
I have started searching and am having a hard time finding exactly what I need. Anyway, I haven't used my Rezound since I got my S3 so I am not really up to speed on where the Rezound is in terms of OTA updates and whatnot. Right now my Rezound is S-Off on a engineering hboot (I believe) and rooted, but it was stock otherwise (up until I stopped using it).
I would like to get it back to 100% stock (other than S-Off, I will leave that as is for now). What is the easiest way to get there? I am assuming flashing an RUU of the latest stock build? If so, what is the latest stock build that I would get if I re-activated the phone and updated it (meaning I don't want any leaks or anything).
Also, it has been so long since I did any flashing on the phone, but what is the easiest way to flash a RUU (since I have never done that). And can I just flash the latest RUU without flashing anything else first?
Thanks, and sorry for all of the noob questions.
xceebeex said:
I have started searching and am having a hard time finding exactly what I need. Anyway, I haven't used my Rezound since I got my S3 so I am not really up to speed on where the Rezound is in terms of OTA updates and whatnot. Right now my Rezound is S-Off on a engineering hboot (I believe) and rooted, but it was stock otherwise (up until I stopped using it).
I would like to get it back to 100% stock (other than S-Off, I will leave that as is for now). What is the easiest way to get there? I am assuming flashing an RUU of the latest stock build? If so, what is the latest stock build that I would get if I re-activated the phone and updated it (meaning I don't want any leaks or anything).
Also, it has been so long since I did any flashing on the phone, but what is the easiest way to flash a RUU (since I have never done that). And can I just flash the latest RUU without flashing anything else first?
Thanks, and sorry for all of the noob questions.
Click to expand...
Click to collapse
Find the lastest RUU. I know its on android police. Place the file on the root of your SD card, check md5, rename to ph98img.zip, boot into bootloader and let it do its thing. You should be up to date.
EDIT: for you http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
topgun1953 said:
Find the lastest RUU. I know its on android police. Place the file on the root of your SD card, check md5, rename to ph98img.zip, boot into bootloader and let it do its thing. You should be up to date.
Click to expand...
Click to collapse
Thanks! Yea, I just found it on android police. I am assuming it won't wipe the SD card or anything right? Since I am S-OFF I don't have to worry about re-locking correct?
Also, will that RUU get it back to the point where someone could get the OTA's and everything as if it was 100% stock with S-ON?
EDIT: How come that 4.03.605.2 isn't listed on HTC website yet? Has it not been pushed out yet? The one listed on their site is the 3.14.605.12
xceebeex said:
EDIT: How come that 4.03.605.2 isn't listed on HTC website yet? Has it not been pushed out yet? The one listed on their site is the 3.14.605.12
Click to expand...
Click to collapse
4.03.605.2 is the latest leak. it has changes to make the rezound a Verizon global phone.
3.14.605.12 is the last nationwide OTA official ICS.
HowardZ said:
4.03.605.2 is the latest leak. it has changes to make the rezound a Verizon global phone.
3.14.605.12 is the last nationwide OTA official ICS.
Click to expand...
Click to collapse
Ok thanks! So I think I want to stick with the 3.14.605.12 then since I am trying to sell the phone. So if I am Unlocked and S-OFF can I just flash the RUU or do I have to relock first? And do I need to flash the gingerbread firmware patch?
s-off and unlocked is fine to ruu.
---------- Post added at 10:30 AM ---------- Previous post was at 10:28 AM ----------
s-off and unlocked is fine to ruu.
no patch needed
HowardZ said:
s-off and unlocked is fine to ruu.
Click to expand...
Click to collapse
Awesome, thanks! It won't wipe the SD card I am assuming right? Just the phone?
xceebeex said:
Awesome, thanks! It won't wipe the SD card I am assuming right? Just the phone?
Click to expand...
Click to collapse
my experience is it wipes the internal sd, but left the removable microSD card untouched.
HowardZ said:
my experience is it wipes the internal sd, but left the removable microSD card untouched.
Click to expand...
Click to collapse
Ok cool. That is what I would assume would happen. The only other question is if I need the GB firmware patch as well or does the RUU take care of everything?
Thanks for your help!
It takes care of everything
Sent from my ADR6425LVW using Tapatalk 2
mjones73 said:
It takes care of everything
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks everyone!
EDIT: Will it also stay "Locked" and S-OFF?
xceebeex said:
Thanks everyone!
EDIT: Will it also stay "Locked" and S-OFF?
Click to expand...
Click to collapse
Yes , running the RUU will not effect s-off status nor your bootloader locked status.
not to hijack the thread....but I have a question that relates to getting back to stock. I am running business sense, with the OTA. I would like to get the other global OTA.. I am s on. How do I go about doing that?
flash stock recovery
relock
run which RUU? the newest one is a PH file on android police
unlock
flash amon ra
flash new rom
does that sound right?
the part that I am questioning is the fact the global RUU is a PH file. But it says I have to be completly back to stock and locked.
any help would be greatly appreciated
Thanks
putney1477 said:
not to hijack the thread....but I have a question that relates to getting back to stock. I am running business sense, with the OTA. I would like to get the other global OTA.. I am s on. How do I go about doing that?
flash stock recovery
relock
run which RUU? the newest one is a PH file on android police
unlock
flash amon ra
flash new rom
does that sound right?
the part that I am questioning is the fact the global RUU is a PH file. But it says I have to be completly back to stock and locked.
any help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
I not sure about s on but I think you have to stock recovery and locke the hboot then runn the ruu on hboot
This is the latest one
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Why don't you s off before updating?
Kratz17 said:
I not sure about s on but I think you have to stock recovery and locke the hboot then runn the ruu on hboot
This is the latest one
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Why don't you s off before updating?
Click to expand...
Click to collapse
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
putney1477 said:
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
Click to expand...
Click to collapse
Ok I understand but whenever you decide to do it follow this guide its pretty easy.
http://forum.xda-developers.com/showthread.php?t=1696394
It says to be on a certain firmware but I have heard from other users that it's works with any ics firmware. Good Luck
putney1477 said:
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
Click to expand...
Click to collapse
I did s-off procedure a few months ago. it took several hours and kept failing. I used a large insulated paperclip with the insulating material removed from each end for good electrical contact.
What I had been doing wrong was not keeping the wire nice and straight in the hole. when the wire is not straight, it will not make good electrical contact with whatever is directly beneath the hole.
I just thought I'd share this tip in case it helps others.
regards,
Howard
p.s. There is no need to install the jbear modified hboot if you are uncomfortably with it. Installing the modified hboot is optional at the end of the s-off procedure. You will still have benefits of s-off with a htcdev unlocked bootloader while using a stock unlocked hboot. For example one can flash kernels via fastboot flash command with a stock hboot. s-off and jbear modified hboot are two separate modifications to the phone.
HowardZ said:
p.s. There is no need to install the jbear modified hboot if you are uncomfortably with it. Installing the modified hboot is optional at the end of the s-off procedure. You will still have benefits of s-off with a htcdev unlocked bootloader while using a stock unlocked hboot. For example one can flash kernels via fastboot flash command with a stock hboot. s-off and jbear modified hboot are two separate modifications to the phone.
Click to expand...
Click to collapse
actually, on a stock, locked HBoot, you CAN'T use any fastboot commands. That's why it's highly recommended to install the JBear HBoot, plus it gives you an easy option to do it and it does it without the user having to do anything
I have been trying for months to try and get back to stock in order to get S-OFF and rooted. I have tried many tut's and when I get to the RUU part, it stops me and prompts the error 140. Then I have gone to other websites and threads to find a solution to the problem but I haven't found a successful one.
As of right now this is what I have when I go into bootloader:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1. 58.0000
eMMC-boot
May 17 2012,15:06:44
lxbeale said:
I have been trying for months to try and get back to stock in order to get S-OFF and rooted. I have tried many tut's and when I get to the RUU part, it stops me and prompts the error 140. Then I have gone to other websites and threads to find a solution to the problem but I haven't found a successful one.
As of right now this is what I have when I go into bootloader:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1. 58.0000
eMMC-boot
May 17 2012,15:06:44
Click to expand...
Click to collapse
What RUU are you trying to run? Since you are S-ON with hboot 1.58 the only version that should work is the Sprint ICS (2.89.651.2) version.
If you issue the following commands from fastboot you can verify that you have correct CID and man version (mainver) to flash that RUU:
fastboot getvar cid
fastboot getvar mainver
Click to expand...
Click to collapse
ramjet73
ramjet73 said:
What RUU are you trying to run? Since you are S-ON with hboot 1.58 the only version that should work is the Sprint ICS (2.89.651.2) version.
If you issue the following commands from fastboot you can verify that you have correct CID and man version (mainver) to flash that RUU:
ramjet73
Click to expand...
Click to collapse
Do you have a link to a RUU that would work? And I was trying RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
lxbeale said:
Do you have a link to a RUU that would work? And I was trying RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Click to expand...
Click to collapse
Yea, that's the latest GB version but won't flash over the Sprint ICS build.
Here's the one you want.
ramjet73
ramjet73 said:
Yea, that's the latest GB version but won't flash over the Sprint ICS build.
Here's the one you want.
ramjet73
Click to expand...
Click to collapse
I downloaded it and ran it, It got about 3 minutes into it and then gave me ERROR[132]: Signature error
lxbeale said:
I downloaded it and ran it, It got about 3 minutes into it and then gave me ERROR[132]: Signature error
Click to expand...
Click to collapse
Did you ever run the fastboot commands posted above to display your CID and mainver? If so, what were the values they returned?
Also, did you check the MD5 for the RUU.exe file after you downloaded it? I know that RUU.exe is good because there have been almost 1400 downloads without any problems reported.
Is the phone in "fastboot USB" mode when you start the RUU.exe? Here's a post with some more RUU.exe troubleshooting tips that might help.
ramjet73
ramjet73 said:
Did you ever run the fastboot commands posted above to display your CID and mainver? If so, what were the values they returned?
Also, did you check the MD5 for the RUU.exe file after you downloaded it? I know that RUU.exe is good because there have been almost 1400 downloads without any problems reported.
Is the phone in "fastboot USB" mode when you start the RUU.exe? with some more RUU.exe troubleshooting tips that might help.
ramjet73
Click to expand...
Click to collapse
I Got SPCS_001 and 2.89.651.2,
I did not check the MD5 because I have no clue what that is,
It was in fastboot usb mode when I started it.
lxbeale said:
I Got SPCS_001 and 2.89.651.2,
I did not check the MD5 because I have no clue what that is,
It was in fastboot usb mode when I started it.
Click to expand...
Click to collapse
You have the correct CID and mainver for the Sprint ICS build, so that looks good.
Have you tried a different USB cable and/or another PC? Based on everything I've seen in this thread so far you are doing things right, but something may be corrupting the RUU as it's being flashed.
ramjet73
I have tried different cables but not different PC's, I will give it another go with my laptop
ramjet73 said:
You have the correct CID and mainver for the Sprint ICS build, so that looks good.
Have you tried a different USB cable and/or another PC? Based on everything I've seen in this thread so far you are doing things right, but something may be corrupting the RUU as it's being flashed.
ramjet73
Click to expand...
Click to collapse
I have tried a different cable but not a different PC, I will have another go with my laptop
lxbeale said:
I have tried a different cable but not a different PC, I will have another go with my laptop
Click to expand...
Click to collapse
I just tried using my laptop and got Error 170, so I tried a different cord and that didn't work, I then thought that the file may have been corrupted and re downloaded it and still got the same problems. I then went to go and see if the other RUU (2.17) would connect to the phone and it did but still got me the error 140. Would I need to use another PC or what, cause I don't know where to go from here
lxbeale said:
I just tried using my laptop and got Error 170, so I tried a different cord and that didn't work, I then thought that the file may have been corrupted and re downloaded it and still got the same problems. I then went to go and see if the other RUU (2.17) would connect to the phone and it did but still got me the error 140. Would I need to use another PC or what, cause I don't know where to go from here
Click to expand...
Click to collapse
Let's take a different approach.
Try downloading the 2.89.651.2 RUU (the first one) from this post, place it in the root of your SD card and rename it to PG86IMG.zip, then start your bootloader and press the power button once. That should give you a prompt to authorize the installation so go ahead and do that.
This approach will eliminate both the cable and the PC as possible causes of the problem.
ramjet73
ramjet73 said:
Let's take a different approach.
Try downloading the 2.89.651.2 RUU (the first one) from , place it in the root of your SD card and rename it to PG86IMG.zip, then start your bootloader and press the power button once. That should give you a prompt to authorize the installation so go ahead and do that.
This approach will eliminate both the cable and the PC as possible causes of the problem.
ramjet73
Click to expand...
Click to collapse
I performed this twice on two different computers using different cords each time and when I went into the bootloader, on the top right it went through a blue and then a brown loading bar and then went back to bootloader doing nothing
lxbeale said:
I performed this twice on two different computers using different cords each time and when I went into the bootloader, on the top right it went through a blue and then a brown loading bar and then went back to bootloader doing nothing
Click to expand...
Click to collapse
Did you try flashing the zip version that I linked in my last post from the bootloader?
ramjet73
ramjet73 said:
Did you try flashing the zip version that I linked in my last post from the bootloader?
ramjet73
Click to expand...
Click to collapse
Yes I did, do you think if I would root my phone again and then relock it, this could be fixed?
lxbeale said:
Yes I did, do you think if I would root my phone again and then relock it, this could be fixed?
Click to expand...
Click to collapse
I really don't know what the problem is but you would definitely have a better chance of fixing it if you are S-OFF. You could unlock the bootloader, flash a custom recovery and then a stock rooted ROM and try the wire trick. If you can get that to work you should definitely be able to flash the RUU.
There is a stock rooted version of the Sprint ICS ROM in this post.
ramjet73
ramjet73 said:
I really don't know what the problem is but you would definitely have a better chance of fixing it if you are S-OFF. You could unlock the bootloader, flash a custom recovery and then a stock rooted ROM and try the wire trick. If you can get that to work you should definitely be able to flash the RUU.
There is a stock rooted version of the Sprint ICS ROM in this post.
ramjet73
Click to expand...
Click to collapse
Okay so I unlocked my bootloader and put 4ext recovery on, but I am still having problems flashing firmware, it goes to a loading bar then it says it is parsing then returns back to the bootloader
lxbeale said:
Okay so I unlocked my bootloader and put 4ext recovery on, but I am still having problems flashing firmware, it goes to a loading bar then it says it is parsing then returns back to the bootloader
Click to expand...
Click to collapse
Unlocking your bootloader and installing a custom recovery is considered "rooting" and not the same as being S-OFF. If you want to flash PG86IMG.zip files from your bootloader you will have to perform the wire trick procedure to get radio S-OFF.
ramjet73
ramjet73 said:
Unlocking your bootloader and installing a custom recovery is considered "rooting" and not the same as being S-OFF. If you want to flash PG86IMG.zip files from your bootloader you will have to perform the wire trick procedure to get radio S-OFF.
ramjet73
Click to expand...
Click to collapse
But in order to do the wire trick, you have to be on a stock RUU and at the moment I am not. I tried installing the stock rom but all its getting me is to the sprint loading screen when trying to boot. Will the wire trick still work?
lxbeale said:
But in order to do the wire trick, you have to be on a stock RUU and at the moment I am not. I tried installing the stock rom but all its getting me is to the sprint loading screen when trying to boot. Will the wire trick still work?
Click to expand...
Click to collapse
According to the OP of this thread you have hboot 1.58 and should be able to boot a rooted stock Sprint ICS ROM. Did you do a wipe before you flashed it?
If you can't get the rooted stock ROM working you can try doing the wire trick with a "stockish" ROM like MeanROM 2.6. That's not supported by the JBear team but it's worked for some users.
You can't use a GB stock ROM because it won't boot with 1.58, so that's not an option.
ramjet73
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
therreid said:
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
Click to expand...
Click to collapse
You either need to wait, or try search how to revert the update.
dafuzzbudd said:
You either need to wait, or try search how to revert the update.
Click to expand...
Click to collapse
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
dkkunkel said:
Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. ..
Click to expand...
Click to collapse
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
pmcall said:
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
Click to expand...
Click to collapse
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
Were you rooted with s-off, or s-on?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
dkkunkel said:
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
Click to expand...
Click to collapse
Prior to update coming out, I have not installed the OTA.
junkmail9 said:
Were you rooted with s-off, or s-on?
Click to expand...
Click to collapse
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
dkkunkel said:
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
Click to expand...
Click to collapse
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
junkmail9 said:
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
Click to expand...
Click to collapse
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
stevey500 said:
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
Click to expand...
Click to collapse
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
junkmail9 said:
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
Click to expand...
Click to collapse
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
stevey500 said:
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
Click to expand...
Click to collapse
Anyone figure out if this works?? DirtyRacun after OTA I mean. thanks
join in for the unbelievable ... post2014-OTA [S-OFF] has been achieved
http://forum.xda-developers.com/showthread.php?t=2664460