Related
I would like to FINALLY S-OFF to make life easier and I am currently running Newt's one XXX Rls 1.0 on the ICS Firmware. MY question is if anyone can point me to a definitive guid on what I need to do to get back to the correct stock rom in order to do this, if anyone can point me in the correct direction for easy instructions that'd be great, my searches have put me in 20 different places and have given me a headache... thanks!!!
http://forum.xda-developers.com/showthread.php?p=25816870
That should do it for you as far as ensuring you flash a working stock ROM, good instructions. If you want the latest leak, since it is highly likely the OTA given the numbers HTC leaked today:http://forum.xda-developers.com/showthread.php?p=27244835
Note the attachment if you have root issues, read and check after flashing this one.
Pretty sure those unlimited.io instructions about being on a stock ROM are just to cover their butts for troubleshooting. Unless the custom ROM has issues with USB debugging or issues with root, should be fine. That is what the concern in the instructions is truly about, proper access for the program to work its magic. Just saying XXX RLS 1 should be good to go lol.
I was wondering the same thing I'm on the gb firmware running rezrom sense 4. So are you saying I can s off just how my phone is or do i need to flash something else first. Should I flash ice firmware first or just s off?
Sent from my ADR6425LVW using XDA
PhantasmRezound said:
http://forum.xda-developers.com/showthread.php?p=25816870
That should do it for you as far as ensuring you flash a working stock ROM, good instructions. If you want the latest leak, since it is highly likely the OTA given the numbers HTC leaked today:http://forum.xda-developers.com/showthread.php?p=27244835
Note the attachment if you have root issues, read and check after flashing this one.
Pretty sure those unlimited.io instructions about being on a stock ROM are just to cover their butts for troubleshooting. Unless the custom ROM has issues with USB debugging or issues with root, should be fine. That is what the concern in the instructions is truly about, proper access for the program to work its magic. Just saying XXX RLS 1 should be good to go lol.
Click to expand...
Click to collapse
So here's my software info screens, which s off file should I download? I'm not sure which ice leak I am on I can't remember and I can't tell from here
Burkejt1 said:
So here's my software info screens, which s off file should I download? I'm not sure which ice leak I am on I can't remember and I can't tell from here
Click to expand...
Click to collapse
Can't tell there since XXX is not based on Rezound firmware, it's ported... Have to check bootloader version and match up with firmware. (see below)
Make it safe and by the book, simply back up your data, and then flash to a stock rooted ICS ROM. That said:
http://unlimited.io/juopunutbear-public-beta-0-1/instructions/htc-rezound/
Well this is why this advice is simply off the cuff. In theory you'd just grab the corresponding bootloader regardless of the ROM used with. But the files are labeled by firmware version with no hboot label. I know a 2.25 hboot corresponds to the 3.14.605.5 file, 2.21 hboot to the ICS builds before that. 2.11 hboot to the latest GB firmware...
Check the hboot version in your bootloader and match it up with the proper package based on that info, if you wish to attempt on current ROM. If you have 2.21 I am unsure if that could be "Early ICS" or 3.13 leak, have to look at radio numbers then which I don't know off the top of my head...
Again, recommend you backup ROM and flash the 3.14.605.5 firmware rooted for the procedure just to ensure you get through the S-off properly. Get your JuopunutBear hboot on there, reflash recovery, and restore the ROM backup or try an upgrade...
Famester, you have GB firmware and so you only have one package to choose from. You have a better chance than Burkejt1 of just going ahead with S-off using GB package. Remember to do a ROM backup.
If you flash ICS firmware for the procedure too, remember to use the backup afterwards means it must be repatched for new firmware mounting points. Patch after restoring it but before booting the ROM.
Okay, I'm working until 11pm EST tonight and I'll flash the stock rooted ROM for your first post, and then attempt this S-OFF business with a paperclip and some electrical tape.
Thanks for your help I'll let you know how it goes I have been meaning to do this for a while and I think I'll finally have the time to tonight.
famester said:
I was wondering the same thing I'm on the gb firmware running rezrom sense 4. So are you saying I can s off just how my phone is or do i need to flash something else first. Should I flash ice firmware first or just s off?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
I was in the same situation before I s-off'd. I stayed on the GB firmware (and still am) but I flashed one of scotts stock roms. scottsroms.com Just to be safe. I also made sure I was on Amon Ra only for the s-off process. I typically prefer TWRP after my initial struggles with Clockwork.
Good luck y'all. It seems scarier than it is.
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.
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
So i just got my One yesterday and it still has the .7 firmware / rom on it. I am going to root it and s-off right now, but just wondering a couple things.
1. Can or should i use an ruu to update the firmware to the more recent versions?
2. If yes, will this make me lose root or s-off? (i would imagine root would be easy enough to get back as long as i still have s-off)
thanks!!
At the moment, unless the situation has changed, there isn't an RUU for the TMo HTC One. One was released the other day, but it didn't work and HTC pulled the download. For now, I'd wait a couple of days to see if they release a fixed version. Your only other option would be to flash the .ZIP with the updated radio after going S-OFF.
Sisyphus306 said:
At the moment, unless the situation has changed, there isn't an RUU for the TMo HTC One. One was released the other day, but it didn't work and HTC pulled the download. For now, I'd wait a couple of days to see if they release a fixed version. Your only other option would be to flash the .ZIP with the updated radio after going S-OFF.
Click to expand...
Click to collapse
Ah.. ok. That makes sense. I downloaded one that was labeled for TMO, but i will just wait until it all gets sorted out. I am not to concerned about the radio, those are always easy to flash. Was wondering if there was anything else in the firmware i needed (like when the one s got jellybean there was WIFI partitions that needed to get flashed for everything to work properly)
For anyone else that is searching for this answer, here is what i ended up doing and it worked well.
My phone came with the .7 build install (this was the very first build before any updates). I rooted, and went s-off BEFORE ANY OTA's we taken. At this point i still had the original stock rom, it was just rooted. Since I always like to at least try the newest firmware out (cause you never know what benefits it may have) I flashed the STOCK TMO recovery back onto the phone.
Now you can boot into your OS, and go through the normal OTA process that you would get in any unrooted rom. Once those updates are complete you will be on the latest firmware and ROM from TMO, but no root access. Since you still are S-OFF, you have no problems here, flash TWRP back on (or CWM, i prefer TWRP) and flash whatever you want.
Hope that helps someone else that may be looking for the same answers.
frettfreak said:
For anyone else that is searching for this answer, here is what i ended up doing and it worked well.
My phone came with the .7 build install (this was the very first build before any updates). I rooted, and went s-off BEFORE ANY OTA's we taken. At this point i still had the original stock rom, it was just rooted. Since I always like to at least try the newest firmware out (cause you never know what benefits it may have) I flashed the STOCK TMO recovery back onto the phone.
Now you can boot into your OS, and go through the normal OTA process that you would get in any unrooted rom. Once those updates are complete you will be on the latest firmware and ROM from TMO, but no root access. Since you still are S-OFF, you have no problems here, flash TWRP back on (or CWM, i prefer TWRP) and flash whatever you want.
Hope that helps someone else that may be looking for the same answers.
Click to expand...
Click to collapse
Would you mind linking the T-mobile stock recovery that you flashed? I'm in about the same situation you were in.
FYI, there is a working TMOUS RUU available now, you can download it through the following link. I downloaded it yesterday and used it last night, I can confirm it works.
http://forum.xda-developers.com/showpost.php?p=43963285&postcount=9
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