Wondering if anybody has experience or suggestions on this issue. I've searched around but I can't find this particular formulation of an Amaze/Ruby boot loop problem.
I unlocked my bootloader a few months back and, after a fair bit of monkeying around, got Speedrom running perfectly smoothly. I had the occasional random reboot, same as on the stock rom, but everything was working well.
A few weeks ago, the reboots got more and more frequent. They only ever occurred when I was interacting with the phone i.e. not when the screen was off. Last week, the phone stopped turning on altogether. I couldn't even boot to recovery. After a day with the battery pulled, I managed to get to recovery and reflash Speedrom. Now a few minutes after every boot, the phone reboots itself and the process loops indefinitely. This happens whether I'm using the phone or not. The strangest part is that as long as I have the phone plugged into the USB drive of my computer (charge only, storage not mounted), it's rock solid with no random reboots. The second I unplug the USB cable, it reboots itself.
I've tried flashing the stock RUU (I'm on Mobilicity), a backup I made while on stock, and multiple other roms. They all work perfectly as long as my Amaze is charging off my computer via USB, and all reset ever minute or so when not plugged in. I'm really at a loss here.
For what it's worth I'm using 4ext and I'm s-on. If anybody has any words of wisdom here you will be my internet hero.
Related
It started out of a blue, one day my phone started to lose signal. Nobody was able to call me and I wasn't able to call anyone (Same deal with texts). So, I rebooted device and I still wasn't been able to use it, and in addition battery level decreased suddenly from sth like 70% to 3%. After about 10 minutes I was able to use it again. I thought that problem was my old TeamWhiskey Bionix, so I flashed CM10. Issue repeated several times a day. I tried different radios - nothing helped. Fortunately, WIFI still works, so I can use SIP...
Anyone has idea what can be the problem?
And I almost forgot... One week before radio freezed - I rebooted and device was alive again, so I forgot about it until now :/
EDIT//
Now I'm no more able to charge it cause Interface crashes when i plug USB in...
Hey everyone, I could use some help with a few Thunderbolt issues I have.
Here's a few points of description about the issues:
Whenever I use data on the phone (either 3G or 4G), the phone browses fine for about 3-5 minutes, then suddenly powers off. When I power it back on, the phone says it has 0% battery left, and will very quickly turn itself back off. When I plug it in to charge, the phone will turn on without issue and say it has whatever % battery it had before it turned off suddenly the first time.
If I simply use the phone for calls or non-internet things, the phone works fine. Once it's turned off once, though, it'll think it has 0% battery and not even offline things will work.
The phone seems to work OK for short-burst internet browsing, like checking email, but anything continuous (web browsing, streaming music) will shut it down within a few minutes
While plugged in, I can browse the internet, stream music, etc. just fine without the phone ever having any issues.
As a less serious and potentially unrelated problem,
The phone is not recognized by any computer. I have tried changing USB cables, computers, laptops, installing drivers, etc., but the phone only lists itself as "Charging" and never says anything about USB connections / USB debugging.
The issues first started when I tried out LiquidSmooth ICS about a month ago, with the recommended newer radio. I tried running the MR2 and MR2.5 radios on LiquidSmooth, and that didn't seem to change anything, so I went back to my old Gingerbread AOSP ROM, but the problems persisted.
Now I'm running stock with the stock radio (S-ON unrooted), and once again the problems are the same. The phone has been trying to download the ICS OTA update, but it always says "DOWNLOAD FAILED."
Anyways I'm not sure if the hardware on the phone has just broken, or if it's possible to fix through software. Anyone have any ideas? It would be much appreciated.
Sounds like you have a bad battery. Only thing I can say is you must not have properly unrooted your device or you have one of the few phones that will not do an ota update. I had this happen to my original droid when froyo came out. They try pushing the update but just wouldn't accept it. Also maybe your battery issue is causing your update issue. So just get a new battery and go from there.
Sent from my Nexus 7 using Tapatalk HD
I replaced my batt and my problems (the same as yours) went away!
Sent from my iPad using Tapatalk
Hi,
I have a Sprint 4G LTE rooted with VIPER rom installed. Last night my phone freaked out, so I did the 10 second "battery pull" and it started up again. I plugged it into the charger and I fell asleep without much worry.
I woke up to find my phone stuck at the LTE splash screen of the VIPER rom. I've done the 10 second "battery pull" several times, and it doesn't just shut the phone off, it forces a reboot. Each time it only makes it as far as the LTE splash screen.
My experience with phones and computers is telling me that the OS might have gotten corrupt some how since it is stuck at the splash screen.
I do have access to the bootloader, so I have some paths I can go down, factory reset/recovery, but both those I'd like to avoid so that I do not lost the contents of my storage.
I have had VIPER rom installed for a good half year, so this issue isn't due to a new rom being flashed.
Does anyone have any suggestions?
Thanks,
-billypilgrim
When data gets corrupted, all you can do is wipe and start over. I had to do that once when running Viper as well.
Just a thought in trying to be helpful....
I used that ROM for a while myself and never really had any issues but have had a similar situation.
I pulled my sd card out and backed it all up. Replaced SD card.
Then went into recovery and reflashed the ROM.
Worked solid after that and no explanation as to why it was corrupt/hanging in a loop.
Hope this helps..
billypilgrim said:
Hi,
I have a Sprint 4G LTE rooted with VIPER rom installed. Last night my phone freaked out, so I did the 10 second "battery pull" and it started up again. I plugged it into the charger and I fell asleep without much worry.
I woke up to find my phone stuck at the LTE splash screen of the VIPER rom. I've done the 10 second "battery pull" several times, and it doesn't just shut the phone off, it forces a reboot. Each time it only makes it as far as the LTE splash screen.
My experience with phones and computers is telling me that the OS might have gotten corrupt some how since it is stuck at the splash screen.
I do have access to the bootloader, so I have some paths I can go down, factory reset/recovery, but both those I'd like to avoid so that I do not lost the contents of my storage.
I have had VIPER rom installed for a good half year, so this issue isn't due to a new rom being flashed.
Does anyone have any suggestions?
Thanks,
-billypilgrim
Click to expand...
Click to collapse
I have that happen several times. Nothing obvious that causes it. Cap'n is right need to wipe and re-flash. Here's the small trick since it just keeps rebooting on you, after you hold power for ten seconds and the screen blacks out. Make sure the capacitive buttons go out as well, that split second they go dark let go of the power button and press vol down and power to get it back into bootloader. Then you can get back in recovery to flash.
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
DentalAppointment said:
Hi everyone. I'll try to make a long story short while being thorough. Any help is much appreciated in advance.
TLDR Version: after messing around trying to get a working ROM and finally getting Tachyon 4.3.1 to load (without the SIM Card in), I powered down and the Rezound no longer powers on in any mode nor is it registered by adb. LED lights up while plugged in, that's it.
Complete version:
I spent a few days reading up on rooting & ROMing - but apparently not long enough - then spent an arduous night attempting to get a working ROM on my Rezound. I initially used AmonRa to get RezROM EX 3.4 to load up, but was stymied by constant "com.android.phone has stopped working" messages. After attempting several fixes, I formatted all back to Ext 3, and wiped the phone to factory settings (I know, I know...) in an attempt to start fresh. After that sloppy attempt, the phone wouldn't get past the initial white HTC screen, so I did the following using less than stellar judgment: I removed the Verizon SIM Card, rebooted, and installed Tachyon 4.3.1 (linked at bottom) in AmonRa recovery. Miraculously, I thought, the phone loaded up Tachyon and after one "com.android.phone has stopped working" message, I was able to use the phone, albeit with no network connection. I thought all I had to do was power down, put in the SIM Card, and maybe things would be alright.
Instead, what happened was this: I powered down, took out the battery (which had some charge) and put the SIM Card in. When I pressed the power button back on, the phone did not turn on. Unplugged, not even the LED would light up. I plugged it into my PC, at which point the LED does turn on, but pressing power only causes the buttons on the bottom portion of the phone to light up for a few seconds. That's it. The screen does not do anything. Holding Volume Down + Power does the same thing; it does not vibrate or boot to Recovery. Lastly, adb no longer registers the phone's presence (error: device not found). I plug it in the USB, hear the chime, but commands like adb list, adb reboot, etc. do nothing. The phone appears as an external drive in Explorer, but it cannot be opened. I've now tried two batteries and let the phone charge for a few hours. Still no results.
If I've bricked the phone, I understand. I fortunately have another Rezound I can fall back on. I understand the risk of taking the unresponsive phone to the Verizon store, so I'm asking for help/suggestions here. Thanks!
Click to expand...
Click to collapse
So, if you disconnect the USB cable, remove and reinsert the battery (also, try another battery), then press and hold POWER+VOL DN for a few seconds are you able to get into HBoot? If not, it is likely borked, but not because of flashing a ROM, it was probably just it's time to go...
got it working
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
DentalAppointment said:
Thanks for the reply.
Just to update this post, I did eventually get the Rezound working again. Clearly it wasn't totally borked, but I guess I had in fact drained the first battery without knowing it - when I inserted the second battery, which I believe did have some power left, for some reason that power wouldn't register with the phone. I left it plugged into USB for a couple more hours and after several on-off and USB plug-unplug attempts, I eventually got it back into HBOOT (not to give myself credit for this), to my relief.
I then switched to Clockwork revival and managed to get Cyanogenmod 10.2 (10.2-20131217-Flyhalf2015-vigor) working on the phone. Without understanding what happened with perfect clarity, I surmise the reason the install wasn't working in the first place was that I was attempting to install a different kernel simultaneously - ie. from recovery mode without a reboot in between. Either I got the order of installation wrong (ROM before kernel or ROM after kernel I don't know) or that kernel was not compatible. Anyway I wiped the phone again and just installed Cyanogen without attempting to install a kernel and it worked - I'm guessing with cyanogen's own kernel.
So now I have Cyanogen working and ROM Manager set up with a backup. While the new features and customizability are cool, the system overall is somewhat glitchy. Don't know if that's due to the version of cyanogen, the kernel, my installation technique, or the phone hardware. It's certainly not unusable and I'm going to leave it as-is for a bit after this ordeal, but the following glitches happen occasionally:
-not all lock screen features appear, or lock screen background won't appear
-phone screen will suddenly fill up with random 'glitchy' patterns of colored pixels
-screen will remain black after tapping power switch to go from idle state to using. backlit keys will light up but will have to remove battery and restart device to work again
-battery life is still poor if not a bit worse (probably not a glitch, just rezound's stock battery)
But it's now an old piece of hardware and I'm still happy I carried the process through to the end. Given that I couldn't stand certain aesthetic features of the stock OS, I am content with the results for now.
Fin
Click to expand...
Click to collapse
I had some unfortunate nastiness happen to my Rezound a while back which prompted me to go out and get an M8, but I did eventually get the Rezound 99% functional again.
First off, cell phones in general rely on something called NAND memory for all mass storage. It's decently quick stuff, but not the most reliable storage medium in the known universe. Basically, it slowly dies with use. NAND only has so many read/erase/write cycles before it begins to degrade. This can lead to very quirky corruptions in the partitions, and that's kind of what it sounds like has happened to your Rezound. The fix that got mine back to working order was a complete stock RUU restoration followed by a "factory reset" through Hboot. That will wipe and rewrite all of your partitions. Then flash your custom recovery, ROM, and kernel.
As for flashing ROM's and kernels in the right order, you want to flash the ROM and then the kernel. A lot of devs recommend flashing the ROM, then booting it up, then flashing a custom kernel, however, if you know you've got a working combination of ROM and kernel, there is no reason you can't just flash the ROM and kernel (in that order) at the same time in recovery.
I encountered this problem yesterday. Every time the phone would sleep, when awaking it, the system with momentarily freeze then reboot. Here is the real mystery, it also would not power down. Instead of powering down, it would reboot. It would reboot into system if powering down from the desktop, if power down or recovery was selected from bootloader or if power down was selected from the recovery screen. The only way I could reach recovery would be to allow it to boot to the desktop, plug in the USB port to a computer and ADB reboot recovery. Bottom line, you couldn't turn the thing off!
I'm running Captain Throwback's 4.13.651.4 Custom ROM, TWRP 2.8.5.0, HBOOT 2.10.0000, Radio 1.13.11.1105, UNLOCKED, S-OFF, rooted with SuperSU. I loaded the Captain's ROM according to the instructions, electing to run the stock 4.13.615.3 RUU before flashing his custom ROM. I've been running fine on this config for about a month.
Here is what I did to fix it. First, I wiped Dalvic Cache, Cache, System, Data, and Internal Storage. Then, I tried to do a full restore from a TWRP backup I had done after I loaded the stock 4.13.651.3 RUU. The restore ran for about a 30 seconds and suddenly, rebooted into system before the restore finished. Obviously, it didn't complete the boot and was locked on the boot screen. Now, all I had could reach was bootloader. Bootloader still would reboot into system (unsuccessfully) if recovery or power down was selected. I'm thinking brick at this point. All things start from boot so, I decided to try replacing boot. I connected the USB cable to the computer and fastboot flashed the copy of boot.emmc.win (same as the existing running version) from the TWRP backup done after I loaded the stock 4.13.615.3 RUU. Rebooted into bootloader (flashed copy, I assume) but, no change except, now, the phone would reboot if I connected the USB cable to the computer in fastboot. However, it would not reboot if I connected a wall charger in fastboot. I'm definitely thinking brick now.
Tried one last thing before frisbeeing it. I took phone out of the mid-frame and pulled the battery cable to the motherboard. I left it off for a minute or so before reconnected it. When I reconnected the battery cable, the phone immediately booted into system (unsuccessfully) instead of staying powered off. Now, I'm sure it's Frisbee time. I pulled the battery cable to the motherboard and went to dinner. Got back from dinner and reconnected the battery cable and started putting it back together. But, the phone stayed powered off this time. I finished putting it together and it started working normally. Bootloader would power off the phone and would boot recovery. Recovery would also power off. I reflashed Captain Throwback's 4.13.615.4 custom ROM and everything seems back to normal.
Does anybody have any insight into this? I've never heard of a phone behaving like this. If it was a corrupted HBOOT, it seems reflashing it would have fixed it. Why did leaving the battery disconnected for a long period finally resolve it?
Update on this problem. Discovered the power-down problem resulting in a reboot is common on Android AND IOS. All the replies I've seen so far keep referring to a "bug" that will hopefully be resolved in a later update. Still can't find any replies about reboots after waking from sleep. The reboot on power-down problem has returned to my phone as well. It is not rebooting when waking from sleep however. I did discover that, if I turn Wifi off before I power-down, the phone does not reboot. I have reproduced this 10 to 15 times. Each time the reboot on power-down problem occurs, the Wifi was on when I powered-down from the desktop. When I turned Wifi off before I powered-down, it did not ever reboot.
I'm not getting any replies to this tread. Am I posting in the right place?
Second update on this lonely thread. I've narrowed down the problem to a hardware issue. I was having another problem with the WiFi not connecting to local routers intermittently. This is another issue that is commonly reported for this device. I noticed that, when I pressed on the front of the mid-frame on the HTC logo, the WiFi would suddenly connect and stay connected for a period of time. The connection would eventually be lost and, I would have to press on the same area of the mid-frame to get the WiFi to connect again. If you take the top rear cover off, the part on the motherboard where the WiFi antenna (and, perhaps some of the WiFi circuitry) is located directly behind the area where I was pressing to make the WiFi connect.
As previously noted, the reboot problem on power-did not occur when WiFi was turned off before shutting down. My theory is, when the system was shutdown with WiFi turned on, the malfunctioning WiFi circuit could have been causing the power circuit on the motherboard to sense a power-on condition and, restarting the system instead of completing the power down. OTOH, If the WiFi circuit was turned-off before shutdown, the malfunctioning WiFi circuit was disabled and did not cause the false restart.
Lastly, I noticed the phone seemed to have a bend in it. If I sighted along the top edge of the phone, it seemed to have a slight bowed appearance. It was bowed outward toward the front of the phone. This is why I thought to try to press on the top front of the phone to see if that would cause the WiFi to connect. To my surprise, it did. The WiFi connect problem is a common complaint on these phones as well as the reboot on power-off problem. However, there are plenty of accounts from other users that do not have either problem. I happened to go to the grocery store the other day and saw a young clerk at the store with her phone in the hip pocket of her jeans. It made me wonder if, people sitting on their phones is how these phones get damaged.