ok heres the play by play of what i did to get from a fully functioning s3 to brick.
I used Samsung GS3 toolkit and rooted did full nandroid backup installed CWM recovery 5 something then i went to install the at&t version of cynogenmod10. which seemed to be working fine but i was without the google play store on that rom so i installed from zip and i wasnt happy with how it looked so i decided to go back to my nandriod backup which i did threw recovery. when it was doing the recovery it didnt successfully restore the (system) folder. Then i rebooted and am now stuck in bootloop where it just shows the samsung logo. ive tried going into recovery and it doesnt work. It will flash with the screen saying going into recovery with blue writing on top left. then goto black till i release the buttons then it continues into bootloop. any help would be appreciated right now im installing andriod sdk to view the boot log as it boots up.
curry67 said:
ok heres the play by play of what i did to get from a fully functioning s3 to brick.
I used Samsung GS3 toolkit and rooted did full nandroid backup installed CWM recovery 5 something then i went to install the at&t version of cynogenmod10. which seemed to be working fine but i was without the google play store on that rom so i installed from zip and i wasnt happy with how it looked so i decided to go back to my nandriod backup which i did threw recovery. when it was doing the recovery it didnt successfully restore the (system) folder. Then i rebooted and am now stuck in bootloop where it just shows the samsung logo. ive tried going into recovery and it doesnt work. It will flash with the screen saying going into recovery with blue writing on top left. then goto black till i release the buttons then it continues into bootloop. any help would be appreciated right now im installing andriod sdk to view the boot log as it boots up.
Click to expand...
Click to collapse
If you can't get into recovery your only option is to reflash a stock rom via ODIN. This is assuming you can get into download mode. (Vol Up + Home + Power) Stock images can be found here: http://forum.xda-developers.com/showthread.php?t=1968625
Follow the directions in the post. Once you are done with the flash, go into recovery and factory reset, wipe dalvik and wipe cache. Reboot and you should have a fully functioning s3 again. Albeit a unrooted s3, but a function s3 nonetheless. You will have to re-root, re-install cwm (I recommend looking into TWRP instead, better recovery IMO), and then you can start flashing again. Make sure you make another Nandroid before continuing to flash. =)
root-injected stock recovery here: http://forum.xda-developers.com/showthread.php?t=1739426
oh ok i found out i wasnt releasing the buttons properly i am now in recovery mode so im guessing the route to go now is to do factory restore im wondering is there a factory image to do that or do i have to download one ive downloading one now from a source on xda
ok so i got the stock firmware and i did factory wipe with catch and dalvik. then i booted into download mode and but in odin 3.07 it isnt being recognized like the box isnt displaying. Im gonna try some different cables and maybe reboot my computer.
curry67 said:
ok so i got the stock firmware and i did factory wipe with catch and dalvik. then i booted into download mode and but in odin 3.07 it isnt being recognized like the box isnt displaying. Im gonna try some different cables and maybe reboot my computer.
Click to expand...
Click to collapse
You may not not need Odin. Load a ROM on a SD card and just flash it. Sounds like you just have a bad flash. A basic soft brick.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
yeah ill give that a go. gotta love havin these canada variants. oh yea would i flash the zip folder the mp5 file came in?
Related
I have been trying to find an answer for the last several hours. But I can't seem to get anything to work.
I have the AT&T GS3 and I was able to flash AOKP but then I wanted to revert back to stock. I tried the toolkit and followed the steps and what might of happened is that AOKP did not get wiped completely when I flashed the stock image. Now after successfully flashing the stock image (I get the PASS! on Odin), my phone is stuck while booting. It goes past the AT&T boot image but gets stuck on "SAMSUNG". I tries flashing through ODIN, another downloaded version of the stock image but it didn't work. What am I doing wrong?
Another problem with being stuck in bootloop is that since I flashed the stock image; I think I no longer have CWM. I can't find a way to get to recovery.
I'm not really sure how to help but if you can get to the boot animations you aren't bricked. I know you're not on verizon but in this thread: http://forum.xda-developers.com/showthread.php?t=1759642 it says when coming from an AOSP rom back to the stock rom you have to flash a stock boot.img before flashing the stock rom. Hope you can get it working again
Did you make a nandroid backup before you flashed the Rom...if you did you can restore from cwm recovery...hold power, volume up, and home...after the screen goes black let go of the power...hope this helps
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If you can get into download mode , just flash recovery from odin.
And how long have you waited at samsung logo , it might take few minutes to bootup.
I don't have CWM recovery. It got stuck on the Samsung logo for 20 minutes before I gave up and did a battery pull.
What do I flash through odin to get it working again. Which recovery file?
Ok, I just used the method described in this article and I am still stuck at the SAMSUNG logo.
http://www.androidegis.com/how-to/unbrcik-your-us-samsung-galaxy-s3-how-to/
http://forum.xda-developers.com/showthread.php?t=1727443
Tried that. Still same problem. Noticed that the boot-stock-att-sgh-i7.tar is only 10.5 mb. I don't know much about this, but is that tar file enough to get me unbricked?
usually the .tar file should be much larger than that. It's possible that the file you downloaded got corrupted. Try re downloading the file and than flashing it again.
Sent from my SCH-I535 using xda premium
If you look in the mediafire link inside ths artivle, you will notice that the download is only 10 mb
http://forum.xda-developers.com/showthread.php?t=1727443
try this
VJKotts said:
I have been trying to find an answer for the last several hours. But I can't seem to get anything to work.
I have the AT&T GS3 and I was able to flash AOKP but then I wanted to revert back to stock. I tried the toolkit and followed the steps and what might of happened is that AOKP did not get wiped completely when I flashed the stock image. Now after successfully flashing the stock image (I get the PASS! on Odin), my phone is stuck while booting. It goes past the AT&T boot image but gets stuck on "SAMSUNG". I tries flashing through ODIN, another downloaded version of the stock image but it didn't work. What am I doing wrong?
Click to expand...
Click to collapse
Get into download mode
clear cache option
factory reset phone option
That should fix it
CC
How do you factory reset/clear cache in download mode?
VJKotts said:
How do you factory reset/clear cache in download mode?
Click to expand...
Click to collapse
just re flash stock in odin flash Flash this file http://forum.xda-developers.com/showthread.php?t=1737848
I think I bricked my Rogers S3.
I had JB running on it. Today I decided to root it again ( I rooted it couple of months ago and then went back to stock). I did the same procedure as last time i.e. using toolkit, however, when I had to choose which file to choose in odin to be flashed in insecure boot, I chose "boot-insecure-spr-l710palen.tar" instead of choosing "boot-insecure-canada-rogers-i747mvale8.tar".
Now after odin finished doing ALLINONE "insecured boot, CWM, root phone + install busybox", my phone restarted and I could hear the samsung logo voice but the screen was totally blank.
I went back to odin and chose ALLINONE "insecured boot, CWM, root phone + install busybox" and this time chose the right file but still the same thing.
So now I decided to unroot the phone by flashing the custom rogers version back on, so I flashed the custom rom using ODIN but still my phone keeps on getting stuck at the samsung logo at the start up. It doesn't go any further.
Is it bricked? How can I solve this problem? Thanks
Note: If i press volume up+home+power, I can get into the mode where it gives me the options to reboot, wipe etc.
Should I try to root it again and try to get into recovery mode to see what can be done to fix it?
Bumped!!!!!!!!!
It's a soft brick, so you're okay.
Just download Odin and flash a restore image on your phone with it.
Search the "development" subforum for "Odin" and you'll find everything you need.
CZ Eddie said:
It's a soft brick, so you're okay.
Just download Odin and flash a restore image on your phone with it.
Search the "development" subforum for "Odin" and you'll find everything you need.
Click to expand...
Click to collapse
No no...do a factory reset
sent from outside ur window
twanskys204 said:
No no...do a factory reset
sent from outside ur window
Click to expand...
Click to collapse
Yup. It worked. I just performed a factory reset along with cache wipe and phone started working again. Thanks guys.
Earlier this morning I was trying out a new rom and I didn't like it. I went back into recovery and wiped the cache dalvik and system and flashed a different rom, I think it was paranoidkangdroid. After it booted up I went to the playstore to download TitaniumBackup. It finished downloading but when I went to the app drawer it wasn't there. I just did the steps from http://forum.xda-developers.com/showthread.php?t=1739426 to put a rooted stock image of the phone onto the phone. Odin says that it passed but now my phone is stuck at the Samsung logo. It makes the noise and does the whole ATT splash screen business but it just sits there. It's been like this for about 15 minutes. The phone is still connected to my PC if that makes a difference. Anyone have any idea on what to do?
Edit: I've also posted in their thread.
DynamiteRave said:
Earlier this morning I was trying out a new rom and I didn't like it. I went back into recovery and wiped the cache dalvik and system and flashed a different rom, I think it was paranoidkangdroid. After it booted up I went to the playstore to download TitaniumBackup. It finished downloading but when I went to the app drawer it wasn't there. I just did the steps from http://forum.xda-developers.com/showthread.php?t=1739426 to put a rooted stock image of the phone onto the phone. Odin says that it passed but now my phone is stuck at the Samsung logo. It makes the noise and does the whole ATT splash screen business but it just sits there. It's been like this for about 15 minutes. The phone is still connected to my PC if that makes a difference. Anyone have any idea on what to do?
Edit: I've also posted in their thread.
Click to expand...
Click to collapse
Did you clear data/cache before/after flashing the stock ROM?
If you didn't, boot to recovery (Vol Up + Home + Power) and do so.
smelenchuk said:
Did you clear data/cache before/after flashing the stock ROM?
If you didn't, boot to recovery (Vol Up + Home + Power) and do so.
Click to expand...
Click to collapse
I did it before flashing the new rom. Now the only recovery I have on the phone is what I think is stock recovery. I had teamwin recovery on it and now it looks more like clockworkmod, so I'm assuming that's stock. I went into that recovery and did a factory reset which apparently worked. (As I'm typing this it's fixed)
Mods can delete this thread.
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
So i attempted to root my gs3, i had succeeded in doing so. i had cm10 flash and was looking good but once i tried to flash gapps to my phone, i am now stuck right before the os boots up and get an error message saying that gapps has stopped working and must force close and unfortunately, setup wizard has stopped working. after attempting to recover using twrp, which failed, i tried to flash my recovery zip i had made from titanium backup. now i am still stuck at previously mentioned screen but twrp is now gone and when i boot into recovery mode it comes up with the stock mode. being dumb and thinking that the recovery from titanium would be enough i didn't make a back-up using nandroid. i can still get to download mode as well as recovery mode but i am not entire sure if usb debugging mode is still on or not. i have odin downloaded on my computer but am not entirely sure on how to go about restoring my phone. at this point i'd be happy just to get it back up and running stock. can anyone help?
Update:So i downloaded a stock rom and tried flashing it using odin and now i am stuck on the samsung splash screen. been waiting about 5 min. but would still appreciate any input if possible
Teeter89 said:
So i attempted to root my gs3, i had succeeded in doing so. i had cm10 flash and was looking good but once i tried to flash gapps to my phone, i am now stuck right before the os boots up and get an error message saying that gapps has stopped working and must force close and unfortunately, setup wizard has stopped working. after attempting to recover using twrp, which failed, i tried to flash my recovery zip i had made from titanium backup. now i am still stuck at previously mentioned screen but twrp is now gone and when i boot into recovery mode it comes up with the stock mode. being dumb and thinking that the recovery from titanium would be enough i didn't make a back-up using nandroid. i can still get to download mode as well as recovery mode but i am not entire sure if usb debugging mode is still on or not. i have odin downloaded on my computer but am not entirely sure on how to go about restoring my phone. at this point i'd be happy just to get it back up and running stock. can anyone help?
Click to expand...
Click to collapse
If you have Odin already you need to just download the stock rooted rom and flash it. Make sure when you flash a custom Rom that your recovery is up to date and you download the correct gapps package.
Ignore any file names. The video is just too get you accustomed to Odin.
https://www.youtube.com/watch?v=OqinDlH4hII&feature=youtube_gdata_player
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Boot into stock recovery, the perform a factory reset. Reboot and enjoy.
Sent from my SGH-I747 using xda app-developers app
After flashing the stock rom in ODIN, boot into recovery and wipe data and & the cache. Reboot
Stock roms
Teeter89 said:
So i attempted to root my gs3, i had succeeded in doing so. i had cm10 flash and was looking good but once i tried to flash gapps to my phone, i am now stuck right before the os boots up and get an error message saying that gapps has stopped working and must force close and unfortunately, setup wizard has stopped working. after attempting to recover using twrp, which failed, i tried to flash my recovery zip i had made from titanium backup. now i am still stuck at previously mentioned screen but twrp is now gone and when i boot into recovery mode it comes up with the stock mode. being dumb and thinking that the recovery from titanium would be enough i didn't make a back-up using nandroid. i can still get to download mode as well as recovery mode but i am not entire sure if usb debugging mode is still on or not. i have odin downloaded on my computer but am not entirely sure on how to go about restoring my phone. at this point i'd be happy just to get it back up and running stock. can anyone help?
Update:So i downloaded a stock rom and tried flashing it using odin and now i am stuck on the samsung splash screen. been waiting about 5 min. but would still appreciate any input if possible
Click to expand...
Click to collapse
=====================================================
Sometimes when you search the for the stock rom they don't give you a good or the actual stock rom i get mine from sammobile.com