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.

[Q] Damaged Captivate - Any help would be appreciated.

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.

[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...

[Q] Unable to charge while off?

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

[Q] Hard-brick? :(

Hi All,
I think I might have hard bricked my phone but I'm not sure. I had Synergy r56 and IMOSEYON's kernel for several months and stayed on that even after the JB releases came out. This past weekend I decided to upgrade to the latest release, r147. I wiped data/cache, flashed r147, and it booted up fine. The only problem was that it would appear to reboot about twice an hour (or more). I read that it could be the kernel that was included (Ziggy). So I decided to try KT747 but before that I flashed the newest radio (VRKL3), then flashed KT747 but that didn't help with the reboots. This was late last night and I had to wake up early for work so I decided to work on this in the morning. Woke up to a dead phone -- it wont charge!
With the power plugged in, I pull out the battery and put it back in and the phone vibrates and a red LED comes on. I see the display turn on and I see the battery image (with zero charge) that you usually see when you charge the phone while it's switched off. This image last less than a second and then it's gone. I tried going into download mode but that doesn't work either. I'm wondering if I get a fully charged battery, would that help me boot up. Any ideas??

Yes get a new battery from someone that's charged. If your seeing life with the screen coming on then you are not hard bricked. I would recommend having everything ready to Odin back to stock when you get the battery and go ahead and put it to stock.
Sent from my VS920 4G using xda app-developers app

Guess that's good news. Now to find someone who has an S3...if I can't, can it take it in to a Verizon store? Or is that a bad idea? Thanks for your response!

Not on this phone but I know people would take the droid x into verizon and they would let them use one of their batteries to see if it would boot. Wouldn't hurt trying. And you can get batteries pretty cheap on amazon, external chargers too. Good luck.

Just placed an order on Amazon for a battery/charger set. Will update this thread tomorrow! Thanks again guys!

This has been happening to me since I got my s3. If I let my battery die it's a pita to charge it back up as I have to keep pulling thwarted battery and or get lucky. The battery charging icon would show up and disappear and the red led light would show up, That doesn't mean its charging. The battery charging icon has to stay put to know it's charging. This hasn't really bothered me enough to get a replacement. So my 2 cents
Sent from my SGH-i535 using xda premium

I'm curious have you just left out plugged in for a couple hours? Also what about recovery mode?
Sent from my VS920 4G using xda app-developers app

The no charge after battery dead is a bug in CWM.

Both CWM and TWRP? I just installed TWRP and haven't had this issue before with CWM.
prdog1 said:
The no charge after battery dead is a bug in CWM.
Click to expand...
Click to collapse

Update:
Got my extra batteries less than 10 minutes back. Stuck one of the batteries in the phone and it booted!!!! I'm stoked! lol...anyway, if someone could guide me through what I'd need to do to get back to the latest Synergy JB rom (r147 I believe it is) after I go back to stock because I'm pretty sure I screwed something up with everything I did to get to where I am.
What I've done so far:
Unlocked bootlader
Flashed the latest radio (RLK3 I think it is)
Flashed the KT747 kernel over the one that came in Synergy r147
What do I need to do to get back to Synergy r157? Do you think it's best to go back to stock and re-do everything or is there an easier way? I'm a little paranoid cos I've been out of this game for a while and am not sure what effects my flashing kernels/radios will have on anything I try to undo. Also, if I do flash the Synergy ICS nandroid (r56) that I took prior to flashing r147, will that revert the kernel to Ziggy's?
Thanks in advance guys!

Nevermind. On Synergy r155 now and am having several unrelated issues. Thanks for the assistance.