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.
Related
Today i woke up to the new Update for the vibrant. So of course i tried to update it. My phone is rooted if that makes a difference running everything else stock though. I did the one click root or whatever it was. Well i clicked update and sat my phone down as i got ready. Come back its at the boot screen where it says Vibrant and Samsung in white. I figured it was just loading the new files and just taking a little long. Well by the time i got to school it was still like that so i removed the battery so it would not overheat. Replaced the battery booted up and stalled on boot screen again. This time it made the opening music but never transitioned screens. So i took battery out replaced it and went into clockwork and did a nandroid. Reset it same thing happened. Tried that with three of my backups of previous dates. all failed. so i decided to wipe all data of the phone or factory reset. still stuck at boot screen.
If anyone can help me it would be much appreciated. if you need any other information just let me know.
same thing here. i've done all those steps. when i get home, im going to try and update the JI6 update through ODIN. i'll let you know what happens.
Common problem, easy solution..
http://forum.xda-developers.com/showthread.php?t=803492
I updated the Flyer through the system menu. It was a small file that downloaded. When it restarted it got stuck in a boot loop where the you would get the white screen with green HTC lettering. It would do the jingle then reboot. Called tech support. They had me do a factory reset. Fixed it. 9 days later. I restarted the tablet and got the same problem. Did another factory reset. Fixed it. Called HTC. They said they can't do anything unless I send them the tablet while it is stuck in boot loop.
It is not rooted. I haven't done anything special with it. Anybody have any clue what might be going on or how I can prevent it from happening again? Or know any apps that could help me figure out what is happening?
Thanks!
Turn on usb debugging and leave it on, then use adb to connect when it goes into a loop and grab the output from logcat. We will probably be able to help you if you can do that.
I had the same thing happen to me yesterday, only the rep said there was nothing to do to fix it. They said it was a known bug. I was able to do a factory reset by plugging in the usb adapter and then power + down vol. Without the adapter, it would continue to reboot even after a factory reset. So far it has worked. I was surprised that the rep did not have me even try anything to solve the problem, but hey.
I had the same problem before updating to Globatron's HC leak. Seemed to happen after rebooting, (almost every time. Got to the point that I decided to never turn it off again) and a factory reset was the only solution. Since HC, the problem hasn't happened once.
\\Carved into this thread by my RAZR//
http://android-gz.com
I had the same problem after the 2.27 update(Never happened before the update.) It would just be random, not all the time (only after a restart, I would always cross my fingers and rub my rabbits foot.) I got into a habit of Nandroid Backing up the device at least once a week, as the problem would occur more than once a month.
I just upgraded to HC a couple of days ago, I have yet to have it happen.
Thanks for the suggestions and sharing. It's good to know I'm not the only one with this issue. I am really tempted to root and go to Honeycomb now. I was trying to keep everything stock until HTC moved it to Honeycomb. If HTC could write software that didn't screw me over, I would be more than happy to be patient for the official update.
Hi
I have a similar issue. I rolled back the device from HC to GB stock rom and I am on the last updated GB stock rom. It is just randomly restarts and I cannot see the reason why? Sometimes after a day or 2. Before this started the sense was randomly freezing and I couldnt do anything just restart. I got taskiller on and this looks like sort out the freezing issue I have over 300 mb memory free most of the time but I have this random restart now.
Is there any way I can diagnose or check in a log file what is the reason for these random restarts?
thx
shadow78 said:
Hi
I have a similar issue. I rolled back the device from HC to GB stock rom and I am on the last updated GB stock rom. It is just randomly restarts and I cannot see the reason why? Sometimes after a day or 2. Before this started the sense was randomly freezing and I couldnt do anything just restart. I got taskiller on and this looks like sort out the freezing issue I have over 300 mb memory free most of the time but I have this random restart now.
Is there any way I can diagnose or check in a log file what is the reason for these random restarts?
thx
Click to expand...
Click to collapse
Yes, like globatron mentioned in the second post, turn usb debugging on (in settings - applications - development) and leave it on until you encounter another bootloop. While the device is bootlooping connect it to your pc and use adb logcat. If you can post the output here someone might be able to help.
Sent from my HTC Flyer.
Hi there,
sorry for using this old thread, but I am having the same problem with my Flyer running Android 2.3.4.
Today I've done nothing with it, just let the battery drain, to make a full recharge. Want to restart it, and: Bootloop. This f*ing melody drives me crazy already!
I've connected it to my laptop, creating a logcat-file. I will edit this post if its ready.
But I am wondering why this happens. There wasn't an update (even if if there whould be: I am rooted, so I couldn't install) and in my opinion I've done nothing special since the last reboot a few days ago.
I've done a backup via CWM, but don't want to perform a Factory Reset because the last backup is... already a few months ago.
... How long does it need to create the logcat-File? I wrote this whole text while he is still writing...
Edit: Haha. It will never end. Have created a 42MB .txt-File.
I've shorten it, until the first repeat of a row. But it is still to long for insertig here, it is attached.
Edit 2: Is there an Option to perfom a backup via adb? "adb backup" doesn't work with Android 2.3, And I haven't found a solution for "adb pull" to copy a complete partition.
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!
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.
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?