Okay everyone here is a hard one...
My son cracked my screen on my S3. It works and functions I put a screen protector on it for now, don't ask why I haven't fixed it yet -- it's irrelevant.
A few nights ago I was sleeping and I woke up to my phone super hot, couldn't even hold it in my hands, but it was okay and was working fine I let it sit out overnight and cool off then charged it back up. All seemed fine, until a day or so ago.
For some reason the phone completely shuts off AS SOON as it loads the rom (ANY ROM) I even went back to full stock and SAME thing happens. I do mean FULL stock. (Hours of work went into that fun process).
WHAT'S WRONG
- Phone shuts off once it loads into any rom then reboots and repeats the cycle
- Phone DOES NOT shut off if plugged into a power source, stays on without issues and works fine
- I can't use my phone without it being plugged in (battery works fine and charges fine)
WHAT I HAVE TRIED
- I tried cleaning the power button and internals by taking the whole phone apart.
- I checked to see if it was bricked in any way
- I tried different roms and android versions including stock (Yes with factory resets)
I have not tried deleting the entire phone internal memory (formatting it essentially) and re-installing android files back to it.
Any ideas?
Scath said:
WHAT'S WRONG
- Phone shuts off once it loads into any rom then reboots and repeats the cycle
- Phone DOES NOT shut off if plugged into a power source, stays on without issues and works fine
- I can't use my phone without it being plugged in (battery works fine and charges fine)
WHAT I HAVE TRIED
- I tried cleaning the power button and internals by taking the whole phone apart.
- I checked to see if it was bricked in any way
- I tried different roms and android versions including stock (Yes with factory resets)
I have not tried deleting the entire phone internal memory (formatting it essentially) and re-installing android files back to it.
Any ideas?
Click to expand...
Click to collapse
I suggest changing the battery to see if it still behaves that way. I also suggest you to completely start with a clean slate (format everything, including the internal SD, external not necessary) to discard possible issues. Those are the only ideas coming up right now.
I'll try and see if its either of those. I also noticed the power button is super sensitive. Light touch sets it off or on. Like capacitative button "light touch " how gentle those are pressed is how gentle I am tapping power and screen responds.
Sounds exactly like a faulty power switch, but it could potentially be the battery itself too though.
When you put the battery in, does it try to turn on by itself? If so it's almost certain to be a bad power switch.
Be very careful flashing in this scenario. ESPECIALLY flashing firmware via Odin. If it reboots during the flash it can be very bad news.
This can cause a brick on its own too btw, so i highly recommend getting it fixed ASAP. People have reported having this happen and at some point it just stops powering up at all. Upon further investigation it would show to be hard bricked, sometimes fixable, sometimes not. Basically the constant resetting (like power is permanently pressed) ultimately causes corruption on some of the partitions. It is possible there is already some data corruption present which could cause processes to hang, eat up battery and cause excessive heating.
If you want to be sure it's not the battery itself causing problems though, find someone with another S3 (go to a Tmobile store if you don't know someone) and borrow a battery to test with.
A bad battery can also cause reboots and overheating, but this is much less common than the bad power switch.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Sounds exactly like a faulty power switch, but it could potentially be the battery itself too though.
When you put the battery in, does it try to turn on by itself? If so it's almost certain to be a bad power switch.
Be very careful flashing in this scenario. ESPECIALLY flashing firmware via Odin. If it reboots during the flash it can be very bad news.
This can cause a brick on its own too btw, so i highly recommend getting it fixed ASAP. People have reported having this happen and at some point it just stops powering up at all. Upon further investigation it would show to be hard bricked, sometimes fixable, sometimes not. Basically the constant resetting (like power is permanently pressed) ultimately causes corruption on some of the partitions. It is possible there is already some data corruption present which could cause processes to hang, eat up battery and cause excessive heating.
If you want to be sure it's not the battery itself causing problems though, find someone with another S3 (go to a Tmobile store if you don't know someone) and borrow a battery to test with.
A bad battery can also cause reboots and overheating, but this is much less common than the bad power switch.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Sounds like I have three possible causes then... So I will first wipe and format internal memory and re flash everything. Oddly enough it does not reboot when plugged in and sometimes doesn't reboot at all but if I open camera or similar apps it then reboots and won't fully boot just tries to load everything and I get signal and texts come in but then it turns off and reboots again.
Then I'll go to my local spot with an S3 in display lol check battery and see.
Last I'll try and look closer at this power switch, don't think its the cause though. Ill place Collin different positions and see.
Even stranger...
So I reformatted my ENTIRE phone internal and external memory. Using multiple devices. Then re formated inside recovery to add the correct folders and files and stuff.
Here is my question.... Previously stated was "Battery could be an issue or Power Switch" -- If these were both the issue why would the phone never turn off in recovery mode? Why would it stay on during boot for long periods of time after flashing?
How can the battery or power switch be the problem when recovery mode keeps the phone on, and I tested this by leaving it on for an hour without it turning off.
The ONLY time it turns off is when the OS is about to boot up Android. If I keep it plugged in, then it boots up fine. What the hell?
A faulty power switch may not always constantly reboot. I've seen some that do, some that stayed on in Download Mode only, some that only rebooted when held a certain way, some that simply just had an extremely sensitive button, etc. In each case, replacing (or sometimes cleaning/fiddling with it) seemed to fix the issue.
I have also seen problems due to an old or defective battery. As it gets older, it doesn't just lose its ability to hold a charge, but it also gets weaker in that it cannot supply a stable or strong enough level of output. So, for example, it could seem to run ok, but as soon as you try to do something requiring more power, such as using the camera, it can crash because the battery can't provide enough power.
In a case like that, it could easily be able to supply enough to run recovery as its power requirements will be much lower than when you are booted up normal.
You did say it works just fine when plugged in though, and that it only reboots when you try to boot normally. But you also said opening the camera will cause it. This is why I suspect it could be the battery.
You also mentioned that the power button is extremely sensitive though. That is not normal and faulty power buttons happen frequently on this device.
All I'm saying is it could be one, or even both, of those causing your problems. It is possible too though that it's suffering from memory failure, which can result in any number of strange problems.
I am just giving you the most likely possibilities based on past experiences in these forums. I'm not saying it's definitely one or more of these. It could be something else entirely.
Did you ever try the test I asked you about? Remove/reinstall battery. Does it try to turn on by itself when you put it back in?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
A faulty power switch may not always constantly reboot. I've seen some that do, some that stayed on in Download Mode only, some that only rebooted when held a certain way, some that simply just had an extremely sensitive button, etc. In each case, replacing (or sometimes cleaning/fiddling with it) seemed to fix the issue.
I have also seen problems due to an old or defective battery. As it gets older, it doesn't just lose its ability to hold a charge, but it also gets weaker in that it cannot supply a stable or strong enough level of output. So, for example, it could seem to run ok, but as soon as you try to do something requiring more power, such as using the camera, it can crash because the battery can't provide enough power.
In a case like that, it could easily be able to supply enough to run recovery as its power requirements will be much lower than when you are booted up normal.
You did say it works just fine when plugged in though, and that it only reboots when you try to boot normally. But you also said opening the camera will cause it. This is why I suspect it could be the battery.
You also mentioned that the power button is extremely sensitive though. That is not normal and faulty power buttons happen frequently on this device.
All I'm saying is it could be one, or even both, of those causing your problems. It is possible too though that it's suffering from memory failure, which can result in any number of strange problems.
I am just giving you the most likely possibilities based on past experiences in these forums. I'm not saying it's definitely one or more of these. It could be something else entirely.
Did you ever try the test I asked you about? Remove/reinstall battery. Does it try to turn on by itself when you put it back in?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Well Doc, I think everything you just said wrapped it up for me and made a ton of sense.
Sounds like the battery. It overheated prior to this and when I checked the logic board there were no signs of heat stress points I remember when I took the phone casing off when it got hot, the battery was the hottest part that I couldn't touch. I think the battery just gave out finally after all these years of use.
Install and reinstalling the battery the phone does NOT turn on by itself. Not ever. ONLY when it tries to boot the OS does it go into a boot loop where it tries to boot fully then restarts, similarly when you have a very low battery and the phone shuts off right as the OS boots.
Think the battery is the culprit here. :fingers-crossed: I just bought a new glass screen kit for the phone as well, $6 bucks isn't too shabby on ebay. Even though it may suck really bad and be flimsy glass, it's still something! So now the battery will be purchased next -- any suggestions?
I just got a new battery on ebay too, but it's got problems. They sent a free replacement but it's worse than the first. They might be fake "oem" batteries so i dont want to recommend them.
They appear to be from the same lot though, so it could be just bad luck and a bad lot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
If you want an OEM battery you're probably better off buying it from Samsung or T-Mobile. I've also heard zerolemon is a good alternative
Related
Hello xba-developers!
>Device HTC One X
>Quad Core 1.5 Ghz processor
>16 GB memory
>Everything is stock, no rooting nothing.
I've been checking this forum for quite a while but just found the need to register obviously because of a problem which I cannot find solution to.
I've checked couple of forum posts like THIS and some others and they KINDA have solution but it's really vague for me and I'll explain why; the reason is that I'm a complete newbie to all this, I've never rooted a device don't even know what that means and all these custom ROMs and everything really confuse me. Plus, my computer can't pick up my phone and generally I don't quite know if the cause of my problem is the same as other posts (Even though the problem is same) which means the solution may be different.
PROBLEM
It was raining, I was outside, some moron bumped into me in the street and phone slipped out of my hand, fell into a pool of water. I took it out as soon as I could but it was all wet. I tried to turn off the device but it kept restarting it wouldn't power down! (When I pressed power off it would do just regular restart) then suddenly it started working but the thing is, BEFORE all of this battery was in 14%, after it magically started working battery was on 80% which means it must have shortened somewhere (Problem with battery). Then all of a sudden it started doing these weird things like turning on music all of a sudden, turning on screen, shutting down, restarting and so on... (The speakers pretty much weren't working but still there was music somewhere). Then it went into a boot loop, I tried to do recovery but it kept restarting even when I was pressing POWER + Volume down buttons.
Then what I feared the most, battery died. Whenever I connect to power source (no matter Computer or Wall charger) it automatically goes into boot loop, the device won't stop working at all it won't shut down nothing. Battery is out of charge and I can't charge the phone enough to do Factory Reset. I took it to Service center but they are having "holidays" because 8th march is women's day and then it's sunday...
I really hate the fact that the battery is sealed inside the phone! It becomes real headache in this situations I could just take the battery out and tried it out but NOPE, can't do that!
Plus it's my first android and it uses this mini sim card thing (which they happily shortened in the store) and I don't really have any other Android phones to use my card on since it's too small for older devices...
So, the question:
How do I charge my phone when it goes into boot loop every time I plug it in?
My PC can't recognize it (it makes the sound when you connect Flash device through USB and then in 0.5 sec makes the one when you disconnect that same device).
I just need my phone to work properly. Or at least start up!
Thanks to everyone who read this huge post and I'm really sorry if I missed one or another forum thread that describes my problem exactly (which is unlikely but still).
Thanks again, have a good day!
LizardProtection said:
Hello xba-developers!
>Device HTC One X
>Quad Core 1.5 Ghz processor
>16 GB memory
>Everything is stock, no rooting nothing.
I've been checking this forum for quite a while but just found the need to register obviously because of a problem which I cannot find solution to.
I've checked couple of forum posts like THIS and some others and they KINDA have solution but it's really vague for me and I'll explain why; the reason is that I'm a complete newbie to all this, I've never rooted a device don't even know what that means and all these custom ROMs and everything really confuse me. Plus, my computer can't pick up my phone and generally I don't quite know if the cause of my problem is the same as other posts (Even though the problem is same) which means the solution may be different.
PROBLEM
It was raining, I was outside, some moron bumped into me in the street and phone slipped out of my hand, fell into a pool of water. I took it out as soon as I could but it was all wet. I tried to turn off the device but it kept restarting it wouldn't power down! (When I pressed power off it would do just regular restart) then suddenly it started working but the thing is, BEFORE all of this battery was in 14%, after it magically started working battery was on 80% which means it must have shortened somewhere (Problem with battery). Then all of a sudden it started doing these weird things like turning on music all of a sudden, turning on screen, shutting down, restarting and so on... (The speakers pretty much weren't working but still there was music somewhere). Then it went into a boot loop, I tried to do recovery but it kept restarting even when I was pressing POWER + Volume down buttons.
Then what I feared the most, battery died. Whenever I connect to power source (no matter Computer or Wall charger) it automatically goes into boot loop, the device won't stop working at all it won't shut down nothing. Battery is out of charge and I can't charge the phone enough to do Factory Reset. I took it to Service center but they are having "holidays" because 8th march is women's day and then it's sunday...
I really hate the fact that the battery is sealed inside the phone! It becomes real headache in this situations I could just take the battery out and tried it out but NOPE, can't do that!
Plus it's my first android and it uses this mini sim card thing (which they happily shortened in the store) and I don't really have any other Android phones to use my card on since it's too small for older devices...
So, the question:
How do I charge my phone when it goes into boot loop every time I plug it in?
My PC can't recognize it (it makes the sound when you connect Flash device through USB and then in 0.5 sec makes the one when you disconnect that same device).
I just need my phone to work properly. Or at least start up!
Thanks to everyone who read this huge post and I'm really sorry if I missed one or another forum thread that describes my problem exactly (which is unlikely but still).
Thanks again, have a good day!
Click to expand...
Click to collapse
See my thread here: http://forum.xda-developers.com/showpost.php?p=50106149
I would suggest replacing the Power Flex Cable and Battery as described. Hopefully it will fix your problem.
de4life said:
See my thread here: http://forum.xda-developers.com/showpost.php?p=50106149
I would suggest replacing the Power Flex Cable and Battery as described. Hopefully it will fix your problem.
Click to expand...
Click to collapse
That seems to be exactly my problem! Thanks!
Couple of weeks ago my gnex fail to start a boot after my battery used up to %0. I used a wall charger but it did not help, I mean there were no charging screen, no boot animation, no vibration that indicate start boot. I assumed battery was so low, it would not boot enough to charge, so I used an cheap battery charger to charge the battery, then everything worked as expected. this happened one more time, that made me think there was a issue about the rom or some software, but I did not act on it. Then a few days ago my phone rejected to try to boot even with full battery.
I search the forums, and find out connecting to wall charger then inserting battery will trigger a boot, and it really did. Then I flashed official google image to see if it fixes the issue but no luck, then I tried odin flash with repartitioning, still no luck.
Currently I am on full stock on my gnex. If I shut it down, no matter which button/combination I try, it won't trigger a boot. If I connect to a wall charger while battery is in, screen does not turn on and charging does not start. If I remove the battery, connect to wall charger, then insert the battery, charging screen came up, then if I press power button for ~5 second it boots to android like everything is okey, and after boot starts, I can disconnect the charger, no issues about battery.
I have no clue what might be causing this. Power button works, battery works, rom/software works, are there anyone with some ideas what might be causing this?
it is very interesting. may it be battery problem?
agritux said:
it is very interesting. may it be battery problem?
Click to expand...
Click to collapse
I tried a friends battery on my device, and my battery on his, mine did not boot, but his one did, I don't think there are anything wrong with battery.
It boots now but unstable
Hi again. Not booting issue seems to be fixed (without doing anything) but now it reboots when I try to download anything. I used stability test to check if cpu or gpu has any issue, the test did not found any issue.
I am suspecting my internal storage causing this issues, but I could not find any tool to check/fix it. Are there anyone that knows a way to do so?
I wanted to report back my last status. The phone is working normally know. I tried out flashing different kernels, and at some point, random reboots stopped. To verify, I downloaded several GB of files, tested with antutu and 3dmark, everything looks normal.
Long story short, I have no idea how it got fixed, but it did. I suggest anybody with my situation to keep trying, I bought a g2 thinking it would not be usable, I regret that decision now.
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
I have same problem!
Bump. I have the same problem too. Seems to have come out of the blue for an otherwise functional phone. Can't figure it out.
I'll add that I can get into twrp and it seems to function without the charger plugged.. But otherwise, if the charger is removed, phone dies like OP.
Anyone can help?
Hey, this happened to me too while I was using the camera too! What's the linkage?
@yakultski, have you figured this out yet?
Try to flash a RUU and if you got the same it should be an hardware problem...
yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
Did you resolve the issue. I heard it could be the battery failing, but i'm not so sure anymore, because when i run antutu benchmark my phone shuts down when using fisheye image processing or 3D, it turns off even when it's plugged in.
I suspect it's the GPU failing or something similar. That is weird since i wasn't using any intense 3D games. I'm sure this is my last HTC.
yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
I don't know if you managed to solve your problem, but in my case I replaced the battery and now the problem is gone. So defective battery is the reason in my case. I replaced it my self which is quite a task but not so hard, you just need patience and time. So if you have time to reply me, please do, as i would like to help.:good:
Gunman84 said:
I don't know if you managed to solve your problem, but in my case I replaced the battery and now the problem is gone. So defective battery is the reason in my case. I replaced it my self which is quite a task but not so hard, you just need patience and time. So if you have time to reply me, please do, as i would like to help.:good:
Click to expand...
Click to collapse
Hey Gunman84, my phone is behaving in a similar fashion as the OP. I have an AT&T phone converted to a GPE. So everything is stock in that sense. If plugged in, phone operates normally. As soon as I unplug it, a couple of seconds later it will power off. If I boot into hboot, the phone will stay on for a long time (its been an hour+ already and its still on).
I watched a youtube video showing how to replace the battery and that was pretty intimidating - haha. Where did you get your battery replacement? and how much did it cost?
thanks
clemdaddy said:
Hey Gunman84, my phone is behaving in a similar fashion as the OP. I have an AT&T phone converted to a GPE. So everything is stock in that sense. If plugged in, phone operates normally. As soon as I unplug it, a couple of seconds later it will power off. If I boot into hboot, the phone will stay on for a long time (its been an hour+ already and its still on).
I watched a youtube video showing how to replace the battery and that was pretty intimidating - haha. Where did you get your battery replacement? and how much did it cost?
thanks
Click to expand...
Click to collapse
Hi, it's not so intimidating . Well you just need to be careful and patient, there are lots of small resistors, connectors and so on. Check the iFixit site for proper instructions here is the link https://www.ifixit.com/Teardown/HTC+One+%28M8%29+Teardown/23615 this is full teardown, and here is 2nd link where they focus mainly on replacing the battery https://www.ifixit.com/Guide/HTC+One+M8+Battery+Replacement/41650. I'm from Slovenia, and the battery cost me 20€, which is around 25US dollars, the battery was original one. I bought it from local supplier. It took me around 2-3 hours to replace it, or something like that, that's because i wanted to be careful.
Gunman84 said:
Hi, it's not so intimidating . Well you just need to be careful and patient, there are lots of small resistors, connectors and so on. Check the iFixit site for proper instructions here is the link https://www.ifixit.com/Teardown/HTC+One+%28M8%29+Teardown/23615 this is full teardown, and here is 2nd link where they focus mainly on replacing the battery https://www.ifixit.com/Guide/HTC+One+M8+Battery+Replacement/41650. I'm from Slovenia, and the battery cost me 20€, which is around 25US dollars, the battery was original one. I bought it from local supplier. It took me around 2-3 hours to replace it, or something like that, that's because i wanted to be careful.
Click to expand...
Click to collapse
Thanks so much for the links.
The phones behavior really makes me question if its the battery. For example, it stayed on in the hboot/recovery screen for 10+ hours (without being plugged in). So the battery can definitely hold a charge.
I'm afraid to open up the phone (and potentially break it), when there is potentially something else going on (maybe a software issue). I guess if I run out of ideas, I'll have no choice but to attempt the battery replacement.
thanks again!
clemdaddy said:
Thanks so much for the links.
The phones behavior really makes me question if its the battery. For example, it stayed on in the hboot/recovery screen for 10+ hours (without being plugged in). So the battery can definitely hold a charge.
I'm afraid to open up the phone (and potentially break it), when there is potentially something else going on (maybe a software issue). I guess if I run out of ideas, I'll have no choice but to attempt the battery replacement.
thanks again!
Click to expand...
Click to collapse
Well in my case i could also stay in recovery mode(TWRP) indefinitely also in bootloader mode, that's because you are not in the operating system. The graphics are not running at that point and so on, it doesn't drain that much power at that point either.. It's a different story if you try to flash a rom in aroma, at that point the phone shuts of if not plugged in. It is the battery, trust me.
Gunman84 said:
Well in my case i could also stay in recovery mode(TWRP) indefinitely also in bootloader mode, that's because you are not in the operating system. The graphics are not running at that point and so on, it doesn't drain that much power at that point either.. It's a different story if you try to flash a rom in aroma, at that point the phone shuts of if not plugged in. It is the battery, trust me.
Click to expand...
Click to collapse
Really appreciate your responses. Makes sense what you say. I'm going to attempt the battery swap. Got no other option!
For the adhesive parts of the phone. When putting it back together, did you need to reapply more adhesive?
Thanks
clemdaddy said:
Really appreciate your responses. Makes sense what you say. I'm going to attempt the battery swap. Got no other option!
For the adhesive parts of the phone. When putting it back together, did you need to reapply more adhesive?
Thanks
Click to expand...
Click to collapse
Nope, no additional adhesive was needed in my case. I used the hair dryer to soften the original adhesive. The speaker grills were difficult to remove as they are glued quite well, but eventually they came off. The toughest part was separating the back casing, as you do need quite a few prying picks or guitar picks.
Just be careful with the motherboard, slowly remove the tape that covers the connectors, you don't want to rip apart any flat cables. And don't throw away that tape, you will need it.
Ohh i have the same issue.i used phone normally before and battery worked fine.but then i flashed ICE rom and when i was using the camera this happend.is this really a battery issue?
Sent from my HTC Desire EYE using XDA-Developers mobile app
Kasun72 said:
Ohh i have the same issue.i used phone normally before and battery worked fine.but then i flashed ICE rom and when i was using the camera this happend.is this really a battery issue?
Sent from my HTC Desire EYE using XDA-Developers mobile app
Click to expand...
Click to collapse
Well if yours symptoms are the same as clemdaddy has, then yes. Sorry, but at least now you know what the problem is.
Got the new battery today and performed the phone surgery. All the connections looked good. Pieced it all back together and everything works BUT the new battery won't charge. The phone is running off the battery, so the connections I made must be correct. Running off the battery the phone no longer exhibits the symptoms I described above (so this most likely confirms my previous battery was the culprit). I tried the hold all buttons for 2 minutes to re-calibrate the new battery. All that did was made the phone now display a full battery (instead of the empty battery it initially showed).
On the weekend I'll open it up again and see if I missed something.
Got the replacement battery. Re-opened up the phone. This time I over heated the upper and lower panels which caused them both to warp a bit, and one of them to have its paint bubble :crying: :crying: :crying: :crying:
I replaced the new defective battery with the most recent one. Put the phone back together and it is back to normal again! Also probably because of the over heating, there is now a little bit of a rainbow effect on the lower part of the LCD screen!
A real pity the first battery was defective, causing me to have to re-open it and carelessly overheat it. Otherwise the 1st attempt would have been a flawless repair!
With the warped panels, the bubbling paint and now the rainbow effect on the screen, I wonder how long I'll keep the phone. These little things are definitely bugging me... If I get rid of it, I'll really miss my google edition htc one m8! Nothing like a nexus like experience with a remove-able microSD card. Such a thing no longer exists
This past week, I purchased a 2014 Note 10.1 off Craigslist. I did check it out before buying it, and the device is in pristine condition, including the screen. It booted fine, and I went partway through the setup (the guy had factory reset it) before closing the deal. It is the wifi-only model, 3G RAM, 8-core Exynos version. It's white if that matters.
Anyways, a while later when playing with it some more, completing setup, etc, it just died on me. I wasn't home, and didn't have a place to charge it until I got home, but just figured that despite the device having said the battery was 99% charged, the guy keeping it unused for a long time might have thrown off the battery calibration. My understanding is that a Li-ion battery has one or more cells, plus circuitry that protects against overcharging and undervoltage conditions, as well as tracking the current charge state. With lengthy non-usage, the circuitry's idea of the current charge can get out of sync with reality, so I figured a few charge-discharge cycles would get it back in shape.
However, the situation after I got home turned out to be a little more complex. If I plug in the device to a power source with enough current (like the charger it came with, or my 2.1A USB outlet by my bed), it will run just fine while plugged in. However, upon unplugging, it would die quickly. Naturally, I assumed the battery was probably shot, so resigned myself to spending $50 on one. This is where it started to get a little weird. It seemed that when I booted into either fastboot or Odin mode, it would stay on much longer than normal, while unplugged. I'm talking hours, rather than between several seconds and several minutes while booted into the OS proper.
This lead me to believe that perhaps it wasn't my battery itself, but rather a glitch in the OS that was causing it to shut down. When I say shut down, I mean an immediate full-off state, not a nice shutdown or one preceded by low battery warnings. It just clicks off like a light that's been turned off. However, trying several different firmwares, including a couple custom ones, has not yielded any improvement. The issue remains.
The device was stock 5.1.1 when I bought it. I tried flashing KitKat (various images downloaded from SamMobile), but for some reason, it would still say it was running 5.1.1. I tried xKat, as in this thread. That results in 4.4.2 with the associated customizations, but the shutdown issue remains. I tried CyanogenMod 13, as instructed here. It works fine, notwithstanding the same issue. In between the stock firmwares (pushed to the device with Odin) and the custom ones, I would do a full wipe through TWRP.
I've popped the back off, disconnected the battery, waited a bit, and reconnected it.
Now my question: does anyone have any idea what's going on? If it's a dying battery, then why does the device say it's got a nearly full charge, and why no low battery warnings? Why would Odin mode or recovery (TWRP now) seem to keep the device powered up so much longer? Sure, they draw less power, but hundreds of times less power? I doubt it. If it's some hardware issue with the chipset/motherboard/etc, then why does it only manifest when running on battery, or a low-current USB connection? If it's an issue with Android itself, then why does nobody else seem to have this issue (googling revealed nothing that matched my symptoms), and why did several different versions exhibit the exact same problem?
I really don't want to spend money on a new battery and wait a few weeks for shipping if there's something else I'm missing that could get my device functional for free and a lot faster.
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off. I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again. For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing. For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Sent from my SM-P600 using XDA Premium HD app
Thanks for your reply.
siralsmooth said:
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off.
Click to expand...
Click to collapse
That's a bit different from my issue. Even when the device reports full charge, if I unplug it, it usually dies within seconds, and always within 2-3 minutes.
siralsmooth said:
I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again.
Click to expand...
Click to collapse
I don't think that's going to make a difference for me. From what I was reading, all it does is delete the batterystats.bin file (hence the root requirement), which doesn't have anything to do with calibration for most devices. It just contains the stats for how much battery drain various things have caused, during this 'running on battery power' session. It's also reset every time the device is charged. Read here for more info.
Furthermore, even if this were not the case, I'd conclude that wiping the system partition (indeed, all partitions except recovery) would have cleared this data.
Still, that said, it's conceivable (though exceedingly unlikely) that some of these calibration apps might do something else, such as talk to the battery circuitry at a low level. Since I've got nothing to lose, I will probably give a few of them a shot. Do you happen to know which one it was that you tried?
siralsmooth said:
For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing.
Click to expand...
Click to collapse
In my case, the values seemed to track pretty closely, and with numerous freshly-flashed versions exhibiting the same issue, I'm pretty sure at this point it's not a software glitch. I've resigned myself to ordering a new battery. I just wish I was certain that it would fix the issue.
siralsmooth said:
For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Click to expand...
Click to collapse
My understanding is that the bootloader doesn't change with flashing. I might be wrong though; is there a way to check the version?
Just a heads up. I ordered a new battery, which arrived yesterday. It seems to have completely solved the issues I was having.
My guess is that Android itself monitors the battery more diligently, and takes a more conservative approach to preserving battery life by shutting down when the voltage drops too low, while recovery mode would just let it run down completely flat (not good for Li-ion cells).
It's a moot point now, because it all seems good.
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Bootloops/shutdowns are going to corrupt your data. I would RUU the thing before looking for hardware trouble, which you've likely sorted out by replacing the battery (of course, we're assuming the new battery is good).
BUT before that, is there a memory test in the bootloader or recovery? If so, I would run that very first thing.
bluedimensional123 said:
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Click to expand...
Click to collapse
Whatever happened to your phone? I have the exact same problem. Infinite boot loop, no illuminated LED, and no way of getting into recovery or anything else with it bootlooping. It occurred after I made the mistake of trying to restart it at 25%. I have the new battery and screen. i'm going to attempt to open this Pandora's box. Seriously going to have to turn my back on HTC. The 10 is so full of software issue problems regarding the batteries that they never bothered to address.
I did the exact same thing a few days ago and my phone won't charge or boot, but I do think the problem is with the button strip, that's what i think, because i tried turning it on before re assembling it and it did turn on successfully and was charging normally but when i re Assemble it, the phone got this problem, now i think when i turned it on before assembling i pressed the power button with a screw driver because i couldn't press it with my fingers, I think there i messed it up, any advice how to fix the button strip and remove a slip nut would be very much appreciated
I had the exact same issue as you(shutting down at 50%), have you found any solution to it?
edit: I THINK clean flashing oreo firmware then latest RUU then twrp then lineage fixed my issue, charging to full rn will drain it over the next day and report back if its gone for good