So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
Related
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
antiseen said:
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
Just s-off on GB. You can do it on ICS or GB works the same way. Just if you RUU to ICS you will have to reunlock to soff.
Once s-off he can flash any ruu he wants in any order and keep s-off.
Also on a secondary note, you must have not had a thunderbolt when we first got s-off as getting s-off manually took about 30+ mins of constant cmd line use.
S-off on the rezound is much easier than it sounds. The only part that gives people trouble is the wire trick and mainly because it is all about timing.
Sent from my ADR6425LVW using XDA
I will say this outright: you can S-off right now using the GB package option on unlimited.io since that is the firmware you have. Answering the rest of this assuming an upgrade to ICS firmware, but that is the simplest path.
antiseen said:
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms).
Click to expand...
Click to collapse
Correct. If you're patching the firmware is still Gingerbread. Check in the bootloader for "hboot 2.11" to confirm this. Only way you can update firmware and radios while S-on is to run a RUU.
antiseen said:
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
Click to expand...
Click to collapse
When a phone gets an OTA update, it is expecting you to be on the latest official release. That currently is the 2.01.605.11 Gingerbread build, the first OTA we had. That means you need to be on the GB firmware, and stock everything else, not on ICS firmware.
That said, last part is correct: You would re-lock, flash an ICS RUU, unlock again, put recovery back on, and either flash a pre rooted stock ROM based on the leaks, or root the stock ROM yourself. Then you are on ICS firmware, ready for S-off.
antiseen said:
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
Click to expand...
Click to collapse
Leave the ROM. Do a nandroid backup. Re-lock and flash the RUU. You can restore the nandroid afterwards, just be sure to repatch the thing to new ICS firmware if you go that route. Check second listing in the Roll Up Sticky post in the Dev section.
antiseen said:
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
Unlimited.io has files for GB firmware and the first three out of four ICS leaks. Note this last leak, the fourth one, is compatible with the unlimited.io files for the third leak ("5/7 leak"). So little was changed, so you're safe going with that combo if you wish.
nosympathy said:
Also on a secondary note, you must have not had a thunderbolt when we first got s-off as getting s-off manually took about 30+ mins of constant cmd line use.
Click to expand...
Click to collapse
You're actually right. I didn't get my TB til June and I spent months reading how to get s-off and finally did it in...august or september, I forget. It was MUCH easier by then.
I was familiar with the original process(only by reading, but felt confident in doing it that way) but by the time I was done learning everything about it, revolutionary method came out and I did it that way.
I know that I can get s-off right now on his gingerbread firmware, my only question is what happens when ICS does get released and all the good ROMS start to come out? I want to get him on an AOSP rom when they come out. I feel like he'll be stuck on gingerbread firmware and when it comes time to flash any of the ICS roms, he'll be clueless. I could figure out how to do it if it required an extra step or two but explaining that to him might be a bit much. I'd rather him be geared for ICS (he has no intention of going back to gingerbread, ever).
Also, I was under the impression that flashing a RUU would make it S-on. So if I ever wanted to upgrade his firmware to ICS we would have to do the wire trick again to achieve s-off once more.
Anyway, Thanks a ton guys for your feedback already. Love this community and you're both a great help. Thanks for the clarification/instructions phantasm.
antiseen said:
I feel like he'll be stuck on gingerbread firmware and when it comes time to flash any of the ICS roms, he'll be clueless. I could figure out how to do it if it required an extra step or two but explaining that to him might be a bit much. I'd rather him be geared for ICS (he has no intention of going back to gingerbread, ever).
Click to expand...
Click to collapse
Hop through S-off with the GB files from unlimited.io. Keep the stock bootloader for now rather than flashing the JuopunutBear hboot when their program asks you. (Note S-off makes the bootloader "Locked" again, but the JB files are hacked so you can use them *as if* they are Unlocked status... handy and makes it simpler to get the phone ready for warranty exchanges again. But! We want to make sure we get ICS firmware and radios first...then slap on an *ICS* JB bootloader...)
antiseen said:
Also, I was under the impression that flashing a RUU would make it S-on. So if I ever wanted to upgrade his firmware to ICS we would have to do the wire trick again to achieve s-off once more.
Click to expand...
Click to collapse
Nope. Once you achieve S-off you keep S-off. The only thing that affects S-off is turning the flag back on manually yourself with some fastboot commands.
So now you will be S-off and with a Locked stock bootloader. Download the RUU from the 6/10 leak here, rename to just PH98IMG.zip and flash it in bootloader:
http://www.androidfilehost.com/main/-Support_Files-/RUU/Vigor/RUU_Vigor_3.14.605.10_PH98IMG.zip
Then grab "[ICS][2.25][JB][5-7]PH98IMG.zip" from SuperChilPil's repository. (Note the 6/10 leak and the 5/7 leak have the same bootloaders just like the first pair of leaks did, so this is fine to use.) Rename to PH98IMG.zip and flash in bootloader:
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
This will make you S-off with a JuopunutBear hacked hboot, running the latest firmware and ROM available. Choose a recovery to flash, preferably TWRP or AmonRa. ClockworkMod has charging issues, there is a fix floating around thanks to NilsP and his own source if you insist. You can then proceed to flash the ICS custom ROM of your choice.
TWRP:
http://forum.xda-developers.com/showthread.php?t=1613576
AmonRa:
http://forum.xda-developers.com/showthread.php?t=1339679
CWM (fixed):
http://forum.xda-developers.com/showthread.php?t=1722989
Edit: User zhp pilot claims this version of CWM is also not functioning properly at this time, see the thread. Proceed with caution on CWM.
And don't forget to make a splash screen now that you are S-off lol, stop blinding yourself with that white HTC screen:
http://forum.xda-developers.com/showthread.php?t=1615811
~~~
Other useful files for S-off if you don't have them on the PC... The latest HTC drivers (extracted from HTC Sync so you don't have to download all of that) and an adb/fastboot mini console:
https://rapidshare.com/files/1796700693/HTCDriver_3.0.0.021.exe
http://rapidlibrary.com/files/adb-fastboot-and-other-tools-zip_ulcmnmxxtci89on.html
antiseen said:
Anyway, Thanks a ton guys for your feedback already. Love this community and you're both a great help. Thanks for the clarification/instructions phantasm.
Click to expand...
Click to collapse
Nope, thanks you for asking.
antiseen said:
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
In order to S-off the Rezound, you need to be HTCDEVunlocked, Rooted and on Stock Rom.
Hi all! This is my first post and hope it's not too silly of a question. I am currently using a Thunderbolt but very likely will be upgrading to a Rezound (I have both phones now). I know the ICS OTA is out for Rezound. I want to get root and S-off on Rezound running the stock ICS OTA, but I am not sure about the order of events.
1. Should I get S-off and root on the stock Gingerbread rom per the instructions in this thread (http://forum.xda-developers.com/showthread.php?t=1823362), and then upgrade to the ICS OTA? Or should I upgrade the stock Gingerbread to ICS OTA and then attempt to get S-off and root?
2. Is a confirmed s-off/root procedure out for the stock ICS OTA? sorry if I missed it - I promise I did my best searching through the forum before posting
I thought I'd start with the stock ICS OTA rom so I'll get a baseline for when I try out other roms down the road. And from what I've read here, the stock rom is probably a little bit more robust for day to day (correct me if I am wrong!). I hate the verizon bloatware and I think I'd be happy for a while if I can have S-off and root on the stock ICS.
thanks in advance for any help!
from scratch
Hiya, You're getting ready to become addicted to roms, by the way.
All your choices are kind of 'what do you want' things, but assuming you
receive it with stock Gingerbread, easiest thing would be to:
1 unlock by way of HTC Development instructions - lots of info here on xda
2 flash Cleanrom 175 a gingerbread stockish rooted rom
3 do the S-0ff thing with Juopunutbear, being careful not to amend or skip
any instructions in the S-0ff recipe (critical).
4 now your phone is s-0ff and locked. leave it just that way: no unlocks ever needed again and no pink warnings
5 flash Android police newest ICS RUU
6 flash amon ra as a PBIMG in recovery
7 use amon ra to wipe and install ANYTHING you want
haha Yeah roms are pretty addictive! So my background in rooting is limited to the Thunderbolt, which is my first smartphone. I used the Revolutionary IO method, which got me S-Off and root. But after reading through the Juopunutbear (Unlimited IO), I am slightly confused. I definitely did not do the wiring procedures involving the antennae contacts to get S-Off with the thunderbolt. I did more research and it sounds like the S-Off in thunderbolt is a "fake" S-off from a patched hboot?
That also leads to my next questions... up until now, I thought the following:
1. hboot = bootloader, which is the "BIOS" of the phone
2. In order to be rooted, S-off must happen first (this I guess is not true from your steps)
3. Recovery = part of hboot (from what I've read so far, this is incorrect too)
Also, would you elaborate on step #4? I thought unlocked is what I want, but instead I really want to have S-off and locked bootloader?
Thanks!
michaelbsheldon said:
Hiya, You're getting ready to become addicted to roms, by the way.
All your choices are kind of 'what do you want' things, but assuming you
receive it with stock Gingerbread, easiest thing would be to:
1 unlock by way of HTC Development instructions - lots of info here on xda
2 flash Cleanrom 175 a gingerbread stockish rooted rom
3 do the S-0ff thing with Juopunutbear, being careful not to amend or skip
any instructions in the S-0ff recipe (critical).
4 now your phone is s-0ff and locked. leave it just that way: no unlocks ever needed again and no pink warnings
5 flash Android police newest ICS RUU
6 flash amon ra as a PBIMG in recovery
7 use amon ra to wipe and install ANYTHING you want
Click to expand...
Click to collapse
yep
yo!
hboot is bootloader alright: some folks like a modified hboot which lets you do more than stock hboot.
personally I keep the stock ICS hboot 2.25.
nope, you dont have to be s-0ff to be rooted, only unlocked.
You can do most all modifications with unlock EXCEPT go back to previous hboot & rom.
Recovery is separate from hboot. Recovery is a menu choice in hboot.
A new recovery can only be installed if unlocked or s-0ff.
There's ClockworkMod and AmonRa. You'll wanna check them out both, I like Amon Ra.
re: step #4.
I know it's counterintuitive, but if you unlock it again after s-0ff, even though it's s-0ff, you will
have a nasty PINK Tampered flag every time you boot to hboot/custom recovery. And that crappy reminder stays
even after you you relock. The Juopunutbear process relocks the phone, making it S-0ff, Locked. Perfect.
Now with S-0ff, locked or unlocked doesn't matter regarding any roms or radios you may install and No warning flags.
Dont be intimidated by the wire procedure for s-0ff, just read it so many times beforehand that you effen KNOW it.
Enjoy: my Zound is so fast cool and perfect now that ive customized it to my useage pattern - hoping for
same experience for you!.
dashbored said:
Hi all! This is my first post and hope it's not too silly of a question. I am currently using a Thunderbolt but very likely will be upgrading to a Rezound (I have both phones now). I know the ICS OTA is out for Rezound. I want to get root and S-off on Rezound running the stock ICS OTA, but I am not sure about the order of events.
1. Should I get S-off and root on the stock Gingerbread rom per the instructions in this thread (http://forum.xda-developers.com/showthread.php?t=1823362), and then upgrade to the ICS OTA? Or should I upgrade the stock Gingerbread to ICS OTA and then attempt to get S-off and root?
2. Is a confirmed s-off/root procedure out for the stock ICS OTA? sorry if I missed it - I promise I did my best searching through the forum before posting
I thought I'd start with the stock ICS OTA rom so I'll get a baseline for when I try out other roms down the road. And from what I've read here, the stock rom is probably a little bit more robust for day to day (correct me if I am wrong!). I hate the verizon bloatware and I think I'd be happy for a while if I can have S-off and root on the stock ICS.
thanks in advance for any help!
Click to expand...
Click to collapse
I basically had the exact same questions. Here's what I figured out:
S-Off, then Stock Recovery, then ICS OTA:
http://forum.xda-developers.com/showthread.php?t=1821303
After post #6, go to the next link...
... Then flash AR Recovery 3.15:
http://forum.xda-developers.com/showthread.php?t=1827263
I had to unlock my hboot again, which means I wiped my data... However, I've read that adding a custom hboot is very risky, since your phone can't run anything if this gets screwed up. I'm no expert, but this is what I've read. So re-unlocking felt safer to me, even if it was probably a little more hassle. Better than bricking, imo.
A word of caution about custom recovery: Clockwork Mod (CWM) has a serious bug that does not allow the Rezound to charge properly! When my battery died, I had to use my wife's Thunderbolt to charge the battery before I could turn my Rezound back on... A royal pain. I installed AR Recovery, and it's perfect.
... Then continue at the first link at post #7 for how to use AR Recovery to flash superSU to restore root.
I'm thinking about writing up a simple guide, since that was the hardest thing for me to find through this process.
Rezound
AR Recovery 3.15
Stock hboot
ICS OTA
Rooted
I sold the Thunderbolt today and so now I've officially transitioned over to the Rezound! The phone is the stock gingerbread. I am dying to root it if only just so I can use titanium back up to transfer my crap over.
Thanks guys for the helpful replies! I've decided that right now, what I want is to be on the ICS OTA but with S-off & root so I can remove the bloat and optimize it. I'll stay with that for a bit to get a baseline before trying out different ROMs
What kind of wires did you guys use for the S-off procedure? Do I need to go out and buy something specific, or is there something around the typical household setting that I can grab? Obviously, not frying the phone is top priority. I've read through too much posts in the past 48 hours and I've come across a few that mentioned fried USB ports and even dead phones that had to be returned, which's made me a bit tentative. But I want S-off, so any pointers/comments you may have that would help about this would be much appreciated!
michaelbsheldon - question about your steps #1 & #2. Aren't these extraneous steps, as in you could just do the S-off wire with the stock Gingerbread? I am kinda confused as to the purpose of unlocking it first via HTC Dev and flashing a stockish ROM before the wire trick.
bloodymurderlive said:
I basically had the exact same questions. Here's what I figured out:
S-Off, then Stock Recovery, then ICS OTA:
http://forum.xda-developers.com/showthread.php?t=1821303
After post #6, go to the next link...
... Then flash AR Recovery 3.15:
http://forum.xda-developers.com/showthread.php?t=1827263
I had to unlock my hboot again, which means I wiped my data... However, I've read that adding a custom hboot is very risky, since your phone can't run anything if this gets screwed up. I'm no expert, but this is what I've read. So re-unlocking felt safer to me, even if it was probably a little more hassle. Better than bricking, imo.
A word of caution about custom recovery: Clockwork Mod (CWM) has a serious bug that does not allow the Rezound to charge properly! When my battery died, I had to use my wife's Thunderbolt to charge the battery before I could turn my Rezound back on... A royal pain. I installed AR Recovery, and it's perfect.
... Then continue at the first link at post #7 for how to use AR Recovery to flash superSU to restore root.
I'm thinking about writing up a simple guide, since that was the hardest thing for me to find through this process.
Rezound
AR Recovery 3.15
Stock hboot
ICS OTA
Rooted
Click to expand...
Click to collapse
Thanks for the tip about the CWM recovery! As I no longer have a thunderbolt, I would've been totally screwed. Question though - it sounds like you did what michaelbsheldon said not to do, re-unlock after you're S-off. Do you have the pink flag that he mentioned?
So here's my plan to get my Rezound into a S-off, rooted ICS OTA - please let me know if it's valid:
1a (waiting for michaelbsheldon reply if truly necessary, or if can proceed on stock GB) - HTC Dev unlock and flash Cleanrom 175
1. S-off wire procedure
2. Apply ICS OTA update
3. Apply global roaming update (if available? read about this in the past few days)
4. Since no need to unlock, flash appropriate Superuser for ICS OTA (will google, or if anyone would like to help make sure I find the right one, please feel free to link )
5. flash Amonra recovery. Keep stock hboot.
6. Install root explorer to delete VZ bloatware and titanium backup to restore apps and data from Thunderbolt
dashbored said:
Thanks for the tip about the CWM recovery! As I no longer have a thunderbolt, I would've been totally screwed. Question though - it sounds like you did what michaelbsheldon said not to do, re-unlock after you're S-off. Do you have the pink flag that he mentioned?
So here's my plan to get my Rezound into a S-off, rooted ICS OTA - please let me know if it's valid:
1a (waiting for michaelbsheldon reply if truly necessary, or if can proceed on stock GB) - HTC Dev unlock and flash Cleanrom 175
1. S-off wire procedure
2. Apply ICS OTA update
3. Apply global roaming update (if available? read about this in the past few days)
4. Since no need to unlock, flash appropriate Superuser for ICS OTA (will google, or if anyone would like to help make sure I find the right one, please feel free to link )
5. flash Amonra recovery. Keep stock hboot.
6. Install root explorer to delete VZ bloatware and titanium backup to restore apps and data from Thunderbolt
Click to expand...
Click to collapse
I'm going to give you a response this afternooon... I recommend that you don't do anything until I can clarify some things. brt...
dashbored said:
Thanks for the tip about the CWM recovery! As I no longer have a thunderbolt, I would've been totally screwed. Question though - it sounds like you did what michaelbsheldon said not to do, re-unlock after you're S-off. Do you have the pink flag that he mentioned?
So here's my plan to get my Rezound into a S-off, rooted ICS OTA - please let me know if it's valid:
1a (waiting for michaelbsheldon reply if truly necessary, or if can proceed on stock GB) - HTC Dev unlock and flash Cleanrom 175
1. S-off wire procedure
2. Apply ICS OTA update
3. Apply global roaming update (if available? read about this in the past few days)
4. Since no need to unlock, flash appropriate Superuser for ICS OTA (will google, or if anyone would like to help make sure I find the right one, please feel free to link )
5. flash Amonra recovery. Keep stock hboot.
6. Install root explorer to delete VZ bloatware and titanium backup to restore apps and data from Thunderbolt
Click to expand...
Click to collapse
It doesn't matter much if you do the OTA update before or after s-off. If it were me, I would do the OTA update first, especially if you are still locked....then unlock and do s-off using the proper ICS (for .5) jounuputbear. You can keep the stock hboot. NO NEED to unlock after s-off! AFter s-off, flash your Amonra recovery and then flash your SU...or just flash a rooted ROM. I haven't looked a lot, but I bet there is a stock, rooted, debloated ROM based on this OTA...just flash that and you'll be all set! ....
dashbored said:
Thanks for the tip about the CWM recovery! As I no longer have a thunderbolt, I would've been totally screwed. Question though - it sounds like you did what michaelbsheldon said not to do, re-unlock after you're S-off. Do you have the pink flag that he mentioned?
So here's my plan to get my Rezound into a S-off, rooted ICS OTA - please let me know if it's valid:
1a (waiting for michaelbsheldon reply if truly necessary, or if can proceed on stock GB) - HTC Dev unlock and flash Cleanrom 175
1. S-off wire procedure
2. Apply ICS OTA update
3. Apply global roaming update (if available? read about this in the past few days)
4. Since no need to unlock, flash appropriate Superuser for ICS OTA (will google, or if anyone would like to help make sure I find the right one, please feel free to link )
5. flash Amonra recovery. Keep stock hboot.
6. Install root explorer to delete VZ bloatware and titanium backup to restore apps and data from Thunderbolt
Click to expand...
Click to collapse
dashbored... The thing you need to understand is that everyone has their own way of doing things. You need to either (a) study everything everyone says until you understand everything well enough to create your own process, or (b) follow somebody else's process. I will provide you with one below.
In regards to the latest comments...
Flash CleanROM?
I see very little point in flashing a ROM, if you're trying to get the official ICS, root, and S-OFF. I believe the purpose of flashing the ROM is that the ROM is already rooted for you. However, you will need to re-root after you install the OTA, so why not do the same process twice (flash superSU) rather than two different processes (flash ROM, flash superSU)? Seems to me that flashing CleanROM introduces more variables than necessary.
MOST IMPORTANTLY: Maybe I don't know what I'm talking about, but I wouldn't try to install the OTA unless you are running stock Gingerbread. Alternatively, you could try to find a ROM based on the official ICS OTA, but the OTA is still very new... I would just do it the "proper" way (install through Gingerbread) and let those ROMs cook a little more before playing with them.
S-OFF before or after OTA?
I recommend achieving S-OFF before installing the OTA. The S-OFF procedure may very well work with the OTA, but it is guaranteed to work with stock Gingerbread. There is an ICS option in hansoon2000's all-in-one toolkit, but this is based on a leak... Which again is probably very similar (if not identical) to the OTA. But the official OTA is very new, so... In my opinion, the surest thing is to achieve S-OFF before installing the OTA.
Unlock after S-OFF?
My bootloader was locked after I installed the OTA update. What I discovered was that I was unable to flash any custom recoveries (AR Recovery 3.15). Even though I was S-OFF, I still needed to unlock before it would let me flash a recovery.
What I think some people do after achieving S-OFF is install a custom bootloader, and this is why they're able to install custom recoveries without having to unlock again. This is risky. As I understand it, nothing can run on your Rezound if your bootloader has a problem. So if you happen to install a corrupt bootloader, you could brick your Rezound.
It is kind of a pain to go through the HTC unlock process twice, but hey... It's up to you how much risk you're willing to take with your brand new Rezound. I took the safe route. It took maybe a little more time, and I had to do some steps twice (achieving root for GB, then for ICS... unlocking before and after ICS...), but since you only have to go through this whole process once, I recommend playing it safe.
PINK Tampered flag?
I unlocked again after achieving S-OFF. I just double-checked, and I do not see any pink "Tampered" flag anywhere in my bootloader. If you follow my instructions below, this shouldn't happen.
My start-to-finish recommendation:
If the end result you're looking for is ICS OTA, rooted, S-OFF, then I recommend you follow these guides, in the following order:
1: Scotty's noob-friendly guide to root Rezound:
http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html
One thing to note: Scotty gives instructions both for temporary and permanent flashing of custom recovery. In your case, I would recommend doing the temporary flash. This will allow you to flash superSU (achieve root) - which you need to do in order to achieve S-OFF - but it will also save you the hassle of later having to flash the stock recovery back - which you need to have in order to install the OTA.
2: My guide to achieve S-OFF:
https://docs.google.com/document/d/1_kRxD5LtazP7vEnr9cDb3iHwWB1ZfJD_yn6xXo7d1bo/edit
3: My guide to install the OTA after rooting and S-OFF:
https://docs.google.com/document/d/1tmlh4OnplVfBNSjSyXfTYIVGfyb9lgI6ABpfg7gHY44/edit
If you flashed a temporary recovery, then you can skip to step 7 in this guide to verify that you have stock recovery on your device. If you do, then you should be able to initiate the OTA from within Gingerbread, and successfully install. In other words: If you flashed a temporary recovery, you can follow steps 7 to the end in this guide.
These three guides together, in the order that I listed them, are the exact steps I followed to achieve the same thing that you say you're shooting for: official ICS, rooted, S-OFF. I think these steps are the least risky steps you can take to achieve these things.
Keep us posted on how it goes!
bloodymurderlive said:
dashbored
Unlock after S-OFF?
My bootloader was locked after I installed the OTA update. What I discovered was that I was unable to flash any custom recoveries (AR Recovery 3.15). Even though I was S-OFF, I still needed to unlock before it would let me flash a recovery.
What I think some people do after achieving S-OFF is install a custom bootloader, and this is why they're able to install custom recoveries without having to unlock again. This is risky. As I understand it, nothing can run on your Rezound if your bootloader has a problem. So if you happen to install a corrupt bootloader, you could brick your Rezound.
Keep us posted on how it goes!
Click to expand...
Click to collapse
FYI: AFter you s-off you can not use fastboot flash commands unless you install the JB Hboot at the end of the S-off process (it should offer you the option) That is the custom hboot you refer to. All flashers are encouraged to check MD5 sum of the files they download before flashing (primarily RUU, hboot/radios..not so much roms). This will guard against corrupted files, making the process less risky.
If you have the ph98img.zip file version of amonra, it will flash just fine in the stock hboot. Hboot picks it up when it scans for ph98img.zip files and you select yes to install.
Personally, I've kept the stock hboot because there are ph98img.zip files of anything I've needed to flash so I don't have a need to be using a lot of fastboot commands.
topgun1953 said:
Personally, I've kept the stock hboot because there are ph98img.zip files of anything I've needed to flash so I don't have a need to be using a lot of fastboot commands.
Click to expand...
Click to collapse
Exactly... I prefer that my Rezound is self-sufficient, without needing a PC to mess with it.
Good note on fast boot!
stock or rooted
Dashboard:
Juopunutbear instructions require a rooted rom.
So if you wanna go S-0ff, you CAN use a stock rom, but it must
be rooted (SU and Busybox) for the S-0ff process to work.
michaelbsheldon said:
Hiya, You're getting ready to become addicted to roms, by the way.
All your choices are kind of 'what do you want' things, but assuming you
receive it with stock Gingerbread, easiest thing would be to:
1 unlock by way of HTC Development instructions - lots of info here on xda
2 flash Cleanrom 175 a gingerbread stockish rooted rom
3 do the S-0ff thing with Juopunutbear, being careful not to amend or skip
any instructions in the S-0ff recipe (critical).
4 now your phone is s-0ff and locked. leave it just that way: no unlocks ever needed again and no pink warnings
5 flash Android police newest ICS RUU
6 flash amon ra as a PBIMG in recovery
7 use amon ra to wipe and install ANYTHING you want
Click to expand...
Click to collapse
I am new to this and need help when performing a wipe with amon ra there are a lot of options in recovery for the wipe, and I am not sure which option to do. Can you help.
Thanks
flspanky said:
I am new to this and need help when performing a wipe with amon ra there are a lot of options in recovery for the wipe, and I am not sure which option to do. Can you help.
Thanks
Click to expand...
Click to collapse
What are you trying to accomplish? Root? In that case, I believe you need to use amon ra to Wipe cache, then Wipe dalvik cache. Then.com use it to flash superSU.
bloodymurderlive said:
dashbored... The thing you need to understand is that everyone has their own way of doing things. You need to either (a) study everything everyone says until you understand everything well enough to create your own process, or (b) follow somebody else's process. I will provide you with one below.
In regards to the latest comments...
Keep us posted on how it goes!
Click to expand...
Click to collapse
Wow thank you for that informative reply! That really cleared up all of my questions. I now have two new, minor questions.
1. The audio clip for the S-off wire trick has two distinct tones. From watching the video, it looks like the different tones don't matter. Basically just hit tap and release as the metronome hits the first beat, and then again on the second beat. Correct?
2. This is probably a silly question, but what are the advantages of Amon Ra recovery over the stock?
I am too tired tonight, but I think I am going to give this a go this weekend...
michaelbsheldon said:
Dashboard:
Juopunutbear instructions require a rooted rom.
So if you wanna go S-0ff, you CAN use a stock rom, but it must
be rooted (SU and Busybox) for the S-0ff process to work.
Click to expand...
Click to collapse
Gotcha. Thanks for clearing that up for me!
bloodymurderlive said:
What are you trying to accomplish? Root? In that case, I believe you need to use amon ra to Wipe cache, then Wipe dalvik cache. Then.com use it to flash superSU.
Click to expand...
Click to collapse
Thanks. I was installing the ICS Global root and ROM and the instructions said to wipe all, and I was not sure how many areas under the wiping options I should perform.
Quick update - I've rooted my Rezound. Have not done the S-off wire trick yet. Still on stock GB.
Question - none of the wifi tether app seems to be working! Open garden was working perfectly for me with my old rooted Thunderbolt. A quick search seems to show that Rezound has issues with wifi tethering?! This was one of the main motivations behind rooting, so I am a feeling a bit underwhelmed right now with my new Rezound...
Newest wifi tether works fine...even has Rezound settings. Since you are still on GB search for sirgatez mod. Worked great for me when I was still on GB.
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.2.7
Hey guys,
Im not sure what Im missing but Im getting a little frustrated with the rezound/my ignorance haha. My only other android was a dx and that one seemed to flash all roms much easier as far as compatibility. I have read guides and not sure what Im missing. I have an unlocked bootloader and amonra recovery 3.15, S-ON....
I have only been able to use the cleanrom series since 4.3? and conrom (liked but gets HOT) and now wanted to try cm9 lenoob but that failed to boot and also tried miui4.0 with a fail also. They get stuck on the htc logo and get warm, waited about 10mins each and am worried my battery might get low so turned it off before I didnt have enough to recover a backup. The directions said to place in sd and flash, thats what I did in and it didnt work, miui4.0 prompted if I needed the GB patch and I selected yes as well. I know with cleanrom I needed to do the GB patch and ph zip which I have, conrom did everything on its own but the cm9 versions I had no luck with.
Please point out my error guys, this phone has solid specs and just want the latest build of ICS.
66racer said:
Hey guys,
Im not sure what Im missing but Im getting a little frustrated with the rezound/my ignorance haha. My only other android was a dx and that one seemed to flash all roms much easier as far as compatibility. I have read guides and not sure what Im missing. I have an unlocked bootloader and amonra recovery 3.15, S-ON....
I have only been able to use the cleanrom series since 4.3? and conrom (liked but gets HOT) and now wanted to try cm9 lenoob but that failed to boot and also tried miui4.0 with a fail also. They get stuck on the htc logo and get warm, waited about 10mins each and am worried my battery might get low so turned it off before I didnt have enough to recover a backup. The directions said to place in sd and flash, thats what I did in and it didnt work, miui4.0 prompted if I needed the GB patch and I selected yes as well. I know with cleanrom I needed to do the GB patch and ph zip which I have, conrom did everything on its own but the cm9 versions I had no luck with.
Please point out my error guys, this phone has solid specs and just want the latest build of ICS.
Click to expand...
Click to collapse
That's because no kernel was flashed. When your S-On, you have to manually flash the boot.img within the rom zip. Fastboot comes in handy in that situation. Most devs are S-On friendly and provide a PH98IMG.zip for you to flash.
On a side note, I suggest you upgrade to ICS via the global RUU. If you do, be sure to re lock bootloader, then flash RUU.
HTC Rezound
luis86dr said:
That's because no kernel was flashed. When your S-On, you have to manually flash the boot.img within the rom zip. Fastboot comes in handy in that situation. Most devs are S-On friendly and provide a PH98IMG.zip for you to flash.
On a side note, I suggest you upgrade to ICS via the global RUU. If you do, be sure to re lock bootloader, then flash RUU.
HTC Rezound
Click to expand...
Click to collapse
Thanks. So basically to have the easiest time I should get on the latest ruu?
Do you have the Android SDK or the Rezound All In One Toolkit?
scy1192 said:
Do you have the Android SDK or the Rezound All In One Toolkit?
Click to expand...
Click to collapse
All in one toolkit
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
So while in process of s-off once I got to the part when you "fastboot oem rebootRUU" that went through. But right after trying to flash a zip im stuck looking at the blk HTC screen. I was given a "<Failed <remote: 99 unknown fail>". Now its just stuck.
I've been trying to figure out what happened but just have no where else to turn. Please lend a hand.
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
aarsyl said:
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
It's not a full RUU in the normal sense. It's the one for Facepalm.
To the OP, did you gain SuperCID prior to running those commands? If not, then the process will fail. You should simply be able to hold the power button down & reboot your phone. Also, as stated above, list your device info so we can make sure you're using the right S-off exploit.
Sent from my HTC EVO 4G LTE
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
z3r0t0l0rEnCe said:
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
Click to expand...
Click to collapse
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
aarsyl said:
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
Click to expand...
Click to collapse
This is odd to me, because I ran rumrunner at least 3 times using just my stock ROM (no custom kernel or anything), and it worked fine every time. I guess the new version of rumrunner added some limitations to make it more generic.
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
z3r0t0l0rEnCe said:
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
Click to expand...
Click to collapse
No, don't. If it fails, don't force it. Reflash TWRP 2.6.3 (not the kit kat version), and try to flash again.
@Captain_Throwback: Yes, I didn't remember needing a custom kernel when I used Dirty Racun, but rumrunner needs it now. Keep in mind that rumrunner isn't for this device exclusively. Maybe that's the purpose of the custom kernel.
i'd wager you're trying to flash files that aren't recovery flashable, then lying to the people who are trying to help you.
i got it running again using capt stock rooted rom. attempting rumrunners s-off again now that i got this part working.
Are you using a custom kernel?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
now s-off and updated rumrunners hboot. now onto flashing roms finally.
Thank you all that helped me with my stupidness and not reading directions.
Last post. I can't say it enough that you must read read read when it comes to directions. If I would of followed directions as directed I would of never ran into the issues I did. It was a learning experience.
One thing for sure that I took from this experience is adb and directions. I've learned a lot in the last 24hrs alone.
I'd like to thank Capain_throwback and everyone in the irc for the help and you all here that assisted me.
Sent from my EVO using XDA Premium 4 mobile app