Hi all, I have a Lenovo A1107 tablet running stock ICS. It began powering down when it reached <50% or so and gradually climbed the % scale to the point where now it is does it at 98% and while plugged in. I have searched for hours and tried few troubleshoots (cleaning up system resources such as apps, home screens etc..., factory reset, airplane mode) but no luck finding a fix.
This problem has become seriously annoying and I just can't seem to narrow down what the problem is. Does anyone have any ideas? Thanks much!
Well, after thinking about it more I realized that the problem seems to be that for some reason or other the system isn't registering the device getting charged, even though the battery indicator says it is charged (90%, 98%, or whatever). The reason it got progressively worse (first starting at @50%, then at 80% and so on) was because even though the battery was getting charged the system was being told that it hadn't. That is why eventually it would power down almost as soon as it turned on, just like it would if the battery were completely dead. The reason I know that is not completely dead and not the battery indicator that is in error is because I could boot into recovery mode and stay in that for well over an hour, despite the fact even that the device will not boot into recovery mode if it is <30% or whatever.
So, I guess the best question would be.......what part of the system communicates between it and the battery? The part that says "no/low power so shut down"?
All moot now as I just took the tablet back and got a different one. Thread closed.
Related
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.
Battery dead, not charging, stuck on "low battery screen", bootloops with forceboot
Hello people, this is my very first post on xda, even though I've been lurking around for about a year. The community has helped me a lot, I'd like to thank you all for that.
Back on topic though! My error seems to be very similar to the one here.
I was watching some YouTube, battery sitting on a respectable 85%, when it suddenly shut off. Not the usual "shutting down for low battery" kind of shutting down, it was istantaneous, more like the battery was unplugged from the phone. Which is clearly impossible. I tried to boot it using the power button to no avail. I connected it to the charger, and the "the battery is too low" screen popped up. I left it at that for about 45 minutes, then unplugged from the charger and tried to boot. No success. The battery didn't even charge; the charger should be is fully working.
So I tried leaving it plugged to the charger and force boot the phone via volume down and power button; it attempted to boot, but stopped midway through, bootlooping until I unplug it, at that point it shuts off again.
The loop goes like this: OnePlus white logo (normal when you boot), radioactive kernel loading, reboot and repeat. That happens, again, until I unplug it from the charger. Then it shuts off.
EDIT: If I try to get into bootloader instead (volume up + power), after about 8 seconds of me pressing the buttons the screen just shuts off and doesn't react to any more presses (even while plugged). If I unplug and replug it to the charger, I'm back to square one (low battery, please charge).
PC doesn't recognize it. It makes the "the battery is low" screen pop up, but nothing else.
Here's some phone information in case you need them.
Phone info:
Rom: NucleaRom 1.3 (+ Radioactive kernel which comes with it) got it from here
Xposed modules: Youtube Background Playback, AdAway
Root: Yes
Thanks in advance everyone.
I doubt it would be software related if it does it even when in bootloader. It could be the problem I had with my nexus 7 a few times. I needed to charge it like all day for it to even turn on. Either that or faulty phone/bad battery. I hope it's just dead
NUNsLAUGHTER92 said:
I doubt it would be software related if it does it even when in bootloader. It could be the problem I had with my nexus 7 a few times. I needed to charge it like all day for it to even turn on. Either that or faulty phone/bad battery. I hope it's just dead
Click to expand...
Click to collapse
Hello there, thanks for taking the time to reply. Yesterday I worked all day to try and make sense of the problem. I could have just bought another phone but I'm fairly attached to this one so I went deep.
I was fairly sure (like you) that it couldn't be a software problem, so I looked at the logic board of the phone; turns out (correct my poor technical wording) the bracket (connector?) for the battery on the logic board was coming off from the motherboard itself (the battery was indeed attached to the bracket, the bracket was just coming off of the board). What I did was just reposition the bracket and pushed it down with a bit of force on the board, then replugged the battery in the newly restored battery plug, and tried my luck. It booted! Back at its original 75%-ish.
My only guess would be that due to a fall the bracket got misplaced, but stayed close enough for it to still make contact and never actually shut down, until yesterday. That was... Quite an interesting ride.
Thanks for replying, it was indeed a "faulty phone", but I just couldn't leave it at that without trying
I'm glad it worked out for ya
Not work at all ...
My phone its show the logo on charging or low charge but its stuck for this for while full battary is empty... When I plagued in charger the same show charging logo with indicator but not charging its suck on that logo to .......then I charged the battary externally then put the battary try to open its show only a (powered by android log ) stuck on this ......I cant go any recovery modes ..fast boot mods... Only show this one or charging logo if battary low that logo to ... I try to get adb driver on my computer its also not show because of not get recovery modes ........
Any other idea to solve this
So I've read a billion threads, but none of them are quite the same as what is happening here. My friend handed me a Nexus 5 the other day, said he had dropped it and it wouldn't boot after that.
Sure enough, on battery power, it only went until just after the "Google" screen, and then powered off.
When plugged into power, it would boot into the (stock) OS, and then promptly die. This problem is not an issue with the hardware, with what I can see, as in fastboot / recovery mode, it will last until the battery dies out. (probably)
So, after trying a number of things, including unplugging the battery and reattaching it, I installed TWRP and CM 13. The issue still happens, but once more, in TWRP, it will remain alive.
Also, if the battery is at 100% when off and charging, I can boot it up with the charger plugged in, and once it shuts down, it then has somewhere around 95%, while only running for about a minute. While "charging."
I can't find any logical explanation for this. I don't think it's hardware, since it's fine up until it fully boots. At the same time, it couldn't be software, could it?
To whomever solves this, I will be eternally grateful.
Thanks.
I have a P900 that was left in a drawer for 2 or 3 years, never getting charged even once in all that time. Turning it on, I immediately realized something was wrong because it took forever to boot. The lock screen was so slow that the entire machine locked up for a few seconds, scrolling between pages on the launcher stuttered hard or locked up and everything else with the machine was generally the same. The web browser is unusable, even typing in a URL locks things up. The device is unusable.
So I thought the battery was obviously damaged, even charged at 100% it would be flat for sitting for maybe 2 hours with the screen off. I tried several cycles of charging to 100% then discharging and back up, but nothing seems to help. I don't have much money so I took at stab in the dark and got a cheap battery from ebay and it didn't help. I don't know if this battery is new, but it does seem to hold a charge like the device did when it was new but it's just still so slow that you can't use it.
However, one thing that I've noticed is that apps that don't touch the storage seem to work OK. I have a Spectrum TV app that once it starts up seems to be okay, but not great. Netflix seems to be okay as well after starting up. They both stutter a bit and rarely freeze. I don't know if this is relevant at all.
I'm at a loss of what else could be damaged or how to fix this. I'm in the process of cycling this new battery up and down, though I don't know if this would actually help. I just don't know how to diagnose this problem.
Okay, the problem was the battery, it just took a few hours of charging. I guess now that it can see it has a fully functioning battery that it's running as it should now. Android really should give you an error message about that instead of just slowing the whole thing down to a crawl, leaving you scratching your head.
This strange thing happened to me also.
I was given a tablet that was not in use couple of years. It takes about one hour on charger to start booting at all, I was thinking that it don't working at all.
Then it sits on Samsung Note Pro logo about 15 minutes, then logo changed to Samsung and it took about 15 more minutes to boot in home screen.
Then i realized that it's very slow and unresponsive, I charged it to full and reset, but it's remain the same, very sluggish.
Tried everything, reset it couple of times, flash rom with Odin, nothing helped.
After couple of charge-discharge cycles it starts to work like new!
I would never have thought that the battery could do that, but there it is.
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.