***Emergency Thread*** Here To Help!

---

I have created this thread for all you SG-SIII Noobs & Senior Members!

The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.

This is the Emergency thread!

*Did you run into a problem and need quick assistance?

*Do you have a question or concern about your SG-SIII device?

Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!

Re: ***Emergency Thread*** Here To Help!

---

In case of emergency!

Okay I guess I'll be the first to post.

About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.

Any advice? Or am I stuck doing a warranty exchange?

Re: ***Emergency Thread*** Here To Help!

---

Originally Posted by Rayman0625

Okay I guess I'll be the first to post.

About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.

Any advice? Or am I stuck doing a warranty exchange?

Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.

If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.

Sent from my HTC One S using Tapatalk 2

Originally Posted by ...Awesome...

Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.

If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.

Sent from my HTC One S using Tapatalk 2

The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.

Sv: ***Emergency Thread*** Here To Help!

---

Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.

Sent from my LG-P990 using xda app-developers app

Originally Posted by lintz

Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.

Sent from my LG-P990 using xda app-developers app

Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.

Re: ***Emergency Thread*** Here To Help!

---

Originally Posted by Rayman0625

The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.

Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.

I have the t-mobile US t999.

Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.

So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.

Also worth noting, when I attempt to boot into recovery it just vibrates over and over.

Not sure what my next steps should be. Any help would be greatly appreciated.

Originally Posted by heartspains88

I have the t-mobile US t999.

Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.

So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.

Also worth noting, when I attempt to boot into recovery it just vibrates over and over.

Not sure what my next steps should be. Any help would be greatly appreciated.

after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download