Hi all
Apologies if this has been covered before, but I've done many searches and can't find something that matches my unique symptoms, that has pin pointed the root cause.
I've basically got an Australian model LG G3 (D855), and for about the last 3-4 months it has been randomly rebooting itself. It is generally (but not always) triggered when I'm undertaking an action (playing a game, taking a photo, opening an app).
It seems to have progressively gotten worse, to the point where lately it's at time going into an infinite loop, which can only be broken by plugging the phone in to charge it (often pulling the battery out and putting it back in does nothing, as it just continues to reboot once I power it on again).
The whole thing is very random. Some days it can go hours on end without happening. Others, it's every few minutes.
I'm beginning to think that it's battery related, but have read other reports of people with similar issues who have replaced the battery, but with no success, so am not sure. The phone is rooted and currently on a custom rom, but the issue predated the ROM (ie occured on the stock ROM also).
Any suggestions, advice, ideas would be greatly appreciated.
cheers!
So I ended up replacing the battery and problem solved (got someone to test the battery and it was completely stuffed).
/thread
I had the same issue and my phone getting random shutdown and only way to turn it on was to pull the battery.
I went to LG service center and they replaced motherboard without any tests.
And now the issue is gone. It seems LG is also aware about this issue.
Related
Completely stock T-Mo m8. Been running Lollipop since the OTA came through, and it has worked fine for the longest time, no problems other than a bit of lag, even after clearing the cache.
A couple of days ago, the phone began to shut down whenever (seemingly) any app was launched when on battery, and then would not boot on repeated attempts. It doesn't seem to make it past the first stage of the bootloader (first HTC screen, pre-animation), most of the time. Sometimes it will make it to the T-Mobile animation and then give up.
While plugged in, it boots and works fine 9/10 times, but sometimes gives some resistance to booting. If it is unplugged and any apps are launched, it shuts down as if the battery were removed. Though, the whole while the battery seems normal, no weird fluctuations or sudden drops in battery level.
If it is unplugged after having booted and it is relatively inactive (no apps launched, or any processes, i.e. alarms, syncing, downloads, etc.), it will remain powered on.
I have attempted to Factory Reset a couple of times, and cleared the cache a couple of times. The problem persists. I can boot into recovery, though I am not rooted.
Is my battery in need of a replacement or some such? I would like to remain fully stock if at all possible. I may be able to get a replacement phone out of T-Mobile, but would also like to avoid that.
Try to RUU. Otherwise, it may be a battery or other hardware issue. In that case, a warranty replacement is probably your best course.
Agree that modding the phone is not recommended, since the phone is fully stock, and it looks to be a hardware defect of some kind (covered under warranty).
Ah! It's been so long since I've even had to connect my phone to the computer that I'd completely forgotten that RUU is an option.
I'm trying it now, thanks!
So this issue has been happening randomly over the last two weeks and suddenly it started to happen on specific times.
Basically what happens is that my phone reboots when I open Snapchat or get a message on Messenger and I press on it right as I get it. It seems to also happen when the CPU jumps up a notch.
I think it is the battery because when the phone is plugged in and charging, it never reboots even if I open Snapchat. As soon as I remove the charger it will reboot while still in Snapchat...
As I said, I think the battery is faulty but I do not know how to be sure. Is there any apps or ADB commands to check my battery wear etc? I need to fix this because I need my phone everyday for school (doing a project which makes me need my phone all the time for verification), and I am waiting for the Moto X Style.
I've tried different ROMS and different kernals but nothing helped.
So it's surely caused by battery health.
Try to replace them in warranty, or try the better Mugen battery.
If the problem persists, you sadly have to return to stock and look for LG assistance.
I'm currently on stock because I thought something was wrong with my ROM. But as I will get a new phone next month I really can't be bothered to send for warranty. Weird part is that my friend who has a LG G3 also has the same problem but he hasn't rooted nor installed any new ROM...
Hi all,
I have been running my Z1 Compact on 4.4.4 for the longest time, mainly due to sound issues after updating to Lollipop.
Recently, the battery has been dropping randomly from 60 odd percent to 3 or 4 and then shutting down all within a few seconds. The last time it did this, I tried charging it when I got home but the charging light would not stay on, thus it was not charging. All typical signs of battery failure due to age.
Having already replaced the battery successfully on my Z1, I bought a replacement original Sony battery and replaced it. The problem persisted. On first boot, the phone got to the blue waves then black screen, and power off. Charging screen just showed the battery at about 40%.
I risked it and flashed the latest software with Flashtool, having done a complete wipe. The result of this proved no better, but I did get a different message on the charging screen, a message saying the phone had shut down due to overheating. Picture is attached.
The phone is in no way overheating and I've even booted it while sat on a shelf in the fridge to help dissipate any heat generated but with no luck.
So, the old battery maybe did overheat and caused the phone to shut down, I'll accept that as a probability. It may have even damaged something, but I don't think that's likely.
After changing the battery, I would have expected the problem to resolve itself, but it seems like some kind of hardware 'flag' has been raised that is now not allowing the phone to boot in case it overheats again.
Does anyone know of any way to resolve this, reset the 'flag' per se, other than going to Sony? The phone is definitely out of warranty due to its age, never mind me taking the back off lol
It is a shame because it has been a great phone over the years, and I would like to fix it if possible, even if to give it to one of the grandkids. I have my Z3 still (which I won't part with for anything) and I have an XZ too and both are great phones. I would just like to save the XZ1c if I can.
The phone is not, and has never been modified in any way, no rooting, no bootloader unlocking. Only stock roms have ever been flashed, and then only once or twice, to put it back on 4.4.4.
I have tried reflashing just the kernel, or just the system too, to no avail.
In desperation I even left it in the fridge for a few hours in case the temperature sensor was on the fritz, but that did nothing at all.
I just feel like there's nothing actually wrong with the phone, apart from this trigger that won't reset.
Any help greatly appreciated of course.
Thanks,
Mick
Maybe theres lot of consideration:
1. Rom Bugs
2. The Kernel not supported well
3. Battery Issues (But you already change it right)
There are two temperature sensors afaikin our phone. One in the SOC and another one in the battery (hence three pins).
The battery is probably the one giving the high temp report. Try yet another battery.
A bad battery normally heats up very fast inside and the battery temp sensor stops the battery from charging and/or working to protect the phone and the battery.
I changed my battery before when it had symptoms like yours 100-90-0 drop and after replacing with a battery from eBay it was OK. I gave it a full charge then complete discharge and then complete charge to full cycle the battery once and let the phone Guage its full capacity. one year later now my battery is acting funny again (not charging past 30%) and getting so hot when charging it triggers overheat control service in Android.
Any luck?
Apologies for the necro. But did you ever fix this issue, having the same problem
Karter Ires said:
Apologies for the necro. But did you ever fix this issue, having the same problem
Click to expand...
Click to collapse
No, I never did figure it out. I've been loathe to spend more money on another battery when I've got other much newer phones. I really have no idea why it would not reset once the battery was replaced, maybe it's the replacement battery.
Have you tried changing the battery?
I've tried flashing different stock roms, Kit Kat, Lollipop, and it doesn't help.
Short of going to Sony, I'm not sure what else to do.
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
So I've had this phone for about a year now, loved it (other than the lack of custom ROMS but that was my own fault for not doing enough research to begin with..) Anyways, to the problem..
The phone ran completely fine for about 6 months, no issues whatsoever. Then, I cracked the screen while working (oops). I consider myself at least a bit knowledgeable when it comes to phone repair, as I have done many in the past successfully. I purchased a new screen off E-bay, and installed it. No issues other than it had a few weird spots on the screen but it was bearable so I was living with it. About a month later I started having charge port issues. I had to prop it up certain ways to get it to charge, etc etc. I looked it up and apparently many people had this problem. It was running fine still for about another month until the strangest thing happened that I've never seen before.
The batter would immediately say 100% when I first plugged it in, and after powered on, it progressively brings itself down to 0% and then dies completely. Never seen it before and couldn't find anything about it on the internet really.
I figured that it was probably just the battery crapping out on me, so I thought, if I'm going to keep this phone (can't really afford a nicer phone right now), that I may as well purchase a new charge port and battery and repair them both.
The repair went flawlessly. The charge port works again perfectly but the battery problem still remains. It still says 100% and gradually goes down to 0% and dies.
What is going on here? Any ideas? I am now trying a system restore (my phone was encrypted so I wasnt able to get into TWRP without remembering the password which I don't even remember putting on there). I did a wipe on the phone and now I am able to access TWRP just fine on my internal storage, is there anything that may be able to fix this? Assuming this is a software issue and not a hardware one? And if it is a hardware one, what could it be??
Thank you for your time!
EDIT:
I forgot to mention. About a day before the battery started doing this. I downloaded the magisk module "ACC" (Advanced charging controller), thinking it may be useful considering how weird my charge port thing was being. It completely made my phone unable to charge when plugged in. I disabled and deleted the module and it went back to the way it was before (it didn't have the weird issue of discharging constantly). The next day or 2 that's when it started discharging immediately and always says its at 100% when I first plug it in. Don't know if that's relevent or not but I figured I would add it.