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

[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

[Q] Problem after rooting t moble note 3 with kingo

Hi, this is the first time I've ever posted anything, so I hope I'm doing it correctly. I attempted to root my T Mobil note 3 using kingo one step rooting software. When it completed their was a message on my computer that read "successfully completed rooting" but when my phone went to reboot it had the Samsung galaxy logo appear along with a recovery booting in blue in the top left hand side of the screen and then one second later just under the blue "recovery booting" appears "set warranty bit : recovery" in yellow. then everything go's blank and it go's through the same proses all over again. It just keeps trying to boot. Dose anyone know what I can do to get it to boot. I tried holding the up volume bottom at the same time as the power and home but this dose nothing. Please help.

re: recovery-root issues
Triplingcs said:
Hi, this is the first time I've ever posted anything, so I hope I'm doing it correctly. I attempted to root my T Mobil note 3 using kingo one step rooting software. When it completed their was a message on my computer that read "successfully completed rooting" but when my phone went to reboot it had the Samsung galaxy logo appear along with a recovery booting in blue in the top left hand side of the screen and then one second later just under the blue "recovery booting" appears "set warranty bit : recovery" in yellow. then everything go's blank and it go's through the same proses all over again. It just keeps trying to boot. Dose anyone know what I can do to get it to boot. I tried holding the up volume bottom at the same time as the power and home but this dose nothing. Please help.
Click to expand...
Click to collapse
Since you seem to be having multiple issues with your phone your best bet
would be to Odin flash the stock official Tmobile firmware/rom for your phone.
You can download it from http://SamMobile.com .
After Odin flashing the stock firmware, use CF-Autoroot to root the phone.
Once it's rooted, you will need to Odin flash a custom recovery like TWRP
or CWM.
The stock official Odin flash firmware at Sammobile.com includes Odin
in case you need it.
You can try other ways to fix the problems you are having, but you will
most likely be wasting your time and effort and will need to Odin flash
the stock official firmware in any case.
Good luck!

Are you on KitKat? Kingo doesn't seem to work with 4.4.2. I tried the same thing- pulled the battery and got to download mode, then rebooted and used cf autoroot and have no problems. Good luck.
Sent from my SM-N900T using XDA Free mobile app

Triplingcs said:
Hi, this is the first time I've ever posted anything, so I hope I'm doing it correctly. I attempted to root my T Mobil note 3 using kingo one step rooting software. When it completed their was a message on my computer that read "successfully completed rooting" but when my phone went to reboot it had the Samsung galaxy logo appear along with a recovery booting in blue in the top left hand side of the screen and then one second later just under the blue "recovery booting" appears "set warranty bit : recovery" in yellow. then everything go's blank and it go's through the same proses all over again. It just keeps trying to boot. Dose anyone know what I can do to get it to boot. I tried holding the up volume bottom at the same time as the power and home but this dose nothing. Please help.
Click to expand...
Click to collapse
I actually JUST had this same issue. Thank God further research in another post helped me out. I took these steps:
1. Pull the battery
2. Wait for about a minute or so
3. Reinsert battery
4. Hold volume down + home + power button
5. A warning message will come up (forgot what it said) but choose the 2nd option (that you don't want to continue)
6. Phone will boot normally as before
I rebooted the phone again and have no further issues. I don't know if it is actually rooted (at this point, I don't care...haven't actually checked). I'm just happy this 3 hour ordeal is over!
Good luck!

Failed CF-Root - Can't boot into download mode

Galaxy Tab S 8.4, SM-T700. Received the lollipop update and that worked fine. Immediately tried to run CF-Auto-Root on it using Odin 3.07 and CF-Auto-Root-klimtwifi-klimtwifixx-smt700.tar.md5. I booted into download mode, started Odin and clicked Start. Only the first progress block in Odin lit up and the Tab S only showed about an inch of blue progress line. That was it for about 4 hours.
The tab was not responsive, shutting down Odin did nothing and trying a different Odin version also did nothing. So I had no choice but to disconnect the Tab S. Immediately rebooted to the "Firmware upgrade encountered an issue...." message. Running Kies does not recognize the tablet, running different versions of Odin with the stock firmware does nothing and the Tab won't do anything but restart into the "Firmware encountered an issue" screen. Won't go into download mode at all and nothing I do in Kies or Odin seems to work.
Last several times I've used CF-Auto-Root went flawlessly. This time, not. So if it continually reboots in to the "Firmware encountered an issue" screen, is there any recourse?
I have let it run out of juice and left it plugged in long enough to recharge fully but no matter what I do, it won't do anything but get to that one annoying screen!
Maybe there's a sequence of steps I'm missing. Anyway, been trying everything I can find out there on this but it's not working.
Thoughts?

You likely have a bad cable there. That's what happens.
You should be able to get download mode if it boots to the firmware failed screen
If you can boot to recovery then just wipe cache and it should boot.
From the firmware failed screen hold POWER + VOL DOWN + HOME until it restarts then immediately change to VOL UP whilst still holding the other buttons.
If that doesn't work try again with POWER + VOL DOWN + HOME until download mode boots.
If you still can't get either you can try the usb jig, which apparantly does work on this device.
Ask skOrPn which one to use, he use to build these things.

Hmmmm, you're right. I was using the Samsung cable that came with the tablet so figured there wasn't anything wrong with it (since one of the popular solutions is to not use a generic and make sure to use the Samsung).
So I dug deep in the vault for a slightly older Samsung cable from a previous phone and tried it. Sure enough - it worked. Odin completed the CF-Auto-Root in the 10 seconds it usually takes.
Clearly even Samsung cables go bad.
Thanks for pointing out the obvious but not so obvious!
Bob

Any way to recover Edge Plus?

Hi...
I got my S6 Edge+ rooted and attempted to install recovery via TWRP Manager app. This was a mistake and it failed. When I tried to reboot the phone, it became stuck on the start up Samsung logo screen, displaying the message "Recovery is not seandroid enforcing." Then it either sticks there...or quickly shuts down.
Pressing volume down/power reboots to logo screen and that's all.
Pressing volume up/power/home does nothing.
Pressing volume down/power/home gets me to screen where I can connect to Odin. That seems to be working okay. I've tried to flash a couple different recoveries, but nothing has an effect. Some seem to flash successfully but nothing changes. Others fail.
I also tried flashing a stock firmware file (G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5), but that failed.
Seems if I found the right file to use through Odin it might set things right. Or is there another possible solution? If anyone has any help or suggestions (or links!) I would much appreciate it.
Thanks...Mike

cosdog said:
Hi...
I got my S6 Edge+ rooted and attempted to install recovery via TWRP Manager app. This was a mistake and it failed. When I tried to reboot the phone, it became stuck on the start up Samsung logo screen, displaying the message "Recovery is not seandroid enforcing." Then it either sticks there...or quickly shuts down.
Pressing volume down/power reboots to logo screen and that's all.
Pressing volume up/power/home does nothing.
Pressing volume down/power/home gets me to screen where I can connect to Odin. That seems to be working okay. I've tried to flash a couple different recoveries, but nothing has an effect. Some seem to flash successfully but nothing changes. Others fail.
I also tried flashing a stock firmware file (G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5), but that failed.
Seems if I found the right file to use through Odin it might set things right. Or is there another possible solution? If anyone has any help or suggestions (or links!) I would much appreciate it.
Thanks...Mike
Click to expand...
Click to collapse
You flashed the wrong firmware for your phone, we have a S6 Edge+ G928T and the
firmware you flashed was for the G925T phone.
Make sure that before you odin flash the S6 Edge+ G928T firmware that you go into the
phone's recovery by pressing volume up, power and home button at the same time.
and do a factory reset or factory data reset first.
Your best bet is to odin flash the correct firmware and start from the beginning.
Here is a fast download link for the proper firmware for your phone (COKC):
https://www.androidfilehost.com/?fid=24337548750880895
Also the "Recovery is not seandroid enforcing." message you see is normal if
you have rooted and twrp'ed your phone.
Good luck,
Have a great day!

Thank you so much Misterjunky!
After I made that post I was looking at the file name that I copied in there...thinking it should include 928. Why I didn't notice before, I'm not sure, I think I was in a panic searching around for an answer.
The only problem is I can't go into the phone's recovery by pressing volume up, power and home button at the same time. I kept trying desperately to do that yesterday, but no luck.
Any suggestions on getting that working? I have the correct firmware file downloaded and ready to go. Thanks again for the help.
Mike

re: going to recovery mode
cosdog said:
Thank you so much Misterjunky!
After I made that post I was looking at the file name that I copied in there...thinking it should include 928. Why I didn't notice before, I'm not sure, I think I was in a panic searching around for an answer.
The only problem is I can't go into the phone's recovery by pressing volume up, power and home button at the same time. I kept trying desperately to do that yesterday, but no luck.
Any suggestions on getting that working? I have the correct firmware file downloaded and ready to go. Thanks again for the help.
Mike
Click to expand...
Click to collapse
There is another way to get into recovery, it's a bit complicated but if you do it just
right the phone will either go into stock recovery or twrp if you have twrp installed.
You have to have fast and accurate fingers for for the following:
First you need to go into "download" mode, then press the power,
home, volume up and volume down all at the same time until you
see the full black screen of the phone without any writing on it.
While still pressing all four buttons let go of the volume down button
while pressing the other three buttons, then keep pressing the three
buttons until you see stock or twrp recovery on the screen then let
let go of all the buttons.
Remember, when doing this you need to be not only fast but very accurate.
If you still cannot get into recovery then you need to go into download mode
and odin flash the official stock G928T firmware before doing anything else.
Good luck,
Have a great day!

Thanks again for the help Misterjunky. The alternate button presses to enter recovery didn't work either...the phone was very messed up.
Plus the battery wouldn't charge. It had drained out (because at first it wouldn't turn off), and so the phone would stay on only intermittently when plugged in. Not long enough to flash the firmware, which was very frustrating.
But suddenly, in desperation, I got a version of TWRP to flash successfully from Odin and open...which allowed the battery to charge. Then I was able to flash the firmware from your link, and after a couple of false starts, it was working perfectly.
I've subsequently found the correct version of TWRP to flash in your post in another thread, and it's fine. Now the phone is re-rooted and back to normal.

Misterjunky said:
You flashed the wrong firmware for your phone, we have a S6 Edge+ G928T and the
firmware you flashed was for the G925T phone.
Make sure that before you odin flash the S6 Edge+ G928T firmware that you go into the
phone's recovery by pressing volume up, power and home button at the same time.
and do a factory reset or factory data reset first.
Your best bet is to odin flash the correct firmware and start from the beginning.
Here is a fast download link for the proper
Also the "Recovery is not seandroid enforcing." message you see is normal if
you have rooted and twrp'ed your phone.
Good luck,
Have a great day!
Click to expand...
Click to collapse
I've had the same issue on my phone, however when I download the stock firmware and flash with TWRP I get an error: "could not locate meta-inf/com/google/android/update/binary"
It also freezes and crashes odin anytime i try to flash through there.
Am I missing something? I have the same model (SM-G928T)