Related
I've searched the forums and have not seen anything quite like my problem, so if I missed an important thread, I'm sorry.
Over the weekend, I plugged my Captivate (using a stock battery) into the official Samsung charger and overnight my roommate semi-dislodged the charger. When I woke up and grabbed my phone it only registered a few hours of charging yet still had almost full battery. Upon rebooting the phone, I was sent into a bootloop. Not at the ROM, not at the Kernel, not even at the bootloader. It goes so far as to show the white loading ring at the center of the screen which never moves. At one point, a thin pink line appears halfway through the screen as it shuts down and reboots, never making it any farther. If I plug the phone in, it will boot normally though it does not accurately report battery levels or charging.
Other oddities: after 5 minutes of a phone call, the phone hard crashes. Not FC's, but just goes black. Upon a reboot, I get stuck into the same boot loop. If I plug the phone into the wall charger without a battery, it will go into the turned-off charging animation and show a 100% charged battery. Furthermore, my other roommate has a brand new i9000 so I tried that battery (again, stock Samsung) and it continues in the same bootloop. I have tried flashing other ROMS and going back to stock, but that does not seem to help.
Other info: I was running OneCosmic's ICS 3.1 with no overclock and light undervolting at the time. It was perfectly stable for the few days until the charger dislodged. I am also out of warranty and am not eligible for a hardware upgrade so repairing my Captivate would be ideal. I also have a usb jig if that is of any use to this scenario.
Has anyone experienced anything remotely like this? If not, what debugging steps should I attempt?
What I would suggest is using one of the ODIN one clicks and flash back to stock
Sent from my SGH-I897 using xda premium
I've flashed back to Rogers 2.2 stock. Doesn't help. It actually made it harder for me to get the phone started though I have yet to make a phone call from it.
Have you had the phone for less than a year? if so call at&t(or rogers) and they'll replace it for you.
then try factory reset
then try using odin or rom manager to flash back to stock
When all else fails, flash to cm7. that will completely wipe everything and start from scratch.
if that STILL dost work.... than you can be sure that its a hardware problem :/ theres nothing you can do except replace and sell for for parts.. sorry
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Skoffer said:
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Click to expand...
Click to collapse
I have exactly the same problem, I did the reset of the battery stats and still not working.
Did you solve the problem?
thanks
Martin
Thanks to everyone for their suggestions, however, no amount of battery calibration could get it to work. Furthermore, a bad flash has made the situation even worse. Now Im bootlooping even when plugged in and when unplugged my jig is of no help. I have declared my Captivate dead.
Best of luck toominds, if you get it to work, let me know. I'd love to have a spare phone sitting around.
So my phone shut off yesterday due to loss of battery power.
However, when I went to charge it, it would not charge when it was off.
IE: The battery picture with the "goo" in it that fills as it charges.
So since it wouldn't charge I was stuck at the a bootloop at the logo. Not animation.
Luckily my buddy at work has a Bionic that I was able to stick my battery into and charge. If not for that I would have been screwed.
Now I know I have personally a MILLION posts due to this problem and I'm wondering.
Who else can't charge while the phone is shut off? Is this due to CWM on boot? Our modded ROM's? If this is true for you, are you rooted? Stock ROM? CWM on boot?
We should really find a way to fix this. We need to be able to charge while the phone is off. This would save a lot of people headaches. Thoughts?
Fall of Enosis said:
So my phone shut off yesterday due to loss of battery power.
However, when I went to charge it, it would not charge when it was off.
IE: The battery picture with the "goo" in it that fills as it charges.
So since it wouldn't charge I was stuck at the a bootloop at the logo. Not animation.
Luckily my buddy at work has a Bionic that I was able to stick my battery into and charge. If not for that I would have been screwed.
Now I know I have personally a MILLION posts due to this problem and I'm wondering.
Who else can't charge while the phone is shut off? Is this due to CWM on boot? Our modded ROM's? If this is true for you, are you rooted? Stock ROM? CWM on boot?
We should really find a way to fix this. We need to be able to charge while the phone is off. This would save a lot of people headaches. Thoughts?
Click to expand...
Click to collapse
You CAN charge in this situation, but it is a real PIA, and you have to really keep playing with it until you get the sequence correct.
It is a little dance like this:
1) power off.
2) take the battery out.
3) plug the phone into the wall socket, not a usb computer connection, with the battery out!
4) HOLD the power button to turn the phone on
while the dual core screen comes up, hold the power button for a very long time, and the phone will eventually shut off.
5) put the battery back in the phone and put the back on, the phone may try to power on again, and you may have to due 1-4 all over again, or you can HOLD the power button for a VERY long time again until it powers off.
Now if it turns off, you should see the white light come on and that means it is charging.
Note the timing is key and you may have to play around to get it exact, because two of the different exchanges of my phones each had a slight different sequence to make it work.
jimbridgman said:
You CAN charge in this situation, but it is a real PIA, and you have to really keep playing with it until you get the sequence correct.
It is a little dance like this:
1) power off.
2) take the battery out.
3) plug the phone into the wall socket, not a usb computer connection, with the battery out!
4) HOLD the power button to turn the phone on
while the dual core screen comes up, hold the power button for a very long time, and the phone will eventually shut off.
5) put the battery back in the phone and put the back on, the phone may try to power on again, and you may have to due 1-4 all over again, or you can HOLD the power button for a VERY long time again until it powers off.
Now if it turns off, you should see the white light come on and that means it is charging.
Note the timing is key and you may have to play around to get it exact, because two of the different exchanges of my phones each had a slight different sequence to make it work.
Click to expand...
Click to collapse
Won't it also charge in stock recovery? I know that's not really off, but it is low power.
lkrasner said:
Won't it also charge in stock recovery? I know that's not really off, but it is low power.
Click to expand...
Click to collapse
Not sure, I have never tried it. I have however done what I have mentioned during a boot loop MANY times now, and never had an issue. Once you figure out the EXACT steps it takes, it just becomes second nature. Oh and like I said, it can be just slightly different even between two different A2s, but it is only like a millisecond here or a slight step there, that is different, or maybe when the battery goes in and or comes out of the phone...
I can assure you though that it does work to get you a full charge before a flash after and during a boot loop.
jimbridgman said:
Not sure, I have never tried it. I have however done what I have mentioned during a boot loop MANY times now, and never had an issue. Once you figure out the EXACT steps it takes, it just becomes second nature. Oh and like I said, it can be just slightly different even between two different A2s, but it is only like a millisecond here or a slight step there, that is different, or maybe when the battery goes in and or comes out of the phone...
I can assure you though that it does work to get you a full charge before a flash after and during a boot loop.
Click to expand...
Click to collapse
Good to know. I have a family member with the same phone, so when I kill mine and need to flash I just steal her battery for a few minutes.
So this happened to me again. Accidentally let the phone discharge. Not to worry, I'm not bricked. But now again I'm gonna have to charge my phone battry on my buddies bionic. BUT WHY WON'T OUR PHONES CHARGE WHILE THE IT'S OFF?
I shouldn't have to be paranoid if my phone dies.
I guess I never really got an answer to my OP, while I got it reconciled, it'd be nice to have an answer.
In GB, if your phone was off (powered completely down) you could plug it in, and the screen would come on with the battery that had the goo that would fill up as it charged. I seem to have lost this capability ever since I have rooted and started running custom ROMS. WHY?
So, four questions remain: Why is this happening? And is it happening to anyone else? If you're unsure, can you test it for me (see if your phone will charge while off) and most importantly. HOW TO FIX IT?
It's a little infuriating.
I've never had this happen to me. I know that's not helpful in your circumstance. My phone will shut off at the '0% battery level' and I can plug into my wall charger or USB to my laptop, and goo I get. I'm wondering if its your charger? The Moto chargers seem to be a little on the shoddy side. I've replaced all of mine with other non-Moto wall chargers. And as you know, if you're completely out of juice, USB may not have enough current to charge it back to full. Just my thoughts.
Sent from my Atari Falcon030
Thanks for the thoughts mate, but it doesn't matter what I try to charge it on? Will it charge for you no matter what ROM?
Fall of Enosis said:
So this happened to me again. Accidentally let the phone discharge. Not to worry, I'm not bricked. But now again I'm gonna have to charge my phone battry on my buddies bionic. BUT WHY WON'T OUR PHONES CHARGE WHILE THE IT'S OFF?
I shouldn't have to be paranoid if my phone dies.
I guess I never really got an answer to my OP, while I got it reconciled, it'd be nice to have an answer.
In GB, if your phone was off (powered completely down) you could plug it in, and the screen would come on with the battery that had the goo that would fill up as it charged. I seem to have lost this capability ever since I have rooted and started running custom ROMS. WHY?
So, four questions remain: Why is this happening? And is it happening to anyone else? If you're unsure, can you test it for me (see if your phone will charge while off) and most importantly. HOW TO FIX IT?
It's a little infuriating.
Click to expand...
Click to collapse
Ok I am going to answer this finally, for you....
The battery screen with the "goo" is a "boot hijack", we have stolen that ability to use it for CWM/bootsrtap and it's boot hijack replaces it. YOU CAN NOT LET YOUR PHONE FULLY DISCHARGE. When you get to less than 10% find a place to start charging it, or turn the phone off until you can connect it to a charger.
Sometimes we have to rob peter to pay paul, and in this case we "stole" that ability to get to CWM on a boot with either bootstrap and BP tools, or the J.Y.Daddy hack, but either of those steal this same boot hijack "space".
PERFECT JIM! Thanks man. I just wanted to understand why it was doing it. Thanks so much! Although that doesn't explain why Apex is able to charge lol. I figured since I was stock(ish) ICS that it wouldn't matter? Although I did use bootstrap to flash Altered's carrier remover zip. And maybe Apex is completely stock.
EDIT: I grabbed my buddies bionic to stick my battery into to charge, and his is rooted running a custom and they use safestrap as their recovery, however when his boots up, it boots into safestrap and then starts charging with the goo.
How come Bionic can do it and we can't? WAH!
That's interesting. Any idea why I don't have any problem from a full discharge-to-shut off and charge problem? I've not done anything that anyone else hasn't, I mean, I rooted, installed the bootstrap, J-Y-Daddy CWM, flashed myself silly, edited "this" and "that" and tweaked "these" and "those". Never found myself not being able to charge after a shut down...
Edit: I'm running Lithium v.1.3.1
Edit #2: Knocking frantically on wood! Hope I didn't just jinx myself!
Sent from my Atari Falcon030
Apex_Strider said:
That's interesting. Any idea why I don't have any problem from a full discharge-to-shut off and charge problem? I've not done anything that anyone else hasn't, I mean, I rooted, installed the bootstrap, J-Y-Daddy CWM, flashed myself silly, edited "this" and "that" and tweaked "these" and "those". Never found myself not being able to charge after a shut down...
Edit: I'm running Lithium v.1.3.1
Sent from my Atari Falcon030
Click to expand...
Click to collapse
You probably have something with the logwrapper and boot hijack link that is not fully correct... that is what actually does the boot hijack.
Here is where we started to think about this whole thing, just so people can see how we got to where we are with these hacks... yes this is quite old..
http://forum.xda-developers.com/showthread.php?t=1341198
jimbridgman said:
You probably have something with the logwrapper and boot hijack link that is not fully correct... that is what actually does the boot hijack.
Here is where we started to think about this whole thing, just so people can see how we got to where we are with these hacks... yes this is quite old..
http://forum.xda-developers.com/showthread.php?t=1341198
Click to expand...
Click to collapse
So, I'm wondering if that's a good thing or a bad thing. I suppose its good for the sake that I don't have the charging after dead issue, but could it pose any others? I've had things this way for 4 months...
Sent from my Atari Falcon030
Apex_Strider said:
So, I'm wondering if that's a good thing or a bad thing. I suppose its good for the sake that I don't have the charging after dead issue, but could it pose any others? I've had things this way for 4 months...
Sent from my Atari Falcon030
Click to expand...
Click to collapse
Good question, I am not really sure.. you are kind of the odd man out possibly.. I have had the battery after dead charge scree too before too with the boot hacks, and other times not so much... I think it has to do with how the hacks are done and the order they are all done in. I am not totally sure what that order is though.
Here are more links on the CWM history:
http://forum.xda-developers.com/showthread.php?t=1335933
This is from the above thread but it talks about what I am saying, and how this all was finally made to work for us:
http://forum.xda-developers.com/showpost.php?p=19368661&postcount=24
See the EDIT in my previous post. The bionic boys "safestrap" recovery has the ability. I know cause I just used my buddies bionic to charge my battery. it boots into safestrap, and then if you don't choose recovery, or boot normally, poof, into battery charging.
It's interesting how they have it and we don't. Hmm...
Fall of Enosis said:
See the EDIT in my previous post. The bionic boys "safestrap" recovery has the ability. I know cause I just used my buddies bionic to charge my battery. it boots into safestrap, and then if you don't choose recovery, or boot normally, poof, into battery charging.
It's interesting how they have it and we don't. Hmm...
Click to expand...
Click to collapse
safestrap is a little different.... I know I did the OG mods to make it work for us back in nov/dec. It uses a different hijack method, and we can't use that one on our phone, and thier recoveries don't work on our phone.
Apex_Strider said:
That's interesting. Any idea why I don't have any problem from a full discharge-to-shut off and charge problem? I've not done anything that anyone else hasn't, I mean, I rooted, installed the bootstrap, J-Y-Daddy CWM, flashed myself silly, edited "this" and "that" and tweaked "these" and "those". Never found myself not being able to charge after a shut down...
Edit: I'm running Lithium v.1.3.1
Edit #2: Knocking frantically on wood! Hope I didn't just jinx myself!
Sent from my Atari Falcon030
Click to expand...
Click to collapse
Time to pull a system.img! LOL!
Sent from my MB865 using xda premium
By the way folks, with the release of our spiffy new recovery (Thanks whirley and Luk!) This thread is no longer an issue. Since the battery monitoring had been removed for the boot hijack with the bootstrap.apk we could not charge with the phone off.
NOW, I tested it and we can. Apparently the removal of the battery monitor was not an issue with the new recovery. HOORAY! We should have no more people complaining about dead batterys!
I had this issue this morning and I thought my phone had bricked at first since I installed SCv7 late last night. My phone shut off at 3% and it would not allow me to charge it and it would not turn on at all. I tried Jim's method a few times; did not work for me. I am on SCv7 ICS, rooted, and I do have Bootmenu installed. I went and bought another battery today, which I was going to do soon anyway; and Im going to buy a battery charger on Amazon, just in case. Im not quite sure how to fix it, but as long as I have an extra battery, I will be okay.
Are you not able to charge while off? That issue has been resolved with the new recovery. What does it do when you try to charge it?
Sent from my MB865 using xda premium
I used this method to root, flash CWM Recovery, and unlocked the bootloader.
http://youtu.be/6-tQ05Zo_9U
http://forum.xda-developers.com/show....php?t=1974114
Everything went well. I then flashed "The Executioner 2" Rom. Again, everything was fine I was running the Rom for about 2/3 hours. All of a sudden, I was texting and boom, my phone turns to a black screen. Keep in mind at this time my phone is at about 18% battery when it happened. I managed to boot into CWM. I was wiping everything like I would if I was gonna flash a rom + go to restore back up. I factory/data wipe, wipe cache, wipe dalvik cache, BOOM black screen again. Couldn't boot up normally. Tried to get into CWM, no go, just vibrating and black screen. Tried getting into download mode, no go just vibrating with black screen. Now my phone ain't even charging if I have the USB in. It seems completely dead. Any ideas or do I have to tell Verizon I lost my phone?
It is out of battery. Let the thing charge.
con247 said:
It is out of battery. Let the thing charge.
Click to expand...
Click to collapse
I have my phone sitting and the charger in. There's no red LED or any battery icon to show that it's charging. You know how normally when you turn your phone off, there's still something that indicates you that the phone is charging when you have it plugged in. In my case, it's just a black screen. It's like the phone is dead?
this happened to me once, it was the battery dead and no led when plugged in or anything. Let it sit on the charger for like 30 mins then unplug it and try to boot it.
x714x said:
this happened to me once, it was the battery dead and no led when plugged in or anything. Let it sit on the charger for like 30 mins then unplug it and try to boot it.
Click to expand...
Click to collapse
Should I try to boot up into custom recovery or download/odin mode? If it's possible I want to fix the brick and just flash my phone back to stock for now. The last thing I want is to have a bricked device. I saved up, sold my Razr Maxx, and paid full price off contract for this phone. Yep, all that down the drain if my phone is bricked. I really appreciate the replies guys, it makes me feel better whether my phone can be saved or not.
I can't remember if it's that rom or not, I look at so many threads but there have been a few reports of major battery drops. Search the thread.
Sent from my SCH-I535 using xda app-developers app
see if you can borrow somebody else battery
Thank Me Later said:
Should I try to boot up into custom recovery or download/odin mode? If it's possible I want to fix the brick and just flash my phone back to stock for now. The last thing I want is to have a bricked device. I saved up, sold my Razr Maxx, and paid full price off contract for this phone. Yep, all that down the drain if my phone is bricked. I really appreciate the replies guys, it makes me feel better whether my phone can be saved or not.
Click to expand...
Click to collapse
This had also happened to me before, buy after charging it still wouldn't boot normally.
I had to boot into recovery and then select reboot device, hasn't happened since.
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
This had also happened to me before, buy after charging it still wouldn't boot normally.
I had to boot into recovery and then select reboot device, hasn't happened since.
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
My phone won't boot up at all!! Can't boot into recovery, can't boot into download/odin mode either. And now there's no vibration. It seems dead. I didn't do anything wrong, the Rom was running fine. All of a sudden black screen and it started being stupid the way I said in the OP.
Thank Me Later said:
My phone won't boot up at all!! Can't boot into recovery, can't boot into download/odin mode either. And now there's no vibration. It seems dead. I didn't do anything wrong, the Rom was running fine. All of a sudden black screen and it started being stupid the way I said in the OP.
Click to expand...
Click to collapse
Well I would try to get my hands on another battery and see if it will work then. If not and it really just died take it to Verizon and tell them you were sending a text and it shut off. That sound like hardware failure to me.
If I helped you in some way.... pass on the favor and help the next person!
You wiping it while it ran out of juice for the 2nd time probably didn't help.
con247 said:
You wiping it while it ran out of juice for the 2nd time probably didn't help.
Click to expand...
Click to collapse
I know. At that time I didn't think of the battery, I was just in a panic to get out of the problem.
I think I got somebody to barrow me their GS3 battery tomorrow. IF, the phone lets me boot into anything, what should I do? I don't know which method I should use for fixing the soft brick because there's more than one? I just want to fix it and odin back to complete stock unrooted again.
Reflash your ROM and once it boots up go back to factory rom
Sent from my Holiday using xda app-developers app
Thank Me Later said:
I think I got somebody to barrow me their GS3 battery tomorrow. IF, the phone lets me boot into anything, what should I do? I don't know which method I should use for fixing the soft brick because there's more than one? I just want to fix it and odin back to complete stock unrooted again.
Click to expand...
Click to collapse
Try to go straight to download mode and follow section 5 here using the stock jb image
http://forum.xda-developers.com/showthread.php?p=28530394
If I helped you in some way.... pass on the favor and help the next person!
Happened to me too..Pretty sure its the battery. When mine shut off, I tried different chargers and nothing.. I tried a combo of things like pulling battery while charging and just leaving the battery out for a couple minutes and then plugging it in till you get a red charging light. When it lights up , let it charge and then restore. Good luck..
Sent from my SCH-I535 using xda premium
kintwofan said:
Try to go straight to download mode and follow section 5 here using the stock jb image
http://forum.xda-developers.com/showthread.php?p=28530394
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
If it does let me boot up with a new battery I WILL do this. Thank you!
elmer1500 said:
Happened to me too..Pretty sure its the battery. When mine shut off, I tried different chargers and nothing.. I tried a combo of things like pulling battery while charging and just leaving the battery out for a couple minutes and then plugging it in till you get a red charging light. When it lights up , let it charge and then restore. Good luck..
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I am hoping that it's just the battery being dead and not a hard brick on my phone. I don't understand what happened that made my device do this in the first place? Everything seemed fine. No hiccups when rooting, flashing, ect. I ran the rom for a good few hours. Out of no where BAM, black screen while I was texting?
Thank Me Later said:
If it does let me boot up with a new battery I WILL do this. Thank you!
I am hoping that it's just the battery being dead and not a hard brick on my phone. I don't understand what happened that made my device do this in the first place? Everything seemed fine. No hiccups when rooting, flashing, ect. I ran the rom for a good few hours. Out of no where BAM, black screen while I was texting?
Click to expand...
Click to collapse
It misjudged the battery life (ie the percentage was wrong). Then it realized what was happening then shut off the device to protect the battery.
Thank Me Later said:
Should I try to boot up into custom recovery or download/odin mode? If it's possible I want to fix the brick and just flash my phone back to stock for now. The last thing I want is to have a bricked device. I saved up, sold my Razr Maxx, and paid full price off contract for this phone. Yep, all that down the drain if my phone is bricked. I really appreciate the replies guys, it makes me feel better whether my phone can be saved or not.
Click to expand...
Click to collapse
Your phone isn't bricked....your battery is dead.
Let it charge with a WALL charger for at least 30-60 mins. Walk away. Come back, HOLD just the power button until it boots. Let go. Enjoy your "unbricked" device. Why would you want to go into Odin or CWM without even seeing if it boots? A hard brick wouldn't do anything. Just see what happens. If it bootloops or has constant system.ui closes you'll know it. Then go into recovery and either:
1) rewipe/reflash ROM
2) restore functional backup
Please change the title of this thread. You didn't brick. Your battery died. Lol. TW ROMs on this phone have been known to die with 18-23% on the battery gauge. 23 is my number It's happened to a few of us.
Sent from my SCH-I535 using Tapatalk 2
As I let my phone sit with the charger in while I went to sleep, twisting and turning thinking F*****ck lol. A lot of you guys were right. It WAS my battery. I am now able to boot up into recovery
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
minirx7 said:
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
Click to expand...
Click to collapse
Never flash anything or make major changes to your phone with a low battery (below 70%).
I may be the member he was talking about. I had a thread on this. Only difference was my phone wouldn't charge at all. When I plugged it in when it was off it would boot loop the charge screen. It was rooted and I had some bloat frozen, but the issue started after I installed Sugarsync. I had the same configuration for a few days with no problems, and my battery was about 50 percent when I tried to charge.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just trying to help. I freaked yesterday because no matter what i did, it wasnt charging. But once i fully powered off, it started chargin!!
scott14719 said:
Never flash anything or make major changes to your phone with a low battery (below 70%).
Click to expand...
Click to collapse
I just flashed a ROM with 56%. I like to live dangerously.
AdePower said:
I just flashed a ROM with 56%. I like to live dangerously.
Click to expand...
Click to collapse
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
scott14719 said:
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
Click to expand...
Click to collapse
I bricked a S2 like that. Flashed a rom adn the battery drained in the process, causing it not flash properly. phone was dead, no download mode or anything.
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/