Related
I've got an Amaze 4G on Wind Mobile. My brother and I recently tried upgrading it to ICS. We followed numerous sets of instructions, flashing a recovery, a new version of hboot, s-offing the phone, changing the SuperCID and flashing an ICS ROM. We originally tried Android Revolution HD, but the phone always got stuck at the HTC logo and wouldn't boot up.
After a few hours of searching the forums and trying various things, we finally got the Energy ROM version 5/1 installed, after changing the SuperCID back to the Wind default (globa001 I think). We figured it was an issue with the Revolution ROM, but when I tried upgrading to Energy 5/6, I ran into the same issue.
I have searched the forums and found numerous people with the same problem, but I have not found a solution. I spent all night flashing ROMs and trying various things and I finally got it to go to the Energy boot animation, but it would just sit there and do nothing (I left it a good half hour). The next morning I tried installing Speed Rom with the SuperCID 11111111 and it worked. However, I had tried the same thing the night before, so I'm not sure what changed.
I'm not happy with Speed and would like to go back to Energy, but I'm worried it will brick my phone again.
I am currently using the TWRP recovery, but I used 4ext before with the same result. My firmware versions are as follows:
RUBY PVT SHIP S-OFF RL
HBOOT-1.93.0002
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Any help would be very much appreciated.
acc3ssd said:
I've got an Amaze 4G on Wind Mobile. My brother and I recently tried upgrading it to ICS. We followed numerous sets of instructions, flashing a recovery, a new version of hboot, s-offing the phone, changing the SuperCID and flashing an ICS ROM. We originally tried Android Revolution HD, but the phone always got stuck at the HTC logo and wouldn't boot up.
After a few hours of searching the forums and trying various things, we finally got the Energy ROM version 5/1 installed, after changing the SuperCID back to the Wind default (globa001 I think). We figured it was an issue with the Revolution ROM, but when I tried upgrading to Energy 5/6, I ran into the same issue.
I have searched the forums and found numerous people with the same problem, but I have not found a solution. I spent all night flashing ROMs and trying various things and I finally got it to go to the Energy boot animation, but it would just sit there and do nothing (I left it a good half hour). The next morning I tried installing Speed Rom with the SuperCID 11111111 and it worked. However, I had tried the same thing the night before, so I'm not sure what changed.
I'm not happy with Speed and would like to go back to Energy, but I'm worried it will brick my phone again.
I am currently using the TWRP recovery, but I used 4ext before with the same result. My firmware versions are as follows:
RUBY PVT SHIP S-OFF RL
HBOOT-1.93.0002
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Any help would be very much appreciated.
Click to expand...
Click to collapse
ok, well if your on wind mobile you want to use super cid.
but heres what i think the problem is, you didnt mention anything about wiping. try flashing the superwipe.zip before flashing roms. and always have a nandroid of a working rom. or else you may get stuck....
if you need anymore help, i will be watching this thread
Sorry, I forgot to mention that. I used superwipe and tried the various wipe options in the recovery, with the same result.
I'll definitely look into nandroid before I try installing another rom ;-)
I'd advise switching back to 4EXT recovery, makes flashing easier, trust me. Now update your phone to stock ICS, install 4EXT recovery then format all partitions except sd then install the ROM of your choice.
Before installing ICS you'll need to flash GB stock from WIND, then update to ICS via either OTA or directly on the phone via OTA. Then do what I said above, let us know what happens.
yeah like dark said above me, use 4ext. it makes flashing easier.
ziggy46 said:
yeah like dark said above me, use 4ext. it makes flashing easier.
Click to expand...
Click to collapse
Damn thanks limit, lol. +ziggy.
Dark Nightmare said:
Damn thanks limit, lol. +ziggy.
Click to expand...
Click to collapse
haha they should make it like 12 max
ziggy46 said:
haha they should make it like 12 max
Click to expand...
Click to collapse
The app has no limits, gonna switch to that in a sec, I already gave out like 30 thanks for today, therefore no limits would be awesome, just people might abuse it, smh.
Dark Nightmare said:
I'd advise switching back to 4EXT recovery, makes flashing easier, trust me. Now update your phone to stock ICS, install 4EXT recovery then format all partitions except sd then install the ROM of your choice.
Before installing ICS you'll need to flash GB stock from WIND, then update to ICS via either OTA or directly on the phone via OTA. Then do what I said above, let us know what happens.
Click to expand...
Click to collapse
Thanks for your help everyone. I'm a little confused about how to proceed though. I downloaded the stock Wind ruu.exe file from the forums, but I'm not sure what to do with it. I'm running Linux, so I can't execute the file. Is there any way to flash it without a Windows machine?
Also, do I need to relock my bootloader and go through the whole s-off procedure again, or can I simply downgrade to GB and upgrade back to ICS again without going through all those steps?
acc3ssd said:
Thanks for your help everyone. I'm a little confused about how to proceed though. I downloaded the stock Wind ruu.exe file from the forums, but I'm not sure what to do with it. I'm running Linux, so I can't execute the file. Is there any way to flash it without a Windows machine?
Also, do I need to relock my bootloader and go through the whole s-off procedure again, or can I simply downgrade to GB and upgrade back to ICS again without going through all those steps?
Click to expand...
Click to collapse
You need windows to flash it.
acc3ssd said:
Thanks for your help everyone. I'm a little confused about how to proceed though. I downloaded the stock Wind ruu.exe file from the forums, but I'm not sure what to do with it. I'm running Linux, so I can't execute the file. Is there any way to flash it without a Windows machine?
Also, do I need to relock my bootloader and go through the whole s-off procedure again, or can I simply downgrade to GB and upgrade back to ICS again without going through all those steps?
Click to expand...
Click to collapse
Once you're s-off once, you'll always be s-off unless you s-on again, to use the windows file your best option would be to use WINE. Which I figure you should be know how to use.
Dark Nightmare said:
I'd advise switching back to 4EXT recovery, makes flashing easier, trust me. Now update your phone to stock ICS, install 4EXT recovery then format all partitions except sd then install the ROM of your choice.
Before installing ICS you'll need to flash GB stock from WIND, then update to ICS via either OTA or directly on the phone via OTA. Then do what I said above, let us know what happens.
Click to expand...
Click to collapse
Thanks again for your help. I followed your instructions: Downgraded to GB, flashed the Wind ICS OTA, install 4ext recover, ran superwipe and formatted everything except the SD card, and then flashed Energy 6/6. It got past the HTC screen, but got stuck on the Energy boot animation.
Do you have any other suggestions?
acc3ssd said:
Thanks again for your help. I followed your instructions: Downgraded to GB, flashed the Wind ICS OTA, install 4ext recover, ran superwipe and formatted everything except the SD card, and then flashed Energy 6/6. It got past the HTC screen, but got stuck on the Energy boot animation.
Do you have any other suggestions?
Click to expand...
Click to collapse
flash the kernel from his 3rd post on energy rom
also you did flash the PH85IMG.zip on his downloads ya ?
Jay_Rulen said:
flash the kernel from his 3rd post on energy rom
also you did flash the PH85IMG.zip on his downloads ya ?
Click to expand...
Click to collapse
And did you wait a bit? First boot usually takes a while.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
And did you wait a bit? First boot usually takes a while.
Click to expand...
Click to collapse
I waited at least half an hour, took out the battery and tried again to no avail.
Jay_Rulen said:
flash the kernel from his 3rd post on energy rom
also you did flash the PH85IMG.zip on his downloads ya ?
Click to expand...
Click to collapse
Is that an Energy ROM image?
acc3ssd said:
Is that an Energy ROM image?
Click to expand...
Click to collapse
Yes it is.
Sent from an Amaaaaaazing place :-D
Same issue
I'm doing the same and I need help
I'm trying to get the latest EnergyRom. I was using the GB EnergyRom before and finally made it to the T-Mobile Stock ICS rom using fastboot instructions from here: androidforums.com/rezound-all-things-root/535820-how-easier-way-flash-ph98img-files.html using the this ruu. [bravo.d-h.st/z70?key=1340081175
Right now I don't se any S-On instructions for Energy rom, though I do see one for Android Revolution HD. I need to get CWM re-installed as that was lost. Do I need S-Off to get Energy Rom?
How do I get the latest Energry rom installed?
Dark Nightmare said:
Yes it is.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Yes, that's the one I installed. What will the other kernel do?
Sent from my HTC Amaze 4G using Tapatalk 2
acc3ssd said:
Yes, that's the one I installed. What will the other kernel do?
Sent from my HTC Amaze 4G using Tapatalk 2
Click to expand...
Click to collapse
It's the kernel he built his rom on, so requires it to work properly.
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
I am at my wits end here. This phone is driving me crazy. It seems like the only ROM's I can get to work are ones that use Aroma installer. I don't know what part of the Aroma installer is what makes it work, but I would really like to know because I want to try NeWt's and/or AOSP.
I am S-ON
I am on whatever firmware gets installed with the Nil's business ICS Sense 4.0 Aroma installer. (I don't know how to check my firmware, I imagine it's easy to check and/or install new firmware, but I can't seem to find a thread about firmwares anywhere. All I can find is Kernels/Roms)
I tried newt's first. I wiped everything, installed the rom. Then I rebooted to bootloader and did fastboot flash boot boot.img (the boot.img I pulled out of the rom's .zip) it flashed that, then I rebooted. The result: Stuck at HTC logo.
No idea what caused that, but I decided I'd go for ICS AOSP instead. I installed that, following the same process as above, and in this scenario I get stuck at the CM9 bootlogo infinitely (bootloop).
I'm sorry if I seem really frustrated, but honestly it's because I am. I've never had this much of a problem getting custom roms to work on any phone I've ever had. I really hope it's something I'm just missing, because I feel like a moron. I can't get any of these roms to even boot, and that's just sad...
PLEASE HELP!
bigbabys said:
I am at my wits end here. This phone is driving me crazy. It seems like the only ROM's I can get to work are ones that use Aroma installer. I don't know what part of the Aroma installer is what makes it work, but I would really like to know because I want to try NeWt's and/or AOSP.
I am S-ON
I am on whatever firmware gets installed with the Nil's business ICS Sense 4.0 Aroma installer. (I don't know how to check my firmware, I imagine it's easy to check and/or install new firmware, but I can't seem to find a thread about firmwares anywhere. All I can find is Kernels/Roms)
I tried newt's first. I wiped everything, installed the rom. Then I rebooted to bootloader and did fastboot flash boot boot.img (the boot.img I pulled out of the rom's .zip) it flashed that, then I rebooted. The result: Stuck at HTC logo.
No idea what caused that, but I decided I'd go for ICS AOSP instead. I installed that, following the same process as above, and in this scenario I get stuck at the CM9 bootlogo infinitely (bootloop).
I'm sorry if I seem really frustrated, but honestly it's because I am. I've never had this much of a problem getting custom roms to work on any phone I've ever had. I really hope it's something I'm just missing, because I feel like a moron. I can't get any of these roms to even boot, and that's just sad...
PLEASE HELP!
Click to expand...
Click to collapse
First off, no firmware will be installed with a rom, but this is a good place to start. With you being s-off, even a kernel won't be installed with a custom rom unless you flash the boot.img in hboot (or fastboot flash). My suspicion is that you are still on GB firmware. This can be alleviated by installing a patch. However, I think it in your best interest to re-lock, flash the newest RUU (found at androidpolice), and unlock again. That way, you will have updated to ICS firmware (therefore making it easier to run ICS based ROMS).
Do you have a working ROM right now that you can rever to so we can get some information off of it?
iamwalterwhite said:
First off, no firmware will be installed with a rom, but this is a good place to start. With you being s-off, even a kernel won't be installed with a custom rom unless you flash the boot.img in hboot (or fastboot flash). My suspicion is that you are still on GB firmware. This can be alleviated by installing a patch. However, I think it in your best interest to re-lock, flash the newest RUU (found at androidpolice), and unlock again. That way, you will have updated to ICS firmware (therefore making it easier to run ICS based ROMS).
Do you have a working ROM right now that you can rever to so we can get some information off of it?
Click to expand...
Click to collapse
Well, it's funny you should say that. I DID, or so I thought. I got fed up and restored a backup. How even my backup won't boot. I have no idea how that is even possible. Do I need to re-lock the device to install an RUU? What you are saying sounds like exactly what I need (to get on ICS firmware) so if you could tell me the easiest way to do that, I'll get started right away, haha.
Anyways, the backup I tried to restore was viper rez 1.03, and my hboot version is 2.11.0000. I cant' boot a rom at all.
bigbabys said:
Well, it's funny you should say that. I DID, or so I thought. I got fed up and restored a backup. How even my backup won't boot. I have no idea how that is even possible. Do I need to re-lock the device to install an RUU? What you are saying sounds like exactly what I need (to get on ICS firmware) so if you could tell me the easiest way to do that, I'll get started right away, haha.
Anyways, the backup I tried to restore was viper rez 1.03, and my hboot version is 2.11.0000. I cant' boot a rom at all.
Click to expand...
Click to collapse
If you can't boot a rom at all, then I can't tell you exactly which firmware you are on. With your hboot version, though, it looks like you are on GB firmware. Yes, you need to relock to run the RUU. Relock, run the RUU (found here: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ ), unlock again, flash AR 3.15, then move onto ICS goodness.
iamwalterwhite said:
If you can't boot a rom at all, then I can't tell you exactly which firmware you are on. With your hboot version, though, it looks like you are on GB firmware. Yes, you need to relock to run the RUU. Relock, run the RUU (found here: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ ), unlock again, flash AR 3.15, then move onto ICS goodness.
Click to expand...
Click to collapse
Ok, I relocked, put the PH98IMG on my sdcard, I loaded up the bootloader, pressed power, and it loaded PH98IMG.zip (took a while, said loading) then after it finished loading it said checking PH98IMG.zip (which also took a while) but after that, nothing happened. It just went back to the bootloader main menu... what am I doing wrong?
bigbabys said:
Ok, I relocked, put the PH98IMG on my sdcard, I loaded up the bootloader, pressed power, and it loaded PH98IMG.zip (took a while, said loading) then after it finished loading it said checking PH98IMG.zip (which also took a while) but after that, nothing happened. It just went back to the bootloader main menu... what am I doing wrong?
Click to expand...
Click to collapse
Wow, I just can't catch a break. Turns out, the RUU I downloaded was corrupt. So I got one that works, flashes the RUU, re-locked, reinstalled recovery, and flashed NeWt's and guess what. Hangs at HTC logo. WTF!
Edit: My hboot is 2.27.0000 now...
I just flashed that CM9 with the table being flipped over and it seems to boot okay. So I'm not sure what happened with newts. Oh well, I'm calling it a night. Been at this for over 5 hours (yea I know, that's insane)
bigbabys said:
Wow, I just can't catch a break. Turns out, the RUU I downloaded was corrupt. So I got one that works, flashes the RUU, re-locked, reinstalled recovery, and flashed NeWt's and guess what. Hangs at HTC logo. WTF!
Edit: My hboot is 2.27.0000 now...
I just flashed that CM9 with the table being flipped over and it seems to boot okay. So I'm not sure what happened with newts. Oh well, I'm calling it a night. Been at this for over 5 hours (yea I know, that's insane)
Click to expand...
Click to collapse
You didn't say if you flashed the boot.img from Newt? You should have if you are s-on.
bigbabys said:
Wow, I just can't catch a break. Turns out, the RUU I downloaded was corrupt. So I got one that works, flashes the RUU, re-locked, reinstalled recovery, and flashed NeWt's and guess what. Hangs at HTC logo. WTF!
Edit: My hboot is 2.27.0000 now...
I just flashed that CM9 with the table being flipped over and it seems to boot okay. So I'm not sure what happened with newts. Oh well, I'm calling it a night. Been at this for over 5 hours (yea I know, that's insane)
Click to expand...
Click to collapse
Hahaha, "CM9 with the table flipped over"! I'm sure that's how you felt after 5 hours. Not to make light of how frustrating that can be, but I'm glad you've got something working again.
topgun1953 said:
You didn't say if you flashed the boot.img from Newt? You should have if you are s-on.
Click to expand...
Click to collapse
For both installs, I did a flashboot boot amonrarecovery.img so that it could write to the boot partition. (A nifty little trick courtesy of scotty over at androidforums.com ) however, not wanting to rule out the possibility that maybe that little trick was the cause of the issue, I extraced the boot.img and did a fastboot flash boot boot.img to make sure. However it still was hanging at the HTC logo. That's when I tried the cm9 rom, and used the trick, and it worked fine.
I have no idea why NeWtS didnt' work for me. I can't post in the thread specifically for it yet, but as far as I know I did everything correct this time, so I'm at a loss.
iamwalterwhite said:
Hahaha, "CM9 with the table flipped over"! I'm sure that's how you felt after 5 hours. Not to make light of how frustrating that can be, but I'm glad you've got something working again.
Click to expand...
Click to collapse
Oh believe me, I'm just as glad My original plan was to flash a ROM real fast before going out with some friends. I figured worst case scenario I could flash a backup. But I didn't realize you can't restore a nandroid from recovery if you are S-ON without manually writing the boot image again. So I made myself a nice paperweight and spent the entire night fixing it I'd like to find out what went wrong with NeWts, but to be honest I tinkered with cm9 most of last night and I think I'm happy with it. It's so smooth. And to be honest, I have low expecations for every sense rom now since every single one I tried has the autofocus issue.
Ok, I don't consider myself too much of a noob, I have rooted my old droid incredible many times...however,
I tried rooting my rezound today and believe I was successful at least in getting my bootloader unlocked...(using Hasoon's AIO kit v3.1)
I tried loading aokp rom and it just stuck on the white HTC screen..I can get into hboot, I tried rebooting many times..I downloaded
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.zip and copied it to the sd card, renamed it PH98IMG.zip and tried re-flashing to the same stuck white HTC screen.
I am starting to freak out and wish I didn't have to ask for help here, but I am at the end of the rope and don't know what else to do...
Any kind souls out there that can help me?
Thanks in advance...
Being stuck at the white screen means the kernel didn't load when you installed the rom. I'm assuming your phone is still s-on. You need to flash the kernel seperate from the rom using fastboot. Extract the boot.img from the rom zip and flash it from your PC, I believe the option is there in the all in one tool.
If you wan to run the RUU, you need to re-lock your bootloader first and flash it through the bootloader, not recovery.
mjones73 said:
Being stuck at the white screen means the kernel didn't load when you installed the rom. I'm assuming your phone is still s-on. You need to flash the kernel seperate from the rom using fastboot. Extract the boot.img from the rom zip and flash it from your PC, I believe the option is there in the all in one tool.
If you wan to run the RUU, you need to re-lock your bootloader first and flash it through the bootloader, not recovery.
Click to expand...
Click to collapse
Ok, Thanks a ton!!! Will try that now!
Correction-=-
The boot.img flashing DID work...
Now I just have to find the correct stock ROM... The one I tried said it was too old during the recovery...
any thoughts....Any links to a solid recent stock ROM??
Thanks again!!
Edit: ignore me, posted in wrong thread
If you want to stick with Sense 3.6, I recommend this one - http://forum.xda-developers.com/showthread.php?t=1855605
I've download stock one for my rezound from android police website.
Edit: there is the latest one there, v. 4.xx maybe.
Sent From Rezound S-off rooted VenomRez ROM
drumrjoe said:
Correction-=-
The boot.img flashing DID work...
Now I just have to find the correct stock ROM... The one I tried said it was too old during the recovery...
any thoughts....Any links to a solid recent stock ROM??.
Thanks again!!
Click to expand...
Click to collapse
If you want the latest official RUU, here is a link:
(the RUU you tried to use above was a GB one)
http://androidfiles.org/ruu/?dir=Vigor Grab 3.14.605.12
There was a recent OTA to take it to .13 but it's not really necessary.
If you want to go to the global leak RUU here is a link:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Since you are s-on, if you go to the global leak you won't be able to go back to anything official unless you s-off.
The above will have Verizon bloat, so if you want something stock without bloat you can look through the ROMs. I think there's a couple in there.
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