Background: I had my completely stock Nexus 5 on the charger for around an hour. When it got near 100%, it locked up for about 5 seconds and powered off. It wouldn't charge or power on again until 2 days later where it would power up but not charge. It could go to the bootloader/recovery but it would still shut down. The charger used won't charge anything anymore, it may have been a power surge that messed it up.
I replaced the battery and the system is still unable to maintain power but recovery and the bootloader are stable (just formatted the cache and the phone did not power off, took around 15 minutes). Now it won't power up again.
Any idea what the issue could be? Could it be corrupted data?
First, try another cable and charger.
Also, make sure you have enough juice on the device first, reflash stock firmware with fastboot and see if the issue remains.
If you successfully flash your stock firmware and use another known working cable and charger and it's the same.... Then unfortunately it could be a hardware issue.
Thanks for the reply.
Unfortunately, that didn't bring my N5 back to life. I'm think a circuit may be fried on the motherboard but I don't have a real way of judging that at the moment.
Any chance you might be able to guess what the hardware issue could be? I'm mainly trying to save the data on my phone and I'm not against taking the phone apart to do that.
Update: I took the phone to a Sprint store and a technician looked at it. When the tech plugged it into the charger, the phone LED was flashing red with no charging screen. It eventually booted up and shut down. Later that day, I could see my notifications (Pushbullet is a wonderful app) and noticed the phone stayed on consistently. He said everything was fine and their formal report didn't mention any sort of damage to the phone that they could find. Later that same day, it died again. Today, I decided to completely wipe and load 5.1 to the phone. It stayed powered on through the whole flashing process (bootloader unlock and individual partition flashes) but shut off during "optimizing apps". Considering it powered off in the system, I'm thinking the issue is with the RAM or the CPU possibly being fried due to a power spike while on the charger. It seems like it only happens during heavy operations.
Something hardware it seems. Not sure what, but if a component on the mb is bad then it is a replacement.
I like the title though, doubt anyone has a device that stays charged while in system. Sorry about your phone, but made me chuckle. I really can't think of a better way to describe it, not trying to pick on you.
Related
Hey all,
My wife and I both have Nexus S phones bought together sometime in Jan. Both phones are running stock Android 2.3.2, no rooting or anything done yet.
Right now her phone is behaving weirdly, while mine is perfectly normal. I suspect that her battery is messed up somehow, but I can't figure out what to do.
For the last day or so, when her phone hits <15% battery, the low battery warning pop-up appears.. and just keeps reappearing. No matter how many times the pop-up is acknowledged, the pop-up just does *not* go away until we connect the phone to a charger. Sort of an aggressive warning
This means that the phone won't let itself be put to sleep, keep the screen turned off or anything -- unless we connect the phone to a charger. I feel as though the battery is charging slowly, but I can't be sure.
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display. This behavior goes away if the phone is connected to the charger. My phone does not show this behaviour - display goes off the moment I press the power button, regardless of charging status.
Any thoughts?
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S? We removed the battery and put it back in (which is basically a soft reset apparently) and now it seems as though the battery has lost calibration or something. Have not done a hard reset yet -- should I go ahead and try that too?
Thoughts/help much appreciated. This is very worrisome!
satishev said:
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display.
Click to expand...
Click to collapse
Sounds like it has a glitch in the software. Try wiping everything. Go into settings, unmount the USB memory, erase the USB memory, then do a factory reset. That will reload the firmware back into active memory for the phone and wipe anything out of the USB memory that might be causing this issue. I usually do a factory reset with a new phone after I play with it for a while anyway, and it doesn't hurt the phone at all. You simply lose your texts, contacts, photos, etc. Just copy or backup anything you need to keep and wipe it clean.
If that doesn't fix it, then you need to get it replaced.
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S?
Click to expand...
Click to collapse
Once you do a factory reset, turn off the phone and fully charge it using the supplied AC charger (don't use the computer port to charge), unplug it and wait a minute then re-connect the charger again for another hour, unplug it, turn on the phone and start using it.
Let us know if the reset fixes the issue.
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
satishev said:
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
Click to expand...
Click to collapse
Well a factory reset is a lot easier and faster than a return/exchange and accomplishes the same thing.
A new symptom has just surfaced -- right now, when my wife tries to lock the phone, it locks the screen but won't switch off the display. No matter how many times the phone is restarted, or the lock button is pressed, the display never actually goes off (timeout has been varied from 15 secs to 1 minute, to no avail). Phone was completely charged as of today morning, so its not popping any low battery warnings.. just not switching off display.
It definitely seems like a battery/software glitch of some kind. We've not done the factory reset yet (she's at work, and this just started happening). Just thought I'd keep the thread updated.
I went ahead and factory reset the phone, as well as manually installed the 2.3.3 update. Figured between the system reset and the update, something should get fixed
Restoring settings was relatively painless (love how everything just gets set up the way it was due to backing up everything with Google). We have the phone charging now (overnight), will update again tomorrow morning once its full charged and my wife is using it as normal.
Fixed?
Hey @satishev
I have the exact same problem, did yours get fixed?
thanks
Hey crobbie, sorry I forgot to update the thread.
After factory reset and update to 2.3.3, the phone has been working normally (so far). All issues related to battery/display are gone! Looks like it was some kind of software glitch that was causing it to read battery state incorrectly (Another symptom I had noticed was that on alarm/dock mode it would keep flashing a charging icon, despite no charger being connected). Initially after reset, the battery usage was acting wonky, but that worked itself out and everything is showing what I expect.
If interested, a blog post summarizing process/ZIPs for all updates to date can be found here.
Thanks, bfksc for all your help
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.
I do apologize for filling up this forum with yet another "Did I brick..." question, but I'm really at my wits end and need some guidance.
This morning I decided to update my kernel to ElementalX 5.0. Prior to this I was using the 4.5b kernel and had no issues, but I wanted to move to the stable release and hadn't had any issues in the past. I have ViperXL 3.2.3 installed on this as well. I have yet to apply S-Off as I haven't had any real issues at the time and wanted to wait for the weekend when I had enough time to dedicate to the process (life is hectic blah blah blah).
I downloaded and installed the 5.0 kernel as I had previously, making a nandroid prior to the install. I decided to try some of the overclocks/undervolts that everyone raves about so during the install I chose the 2.1GHz overclock (because I can always step it down if it gets flaky, right?) as well as overclocking the GPU and undervolting to 850. I also went with zRAM as usual. After this was done and the phone rebooted twice (a common occurrence) I was brought to the window where Android was optimizing my apps. After that completed, I was brought to my home screen where I saw the clock and everything else. It looked like yet another successful install....and then the phone went black. Since then I have been unable to get it to boot. Pressing and holding the Power + Volume Down does nothing. I've held it for over a minute and no blinking capacitive lights or anything. The charge light does not come on when it's plugged in and, while my computer first tried to install the drivers when I plugged it in, I received an error saying the device was unplugged and no matter what I do I cannot get it to try to install again. Device Manager doesn't show it as being plugged in and it no longer comes up in Windows Explorer. Prior to the install the batter was at 83% and I have had it plugged in now for almost 20 minutes and still the charge light has not illuminated.
I never thought it would be possible to kill this phone, but I think I successfully did. Does anyone have any insight, suggestions, or helpful pointers. Yes, I know this was a risk I took doing this and I am not going to bemoan the fact that I did this to myself...I just really want to know if it's possible to resurrect this phone.
HTC OneXL
Hboot 1.14
S-On
Leave it plugged in to a wall charger for a while
a box of kittens said:
Leave it plugged in to a wall charger for a while
Click to expand...
Click to collapse
So do that as opposed to plugging it into a PC? Asking since I don't have a cube with me at the moment and will need to run home at lunch to grab one if the case.
Yes into the wall charger...and hold power for thirty seconds does anything light up?
As for my own experience I have had trouble getting my phone to reboot or get into the bootloader when it plugged in. The charger seems to keep the phone turned on while it charging. Try unplugging it from the charger and try again.
Sent from Xparent Red using my Venomized Evita
This happened to me too, but I got it to reboot by holding down the power button. What's happened is that the phone thinks the battery is dead. When it comes back up, you'll probably show 1% charge. Somehow or another, the battery monitor data gets corrupted. I think it's related to the general battery data bug that's plagued this phone from the beginning.
Your phone clearly can't handle 2.1 and undervolting (I increased my voltage to run 2.1). Bump up the voltage when you get it back up.
Pdj7969 said:
So do that as opposed to plugging it into a PC?
Click to expand...
Click to collapse
Definitely. The wall charger is much faster than USB from a computer.
IT LIVES!!!!
I ran home and grabbed my wall charger and brought it back to work. I plugged the phone into the charger and let it sit. After about 2 minutes, the charging LED lit up. I gave it about 15 minutes and then tried to power it on but it was no go, turning off the charging light and not doing anything, so I let it charge for another 30. When I thought it should be good and ready, I decided to go ahead and attempt to boot into the bootloader, as my fear was that the undervolt and massive overclock would most likely bring me back to square one. Holding down Power and Volume Down, I said a silent prayer to the device gods.....and the capacitive buttons began flashing.
Once I got into the bootloader, I quickly booted into TWRP, cleared cache and Dalvik, and then reinstalled ElementalX 5, this time choosing the stock voltage and not overclocking the GPU. I kept the overclock at 2.1 because, like I said before, if the phone is flaky, I can dial back the speed and restore functionality. I like the idea of having the option to go balls-to-the-walls if I WANT to, but not necessarily will I go that route.
After the lengthy kernel install and the normal 2 boots, I was met with my beautiful Viper lock screen. Thank you guys so much for the insight into needing to charge from the wall instead of the PC. I never imagined the computer would refuse provide a charge to it if it was completely dead (or the phone thought it was completely dead...once I got into TWRP it stated battery life was 86%). I am calibrating the battery now as I just realized it hasn't been done in probably 6 ROM installs.....derp!
Since this issue is resolved now, the thread can be closed. Thanks again, all!
Pdj7969 said:
I never imagined the computer would refuse provide a charge to it if it was completely dead
Click to expand...
Click to collapse
USB charging might still work, it would just take a lot longer. Some folks have had to plug there wall charger for hours or overnight, even on the wall charger, to get their phone booted again. So the wall charger is just better since its faster.
redpoint73 said:
USB charging might still work, it would just take a lot longer. Some folks have had to plug there wall charger for hours or overnight, even on the wall charger, to get their phone booted again. So the wall charger is just better since its faster.
Click to expand...
Click to collapse
And it may have, but the thing I noticed in the 90 or so minutes it was connected to my work PC was that the phone was the coldest it had ever been since I got it, meaning that the usual warmth caused by charging was not present at all. I did notice in Device Manager that when I plugged in the phone, it would register the phone as an HID (Human Input Device) and then it would disappear, only to reappear again and then disappear once more. This would happen non-stop until I disconnected it, so perhaps that's why it didn't charge at all during the time it was plugged into the computer? In any event, good ol' wall current supplied the juice necessary to bring this sucker back to life, so I'll file this info in my memory banks and make sure I have a wall charger at my desk from now on.
Hello,
I went out last Friday and came home late. My phone is out of battery and dead. I plugged it in and woke up the next day with a dead phone. Apparently, there is a bug with the OPO. If the battery is too low, it won't even charge after you plug it in for charging. I have tried all tricks and even contact the OPO Tech Support Team. This thread describes how horrible they are:
http://forum.xda-developers.com/oneplus-one/general/tech-support-onepluse-one-horrible-t3084022
I am at my wit's end. I have tried all the the tricks. This is a thread that I found that seems to have the same problem as I have.
http://forum.xda-developers.com/oneplus-one/help/oneplusone-phone-dead-t3079256
The only choice I have left is to open the phone, disconnect the battery connection and reconnection it again. Hoping it will recharge. However, there is a warranty sticker and I don't want OPO to deny my warranty. I am not new to Android and I have fixed phones before. I also think of buying a new OPO battery and switch it with the factory one. Since the new battery will be charged, I think that will work in fixing it. But, doing that is much more complicate and it requires me to remove more components. If you have a good working solution for my problem, please help.
NOTE: please don't ask me to check my charger or use a different one. I check it 1000 times already. The original charger works, the cable works. I use different chargers and cables. Same result.
Thank you for your help.
Have you rooted and unlocked? I had the same problem when I got mine at first. It would show charging but never fully charge. 73% was all it would do. So after rooting and flashing a custom kernel the problem went away. Now I can go back to stock and the problem has never comeback. Maybe just a small software glitch or something. I'm just happy it's gone!
brandonhatty said:
Have you rooted and unlocked? I had the same problem when I got mine at first. It would show charging but never fully charge. 73% was all it would do. So after rooting and flashing a custom kernel the problem went away. Now I can go back to stock and the problem has never comeback. Maybe just a small software glitch or something. I'm just happy it's gone!
Click to expand...
Click to collapse
The phone is unlocked and rooted. The issue is not fully charged or not. The issue here is the phone does not charge after the battery die. The phone is dead because I let the battery run to 0. When I plug it to recharge, the low battery screen does not even come up. The phone is dead and refuse to recharge. There is no issue with the charger or the charging cable. I have checked it several time already. I am very frustrated with OPO Tech Support right now.
I see. Only other thing I can think of is try holding the power button for 60 seconds while it's plugged in. That does suck man.
I had similar issue, my conclusion is the bootloader charging function is broken.
Basically I would start the charging, it would charge for about 10 seconds or so, and then stop. I thought my battery was dead.
I couldnt boot the os as wasnt enough charge.
So eventually I just kept repeating the process, 10 seconds charge at a time, and eventually had enough juice to boot android and after that point it charged to full ok.
Never had this issue on any of my samsung phones.
Also to point out when it went dead it was plugged into my pc usb at the time with twrp loaded.
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.