I am a rooted htc rezound user and am in desperate need for help. My rezound is rooted and the bootloader is unlocked. I just recently tried the new ICS (sense 3.5) rom that was released yesterday. Before i used the rom i did a nandroid backup and then a factory reset. Once i was finished with the rom (because of the bugs it carried), i went to restore my phone using the nandroid backup. When the phone booted back up, after it hit the HTC splash screen, it freezes. The phone is still on, but stuck on a black screen.
I have tried everything. Restoring the nandroid backup multiple times. Flashing a stock rom of the htc rezound in the recovery and also (changing the name to PH98IMG) and the tried flashing it through bootloader/hboot. I also took the stock kernel and did the same exact thing. Ive also downloaded the automatic (.exe) RUU update of the stock rom, from Scott's Roms, but that just kept giving me an "Update Fail" message.
Please help me!
.
Thread moved. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore or install a rom of your choice.
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
Anyway. To restore the stock kernel, I am building a special PH98IMG.zip right now. DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
Omg, thank you sooooooooo much. It worked beautifully! Thank you times a million!
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
Anyway. To restore the stock kernel, I am building a special PH98IMG.zip right now. DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
As stupid as it was that I installed that PH98IMG.zip without looking further into it, or if I had just used fast boot, or cleanFLASH I wouldn't be in this mess. I mainly blame it on having the Eris, INC1, and INC2 all S-OFF, esp my latest phone before the Rezound inc2, was perma S-OFF thanks to the XTC clip so I could flash just about anything without repercussion. But you live and you learn. The Eris had crazy 2.1 leaks and people got stuck on some bad builds, and not only that they were unable to root when root finally came out, because they flashed the 2.1 leak.. I thought I learned my lesson then but with this I didn't know any better. Learn something new everyday. but I disagree with this part. "It is possible you WILL NOT be able to EVER use an RUU to restore in the future."
Jcase has assured me this is not true.
Ignore This and the next post plz
I need ten post in order to post on development forums. I am just going to use my thread so plz ignore this.thnks
I need ten post in order to post on development forums. I am just going to use my thread so plz ignore this.thnks
ggggggggggggggg
hhhhhhhhhhh
Don't give up now! You're almost there...
Lol.. i had to do same to be able to post to the appropriate threads and forums ...
Careful about that. If a mod's having a bad day your posts could be deleted.
Just sayin'.
Sent from my Unlocked/Rooted Rezound running CleanROM 2.0/AmonRa
Sounds like you haven't gotten a hang of flashing a ROM with this device. Try the following.
1 - Download Cleanflash to computer
2 - Download ROM you want to install.
3 - Using a ZIP program, look in the ROM and copy the boot.img file and put in the Cleanflash folder.
4 - Open the back cover, pull battery, wait 10 seconds, put back battery and cover.
5 - Press and hold Vol-, then power for 2 seconds, release power, wait for hboot screen, then release vol-
6 - Connect phone to computer
7 - Make sure HTC Sync is not running on computer
8 - Run CleanFlash and use option 2 to flash boot.img to phone
9 - On the phone, use vol keys to go to recovery (I assume you have Amon Ra recovery already installed)
10 - Follow the menu to mount your sd card
11 - From the computer, your phone's sd card should now show up as a drive
12 - Copy ROM (entire zip file) to sd card, while your at it make sure there is no other ZIP file on the card. You should also mount the internal card and make sure there are no zip files there either.
13 - Unmount the card and disconnect from computer
14 - Now flash the new ROM
15 - reboot phone
feralicious said:
Don't give up now! You're almost there...
Click to expand...
Click to collapse
LOL (I hope an LOL is not cause for banishment)
Sent from my ADR6425LVW using XDA App
Considering I can't post in the development forum yet, I'll try asking here first. I've been reading up for the past few days on flashing recovery and ROMs for my new Rezound, mostly on ADB today to get a feel for the very basics. Right now I'm trying to get Amon Ra onto my device, only to run into the command prompt telling me, "error: cannot load 'recovery-ra-vigor-3.12b-gnm'. The recovery.img is in the root directory where the fastboot and adb executables are located. What am I missing? It's likely a simple fix, but as of yet my searches aren't finding the results I'm after.
Also, when I tried using fastboot to reboot the device to the bootloader (fastboot reboot-bootloader) I got a < waiting for device > message. I ended up just doing a battery pull to get into the fastboot menu on the phone. And as I've seen it asked previously, I did install the drivers when I was going through the unlock process last night. Any suggestions?
canned karma said:
Considering I can't post in the development forum yet, I'll try asking here first. I've been reading up for the past few days on flashing recovery and ROMs for my new Rezound, mostly on ADB today to get a feel for the very basics. Right now I'm trying to get Amon Ra onto my device, only to run into the command prompt telling me, "error: cannot load 'recovery-ra-vigor-3.12b-gnm'. The recovery.img is in the root directory where the fastboot and adb executables are located. What am I missing? It's likely a simple fix, but as of yet my searches aren't finding the results I'm after.
Also, when I tried using fastboot to reboot the device to the bootloader (fastboot reboot-bootloader) I got a < waiting for device > message. I ended up just doing a battery pull to get into the fastboot menu on the phone. And as I've seen it asked previously, I did install the drivers when I was going through the unlock process last night. Any suggestions?
Click to expand...
Click to collapse
Recovery img has to be in the same folder as the fast boot file. Second...you must make sure too add the file ext for that file. Should be .img for a recovery file.
Sent from my ADR6425LVW using XDA App
I hadn't added in the file extension, that did the trick nicely. Thanks!
i love
lamp and rezound
Can i use the PH8 zip to return my Rezound to stock? I am on Scotts leaked ICS rom. It works and all but i want to restore my phone to stock. Im on a Mac so i can't use a RUU. Is there a zip of the latest RUU i can flash in Hboot?
There is a stickied post with the stock vigor RUU's that the phone's came with . Shouldn't have an issue since you used Scott's version he altered the mainver to avoid issues with going back to stock.
Need to relock then run RUU though FYI.. just in case you weren't clear about that.
Related
Hey all,
I'm currently running Innefabilis Deus Alpha Preview and I like it, but will wait for another update that's more stable. Anyway, I tried reverting back to Ineffabilis v1.0 (GB) but when I installed a Kernel by dsb, it says something about "Main version is older!" in fastboot. I read that if you've already flashed the latest leak (ICS), it's not easy to revert back to GB.
I'm wondering if I'm able to use CleanTool to flash dsb's Kernel instead after flashing a GB Rom. Can anyone help me? I've already tried flashing other Kernels via fastboot on my phone and have failed.
This is a common problem right now and you can do a few things...fastest and easiest way is you can flash boot.img via fastboot for short term fix. Just pull the boot.img from the ROM you are flashing. This will get you up and running...but you will run into this again.
For a long term solution...I just came across this...which should help you...
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore or install a rom of your choice.
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
get the PH98IMG from his post here...
http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3
this works well. Myself I just cleaned everything up installed my GB rom, let it fail then pulled the battery and used the trusty droid to mount the sd card from the rezound and put this file on it. booted in to recovery let it do its thing and it worked perfect.
However I'm not sure if pulling the battery after the the file fails is safe, just a risk I took.
Okay, I'm pretty sure that the guys at the other forum site gave up on me. Starting to think that I'm stuck with a paperweight that illuminates a white HTC Screen. I've searched every forum and have had no luck, but here goes:
- I'm on day four of intense troubleshooting. Apparently I'm the only person to ever root a HTC Rezound and then flash a new rom using Rom Manager (first mistake).
-I flashed a new ICS Rom using Rom Manager. I did do a backup using Rom Manager and wiped all of the caches before doing the flash. There was no problem with the install, but once I rebooted, the HTC Screen was my only accomplishment. In addition to that, the CWM Recovery Tool did NOTHING.
After reading and reading, I finally realized that only idiots like myself would still be using Rom Manager over Aman-Ra. Therefore, I installed Aman-Ra via fastboot and flashed a few other roms trying to get past the HTC screen... All of this was without any success.
I was told in a forum by someone much smarter than myself that "the easiest way back to a working phone would be to simply install a new rom like: [ROM 7/11 CONROMV5][4.0.3OTA Sense3.6+DeSense][DeBloated Root Aroma Tweaks][CDMA/GSM]." I was next told that "Conrom will deposit the PH98IMG.zip file on the sd card." This never happened.
SO, Here's where I'm ending up:
It does not boot me into Fastboot after ROM install. Instead, It gives me a "Next" button at the bottom with a log that states:
--
-Checking Model ID
-Success!
Model ID - HTC Rezound (Vigor)
-Ok to proceed
Welcome to CONROM V4!!
Installing...
Sense Selected
Sense Extracted
Face Unlock REMOVE Selected
Face Unlock NOT Extracted
Beginning Experimental Security Identification
read_file() loading "/tmp/initrd.img" failed: No such file or directory
When I click "Next" I get another screen that says:
"Congratulations... CON ROM 4.0 has been installed successfully. Press Finish, and reboot your phone. If S-ON was detected, please reboot to bootloader to flash the boot image. Thanks.
It then goes into the regular reboot process. I do a battery pull, press power+vol down and go back into HBOOT, it runs through it's IMG Check and there's nothing there. I then created a PH98IMG.zip file from the boot image inside the rom's zipped folder. Tried flashing that, and I'm still looking at the HTC Screen.
I've gotten myself into tight jams before, but been able to figure it out... I'm just at the end of my rope here. Someone with more intelligence than myself please tell me what to do to get past this and I promise to never assume that flashing a rom to a Rezound is as easy as it was with my Thunderbolt.
Thanks to whomever takes pitty on me, in advance. (seriously, Thank you)
Start over with a stock RUU zip, renamed to PH98IMG.ZIP. Put it on the SD Card. let er run?
You say you can get to HBOOT?
the only thing that generally fixes huge problems like these are to run the FULL RUU (AKA pull a complete stock rom and rename it PH98IMG.zip, enter HBOOT and let it run TWICE!!) and let it reinstall EVERYTHING (including the radios and such.) Then go into the stock recovery, do a full restore.
Then unlock your boot loader and install Amon-Ra, root and flash a rom correctly
{Full RUU here http://www.androidpolice.com/2012/0...id-4-0-build-3-11-605-22-for-the-htc-rezound/
^ I don't think it is the most recent version, but it should do as long as it is GREATER than the leak you are already on}
Don't try this solution until someone else gives a thumbs up... I don't want to be the one who causes more harm to your phone hahahaha
EDIT: Changed it to PH98IMG, my bad! Should have proof read my post one more time.. Thanks Paulhoop for catching that!
Well he was more complete in his intstructions, but we are recommending the same thing.
However, just want to correct the typo above. PH98IMG... Not PH89IMG
Also not sure about the stock recovery, full restore. But I would let the stock RUU setup run once before going to AmonRa
brandononeal00 said:
Okay, I'm pretty sure that the guys at the other forum site gave up on me. Starting to think that I'm stuck with a paperweight that illuminates a white HTC Screen. I've searched every forum and have had no luck, but here goes:
- I'm on day four of intense troubleshooting. Apparently I'm the only person to ever root a HTC Rezound and then flash a new rom using Rom Manager (first mistake).
-I flashed a new ICS Rom using Rom Manager. I did do a backup using Rom Manager and wiped all of the caches before doing the flash. There was no problem with the install, but once I rebooted, the HTC Screen was my only accomplishment. In addition to that, the CWM Recovery Tool did NOTHING.
After reading and reading, I finally realized that only idiots like myself would still be using Rom Manager over Aman-Ra. Therefore, I installed Aman-Ra via fastboot and flashed a few other roms trying to get past the HTC screen... All of this was without any success.
I was told in a forum by someone much smarter than myself that "the easiest way back to a working phone would be to simply install a new rom like: [ROM 7/11 CONROMV5][4.0.3OTA Sense3.6+DeSense][DeBloated Root Aroma Tweaks][CDMA/GSM]." I was next told that "Conrom will deposit the PH98IMG.zip file on the sd card." This never happened.
.
Thanks to whomever takes pitty on me, in advance. (seriously, Thank you)
Click to expand...
Click to collapse
You have to lock the bootloader first if you want to run the RUU.
First off...you said s-on..
Do you now what firmware you are on? Ginberbread or ICS? If you are on GB you should have installed a SD Card patch as part of your ROM flashing process. If you didn't, that is part of your problem. What happens when you try to flash the boot.img? Do you do it through fastboot? or PH98img file? It sounds like the boot.img is not flashed correctly.
topgun1953 said:
You have to lock the bootloader first if you want to run the RUU.
First off...you said s-on..
Do you now what firmware you are on? Ginberbread or ICS? If you are on GB you should have installed a SD Card patch as part of your ROM flashing process. If you didn't, that is part of your problem. What happens when you try to flash the boot.img? Do you do it through fastboot? or PH98img file? It sounds like the boot.img is not flashed correctly.
Click to expand...
Click to collapse
Ok. First off, wow, what an awesome response. I had rooted the phone through fastboot, but was still on the stock GB. I didn't know about the SD Card Patch. When I try to flash the boot.img, I did that by extracting the boot.img from the rom folder, renaming to PH98.img, and running that through the HBOOT Process (I didn't try it with fastboot). The file would update, begin the "parsing' process, and then stop and go back to the basic HBOOT screen. What would be the correct way to flash the boot.img file? What patch should I have installed relating to the SD Card, and is it too late for that?
brandononeal00 said:
Ok. First off, wow, what an awesome response. I had rooted the phone through fastboot, but was still on the stock GB. I didn't know about the SD Card Patch. When I try to flash the boot.img, I did that by extracting the boot.img from the rom folder, renaming to PH98.img, and running that through the HBOOT Process (I didn't try it with fastboot). The file would update, begin the "parsing' process, and then stop and go back to the basic HBOOT screen. What would be the correct way to flash the boot.img file? What patch should I have installed relating to the SD Card, and is it too late for that?
Click to expand...
Click to collapse
The boot file should be named ph98img.zip CHECK your named file (PH98.img???), the computer should put the .zip on it. Just be sure its not named ph93img.zip.zip!
The other way, if you're comfy with fastboot commands is to put the boot.img in the same directory as fastboot and type "fastboot boot boot.img" . No its not too late to do the SD Card Patch. You can get it here (among other places), I believe its the 'Old Firmware patch" http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/ . JUst flash in recovery.
The info for your ROM says that the installer would identify the need for the SD card patch, so maybe it did install it? Won't hurt to do it yourself though. Did you consider a more 'basic' ICS rom, like CLeanRom4.5 or the new rooted 3.14.605.12 one?
I'm on Newt's One xXx, ICS sense 4 rom myself.
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
Let me start off by saying that I'm a complete idiot and wasn't being very careful.
I have several problems with my Rezound right now and I'll try to be clear and concise. My internal SD card won't mount in the recovery menu, nor HBOOT, therefore I cannot flash PH98img.zip in HBOOT. My external SD will mount, but I'm not sure if the PH98img.zip will work from the external SD because it doesn't show up in HBOOT. My HBOOT reads as follows:
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.10.00000
eMMC-boot
OCT 5 2011,21:18:48
And also, here's a weird thing: My phone will show up in adb devices only when the phone is off or when I'm in the Recovery menu. My phone won't appear in adb devices when I'm in HBOOT menu. I'm running ClockworkMod Recovery v6.0.2.3.
I have tried using a few different ROMs to no avail. I think my main problem as of now is that I cannot access my internal SD card. Before I install a ROM I wipe everything I can think to wipe, cache, dalvik cache, factory reset. Some of the ROMs have the Aroma installer where it asks if I want to wipe on those and I say yes every time. I cannot start my phone because I'm stuck on HTC white screen whenever I try to boot the phone. I've tried using the Old_Firmware_Patch.zip and the GB Firmware Patch.zip. I have had no luck so far. Again, I'm sorry that I'm not exactly sure what I'm doing and I need a bit of help. Thank you and I appreciate any help that you can give.
Additional Information
Prior to this complete failure in my phone I was using an early leak of ICS, one of Newts ROMs. His ROM didn't support 4G and had trouble with a few other things including stock wifi settings. Every time I tried to go to wifi settings the "com.settings.htc" or some such process would crash. So I wanted to update to a newer ICS ROM that hopefully supported 4G and didn't have problems with wifi settings. I thought it would be as simple as loading a ROM onto the external SD and loading it from recovery, but it wasn't that easy. Because I'm S-ON I apparently missed a few steps and forgot that I have to flash PH98img.zip. But now that I cannot access my internal SD card, I cannot flash PH98img.zip as far as I know.
First thing you want to do is get off of Clockwork Mod recovery. It doesn't play well with the Rezound. Go grab Amon Ra and flash v3.16.
Secondly, you can flash a PH98IMG file off the external sd, providing you can read it of course.
I think you are still on GB firmware based on your hboot, not completely sure about that. But it's def an old hboot.
So actually, I would run the RUU and update all your firmware, don't bother flashing Amon Ra first, do that after the RUU. Find it here:
http://androidfiles.org/ruu/?dir=Vigor
Top one, 3.14.605.12. Then after you run that, you can check for and accept the latest OTA that came out a couple weeks ago and then you'll be up to date with the official updates.
You'll need to relock the phone before running the RUU
fastboot oem lock
And save everything you need from the phone first since this will wipe everything and get you back to factory stock.
Then to run the RUU attach the phone to your pc and double click on the exe RUU file. It will do it's thing. Or you can use the following commands in fastboot to get it going:
fastboot oem rebootRUU
fastboot flash zip NameOfZip.zip
Make sure you let it go all the way through. I ran the global RUU and the screen went black for a while then it goes back to finishing up, so if that happens just let it keep going. I think you end up in bootloader when it's done, and it'll ask you if you want to reboot. You should go ahead and boot up and make sure it's working okay.
After you run the RUU you will need to unlock again. Then flash Amon Ra, flash superSU for root (though I think you can just get root via Amon Ra again now) and make a nandroid of stock so you can always go back to this when you run into trouble, then flash a custom ROM if you choose.
That should sort everything out since like I said, it'll be a clean start and you'll get everything updated.
Oh, and the PH98IMG.zip file you have to flash because of being s-on is the kernel for the ROM you are flashing. So know that each PH98IMG.zip file is not the same as the other, the ROM makes the one you need using the kernel that is specifically for that ROM. So you'll either need to pull it out of the ROM and flash via fastboot, download the separate PH98IMG file if there is one in the ROM's thread, or the ROM may make one during the flash and leave the PH98IMG file on your SD card in which case you go to bootloader and accept the update, which will be the kernel.
If you don't flash the kernel then the phone won't boot, it'll just get stuck.
One last thing, I would grab CleanWipe from the Dev section and use that for wiping whenever you change ROMs. It'll really get the job done.
Back to stock now
You, feralicious, are a beautiful person for replying so detailed lol. I got my phone to start up gladly. I just now read your post. Earlier I got it working by following a thread which basically said exactly what you said: relock using fastboot oem lock and then do the lastest RUU. It was a thing of beauty. I as so lost prior to that.
It's good to know that each PH98IMG.zip is different per rom. I had no idea. I'm going to stay stock for a while. It's just nice to finally see that 4g up on the top of my phone after having dealt with 3g only for like 6 months. I'll definitely come back to this site if I have an trouble while attempting to re-root the phone. Thanks so much for your excellent reply.
Q&A for [ROM][4.4.4_r2][OFFICIAL][GPL] LiquidSmooth v3.2 - vigor - 10|12|14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
bunchies said:
Final KitKat build coming soon, Lollipop was released this morning :thumbup:
Let's see if the Rezound can run android 5.0
Click to expand...
Click to collapse
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
catcher8587 said:
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
Click to expand...
Click to collapse
Yeah, you will be fine
s-on users flash boot.img in fastboot
Last Build
I set the last build and at once found an error. If to come Settings - the Mobile network - Settings of the operator you give out an error: "In application of "com.android.phone" there was an error..." At all so? I quickly discharge the battery for some reason!
Crash video playing
added small problem... When I want to view video sometimes issues the error message. Video doesn't play...
re:chrome floating windows
Just uninstall and download an older version of chrome. Then, don't accept the update. You can't turn off the floating windows. Very annoying
HTC Rezound Liquidsmooth 3.2 ROM install failure
I used this link (theunlockr.com/2013/10/22/how-to-root-the-htc-rezound/) on my stock HTC Verizon Rezound to unlock the bootloader, installed TWRP, and SuperSU to gain access to root.
Then I downloaded LiquidSmooth 3.2 11/5/14 R2 -- Android 4.4.4 and Gapps 4.4.4 Build 8.1 (not Build 7 on this site) I used TWRP to flash both files in the same flash event to the phone. I had placed the files on the INTERNAL SD in the DOWNLOAD directory. Wiped before and after the flash. Phone came up to HTC screen, Blinked, and returned to HTC screen. Waited 10 minutes or so and had to pull battery . Tried another boot with same results. Restored. Repeated same results.
Downloaded the LS v3.2 file again. Downloaded an md5 checker program to my computer. Both files passed. Repeated using second v3.2 file with same results. Downloaded the 8/21/2014 version of the file, md5 checked it, and repeated with same results.
Then downloaded the final LS v2.9 JB4.2.2 file and the appropriate GAPPS file and md5ed it. Repeated with same results.
I am now back to my rooted but stock ROM. I would like to get this LS v3.2 KitKat ROM installed, but am at my wits end.
I also used this link (android.wonderhowto.com/how-to/ultimate-guide-using-twrp-only-custom-recovery-youll-ever-need-0156006/) to troubleshoot. That is why I did a wipe in advance of the first install attempt and I think most of the others as well, although I couldn't tell it helped. I tried the Fix Permissions hint several times but it failed each time.
The only think I have ever read about on HTC phones is S-On or S-Off, but I don't think this applies as neither link source I referred to mentioned S-ON.
Any help would be appreciated. Thanks in advance.
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Thanks a Million or perhaps 10 million!!!
acejavelin said:
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Click to expand...
Click to collapse
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
xdatsellers said:
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
Click to expand...
Click to collapse
Most general tutorials on flashing ROMs on HTC devices includes this information, although most devs will say their ROMs are for S-OFF devices only, it is assumed with a little fastboot trickery most ROMs will work fine, but devs usually make the assumption you know what you are doing.
I would HIGHLY recommend you go S-OFF... if something catastrophic happens and you are S-ON there is often no method of recovery, since all current RUU (HTC's proprietary ROM restoration image) files are prior to current, so do downgrade and restore to stock you must be S-OFF. Rumrunner makes the S-OFF process pretty painless if you are on a custom ROM already.
The boot image, or more accurately the /boot partition, cannot be written to under normal recovery well S-ON, so that affects a nandroid restore as well, you would have to extract the boot image and flash it manually as well to restore a nandroid. BUT, if you boot the recovery image via fastboot it gets around the /boot write restriction even when S-ON... this is a key difference, essentially you are taking the recovery image and telling the phone "this is your new kernel, start it like a ROM" which gets around some of the S-ON restrictions.
Grey network bars
Hello bunchies
I really enjoyed using this rom except this problem my network bars are grey but i can make and receive calls and use the 3g on slow speed (the problem when i call the customer service centre i can't press numbers)
I've checked hboot radio and recovery they are updated
Sorry for my bad English and thanks in advance
Need help to install liquidsmooth
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Thank you
Sent from my SM-N900 using XDA Free mobile app
edwardnizz said:
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Click to expand...
Click to collapse
Assuming you are on current Hboot & radios, upgrade to latest TWRP, flash ROM ZIP and Gapps, fastboot flash boot.img, then reboot and enjoy.
Hello i'm just asking if there wont be any problems with rom update such as recovery boot loop or Freeze or crashes .....etc kthnxbai
can't send SMS or ssd with liquidsmooth 3.2
Hi. As the title says , i cant sens SMS nor use ussd codes. Another issue is that i can't play music. Any help would be appreciated.