Develop Bugs

S3 won't boot, load CWM, go into download mode...

Alright, so I have an i-747 (AT&T GS3) running AOKP Jellybean (8.28 build) with the KT747 kernel. I just tried to install Chainfire 3D using the automated installer, and when the phone rebooted, it stuck at the Samsung Galaxy S3 logo until I pulled battery. So I tried rebooting into CWM - same problem. And again with download mode. Even after pulling the battery for a good 5 minutes, nothing works. Am I bricked, or is there some fix for this?

If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

g2tegg said:
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I made a nandroid just this afternoon, but I can't actually boot into CWM at all. As in, I turn on the phone (power+home+volume up), it gets to the Galaxy S3 logo and just hangs there. If I could get into CWM (or download mode) this would be about a 10 minute fix, but I'm kind of out of luck here.

Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.

HELP I have the same issue
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse

Hi, sorry to say but sounds like its bricked
Thanks

MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
I doubt it's bricked if he got it into download mode. I'm sure he's flashed it and even got his wallpaper back up by now. Please let us know of you've managed to solve this or not MrPhantom.
Sent from my SGS3 i747m (Bell) on CM10 using TapaTalk2

delete post please

Curious?
I know its technically "Solved" but does anyone have any idea why this is happening? I have a Verizon GS3 and it's happening to me. I try to boot and it vibrates once and doesn't turn on. Recovery does the same thing. But going into Download mode works. Odin back to stock as we speak but I'm just curious what went wrong. I just did a clean install of a rom, set it all up (working at the time), set it down for the night and woke up to it like this.

rrrs444230 said:
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
Click to expand...
Click to collapse
Same thing happned to me but your not bricked. You can get into bolth download and boot mode easy
Here is how you do it.
RECOVERY MODE
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
[edit]Download Mode
Save that somewhere. Make sure do it right. I got stuck also and thought I couldn't get into recovery but I had to do it right (it hit recovery mode first try) I have learned that most people do it slightly wrong. Make sure follow directions
Download mode
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
To get out of Download Mode, simply press and hold the power button until the phone restarts
if helps hit thanks.
Just save that to a text file somewhere
I have also soft bricked when I deleted my rom once on accident. I dunno how I did it but I would get stuck at the TWRP screen. It wouldn't go to download or anything however when I plugged it into odin it saw it .... I even had a soft brick when screen went black from a bad boot animation and same thing.. and I had one bad soft brick where it took about 100 trys to get it into download mode (black screen) but odin detected it. I spent like 4 hours working on it.
I think
1. People don't follow directions correct (they do it a little wrong) which is enough if your phones messed up for it not to work.
when your phones normal it can get into recovery or download easy but when its sick you got to do it perfect.
2. I think something wrong with the phones (my s2 never had any issues in 2 years of owning it) S3 has tons of issues from usb, to bluetooth, to these soft bricks I have had)
3. Roms play a big part
4. I also think the way storage works in this new phone causes lots issues I dunno why just what I think
anyway Like I said now when I have a isssue I open text and read it and make sure I do it right and 95 percent of the time it was my fault I wasn't doing it right. K just my thoughts

when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different

phatchef1 said:
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
Click to expand...
Click to collapse
That's most likely cause you're not in the right section..: http://forum.xda-developers.com/forumdisplay.php?f=1708

Need help!! s3 wont go into recovery/download mode.

Hello! So I'm very new to rooting and roms but I'm very tech savvy.
So here's the situation... I buy a 1 month old s3 from someone and he had a AOKB ROM installed on it. It worked perfectly when I got it but then I decided to revert it to stock and factory settings. I don't know much about aokb ROM but I guess it wouldn't matter since I was just gonna flash the stock ROM on it with Odin. So I turned off the phone and try the recovery boot button combination and it didn't work, it just started normally, I did it several times and suddenly it wouldn't boot anymore. I then try to go into download mode but it wouldn't either, it would just restart and freeze in booting splash screen.
I'm panicking and don't know what to do. How can it possibly brick from resetting and why wouldn't it let me access the recovery/download menu I thought that was standard on all androids no matter what ROM you have installed in it.

esteban089 said:
Hello! So I'm very new to rooting and roms but I'm very tech savvy.
So here's the situation... I buy a 1 month old s3 from someone and he had a AOKB ROM installed on it. It worked perfectly when I got it but then I decided to revert it to stock and factory settings. I don't know much about aokb ROM but I guess it wouldn't matter since I was just gonna flash the stock ROM on it with Odin. So I turned off the phone and try the recovery boot button combination and it didn't work, it just started normally, I did it several times and suddenly it wouldn't boot anymore. I then try to go into download mode but it wouldn't either, it would just restart and freeze in booting splash screen.
I'm panicking and don't know what to do. How can it possibly brick from resetting and why wouldn't it let me access the recovery/download menu I thought that was standard on all androids no matter what ROM you have installed in it.
Click to expand...
Click to collapse
What button combo are you using?
Sent from my SAMSUNG-SGH-I747 using xda premium

esteban089 said:
Hello! So I'm very new to rooting and roms but I'm very tech savvy.
So here's the situation... I buy a 1 month old s3 from someone and he had a AOKB ROM installed on it. It worked perfectly when I got it but then I decided to revert it to stock and factory settings. I don't know much about aokb ROM but I guess it wouldn't matter since I was just gonna flash the stock ROM on it with Odin. So I turned off the phone and try the recovery boot button combination and it didn't work, it just started normally, I did it several times and suddenly it wouldn't boot anymore. I then try to go into download mode but it wouldn't either, it would just restart and freeze in booting splash screen.
I'm panicking and don't know what to do. How can it possibly brick from resetting and why wouldn't it let me access the recovery/download menu I thought that was standard on all androids no matter what ROM you have installed in it.
Click to expand...
Click to collapse
Is it dead? No you can't brick from button combo. I'm guessing the battery died. When you charge it you can then try the button combo or boot it up and go into adb and type adb reboot download

esteban089 said:
Hello! So I'm very new to rooting and roms but I'm very tech savvy.
So here's the situation... I buy a 1 month old s3 from someone and he had a AOKB ROM installed on it. It worked perfectly when I got it but then I decided to revert it to stock and factory settings. I don't know much about aokb ROM but I guess it wouldn't matter since I was just gonna flash the stock ROM on it with Odin. So I turned off the phone and try the recovery boot button combination and it didn't work, it just started normally, I did it several times and suddenly it wouldn't boot anymore. I then try to go into download mode but it wouldn't either, it would just restart and freeze in booting splash screen.
I'm panicking and don't know what to do. How can it possibly brick from resetting and why wouldn't it let me access the recovery/download menu I thought that was standard on all androids no matter what ROM you have installed in it.
Click to expand...
Click to collapse
The button combo is holding volume down and the home button while powering on for recovery, or Volume up and home for download.

hey im in panic mode guys, i just got my brand new phone, instaleld the OTA update to JB, then i odin the preroot version everythign worked perfectly.
Then i tried a custom rom with CWM, the marshmellow perfection one. It flashed and worked, but I wanted to go back to stock
So I odin flashed back to the preroot JB rom i had used before, and now it it hangs at the Samsung boot logo after reboot.
Odin says Pass and everything.
I also cannot get into any sort of recovery other than download mode.
What can i do to fix this???

Try this....plug charger in....when it completely shutdown you'll see battery charging icon on screen.....press volume up, home and power.....release power when you feel it viberate..... release everything else right after you notice blue text in upper left corner...
Sent from my SGH-I747 using xda premium
---------- Post added at 07:23 AM ---------- Previous post was at 07:12 AM ----------
You'll also have to wipe data from recovery screen...before new ROM initializes...
Sent from my SGH-I747 using xda premium

Wrong post sorry
Sent from my SAMSUNG-SGH-I317 using xda premium

Gr8Danes said:
The button combo is holding volume down and the home button while powering on for recovery, or Volume up and home for download.
Click to expand...
Click to collapse
i think you have to hold all 3 buttons until you see the little blue text.

Brick? Faulty power button? (Phone wont stay in download mode)

Hello guys, so today I decided to update my i747 ATT S3 to the latest Task650 Rom, I did as always with the exception that this time I needed to flash a file trough PDA in odin since there was a baseband update back in may. Everything was successful at this point, phone rebooted and went in to the current version of the Task650 ROM i had installed, everything worked great with the exception of my power button that once pressed instead of locking the phone would completely turn it off/trigget the power panel (shutdown,reboot...) so I booted again and powered it off. Tried to get into recovery to flash the latest build of the Task650 ROM without luck, the phone just powers off once trying to boot into recovery, tried the same thing with download mode. At first it went in and stayed in download mode successfully but then I tried to go into recovery again and the same story, went back into download mode and this time it would shut down after 3 or so seconds, sometimes lasts more but no matter what I do it shuts down and the battery has to be pulled in order for it to go into either mode.
At this point to me it looks like a sticked power button but I could be wrong. Any suggestions in order to attend this issue?
[Update] So apparently it really is my power button, wiggled with it for a bit and managed to make the phone boot into the ROM successfully...
Any suggestions on how to permanently fix this issue?
Oscar

Hey man,
If you were able to "wiggle" the power button to work then its definitely the power button. If you have had the phone for a year or less I'd Odin back to stock/ flash counter fix the device and return it to at&t. Back in my captivate days that was a sure sign that the power button was about to malfunction completely. If you are unable to take in for warranty then I'd suggest using the XDA search feature to find the "home remedy power button fixes" or maybe just googling fixes. Mobile tech videos does good work but I won't link to his website because I'm pretty sure its against XDA rules. Or, for even more fun; you could fix it yourself.
Anyways,
Goodluck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

SOLVED, got phone back from repair shop where power button was successfully replaced

wceoscar said:
SOLVED, got phone back from repair shop where power button was successfully replaced
Click to expand...
Click to collapse
Good to hear man
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

um, hard brick?

I was running the 08/20 nightly of CM10.2 and I was typing a SMS in the CM 10.2 default app, then the screen went black. I left it there for sometime (~25 min) then tried to turn the screen on before doing a battery pull, didn't work, so I pulled the battery and then rebooted but it goes to the samsung screen then goes black. I can't boot a ROM, I can't go into recovery, and I can't go into download mode. Hard bricked? What are my choices.
EDIT: the battery is charged because I was able to boot my step dad's VZW sIII using my battery.

Sounds like a hard brick. I think a USB jig might work.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!

Whiplashh said:
Sounds like a hard brick. I think a USB jig might work.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
Do you mean "USB jig" or JTAG? To my understanding USB jigs only worked on the sII, but that's just my understanding, which could be wrong.

Did you try this method?-click here

@jamcar If your phone turns on and you get Samsung screen it is NOT BRICKED.
A bricked device does not even turn on.
Hook your phone up to a computer and use odin to flash it back to stock. Or if you can boot into recovery just wipe cache, Dalvik and do factory reset and reflash the rom you are on.
Sent from the future via Tapatalk 4

edfunkycold said:
@jamcar If your phone turns on and you get Samsung screen it is NOT BRICKED.
A bricked device does not even turn on.
Hook your phone up to a computer and use odin to flash it back to stock. Or if you can boot into recovery just wipe cache, Dalvik and do factory reset and reflash the rom you are on.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I can't get past the first screen that says: SAMSUNG. I can't get into recovery, I can't get into download mode (which means I can't flash a new ROM and can't use ODIN), and can't boot my ROM.

jamcar said:
Do you mean "USB jig" or JTAG? To my understanding USB jigs only worked on the sII, but that's just my understanding, which could be wrong.
Click to expand...
Click to collapse
I thought I saw some people
using them on the s3 to get into Download mode. I heard some had worked.
edfunkycold said:
@jamcar If your phone turns on and you get Samsung screen it is NOT BRICKED.
A bricked device does not even turn on.
Hook your phone up to a computer and use odin to flash it back to stock. Or if you can boot into recovery just wipe cache, Dalvik and do factory reset and reflash the rom you are on.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
He said he couldn't get into recovery. Sounds like somehow his system and recovery got corrupted.
Edit: ALTHOUGH he did say hook it up to a computer then try booting it up!
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!

Ed is right, I done this for a friend who recently thought he bricked his phone.

joeyhdownsouth said:
Did you try this method?-click here
Click to expand...
Click to collapse
I have not, I'll start working on that now.
@joeyhdownsouth so far it is a no go.
But I also don't have a class 10 SD card, so I'll try again when I can get one, hopefully tomorrow. Anyone know why this happened?

jamcar said:
I have not, I'll start working on that now.
@joeyhdownsouth so far it is a no go.
But I also don't have a class 10 SD card, so I'll try again when I can get one, hopefully tomorrow. Anyone know why this happened?
Click to expand...
Click to collapse
I've had plenty of Samsung phones in some pretty bad states (including several hard bricks). Some very similar to your current situation. This includes the s2, s3, note 2, stellar and that's just naming a few. I've never had a phone that booted in any way shape or form and couldn't reach download mode. So if you're situation is as you describe then I'm pretty sure it's a first. Unless it's some sort of corruption (similar to the emmc brickbug that plauged the s2). Maybe even a less severe case of SDS. Just throwing some ideas out there but I bet this ends in needing a warranty repair from Samsung.

@jamcar How are you trying to boot into recovery the 3 finger method? Again I stand solidly on if the phone powers on and you see Samsung it's not bricked. You have other things going on but going through deBricker method is not the answer.
If your phone is powering on and you see Samsung logo then it goes black like it shut off you could be also experiencing the 'sudden death syndrome' which is a power button failure.
Try blowing some compressed air and paying with the power button. It is a known defect on the S3 and Sprint does replace the phone for this issue.
Sent from the future via Tapatalk 4

edfunkycold said:
@jamcar How are you trying to boot into recovery the 3 finger method? Again I stand solidly on if the phone powers on and you see Samsung it's not bricked. You have other things going on but going through deBricker method is not the answer.
If your phone is powering on and you see Samsung logo then it goes black like it shut off you could be also experiencing the 'sudden death syndrome' which is a power button failure.
Try blowing some compressed air and paying with the power button. It is a known defect on the S3 and Sprint does replace the phone for this issue.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I'm trying to boot into recovery by holding down power+vol up+home then in the corner I see "RECOVERY BOOTING..." then the screen goes black and nothing else happens. I try to go into download mode by holding power+vol down+home, I then get the custom OS warning sign, then if I push vol up the screen goes black, if I push vol down the screen goes black. This is with and without deBricker's SD card mod. (It has no affect).
EDIT: I have been looking into SDS for the sIII and most, if not all, threads are for the international sIII and most people say they fixed it by going through Samsung.
EDIT: if they [Samsung] some how get it into download mode, are they going to care that it looks modified? Custom download count (around 5), modified system status, etc.

If it works at all its not a hard brick. A hard brick needs a JTAG to recovery. Put it in Odin mode and flash from there
Sent from my SPH-L710 using xda app-developers app

IDontKnowMang said:
If it works at all its not a hard brick. A hard brick needs a JTAG to recovery. Put it in Odin mode and flash from there
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
ODIN mode is really called download mode, and if you read the post above yours and the OP then you'll see I can't get into download mode only the Custom OS Warning screen, which isn't download mode

You can't continue from the custom OS warning screen? That leads you to download mode doesn't it?

metalfan78 said:
You can't continue from the custom OS warning screen? That leads you to download mode doesn't it?
Click to expand...
Click to collapse
Usually but no matter what button I hit (vol up to continue into download mode---vol down to reboot) I just get a black screen. Every once in awhile (it has happened twice and I've tried many many times [~50+]) the Green android comes and it say "downloading..." but then the screen goes black and it is never seen by my computer / ODIN.
EDIT: the android comes up a for a spit second

Correct that's because his device is shutting down. The power button is bad. SDS... I sent you a reply to your PM. Worth a shot.
Sent from the future via Tapatalk 4

Okay I'll try Sprint then Samsung.

That explains why. You should definitely follow edfunkycold's suggestions.

edfunkycold said:
Correct that's because his device is shutting down. The power button is bad. SDS... I sent you a reply to your PM. Worth a shot.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
You say it is the power button other people say it is the eMMC. Which is it? I'm only trying to understand this SDS problem better.

[Q] My Phone Won't Boot Into Any Mode

So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch

neim81094 said:
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
Click to expand...
Click to collapse
i think the problem is on power button...
if the power button press contiues will be like that
i meet the same case like u...
sory my englis
press thanks if i help...

I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4

DocHoliday77 said:
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
It just turned on, I guess it was the power button.
Sent from my SGH-T999 using xda app-developers app

i'm experiencing a similar issue. I can only get any result while it's plugged in. it wont boot past the second splash screen, I got it into download mode and flashed the stock package from sammobile.com with no change. the phone keeps trying to boot into recovery after flashing stock but it goes to the android with the open chest screen and reboots and tries again over and over. i've taken the phone apart and seen nothing wrong, no corrosion, no water damage and i've even replaced the battery with no success. i tried flashing clockworkmod recovery, the flash was successful but it still wont even boot to recovery. the power button isnt stuck, i can manipulate it when i have the bare motherboard in my hands and still it's fine. would replacing the power switch have any affect? please any thoughts would be appreciated
edit: since flashing stock, plugging the phone into the computer with oem cable causes it to vibrate intermittently. holding power causes it to try recovery mode. running windows 7 with samsung drivers properly installed and adb recognizes my galaxy s2 and captivate no problems. someone mentioned on a post i read about using a 3 part stock rom, modem, pda and phone to flash instead of the all in one tar file, any thoughts?
another edit. this phone has never to my knowledge been rooted or had any kernel/rom flashed onto it. as far as i know it's stock from Wind mobile, 3 months past warranty