I had to do a hard reset (volume- power) just to get the phone out of the loop. The cause? Charging the phone! The battery drained, I plugged it in, and I walked away from it. I come in about a half hour later, and I see the phone is on, constantly rebooting at the LG screen, which means it booted itself somehow. I pick it up, and it's burning hot.
So now I'm royally pissed, and I think it's going back tomorrow. I can put up with the battery life, because there are ways to manage that. But this is the last straw, I'm afraid.
Has anyone else had this happen while doing a simple charge (wall charger)?
When I unlocked mine it did the same thing. I ended up having to use the LG Mobile tool to "update" it and reset the settings to factory. It erased all the programs I had but maintained the rooted unlocked condition it was in. I have had this on several android phones. Never more than once.
Mine has worked perfectly since with an average of 11 hours of battery life per charge with pretty decent use.
Sent from my LG-P999 using XDA App
same here!!
Related
I really don't know if this is possible or not.... but I might need to get some new corduroys after a case of the brown adrenalin with my new sensation.
Got it Friday as could see progress on the rooting and sure enough Revolution came up with the goods same day. Rooted it Saturday.
Fully charged it, switched it off and went back to the HD2 - flip case and car kit arriving today. Really don't wanna damage my new boy toy by pocketing it with car keys etc.
Stone me though I thought I bricked it. Wouldn't switch on this morning - just a dark flicker of the screen. Sweat pouring off my forehead. Never bricked a device and flashed my HD2 & TP2 a million times and my £450 unlocked handset is 3 days old and dead..
Long and the short of it is plugged in the charger again and a few minutes later it powers up - 3% battery.
Is it possible it could drain switched off? Or should I blame the kids for messing with it and deduct my dry cleaning bill from their pocket-money?
After I rooted, I had to do a battery pull until I was able to turn my phone on again, although this doesn't really replicate what problem you had...
The battery does not drain if the phone is turned off.
Question is, was it definitely turned off?
Even if it wasn't, there's no way a full charge is going to drain overnight... Unless you had a Satnav running...
Sent from my HTC Sensation Z710e using XDA Premium App
You're right - it SHOULDN'T... I'd rebooted no problems several times after the rooting. Some OTA update came over and didn't install successfully though.
It'd be very odd (and a warranty issue, get ready to go into rooting reverse) but for now I'm inclined to just blame the kids. Unless anyone else has has similar experiences.
I guess time with it will tell.
EDIT: Apparently it's a known issue and has been fixed with the new CWM update! See: http://forum.xda-developers.com/showthread.php?t=1192300
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
EDIT: Good man. Thanks for the update. Better get onto that right away.
Yup.. that's the same experience... except I'm still on stock rom with tweaks.
What do you reckon - flash back to stock and see if it still happens? Really don't want it turning into permanent paperweight with an iffy bootloader for someone at warranty to find with their JTAG.
Morsolo said:
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
Click to expand...
Click to collapse
I've searched the forums and have not seen anything quite like my problem, so if I missed an important thread, I'm sorry.
Over the weekend, I plugged my Captivate (using a stock battery) into the official Samsung charger and overnight my roommate semi-dislodged the charger. When I woke up and grabbed my phone it only registered a few hours of charging yet still had almost full battery. Upon rebooting the phone, I was sent into a bootloop. Not at the ROM, not at the Kernel, not even at the bootloader. It goes so far as to show the white loading ring at the center of the screen which never moves. At one point, a thin pink line appears halfway through the screen as it shuts down and reboots, never making it any farther. If I plug the phone in, it will boot normally though it does not accurately report battery levels or charging.
Other oddities: after 5 minutes of a phone call, the phone hard crashes. Not FC's, but just goes black. Upon a reboot, I get stuck into the same boot loop. If I plug the phone into the wall charger without a battery, it will go into the turned-off charging animation and show a 100% charged battery. Furthermore, my other roommate has a brand new i9000 so I tried that battery (again, stock Samsung) and it continues in the same bootloop. I have tried flashing other ROMS and going back to stock, but that does not seem to help.
Other info: I was running OneCosmic's ICS 3.1 with no overclock and light undervolting at the time. It was perfectly stable for the few days until the charger dislodged. I am also out of warranty and am not eligible for a hardware upgrade so repairing my Captivate would be ideal. I also have a usb jig if that is of any use to this scenario.
Has anyone experienced anything remotely like this? If not, what debugging steps should I attempt?
What I would suggest is using one of the ODIN one clicks and flash back to stock
Sent from my SGH-I897 using xda premium
I've flashed back to Rogers 2.2 stock. Doesn't help. It actually made it harder for me to get the phone started though I have yet to make a phone call from it.
Have you had the phone for less than a year? if so call at&t(or rogers) and they'll replace it for you.
then try factory reset
then try using odin or rom manager to flash back to stock
When all else fails, flash to cm7. that will completely wipe everything and start from scratch.
if that STILL dost work.... than you can be sure that its a hardware problem :/ theres nothing you can do except replace and sell for for parts.. sorry
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Skoffer said:
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Click to expand...
Click to collapse
I have exactly the same problem, I did the reset of the battery stats and still not working.
Did you solve the problem?
thanks
Martin
Thanks to everyone for their suggestions, however, no amount of battery calibration could get it to work. Furthermore, a bad flash has made the situation even worse. Now Im bootlooping even when plugged in and when unplugged my jig is of no help. I have declared my Captivate dead.
Best of luck toominds, if you get it to work, let me know. I'd love to have a spare phone sitting around.
Hi guys,
I recently ran into this problem after I woke one morning to my alarm clock blaring for about half an hour, the phone was pretty hot but not unbearably hot. I took out the battery and left the phone to cool down til trying to boot again, when I did the phone booted fine but it soon shut off again 5-10 seconds into loading into android. I assumed the heat knocked the charge out of the battery / something went wrong with the reading of the battery (as it read like 85%) so I just plugged it into the charger and left til it said it was full. It doesn't shut off by itself and works fine while on the charger regardless. But as soon as I unplug the phone dies within a few seconds. So I turned off the phone and let it charge overnight, woke again to the same issue and the battery reading 85% again. Before I booted back up though I tried the "Wipe Battery Stats" thing in CWM hoping that maybe it would fix it after I fully charged but it made no difference. Also I found that the phone is able to run off the charger when I severely underclock it to 250MHz but obviously it's too damn slow for every day use at that speed. As soon as I clocked it up to 480MHz it had the same issue again. I forgot to mention I was rooted with CWM, unlocked bootloader and on stock rom. After this I decided to revert to my pre-root back up rom from CWM and I still had the same issue.
The final thing that seems to make it work is removing the sim, I tried booting this morning without sim and the phone functions flawlessly even while under a heavy stress test without turning off. So I tried inserting another sim, this one not active. Issues start up again...
Any Ideas guys? Seems to me like if the phone is pulling "too much power" the phone auto shuts itself off. But then the SIM thing perplexes me, not really sure how it all affects.
Lastly, do you think I can still claim on my warranty? I've had this phone for just under a month and it's still in perfect condition... I really don't want to switch back to my chopped and screwed Motorola Flipout. But atleast that thing could handle the overheating pretty damn well. Also I didn't get this on contract I bought it outright from a reseller as a prepaid phone.
In the Netherlands, the warranty for a phone battery is set to six months by law, just contact HTC, and find out.
Sent from my HTC ChaCha with CM9 using XDA app.
Hello All!
Three days ago I updated my GS3 to JB 4.1.1. I also ODIN'd TWRP onto my phone as a recovery and loaded SuperSU with an unlocked bootloader onto my phone along with BusyBox. I fell in love with my phone again as JB ran smoothly and I was even able to use Wallet Installer to get Google Wallet onto my phone. However, tonight, my phone seemed to experience a case of Sudden Death Syndrome. A common issue found by googling why my phone's failure to respond to boot commands and power commands.
It will not respond to attempts to boot into ODIN mode, my TWRP recovery and the only sign of life on my phone is a solid red LCD that lights up only if I remove the battery and leave the device plugged into a wall charger. Once I try to reinsert the battery, however, the LCD goes away and the phone once again turns into a coffee coaster. It's taking a lot of strength not to throw it against the wall. (I picked the worst week to quit smoking.)
I don't believe I hardbricked the device because three hours ago at the time of this post, I went to sleep and the phone was working and I was able to send and receive messages. I believe that rooting my phone actually made it even more stable than normal. I just can't believe my phone could just suddenly die. Could it be another case of Sudden Death Syndrome? (Corrupted NAND?) I bought this phone in August and many cases of SDS for the GSIII seem to occur within 150-200 days of activation, which would put me in that window. If I answered my own questions, please feel free to tell me. I'm just trying to explore all options as an exasperated user dealing with what seems frustration after frustration and the one release I have from that stress just **** a brick.
I am covered by Asurion Insurance (and if the crack on my screen will not be enough I plan on running it over with my car for good measure to get my money's worth) but I really do not want to have to file an insurance claim unless it is absolutely necessary.
Phone died just last night 12/29/12. The battery was running down, then beeped once like a warning to charge it. Plugged into the charger and no light whatsoever! The battery icon would come on for a second and then nothing. Left it on the charger over night. Nothing. No red charging light, no boot. Pulled the battery and re-plugged into charger. Same charging icon on screen but nothing else. Tried every combination of removing battery, sim card, memory card, and plugging it in to the charger and still won't boot. Tried a different charger and also my laptop. Nothing. The S3 is a USA Verizon variant. 16gb. Black. I guess it's off to Verizon this morning to get a new phone. Phone is only 45 days old!!!
You could try leaving it on the charger for a couple hours then booting into recovery and reflashing your rom. I've seen a couple instances reported on xda where the battery simply just gave up below 23% and refused to turn back on.
Edit: example, not even a couple weeks old...
http://forum.xda-developers.com/showthread.php?t=2056539
Sent from my SCH-I535 using xda app-developers app
If it is a case of "sds" Samsung will replace the board for free.
Ryno77 said:
If it is a case of "sds" Samsung will replace the board for free.
Click to expand...
Click to collapse
Only reports of SDS in the 150-200 day time frame that I saw was with the International Version and it is completely different motherboard.
What do you kids do to your phone? How old are you? I'm going to start a survey. Age please?
Sent from my SCH-I535 using Tapatalk 2
Update: Brought the S3 into Verizon. They pulled the battery (Like I did a few times!) and somehow got it working again!! FM ! Phone reboots and turns off and then back on. BUT..... if you turn it completely OFF and plug it in to charge then the same as I mentioned happens again. STRANGE. The only way to get it to reboot is to pull the battery and keep it out for about 30 seconds. Put the battery back in and it'll reboot again!!!! Is it me or is this a strange quirk???? The previous times I pulled the battery it was out then back in. This time I took it out, waited 30 seconds and VOILA! It works. Thought you might like an update. Verizon S3 bought on 11/17/12. Rooted and not oc/uc'd. Using Clean Rom 5.5.1
h
prdog1 said:
Only reports of SDS in the 150-200 day time frame that I saw was with the International Version and it is completely different motherboard.
Click to expand...
Click to collapse
That's good news..thanks for the correction.
I've had this phone 3 years and it worked well. It's an unlocked ATT phone so no OTA updates other than the standard app updates. It's on Lollipop 5.1. Been working perfectly fine until yesterday, I was watching the CBS app, when the phone rebooted. Now it's stuck on a boot loop and initally went to optimizing apps which it rarely finishes but the times it does, the phone just powers off. It then got into another loop later last night where it'd get to the Kyocera logo then reboot over and over. I let it do that until the battery died 2.5 hours later. Then I kept attempting to boot until the batter was entirely drained to the point it wouldn't attempt to power up any more.(battery is not removable on this model). I've now charged it up, trying to enter recovery mode with power+volume down. That doesn't seem to register. Tried volume up+volume down+power with no effect. Now after charging, it will do the reboot loop mentioned earlier to the Kyocera logo. If I plug it into a charger, it will go to the optimizing apps portion and repeat the above. At the optimizing apps screen, if I unplug the charger, the phone powers off immediately. It appears to be holding a charge according to the charge indicator and the fact that I can try to boot over and over unplugged. Any suggestions? Phone wasn't dropped or damaged in anyway. Very weird what could have happened.
An update: Phone finally got past the "optimizing app" phase last night sitting on the charger. Out of no where the phone booted completely. However, it only works while plugged in. If I remove the charging cord, the phone shuts down after about 2 seconds. Booting without charging cord results in the same boot loop. I've considered the battery has failed however when plugging in the charger, battery shows 100% and it will decrease appropriately over time. I'm thinking there must be a hardware issues at this point. Somewhwere in the charging/power circuit. Any other suggestions?
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
djhurt1 said:
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
Click to expand...
Click to collapse
I have the same exact problem. It started the crazy booting process in my pocket, and I did all the same things you did. Factory reset didn't correct the problem, so I'm think the battery has had a stroke. Sine your problem and my problem are very close to the same time frame, our phones are also probably about the same age, and its a quality control issue. Not bad quality control, just that these batteries were designed to last X number of months or cycles, and probably they died. Too bad, because my E6560 is the very best cell phone I have ever owned. Built like a tank and thank God for that.