HTC Rezound
VIGOR PVT SHIP S-ON 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
A few weeks ago I was had phone Rezound hooked up to my PC and I was flashing it to Pageplus on CDMA Workshop. After I finished I rebooted my and it got stuck in an infinite bootloop. I've been trying for weeks to figure out what went wrong. The phone has an unlocked bootloader, I can flash custom ROM's and recoveries, and the phone responds to ADB commands, but no matter what I do it doesnt seem to work. I've tried about 20 different ROM's. I can't do a full RUU because my phone's Hboot is too new. I'm all out of ideas please help.
jpetreski said:
HTC Rezound
VIGOR PVT SHIP S-ON 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
A few weeks ago I was had phone Rezound hooked up to my PC and I was flashing it to Pageplus on CDMA Workshop. After I finished I rebooted my and it got stuck in an infinite bootloop. I've been trying for weeks to figure out what went wrong. The phone has an unlocked bootloader, I can flash custom ROM's and recoveries, and the phone responds to ADB commands, but no matter what I do it doesnt seem to work. I've tried about 20 different ROM's. I can't do a full RUU because my phone's Hboot is too new. I'm all out of ideas please help.
Click to expand...
Click to collapse
Did you manually flash the boot.img?
Remember that when S-ON, flashing a ROM when booting recovery installed on the device will NOT flash the boot image, you have to do it manually from fastboot... OR you need to boot recovery from fastboot and then flash the ROM... if you don't do one of these methods your device will likely not boot since the boot image isn't updated properly.
Yea i flashed the boot image manually through adb. The phone isnt getting stuck at the boot screen. It goes through the boot screen thens shuts off and tries to boot again. I dont think its the ROM itself thats the problem. Ive tried a bunch of Roms and i know how to flash the boot image but it still doesnt work
jpetreski said:
Yea i flashed the boot image manually through adb. The phone isnt getting stuck at the boot screen. It goes through the boot screen thens shuts off and tries to boot again. I dont think its the ROM itself thats the problem. Ive tried a bunch of Roms and i know how to flash the boot image but it still doesnt work
Click to expand...
Click to collapse
If you try to wipe everything, does any partition fail?
acejavelin said:
If you try to wipe everything, does any partition fail?
Click to expand...
Click to collapse
This is what i get when I try to wipe everthing(Data, Cache, Dalvik Cache, System, Internal Storage, and Android Secure).
Hmm... Unable to mount /emmc and an inability to mount internal storage isn't good. What version of TWRP are you using? Try repairing the emmc/internal storage partition with TWRP, it should be Fat32.
acejavelin said:
Hmm... Unable to mount /emmc and an inability to mount internal storage isn't good. What version of TWRP are you using? Try repairing the emmc/internal storage partition with TWRP, it should be Fat32.
Click to expand...
Click to collapse
Im using TWRP v2.8.0.1
I reinstalled Cyanogen Mod and tried to wipe everything again and im not getting that error anymore. All the wipes went through just fine, but I still cant get past the boot screen.
How long are you waiting? First boot on some ROMs can exceed 5 minutes... Can you get a logcat?
If that shows nothing, try an early JB 4.1or 4.2 ROM... Kinda driving in snowstorm ATM, I can recommend one later. Those had a bug let's swap the internal and external storage partition mounts, in this case we can use it to our benefit.
acejavelin said:
How long are you waiting? First boot on some ROMs can exceed 5 minutes... Can you get a logcat?
If that shows nothing, try an early JB 4.1or 4.2 ROM... Kinda driving in snowstorm ATM, I can recommend one later. Those had a bug let's swap the internal and external storage partition mounts, in this case we can use it to our benefit.
Click to expand...
Click to collapse
I have left it on for at least 20 mins. The problem is not that it get stuck at the boot screen. The phone keeps shutting off and turn back on at the boot screen. Also not really sure how to get a logcat. Sorry im kinda of a noob at this.
acejavelin said:
How long are you waiting? First boot on some ROMs can exceed 5 minutes... Can you get a logcat?
If that shows nothing, try an early JB 4.1or 4.2 ROM... Kinda driving in snowstorm ATM, I can recommend one later. Those had a bug let's swap the internal and external storage partition mounts, in this case we can use it to our benefit.
Click to expand...
Click to collapse
Hey I think I was able to figure out how to generate the logcat. Let me know if this is what your looking for?
jpetreski said:
Hey I think I was able to figure out how to generate the logcat. Let me know if this is what your looking for?
Click to expand...
Click to collapse
Thanks... I'll look at it tonight after work
jpetreski said:
Hey I think I was able to figure out how to generate the logcat. Let me know if this is what your looking for?
Click to expand...
Click to collapse
Unfortunately, this doesn't show much, it looks mostly normal, no looping and nothing sticking... can you try this and pastebin the output?
http://forum.xda-developers.com/showpost.php?p=39981717&postcount=8
acejavelin said:
Unfortunately, this doesn't show much, it looks mostly normal, no looping and nothing sticking... can you try this and pastebin the output?
http://forum.xda-developers.com/showpost.php?p=39981717&postcount=8
Click to expand...
Click to collapse
I think I got it. I attatched the txt file i got.
This was my initial concern but I wanted to verify before I said anything earlier... Got a feeling you messed something up when you tried to program it to PagePlus, it can't talk to the radios anymore...
E/use-Rlog/RLOG-QC-QMI( 156): linux_qmi_qmux_io.c: Unable to open port id /dev/smdcntl0
E/use-Rlog/RLOG-QC-QMI( 156): qmi_qmux_open_connection: QMI_QMUX_IO_PLATFORM_OPEN_CONN failed -1
E/use-Rlog/RLOG-QC-QMI( 156): qmuxd: opening connection for RMNET0 failed, Waiting 500 milliseconds before retry
I/kickstart( 486): INFO: function: tx_data:346 Transmitting 1048576 bytes
D/QC-DS-LIB( 152): ifioctl: open port failed: (19)No such device
D/QC-DS-LIB( 152): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 6
The Kernel/OS is trying to open communication to the radios and failing, it can't continue... this error is repeated several times, thus the appearance of a "bootloop", which actually the OS stuck in loop trying to bring up communication with the radio layer and failing.
Any chance you can revert the changes? If not, you will probably need to RUU, which could be difficult since you are S-ON.
acejavelin said:
This was my initial concern but I wanted to verify before I said anything earlier... Got a feeling you messed something up when you tried to program it to PagePlus, it can't talk to the radios anymore...
E/use-Rlog/RLOG-QC-QMI( 156): linux_qmi_qmux_io.c: Unable to open port id /dev/smdcntl0
E/use-Rlog/RLOG-QC-QMI( 156): qmi_qmux_open_connection: QMI_QMUX_IO_PLATFORM_OPEN_CONN failed -1
E/use-Rlog/RLOG-QC-QMI( 156): qmuxd: opening connection for RMNET0 failed, Waiting 500 milliseconds before retry
I/kickstart( 486): INFO: function: tx_data:346 Transmitting 1048576 bytes
D/QC-DS-LIB( 152): ifioctl: open port failed: (19)No such device
D/QC-DS-LIB( 152): netmgr_kif_ifioctl_open_port() failed for rmnet0 on attempt 6
The Kernel/OS is trying to open communication to the radios and failing, it can't continue... this error is repeated several times, thus the appearance of a "bootloop", which actually the OS stuck in loop trying to bring up communication with the radio layer and failing.
Any chance you can revert the changes? If not, you will probably need to RUU, which could be difficult since you are S-ON.
Click to expand...
Click to collapse
Damn that what I was afraid of. I cant change anything since i cant get booted. I tried to figure out how to RUU but I couldnt because im S-on and the Hboot version is 2.28. Is there a way to actually do the RUU or a way to go S-off without going to boot.
jpetreski said:
Damn that what I was afraid of. I cant change anything since i cant get booted. I tried to figure out how to RUU but I couldnt because im S-on and the Hboot version is 2.28. Is there a way to actually do the RUU or a way to go S-off without going to boot.
Click to expand...
Click to collapse
Hmmm... Unfortunately no, there is no way to RUU without being booting, and no way to RUU well S-On with that Hboot... Here is what I would do...
Download this ROM: http://forum.xda-developers.com/showthread.php?t=2260154
This Firmware/Radios: https://drive.google.com/file/d/0B-tbsbTajV1UaUVVSTRZVWhQVlk/view?usp=sharing
This recovery: http://techerrata.com/file/twrp2/vigor/openrecovery-twrp-2.8.1.0-vigor.img
Either Wipe Script from this post: http://forum.xda-developers.com/showpost.php?p=38808921&postcount=122
Then place the ROM, Firmware, and Wipe script ZIPs onto your microSD card, and the TWRP image file in your fastboot directory, now boot up into Hboot and start fastboot, now enter this from your fastboot/adb directory:
fastboot boot openrecovery-twrp-2.8.1.0-vigor.img
Now flash just the FIrmware/Radios, pay attention that it flashes successfully, if it does, reboot into the bootloader and start fastboot, then issue the fastboot boot command again.
In TWRP, go to to Wipes and Advanced, and wipe everything except MicroSD/External Storage, twice... Now go Home and go to Install, and flash individually in this order: Wipe script, then ROM zip (do it TWICE)
Now go Home again and into Wipes, Advanced, and select Cache and Dalvik Cache -ONLY- and wipe them once, now remove the USB cable and reboot. Hopefully it will boot fully into the OS, even if it fails some things we don't care, we just need it to boot fully.
Hopefully we can boot... If this works, we can try to install the unsecure kernel from here: http://forum.xda-developers.com/showthread.php?t=1911297 and use Rumrunner to S-OFF.
I know this is a crazy, long procedure, but it is the best we can do at the moment, being S-ON we MUST get the device bootable in order to S-OFF and revert so you can RUU.
acejavelin said:
Hmmm... Unfortunately no, there is no way to RUU without being booting, and no way to RUU well S-On with that Hboot... Here is what I would do...
Download this ROM: http://forum.xda-developers.com/showthread.php?t=2260154
This Firmware/Radios: https://drive.google.com/file/d/0B-tbsbTajV1UaUVVSTRZVWhQVlk/view?usp=sharing
This recovery: http://techerrata.com/file/twrp2/vigor/openrecovery-twrp-2.8.1.0-vigor.img
Either Wipe Script from this post: http://forum.xda-developers.com/showpost.php?p=38808921&postcount=122
Then place the ROM, Firmware, and Wipe script ZIPs onto your microSD card, and the TWRP image file in your fastboot directory, now boot up into Hboot and start fastboot, now enter this from your fastboot/adb directory:
fastboot boot openrecovery-twrp-2.8.1.0-vigor.img
Now flash just the FIrmware/Radios, pay attention that it flashes successfully, if it does, reboot into the bootloader and start fastboot, then issue the fastboot boot command again.
In TWRP, go to to Wipes and Advanced, and wipe everything except MicroSD/External Storage, twice... Now go Home and go to Install, and flash individually in this order: Wipe script, then ROM zip (do it TWICE)
Now go Home again and into Wipes, Advanced, and select Cache and Dalvik Cache -ONLY- and wipe them once, now remove the USB cable and reboot. Hopefully it will boot fully into the OS, even if it fails some things we don't care, we just need it to boot fully.
Hopefully we can boot... If this works, we can try to install the unsecure kernel from here: http://forum.xda-developers.com/showthread.php?t=1911297 and use Rumrunner to S-OFF.
I know this is a crazy, long procedure, but it is the best we can do at the moment, being S-ON we MUST get the device bootable in order to S-OFF and revert so you can RUU.
Click to expand...
Click to collapse
I couldn't get the wipe script. The files and the link were deleted. Do you know of another way to get it. I tried googling cleanwipe v2.0 but couldn't find a different location.
jpetreski said:
I couldn't get the wipe script. The files and the link were deleted. Do you know of another way to get it. I tried googling cleanwipe v2.0 but couldn't find a different location.
Click to expand...
Click to collapse
The OP of that thread had the links to v1.0, it will work fine for what we need, actually, I am not sure of the difference:
http://forum.xda-developers.com/showthread.php?t=1562176
If they don't work, I know I have them at home and can throw them on Drive later. BTW, if you can't get the Wipe Script for whatever reason, just continue and skip it, it isn't really essential, I just use it as a safeguard when things are not right so we are at a good starting point.
acejavelin said:
Hmmm... Unfortunately no, there is no way to RUU without being booting, and no way to RUU well S-On with that Hboot... Here is what I would do...
Download this ROM: http://forum.xda-developers.com/showthread.php?t=2260154
This Firmware/Radios: https://drive.google.com/file/d/0B-tbsbTajV1UaUVVSTRZVWhQVlk/view?usp=sharing
This recovery: http://techerrata.com/file/twrp2/vigor/openrecovery-twrp-2.8.1.0-vigor.img
Either Wipe Script from this post: http://forum.xda-developers.com/showpost.php?p=38808921&postcount=122
Then place the ROM, Firmware, and Wipe script ZIPs onto your microSD card, and the TWRP image file in your fastboot directory, now boot up into Hboot and start fastboot, now enter this from your fastboot/adb directory:
fastboot boot openrecovery-twrp-2.8.1.0-vigor.img
Now flash just the FIrmware/Radios, pay attention that it flashes successfully, if it does, reboot into the bootloader and start fastboot, then issue the fastboot boot command again.
In TWRP, go to to Wipes and Advanced, and wipe everything except MicroSD/External Storage, twice... Now go Home and go to Install, and flash individually in this order: Wipe script, then ROM zip (do it TWICE)
Now go Home again and into Wipes, Advanced, and select Cache and Dalvik Cache -ONLY- and wipe them once, now remove the USB cable and reboot. Hopefully it will boot fully into the OS, even if it fails some things we don't care, we just need it to boot fully.
Hopefully we can boot... If this works, we can try to install the unsecure kernel from here: http://forum.xda-developers.com/showthread.php?t=1911297 and use Rumrunner to S-OFF.
I know this is a crazy, long procedure, but it is the best we can do at the moment, being S-ON we MUST get the device bootable in order to S-OFF and revert so you can RUU.
Click to expand...
Click to collapse
I'm not sure i'm flashing the firmware/radio right. Do I just install it through twrp like a ROM. Cuz it says it failed when I try that.
jpetreski said:
I'm not sure i'm flashing the firmware/radio right. Do I just install it through twrp like a ROM. Cuz it says it failed when I try that.
Click to expand...
Click to collapse
Hmm... I hoped by booting TWRP from fastboot we could bypass some of the S-On restrictions like it does with the kernel, maybe not, what kind of error is it giving you?
We can manually flash via fastboot, but if it fails in TWRP, it will likely fail if we try to flash the other way and it will take me a while look up the process.
The key here is we have to get something to boot fully, any ROM with an insecure kernel and working WiFi is sufficient. You could try some ROMs that are quick and plain like Evervolv, Plain-Andy, Talon or something similar... We don't care about Gapps or anything else, just the ROM itself, from there we can get S-Off, I know we can fix this if we can get to that point. So next step is try some ROMs, put them on the SD card, but flash them from TWRP booted via fastboot boot command.
Whatever changes were made in the RIL broke something bad... Those files are locked to us until we obtain S-Off, right now I think we need to concentrate on getting S-Off... Do you have a working Linux installation and are you familiar with using the shell by chance?
Related
Alright, so I've got an S-On rooted Rezound and I'm stuck in the boot loop. YES I've read all the posts about logging in and dialing *#etc and also to go into Mobile Network and switch to LTE/CDMA, but I can't dial anything because the phone cuts off before I get a chance, and the LTE switch does nothing. I've tried flashing several different kernels, using the adb method and the PH98IMG methods, I've tried installing several different ROMS, I've done at least 10 different wipes/factory resets, I boot my phone without the cover, SIM card and without the SD card..and I'm still stuck in this boot loop. Someone please help a noob
---- EDIT WITH SOLUTION ----
Here's my "solution" to this issue. I'm sure it's located somewhere in these forums, but I couldn't find it so I imagine others can't either. Essentially, you're going to have to S-Off. Here's the solution:
I believe my recovery started acting funny after I failed to S-Off properly the first time. Amon Ra was all gimmicky and said stuff like "E: can't find cache" and reinstalling the recovery/wiping everything (and I mean everything: external SD, internal SD, cache, partioning SD card etc..) wasn't working. I tried re-installing Amon Ra through command prompt with the adb, I tried reinstalling my ROMS but my phone wasn't having it.
It got to the point all I could boot into was a white HTC screen, so I then tried out Twrp's 2.1 Touchscreen (I wasn't S-Off yet) recovery (I don't have enough posts to post a link yet ) which INITIALLY reported the same "E: can't find cache" errors as Amon Ra, BUT when I wiped my files in Twrp it seemed to actually fix them...I'm not sure exactly what I wiped or formatted that fixed the "E: can't find mount/cache" issues, so try everything.
So my ROM installed but I was still stuck on the white HTC logo. This is where I INSTALLED A NEW KERNEL THROUGH ADB. I wish I knew which kernel I installed, but I have like 10 and I just picked a random one. The point is if you're still stuck at a white HTC screen, install a new kernel.
So I got a recovery on the phone, and then I tried to S-Off again but I didn't have a good ROM installation so that was hanging at the HTC white screen. I then installed CleanROM DE 1.4 and I was able to boot into it, but ran into my initial problem of it crashing after dialing a number and entering infinite reboot. However, it would stay on just long enough for me to run ControlBear's program to S-Off.
So I S-Offed, I downloaded the Gingerbread RUU (the .exe version for Windows), I installed it, and now I can dial numbers and I'm all goodie again. Unfortunately, I honestly think the only way I was escaping my trouble was doing an S-Off, unless they leak a Ice Cream Sanwhich executable for Windows.
TL;DR Install Twerp 2.1 through adb, wipe everything, install CleanROM DE 1.4, install kernel S-Off, run Gingerbread RUU .exe
autotuneuser said:
Alright, so I've got an S-On rooted Rezound and I'm stuck in the boot loop. YES I've read all the posts about logging in and dialing *#etc and also to go into Mobile Network and switch to LTE/CDMA, but I can't dial anything because the phone cuts off before I get a chance, and the LTE switch does nothing. I've tried flashing several different kernels, using the adb method and the P87etc methods, I've tried installing several different ROMS, I've done at least 10 different wipes/factory resets, I boot my phone without the cover, SIM card and without the SD card..and I'm still stuck in this boot loop. Someone please help a noob
Click to expand...
Click to collapse
Have you tried running a RUU to put it back to factory like you just bought it?
I can't tell you how many times I've had to do that to fix stuff.
Magestic12 said:
Have you tried running a RUU to put it back to factory like you just bought it?
I can't tell you how many times I've had to do that to fix stuff.
Click to expand...
Click to collapse
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
autotuneuser said:
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
Click to expand...
Click to collapse
It is if you're s-on. Also, what did you mean by "P87etc," are you flashing the files properly?
autotuneuser said:
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
Click to expand...
Click to collapse
People say a lot of things are impossible, most have the virtue of never being tried.
This is the one I used to fix mine when I screwed up the partitions on my phone. I will warn you, the link in the thread takes you to another site & you have to sign up to download it. Its completely free & legit, but it won't let you download unless you register which is STUPID!
http://forum.xda-developers.com/showthread.php?p=25664508
Let me know if that helps
Oh & BTW I was & still am on the ICS leaks when I did this, so you'll be fine. You will lose everything on your phone though, because it wipes everything. But if you can't use it, that's not really an issue I guess.
tekhna said:
It is if you're s-on. Also, what did you mean by "P87etc," are you flashing the files properly?
Click to expand...
Click to collapse
The PH98IMG file. And I believe I'm flashing the properly..I do it twice; flashboot in adb, it tells me success, I then flash again right there, and then I reboot back to the bootloader and flash again so I do it 3 times in total.
I'm downloading the Vigor executable now. It's going to take a while but I'll report back with my results.
autotuneuser said:
The PH98IMG file. And I believe I'm flashing the properly..I do it twice; flashboot in adb, it tells me success, I then flash again right there, and then I reboot back to the bootloader and flash again so I do it 3 times in total.
I'm downloading the Vigor executable now. It's going to take a while but I'll report back with my results.
Click to expand...
Click to collapse
PH98IMG is not going to help you in this situation. You are going to have to download & run the RUU that I linked in the previous post. Trust me on this, not only have I already tried that before, I've blown my phone up enough times to know.
Magestic12 said:
PH98IMG is not going to help you in this situation. You are going to have to download & run the RUU that I linked in the previous post. Trust me on this, not only have I already tried that before, I've blown my phone up enough times to know.
Click to expand...
Click to collapse
Ok, I went to use the RUU and at first I got error 150, so I read somewhere I should lock my bootloader, so I relocked and now I get error 140, whcih is bootloader verision error. I think that's because I'm on ICS with S-On right? Is there any ICS RUU I can use to restore my phone? I downloaded Vigor_Stock_Doedexed_3.14.605.5 before but it still wasn't working for me.
autotuneuser said:
Ok, I went to use the RUU and at first I got error 150, so I read somewhere I should lock my bootloader, so I relocked and now I get error 140, whcih is bootloader verision error. I think that's because I'm on ICS with S-On right? Is there any ICS RUU I can use to restore my phone? I downloaded Vigor_Stock_Doedexed_3.14.605.5 before but it still wasn't working for me.
Click to expand...
Click to collapse
And as far as this goes yeah you can't use the .exe if your on ICS firmware with s-on and there are no available .exe's for ICS
Sent from my ADR6425LVW using Tapatalk 2
Unless you are already on the gingerbread build, and it sounds like your not, if you are s-on, it simply will not work. My suggestion is to download the latest leak and that should get you going. If it were me, and I aleady did it, download the latest leak here: http://android.thesmallprint.org/ICS.LEAK.3.14.605.5_PH98IMG.zip. Rename it PH98IMG.zip and put it on your external sd card. Should take less than 10 mins to download. Reboot into bootloader and let hboot install it. Make sure you are locked or relocked. After that is installed either delete or change the name of that file. Reboot into bootloader, unlock, and install either amon ra or tpwr and you can reinstall that rooted rom.
what he said
mikey's comments just previous are totally right, but after install, i would recommend
a factory reset, maybe even twice.
your bootloop problem should be cured then...
I was on the latest ICS firmware running an ICS ROM when I had to run the RUU I gave the link for & it worked fine for me.
Here's my suggestion & you can take it for what its worth.
I would download the latest HBoot & Radios & flash them.
Then if you can get into recovery, wipe everything, manually wipe the system, boot, etc. Then after that try running the RUU.
I just did this earlier in the week & it worked fine & my phone was all screwed up because the partitions were mounting to the wrong places & just all messed up.
I am by no means a dev or an expert, I'm just telling you what I did.
WHATEVER YOU CHOSE, YOU DO AT YOUR OWN RISK, but I don't see where you really have a choice.
Let me know if I can be of anymore help as I know what its like to have a phone that's freaking out on you. You can PM me or post here which ever you prefer. If after that we still can't get it fixed, we'll go find a dev to help us.
mikeyk101 said:
Unless you are already on the gingerbread build, and it sounds like your not, if you are s-on, it simply will not work. My suggestion is to download the latest leak and that should get you going. If it were me, and I aleady did it, download the latest leak here: . Rename it PH98IMG.zip and put it on your external sd card. Should take less than 10 mins to download. Reboot into bootloader and let hboot install it. Make sure you are locked or relocked. After that is installed either delete or change the name of that file. Reboot into bootloader, unlock, and install either amon ra or tpwr and you can reinstall that rooted rom.
Click to expand...
Click to collapse
Well now my recovery is saying it can't mount various things like "E: can't mount b dev/block/ blah blah"
And I tried flashing my ROM through Amon recovery but it's saying it can't open the file because it's (bad). I formatted the SD card and I'm still getting the issue. Any ideas?
Did you download the one from the link? You don't flash that PH98IMG.zip in recovery, you boot up into bootloader and let hboot find it. If when you get to your bootloader and it is fastboot, use your volume key and select on bootloader option. Then hboot will find it and ask you if you want to install it. Install it. After that, you will then need to reinstall either amon ra or the other but stay away from clockworkmod. But to reinstall the recovery, you will have to unlock again.
mikeyk101 said:
Did you download the one from the link? You don't flash that PH98IMG.zip in recovery, you boot up into bootloader and let hboot find it. If when you get to your bootloader and it is fastboot, use your volume key and select on bootloader option. Then hboot will find it and ask you if you want to install it. Install it. After that, you will then need to reinstall either amon ra or the other but stay away from clockworkmod. But to reinstall the recovery, you will have to unlock again.
Click to expand...
Click to collapse
I did install in hboot. I then installed Amon so I could flash the ROM and that's what's giving me all those errors.
If all you are after is stock and rooted, try looking at this one: http://forum.xda-developers.com/showthread.php?t=1642217
Since you ran the PH98IMG that I directed you to, you are now on ICS. So follow the directions in that thread for "S-On and ICS".
Installation for S-ON Devices on ICS firmware
•Copy ROM to SD Card AND PH98IMG.zip to ROOT of SD Card
•Reboot to recovery
•wipe data / Factory Reset
•Flash ROM
•Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
•Reboot
•Profit!
Edit: The only change I would recommend is to hold off putting that PH98IMG file from that thread on the sd card right away. You will have a hard time getting to recovery if you have that on the card. I would suggest following all the instructions up to and including "Flash ROM". Then I would "return" back to the main Amon Ra screen, make sure you have the data cable connecting your phone to the computer, select "USB-MS Toggle", then select the SD Card, and that will allow you to copy the PH98IMG file to the SD card. Then continue with the rest of the directions. If you do this right, you should be ok.
mikeyk101 said:
If all you are after is stock and rooted, try looking at this one: http://forum.xda-developers.com/showthread.php?t=1642217
Since you ran the PH98IMG that I directed you to, you are now on ICS. So follow the directions in that thread for "S-On and ICS".
Installation for S-ON Devices on ICS firmware
•Copy ROM to SD Card AND PH98IMG.zip to ROOT of SD Card
•Reboot to recovery
•wipe data / Factory Reset
•Flash ROM
•Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
•Reboot
•Profit!
Edit: The only change I would recommend is to hold off putting that PH98IMG file from that thread on the sd card right away. You will have a hard time getting to recovery if you have that on the card. I would suggest following all the instructions up to and including "Flash ROM". Then I would "return" back to the main Amon Ra screen, make sure you have the data cable connecting your phone to the computer, select "USB-MS Toggle", then select the Internal_sd, and that will allow you to copy the PH98IMG file to the SD card. Then continue with the rest of the directions. If you do this right, you should be ok.
Click to expand...
Click to collapse
It's the actual recover I believe to be giving me the errors, but I'll try what you said in about 2 days (I need to study for finals). It might be because I tried to S-Off and I installed all of that guys software and it might be making the phone act funny. I'll be much more descriptive about my errors when I post back in 2 days.
I fixed it!!
Ok, so I finally got it working, I'll try to detail my steps for anyone else who ran into similar issues:
I believe my recovery started acting funny after I failed to S-Off properly the first time. Amon Ra was all gimmicky and said stuff like "E: can't find cache" and reinstalling the recovery/wiping everything (and I mean everything: external SD, internal SD, cache, partioning SD card etc..) wasn't working. I tried re-installing Amon Ra through command prompt with the adb, I tried reinstalling my ROMS but my phone wasn't having it.
It got to the point all I could boot into was a white HTC screen, so I then tried out Twrp's 2.1 Touchscreen (I wasn't S-Off yet) recovery (I don't have enough posts to post a link yet ) which INITIALLY reported the same "E: can't find cache" errors as Amon Ra, BUT when I wiped my files in Twrp it seemed to actually fix them...I'm not sure exactly what I wiped or formatted that fixed the "E: can't find mount/cache" issues, so try everything.
So my ROM installed but I was still stuck on the white HTC logo. This is where I INSTALLED A NEW KERNEL THROUGH ADB. I wish I knew which kernel I installed, but I have like 10 and I just picked a random one. The point is if you're still stuck at a white HTC screen, install a new kernel.
So I got a recovery on the phone, and then I tried to S-Off again but I didn't have a good ROM installation so that was hanging at the HTC white screen. I then installed CleanROM DE 1.4 and I was able to boot into it, but ran into my initial problem of it crashing after dialing a number and entering infinite reboot. However, it would stay on just long enough for me to run ControlBear's program to S-Off.
So I S-Offed, I downloaded the Gingerbread RUU (the .exe version for Windows), I installed it, and now I can dial numbers and I'm all goodie again. Unfortunately, I honestly think the only way I was escaping my trouble was doing an S-Off, unless they leak a Ice Cream Sanwhich executable for Windows.
TL;DR Install Twerp 2.1 through adb, wipe everything, install CleanROM DE 1.4, install kernel S-Off, run Gingerbread RUU .exe
so i went to switch out my battery and when i turned the phone back on it vibrated and displayed the white htc screen, then went black for a second and then stays on the white htc screen forever! Im a total noob when it comes to all the technical stuff about RUU's Kernels Roms and whatnot. I can get to bootloader, but i tried to do factory reset and it showed a green circle with a loading bar but then it changed into a red triangle with an exclamation. I tried flashing amon ra recovery but it doesnt work, although TWRP works. While in TWRP though, whenever i try to flash a zip file, it fails and says something like E:failed to mount /cache E:failed to mount /system E:failed to mount /data. Please help me i need this phone working to help me at my job. If someone can walk me through what i need to do i would REALLLYYYY appreciate it. Like i said though, i am a noob so i need realy stupified instructions lol. Thanks
just wanted to note that right now when i go to bootloader it says
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Vigor PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
kverduin said:
just wanted to note that right now when i go to bootloader it says
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Vigor PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Click to expand...
Click to collapse
First you should go to shipped-roms.com and download the vigor ics ruu.exe, the rezound downloads there are under vigor . Plug your phone into your computer and from hboot highlight fastboot press power and run the .exe file from your computer and follow the on screen instructions, this will return your phone to full stock ics. Make sure you download the vigor ics ruu.exe as the GB ruu will not work with s-on.
You can also download this: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ it's the latest ruu it'll update your hboot, stock recovery, rom, and radios, to latest stock. Just download, rename the zip file to PH98IMG (don't include .zip it is a zip file it'll add it on its own in hboot) put it on your sd card, not in a folder just on. Put it back in your phone and boot to bootloader and runn the update, when it powers off. Run it again. (As it has to update the hboot to 2.27 first)Then you'll be on the stock latest. Then root and Rom from there. Of you need help pm me for my gtalk and I could walk you thru it..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Sounds like no boot.img
GrayTheWolf said:
Sounds like no boot.img
Click to expand...
Click to collapse
Its because of the security warning. The phone wont boot if it says that he has to run an RUU
Sent from my HTC Droid Incredible
Same exact problem. Installing zip now, god i hope this works!!
So my screen is the exact same, i tried to flash a kernal for not only wrong phone but wrong carrier too. Anyways no OS, when i try to flash either of the ways you have explained they both dont work. When i put it on the sd card as PH98IMG it looks like it loads it in the upper right then thats it. regular bootload screen after that nothing happens. try to load it by opening the application after im plugged in as fasboot usb and the program says Install script setup launcher has stopped working. I have been able to flash liquids rom and looks as if it is booting but waited 24 min and nothing happpend just stayed on boot screen. So im just trying to get back to RUU then work from there.
mrcorson said:
So my screen is the exact same, i tried to flash a kernal for not only wrong phone but wrong carrier too. Anyways no OS, when i try to flash either of the ways you have explained they both dont work. When i put it on the sd card as PH98IMG it looks like it loads it in the upper right then thats it. regular bootload screen after that nothing happens. try to load it by opening the application after im plugged in as fasboot usb and the program says Install script setup launcher has stopped working. I have been able to flash liquids rom and looks as if it is booting but waited 24 min and nothing happpend just stayed on boot screen. So im just trying to get back to RUU then work from there.
Click to expand...
Click to collapse
You need to extract the boot.IMG from liquid Rom and rename it ph98img and put that on your sd card or in the folder with adb and fastboot flash it using fastboot flash boot boot.img
Sent from my ADR6425LVW using xda app-developers app
Also wipe cache and dalvik cache in recovery immediately after doing this
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
I ended up flashing liquidsmooth rom in recovery then had to wipe factory data reset, then i could wipe dalvick cache then when i rebooted it actually booted the rom and I LOVE IT. Still having some issues tho.
Still cant get my computer to talk to my phone when in fastboot usb i cant get any devices when i do "adb devices" cmd.
It says devices listed below but no devices.
Also im still stuck on TWRP 2.2 and I cant my 2.6 to flash in recovery. - Still troubleshooting this and might get it in a bit.
Thanks for the suggestions!!!
mrcorson said:
I ended up flashing liquidsmooth rom in recovery then had to wipe factory data reset, then i could wipe dalvick cache then when i rebooted it actually booted the rom and I LOVE IT. Still having some issues tho.
Still cant get my computer to talk to my phone when in fastboot usb i cant get any devices when i do "adb devices" cmd.
It says devices listed below but no devices.
Also im still stuck on TWRP 2.2 and I cant my 2.6 to flash in recovery. - Still troubleshooting this and might get it in a bit.
Thanks for the suggestions!!!
Click to expand...
Click to collapse
ooooh older stuff ick lol...do you have your htc sync drivers installed....what os are you on? are you s-on? what hboot you on? you need to be wiping before rom install and not after....are your issues pertaining to random reboots?
REV3NT3CH said:
ooooh older stuff ick lol...do you have your htc sync drivers installed....what os are you on? are you s-on? what hboot you on? you need to be wiping before rom install and not after....are your issues pertaining to random reboots?
Click to expand...
Click to collapse
Yes i did reinstall my HTC Sync drivers, I have been wipining factory reset, cache, system, dalvick cache before i flash a new rom. I am S-On. Havent really determined a reason to go s-off yet, i am messing up my phone good enough with this let alone a paperclip. no problem with random reboots. I finally decided to go to a custom rom bc i was sick of my phone rebooting for OTA updates then being late for work. So the 3 roms i have now tried are Liquid smooth which i liked but i couldnt get mms messages to show up on phone. Also it wouldnt change from silent to a beep for text message notifications. i could select it but it would stay as silent. So.... I flashed ViperRezROm which i just didnt like the look and theme. So i finally flashed Cyanogen ROM and come to find out its the same kernal as Liquid smooth so it looks the same and I like that but I still cant change the notification from silent to a beep for text messages. So i never know when i get a text.
Still working on trying to flash a newer version of TWRP.
Then this time flashing I tried to titanium backup and went to load my backup and it cant find it.... WTF
UGH... Learning so much with this stuff. just taking alot of patience.
Thanks again for yalls support, I love this forum.
Mike
BTW just to note...if your bootloader is locked fastboot flash methods will not work 90 percent of the time...if you flashed liquid 3.0 that's more than likely your problem with mms as that is a beta...but on more recent 4.3 builds mms is fixed...and no its not the same kernel...just similar source code...liquid 2.9 does not have this mms issue...any random reboots on 4.2 are caused by min frequency not set right at 384 mhz and using amon ra to flash or not doing a proper clean flash....I do recommend s-off as it will make life much easier for you for modding things or flashing custom zips and for future flashing back to full stock if needed as its not possible while s-on...you can always pm me for help as I've yet to run into an error I can't fix unless posted in op caused by source
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
There is a few good reasons to S-Off.
1.No need to fastboot flash kernels
2.can RUU if needed
3.can flash recovery updates (cwm, twrp) as ph98img zips
4. Can keep bootloader ***locked***
5. No more ***tampered*** tag after you RUU
Scenario: you are out and about (or a computer isn't handy) somehow you are in an infinite bootloop. You nandroid restore. But it is something on boot partition. Only way to fix this while S-On is fastboot flashing a boot.img, but if you were S-Off, you would have restored the boot image from the nandroid.
Edit: added 5th reason
Sent from my ADR6425LVW using xda app-developers app
Uzephi said:
There is a few good reasons to S-Off.
1.No need to fastboot flash kernels
2.can RUU if needed
3.can flash recovery updates (cwm, twrp) as ph98img zips
4. Can keep bootloader ***locked***
5. No more ***tampered*** tag after you RUU
Click to expand...
Click to collapse
I finally went S-OFF to help another user get step by step to restore to fully locked and stock ruu. I decided to leave it S-OFF. It's so nice to be able to just load a rom and not have to do anything else (other than wiping). It makes changing/upgrading rom's a breeze.
I highly recommend it. It seems scary, but once you have done it once, you will not go back.
But be warned, never go back to S-ON on a non-HTC hboot... you will hard brick your device. That is the only real threat I've heard about... if you never go back to S-ON, then you have absolutely nothing to worry about. Just about any error can be fixed except for going s-on on a non-ruu hboot.
Thanks
molson8045 said:
You need to extract the boot.IMG from liquid Rom and rename it ph98img and put that on your sd card or in the folder with adb and fastboot flash it using fastboot flash boot boot.img
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You saved me! That worked like a charm.
please help
Hi guys
Im have that problem in my htc rezound i seen the above comments but i couldnt able to understand so please tell the procedure one by one please pleasr..........
parthis said:
Hi guys
Im have that problem in my htc rezound i seen the above comments but i couldnt able to understand so please tell the procedure one by one please pleasr..........
Click to expand...
Click to collapse
If English is not your first language I apologise.
Otherwise, you need to be more specific and use full sentences.
GrayBoltWolf said:
Sounds like no boot.img
Click to expand...
Click to collapse
you were dead on accurate regarding my problem. Your post helped me revive an all but dead rezound!! Thanks man!!
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.
Hi everyone, I've seen you guys help out so many other people I figured I'd give it a try.
My HTC Rezound is not working. I can't charge the device while off. I can't start the phone (Flashes the HTC logo, screen goes dark for one second, then stays at the HTC logo. Luckily, I have an old Thunderbolt, I have been able to charge my battery through that, and access the bootloader using the power + vol down method.
I have never rooted my Rezound and have been using stock since I got it, here is what I see in my bootloader:
***LOCKED***
VIGOR PVT SHIP S-ON 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
Under that I see the regular Bootloader menu. I cannot use recovery, factory reset or clear storage, because it fails and I get the E: Can't mount /data/data/recovery/log error message. I tried downloading a PH98IMG.zip file, but when it tries to load it I get an error saying that the version on the phone is newer than the one on the SD card, and it won't update (Don't know if that's an issue with downloading things from before Sep 20 2012, but I havn't found anything post that). I can't use the RUU updater because my computer will not mount/ recognize my phone, I downloaded all the HTC sync stuff, and my computer beeps and says that there is something there, but it fails somewhere in the process and nothing sees it. I also tried to push it with ADB, but I get the same issues, CMD will ask me to attach the device and I can't get past it.
So that's where I am, I can get to my bootloader, but I can't do anything via the RUU exe, ph98IMG.zip file on an SD card, or ADB/Fastboot. I'm stuck.
I am willing to try anything, and will give any other information you guys need if you think you can help. Meanwhile I'm using my old cracked Thunderbolt that lost it's 4G capability, I feel dirty.
Please let me know if you can help! And thanks in advance!
If past your warranty or if you have no insurance on it. Go to the htcdev website and unlock the phone.
Sent from my ADR6425LVW using Tapatalk 2
reallyneedshelp said:
Hi everyone, I've seen you guys help out so many other people I figured I'd give it a try.
My HTC Rezound is not working. I can't charge the device while off. I can't start the phone (Flashes the HTC logo, screen goes dark for one second, then stays at the HTC logo. Luckily, I have an old Thunderbolt, I have been able to charge my battery through that, and access the bootloader using the power + vol down method.
I have never rooted my Rezound and have been using stock since I got it, here is what I see in my bootloader:
***LOCKED***
VIGOR PVT SHIP S-ON 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
Under that I see the regular Bootloader menu. I cannot use recovery, factory reset or clear storage, because it fails and I get the E: Can't mount /data/data/recovery/log error message. I tried downloading a PH98IMG.zip file, but when it tries to load it I get an error saying that the version on the phone is newer than the one on the SD card, and it won't update (Don't know if that's an issue with downloading things from before Sep 20 2012, but I havn't found anything post that). I can't use the RUU updater because my computer will not mount/ recognize my phone, I downloaded all the HTC sync stuff, and my computer beeps and says that there is something there, but it fails somewhere in the process and nothing sees it. I also tried to push it with ADB, but I get the same issues, CMD will ask me to attach the device and I can't get past it.
So that's where I am, I can get to my bootloader, but I can't do anything via the RUU exe, ph98IMG.zip file on an SD card, or ADB/Fastboot. I'm stuck.
I am willing to try anything, and will give any other information you guys need if you think you can help. Meanwhile I'm using my old cracked Thunderbolt that lost it's 4G capability, I feel dirty.
Please let me know if you can help! And thanks in advance!
Click to expand...
Click to collapse
The fact you've kept it stock and it won't let you get past hboot or the HTC screen and you can't do anything via hboot tells me it's dead.
You have the latest hboot, there is no RUU/firmware zip available to let you re-install everything clean.
You're probably gonna have to get it replaced.
Flyhalf205 said:
If past your warranty or if you have no insurance on it. Go to the htcdev website and unlock the phone.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I was able to unlock it using the method on the htcdev website.... what can I do with it now? Bootloader looks the same, but says **UNLOCKED** at the top of the screen.
reallyneedshelp said:
I was able to unlock it using the method on the htcdev website.... what can I do with it now? Bootloader looks the same, but says **UNLOCKED** at the top of the screen.
Click to expand...
Click to collapse
Download TWRP at http://forum.xda-developers.com/attachment.php?attachmentid=2102623&d=1373341752
Extract the .zip and place the .img file in the same folder as fastboot. Use fastboot to flash it. The command is going to be fastboot flash recovery recovery.img
Once you done that. use command fastboot boot recovery.img
Go to backup and create a backup
After that finishes backing up. Download http://vp-zp.com/snuzzo/kernels/rezound/sense/Funky-Kernel-v3.7.3.zip and place it on your sdcard. You can mount your usb drive inside TWRP recovery.
After you have copied it over. Install that zip from the sdcard and it should go through the steps of being s-on since you are s-on. Then reboot phone
Flyhalf205 said:
Download TWRP at http://forum.xda-developers.com/attachment.php?attachmentid=2102623&d=1373341752
Extract the .zip and place the .img file in the same folder as fastboot. Use fastboot to flash it. The command is going to be fastboot flash recovery recovery.img
Once you done that. use command fastboot boot recovery.img
Go to backup and create a backup
After that finishes backing up. Download http://vp-zp.com/snuzzo/kernels/rezound/sense/Funky-Kernel-v3.7.3.zip and place it on your sdcard. You can mount your usb drive inside TWRP recovery.
After you have copied it over. Install that zip from the sdcard and it should go through the steps of being s-on since you are s-on. Then reboot phone
Click to expand...
Click to collapse
When I ran fastboot boot recovery.img the phone when dark for a second, went back to the fastboot menu, but now at the top of the screen above ***UNLOCKED*** there is a *** TAMPERED*** but no recovery menu. Is this ok?
EDIT: I went into recovery and see the new menu. will update once finished.
reallyneedshelp said:
When I ran fastboot boot recovery.img the phone when dark for a second, went back to the fastboot menu, but now at the top of the screen above ***UNLOCKED*** there is a *** TAMPERED*** but no recovery menu. Is this ok?
Click to expand...
Click to collapse
That is fine saying TAMPERED. Just means you have something custom flashed. Hit the power button and go into HBOOT. Then select recovery in the list.
EDIT: Just saw you edited after I posted
Flyhalf205 said:
That is fine saying TAMPERED. Just means you have something custom flashed. Hit the power button and go into HBOOT. Then select recovery in the list.
EDIT: Just saw you edited after I posted
Click to expand...
Click to collapse
Ha! OK, now I'm done, but there was another problem. The installation failed. Here is what it said:
Funky Kernel
for
HTC Rezound
Funky-Kernel-v3.7.3
Linux upstream version : 3.0.87
Mounting /system
installing modules
file_getprop: failed to stat " /system/build.prop
E: Error executing updater binary in zip ' ?sdcard
Error flashing zip ' /sdcard/funky-kernel-v3.7.3
Updating partition details...
"E: Unable to mount" /cache
""/data
""/system
""/emmc
"" unable to mount internal storage
Am I done for?
You might be...
Flyhalf205 said:
You might be...
Click to expand...
Click to collapse
Well, I sincerely appreciate the effort. It seems like the internal storage somehow got damaged, can't imagine how that happened. At least I have a thunderbolt to keep me until I find a new phone. It could be worse.
Thanks for the help!
reallyneedshelp said:
Well, I sincerely appreciate the effort. It seems like the internal storage somehow got damaged, can't imagine how that happened. At least I have a thunderbolt to keep me until I find a new phone. It could be worse.
Thanks for the help!
Click to expand...
Click to collapse
Just out of curiosity. Did you try doing a Factory Reset in that white HBOOT screen before we started this process?
Flyhalf205 said:
Just out of curiosity. Did you try doing a Factory Reset in that white HBOOT screen before we started this process?
Click to expand...
Click to collapse
Yeah, same as anything else, can't mount E.
In TWRP try to mount internal storage when plugged into a PC. See if formatting would work.
Sent from my Infected Rezound using xda app-developers app
Uzephi said:
In TWRP try to mount internal storage when plugged into a PC. See if formatting would work.
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
Won't let me. Internal storage showing up as 0MB. :/
reallyneedshelp said:
Won't let me. Internal storage showing up as 0MB. :/
Click to expand...
Click to collapse
It doesn't sound like your internal storage is completely toast. You are able to boot into the hboot partition and the recovery partition, the others may be corrupt and reflashing the recent RUU may help. Try to s-off to be able to RUU recent and older RUU zips (stock IMGs)
Sent from my Infected Rezound using xda app-developers app
Uzephi said:
It doesn't sound like your internal storage is completely toast. You are able to boot into the hboot partition and the recovery partition, the others may be corrupt and reflashing the recent RUU may help. Try to s-off to be able to RUU recent and older RUU zips (stock IMGs)
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
There's no recent RUU to flash, that's part of the problem, none came out for the OTA update and you also need a running rom installed to s-off.
OP - What happens if you try to format the partitions via TWRP?
mjones73 said:
There's no recent RUU to flash, that's part of the problem, none came out for the OTA update and you also need a running rom installed to s-off.
OP - What happens if you try to format the partitions via TWRP?
Click to expand...
Click to collapse
Won't mount anything to format, just will say can't read. I can however go through the file tree. Somehow the internal memory got semi-fried. I don't know what happened.
im having a very similar problem except none of my computers will recognize my phone so i cant re-unlock my bootloader any suggestions
Hello all,
So I am having an interesting issue with my Rezound which has served me well for the past two years. Last night while I was browsing the internet I got the warning that my battery was going to go dead. Ignored it and kept browsing, eventually causing the phone to auto shutdown, fine, I have a spare battery (love removable batteries), threw that in and it started to boot but gets stuck at the white "HTC" loading screen. I am able to get into HBOOT and get the following.
*** LOCKED ***
VIGOR PVT SHIP S_ON 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
When I try to do a factory reset it will act like it is going to start, showing a phone with a green circle and an arrow, and a loading bar. Then before the loading bar begins to get filled in at all (it is just gray with diagonal lines) the green circle changes to a red triangle and an exclamation point.
If I try to boot into recovery I get the same phone with a red triangle image.
This phone is 100% stock unrooted and untouched in any way save for disabling the stock bloatware (I didnt even root it to uninstall that!). AFAIK there was no OTA update done to it yesterday, and I have been using it every day up until now with no real issues.
Simply just the battery died, and now it wont boot. Any ideas?
I am having the same issue on my wife's Rezound. It died last night and went into the same bootloop. Tried a factory reset to no avail. Phone is stock with the same info as previous poster in HBOOT.
I'm familiar with some android development, but know nothing about HTC phones. If somebody could point me in the right direction it would be greatly appreciated.
So I have tried running the stock RUU, no dice, I was already at the latest version.
I then unlocked my bootloader through HTC dev and tried to flash AmonRA so I can do custom ROMs.
Now when I go into my bootloader and select "Recovery" the white HTC screen pops up with a brown progress bar in the top right which fills up quickly, then the phone turns off and that is it until I remove the battery (wont respond to power again after it turns itself off).
So it would appear flashing AmonRA did not work either. Next I will be trying CWM.
Thanks for the update. Keep us posted if anything works. I just don't have the time to learn and try everything right now.
So I got CWM Recovery flashed successfully, but when I boot into recovery and try to wipe I get format failed and mounting errors.
Could my eMMC have been corrupt? How can I fix it?
EDIT: I also get cant mount and cant open on /cache, /system, /sdcard from inside the CWM recovery
Have you attempted to s-off and ruu down to an official exe?
Sent from my DNA using my mind.
I have not done s-off yet, would that fix my mount issues? I am now running TWRP recovery, that also is unable to mount anything. I appear to be having issues with the /dev/block/mmcblk0p35 and /dev/block/mmcblk0p36 and /dev/block/mmcblk0p29 etc areas. At this point any help would be greatly appreciated.
I have put a good 12 hours into trying to get this thing to boot. I feel like I am close and if I could just get it to somehow re-format the whole /block directory then flash a new rom it would would. Pushing an RUU from fastboot did not work, nor did running it from TWRP. TWRP gave me issues in the aforementioned mmcblk areas, and fastboot just says failed, I would guess for the same reason though.
Yes, if all else fails. RUU exe is the last resort
Sent from my DNA using my mind.
I found another phone for the wife to use for now. I'll try to s-off and ruu when i have some time.
Uzephi said:
Yes, if all else fails. RUU exe is the last resort
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Where can I find the instructions and files to get S-Off without access to a ROM and running windows? The JPBear instructions state Linux only and says I need to have a stock ROM.
OK, so from my research I will need to use Linux. Do I need the HTC USB drivers or anything or can I just take a fresh install of Ubuntu and run JPBear? Also, since I have unlocked my bootloader and (tried) to flash a rooted stock rom, do I now need to re-lock and try to run the RUU again? I did try that tonight (re-locking then running the stock RUU) but it still gave me the error that HBOOT was older on the version I was trying to flash.
You won't be able to run any RUU with being s on as their isn't one available for the latest OTA. Try wiping and formatting cache data and system with the latest CWM (Touch). Then follow flash instructions of a ROM for s on.
Sent from my Rezound using Tapatalk 4
I have personally used the windows version of jpbear on a custom ROM to s-off my Rezound. It is somewhere in this forum. I was in a similar pickle and needed s-off to ruu. Albeit, my phone didn't have mount issues, so I don't know if ruu will fix your specific issue, but if anything will, ruu will fix it.
Sent from my Rezound using xda app-developers app
Uzephi said:
I have personally used the windows version of jpbear on a custom ROM to s-off my Rezound. It is somewhere in this forum. I was in a similar pickle and needed s-off to ruu. Albeit, my phone didn't have mount issues, so I don't know if ruu will fix your specific issue, but if anything will, ruu will fix it.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
I believe an RUU would fix it if I can manage to get S-Off. I found an old version of ControlBear 0.2.2 for windows, when I run it it tells me to connect my phone and install drivers if I run from recovery. If I run from fastboot USB it trys to reboot my device into the ROM. So I dont know if JPBear will even work for me if I don't have access to my ROM.
Jensen567 said:
I believe an RUU would fix it if I can manage to get S-Off. I found an old version of ControlBear 0.2.2 for windows, when I run it it tells me to connect my phone and install drivers if I run from recovery. If I run from fastboot USB it trys to reboot my device into the ROM. So I dont know if JPBear will even work for me if I don't have access to my ROM.
Click to expand...
Click to collapse
i have a guide for obtaining s-off in linux....very well explained and thorough....
REV3NT3CH said:
i have a guide for obtaining s-off in linux....very well explained and thorough....
Click to expand...
Click to collapse
First off let me say a big THANK YOU for taking the time to respond and help me out. I did some searching, this is the guide you are referring to?
http://forum.xda-developers.com/showthread.php?t=2502814&highlight=s-off
I have no qualms with using linux and have some experience with ubuntu I just do not have an install up and running now so I wanted to avoid that if possible, but no big deal. In this thread
http://forum.xda-developers.com/showthread.php?t=1612035&page=202
you suggest I use fastboot usb to reinstall everything, is there a guide for this also? I am able to get to the white HBOOT screen to do fastboot USB, and I am also able to get into TWRP recovery. Version 2.6.3.3. However if I try to wipe anything from inside recovery I get "Unable to mount '/emmc'" or '/cache' '/data' or '/system'.
Sorry for my noobness with flashing, last time I did any of this was when I unlocked/s-off my DINC which was very easy at the time.
EDIT: I notice also in that guide you suggest to start from inside the ROM, I am unable to do this. Will it work from HBOOT, fastboot usb, or recovery?
Jensen567 said:
First off let me say a big THANK YOU for taking the time to respond and help me out. I did some searching, this is the guide you are referring to?
http://forum.xda-developers.com/showthread.php?t=2502814&highlight=s-off
I have no qualms with using linux and have some experience with ubuntu I just do not have an install up and running now so I wanted to avoid that if possible, but no big deal. In this thread
http://forum.xda-developers.com/showthread.php?t=1612035&page=202
you suggest I use fastboot usb to reinstall everything, is there a guide for this also? I am able to get to the white HBOOT screen to do fastboot USB, and I am also able to get into TWRP recovery. Version 2.6.3.3. However if I try to wipe anything from inside recovery I get "Unable to mount '/emmc'" or '/cache' '/data' or '/system'.
Sorry for my noobness with flashing, last time I did any of this was when I unlocked/s-off my DINC which was very easy at the time.
EDIT: I notice also in that guide you suggest to start from inside the ROM, I am unable to do this. Will it work from HBOOT, fastboot usb, or recovery?
Click to expand...
Click to collapse
1.) yes that is the guide im referring to...2.) AHA 2.6.3.3 HAS MOUNT ISSUES AND IS POSTED....go to an earlier version like 2.6.3.0...2.6.3.3 is only meant for FLASHING KITKAT ONLY and nothing else.....also why did you even trey to wipe internal sd anyway its not required...if you want the rezounds proper wipe method i can tell you...keep in mind the dinc is a whole different phone using a whole different motherboard....hence the differences....3.) once you have the proper version ill tell you how to get rid of mount issues
REV3NT3CH said:
1.) yes that is the guide im referring to...2.) AHA 2.6.3.3 HAS MOUNT ISSUES AND IS POSTED....go to an earlier version like 2.6.3.0...2.6.3.3 is only meant for FLASHING KITKAT ONLY and nothing else.....also why did you even trey to wipe internal sd anyway its not required...if you want the rezounds proper wipe method i can tell you...keep in mind the dinc is a whole different phone using a whole different motherboard....hence the differences....3.) once you have the proper version ill tell you how to get rid of mount issues
Click to expand...
Click to collapse
OK, I installed 2.6.3.0 and that is running. Still have mount issues but I am guessing that is normal at this point? I didn't try to wipe the internal SD per say, I was trying to wipe the cache and system to do a reinstall after the battery died and I was stuck at the white HTC boot screen.
Basically I am a noob and was just trying anything/everything to get it booting again. I found my old DINC now and am running that for now so I have some more time to work on it. On a side note, CM7.2 GB is still awesome.
Jensen567 said:
OK, I installed 2.6.3.0 and that is running. Still have mount issues but I am guessing that is normal at this point? I didn't try to wipe the internal SD per say, I was trying to wipe the cache and system to do a reinstall after the battery died and I was stuck at the white HTC boot screen.
Basically I am a noob and was just trying anything/everything to get it booting again. I found my old DINC now and am running that for now so I have some more time to work on it. On a side note, CM7.2 GB is still awesome.
Click to expand...
Click to collapse
so wait you are staying on ice cream sandwhich or lower? ok steps on 2.6.3.0 to get internal back is first go to wipe>advinced wipe and tick internal sd only...then swipe to wipe...youll get an error and thats ok....do the same method again except this time you'll notice it says emmc instead of internal sd....now go to mount option from main screen..then make sure only internal sd is checked and right below all options make sure it says Storage: Internal SDcard (size in mb) if it still says micro sd just tap on that area to change it....tap mount usb and plug into pc...reformat in windows using administrative tools in control panel or if it shows in my computer do it that way.....if you are staying on ICS or lower STAY WITH AMON RA ONLY...twrp and cwm is meant for jb and higher on the rezound....if the above method doesnt work...install amon ra and moun usb that way....you will have to fastboot install the recoveries obviously
REV3NT3CH said:
so wait you are staying on ice cream sandwhich or lower? ok steps on 2.6.3.0 to get internal back is first go to wipe>advinced wipe and tick internal sd only...then swipe to wipe...youll get an error and thats ok....do the same method again except this time you'll notice it says emmc instead of internal sd....now go to mount option from main screen..then make sure only internal sd is checked and right below all options make sure it says Storage: Internal SDcard (size in mb) if it still says micro sd just tap on that area to change it....tap mount usb and plug into pc...reformat in windows using administrative tools in control panel or if it shows in my computer do it that way.....if you are staying on ICS or lower STAY WITH AMON RA ONLY...twrp and cwm is meant for jb and higher on the rezound....if the above method doesnt work...install amon ra and moun usb that way....you will have to fastboot install the recoveries obviously
Click to expand...
Click to collapse
I have not decided what ROM I want to run, for now just getting it booting on the rooted OEM rom is fine.
I tried that method and it did not work. It does say unable to mount /emmc, but it also comes up with unable to mount just about everything else. Nothing shows as mounted under mount from the main menu (I have my SD card removed for now) and when I tap Internal SDcard to mount it I get unable to mount /emmc in the console.
I tried AmonRA first, flashing through fastboot usb, and it did not work for me. When I would select recovery from HBOOT the phone would go to the white HTC screen then the screen shuts off but recovery never comes up. The phone just got hot and would not respond to power button so I pulled the battery.