Anybody has an idea how to fix an HTC rezound phone that is stock never rooted, went thru the ICS OTA update, after restart is just restarting over and over again. Only shows HTC white display and keeps restarting.
I can go into Hboot, tried factory reset, even downloaded ruu ran it but it keeps bootlooping!!!..
Any ideas?
mpmorph said:
Anybody has an idea how to fix an HTC rezound phone that is stock never rooted, went thru the ICS OTA update, after restart is just restarting over and over again. Only shows HTC white display and keeps restarting.
I can go into Hboot, tried factory reset, even downloaded ruu ran it but it keeps bootlooping!!!..
Any ideas?
Click to expand...
Click to collapse
Perhaps it is the network bootloop issue, had that issue with the first OTA, try diagnosing that:
http://forum.xda-developers.com/showthread.php?t=1394659
mpmorph said:
Anybody has an idea how to fix an HTC rezound phone that is stock never rooted, went thru the ICS OTA update, after restart is just restarting over and over again. Only shows HTC white display and keeps restarting.
I can go into Hboot, tried factory reset, even downloaded ruu ran it but it keeps bootlooping!!!..
Any ideas?
Click to expand...
Click to collapse
mpmorph, let us know if your problem was same as the network boot looping issue, so we can assist others that get it with this OTA.:good:
....Sadly that is not the case. I tried to follow the instructions on that link but never managed to enter the code. The phone never got that far. The device just displays the white screen with the HTC green logo and then it dims the light a bit, and......it shutdowns, just to restart again. Removed everything, SIM card, microSD card, and nothing.
Received a replacement from verizon today, but before i send the other one back if anybody has any ideas to try.....now is the time....please?
Draw all over it to make VZW mad.
On a serious note, it would be nice if the internal sd was a real micro sd that you could remove and stick in a computer to get all of your files back.
mpmorph said:
....Sadly that is not the case. I tried to follow the instructions on that link but never managed to enter the code. The phone never got that far. The device just displays the white screen with the HTC green logo and then it dims the light a bit, and......it shutdowns, just to restart again. Removed everything, SIM card, microSD card, and nothing.
Received a replacement from verizon today, but before i send the other one back if anybody has any ideas to try.....now is the time....please?
Click to expand...
Click to collapse
Run the OTA RUU on it
I had the same issue with my OTA update. But Verizon won't warranty my 5 month old phone because it was not purchased on my line. Grr... Anyone that has any suggestion of how to fix it, please let me know/.
AshtonTS said:
Run the OTA RUU on it
Click to expand...
Click to collapse
Tried it. RUU ran then on restart same thing. No go.
I think S-OFF and running a GB RUU might work, don't wanna risk getting 500 dollar spike on my Verizon bill Cuz it was hacked.
Thanks for trying guys.
I had a similar problem, if you are able, wipe everything and reinstall the update. It worked for me.
Is the stock recovery installed?
Bootloader is locked/relocked ?
Did you remove the PH98IMG.zip file from your SD card?
Did you try booting with the back cover removed?
mpmorph said:
Tried it. RUU ran then on restart same thing. No go.
I think S-OFF and running a GB RUU might work, don't wanna risk getting 500 dollar spike on my Verizon bill Cuz it was hacked.
Thanks for trying guys.
Click to expand...
Click to collapse
Lol they won't bill you $500 for "hacking" your phone. Jailbreaking / rooting / etc. is all legal; the most they can do is void your warranty.
shadytech said:
I had the same issue with my OTA update. But Verizon won't warranty my 5 month old phone because it was not purchased on my line. Grr... Anyone that has any suggestion of how to fix it, please let me know/.
Click to expand...
Click to collapse
Contact HTC; see if they can warranty it if VZW won't.
Related
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.
My phone has is in a bootloop from out of no where. I am on CounterShrike 2.3a and have been for a while. My phone died on my way home and when I plugged it in to charge on my laptop, it came on after about a minute and started to bootloop. I've tried to get into recovery but it get into is HBOOT screen. Any ideas? Also ADB will not recognize my device
Interesting. I know a few others that had this issue. I am mentally noting which rom they were on.
Jlluna87 said:
My phone has is in a bootloop from out of no where. I am on CounterShrike 2.3a and have been for a while. My phone died on my way home and when I plugged it in to charge on my laptop, it came on after about a minute and started to bootloop. I've tried to get into recovery but it get into is HBOOT screen. Any ideas? Also ADB will not recognize my device
Click to expand...
Click to collapse
ive had this happen to me too in the past. i had to get a copy of recovery onto my sd and flash it that way. i have no clue why and i was on viper rom at the time but that was the only way i could fix it. :/
Okay got to through. But now i have no connectivity to data? Would this be a radio issue?
Edit: Okay, so it might be a SIM card issue. Switched back to Global Rom and it popped up saying it doesn't register my SIM card. Gonna try that on my next day off.
Edit: Everything is good again. New SIM card fixed the data issue
Sent from my ADR6425LVW using xda app-developers app
I know there are lots of posts about bicks, but after a week searching I could not find any fix for my problem.
I have a S-Off, rooted GSM Evo 3D running Yoda ICS ROM and 4ext Recovery. One day, I was charging it when it hung, I restarted the phone, but it went directly to the bootloader (I didn't touch anything), as I was unaware of what was happening, I simply power it off (using the menu option), when I tried to power it on again, I got no success, only a dim red light appeared, and it is this way eversince.. I cannot power it on, go to the bootloader or anything, the computer recognizes it as QSUSB-DLOAD but there is no partition on it (I tried both Linux and Windows). I tried some unbricking methods without success. I am in Brazil, I tried to call HTC but they said I have to send the device to the origin country (mine is from Rogers, I believe it is Canada), but I don't even know where to send and I'd prefer to fix it by myself if possible. I am open to suggestions anyone could help?
Thanks a Lot!!
AW: [Q] Hard Brick evo 3D
Does adb detect the device?
In that case you could try to run a ruu...
If he can get it into recovery mode then yes. Most of the time its usually something that the end user has done to make it get bricked. I am not saying he actually did something. We also don't know what he has done with his . Phone changing your cid is a good way to brick it. Pulling the battery during a ruu update, flashing a CDMA firmware etc things like that are guaranteed brick makers. However there's only one solution I know of should you not be able to boot into recovery. Try and Google up JTAG. I'm fuzzy on the details about how it works but it can restore your hboot. If you know somebody that knows how to do it, that's your best shot. Otherwise, you will have to send it into HTC Canada or you could try to buy the JTAG hardware and learn how to use it to restore your phone. If anybody has a solution for him please feel free to chime in. Sorry about your phone though. I wish you the best of luck on getting it restored.
Quantenhall said:
Does adb detect the device?
In that case you could try to run a ruu...
Click to expand...
Click to collapse
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
RonaldoPA said:
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
Click to expand...
Click to collapse
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
RonaldoPA said:
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
Click to expand...
Click to collapse
Try using this to unbrick the phone (aimed specifically for DLOAD error, but has worked for other cases): http://forum.xda-developers.com/showthread.php?t=1522351. Afterward, use a combination of both the official instructions from Unlimited.io and this video tutorial to achieve S-OFF. The instructions give you an idea of how-to, the video actually gives you a better sense for the timing. The timing is very specific that needs to be done just right (might take quite a few times to get it done).
If you have an HTC Evo V 4G with Virgin Mobile USA, then you can use this flashable RUU to return to stock (I extracted this from the RUU.exe; just ensure that your bootloader is LOCKED. You can check this by Holding Pwr+Vol Down during boot; top of the screen should say LOCKED). If your phone skips loading into your bootloader and boots into the main OS, pull the battery to bypass quickboot (or turn it off in the settings). To flash the RUU, move the file to the root of your SD card, boot into bootloader, and follow the directions on screen.
brick evo 3d
when i update mwakiousSGS2rom_v.3.0.03 to my evo 3d . this is my bi mistake .and after that my mobile is of ..so pls what can i do .help me
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
sethandian said:
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
Click to expand...
Click to collapse
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
t5620 said:
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
Click to expand...
Click to collapse
Thanks for posting up the links.
sethandian said:
Here is where I was at, ready to throw away the phone I ruined.
Click to expand...
Click to collapse
As long as the screen comes on for this phone, its virtually always recoverable. There was never any reason to think you had to throw away the phone. Next time you are stuck, just ask for help here; as we are happy to help. You did the right thing in trying to find existing solutions. But it sounds like you did your due diligence searching and reading; and would have been justified starting a new thread and asking for help.
sethandian said:
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else.
Click to expand...
Click to collapse
That is precisely what the RUU does. Its a complete image, and handy for recovery purposes.
sethandian said:
I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. l
Click to expand...
Click to collapse
While the OTA has had some reports of causing battery issues, the RUU has not had any reports of such issue, and seems to be free of it.
sethandian said:
I am not sure a phone that is S-OFF would work but it doesnt hurt to try.
Click to expand...
Click to collapse
S-off does not affect whether or not the RUU will work, I don't know why folks keep saying or asking this. RUU will work whether S-on or S-off. The only difference, is that with S-on, you need to either have a LOCKED bootloader, or RELOCKED (relock it manually if you unlocked it).
Also, in general, S-off does not limit anything. It means "all security off" and enables more access, not the opposite. If anything, S-off enables more things than S-on.
Thanks for the all the info. The experience was a valuable teaching moment. Now back to playing around with the M8.
Got hit with the dreaded bootloop this morning. Currently rooted+unlocked bootloader so the yellow 'your android os may be corrupted' triangle shows when restarting. Will that affect my warranty situation? Guessing yes, so has anyone been able to unroot while the bootloop is happening?
CLKeenan said:
Got hit with the dreaded bootloop this morning. Currently rooted+unlocked bootloader so the yellow 'your android os may be corrupted' triangle shows when restarting. Will that affect my warranty situation? Guessing yes, so has anyone been able to unroot while the bootloop is happening?
Click to expand...
Click to collapse
I guess I would try to get rid of that....
You can check out my topic here- Random (Hard?) Brick
Can you get into Download Mode? Recovery? Anything?
You should be able to get into USB-Download Mode by pulling the battery, putting it back in, hold down Vol-Up, and connecting your phone via USB to your PC.
If you are able to get in there, I guess I would try doing an update via LG Bridge. That put my phone 'back to normal' (except still bootlooping). I was then able to get into Fastboot as well and relock the bootloader.
Results May Vary
I wanted to bump this thread as I just went through the same issue with my phone in the same state.
My local T-mobile store got on the phone with support to confirm there was no fix and they (T-mobile) employee saw the corrupt screen and she read what the screen said to tech support, no one had an issue, they simply warranteed the phone and I paid nothing.
Not saying this will be typical but for me, it was very easy.
CLKeenan said:
Got hit with the dreaded bootloop this morning. Currently rooted+unlocked bootloader so the yellow 'your android os may be corrupted' triangle shows when restarting. Will that affect my warranty situation? Guessing yes, so has anyone been able to unroot while the bootloop is happening?
Click to expand...
Click to collapse
I had an issue where my phones charging port died. I went in with the "Corrupted OS" screen and they took it. Lady even looked at that screen for the entirety of it showing. Good luck though
CLKeenan said:
Got hit with the dreaded bootloop this morning. Currently rooted+unlocked bootloader so the yellow 'your android os may be corrupted' triangle shows when restarting. Will that affect my warranty situation? Guessing yes, so has anyone been able to unroot while the bootloop is happening?
Click to expand...
Click to collapse
I had the exact same thing happen to me while I was out of town for work. When I got back to my hotel, I kept trying to flash the stock KDZ using LGUP over and over and it would not work. I went to my local T-Mobile store once I got back home and filed a warranty claim and had a new V10 within 2 days.
You could always remove your SD card, put the phone in fastboot mode and re-lock the bootloader to remove that warning before you return it.
thnx.