Database Info

Phone is dead. Nothing works :(

Hi all, laid down to take a nap and woke up to a dead Thunderbolt. I can't get it to turn on, no indication light is shown when it is connected to the charger, and I get an unknown device when plugging into USB and trying to ADB reboot.
Everything was fine right before I took a nap and now nothing works . I've never flashed leaked radios and the latest ROM I was running was CM7 RC1.2 with the stock kernel. Not really sure what else to do at this point except weep.

try pulling out the battery?

Tried several battery pulls and none seemed to make a difference. My phone decided to come alive again just a few minutes ago on its own. Now I'm really perplexed by what happened and worried this may happen again in the future.

Uber-weird...

I read this post last night, then woke up this morning with the same symptoms. Plugged it into charger and the indicator light just blinked once and then nothing. I guess this is where some might panic but just let it alone, it doesn't have enough juice to power up yet.
Sent from my ADR6400L using XDA App

yeah i have seen that before...sometimes you just gotta leave it plugged in to charge for a little before you can boot up the phone

Agreed let it charge a while or go get a new battery and try it
Sent from my ADR6400L using XDA Premium App

00negative said:
Agreed let it charge a while or go get a new battery and try it
Click to expand...
Click to collapse
Yesterday when this happened, I was at around 50% battery life. If others are experiencing the same symptoms then we should try to get to the bottom of this somehow. Not really sure what kind of diagnostics or feedback I could submit because other than this freak accident my phone has been running perfectly.

raphytaffy said:
Yesterday when this happened, I was at around 50% battery life. If others are experiencing the same symptoms then we should try to get to the bottom of this somehow. Not really sure what kind of diagnostics or feedback I could submit because other than this freak accident my phone has been running perfectly.
Click to expand...
Click to collapse
When people had issues like this before for some reason they experienced battery drain and didn't realize the battery was really dead. If its that it could be a bad app, rom issue, or kernel issue.
If is battery after you fully charge I would wipe battery stats then maybe run a rom of your chosing without unnecessary mods or apps to see if it still happens
Sent from my ADR6400L using XDA Premium App

I have had this happen to me twice in the past few weeks. Each time I just left it alone, charging, and tried powering on after several minutes (10+). I would then fully charge and calibrate the battery.

To OP .... i also had an issue like this and i ended up having to warranty replace it with VZW.
This one was already a replacement to a previous one, and within minutes of booting it up, it was experiencing 'reboot' problems. Verizon indicated i should wait for the update to fix the issue. I just left the phone plugged into the wall for the weekend (didnt even look at it), and Monday morning it was dead. I pulled battery.... let it sit unplugged, let it sit with pulled battery ... nothing would bring it to life.

is this a rooted phone?
If so, we can flash an alternate kernal to see if that is the problem. Usually powering off problems are related to the kernal in my experience with the TB.
IF NOT,
I would try wiping the device so there are no apps before returning to verizon for a refurbed.
It is not likely but possible you have a misbehaving app draining your batter like crazy.
Also, your phone might be doing something weird like closing system resources when it needs ram by accident thinking its an app or something. I've seen that happen before.

I have had this problem twice in the last three days. The two days it happened, I woke up to a dead phone while still plugged in. Unplugged it and put it back on the charger and it eventually turned on. I use it as my alarm clock, so its getting frustrating having to rush to get ready in the morning because my phone dies when on the charger. It is rooted with bamf 3.0, but I haven't done anything to it in months just because it ran so good. I am going to check my app stats to see what I may have downloaded.

Annoying battery issue

Hi!
When my phone (a normal secretion) shows 9% left of battery, it just dies, and wont boot before it has charged in 15-20 minutes.
It happens on both Anker og EVO 3D battery. I'm currently running the newest ARHD with faux kernel.
I have deleted batterystats when its fully charged and currentwidget shows 0 ma.
Any advises? Thanks!

Well I can tell you that deleting battery stats does nothing. Other than that, no idea.

Hey man I just made a similar thread. I'm using the latest ARHD Rom as well and was having the same issue regardless of which kernel I used. Mine will die at any battery percentage randomly and refuse to boot for awhile. Then ill get a successful boot and it will be done for awhile butthen start happening again. Battery percentage will be jumping everywhere. The only time its fine is when the charger is plugged in.
Sorry for typos on my phone now.

ImHuge07 said:
Hey man I just made a similar thread. I'm using the latest ARHD Rom as well and was having the same issue regardless of which kernel I used. Mine will die at any battery percentage randomly and refuse to boot for awhile. Then ill get a successful boot and it will be done for awhile butthen start happening again. Battery percentage will be jumping everywhere. The only time its fine is when the charger is plugged in.
Sorry for typos on my phone now.
Click to expand...
Click to collapse
Tnx for answer. I had the same issue with random reboots on the Anker, bit not with the EVO 3D battery, just at that 9%. Im so satisfied with the rom/kernel, so i hate to try another rom.
Im also typing from my phone, its nice!

[Q] Roms and battery life - Unable to start phone

Hi,
I have recently tried out a few ROMs with my Nexus S to try to get better battery life. I tried CodeName Android and then figured I would try Slim ICS afterwards. I completely wiped everything and installed Slim ICS.
I have observed the following:
- Battery was ~40% when I installed Slim ICS
- I used it until the battery depleted
- Plugged phone into the wall charger
- Started the phone shortly afterwards (~25 minutes) and it says battery is 100% and then the phone randomly shut off
- Phone has been plugged into the wall charger and when I try to start it now sometimes it boots completely and then shuts off. Other times it just shuts off before it finishes booting up. The few times it does fully boot up, it says the battery is 100%
I've read through many postings about calibration but at this point I am not even able to fully turn on the phone even when its plugged into the wall.
Is this expected or is something else going on? I've never seen anything like this when I had the stock ICS. Why would erroneously report 100% but then not even let me fully turn on the phone? Thanks!

timetosave said:
Hi,
I have recently tried out a few ROMs with my Nexus S to try to get better battery life. I tried CodeName Android and then figured I would try Slim ICS afterwards. I completely wiped everything and installed Slim ICS.
I have observed the following:
- Battery was ~40% when I installed Slim ICS
- I used it until the battery depleted
- Plugged phone into the wall charger
- Started the phone shortly afterwards (~25 minutes) and it says battery is 100% and then the phone randomly shut off
- Phone has been plugged into the wall charger and when I try to start it now sometimes it boots completely and then shuts off. Other times it just shuts off before it finishes booting up. The few times it does fully boot up, it says the battery is 100%
I've read through many postings about calibration but at this point I am not even able to fully turn on the phone even when its plugged into the wall.
Is this expected or is something else going on? I've never seen anything like this when I had the stock ICS. Why would erroneously report 100% but then not even let me fully turn on the phone? Thanks!
Click to expand...
Click to collapse
Maybe a bad battery?
Sent from my Nexus S 4G using Xparent Cyan Tapatalk 2

Battery is fine. I ended up letting it charge a few hours and it now fully boots up and battery is almost fully charged now.
Whats strange is at times, when the battery was close to empty, when turned off and plugged into the wall, it showed the battery as being completely charged so I don't think it was charging. I had never observed this behavior with the stock ICS.

timetosave said:
Battery is fine. I ended up letting it charge a few hours and it now fully boots up and battery is almost fully charged now.
Whats strange is at times, when the battery was close to empty, when turned off and plugged into the wall, it showed the battery as being completely charged so I don't think it was charging. I had never observed this behavior with the stock ICS.
Click to expand...
Click to collapse
If it happens again I would suggest taking it to a sprint repair
Sent from my Nexus S 4G using Xparent Cyan Tapatalk 2

same problem
Even I have faced the same problem whenever I reboot keeping my pfone charging,
This is very normal,
just let the battery drain completely and next time charge it till 100% it will work perfectly,
It happens with me whenever I install new rom.
basically the battery indicator shows incorrect status also battery will drain very quickly later but once you finish installation just let your phone charge for 3 hours . Problem will get solved

saurabhkubadia said:
Even I have faced the same problem whenever I reboot keeping my pfone charging,
This is very normal,
just let the battery drain completely and next time charge it till 100% it will work perfectly,
It happens with me whenever I install new rom.
basically the battery indicator shows incorrect status also battery will drain very quickly later but once you finish installation just let your phone charge for 3 hours . Problem will get solved
Click to expand...
Click to collapse
Also, you could try clearing the battery stats in clockwork mod recovery
Sent from my Nexus S 4G using Xparent Cyan Tapatalk 2

Thanks. So it sounds like its more of a generic issue with ROMS in general as I never observed this before putting on a custom ROM.

[Q] CM 10.2 D2ATT problem please help

Cannot post in appropriate category yet so I have to post here and hope someone can help. I clean flashed this rom the other day (did everything properly), and the issue I keep having is that now my battery won't charge, and battery drain is horrendous (about 3 hours from 100 to 0). If my phone is off and plugged in, charging does not occur after 5%. After my phone dies it is almost impossible to get it charged to 100% again. Even plugged in it stays alive at 0% and does not charge. I have rebooted the phone on and off the charger (which was suggested in the forum) and that did not help. I really like this rom other than that, and even if I wanted to flash a different one I can't with 0-5% battery left. Any help would be appreciated. Thanks!

RE:
Did you try replacing the battery with either OEM replacement or aftermarket equivalent? It's possible the battery may be bad, yes it happens.

android_geek_0507 said:
Did you try replacing the battery with either OEM replacement or aftermarket equivalent? It's possible the battery may be bad, yes it happens.
Click to expand...
Click to collapse
Yes I did. I Used my GF's battery (also gs3) to see if it would charge as well. It did not. It has something to do with this rom. My phone has been dead for 2 days now and will not charge. Anyone have any other suggestions?

To be more specific: Several people on this rom have noticed that if you reboot on the charger it causes a wakelock that does not go away. It is then suggested to reboot off the charger and that will make the wakelock go away. It seems like regardless of what I do, the wakelock will not go away.

mjricha.isu said:
To be more specific: Severa, l people on this rom have noticed that if you reboot on the charger it causes a wakelock that does not go away. It is then suggested to reboot off the charger and that will make the wakelock go away. It seems like regardless of what I do, the wakelock will not go away.
Click to expand...
Click to collapse
That's very strange have you tried to Odin back to stock and start from scratch by keeping the phone charging via USB.
I did some checking around and I personally haven't found another solution to this.

My opo doesn't seems to full charging

Hi guys,
I have an issue since i updated to 33R.
When i charge it, it stuck at 99% for a long long time.
Ι have try to charging it powered off or not, i have try differents cables or chargers but nothing change.
I have install 33R with full wipes, stock kernel, just rooted.
Any idea or i need a fresh installation???
Thanks,
Ilias.

eliashadow said:
Hi guys,
I have an issue since i updated to 33R.
When i charge it, it stuck at 99% for a long long time.
Ι have try to charging it powered off or not, i have try differents cables or chargers but nothing change.
I have install 33R with full wipes, stock kernel, just rooted.
Any idea or i need a fresh installation???
Thanks,
Ilias.
Click to expand...
Click to collapse
It shows never fully charged?
Does it happen with the stock charger + cable to?
I never noticed this, but I'm currently on crdroid + ak kernel... so the comparison is quite hard

Klobal said:
It shows never fully charged?
Does it happen with the stock charger + cable to?
I never noticed this, but I'm currently on crdroid + ak kernel... so the comparison is quite hard
Click to expand...
Click to collapse
It shows never fully charged... With stock charger/cable too.
I haven't this issue before update to the last firmware.
I supposed its full charging but its not show the correct %.
But i don't really know...

N/m

I went out of town on business last week and I took a charger that was for my old HTC M7 and I noticed that my One would only charge to about 98%. I also noticed that one morning when I woke up that my phone was at 85% which I thought was a little strange. I thought it was due to the charger when I got home my phone charged back to 100% with the stock charger. Maybe something is wrong with your stock charger.