Remove All Ads from XDA
Post Reply Subscribe to Thread Email Thread
My brother has an S3 on AT&T running a nightly build of CyanogenMod 11.
It's been running this build for a while. However, he was on it today, and it crashed. Now it won't even try to boot unless you take out the battery and put it back in, in which it will show the samsung logo and shut off. It won't boot into recovery, it won't boot into download mode.
I'm thinking it's hard bricked, but why would it randomly hard brick itself like this? And is there any way to fix it?
21st January 2014, 01:25 AM |#2  
audit13's Avatar
Senior Member
Flag Toronto
Thanks Meter: 3,641
Maybe it bricked because some files got corrupted? Not sure. If you can get into recovery, try wiping the cache, data, and Dalvik. If that doesn't work, you could try an updated CM11 ROM.

Did you try to get into download mode with a USB jig?
21st January 2014, 01:29 AM |#3  
Senior Member
Thanks Meter: 25
Its not hard bricked. Boot it into download mode and Odin back to stock

Sent from my Nexus 7 using xda app-developers app
21st January 2014, 01:35 AM |#4  
audit13's Avatar
Senior Member
Flag Toronto
Thanks Meter: 3,641
Don't use desktop Odin if the phone has been updated via an OTA update to stock AT&T 4.3 ROM.
21st January 2014, 03:36 AM |#5  
Junior Member
Thanks Meter: 0
I'm the brother with this problem, I just couldn't post at the time.
Anyway, I can't boot it into anything. not recovery, not download mode, nothing. The only way I can force it to even try to boot is to take the battery out, and back in.
After this, "Samsung" appears for all of about a second, and it shuts off again.

Edit: it seems I can boot into download mode, but like the samsung logo, it disappears. It's almost as if it's crashing after a second each time. Any ideas?
Last edited by RichDMartin; 21st January 2014 at 05:13 AM.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes