Been humming along fine with cyanogen9, reboot today stuck boot looping - HTC Rezound

I reflashed my phone last week and had 0 issues. I'm using the rom from graythewolf in this thread: http://forum.xda-developers.com/showthread.php?t=1885553
Today I noticed I had bars but it didn't say anything about what type of service (3g, LTE, etc). I've had this problem before and typically putting into airplane mode and turnign it off fixes the issue. Its a minor annoyance but one I could live with. Since flashing that above rom I haven't had to do this. Awesome right?
Today the issue came back and I turned on airplane mode and turned it off, nothing happened. I tried a few more times and still would only gets bars but no data service. I rebooted the phone and that is the last time it came up. Its boot looping at the HTC white screen. I tried going into recovery and it goes right back to the HTC screen and constant reboots. I tried reflashing the recovery (AMonRa) and it flashes fine according to the response in fastboot but when I try to get into it it shows the 1st two lines of amonra and then goes RIGHT back to the HTC rebooting screen.
I have been trying to find a RUU that I can use to reflash the entire phone from the computer (tried fastboot flashzip ph86img.zip and it failed after trying). Any ideas guys. I kinda live and die by my phone but this is my 3rd rezound and this is extremely frustrating.
Yes I am S-OFF and unlocked.
Pointing me to any ICS RUU that runs off a windows machine would help immensely as I think that might get me out of what ever reboot hell I'm in.
Thanks in advance.

1st thing, take the battery out for at least 5 minutes to let everything discharge.
Pop it back in and do the power + volume down to try to get to hboot and then to recovery. Once there do a full wipe and reflash.
CM9 is going to have issues, so just stick around. If you need a stable ROM you should be on CleanROM or Neomax.

GrayTheWolf said:
1st thing, take the battery out for at least 5 minutes to let everything discharge.
Pop it back in and do the power + volume down to try to get to hboot and then to recovery. Once there do a full wipe and reflash.
CM9 is going to have issues, so just stick around. If you need a stable ROM you should be on CleanROM or Neomax.
Click to expand...
Click to collapse
Definitely agree. CM9 is being improved greatly but its not at the state where you dont have to worry about things like toggling airplane mode to fix data or stuff like that and bugs or glitches.
Especially if your like me and expect you phone to last long and always be ready to work, definitely try another rom for now. Theres literally a ton of roms that are all awesome

I had this same problem somewhere along the line. All I had to do was the "fastboot boot (name of your recovery).img" through adb. Did a clean wipe and install and everything cleared up.
Sent from my RAGE'in Rezound

I had a boot loop issue last night too. It was strange, just looking around on Facebook, suddenly it reboots and halfway through the cm9 animation, back to HTC white screen. I could get into hboot and even recovery, but restarted as soon as I tried to wipe or nandroid restore. Had to rerun ruu and re flash cm9 and all that. No idea what happened
Sent from my ADR6425LVW using xda app-developers app

Related

Rooted phone gone bad! Can I just wipe to factory?

Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.

[Q] Bricked/QHUSB-DLOAD mode with S-ON

I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:

[Q] looking for some advice or help... boot loop?? or broken phone...

Have been rooting Androids for a while and have been about to solve all my problems by doing research and finding the solution... first time i actaully am stumped...
I have a HTC EVO 4G LTE, second one i had the first the microphone went bad, i rooted it just like the last one and it was running fine. I deleted a few system apps such as sprint music, friend stream, tunein radio, and an HTC app. forget what that was. but now my, at work today, keep restarting randomly and died very quickly. when i finally got a chance to charge it, it hung on a boot loop and then entered the system about 45 minutes later. and then quickly reset back into the boot loop, i have at least 25% battery at this point. it continues to cycle through this for the next 4 hours. i tried to just shut the system off but after like 10 minutes it would start the boot loop again and since i work at radioshack trying to fix it there really wasn't an option. I did try to boot into twrp and do a factory reset how ever when i attempted to boot in it just froze at the HTC screen and then reset into the boot loop.
Once i got home i relocked the bootloader and did a hardreset... to no prevail... it continued to reset i even took my memory card and then that seemed to solve it... i put the back cover on without the memory card and it almost instantly reset and continued through the boot loop until i removed the back cover again. i don't know to much about the making of this back cover but it does seem to have three sensers to know it if it on or off, i am assuming... i tried installing stock recovery and taken off root. the only thing i haven't does is a completely stock OS reset through an ruu... and if i do that i am taking the phone back to sprint and getting another new one... does anyone have any ideas? and if this same thing is posted somewhere i am sorry, i have searched and tried everything i found and so far aside from the stock reset nothing has really worked. i factory reset from system, fastboot, and twrp (it loaded only once). I did relock the oem and did uninstall root. removed micro sd and formated internal memory. any other suggestions
i would just run RUU.. if it still giving u problems take it to sprint.. if u runn a RUU and it goes away just root it again start fresh.,. thats what i would do
Thanks EVO. I did end up running ruu and when it completed it started the boot loop again. Almost all night and ended up heating the phone up to the point I just booted into bootloader so it would stop. It continued this morning. But here's the part I wanna know... I pulled the back cover off for sh*ts and giggles and it booted right up. I am actually posting from it. I am afraid to put the back cover on...
Soo... I confirmed it was the back. I used the phone to post that. Made several calls to sprint and talked to ny mother... Phone was fine. Replaced back, phone froze and went into boot loop until the back cover was removed.... Why though?...
soo... it looks like i wont be needing any help with this phone... as it has completely died..... won't even try to power on. well sprint see you tomorrow at noon!

Stuck in boot cycle, won't get past Beats animation

Hello all....so I've got an issue with a friend of mine's HTC Rezound.
The thing, all of a sudden one day, wouldn't boot back into the OS. I either hangs at the HTC screen or it gets to the beats boot animation and hangs right there. No further. This was a stock phone. So far, I've been able to unlock the phone via HTCdevs.com, and install Amon Ra's recovery. Prior to this, hboot and fastboot were all I had. Recovery from stock wouldn't boot at all, and factory reset didn't do anything either. Custom recovery let me get in, to where I could flash an RUU or 2, and still, no luck. I've wiped the whole phone, and even reformatted all partitions, then installed 2 different RUU's on it, wiping both times before proceeding. I own a Gnex myself, so I'm no newb to flashing and things.
No matter what, the phone never will boot past the beats logo. Sometimes it only makes it to the start of the "b" curling up, sometimes it makes it to the circular "b" logo, sometimes just will sit at HTC before rebooting. Phone hasn't been wet, and was working fine, prior to this. Battery has been completely discharged as well. Tried booting without the back cover on, as if this were a network bootloop, but still same issue persists. Anybody got any ideas I can try? Considering I've tried different RUU's, and still can't get this thing to rock, wondering what could be causing it. Let me know, down below!
Bump

Starting to really hate EVOs, 2 Phones Bricked today

This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
oceanisbleu said:
This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
Click to expand...
Click to collapse
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
goliath714 said:
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
Click to expand...
Click to collapse
Yes of course I tried, the phone has been absolutely unresponsive. No amount of button holding is going to fix QHSUSB_DLOAD
Correct me if I'm wrong but http://forum.xda-developers.com/showthread.php?t=1948485 is the only known solution for QHSUSB_DLOAD due to firmware issue (I'm pretty sure this is what happened) or Jtag.
Here's the kicker, the files in that thread are no longer there so as it stands phone's just a Brick.
So for now I'm giving up on it and going samsung.
When I have the energy I may try working on the second one I have which turns out wasn't bricked instead the power button is unusable 90% of the time, but for now that's going to be left out of commission. Ultimately I need a backup because sprint techs seem to only operate on a 3 day basis when it comes to physical repairs therefore I plan to revive the second phone just to keep it as plan-b.
May all be user error but frankly what takes me minutes with a samsung seems to take days on the past couple of HTC phones I've had, so the ranting aspect of my post is merely in these regards and that only and out of frustration, this sucks because I'd take HTC build quality over samsung any day. I've been an HTC faithful since their first windows phone (5 years ago or so).
I know I have to fix the power button on the second phone but have any idea why it fails halfway through a factory RUU?
that's where I left off with it, it's S-On Unlocked running TWRP 2.8.0.1 I was trying to return it to full stock so I can have a go with facepalm S-Off procedure.
Did you relock the bootloader prior to attempting to run the RUU?
Magnum_Enforcer said:
Did you relock the bootloader prior to attempting to run the RUU?
Click to expand...
Click to collapse
out of 3 different RUUs I donwloaded only one worked, bootloader was relocked, ran RUU, Error 132 "Signature Error"
the one that did work the installer said finished, phone reboots but goes right back to bootloader where it says "Relocked" & "Security Warning" won't do anything else.

Categories

Resources