Database Info

NEED HELP!!!! phone won't stop powering off

My inspire keeps powering off at ranodm times and has gotten worse. If its plugged into a power source it will stay on, but the second its pulled off theres a huge chance that it will just randomly power off. I've wiped the battery stats, factory rest a bunch of times, tried multiple roms and radios and can't find a solution. ANY HELP WOULD BE GREATLY APPRECIATED!!!!

See if ATT will give you a new battery.

Tx Redneck said:
See if ATT will give you a new battery.
Click to expand...
Click to collapse
I know it sounds like he's being an ass, but I think he's right. I have the exact same problem. Used CoreDroid, MIUI, & HoneySense 4 & 5 and they all randomly rebooted. I noticed that after I powered back on, the battery level would be significantly different. It got progressively worse as the battery level drops. Once I get to about 23%, it just turns off when I try to do anything. I speculate that the sudden increase in battery drain from the screen getting bright & the radio draws more current than the battery can provide.
To test, I got my phone to the point that it would turn off every time I booted it. It would show the homescreen & say that it had 18% battery. I then plugged it in to the USB charger & it works fine. I'll be replacing the battery ASAP.

this happend to me on CM7 and MIUI twice and the first time i just flashed off of CM7 and it stooped and on MIUI i just rebooted the phone while connected to the charger then when it was completely booted up i unplugged it and it was fine after that but that time it was caused by letting my battery die down and then i kept booting up my phone to completely deplete the battery and did this about 20 times and it wouldn't die so i just changed out batteries and when i booted and it would immediately power down like the battery was dead so thats when i plugged it in and powered on and it worked, and i know its not the battery because i have 4 batteries

cordell507 said:
this happend to me on CM7 and MIUI twice and the first time i just flashed off of CM7 and it stooped and on MIUI i just rebooted the phone while connected to the charger then when it was completely booted up i unplugged it and it was fine after that but that time it was caused by letting my battery die down and then i kept booting up my phone to completely deplete the battery and did this about 20 times and it wouldn't die so i just changed out batteries and when i booted and it would immediately power down like the battery was dead so thats when i plugged it in and powered on and it worked, and i know its not the battery because i have 4 batteries
Click to expand...
Click to collapse
Ok then, you "know" it's not the battery - so what is your speculation? Until I get the spare batteries I ordered today, I won't be able to fully test the battery theory. I can only say with certainty that the phone doesn't shutdown while plugged in.
I could also go along with another theory - The Thunderbolt got a recent OTA update that makes them randomly shutdown. Is it possible that a piece of that code made it into the new Gingerbread ROMs? I didn't note the issue running CoreDroid 6.4 (a GB build but the last to use EXT3 instead of EXT4 and was also released before the TB OTA update), but only after upgrading to 6.5. Could it be some finicky problem with EXT4?

meatrocket said:
Could it be some finicky problem with EXT4?
Click to expand...
Click to collapse
Actually, forget this part. I forgot I used HoneySense 4.0 with EXT3 & still had the random shutdown problem.

with it plugged in do a nandroid backup and then restore to stock then restore back with only restoring system and data

I know its not the battery because it will stay in CWM for several minutes and much longer than it does on without any random shutdowns. Going to try the return to stock and reflash method and post back.

Ok, so that I get this right, the test plan is to: flash back to stock, re-root & then reflash to a new ROM such as Coredroid 6.8? If that's what one of you are going to do, then I'll do it also so we can see if we get the same results.

Well, I actually downgraded to RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed, went through Bubby's One Click and the damned phone shutdown upon boot to the first image of Bubby's. I figured MAYBE something was wrong with Bubby's One Click as I had originally used the ACE hack kit.
I reverted back to RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed again & decided to use it for a minute to see if it shutdown and it DID!
There is either (A) a problem with my battery or (B) a problem with the charging system on my phone. This IS NOT a firmware/radio issue! It may be different for you, but I'm positive about my phone now. I'm going to wait until my new batteries come in on Wednesday and if it acts the same, I'll be replacing my phone under warranty. I should also note - I've never overclocked this phone, so I don't want anyone fear-mongering the N00BS about "see what overclocking will get you"!

Does yours stay on when its plugged in?

samftw said:
Does yours stay on when its plugged in?
Click to expand...
Click to collapse
Yes. I noticed the shutdowns started about 1½ to 2 weeks ago. It got more frequent as time went on. The phone is practically unusable now unless I leave it plugged in. I suspect that if it is indeed the battery, it may even start shutting down when plugged in since the phone will turn off if you remove the battery when it's plugged in. Just a hunch.

same exact story here totally bummed right now but at least i work for at&t so getting anew battery shouldnt be an issue. still a huge pain in my ass

samftw said:
same exact story here totally bummed right now but at least i work for at&t so getting anew battery shouldnt be an issue. still a huge pain in my ass
Click to expand...
Click to collapse
Well, bummer dude. I called AT&T and they said that the battery was covered under warranty & they'd be happy to send me one right out. The only problem was that they didn't have any in stock! They offered to credit my account with whatever I have to spend on replacing the battery myself. When I get the 2 batteries from Amazon & make sure they work, I'll get the credit for them applied to my account. It was only $25 for 2 batteries & charger shipped.
I called my local AT&T Corp stores to see if they had any batteries for the Inspire & they didn't either. Me thinks this widespread shortage of batteries could be indicative of a bigger problem.

WoW! Here's the feel-good part of this story....
As I posted earlier, AT&T service didn't have the battery to send me. I couldn't find a battery anywhere - I called the 2 AT&T Corp strores, BestBuy and Batteries +.
I went to the AT&T Corp store where I bought the phone & signed in for help. The girl came over to help as I was explaining to her what was happening & telling her that I wanted to take the battery out of her demo phone to make sure it was the battery. If it wasn't, then I could call service back & have them ship me a repalcement phone instead of having to wait until the batteries I ordered off of Amazon arrived.
She told me that she didn't want me to mess her floor phone up & offered to go in the back & get a phone to test with. She came back with a new battery still in the plastic. I popped it in and sure enough, it has been the battery! I told her thanks and that I felt a lot better knowing that it was indeed the battery.
She insisted that I keep the new battery since there were none to be found & she would "adjust" the phone she took the new battery from. I assume "adjust" is speak for "send it back as defective". I'm really positive about the whole experience, especially since she didn't have to do that at all. You can bet I'll be going back to that Corp store & buying from that rep when I'm ready to get my Samsung Galaxy S II!

I'm having the same problem I don't know why it's doing this
Sent from my HTC Inspire 4G™ using the XDA App.

King Askaba said:
I'm having the same problem I don't know why it's doing this
Sent from my HTC Inspire 4G™ using the XDA App.
Click to expand...
Click to collapse
Uh...did you read ANY of the thread or just post a reply? It seems rather obvious that there's a battery problem. Maybe you could do some of the same or similar testing we did to see if you have similar results?
The only thing I didn't say in all of this is that I got my phone on 2/14/11. So I've had it almost exactly 4 months before the problem really came up.

Annoying boot loop issue

This one has got me baffled and annoyed. So ive updated to fp1 as ive noted in past posts. Ive tried pjb (fp1 version) and the stock ota update, both with tweaked 2.0. I have multiple batteries so wen 1 dies i swap it out for a fresh one. Everything will be working fine til i need to swap out batts, wen i do and try to reboot i get stuck in a damn bootloop and have to wipe data to get the phone to wrk. As u can imagine its pretty annoyin, even wit TB, to have set up my stupid shortcuts n widgets every othwr day.
Before anyone asks i went back to stock first, then the ota update, the fashed rom and kernel. Never had this problem on ep4. U might think tht i should just go back to ep4 then. Well, the problem there is that my email wont sync rite becuz of ozmail notifocation (yes i typed STOP, yes i contacted vzw, they said it should be fixed but it wasnt. Only thing that fixed it was goin to fp1)
So that is my problem. This is my 4th time starting from scratch, so hopefully this time will stick. We shall see.
If anyone has any advice i am all ears.
Sent from my SCH-I510 using XDA

Check out post #585 in the [FP1H][Rom][Cwm][Odin]Tweaked v2.0 thread under the Dev forum. Sounds like the same issue reported there.
EDIT: oops, that was you!

I can't for the life of me think of why that would happen. I also have an extra battery and have NEVER had that happen when swapping them. Has it been the same battery inserted when this happens or does it happen with both? Are they the exact same battery? After turning the phone off to switch do you wait about 30 seconds or so before pulling the battery? Happened with stock kernel and custom FP1 kernel? Stock rom and custom rom? Those are the first things that come to mind that MAY be a factor.

I actually have 3 batteries, 2 oem 1600 and 1 extended life 3600. It makes no sense, just went through the whole thing again, flashed to stock, started it up and all was well. flashed to fp1, started it up and was well. flashed pjb and tweaked 2.0 and im stuck on the samsung logo. this is really pissing me off!

cnoevl21 said:
I actually have 3 batteries, 2 oem 1600 and 1 extended life 3600. It makes no sense, just went through the whole thing again, flashed to stock, started it up and all was well. flashed to fp1, started it up and was well. flashed pjb and tweaked 2.0 and im stuck on the samsung logo. this is really pissing me off!
Click to expand...
Click to collapse
Did you test between flashing the kernel and rom on fp1? Might be interesting to see if you can isolate the issue further. I'm at a loss for what I could've done to cause the issue, but I can try to look into it if all signs point to tweaked.

How are you replacing the batteries? It sounds like you just pull it out with the system running. Power off the phone if you aren't, then replace the battery. Also, are all batteries stock Samsung batteries meant for the Charge?

imnuts said:
How are you replacing the batteries? It sounds like you just pull it out with the system running. Power off the phone if you aren't, then replace the battery. Also, are all batteries stock Samsung batteries meant for the Charge?
Click to expand...
Click to collapse
I doubt the 3600 is oem because samsung hasn't heard of batteries that big yet :S

I have tweaked running right now with stock fp1 so we'll see what happens on next batt swap.
I have 2 oem 1600 batts and a 3rd party extended batt. I always power down before pulling the batt. I marked the oem batt that i swapped in wen the prob happened today. Its possible i took it out to early, though i doubt it. But ill make sure to leave it in a few min after powerin down before pullin. Ill try flashing pjb over the weekend, gta work in a few hours n just needed to get things up n running.
Sent from my SCH-I510 using XDA

cnoevl21 said:
I have tweaked running right now with stock fp1 so we'll see what happens on next batt swap.
I have 2 oem 1600 batts and a 3rd party extended batt. I always power down before pulling the batt. I marked the oem batt that i swapped in wen the prob happened today. Its possible i took it out to early, though i doubt it. But ill make sure to leave it in a few min after powerin down before pullin. Ill try flashing pjb over the weekend, gta work in a few hours n just needed to get things up n running.
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
OK so if you swap batteries and get bootlooped, does the phone work again if you put in the original battery?

Nope. Once in the bootloop the only way Ive found to get out of it is to reflash.
Sent from my SCH-I510 using XDA

I just tried to reproduce you issue by shutting down and swapping in my spare 1600mAh battery. The phone booted up fine.
Not sure if it would have any impact, as I'm not sure exactly what it does, but have you tried wiping battery stats in CWM before booting with the new battery?

I am going to do the wipe battery stats this time around. I always do anyway on a fresh flash just to try n calibrate the battery.
DW I dont think it is Tweaked, its prob my phone or possibly i am screwin up the flash somehow (though i dont know what I could be doing wrong) If no one else has had this issue it cant be the rom.
Heres a few questions that answers could possibly explain the problem. Does it matter what is flashed first? ROM or kernel? And after you power down the phone there is that Team whatever animation, when that goes away is the phone powered down or does it take more time afterwards to be completely powered down? I always wait til the animation turns off, then pull the batt, but maybe the phone is fully off?

I always flash ROM first, then kernel. When shutting down, when the button back-lights go dark, it's off. That should be 5 seconds or so after the shutdown animation, not immediately after.

sbradley07 said:
I always flash ROM first, then kernel. When shutting down, when the button back-lights go dark, it's off. That should be 5 seconds or so after the shutdown animation, not immediately after.
Click to expand...
Click to collapse
Unless the ROM you are flashing includes a kernel (AFAIK only the ones based on leaks did), there should be no difference in order (just saying).

Sad to report that it happened again! Just went to switch out batteries, powered down phone, waited at least a minute before pullin battery, put in the new batt and stuck on samsung loop. Im pretty f'n over this crap! Have to be up for work in a few hours and I have to waste time that should be for sleep flashing back to stock, reinstalling fp1, etc. how do other ppl get replacement phones from verizon? anyone know a problem i could tell verizon that theyd give me a new phone? lol

cnoevl21 said:
Sad to report that it happened again! Just went to switch out batteries, powered down phone, waited at least a minute before pullin battery, put in the new batt and stuck on samsung loop. Im pretty f'n over this crap! Have to be up for work in a few hours and I have to waste time that should be for sleep flashing back to stock, reinstalling fp1, etc. how do other ppl get replacement phones from verizon? anyone know a problem i could tell verizon that theyd give me a new phone? lol
Click to expand...
Click to collapse
That sucks it happened again. Does it happen when you're completely stock? Luckily I've never had to get a replacement (knock on wood) but I would just tell them that when you switch batteries it factory resets and that should probably be a good enough reason. Good luck

THEbigSWEEN said:
That sucks it happened again. Does it happen when you're completely stock? Luckily I've never had to get a replacement (knock on wood) but I would just tell them that when you switch batteries it factory resets and that should probably be a good enough reason. Good luck
Click to expand...
Click to collapse
never happened until i updated to fp1. i havent tried just using stock fp1 cuz stock is just horrible on this phone. im all reloaded (once again) so we'll see, but if it happens again i will contact verizon about it and see if they will send a replacement.

[Q]MT4GS - wont charge

Hey so i recently rooted, im boot loader unlocked S-ON, flashed the boot.img and am running CM9 alpha 4 on my double shot.
however as of yesterday, all it does is keep blinking an orange light and and not charging, the few times i have been able to turn it on it shows 0 - 4 % battery.
i was running CWMR the latest version but i read another similar thread that was resolved and flashed stock recovery i think, i cant turn it on to check currently :/
Checked for similar threads nothing could really help.

If you have no juice to experiment, you will need a different battery thats charged in order to work with it.

Try leaving it on the on the charger for little while. Sometimes the batteries take a while to accept a charge. My Anker will take quite a while for it to start showing charge if I ran it all the way down.
Barring that get another battery and the standalone charger such as the Anker battery two pack.
Hastily spouted for your befuddlement

make sure that Tis not your charger. Did you try charging with a different charger.

Ok well i still have my broken phone(the one i have no is the warranty one i got from them, didnt send the old broken one back yet), and ive put the battery in there to charge before the problem seems to be this.
The phone isn't charging while its off. It can charge while turned on however at a VERY VERY slow rate. ive read on some thread that CWM recovery might be to blame due to a fastboot thing?

Script Kitty said:
Ok well i still have my broken phone(the one i have no is the warranty one i got from them, didnt send the old broken one back yet), and ive put the battery in there to charge before the problem seems to be this.
The phone isn't charging while its off. It can charge while turned on however at a VERY VERY slow rate. ive read on some thread that CWM recovery might be to blame due to a fastboot thing?
Click to expand...
Click to collapse
This was a known bug with the old Madaco recovery, is that the one you are using? If so, update to the latest one from rom manager in the market.

No im using the 5.0.2..7( i think something around there) CWM, finally charged the battery up, and it went from 100% - 88 like that* snaps fingers* , trying to calibrate the battery to see if that helps but the voltage is almost 4200 mv and the percentage is decreasing... so i might just flash stock, flash stock recovery lock boot loader then just see if i can warranty it...

Bricked My GS3

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

[INFO]Software related charging issue on S4

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.