Hi all,
My rooted (but otherwise stock) Optimus G was VERY low battery, I plugged it into a car charger and it looked like it was charging for a minute, unplugged it to try booting it and it booted halfway then died. Then it wouldn't charge (tried multiple chargers in different contexts). Had to send it back under warranty, they flashed my phone and said it was "software related" and sent it back.
It should be working once I get it back. But my question is:
HAS THIS HAPPENED TO ANYONE ELSE?
And my advice is: rooted or not, I'm guessing that having it die halfway through a bootup might have been the culprit here. So the lesson—I think—is not to let it deep discharge and, if you do, to charge it for 5-1o good minutes before booting it back up.
Unheard of for me, seems kinda freaky actually.
Sent from my LG-LS970 using xda app-developers app
Generally a battery pull will fix that. It's kinda a pain in the bum, but it fixed it for me! Amazing what a hardware reset can do lol
Sent from my LG-LS970 using xda app-developers app
This happened to me too.
I think it is kernel related issue. It happened to me when I was using LG based rom and kernel. I just flashed CM kernel thru twrp (I could boot into twrp luckily and I had CM kernel in my phone) and it charges like normal.
Don't let your battery go down to 0 when you are on LG based rom and kernel!
Sent from my LG-LS970 using xda app-developers app
Wasn't able to do battery pull b/c it would void the warranty (this is not a consumer-replaceable battery).
Wasn't able to access it via computer either, so that was no good. Sounds like there's some agreement—let LG phones hit 0% at your own risk!
I have had this happen a few times. Most of the time I've left it plugged in undisturbed for twenty minutes to an hour and it will boot. Try that first.
Once it wouldn't boot no matter what I tried but I could get into twrp and download mode so I used LGNPST and took it back to complete stock. This was obviously last resort but worked. Hope this helps. Good luck
Current Phones
Sprint Optimus G/Sprint Galaxy S3
Previous
Epic 4g/ myTouch 4g/iPhone 3g
Tablet
HP Touchpad
Related
So it began with my computer not being able to read my phone, my phone wouldn't even give me the option to connect as a storage device. Then my phone would still say its charging even when its not plugged in and now my device won't charge unless I jiggle the cable around hard when plugged in. My phone keeps going into car mode and opens up the annoying car mode menu when i'm in the middle of things. This is obviously a hardware issue, a weak contact somewhere. My question is will Sprint or Samsung repair my phone or am I now stuck with a broken SII.
They will repair you no problem.
Great news, thanks for the response I was pretty worried for a second.
Thank goodness someone else was having this issue.... Here's MY question...
I've rooted and flashed a few roms on my phone, and I've heard things about how Sprint looks at the "Odin count" ... i puchased a usb jig, do i need to reset my count before i take it in?
I had the same problem, was running un-named when I brought it to Sprint.
Because it was a hardware problem and not a software problem (with the phone being rooted) they ordered me a replacement.
I searched and searched when this first happened to me, I spent so much time going back to out of the box stock, then reloading everything to see it was a bad port.
Now this problem pops up more and more in here.
Try one thing, do a battery pull.
Mine would not boot without going to recovery after a pull, the screen would come on just like it was plugged in and charging.
question
did you even try different usb cords ? you really need to state what you have tried to do when posting something a bad usb cord will do everything you said
my1zamboni said:
I had the same problem, was running un-named when I brought it to Sprint.
Because it was a hardware problem and not a software problem (with the phone being rooted) they ordered me a replacement.
I searched and searched when this first happened to me, I spent so much time going back to out of the box stock, then reloading everything to see it was a bad port.
Now this problem pops up more and more in here.
Try one thing, do a battery pull.
Mine would not boot without going to recovery after a pull, the screen would come on just like it was plugged in and charging.
Click to expand...
Click to collapse
Perfect, thanks! I've tried battery pulls, and reboots and it will return me to normal, but then it happens again... Going to the store now!
Does anybody still use Odin? Just seems so old school.
Vegasrich said:
Does anybody still use Odin? Just seems so old school.
Click to expand...
Click to collapse
I use mobile Odin does not add to the flash count and does same thing but better.... The pro will root it while flashing it
Sent from my SPH-D710 using xda premium
Epix4G said:
I use mobile Odin does not add to the flash count and does same thing but better.... The pro will root it while flashing it
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I have read in this forum before of people trying to inject SU in a stock OTA update and not having it work and getting stuck. Ha e yoy had success with Mobile Odin working as far as injecting SU into a OTA update?
Sent from my SPH-D710 using xda premium
bluefire808 said:
I have read in this forum before of people trying to inject SU in a stock OTA update and not having it work and getting stuck. Ha e yoy had success with Mobile Odin working as far as injecting SU into a OTA update?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yes I have done it multiple times and never had it mess up. I an running Cm7 with no triangle on boot...
Sent from my SPH-D710 using xda premium
Hello,
I have been fairly involved in following this forum, and I think it is undoubtedly the best resource for this phone on the internet. Take a minute to hear my plight:
I bought an ET4G the day it came out in the States. I have tried several custom roms and play with kernels all the time.
About, I'd say...2 months ago, the phone started rebooting itself once a day. Sometimes, the screen lights up by itself while the phone is sitting untouched! The problem got progressively worse, until the phone was rebooting 15 times a day. I installed a fresh stock ROM (rooted), a NEW battery, and the problem went away but started to slowly creep back. At this point, I went back to the stock kernel (was using Agat's), and the problem STILL HAPPENED.
So, I installed a fresh stock ROM, this time unrooted, kept TouchWiz instead of Apex, and did not install any freaking apps, except for the BARE minimum. This time the phone did not turn off. It seemed to have fixed my issue. My speculation was that my phone, for some reason, didn't take the voltage under load quite well. So, I spoke to my friend (who is a Store Manager at a corporate Sprint store,) and he was very kind to help me out in getting an exchange so that I could use the phone the way I was using it (after all, I was still within the 12-month warranty).
It's now been 1 week, and the only modifications I've made have been to install Agat's kernel. THE PROBLEM HAS COME BACK in the replacement phone. So, as a last resort, I undervolted the damn thing -50mV, and even went ahead to underclock it using ExTweaks to 1100 MHz. STILL HAPPENS. I go back to stock kernel, uninstall all tweak apps, STILL HAPPENS.
So, I install a fresh ROM, it gets fixed, gets progressively worse, and then THE PROBLEM COMES BACK.
I'm going crazy, XDA. I just want to have a working phone until July 1st when I can upgrade. Is there any way I can diagnose what exactly the phone is doing when it reboots by itself, and what it's doing when the screen wakes up by itself when untouched? Other tips, suggestions, or anything else that could lead to a resolution?
Note: The phone reboot slightly less often when using stock kernel vs. the latest Agat kernel (0.6.7). It also appears to occur less often when I use default touch-wiz. Lastly, the problem goes away after a flash for almost 24 hours, and then it starts creeping back.
Why did you use undervolting as a last resort if your phone had problems? It would only make things worse
Sent from my SPH-D710 using xda premium
locoboi187 said:
Why did you use undervolting as a last resort if your phone had problems? It would only make things worse
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I mean, I've had the new phone for a week. I haven't done anything crazy with it, and it's already doing weird stuff.
I never over-clocked either of the phones, and once I learned under-clocking was known to help, I tried that last.
There has to be a way to diagnose this thing:
I've been monitoring the last seen services before shut-down, and the last 2 active services on the last shut-down were:
1) [dhd_dpc]
2) system/bin/surfaceflinger
My phone did that and I ended up getting a replacment. Stupid referb had a problem with the CPU. New phone works perfect
Sent from my SPH-D710 using xda premium
m4xwellmurd3r said:
My phone did that and I ended up getting a replacment. Stupid referb had a problem with the CPU. New phone works perfect
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I will return the phone to the store once again in hopes that a replacement gives me a better experience. I'll report with updates.
So, when i try to lgnpst back to stock i can never get it to complete. It stays at 85% and says it lost the connection to the phone, reboot, plug it back in and press ok but it just doesn't work... What is everybody else doing to get it to go through fully to 100%?
Sent from my LG-LS970 using xda premium
If LGNPST errors out at 85%, turn your phone off and hold the power button until the phone powers on, then release.
This is according to PhantomPhreak53's instructions. Part of his LGNPST download from the irc.
Not sure if it'll help, but ya never know.
kayslay21 said:
So, when i try to lgnpst back to stock i can never get it to complete. It stays at 85% and says it lost the connection to the phone, reboot, plug it back in and press ok but it just doesn't work... What is everybody else doing to get it to go through fully to 100%?
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
This happened to me 3 times, but all 3 times it just rebooted my phone like normal. All 3 times
Sent from my LG-LS970 using xda app-developers app
Yea i tried that too and doesn't do anything, i only got it to complete once and that was the first time i ever used lgnpst, but couldn't get it to complete fully since then
Sent from my LG-LS970 using xda premium
10. If LGNPST errors out at 85%, turn your phone off and hold the
power button until the phone powers on, then release. DO NOT
disconnect the cable before LGNPST is done doing its thing.
Your phone may reboot. This is OK.
I got this from carrett's guide in the ATT lgog thread.
BTW did you get your phone fixed?
Sent from my LG-LS970 using xda premium
It works even tho it doesnt complete fully, and I still couldnt get it to finish lol but whatever, we`ll have a rom to flash soon enough
Sent from my LG-LS970 using xda premium
it works even if stuck at 85 percent.
kayslay21 said:
It works even tho it doesnt complete fully, and I still couldnt get it to finish lol but whatever, we`ll have a rom to flash soon enough
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
yeah you are right. it worked on my lg e970.
when it was stuck at 85 percent for me, i turned off the phone and turned it back on. then restarted the process. it stopped at 85 percent again but the phone rebooted and software was installed. awesome
Zantetsuken1983 said:
yeah you are right. it worked on my lg e970.
when it was stuck at 85 percent for me, i turned off the phone and turned it back on. then restarted the process. it stopped at 85 percent again but the phone rebooted and software was installed. awesome
Click to expand...
Click to collapse
sometimes it stuck at 65% but after reboot suddenly jump to 85%, but completed at 85% kinda weird :laugh:
Yeah Ive never seen it get to 100%. The running joke was that 67% or 85% must mean 100% in korean. That's as far as it has ever gotten for me but it has always worked if I just reboot the phone manually. Whether it's a teenybin or stock, once the phone turns back on, it's how I wanted it. Somewhere in the instructions for lgnpst on irc it even states that. It does say the phone should reboot when it gets to 85 but mine never did, I just did a hard poweroff then power back on and my phone turned on as if I had just bought it(when using a full stock bin).
HPTesla said:
Yeah Ive never seen it get to 100%. The running joke was that 67% or 85% must mean 100% in korean. That's as far as it has ever gotten for me but it has always worked if I just reboot the phone manually. Whether it's a teenybin or stock, once the phone turns back on, it's how I wanted it. Somewhere in the instructions for lgnpst on irc it even states that. It does say the phone should reboot when it gets to 85 but mine never did, I just did a hard poweroff then power back on and my phone turned on as if I had just bought it(when using a full stock bin).
Click to expand...
Click to collapse
☝what he said
Sent from my LG-gee using xda app-developers app
Hello,
I know there are countless threads about the battery issues, but im having a hard time trying to find a solution for my problem.
My battery drain insanely fast, even on idle. I can barley get 5-6 hours on my battery. Standard usage, some Internet, texting etc. I have all the pre installed apps disabled, and have most apps I downloaded on manual sync.
A friend of mine had the same issue and replaced the battery and the phone is back to normal. I replaced the battery and still have the same issue.
It takes a long time to charge, sometimes I leave charging while the phone is off, and come back am hour later and it barley charged 3%.
Please I need some help, any suggestions are welcome.
Thanks in advanced.
Sent from my SGH-I747M using xda app-developers app
How long have you had the phone and when did this start happening? Are you stock? If you're running a custom rom, when did you flash it (or any updates)?
I've had it since early September.
Same rom, using 4.1.1. Never been rooted.
Sent from my SGH-I747M using xda app-developers app
It sounds to me that software-wise your phone's battery should be working correctly, especially if you've disabled so many apps and never rooted. I think it's a defective battery. If you don't want to spend too much, you can buy 3rd party replacement batteries, but they probably won't have NFC.
I've already replaced the battery. I got the same battery my friend got when her s3 was having the same problem... Now her phone is fine and mines still isn't.
Sent from my SGH-I747M using xda app-developers app
equinox24 said:
I've already replaced the battery. I got the same battery my friend got when her s3 was having the same problem... Now her phone is fine and mines still isn't.
Click to expand...
Click to collapse
Ok. That's not good. Assuming you've tried factory resetting the phone and it still didn't do anything, I say go back to carrier store and get a replacement phone. Something obviously isn't right. Phone hasn't been out a year yet so it'll fall under manufacturer warranty. I had to get mine replaced a month ago for another issue.
equinox24 said:
I've had it since early September.
Same rom, using 4.1.1. Never been rooted.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
.... uhmmm... LOL thats your problem there buddy.
So, I went to look at the time on my phone and it wouldn't turn on. I held down the power button and the back & home buttons just blinked a few times but it didn't turn on. I plugged it into the charger and it's not charging, no LED light or anything, and it won't turn on.
Does anyone know what could have happened or how to fix it?? I noticed earlier it was running a little hot after some app updates. could that have something to so with this? Is my phone dead??
There have been several reports as of late where the same thing has happened. Were you running a custom Rom and kernel?
What recovery were you running?
Sent from my Lunar Ecliptic One.
brymaster5000 said:
What recovery were you running?
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse
How come this would be caused by a recovery issue? My phone died just today because I forgot my charging cable at home. I charged it up just fine. If the recovery was the issue I wouldn't have been able to charge my phone up after it died. He overheated his phone which seems to be the link to every other case of this happening.
Recovery "might" be an issue, as if recovery cannot respond to a "power on" it will not turn on. Most recoveries will respond to a "adb reboot" command. That may fix his issue... If his PC recognizes the device. I know certain TWRP had issues with the DNA and it could have bled to the m7
Sent from my HTC6500LVW using XDA Free mobile app
Wouldn't this happen a lot more often if the recovery caused in considering that people run out of battery all the time?
disconnecktie said:
Wouldn't this happen a lot more often if the recovery caused in considering that people run out of battery all the time?
Click to expand...
Click to collapse
Depends if they are using a commonly used recovery, or if the MD5 matched. I never let my battery go below 30% as most users should try their hardest to not also, fully draining li batteries drastically reduces their life and capacity.
Edit: it is also good to see everyone's setup who has this issue so we can find the common thing every time it happens.
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
Depends if they are using a commonly used recovery, or if the MD5 matched. I never let my battery go below 30% as most users should try their hardest to not also, fully draining li batteries drastically reduces their life and capacity.
Edit: it is also good to see everyone's setup who has this issue so we can find the common thing every time it happens.
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Yea I generally try to not get way to low. It's a scary thought though that if you happen to forget to charge your phone it might not charge back up. That's why I was interested in what rom and kernel he was using. Plus it seemed to be that most of the people who couldn't recharge had an overheating issue before hand which is more or less why I don't believe it is a recovery issue.
Ok, for some reason it's working again. As I said before, it was just completely dead (wouldn't power on, no LED light when plugged into two different chargers, two different outlets) then I tried again about an hour after all the problems started and it powered on again.
When it came on, it had a 70% charge, so I put it back on the charger and charged it back up to 100%. However, after about two minutes being unplugged, it dropped down to 95%. It's never done anything like that before and this is the first time I've had any kind of problems with it in the year I've had the phone.
Could this have been some sort of temporary battery issue? I'm so confused. Are there and diagnostic tools I can use to try to figure out what happened?
I'm using NuSenseONE-Max_RC6_111313 (4.3 based), not sure what kernel and TWRP recovery. Also, I usually drain the battery down to 15% before I charge it.
Also, this happened after I updated about 20 apps.
JGress said:
Ok, for some reason it's working again. As I said before, it was just completely dead (wouldn't power on, no LED light when plugged into two different chargers, two different outlets) then I tried again about an hour after all the problems started and it powered on again.
When it came on, it had a 70% charge, so I put it back on the charger and charged it back up to 100%. However, after about two minutes being unplugged, it dropped down to 95%. It's never done anything like that before and this is the first time I've had any kind of problems with it in the year I've had the phone.
Could this have been some sort of temporary battery issue? I'm so confused. Are there and diagnostic tools I can use to try to figure out what happened?
I'm using NuSenseONE-Max_RC6_111313 (4.3 based), not sure what kernel and TWRP recovery. Also, I usually drain the battery down to 15% before I charge it.
Click to expand...
Click to collapse
That almost sounds like your battery might be going out but maybe you should update your rom and recovery just out of precaution. You'll need to update your firmware as well since you're probably still running jb firmware considering the age of that rom.
disconnecktie said:
You'll need to update your firmware as well
Click to expand...
Click to collapse
Wait... I thought a ROM and firmware were the same thing.
JGress said:
Wait... I thought a ROM and firmware were the same thing.
Click to expand...
Click to collapse
Not exactly. Grab the firmware from here
http://forum.xda-developers.com/showthread.php?p=46506592
It's version 5.x.605 something lol
Get the one that has no boot and flash it per the instructions in the op. Then grab an updated recovery. I use version 2.7.1.2 from here . http://mdmower.cmphys.com/twrp-m7vzw/ you're more than welcome to flash whatever you like philz or cwm. Then grab a newer rom. Kit Kat has been way better than jelly bean in my opinion.
On the battery dropping to 95% quickly, this is a known software "feature" in android since froyo or earlier. When the phone is fully charged, power cuts off from the Phone and won't "charge" until it hits 90%. System will still show you 100%. It has been proven by many sources that keeping a "trickle" on a fully charged battery will damage it. That is why it probably dropped quickly. Only way to determine if battery is faulty is have it drop below 89% and see it's drain.
Sent from my HTC6500LVW using XDA Free mobile app
disconnecktie said:
Not exactly. Grab the firmware from here
http://forum.xda-developers.com/showthread.php?p=46506592
It's version 5.x.605 something lol
Get the one that has no boot and flash it per the instructions in the op. Then grab an updated recovery. I use version 2.7.1.2 from here . http://mdmower.cmphys.com/twrp-m7vzw/ you're more than welcome to flash whatever you like philz or cwm. Then grab a newer rom. Kit Kat has been way better than jelly bean in my opinion.
Click to expand...
Click to collapse
Ok, thanks for the help!
Does the One maybe have an auto-shutdown feature that triggers if it overheats? I was thinking that was a possibility.
disconnecktie said:
How come this would be caused by a recovery issue? My phone died just today because I forgot my charging cable at home. I charged it up just fine. If the recovery was the issue I wouldn't have been able to charge my phone up after it died. He overheated his phone which seems to be the link to every other case of this happening.
Click to expand...
Click to collapse
Just trying to get the full picture as uzephi said. Just was wondering because there are instances where it can die and if the recovery had a glitch and or missed a charging binary in one build it might not charge...
Sent from my Lunar Ecliptic One.
brymaster5000 said:
Just trying to get the full picture as uzephi said. Just was wondering because there are instances where it can die and if the recovery had a glitch and or missed a charging binary in one build it might not charge...
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse
I understand. I asked because I didn't understand why this would be a recovery issue since you can't always keep your phone from dying and having your phone brick as a result would completely suck. Plus, it would be a lot more frequent (you would think anyway) for this same thing to happen. I wouldn't want to use whatever recovery had this issue either. However, I think he just really needed to update his firmware, rom and recovery. I'm surprised he made it this long without needing to upgrade. It also helps knowing all the info because if it was a rom/kernel issue the dev could take a look into what could potentially cause the overheating because the thermal protection written into the kernel isn't doing its job if it allows the phone to overheat to death.