Streamline Android Theme Customization with Graphic Porter

I dont have a custom theme on my Android phone, and the reason for this is because … more

Boost the Brightness of Your Sony Xperia Z1’s LED

I think the last time anyone has ever used a physical torch to find their earphones, … more

XDA Xposed Tuesday: Modify the Look of Your Volume Control – XDA TV

How many screenshots have you seen with a volume status bar in the … more

Prepare Your Nokia X2 for Battle with Nokia X2 Tools

Unveiled in June this year, the Nokia X2 is the Finnish companys second crack at an … more
Post Reply

Galaxy S3 shuts down during boot

26th June 2014, 10:25 AM   |  #1  
OP Junior Member
Thanks Meter: 0
 
10 posts
Join Date:Joined: Jan 2014
My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).

After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).

I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.

When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).

Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
26th June 2014, 10:49 AM   |  #2  
DocHoliday77's Avatar
Recognized Contributor
Flag HuntsVegas!!!
Thanks Meter: 6,161
 
8,805 posts
Join Date:Joined: May 2011
Donate to Me
More
How old is your battery? Might be time to replace it.
26th June 2014, 02:54 PM   |  #3  
OP Junior Member
Thanks Meter: 0
 
10 posts
Join Date:Joined: Jan 2014
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
26th June 2014, 03:02 PM   |  #4  
BWolf56's Avatar
Recognized Contributor
Flag Outaouais
Thanks Meter: 1,699
 
3,864 posts
Join Date:Joined: Mar 2011
Donate to Me
More
Quote:
Originally Posted by cheezyphil

This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?

They're not as heavy to load.

Was any modification done to your phone (software) about when that started happening?
26th June 2014, 03:42 PM   |  #5  
OP Junior Member
Thanks Meter: 0
 
10 posts
Join Date:Joined: Jan 2014
The s3's been on and off custom roms for a year now
26th June 2014, 03:48 PM   |  #6  
BWolf56's Avatar
Recognized Contributor
Flag Outaouais
Thanks Meter: 1,699
 
3,864 posts
Join Date:Joined: Mar 2011
Donate to Me
More
Quote:
Originally Posted by cheezyphil

The s3's been on and off custom roms for a year now

I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
26th June 2014, 04:08 PM   |  #7  
OP Junior Member
Thanks Meter: 0
 
10 posts
Join Date:Joined: Jan 2014
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
26th June 2014, 04:21 PM   |  #8  
BWolf56's Avatar
Recognized Contributor
Flag Outaouais
Thanks Meter: 1,699
 
3,864 posts
Join Date:Joined: Mar 2011
Donate to Me
More
Quote:
Originally Posted by cheezyphil

Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.

Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
26th June 2014, 04:43 PM   |  #9  
DocHoliday77's Avatar
Recognized Contributor
Flag HuntsVegas!!!
Thanks Meter: 6,161
 
8,805 posts
Join Date:Joined: May 2011
Donate to Me
More
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes