Good afternoon everybody,
First a short story. If it's not interesting, just skip this section:
In the last holiday I dropped my O+O into the swimming pool. After a couple of days drying it restarted. The simcard slot wasn't working anymore. But all the rest kept working fine. I noticed the battery was draining down faster. I had to recharge the phone every day. For that reason I bought at aliexpress a new one. The new battery worked. But to my surprise it lasted not more than 2 days until I head to recharge it. So I found my phone several times completely uncharged.
Some weeks later after the phone was once again completely uncharged it stopped charging. Even with 12 hours plugged to the power outlet the "The battery is too low" picture didn't disappear. I tried the power adapter from a S4, tried to charge it at a pc. Didn't change.
The compact data:
Phone isn't charging, shows always "The battery is too low".
Pressing the power-button resets the phone, the Oneplus logo appears. After about 10 seconds it resets again. (endless loop)
Trying to do a factory reset - not sure. Without power cable nothing happens, with cable plugged it resets every few seconds.
Can boot into fastboot mode
In fastboot mode the phone is not recognized at the pc (lsusb, dmesg)
adb devices doesn't list the device
Is there a chance at least to access the internal memory card? I would like to save my photos.
There could be some water damage on the motherboard. In that case you are probably screwed
If you have some technical skills you could disassemble the phone and see if there is still water inside. I'm not responsible for anything you do...
If only the usb-connector/flex is damaged then it's easy to replace.
I don't have any ideas about the internal memory whether it can be restored or no..
Related
Here's my little story. I dropped my N5 and cracked the screen. It worked, but I wanted it to be pretty again. So I bought a screen/case and proceeded to do the swap. I watched several videos, read guides, etc and followed them step-by-step. After it was done, I was surprised how smoothly everything went. I then went to power it up and got nothing. I checked all the cable connections, reseated them, and still got nothing. I put everything back with the cracked screen. Still nothing. I check the cables carefully, there are no cracks or breaks in them. I left it on the charger all night and the next day, checking periodically, still nothing. I checked the battery connector with a multimeter, and it was getting a reading off it, so the thing must be receiving power, right? Anyway, I gave up for a few days, busy with the rest of life.
I came back to it one day, plugged it into the charger and this time I got the red blinking light. I searched around, and that seems to indicate the battery had lost it's charge completely. Again I charged it overnight, still nothing. I got adventurous and removed the battery and tried powering it with just the power cable plugged in. This time it displayed the charge full battery/lightning icon. Success! I hit power and it starts to boot, displays the Google logo, then shut down after maybe five seconds. So, it must be getting power through the system from the USB port. The mainboard/cpu/screen works, it's able to start booting. It even boots to the bootloader, keys work there.
Again I turned to the problem being the battery. I picked up another, thinking perhaps mine had gone bad somehow even though I never had a bit of trouble out of it (about 1.5 years old). I played with it some more, with either battery inside, it doesn't do anything. Without a battery, it starts to boot but gives up. Hoping I could get something from the bootloader, I plugged it into my PC, but the USB port doesn't seem to provide enough juice to get it back to the bootloader with no battery.
Finally, during one of my tests, I plugged in the battery while it had the charging cable in. Then it popped up the battery charging animation. Exciting! It must be successfully charging, now. Previously, it didn't display anything when I charged it for many hours. Now it's been charging about six hours. The battery animation still shows it filling from the bottom, usually it would blink the animation from like halfway to the top, right? I hold the power button, and the battery animation disappears and it goes dead yet again. I run the same tests, battery in, battery out and get the same results. It boots when there's no battery and the charging cable in, nothing when the battery is in with or without the charging cable.
So, here I am stuck again. Any other ideas? Thanks.
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
I recently dropped my phone on the ground and the glass is now broken. But it worked normally for about 14 days. Then suddenly one day at work it shut down on its own. After that I wasn't able to start it. No reaction for any of the buttons, nor their combinations. Even when I plugged the charger in, no sign of life. I thought it's over.
Then the next day, I plugged the charger in and the screen with 0% battery appeared. So I left it charging, but when I came back to it (20 minutes) it was dead again. Not even the diode indicating it is charging. Again no response for the buttons, nothing. So I tried to disassemble it, disconnected everything. Put it together and viola! The screen indicating 0% battery was there again. I left it like that for a while, and when it was charged a little, I tried to start it. It started and normally worked. At least it seemed to, but after a while (1 - 3 minutes) while I was using it, it went to the dead phone again.
So I discovered, that when I disconnect the battery for a while and then connect it again, I am able to boot the phone. I was even able to do factory reset. I thought I got it and that it was some software fault. However after like 5 minutes (it downloaded all apps, logged to my google account, looked all ok) the screen shut down again and again the phone played dead.
Now I have the phone booted, and charging (almost 100% now). But I guess when I start using it again, it will again go to the dead mode (since it did it everytime after I used it a little, no specific action done, totally random).
I guess it has to be related to the broken glass. Maybe some water or humidity got through it and the phone is trying to save itself from damage by going to the dead mode. It's weird because sometimes (like now) the phone is OK when not used, normally chraging and not shutting down (now it's ON for about 40 minutes), but if it shuts down, it takes about 3 or 4 battery disconnect and connect again, before it boots to the main screen. Sometimes it just dies before the screen, sometimes it dies when I try to plug the charger in, really no idea what causes it.
How should I diagnose it? USB debugging and check the log when using it and when it dies? Or has anyone experienced this too? Or could the battery be damaged? Or can I somewhere set the phone to prevent from selfkilling actions? Today I will try my main board in my friends G Flex 2, to see if it's the board, or something else.
Error log from console before it shut down
mazlixek said:
I recently dropped my phone on the ground and the glass is now broken. But it worked normally for about 14 days. Then suddenly one day at work it shut down on its own. After that I wasn't able to start it. No reaction for any of the buttons, nor their combinations. Even when I plugged the charger in, no sign of life. I thought it's over.
Then the next day, I plugged the charger in and the screen with 0% battery appeared. So I left it charging, but when I came back to it (20 minutes) it was dead again. Not even the diode indicating it is charging. Again no response for the buttons, nothing. So I tried to disassemble it, disconnected everything. Put it together and viola! The screen indicating 0% battery was there again. I left it like that for a while, and when it was charged a little, I tried to start it. It started and normally worked. At least it seemed to, but after a while (1 - 3 minutes) while I was using it, it went to the dead phone again.
So I discovered, that when I disconnect the battery for a while and then connect it again, I am able to boot the phone. I was even able to do factory reset. I thought I got it and that it was some software fault. However after like 5 minutes (it downloaded all apps, logged to my google account, looked all ok) the screen shut down again and again the phone played dead.
Now I have the phone booted, and charging (almost 100% now). But I guess when I start using it again, it will again go to the dead mode (since it did it everytime after I used it a little, no specific action done, totally random).
I guess it has to be related to the broken glass. Maybe some water or humidity got through it and the phone is trying to save itself from damage by going to the dead mode. It's weird because sometimes (like now) the phone is OK when not used, normally chraging and not shutting down (now it's ON for about 40 minutes), but if it shuts down, it takes about 3 or 4 battery disconnect and connect again, before it boots to the main screen. Sometimes it just dies before the screen, sometimes it dies when I try to plug the charger in, really no idea what causes it.
How should I diagnose it? USB debugging and check the log when using it and when it dies? Or has anyone experienced this too? Or could the battery be damaged? Or can I somewhere set the phone to prevent from selfkilling actions? Today I will try my main board in my friends G Flex 2, to see if it's the board, or something else.
Click to expand...
Click to collapse
Adding the error log from console
OK so it was probably mother board fault, so I had to buy a new phone It is like 3 months, and I just yesterday accidentally poured some water on it, so i destroyed another one. It is still in warranty but I guess with water damage there is no warranty. Anyone knows where to find all the water damage indicators? Or is it even possible to make it look like there was no water damage?
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.
The long version of the problem is the phone (ATT model) started having severe battery life issues, to the point where it would go dead in a few hours and then even when it was on the charger it would not reach 100%. If I remember right it would shut off but still charge, then boot up, sometimes but then die. Then one day it just wouldn't turn on and wouldn't charge, no red charging indicator, nothing. It sat like that for maybe a year. Recently I realized there are pictures on it which I had not backed up (because I was looking for them and couldn't find them anywhere else). So I ordered a couple used OEM Samsung batteries on eBay. Good seller, well rated, even agreed to charge up the batteries before sending them to me.
They arrived yesterday, I swapped the batteries today and the phone is still unresponsive. I tried both batteries and got the same result as the original battery. The original battery is puffy/bloated and the new (used) ones are not. So the original battery is/was indeed a problem, but could a bad battery have fried something else in the phone? I tried holding the power and volume down buttons for 10 seconds a few times, also other various button combinations for 10 seconds, multiple times but I still get nothing. I have a USB voltage/amperage meter and it started out showing the phone taking only 0.46 A, then started falling slowly to 0.02 A where it is now. Voltage is a steady 5.11. My computer also does not detect anything when I connect it.
Is there anything more that can be done to revive the phone or retrieve the pictures from it? I assume someone who is capable at BGA soldering could possibly remove the memory chip and put it on another board? Any ideas other than that? The pictures on there are from a trip to Australia and that's a trip that won't be happening again. Any suggestions are appreciated. Thanks.