Related
Check it out =)
http://www.androidpolice.com/2012/0...id-4-0-build-3-11-605-22-for-the-htc-rezound/
Ronn Plae said:
Check it out =)
http://www.androidpolice.com/2012/0...id-4-0-build-3-11-605-22-for-the-htc-rezound/
Click to expand...
Click to collapse
I'm looking now. Thanks for the heads up!
You have to be locked to flash the radios right? Im still on the GB radio. Im iffy about flashing leaked radios.
mighty_markus12 said:
You have to be locked to flash the radios right? Im still on the GB radio. Im iffy about flashing leaked radios.
Click to expand...
Click to collapse
Yes, until we get s-off.
already posted
Can we undo the HTC Dev Unlocker, install the stock, install the leak, and do the HTC Dev Unlock again?
MisfitsTimmy said:
Can we undo the HTC Dev Unlocker, install the stock, install the leak, and do the HTC Dev Unlock again?
Click to expand...
Click to collapse
Yes. See the other post for download and instructions
Just a warning guys, it updates your h-boot AGAIN. This time to 2.21
Sent from my ADR6425LVW using XDA
i dont think the radio is updated based on the ss's of about phone, same as what i have now
downloading,thanks.
nghtmr3 said:
i dont think the radio is updated based on the ss's of about phone, same as what i have now
Click to expand...
Click to collapse
That's what I was thinking.
Sent from my ADR6425LVW using Tapatalk
It does update the radio. You need to relock bootloader then flash.
Sent from my Incredible, faster than a Thunderbolt, Rezound
md5s are different in radio and mdm9k images,for whatever thats worth
has anyone that ran the full RUU and unlocked tried to re-install an older gingerbread or ICS custom rom? if so did it work,or are you now "stuck" on this leak?
not being quite sure if i wanted to run the whole thing,i flashed the boot and system images and the phone is unusable because of the bootloops
im thinking the factory images are not happy with the 2.01.605.11 firmware so im wondering now if once you install the new hboot,radio,etc, if the older custom roms do not work
scotty1223 said:
md5s are different in radio and mdm9k images,for whatever thats worth
has anyone that ran the full RUU and unlocked tried to re-install an older gingerbread or ICS custom rom? if so did it work,or are you now "stuck" on this leak?
not being quite sure if i wanted to run the whole thing,i flashed the boot and system images and the phone is unusable because of the bootloops
im thinking the factory images are not happy with the 2.01.605.11 firmware so im wondering now if once you install the new hboot,radio,etc, if the older custom roms do not work
Click to expand...
Click to collapse
Yes, the older custom roms will not work well with the new firmware. They run fine, but in my case you suddenly didn't have access to your external SD card . Some have lost both cards . Restoring with Scott's rom fixed this for some, I had made a backup of the stock RUU rom so just flashed back and all was good again. Then I flashed Scott's rom. Sounds like something changed with either the mounting points or the mmcc dev block on the new firmware.
scotty1223 said:
md5s are different in radio and mdm9k images,for whatever thats worth
has anyone that ran the full RUU and unlocked tried to re-install an older gingerbread or ICS custom rom? if so did it work,or are you now "stuck" on this leak?
not being quite sure if i wanted to run the whole thing,i flashed the boot and system images and the phone is unusable because of the bootloops
im thinking the factory images are not happy with the 2.01.605.11 firmware so im wondering now if once you install the new hboot,radio,etc, if the older custom roms do not work
Click to expand...
Click to collapse
From my understanding the new firmware doesn't play nice with the older roms. I'm very leery of running the ruu myself. What if the actual release uses the old hboot? Is that even possible?
sent from ics land
its possible that the official OTA may contain a different hboot,but not likely the old one. they have obviously changed some things that would ahve to be re-engineered to work with the old hboot,and their wouldnt really be a point. as much as it seems like a possibility i doubt theyd go to the trouble of releasing a leak just to eff with us
if it contains something different,it would be newer,like 2.22+. but im pretty sure the 2.21 will be the release hboot.
im not sure i want to upgrade yet,either,tho i beieve with the evo3d method we will be able to donwgrade if needed.
my main issue is that i still want to be able to use these older roms,at least long enuff everyone has updated their base and made the old version obsolete. i dont really care about getting back to gingerbread,but without s-off i think its best not to rush into anything.
grrr this whole s-on thing really ticks me off on my thunderbolt or sensation id just run the RUU and not care,as i could always go back to old firmware
scotty1223 said:
grrr this whole s-on thing really ticks me off on my thunderbolt or sensation id just run the RUU and not care,as i could always go back to old firmware
Click to expand...
Click to collapse
I hear you, I want to do this so badly but I'm leery of not being able to go back if something went down with my phone and I had to take it in. Talk about itchy trigger finger.
scotty1223 said:
its possible that the official OTA may contain a different hboot,but not likely the old one. they have obviously changed some things that would ahve to be re-engineered to work with the old hboot,and their wouldnt really be a point. as much as it seems like a possibility i doubt theyd go to the trouble of releasing a leak just to eff with us
if it contains something different,it would be newer,like 2.22+. but im pretty sure the 2.21 will be the release hboot.
im not sure i want to upgrade yet,either,tho i beieve with the evo3d method we will be able to donwgrade if needed.
my main issue is that i still want to be able to use these older roms,at least long enuff everyone has updated their base and made the old version obsolete. i dont really care about getting back to gingerbread,but without s-off i think its best not to rush into anything.
grrr this whole s-on thing really ticks me off on my thunderbolt or sensation id just run the RUU and not care,as i could always go back to old firmware
Click to expand...
Click to collapse
again this is why we need s-off achieved somehow. i feel your pain scotty.
Well, from what I see in the Amon Ra thread, the mount points for storage are definitely different. (The changelog over on Android Police even mentions a "fix" for storage issues.) As for me, I'm going to wait until drellisdee updates Amon Ra for the new firmware, by which point everyone ought to have their ROMs updated and most of the new "gotcha's" that arise worked out.
mjh68 said:
Yes, the older custom roms will not work well with the new firmware. They run fine, but in my case you suddenly didn't have access to your external SD card . Some have lost both cards . Restoring with Scott's rom fixed this for some, I had made a backup of the stock RUU rom so just flashed back and all was good again. Then I flashed Scott's rom. Sounds like something changed with either the mounting points or the mmcc dev block on the new firmware.
Click to expand...
Click to collapse
scrosler from Scott's Rom's posted a flashable zip file that fixes the SD Card Issue.
Link
I'm brand new to this phone and the rezound section on xda. I bought two of these phones yesterday and have both of them S=OFF at the moment. (Last night's fun)
In hboot they say "locked" even though S=OFF on both devices. I'd like to install an ICS ROM, but I'm not really sure what I need to install first before installing the ROM so it doesn't get all messed up.
I remember installing/flashing something on my Sensation to get ICS running on that device, but I'm just a little confused with the steps in the Development section because I'm new here.
Help?
you need to flash a modified Hboot for whichever firmware u are on
http://forum.xda-developers.com/showthread.php?t=1641670
yojoe600 said:
you need to flash a modified Hboot for whichever firmware u are on
Click to expand...
Click to collapse
Software Number: 2.01.605.11
Does it matter which one?
graymonkey44 said:
http://forum.xda-developers.com/showthread.php?t=1641670
Click to expand...
Click to collapse
I spent last night reading that.
yes if you are on GB you need the eng Hboot if you are on ICS firmware you need the jhboot from the s-off method
yojoe600 said:
yes if you are on GB you need the eng Hboot if you are on ICS firmware you need the jhboot from the s-off method
Click to expand...
Click to collapse
HBOOT 2.11.0000
I flashed the hboot after jhboot and I'm not sure if this is the right one for ICS?
android Version: 2.3.4
I would suggest running the latest RUU and then installing whichever ICS ROM you want.
woah wait what
what are you guys saying?
I was stock,GB,rooted, SOFF.
my hboot said 's-off' and '***LOCKED***'.
you don't need to do anything special, you are s-off!
just get the 600mb ph98img.zip from the latest leak and drop it on your SD card.
it'll have to flash twice (first reboot after boot/recovery is flashed, then it does the rest the second time through)
that's how i went to the leak, still locked and s-off. and it runs great!
thatsricci said:
woah wait what
what are you guys saying?
I was stock,GB,rooted, SOFF.
my hboot said 's-off' and '***LOCKED***'.
you don't need to do anything special, you are s-off!
just get the 600mb ph98img.zip from the latest leak and drop it on your SD card.
it'll have to flash twice (first reboot after boot/recovery is flashed, then it does the rest the second time through)
that's how i went to the leak, still locked and s-off. and it runs great!
Click to expand...
Click to collapse
Which one is the latest leak? I'm really not trying to be a moron.
thatsricci said:
woah wait what
what are you guys saying?
I was stock,GB,rooted, SOFF.
my hboot said 's-off' and '***LOCKED***'.
you don't need to do anything special, you are s-off!
just get the 600mb ph98img.zip from the latest leak and drop it on your SD card.
it'll have to flash twice (first reboot after boot/recovery is flashed, then it does the rest the second time through)
that's how i went to the leak, still locked and s-off. and it runs great!
Click to expand...
Click to collapse
So its just that simple for those of us SOFF and GB?
1) Put the PHxxxx.zip image on the SD
2) Boot it into HBoot twice (not flashing via recovery)
3) Flash over our favorite ICS Rom
No patches, no nothing? Is this right?
There are like 10 files in this link.
http://forum.xda-developers.com/showthread.php?t=1365654
I have S=OFF, I'm running GB, with the stock ROM and all the specs I told you. I'm not exactly clear on which one I need to install before installing a ICS ROM.
Do I install an ENG hboot... Do I install a ICS RUU file or a GB one? I'm assuming the bigger the number the newer RUU?
I'm not sure when you say about rom... i'm flashing the 600mb leak file from yesterday (5/7/2012) : http://forum.xda-developers.com/showthread.php?t=1641249
it has the radios, boot, recovery, kernel, rom, everything. I just did it all, like an OTA upgrade.
thatsricci said:
I'm not sure when you say about rom... i'm flashing the 600mb leak file from yesterday (5/7/2012) : http://forum.xda-developers.com/showthread.php?t=1641249
it has the radios, boot, recovery, kernel, rom, everything. I just did it all, like an OTA upgrade.
Click to expand...
Click to collapse
I want to Install the RUU file then a modded ROM (Clean ROM ICS)
If I install the ROM before flashing the RUU won't it bootloop?
jdmba said:
So its just that simple for those of us SOFF and GB?
1) Put the PHxxxx.zip image on the SD
2) Boot it into HBoot twice (not flashing via recovery)
3) Flash over our favorite ICS Rom
No patches, no nothing? Is this right?
Click to expand...
Click to collapse
Is this all that all I have to do?
2Noob4U said:
I want to Install the RUU file then a modded ROM (Clean ROM ICS)
If I install the ROM before flashing the RUU won't it bootloop?
Click to expand...
Click to collapse
I'm not sure... I didn't have any trouble going straight to the leaked RUU from yesterday. I have not flashed any custom roms.
thatsricci said:
I'm not sure... I didn't have any trouble going straight to the leaked RUU from yesterday. I have not flashed any custom roms.
Click to expand...
Click to collapse
Is there something wrong with the Custom ROMs? (Please Developers don't stone me)
I just came from a device with tons of custom ROMs that were way better than anything stock and would install a kernel and everything through recovery when you were installing the ROM...
I'm just not used to the process yet with this device.
I don't think there's anything wrong with them.
I just haven't taken the plunge yet, still researching.... regardless, Once you're fully up to date on the latest RUU, going to a custom rom based on it will be a piece of cake. But i'm not sure the developers have updated their roms to all the latest leaks, in which case, check with the rom you're trying to upgrade to - I'm not certain they all include new kernels/radios...etc. like the leaked ICS does.
thatsricci said:
I don't think there's anything wrong with them.
I just haven't taken the plunge yet, still researching.... regardless, Once you're fully up to date on the latest RUU, going to a custom rom based on it will be a piece of cake. But i'm not sure the developers have updated their roms to all the latest leaks, in which case, check with the rom you're trying to upgrade to - I'm not certain they all include new kernels/radios...etc. like the leaked ICS does.
Click to expand...
Click to collapse
Okay. Can I wifi tether with the new RUU link you gave me?
2Noob4U said:
Okay. Can I wifi tether with the new RUU link you gave me?
Click to expand...
Click to collapse
Great question, let me test that right now.
Edit: seems to not work straight up with the one from the market. i'll check a different .apk that I have here, i know the custom roms use their own .apk's usually.
as i recall from doing this on GB, you gotta configure it right, and then it'll work. But you DO need root, so after you RUU, install AmonRA 3.15, and run the su/superuser install from the recovery menu.
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
Hi, so I have not touched my ROM since last May [using CleanROM Pro 4.5; dev unlocked and rooted] and as it's been a while I wanted to update to some newer stuff. I first looked to just update my ROM, but realized that there hasn't been a new release.., but I know there's been a lot of updates since last May (the official ICS for one, and I guess now Jelly Bean leaks?).
Anyway, I'm trying to get to the new stuff and super confused on how to do it. My original thought was to go back to stock (relock bootloader and then RUU to get all the stock updates [I'm on GB Firmware, but "patched" for ICS leak] and then find a new ROM from there, is that the best way to proceed? Is there an easier way?
Any help would be greatly appreciated!
Btw, if it matters, I'm pretty sure I'm S-on [I can mess with that by reading one of the s-on/off threads though if necessary]
if u like sense i prefer viperrez by joelz, really awesome and stable. if u wanna go with something desensed, try one of neo's roms.u dont have to be s-off, but atleast grab the boot. img out the folders.
Sent from my ADR6425LVW using Tapatalk 2
Yeah, if you run the latest RUU here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
it will update you to the latest and also to global. I'm running ViperRez and like it a lot. If you pick a ROM you can always ask in that thread if it will work on the latest RUU but I believe most of the ICS ROMs will be fine on it. When you run the RUU let it cycle through a few times. It needs to do that to get all the system files. Just wait and make sure it's done.
If you didn't do the "wire trick" you aren't s-off. It involves shorting out something on your phone by using a paper clip or wire so if you don't remember doing that you are def s-on.
I wouldn't bother going s-off since you don't flash often. I don't either and I'm staying s-on. You will have to pull the boot.img out and flash that separately right after you flash the ROM. Going s-off would automate that but also makes it possible to brick your phone.
Thanks for the help!
Just downloaded the RUU.
Quick question: you both mentioned deleting the boot.img file; do I delete this file after I've flashed the RUU and am running a new ROM?
Also, do I need to do anything with the Firmware patch before running the RUU? I.e. delete it, or does it not make any difference?
Thanks again!
mattmns said:
Thanks for the help!
Just downloaded the RUU.
Quick question: you both mentioned deleting the boot.img file; do I delete this file after I've flashed the RUU and am running a new ROM?
Also, do I need to do anything with the Firmware patch before running the RUU? I.e. delete it, or does it not make any difference?
Thanks again!
Click to expand...
Click to collapse
No, don't delete the boot.img. That is your kernel. You need to either copy it from your ROM and install it through adb or use the PH98 method and flash it through Hboot.
Sent from my ADR6425LVW using xda premium
Thanks for the clarification.
I went ahead and flashed the RUU and am up and running again :good: thanks for the help!