Database Info

[Q] Reviving drained battery? (Stops charging)

TLDR: Skip to TLDR near the end!
Well, this is probably the tipping point that will make me demand a new phone from Magenta, because this is getting out of hand. My phone will periodically stop charging, for seemingly no reason at all. Usually its when it has relatively low power already that it decides it doesn't want to recognize the cable being plugged in.
Usually, I will just pull the battery and drain the remaining power via the power button, put the battery back in and all is well. Lately, it happened that it stopped charging and didn't respond to battery pulls, then got so low that it refused to even boot (flashing empty battery icon). This lasted about a day and after I had went into the T-Mobile store (Which they MADE me drive 30 minutes to the store to be there in person so they could hand me a piece of paper saying they'd mail me a new unit. Bull**** in and of itself.) the phone decides it wants to start charging again. After a few more frustrated battery pulls and doing nothing new with it.
When I get my new phone (no new battery), I put the battery in that one and use it, and all seems fine. This one has worse screen bleed (top left corner was pretty much a spotlight), but I'll take that for a working phone at this point. A few days ago I was just heading out on a 3 hour trip for a short vacation when the phone reboots on me while I'm listening to podcasts. Never had this happen with the other 2 G2X's I've had. Yesterday, the thing decides to stop charging as well, but a battery pull while the device was still on did the trick and it charged again.
Once I got home I figured I'd use the original G2X, as that has everything still on it, and migrating those app settings and data is a pain. Also, if it has worse bleed, reboot problems, and the same battery issue, its worse than what I already have.
(TLDR)
Now to my current problem. The phone, once again, stopped charging and has again discharged to where it wont boot. My questions:
1) Is there a way to recover my battery without just letting it sit and praying it charges again?
2) What is the underlying issue here that could cause this? Bad software? Bad hardware (in the phone itself)? Bad battery?
3) What is the best way about getting a new phone for free (or as close to free as possible), preferably an upgrade like the Sensation 4G? I don't want to deal with my local store, as they have been proven to not know ****, and the first line of defense on the phone isnt much better.

Well i am not an expert here but Just by process of elimination it seems to be the battery. They gave you a new phone and not a new battery and now it is doing the same thing. It has to be the battery so I would go back to the store and tell them that they gave you a **** phone as a replacement and it was the battery that was the problem the whole time. They shold be able to give you a new phone and battery. Tell thewm the screen bleed is terrible and the phone yoyu had was really good except for the battery issue. Maybee someone else can give a second opinion about that battery though. Dont just go on my words I am not a pro. Good luck man.
Charlie

P6810 suddenly won't turn on

Anyone come across this? I put it on standby last night after reading a bit of my book on it, and it had around 50% power remaining. This morning, it was totally unresponsive; pressing the power button does nothing at all. I've charged it for 12 hours in the meantime.
I've done the following all with and without the power attached:
- Pressed and held power for 15 seconds through to a minute
- Pressed and held volume up with power to attempt to get into recovery for up to a minute
- Pressed and held volume down with powerfor up to a minute
- Pressed and held power while touching screen (read that one off another forum)
I guess potentially it could be on and in a crashed state and unresponsive to the power, so maybe in a weeks time when it runs out of juice, I'll be able to charge it and power it back up, but in the meantime, I'd welcome suggestions.
A few weeks ago I updated it to the official ICS build that was released, but did the update myself rather than using KIES, as KIES didn't even recognise my Tab's firmware original version. It's been absolutely fine before the update, and since. I only mention it because I've read about the Samsung build of ICS being prone to self bricking itself, but I couldn't determine what the symptoms of this vulnerability were.
Thanks for any help offered,
Will

did you try connecting USB cable and plugging it into your PC? did u get any activity? can ADB recognize your tab?

I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium

Had the same problem while on holidays. Once the battery goes below a certain level, you won't be able to charge it through USB any more. Instead you need to use the wall charger.
I think it's bad enough that the 7.7 doesn't have a micro USB port, but things like that are just stupid and Samsung made a big mistake here. It don't think it's the same with the newer tablets though. It's also not possible to just buy cables or chargers for this strange Samsung port, so when you forget your wall charger at home at some point you won't be able to use your tablet any more.
As long as you charge with the USB cable early enough, you can avoid it though.

A few months ago I experienced the same thing, the Tab just wouldn't turn on anymore.
I tried all there is without any luck.
Contacted amazon and they replaced it with a new one in less than 48 hours.
So far not Problems with the new device.

I have the P6800 and this morning I took it off charge. Put it into standby and only used it for about 20 mins then left in standby all day. It had about 95% remaining when I did so.
Picked it up this evening and the lower left area of the screen was warm and it would not switch on. Didn't think of the ADB idea but will try this next time but I had to reset it and when it powered on tonight after the reset, it was down to 15%. Within about 2 mins of checking stuff it was down to 3%.
Something is running when it is in standby but as I can't switch it on I can't check with BetterBatteryStats or CPUState to know what is wrong.
It does this every day. I am tempted to do a factory reset and reinstall only limited software.
Dave...

I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.

Cluey said:
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Click to expand...
Click to collapse
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal

TeeeJaay said:
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
Click to expand...
Click to collapse
hhmmm, interesting.
I was having trouble with wifi just before this happened. Both my GS2 and this have been claiming to connect to my wifi but aren't actually getting an IP address from it.
I can't remember if it was last night or the night before but I manually set an IP address, the signal strength is fine as my abode isn't very big.
After it has recharged I'll have a poke and see what I can find, thanks for the reply.

So my device seems to be working fine again. It had gone SO flat that the date and time were incorrect!
After I could power it on I had a look at Better Battery Stats and nothing looked wrong so I have no idea what happened. None of the apps I'd installed the day before it played up had long wakelocks and weren't running when I turned it off.
For reference they were:
My Tracks
MyTrails
Google Earth
AndSMB
I'd turned both of the GPS tracking devices off before I turned it off for the night.
It hasn't played up since but it hasn't been long so I'll see what happens.

Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.

A similar thing happens to me every once in awhile. The way i check to make sure everything alright is to see if it boots into download mode. I just leave it plugged in for a couple hours and it eventually comes back on.

someth1ng said:
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
Click to expand...
Click to collapse
this is why my 7.7 is the last tablet/phone from Samsung i'll never trust them they are just bombarding the market with new devices and leaving the old ones to dust

^thats what I thought too but that gs4 is really tempting. I've heard worse about HTC in that regard anyways so that why I'm not going with the one.

Finally.. i bought Sony xperia Z.
I'll sell my galaxy tab 7.7. I.m very disappointed with samsung.
Sent From XPERIA Z

kishd said:
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Unbelievable! ... this trick still works ... thank you very much for you help ...

^^ yo, this 'trickle charge' trick did NOT work on my (long) dead P6800... any other suggestions??

Quite strange because my Samsung GT-P6800 tablet was fully charged, it went completely blank dark as if it was off. To my amazement, SMS keeps dropping and calls kept coming in. Yet it is still as blank as though the tab was off. I pressed the power button and the volume up bottom for it to reboot. It rebooted without the screen coming up. It has been blank for two days now. What could be the cause? And what possible solution can be given?

Help! Possibly bricked my tablet?

I have had the p900 for about two years now. Rooted it some time ago and installed CyanogenMod without any problems. But just recently, when I tried to reset the tablet, it got stuck on twrp. I thought I would let the battery drain and see what would happen afterwards, but now I can't get it to turn on anymore, even though I let it charge. The tablet really doesn't do anything anymore, can't go into download mode and it isn't regocnized by my computer either. So I think it's bricked, but since I'm not really the most tech savvy person, I thought I'd ask here... Could anyone tell me if this sounds like it really is bricked, or if there is still hope?

I'm wondering if your battery discharged too far down, basically killing it. Once that happens, it no longer holds any charge. I've seen that happen on an older battery (actually happened on one of my laptops!). You could try removing the back of the tablet and disconnecting the battery and reconnecting it after a few minutes, then putting the charger back on and see if you get lights. (if you're going to do that, might as well have a new one in front of you and just replace it - easy to do, and Amazon has batteries for a decent price from a few different vendors - just did that to my Note Pro last week. Youtube it for directions, it's easy if you are patient. I used this one, http://www.amazon.com/dp/B00N4KRSVW and it is working well - even got rid of the flickering screen around 50% power and below...

Pixel (rooted) won't turn on or respond

I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?

If it won't turn on even when plugged in, something might be fried. I know batteries can start acting weird and causing problems after a few years too, but I think this is something else.
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk

Maybe, but I got it brand new from Google a bit over a year ago (06/2017), making me generally hope it isn't something related to 'natural causes'. I think what bothers me the most about this is that I don't know what went wrong and can't think of anyway to check. Plugging it into a wall plug to charge doesn't do anything and when I plug it into the computer my computer doesn't see that anything is plugged in (as I have installed upgrades via my computer, it definitely has the right drivers and everything to see it...).
The slightly paranoid side of me recalls back a few days ago to an article I was reading about malicious apps using phones to mine cryptocurrency, sometimes leading to those phones wearing down enough that they could even brick. Logically I'm almost positive this isn't happening for two reasons. The first being that I haven't installed anything for about a week (and the phone was working fine until this morning) and secondly because I had an app that monitored my network traffic and there wasn't nearly the throughput I'd expect for that kind of processing. Still, I can't think of what else might have happened...
sdnative1 said:
If it won't turn on even when plugged in, something might be fried. I know batteries can start acting weird and causing problems after a few years too, but I think this is something else.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse

You would have noticed massive battery drain if your phone was mining cryptocurrency. Try putting it into a freezer for a bit, then see if you can get any reaction when plugging in. If not, my guess is a catastrophic hardware failure, like a bad battery which leaked & fried the board, or something like that.
If you're in the US, contact uBreakiFix (Google contracts warranty repairs through them). I've read reports of them making repairs for free, even outside of warranty.

post-mortem said:
You would have noticed massive battery drain if your phone was mining cryptocurrency. Try putting it into a freezer for a bit, then see if you can get any reaction when plugging in. If not, my guess is a catastrophic hardware failure, like a bad battery which leaked & fried the board, or something like that.
If you're in the US, contact uBreakiFix (Google contracts warranty repairs through them). I've read reports of them making repairs for free, even outside of warranty.
Click to expand...
Click to collapse
Thanks for the freezer suggestion (I recall that trick for old hard drives, but never used it myself). How long you thinking for that to do anything? I tried about 10 minutes and didn't see any difference (not sure if I should be doing something closer to an hour or more?) I did Google support (online chat) and ubreakifix was one of two other options they suggested. It looks like they're a little bit of a drive for me, but I'll see if I can't stop by in the next couple of weeks. My old Galaxy S5 will have to do in the meantime (which is slow with poor reception at this point, but it functions as a phone, so I've got that going for me
I'll try to update if/when I get details from the repair guys.

If the freezer trick did anything, it would likely be temporary (possibly enough time to get data off of it). It would really just confirm a hardware failure, which at this point is my working hypothesis.

One day my pixel randomly shut down, unresponsive, holding power button did nothing, same when I tried to plug it to a pc or when plugged in.
It restarted when i pressed power + vol- (fastboot mode) for about 40secs - I know, it's a lot, never knew what happened.
Then it just worked normally

Saving a phone with a broken motherboard

Hi all,
A little backstory first. I'm very new to XDA, so please let me know if my title formatting is wrong or if this is the wrong category or something else.
I had a Nokia 7.1 for about three years. It broke about two months ago, without a warning. The way it broke was rather strange: I plugged it to a charger with 0% of battery on it. I went to check in 10 minutes or so, and the phone was showing 38% charge. I thought that was weird since the phone should not charge that fast. I didn't care about it too much, powered it on and went to get some food. After coming back, the screen was pitch black. I didn't get to see if it ever even powered on, I only saw the "Android One" logo before going to eat. I tried everything to power it on, but nothing worked. I made sure that the charger was not the problem either. It may be worth noting that the battery life had been degrading for quite a while and wasn't great anymore. I figured that the battery might have died. So, I ripped the phone apart with a rather inappropriate tool (which was probably a huge mistake, but I didn't think it would matter at the time): a regular knife. As I was unplugging the battery from the motherboard, using the knife to pop the connector out, I saw a small spark. After some days of waiting, I got my replacement battery and installed it. Still nothing. I started to suspect a motherboard issue and took the phone to a repair shop. They confirmed it: it was indeed a motherboard issue. Now, I have a few questions that I would really appreciate getting help with:
1. My current theory is that the battery died first. When removing it, the sparks fried the motherboard and this is when the phone broke completely. Do you think this is possible? What is your theory?
2. Is there any possible way to fix the motherboard in this case?
3. If the phone cannot be fixed (which is very likely), is there a way to clone the phone storage onto another device / mass memory without being able to turn the phone on? The reason I want to save this phone so bad is that I have some important 2FA codes in there, can they be saved?
Any help would be greatly appreciated! If you need any extra information regarding this, let me know.