Replacement S3 Also Shuts Down, Won't Turn On Again Without Battery Pull

**robrecht** · 12-22-2012, 01:27 PM

My first S3 started doing this a few weeks ago so Verizon sent me a replacement S3. It's doing the same thing 'though perhaps not as frequently. 1-2 x per day. Previous phone was probably around 4x a day. If this isn't a common problem with the S3, perhaps this is a software problem?

Any ideas? Anyone have similar problems?

**mlb2305** · 12-22-2012, 02:08 PM

I had this problem about a month ago but for whatever reason it stopped for the most part. Now my gps is pretty much sucking. My wife's phone has never had either issue.

Sent from my SCH-I535 using Android Central Forums

**jdk2** · 12-22-2012, 03:12 PM

If you've restored the apps that were on your previous device, then it would seem to be a software issue with one or more apps. If you haven't restored anything, it's probably luck of the draw and you've received another bad phone..

**robrecht** · 12-24-2012, 10:35 AM

Originally Posted by jdk2

If you've restored the apps that were on your previous device, then it would seem to be a software issue with one or more apps. If you haven't restored anything, it's probably luck of the draw and you've received another bad phone..

Yes, I've restored most of the apps I was using, which is why I'm now exploring this option. Is there a way to do a hard reset without Google Play automatically restoring apps?

**jdk2** · 12-24-2012, 01:49 PM

During the setup, you're given the option of using your Google account to restore your phone. Just uncheck that option.

**minnieusa** · 12-24-2012, 09:06 PM

try a different browser. mine was having issues until i changed the browser from the stock one

Sent from my AT100 using Android Central Forums

**robrecht** · 12-25-2012, 09:58 AM

Originally Posted by minnieusa

try a different browser. mine was having issues until i changed the browser from the stock one

Sent from my AT100 using Android Central Forums

Thanks. This problem did arise about the time I went back to using the stock browser. First, I'm going to wait and see if the problem persists with the Jelly Bean version of the stock browser. I just got Jelly Bean yesterday.