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?
Related
I've got a TMOUS TP2 which appears to be stuck in a reboot loop of sorts cause I can't charge the battery.
I've read through the forums and I saw a few similar problems like this but it seems like it those they were stuck at the bootloader, and that's not the case for me.
Basically the battery was down to 14% and I turned off the phone last night intending to charge it this morning. Somehow the battery dropped to 1% by the time I went to turn it on this morning, and it shutdown (really just lost power) right after I started it. So I go to plug it into the wall charger and then:
charge light comes on
after a few seconds charge light goes off
the phone tries to boot (does little vibrate, shows splash)
after the splash screen, phone loses power
charge light comes back on
then tries to boot after a few seconds.
repeat
If left unplugged the phone just sits there dead, but upon plugging it in, it tries to boot.
I've seen it where the phone doesn't have enough power to boot and just needs to be charged for a while, but I can't seem to do that here.
Anyone have any idea how to prevent it from trying to boot after the AC adapter is plugged in?
Thanks
arimp said:
I've got a TMOUS TP2 which appears to be stuck in a reboot loop of sorts cause I can't charge the battery.
Thanks
Click to expand...
Click to collapse
If you're desperate...you might try doing a hard-reset.
Why would that help? I don't know...except sometimes when really stuck it helps to just change the situation...try something completely different.
Of course, a hard-reset deletes all data and applications that you've put on the phone, which is why I suggested it as a recourse if desperate.
Probably keep the phone plugged in while doing hard-reset.
Same problem, solved by itself
Hi,
I had a similar problem with a standard TP2, it was clear a battery fault. Phone was working well with a new battery and, of course, another working phone couldn't boot up with the faulty battery.
I took out the defective battery and let it aside for almost 2 weeks. After that it started to work, but the capacity is clearly smaller.
So from my experience, a hard reset wouldn't help you.
Radu
nradu said:
Hi,
I had a similar problem with a standard TP2, it was clear a battery fault. Phone was working well with a new battery and, of course, another working phone couldn't boot up with the faulty battery.
I took out the defective battery and let it aside for almost 2 weeks. After that it started to work, but the capacity is clearly smaller.
So from my experience, a hard reset wouldn't help you.
Radu
Click to expand...
Click to collapse
Yes, it goes without saying -- though it's good you did -- that if you have access to another battery that's an obvious thing to try first.
The hard reset is worth trying, in general, for otherwise-unresolvable phone issues.
It's a dead battery. Same exact thing you describe happened to me. Granted, it was because of water damage but same symptoms. Thinking the phone was dead I went and bought a new one. Then I decided to try the new battery, bam, phone back alive. Returned the phone and bought a new battery. By the way, the dash2 battery fits as well. Tmobile stores didn't know it... But the connectors were the same do I tried in the store and it worked.
devis said:
It's a dead battery. Same exact thing you describe happened to me. Granted, it was because of water damage but same symptoms. Thinking the phone was dead I went and bought a new one. Then I decided to try the new battery, bam, phone back alive. Returned the phone and bought a new battery. By the way, the dash2 battery fits as well. Tmobile stores didn't know it... But the connectors were the same do I tried in the store and it worked.
Click to expand...
Click to collapse
So it was indeed a dead battery. Oddly I found someone who had a CMDA TP2 from Verizon (mine is GSM TMO), and was able to pop my battery into their phone for a minute or two and charge it to about 5%, then put it back in my phone and all was well. With their phone, plugging in the charger did not cause the phone to start up and then power cycle.
That's really weird "glitch" if you want to call it that. So mental note, don't let the battery run down too far.
Hello people
A couple of hours ago, my phone shut down due to empty battery. I came home, plugged it in and booted it, all was fine. At about 60% I shut it off and went to have lunch, when I came back and tried to turn it on, I couldn't.
Led was orange at the time, I unplugged the power cord but the led stayed on! I removed the battery to be able to reboot it, but when I re-inserted it I still wouldn't boot.
Now no matter how I try to charge it, led stays off like it's not charging. Tried various different cables/chargers, the same. Tried to plug it to the charger without battery but no led flashed. Tried to boot without sim/sd card, still the same.
Any ideas?
My battery has never been changed (for a year now) and has had a bunch of full drains. Could this be a dead battery? :/
Well seems the phone is fried... I tried two more official batteries and no go...
Sorry to hear it. I thought that at first when I read your thread but I thought because I am not the most experienced person here, there might be some kind of fix.
HTC will most likely if not certainly replace this handset for you, seeing as it just happened out of the blue.
Well I certainly hope so, problem is I suspect it's an import (from another European country) and local HTC service generally does not do well with European imports.
Anyway I'll give it a try, meanwhile I'm getting a sensation soon
I have a similar problem.
I'm lucky that my girlfriend has the same handset as I do, the I could compare the phone abnormal behavior tho that of her properly working phone.
The first thing I've noticed, after a while when the charger was attached, was that the phone is very hot and that the battery keeps draining out in a surprisingly high rate.
After a while I've noticed that even when the phone is turned off it wont recharge. Sometimes the Orange LED is on when recharging while it is off, and the LED stays on for a few seconds after removing the charger, as if it was still charging. Note that the affects of connecting the charger to the phone, are mainly the ones listed below (not necessarily altogether)
* The phone indicates as if it recharges.
* Going to an infinite loop of rebooting and crashing.
* Getting hot when power supply is plugged, or at any time when the phone is turned on.
Ultimately the battery was empty, and the only way I had to keep using the phone (mostly to diagnose the symptoms listed here) was to swap the battery with the one of my girlfriend's device, and charge my battery in her device while using her's. That's the place to mention that the battery works just fine and that the phone is draining any battery, no matter what.
I took it apart to have a closer look at the source of all of the heat emitted while the phone is turned on, and it seem to come from the motherboard itself.
That's all I have.
The worst thing is that a friend of mine who helped me opening it up broke the pcb of the volume keys. Now I checked and It turns out that that pcb is actually part of the flex cable, which sort of extension of the motherboard and is mainly the second most important piece of hardware of all the phone parts (not that there are so many). If I would be able to expose the conductors inside the flat cable I might be able to solder an alternative volume pad I'll make out of old some miniature switches I have. The cable is very thin. any Ideas of how to expose the relevant conductors without ripping the cable apart?
Just a (late) update:
It's been almost two years, I had given the phone to a close friend of mine after a couple of weeks since writing the first post, just in case he could resurrect it, nothing.
Then, a couple of months down the road, the phone suddenly woke up! He tried to connect it with the charger, after months of not being able to charge or boot it up and somehow it worked. And it has been working flawlessly ever since.
I just got it back to give to my girlfriend until her sensation is fixed, flashing Viper now
In case something like this happens to any of you, don't give up!
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!
Hello, I'm new to the forum and I may need your help for a problem I've had today. I've been an happy owner of a Nexus 5X until this morning, when I was regularly using it while on charge and at one point it freezed for a few seconds with the screen still on. I pushed the standby button, the screen went off and from then on it was completely bricked. No signs of life, nor access to recovery mode via bootloader. Nothing. Already tried all the possible physical buttons combos, nothing.
It was on Android 8.1 (beta, very happy about that by the way), no root and with locked bootloader. I did some flashing experiments one year ago but in the end I reverted it back to totally stock and I haven't had issues ever since. Never had bootloops or similar problems, it just happened all of a sudden.
Hope to receive your help, by the way it should still be under warranty, so let's see...
Thanks for your help.
Same problem heare. I tried to install the factory image but now, the phone is completely death.
I beleve thet it was a android 8.1 issue because it was not a bootloop problem.
Same problem heare. 8.1 need a reboot but now, the phone is completely death
It might be an 8.1 issue then. By the way, being under warranty I sent it to customer assistance. I've had some signals of life before this morning though. The LED was flashing red indicating very low battery. I connected it to the charger and followed the instructions by Google themselves:
"If you see a red light, your battery is fully discharged. If the red light is flashing, there isn't enough power to turn on. Charge your phone for at least 30 minutes before restarting".
This seemed to resemble my case, so I waited for about 40 minutes (by that time the charging battery icon did show up with the phone still off) and tried to turn on. The only thing that I got has been the Google logo before the boot animation for a few seconds. Then the screen has gone off again and back to death.
From your comments it seems it might be an 8.1 related issue. Watching videos on Youtube about 5Xes with similar behaviours I was actually thinking about a motherboard failure, or a battery failure (the latter is more unlikely though). Disassembling and heating up the motherboard providing a temperature shock seemed to be a decent temporary solution to bring it back to life. I have warranty though so I sent it to assistance, we'll see... I'll probably unenroll my phone from the beta program just to stay safe.
Thanks for your answers.
My nexus 5x had same issue. A few weeks after 8.1, it totally bricked. I was able to get bootloader on once, but it was locked and fastboot didn't see it. Then after i let it discharge, I haven't been able to get it to recharge or get to boot screen at all. I bought another nexus 5x, but bit worried that 8.1 will kill it.
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