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
The first time I've allowed my battery to get very low since installing CM7 on my HTC Merge and I'm now having all sorts of problems.
Firstly my screen won't light up. It's just completely black. The phone is on and the 4 buttons at the bottom light up but that's all. The phone is still responding to my touch as I can load apps and hear noises if I happen to touch the correct parts of the screen. It's almost as if the brightness has been turned way down, but I'm unable to see the controls to try turning it up again. I have tried booting to recovery mode but that doesn't display either.
Secondly the battery won't charge. Since the battery is drained I can only get the phone on when it is plugged in, but the orange "charging" led at the top of the phone never lights up. It just casually flashes like it ordinarily would have done when it was running from the battery. I have two batteries and they're both doing this.
I can't be 100% sure that these problems are due to the installation of CM7 but I've never experienced it before so i'm guessing they're connected.
Does anybody have any suggestions on how I can get my phone working again.
It's also worth mentioning that it is also no longer recognised by my computer
Sounds like a hardware fault, if you have the same issues in recovery as you do in your os then its very unlikely its ROM/software related
I don't your device nor have I taken it apart so its only guesses I could give you on which component needs to be replaced, LCD or flex cable are best guesses
Sent from my Nexus 4 using Tapatalk 2
Want to update on this as I've just had another look at it after a while.
With the battery having completely drained, I connected the phone to charge via my PC and the orange charge light lit up and the phone went into recovery mode without any assistance from me. After about 2 seconds the screen went off again.
When the battery has charged sufficiently, I am once again able to turn the phone on and it boots up... but the screen remains blank.
If I discharge the battery and then plug it into my PC, I am able to repeat the appearance of the recovery screen, but it always vanishes before I am able to do anything.
The screen must be surely be functional or how would I get those 2 seconds of display ?
Does anybody have any ideas of what I can do to get the phone working again?
I acquired a new battery and after fitting it the phone immediately worked again. The battery was completely without charge but the phone charged it up without any problems. However, as soon as the power ran low the same thing happened; the screen has stopped working and the battery doesn't seem to charge anymore.
I made the mistake of letting my HTC Rezound fully drain a few weeks ago. It hasn’t booted since then. It is rooted and S-OFFed, running Amon Ra recovery and the Tron 2.0 ROM. Power light won’t do more than blink a few times after it’s plugged in, and the phone won’t charge the battery. I used an external charger and even bough a spare just in case the original had gone bad. Same effect, except when I try to power it on with a fully charged battery: now, the green HTC on a white background, as if it’s actually booting, will briefly appear before it shuts off again. Trying to power it on a second time without first recharging the battery to full in the wall charger produces no result.
The device does show up under adb devices when plugged in. The problem is that it’s listed as offline. Any commands I send it return with error: device offline . It does not appear at all when I call for a fastboot devices listing.
Is it dead as dead can be or is there something else to be tried? This is likely just hopeful delusion, but I feel that if I could just send it a signal to boot that it’d recognize in offline mode, it’d start. Completely ungrounded belief though, hence why I’m inclined to relegate it to the category of delusions.
I’ve already looked through the following threads for solutions and none worked.
[GUIDE]You've discharged your Rezound and it won't power on. Now what?
[POLL] Dead battery / Powered off inability to charge issue (UPDATE #4!) {Solved!}
[Q] Rezound won't turn on at all, or boot. HELP
Rezound Won't Turn On
Codaraxis said:
I made the mistake of letting my HTC Rezound fully drain a few weeks ago. It hasn’t booted since then. It is rooted and S-OFFed, running Amon Ra recovery and the Tron 2.0 ROM. Power light won’t do more than blink a few times after it’s plugged in, and the phone won’t charge the battery. I used an external charger and even bough a spare just in case the original had gone bad. Same effect, except when I try to power it on with a fully charged battery: now, the green HTC on a white background, as if it’s actually booting, will briefly appear before it shuts off again. Trying to power it on a second time without first recharging the battery to full in the wall charger produces no result.
The device does show up under adb devices when plugged in. The problem is that it’s listed as offline. Any commands I send it return with error: device offline . It does not appear at all when I call for a fastboot devices listing.
Is it dead as dead can be or is there something else to be tried? This is likely just hopeful delusion, but I feel that if I could just send it a signal to boot that it’d recognize in offline mode, it’d start. Completely ungrounded belief though, hence why I’m inclined to relegate it to the category of delusions.
I’ve already looked through the following threads for solutions and none worked.
[GUIDE]You've discharged your Rezound and it won't power on. Now what?
[POLL] Dead battery / Powered off inability to charge issue (UPDATE #4!) {Solved!}
[Q] Rezound won't turn on at all, or boot. HELP
Rezound Won't Turn On
Click to expand...
Click to collapse
since you ARE s-off your best bet is to run ann ruu.exe from my downgrade upgrade guide.....should fix your issue
I usually let my phone all night on the charger and when I wake up check emails, news etc.
So the other day when I waked up, open wifi, check email ... phone started heating up, really heating up, almost too hot to touch and also seemed to drain the battery . So, closed the phone immediately and took the battery off. After that it would start the endless reboot cycle every time I put the battery in and plug in the charger. It won't charge at all even if I tell it to shutdown through fastboot. Bought a battery through ebay which came half charged, managed to flash a stock rom through hboot but nothing changed and the battery is drained now and can't try anything else. Also I have to mention that I couldn't access recovery as it would reboot as soon as I made that choice in the hboot menu. Current status is that as soon as I plug in the charger, red light turns on for one second and than the phone seems to try to boot and well endless cycle of that.
Phone was s-off hboot 1.49 and some recovery which I can't remember.
So... is it dead?
seem like you can boot into bootloader/fastboot. But revovery is a no go? Recovery does off mode charging, so if it's bad you won't charge. That would be a software issue, as for hardware I don't have a clue. If you can power up with cable, then I'd say maybe it's only software. I'd try an ruu, back to stock and see if that fixes.
Phone has been running fine for months, then all of a sudden, it won't boot. Wife said she hasn't dropped it or anything. It is an SCH-i545 with the latest PhoenixROM.
When I turn it on, it briefly shows 'Samsung Galaxy S4', then that disappears and left with a blank black screen from which I can't reboot or shut off without taking out the battery. If I try download mode, I get the warning screen but it goes black before I can hit VolUp to continue. If i try recovery, I see the blue recovery starting text but then the screen goes black. Also, if I plug in the charging cable with battery out, then insert the battery, it won't turn on.
My phone did this. All efforts to get it to boot were futile. Samsung, and then dark. And then just never booted again. Even trying to charge it, the charging screen never showed. Not a vibrate or anything, I even shined a flashlight on the LCD to see if maybe the backlight just died, and again nothing. That was 4 months ago, and today for ****s and giggles I plugged it into my Anker battery to charge and the charging screen came up!!!!! I let it fully charge and then booted the phone and it works again!!!!
Now I just have to fix the screwup I did a long time ago with the radio, I did the "Golden Backup" improperly and my radio quit working on CDMA altogether. No documentation to be found, even Samsung upper tier support has no idea how to resolve it or even what the hell I'm talking about. I'm guessing there is no support but maybe flashing a modem will resolve it.
Graymayre said:
My phone did this. All efforts to get it to boot were futile. Samsung, and then dark. And then just never booted again. Even trying to charge it, the charging screen never showed. Not a vibrate or anything, I even shined a flashlight on the LCD to see if maybe the backlight just died, and again nothing. That was 4 months ago, and today for ****s and giggles I plugged it into my Anker battery to charge and the charging screen came up!!!!! I let it fully charge and then booted the phone and it works again!!!!
Now I just have to fix the screwup I did a long time ago with the radio, I did the "Golden Backup" improperly and my radio quit working on CDMA altogether. No documentation to be found, even Samsung upper tier support has no idea how to resolve it or even what the hell I'm talking about. I'm guessing there is no support but maybe flashing a modem will resolve it.
Click to expand...
Click to collapse
Same radio issue, I get no signal on the phone, just a circle with a diagonal line inside
This is sick
If you can get it to boot into fastboot, just reflash the full OEM rom which should include the modem image