Related
Howdy, guys.
I've got my One rooted, unlocked, and was running a CM10.2 nightly build. Everything was working fine until yesterday, when my battery started to rapidly discharge. I woke up with 100% battery, and after about 15 minutes of playing music it was down to 30%. I recharged it and started noticing rapid battery loss, about 10% per 15 minutes when the phone was idle.
Worried that this had to do with my ROM, I flashed the Eclipse Google Play Edition v1.2 ROM. However, the drain issue continued. I decided to let the phone fully discharge, then try powering it up again.
When it was fully discharged, I tried plugging in the phone. No LED came on and I couldn't turn the phone on. I've let it sit for over 2 hours now with the same result.
Some posts with similar symptoms have mentioned plugging the phone into a Windows PC and experiencing the "USB device plugged in" sound alert. I am not having any such luck, and what I currently have is a very aesthetically pleasing paperweight with no function whatsoever.
Has anyone else experienced a similar issue, or found a fix?
none
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Last Sunday, listening to music with HTC One (bought on Sep 11) on the charger, it suddenly went dark. Would not reboot, no charge light either. Went to a VZW store, they're shipping me a warranty replacement.
I wonder whether my habit of leaving it charger-connected whenever it's sitting on my desk (i.e., way beyond the fully-charged point) somehow stressed the battery (or the charging circuitry) -- though that habit never impacted my two previous HTC models.
When you hold Vol+Down and Power do your home and back arrows blink? If so, point the phone sensors (the two on the front on the left hand side) into a bright light. Then hold down Vol+Down and Power. It should boot. I'm not sure why. But it worked for me today after installing a custom recovery. -shrugs-
musicman625 said:
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Click to expand...
Click to collapse
I've got a replacement being shipped to me, and I'll send them the old one when it comes in. Currently using an old Samsung Stratosphere as a replacement, I was just hoping there'd be an easier fix or something simple. Thanks, though!
I posted this in the noob thread and I'm not sure how posting a new thread will help but hopefully someone may be able to sort me out.
I was using my phone in the car about an hour ago, listening to music (3.5mm jack). At this point my battery was at 3%. I opened Snapchat and the camera was being weird; it had purple noise(?) lines all over the screen every time I pressed the screen to focus it which tells me the camera is stuffed for whatever reason.
Anyway, the phone died on me. I assume the battery died as it was already low. However, it then starts to bootloop about 4-5 times and only manages to reach the encryption screen once, at which point it just switches off. Again, I thought the battery died! So I walk in to my flat, plug the charger in and expect it to boot but nothing happens. At this moment, there is no LED light on the front to indicate charge despite having been on charge for over half an hour, there is no vibration or any form of life from the phone. It just seems to have flat out died on me.
Now I know people will say I dropped it or its water damage so right off the bat, it is neither of those. It was dropped around 3 months ago, once, on carpet, from about 1.5ft if that. Never seen liquid and never been pulled out in the rain or anything like that. Last night it charged fine and today it worked fine too. Now it's dead!
Is there anything I can do/try? The USB cable/charger are fine, I tested them with a volt meter. Other things I have done include trying to boot the phone in any way possible through a number of button combinations, with and without SIM/SD card and even tried to plug the cable into my laptop. It's simply dead. Finally, if this helps: the phone is stock apart from an unlocked bootloader. It is rooted and has xposed installed with 3-4 mods, none of which do a lot (Snappreffs, xnotifications, dpi manager etc). It is running old firmware (like from last May when I bought it. Just never got around to updating I guess!) but this has never caused a problem.
Thanks in advance for any help.
Edit: Phone now responsive after 45 mins+ of being plugged in. Charging and working fine. Weird af..Mods feel free to delete this thread.
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
I don't know what happened, but my true friend is probably deadly ill and she's dying.
My Samsung Galaxy Tab S 10.5 after almost 3.5 years of really hard work, 8h daily of SOT, hard CPU tasks, loading battery two times a day, started to do strange random reboots.
I was installing Blue Filter app, reading big pdf and sending this PDF from Xodo to Voice Aloud reader. Tablet was connected to charger from Moto X Style, which is turbo power charger. I saw first reboot, then other and next. Entered Cwn Twrp, cleaned cache but the problem still existed. Cleaned system, internal storage and tried to flash Iron ROM again. Strange, but tablet couldn't flash Iron ROM 3.2 gauge showed 100%, almost after beginning of installing ROM. I decided to flash 4 elements repair ROM with Odin, but it didn't help. Checked erase NAND, flashed correct pit file.
Strange, but while flashing with Odin, there were no reboots, so downloading mode is working properly. But after install, reboots returned, almost after running system first time.
Maybe it depends on ROM version? I flashed 4 files of 4.4.2 with Odin, while I was on 6.0.1 earlier?
But reboots started on proper ROM.
Also, maybe charger is responsible? Moto X Style 3A charger maybe damaged memory or motherboard of my friend?
Do you think that exchanging the battery may help? My battery when it was loading frequently showed a red cross, it can be that it's damaged, but random reboots never happened to me.
I don't want to buy new device, it's really stupid for me to spend hundreds of dollars every two, there years. I believe that a device should work 5 years or longer. Maybe corporations make devices especially to die after warranty period?
Can you help me to determine what is damaged?
It was my true friend, carrying tons of books with a thin device, reading big pdfs smoothly, making notes tons of paintings, editing photos and taking photos with my Nikon D610 via USB, listening to music with A.r.i.s.e , watching photography tutorials and movies, modern Combat 4 tons of hours, notes, showing portfolio to my clients... Yes I love my small friend, can you help me to rescue it?
You can see the behaviour here
Are the reboots happening even while plugged in or only after unplugging the charging cable?
Also is the percentage reading being sporadic meaning it changes every time it shuts off?
Replacing the battery is fairly cheap and easy on this model.
Here is a guide:
https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S+8.4+Battery+Replacement/51359
Where to buy a replacement battery:
https://www.ifixit.com/Store/Parts/Samsung-Galaxy-Tab-S-8-4-Battery/IF252-014-1
If for some reason it still has the same issue after replacing battery then the battery connector needs to be looked at under microscope. It may have a loose connection to the board meaning it would need to be resoldered.
Dear Benjamen, thanks for your help. Tab reboots even if it's plugged to charger. The percentage is strange, one time it shows 40%, another time beeps and shows low power warning.
Sometimes it works 5 minutes without reboot, some times boots many times continuously.
Do you think it's battery? No EMMC error or some chip damaged on motherboard?
Download mode Odin worked good, also CWRP worked without reboots.
Maybe internal storage is damaged?
What do you think?
If it is battery I can surely exchange it like you wrote.
You can see the behaviour of tablet on YouTube I've posted above.
Have you tried to reinstall Twrp and a custom rom besides Iron Rom and doing a clean flash? Also I was thinking it might be a corrupted sd card try to remove the sd card and reboot see if that works I had a tablet once that was going bonkers cause the sd card was messed up , it might not be it but could always try it. Also make sure your on the proper boot loader for the rom you are trying to flash iron rom thread actually has a link to all the current boot loaders if i remember correctly. I do own this device and run a custom nougat rom no issues, just shooting out some ideas but you are right this is great device and should last a long time.
Astania said:
Dear Benjamen, thanks for your help. Tab reboots even if it's plugged to charger. The percentage is strange, one time it shows 40%, another time beeps and shows low power warning.
Sometimes it works 5 minutes without reboot, some times boots many times continuously.
Do you think it's battery? No EMMC error or some chip damaged on motherboard?
Download mode Odin worked good, also CWRP worked without reboots.
Maybe internal storage is damaged?
What do you think?
If it is battery I can surely exchange it like you wrote.
You can see the behaviour of tablet on YouTube I've posted above.
Click to expand...
Click to collapse
Sounds like battery connector has loose soldering. Take it to a reputable repair shop that does soldering and tell them to check the battery connector and see if it needs resoldering. That's how I ended up fixing it with the same symptoms that you had.
Edit: Forgot to tell you but I cant play the YouTube video, maybe the embedded video link is invalid so can you send me the youtube link?
Mine has been doing the exact same thing for a couple of days now.
I'm running LineageOS 14.1.
Random reboots both with the charger connected and disconnected, Battery percentage is around 45% most of the time, but jumps to 0% or 100%.
I've already replaced the battery with a "new" one (about 12 months old, according to the label), but to no avail.
Any ideas? I really like this device and would not want to buy a replacement...
brot2
My SM-T800 started doing something strange like this yesterday. As I was watching Youtube and reading a news site in split screen mode, the screen suddenly went blank (it didn't shut down, but went blank at once). Before this happened, I saw a warning that my battery charge was below 15%. After powering on the tablet, my charge was 28%. I opened youtube and a web browser again, and the screen went blank within a minute. After powering on, I decided that I will not be using split screen mode again, but the screen eventually went blank. I monitored the CPU temperature and it didn't seem like it was running too warm (50ish C). I will try re-calibrating the battery (if that's even possible) and even replacing one, but if that doesn't help I guess it's time to move on to something new. Sadly, four years after the T800, nobody made a worthy replacement (the leaked Tab S4 specs look good, but they want to charge laptop prices for that).
PS: It's running the stock rooted (later unrooted) MM 6.0.1 from November 2016 with TWRP.
I re-calibrated battery and the tablet seems to be working fine so far.
https://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
Okay first of all very big thank you for your replies
my Galaxy Tab S 1 except strange reboots is also overheating when it has some tasks to do measured temperature on CPU cores is getting around 80 degrees Celsius and is going up and then tablet gets restart so I don't know if it is only the problem with battery maybe it's connected with CPU problems or other electrical problems on MotherBoard.
It's worth to mention, that I've charged the tab with charger from Moto X Style, that is Turbo Charger, with 3A, and the Tab S1 can load with 2A only.
https://youtu.be/APgivhY31ws
Here's the link to movie with Tab behaviour again, can you see it now?
Astania said:
Okay first of all very big thank you for your replies
my Galaxy Tab S 1 except strange reboots is also overheating when it has some tasks to do measured temperature on CPU cores is getting around 80 degrees Celsius and is going up and then tablet gets restart so I don't know if it is only the problem with battery maybe it's connected with CPU problems or other electrical problems on MotherBoard.
Click to expand...
Click to collapse
My tablet used to have a damaged main-board that used to overheat. However, the screen did not go blank when that happened. I actually got some kind of message that said that the tablet is overheating. This was fixed after I replaced the mainboard. You can certainly try it, but these things were not cheap when I did it.
Mine also started doing this last month now it wont power on but resets till the battery is dead.
Did you get it fixed?
Akopps said:
My tablet used to have a damaged main-board that used to overheat. However, the screen did not go blank when that happened. I actually got some kind of message that said that the tablet is overheating. This was fixed after I replaced the mainboard. You can certainly try it, but these things were not cheap when I did it.
Click to expand...
Click to collapse
I'm seeing random shutdowns with no warning popup on heat but the screen area where the motherboard is sure gets hot. I replaced the battery and same result. I looked at the battery connector and looks OK, seems tight but I didn't check with a magnifying glass. Where did you source your motherboard?
Also how has everyone elese resolved this? I see people citing the problem on this old thread but I'm curioius if you found a resolution.
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
SuperGlueG4 said:
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
Click to expand...
Click to collapse
All devices up to March 2016 (so 603) are affected by the ilapo. Your story above sounds exactly like the ilapo. Read my signature for the ilapo fix list which may bring up some hours/days/months life back.
Sent from my LG-H815 using XDA Labs
SuperGlueG4 said:
My G4 was plugged in overnight to charge, and on the following day, I woke up to notice it was completely dead. Strange I thought because it wouldn't respond to anything (recovery/download mode, normal boot, etc.). I assumed it was just the battery's time to die so I ordered a new one off Amazon (PowerBear). I put it in the phone, and it started turning on. Whew, it's back... Right? Suddenly, the screen shuts off during the LG boot logo (before the animation). WTF? Now I'm back at square one. Phone doesn't respond to anything. A couple battery tricks where I take it out and hold the power button for 30 seconds can sometimes get it to show the empty battery screen when connected to my computer, but even that's very rare. If I try putting the battery in at this part, it shows a battery loading animation and then the phone freezes indefinitely.
I've tried multiple USB cables, computers, and A/C adapters. No matter what, I can't get the phone into recovery or download mode. My computers can detect the correct driver as the phone is dead but it still won't work in LGUP. I've also returned the PowerBear battery, arguably prematurely.
If it's of any relevance, I had my G4 screen replaced by a third-party repair store a month prior to this incident, and I find it hard to believe it's just a coincidence my phone dies not too long after. Based off what I know, this isn't a bootloop issue. My friend who works at another repair shop insists it's the motherboard but can't fix it since they no longer have an LG technician. However, before all this, my Android OS was acting super funky - "Android is upgrading 300 apps..." for 20mins upon each reboot, despite it being the latest software, and my data limits had a glitched out schedule where it thought the phone was in the year 2023 despite date/time being set correctly. I had plans to reset the software but not being able to boot the phone anymore has prevented it, obviously.
According to the serial number, the phone was manufactured in November 2015, which I believe is past the date of when the faulty G4s were distributed. So what gives!?
The freakiest part of this is that my iPhone 7 Plus - which was at 100% battery (unplugged) before I fell asleep, was completely drained when I woke up on the same day. I also have no idea what that's about.
Any and all replies are appreciated. Thanks for reading!
Click to expand...
Click to collapse
You need a new battery
deltadiesel said:
You need a new battery
Click to expand...
Click to collapse
Lol
Sent from my LG-H815 using XDA Labs
I had something similar happen, except it is a 2016 model, I believe, to sum it up:
The battery seemed to be starting to die, so I bought a battery of eBay, but it also was having pretty bad battery life, so I drained the battery, to calibrate it, but now my G4 (H812) refuses to show any sign of life when I plug it in, or try to turn it on, is it also the Ilapo/Bootloop issue, or something else?