This is something odd I haven't experienced with any Android device until now.
Whenever my Rezound battery is depleted to the point where the phone shuts down, I cannot get the device to boot back up again without ADB.
While it's powered off in this state and plugged into charger, it exhibits no charge LED or any other type of activity.
After pressing the power button, it appears to do nothing whatsoever.
If plugged into my laptop USB, the OS detects the device and loads the Debug mode drivers. ADB DEVICES shows the device as being in Recovery, and the device is still completely dark, no video, no backlight, no button lights.
At this point I can ADB SHELL and issue commands, but it can take up to a dozen REBOOT commands (although sometimes on the first or second try) to get the device to do anything other than reboot directly back to dark-screen recovery. I just keep running REBOOT until finally the white/green HTC image appears and the phone boots normally as if nothing was wrong.
Once booted, it behaves perfectly for as long as the battery doesn't die. I can reboot, HBOOT, power off and on, do a Clockwork backup... But, if i let the battery die, I have to ADB REBOOT until it decides to come back to life.
What do you think. Hardware or software issue? Try RUU?
Thanks!
there's definietley a huge problem wtih this phone. i had a guy bring in a phone that died overnight and the same thing happend...he'd plug it into the wall, for 5 seconds it would show orange charging LED, then just shut off..phone wouldn't power on, either. he had it plugged in charging for 3 hours though, and the phone was still dead.
when i switched batteries, teh phone would not go past the white HTC screen. it was just dead. we had to get him a replacement. i'm seriously afraid to shut off my phone now or even let it die. sigh.
Oh yea, mine does the not booting past white HTC screen occasionally between REBOOTs as well. I am disappointed with HTC now, my original AMOLED Incredible was totally rock solid for the 2 years I carried it along 40+ airplane rides to 11 different states. This Rezound craps the bed if you give it a dirty look
Everyone should take a look at this thread in the Vivid forum. People were havin problems with their phone booting into CWM when the battery was dead, me included. Our CWM was updated to support charging and now all is fine. Might be worth looking into.
http://forum.xda-developers.com/showthread.php?t=1429250
Weird, just let my battery die before reading this thread, didn't experience this..
but def not going to let it die again!
As per feralicious' suggestion I've created a poll to collect data. Information on the issue below. Sorry about the long poll.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I'm on Rezound #2 right now. Both of the phones had the same exact problem when the battery died ie. they simply wouldn't charge. Now I thought the problem was hardware (which is why i got the replacement), but after being able to boot up my replacement phone with my girlfriend's battery, I relocked and RUU'd back to stock. I then threw in my dead battery and VOILA it began charging. I let the battery die again just to see if i can recreate the problem, and havent had the issue since.
Now i really want to unlock my phone again but my girlfriend isn't here all the time for me to test out if this was an issue with either the unlocked bootloader, a kernel issue, ROM issue, or if I'm actually having hardware issues. I'm hoping someone here with an extra battery or external charger here can recreate the problem and hopefully we can pinpoint this. Just for reference the ROM I was using was CleanROM GBE 1.6.5 *SP1* - Base: OTA 2.01.605.11 and whatever kernel that came with it. If this is a ROM and/or Kernel issue, we need to get a hold of scrosler and let him know.
Any help would be much appreciated guys thanks!
EDIT: Just to let you guys know. I did do all the OTA updates prior to unlocking the bootloader in the first place.
UPDATE: So I've been sitting with my phone literally all day trying to pinpoint what could be the cause of this. Clockworkmod seems to be the culprit. I'm going to be testing more right now so I'll keep you guys updated.
UPDATE #2: Success! The battery not charging while dead and powered off issue was resolved on my end. ClockworkMod definitely was to blame. I noticed it stopped charging while powered off/dead as soon as I flashed ClockwordMod and shut down my phone while it was connected to my PC (This was after my 5th go around with the bootloader unlock). I then flashed over Amon Ra to see if it really was ClockworkMod or if it was the recovery in general, and what do you know Amon Ra allows me to charge while powered down and dead. If you guys are having this very problem with your phone and you're running any version of ClockworkMod I suggest you try flashing Amon Ra 3.13 and posting your results so we can see if this is universal.
Instructions to flash recovery with adb and fastboot for Windows below:
Note you only need to do this if for some reason you can't boot into the bootloader using Vol. Down + Power. I am not responsible for bricked phones.
Prerequisites:
1. ADB & Fastboot (found with the Android SDK)
2. Amon Ra IMG (Use ver. 3.15 if you've flashed ICS RUU)
3. Battery with a charge.
Instructions:
1. Pull out battery, and unplug from charger/computer
2. Reinsert battery
3. Plug in your USB cable to computer and phone (your charge indicator light should go on for 1-3 seconds and shut off, then your drivers should load afterwards.)
4. Place the Amon Ra img file in the folder where ADB and Fastboot reside.
5. Once drivers have loaded open up Command Prompt, and find your way to where you set up ADB and Fastboot. Type cd <folder path>
6. Now type the command adb reboot bootloader (Note: if you get some sort of error try again a few more times. if it keeps giving you error try redoing steps 1-3 before doing 5 again)
7. Your phone should have now loaded directly into Fastboot. When in Fastboot go back to the command prompt and type in fastboot flash recovery <amon_ra_file.img>
8. When the process is done shutdown your phone and test the charging.
**ADDED** If you can run ADB commands while the phone is off, dead, and not charging, type adb reboot. The OS should boot up and begin charging. I would say let it charge till 40% before you flash an alternate recovery. If you're unsuccessful in rebooting with adb try leaving your phone plugged into the charger for 2-5 hours (this seems to have worked for some people to get a charge). If that doesn't work I recommend you get another battery or use an external charger. (Thanks excellentnuke)
If you are coming from a dead battery the charge light indicator should turn on for a few seconds then turn off for a few seconds then begin flashing continuously. When the light becomes solid you should be able to boot. When coming from a charged battery the same thing should happen, except instead of the charge indicator flashing continuously it should come back solid.
UPDATE #3: I've also discovered this problem isn't relegated to having a dead battery. Simply disabling Fast Boot and shutting off your phone can recreate the problem with CWM.
UPDATE #4: I can say that I think I've gotten enough feedback to determine that this issue was solved by what I've written above. I would highly advise people to switch over to Amon Ra until we get a bug fix/update for CWM to address this issue.
Thanks to everyone that was involved in this thread to help determine the cause of this; I appreciate it.
You should set up a poll and change the thread title to indicate that.
I am on Ineffabilis GB and accidentally let the battery die yesterday and it charged no problem. I was ready for a problem, thankfully it went straight to charging. I had also let it die once before unlocking and no problem then either.
feralicious said:
You should set up a poll and change the thread title to indicate that.
Click to expand...
Click to collapse
Good idea. Done!
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
I have been running different ROMs and had it die a few times...
When I plug it in the LED comes on and starts blinking, after a few minutes of the blinking, I unplug then re-plug in the phone to the charger and the light comes on and stays on. I never let it sit there long enough to stop blinking on its own. I get impatient LOL.
UgXvibe said:
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
Click to expand...
Click to collapse
I take it you're running stock still? or a custom rom? It seems odd that the charge indicator would take that long to start. I left mine on the charger for about 30 minutes when it was unlocked without any progress.
This happened to me, I took my phone to verizon and they just gave me a new battery... it took a little while, them trying different batteries, looking for a 'test' rezound battery before pulling a packaged battery to try and finally they were satisfied then swapped it out... all my boot logos and screens were stock but my launcher was not... they never went as far as checking phone specs or asking about root/unlock... they did check the phone settings to check on charge at one point... I was just thankful it wasn't a bad micro connector because I didn't want to have to wait for a new phone
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
andybones said:
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
Click to expand...
Click to collapse
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
drinkhere said:
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Click to expand...
Click to collapse
I would highly suggest you relock and go back to stock. It seems to have made the issue subside. Since you have 2 batteries if you wanna do further testing with other roms and configs that would help out a lot. No pressure though i understand if you dont want to do it.
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
joel4832 said:
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
Click to expand...
Click to collapse
Hmmm... I'm beginning to suspect its either an unlocked bootloader issue or a kernel issue and not a ROM issue.
Now thats cool that your phone was able to boot up after an hour on the charger without the charge indicator light telling you it was charging (my phone was probably doing the same thing) but it still shouldnt take that long to be able to boot up the device.
When stock my charge indicator blinks continuously until it's ready to boot up, then it becomes solid. This only takes about 4-5 minutes. When running custom ROM/Kernel it would give me the same thing it gave yours ie. charge indicator turns on for 1-3 seconds and turns off and nothing else.
afmracer6 said:
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm definitely going to take this into account and try it when i unlock my phone again. Thanks man!
IrvChynaman said:
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
Click to expand...
Click to collapse
Update in OP!
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
edit: i would also like to note, when putting the battery [my 3.7v] into my girlfriends device. It showed about 80% battery.
krstnsn said:
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
Click to expand...
Click to collapse
are you running clockworkmod recovery? Your issue sounds identical to mine and I MAY have a solution. I'm testing right now on my own phone right now.
IrvChynaman said:
are you running clockworkmod recovery?
Click to expand...
Click to collapse
yes. the touch one. However i had this issue prior with the unofficial clockwork.
krstnsn said:
yes. the touch one. However i had this issue prior with the unofficial clockwork.
Click to expand...
Click to collapse
Ok try flashing Amon Ra 3.13. Clockwork mod seems to be the culprit from my end. what was weird is when the phone was shut down I was able to run adb commands and every time i ran "adb devices" it showed my phone as recovery. It seems like clockwork mod recovery was trying to load before anything else preventing the phone from charging and booting up
I'm not sure if I'm slightly ****ed or totally bricked...
HOWEVER, I have: ClockworkMod Recovery, CleanROM (GB version). Installed last night.
Today, I was flying/traveling, and my phone lasted 5 hours (HURRAY!); I turned it off on my second flight because the power was at 11%...figured I'd save my phone in the event I needed the juice.
Well, now I have a brick ATM because now there is no screen magic. The only sign of life is a little orange light that is lit for maybe 10 seconds if I plug the phone after removing batt/plug and re-insert and press power.
I don't know how this could go from working, shut down, then **** you I'm dead?
I'm totally stumped. :/
Edit: I remember reading a while back that if these 3.8v batteries die on an ICS rom or something, then they don't charge? Or something like that.
Have a look at this thread.
http://forum.xda-developers.com/showthread.php?t=1489687&highlight=cwm+battery
It should help you out.
Try pulling the cover off, take the battery out, put it back in and restart normally. My wifes phone would not start one day so I pulled the battery and then it worked fine.
Alright; taken care of. Battery was dead but did that "adb reboot bootloader" command and was then able to restart via the bootloader and it loaded right into Android and charged the battery. Will be flashing Amon Ra shortly though.
Thank you!
A few days ago my phone got soaked through my pants as I was working in the rain. I came home, dried it out, etc. and tried to turn it on. Wouldn't turn on, so I started charging it. I eventually got it to turn on and it seemed to be working fine except for some reason it said the battery life was at 0 %. Note that it was still working normally otherwise.
I went into recovery, made a backup, and did a factory reset to see if that would fix the problem. It didn't, so I restored the backup. Now the phone won't turn on at all.
When plugged in, it shows the charging battery symbol, and if you hold power to turn the phone on it will sometimes begin to start, but it gets to the boot animation and simply stays there forever (I've left it at the boot animation for several hours to no effect). If I try to boot into recovery it simply does not work; it will either just restart the battery charging animation or boot normally (and then get stuck on the boot animation).
In a last ditch effort, I was going to try to flash a stock ROM from Heimdall. However, I plugged my phone in and tried to enter download mode and was greeted with the error: "LOW BATTERY!! CAN'T DOWNLOAD!!." This was after charging the phone all night. I then proceeded to charge the phone for another hour then try again, to the same error. And now here I am. It seems the problem is that my phone will charge, and the battery will be full but for some reason the phone doesn't recognize that the battery has a charge, so it just thinks it's at 0%. I've tried a different battery and was unsuccessful. Is there any way that I can either force my phone to enter download mode or somehow get it to recognize the charge on the battery? Or is there some other way I could resolve this? Or is my phone simply gone for good?
I am (was) running a rooted I777 with Slim Bean ROM ( I believe v8) 4.2.
Have you tried using a JIG it can be an option
If a JIG doesn't work you can try removing the battery, then plug the phone to the PC and go to download.
But for me the problem is with the battery. If after flashing the ROM you get the same results, don't think it and BUY A NEW BATTERY.
Good luck.
Sent from my Nexus 7 2012.
If I'm bad at English is because I'm from Argentina and I'm learning.
I has the same problema, I spend two days searching on the web, but i didnt have any idea.., ,y problem is. when we conect to ANY charger (car/wall/PC-USB..) appears on screen a batery logo, but the batery never charged..., I tried to enter to the CW but, the keys combination doesnt make anything on the phone, and without live on it, I cant access to CW..., I wait for 2 hrs, with these cell phone conected to charger to see if the it gone works...
ANYONE has another idea for how we resolve these issue? My phone has a stable version of CyanogenMod..
same with me but what i did was put a different battery in, let it charge for a bit then put the original one in and it only started charging after i used my car charger as i was driving to work so thats how i fixed mine.
Hi,
So this is the problem,
Screw somehow couldn't screw in with battery installed but it was able to do so with battery removed from phone.
I removed screw again. After some time when I screwed it in again, it just couldn't come out, just kept spinning in place.
So I, just out of boredom went to instal battery with - screwed in and + connector just placed over screw.
It worked for a while but wasn't able to display battery on stock 4.1.2 and custom 4.3, only question mark was displayed.
I have CID error so I boot over BMM.
When battery drained it would not boot anymore. After that, when connected to charger it would display ? again, and only few times it allowed me to boot, but unexpectedly shuts down while still connected.
After that it wont boot again when connected to charger or make any reaction when it's off the charger.
When I connect it to charger while it's shut down, normal process would be CID error-Orange led flash-Battery status, and now it is the same, accept the battery status which is ?
Now if I disconnect it when charging process just started it would hold till end with only charge coming from battery.
I've also tried charging with wires with no result.
Thats about it, I hope you will be able to help.