[HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)

Entropy512 · Aug 21, 2012

lowg said:
Agree, would be good to know the root cause -- eg. is it a bug having to do with some edge case in CWM recovery or a particular ROM that could fixed?

Does someone have a link to your recovery.rc?

If recovery.rc automatically mounts /system before starting CWM, you can sometimes wind up in a state where /system is mildly corrupted (needs an fsck), but can't be fscked or formatted because it's mounted - and in some cases, filesystem corruption causes it to be difficult to umount a partition to. Somehow this even derps up flashing to the partition in question using Odin (I guess it does some sort of partition checks before writing?) - this last symptom would often cause people to think they had suffered eMMC damage when they hadn't.

Galaxy Note (International - N7000) users had this problem on occasion and mistakenly called it "lost partial root".

Solution was easy - don't automount /system in recovery - https://github.com/CyanogenMod/andr...mmit/c362ad689ad24c4f64b58c7cada956808555ec21 was the solution there.

I've never seen this happen to /data before though... Although the GS3 has unified internal storage which could make this... interesting. Probably could be fixed by IMMEDIATELY doing a wipe data/factory reset. On a device with unified internal storage, navigating to /sdcard (linked to /data/media) for any reason would mount /data

Another option might be to try running a fsck from an ADB shell.

psycopanther · Aug 22, 2012

I do not believe it relates to recovery specifically. But still looking into it. Since this thread is a way to fix this, I would not worry to much. It happens rarely but sometimes the result could technically be cause by user error as with anything.

Breezer23 · Aug 22, 2012

Thank you so much! I just came for the Galaxy Nexus, thought I had teh bootloader unlocked but apparently not. I was stuck on that Unapproved Software screen. You fixed it. Thank you sir/ma'am.

Hero · Aug 22, 2012

Breezer23 said:
Thank you so much! I just came for the Galaxy Nexus, thought I had teh bootloader unlocked but apparently not. I was stuck on that Unapproved Software screen. You fixed it. Thank you sir/ma'am.

Sir, lol. Glad to know you got your phone back. Anyone else who fixes their phone by this method, please post here.

BeansTown106 · Aug 22, 2012

PureMotive said:
Sir, lol. Glad to know you got your phone back. Anyone else who fixes their phone by this method, please post here.

thanks couldnt boot for hours this worked!!!!

h311sdr0id · Aug 22, 2012

08/24/2012@16:02MST--------------------------------------------------------------------------------------------------------------------------------------------------
<EDIT BEGIN>

TESTED FLASHING ONLY THE SECOND BOOTCHAIN AND ROOT66:

I have been doing some more research on this procedure for the OP and have discovered a way to shorten the process. I know that before you were supposed to flash both bootchains before flashing root66. I wanted to see if it was possible to just flash "BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5" without having to flash "VRALEC.bootchain.tar.md5" beforehand.

I tested it four (4) times on my device and it worked every single time. I had to use my method of plugging/unplugging and starting/restarting (if you read below on how I had to go through PureMotive's process a little differently). All I did was flash the second bootchain and then root66, and I was fine (using the plugging/unplugging and starting/restarting as I explain below).

-
-
-
NOTE: PLEASE DOWNLOAD FILES FROM PUREMOTIVE'S OP.
-
NOTE: I AM JUST USING THE KNOWLEDGE FROM THE OP AND A COUPLE OF TIPS I HAD ADDED TO MAKE THIS TUTORIAL. ALL CREDIT GOES TO PUREMOTIVE. HE IS THE ONE THAT FIGURED THIS ALL OUT. PLEASE THANK HIM.
-
-
1. Make sure your device is off. Turn on your device so that it is in "Download Mode" (volume-down+home+power). When the first "Warning Screen" appears, press the volume-up button.
---
1a. First off, it is always good to make sure your drivers are installed properly. If you have already installed themin the past, it's okay to install them again. If your not sure, install them anyways. If they have already been installed, you will get this popup asking you if you still want to install them again.
-

---
2. If you received the popup in image "1" above, then you will now be at this screen. Or if this is the first time you have installed the drivers, you will start here as well. Go ahead and press "Next" to continue.
-

---
3. Pick your language and country. Press "Next" to continue.
-

---
4. The default location is usually the best. Press "Install".
-

---
5. Wait for the Drivers to install.
-

---
6. Drivers are installed. Press "Exit"
-

---
7. Don't plug anything in yet. Start ODIN, and this screen will appear.
-

---
8. Now, "Plugin" your Device.
-

---
9. Make sure that ONLY the "F. Reset Time" checkbox is checked.
-

---
10. Click the checkbox next to "PDA" and click on the "PDA" buton to find your "BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5" that you downloaded earlier. ODIN will check the MD5, so wait a second to make sure it is done checking. Click "Start".
-

---
11. It will finish very fast and show the BLUE box saying "RESET". Wait.
-

---
12. Wait a few more minutes. The box will then turn GREEN and say "PASS". Now Unplug your device and Exit out of ODIN. DO NOT REBOOT YOUR PHONE OR PULL THE BATTERY.
-

---
13. Now Restart ODIN.
-

---
14. Plugin your device.
-

---
15. Leave the two boxes thatar e already checked and check the "Nand Erase All" so that there will be three boxes checked now.
-

---
16. Click the checkbox next to PDA and click the PDA button to locate your "root66" file. Make sure it is in .tar format.
-

---
17. Press Start.
-

---
18. The BLUE Reset box will now appear. Wait
-

---
19. The GREEN Pass box will now appear.
-

---
20. Unplug your device, Pull your battery, Re-insert your battery, hold down "volume-up+home+power", boot into the stock recovery, (notice that you will have a few lines of "errors" in red lettering and all starting with E:......) these errors are normal, Wipe Data/Factory Reset, Wipe Cache, Reboot.
-
-
-
-
-
I WOULD ALSO LIKE TO ADD:

When I was trying to figure out a fast way to get back to root66 or stock from Beans ROM easily, I ran into a few problems booting:

I would get stuck in Odin after flashing the bootchain(s) during the root66 installation (when I would try to install the root66 with Odin after performing the bootchain flash/flashes, it would not show it was installing and the texbox showing you your progress would just stop at some point. Also the Exit/Reset/Start buttons were not available to press either during this time and the only option was to exit out of Odin by clicking the "x" in the upper right-hand corner pulling the battery [because it was still in "Download Mode"].

I figured out that if you ever get stuck in any of these two situations and HAVE TO pull the battery, just make sure when you restart the device, you boot into the stock recovery (volume up+home+power). Then you need to do a "factory wipe/install and cache wipe", reboot, and your good-to-go.

<EDIT END>
08/24/2012@1620MST----------------------------------------------------------------------------------------------------------------------------------------------

08/23/2012
ORIGINAL POST:

Background:

Device:

Samsung Galaxy SIII (S3)

Verizon Wireless

Was running CM10 (cm-10-20120818-NIGHTLY-d2vzw) and gapps (gapps-jb-20120726-signed).

ClockWorkMod Recovery 6

Unlocked bootloader using the "Casual App" from Adam Outler.

Ubuntu Machine

I had been running CM10 on one of my Samsung Galaxy S3's. I have one that I keep on me all the time and I usually only load stable ROMS onto it. The other one I play with and use for reviews. I had tried to get back to "root66" by just flashing it over the CM10. I should have read into it more...

I luckily found this post, followed the directions, but it would not work for me... I was having trouble in ODIN and the program would not flash the second bootchain unless I:

1: Flashed the first bootchain as described.

2: Unplugged my device while leaving it in "Downloading Mode".

3: Exited ODIN and then restarted it.

4: Plugged my device back in while still in "Downloading Mode".

5: Flashed the second bootchain.

6: Repeated steps 2, 3, and 4.

7: Then flashed root66.

Issues Prior:

My Samsung Galaxy S3 was stuck in a boot loop and I tried everything.

1 in every 5 times, it would actually boot, but once the lockscreen came up, it froze and I had to pull the battery.

Other Issues:

Had to use a workaround (that might only be specific to my problem, but I thought I might share it just in case anyone else is having the same issue).

Questions

None anymore.

I could not have fixed my device without this. It is working fine now.

Thanks to PureMotive for all of his help.

ker2gsr · Aug 22, 2012

h3llsdr0id said:
Background:

I luckily found this post, followed the directions, but it would not work for me... I was having trouble in ODIN and the program would not flash the second bootchain unless I:

1: Flashed the first bootchain as described.

2: Unplugged my device while leaving it in "Downloading Mode".

3: Exited ODIN and then restarted it.

4: Plugged my device back in while still in "Downloading Mode".

5: Flashed the second bootchain.

6: Repeated steps 2, 3, and 4.

7: Then flashed root66.

[/B]

Issues Prior:

My Samsung Galaxy S3 was stuck in a boot loop and I tried everything.

1 in every 5 times, it would actually boot, but once the lockscreen came up, it froze and I had to pull the battery.

Other Issues:

Had to use a workaround (that might only be specific to my problem, but I thought I might share it just in case anyone else is having the same issue).

Questions

None anymore.

I could not have fixed my device without this. It is working fine now.

Thanks to PureMotive for all of his help.

this was my same issue with odin was trying all day to it with no luck till i saw your post your steps works still big thanks to all who have help us and who came up with this fix h3llsdroid and pure motive you save me

Helpercell · Aug 22, 2012

I have a soft bricked sgs3 verizon but the links to the files in this post dont work. Can I please getting working links.

Hero · Aug 23, 2012

h3llsdr0id said:
Background:

Device:

Samsung Galaxy SIII (S3)

Verizon Wireless

Was running CM10 (cm-10-20120818-NIGHTLY-d2vzw) and gapps (gapps-jb-20120726-signed).

ClockWorkMod Recovery 6

Unlocked bootloader using the "Casual App" from Adam Outler.

Ubuntu Machine

I had been running CM10 on one of my Samsung Galaxy S3's. I have one that I keep on me all the time and I usually only load stable ROMS onto it. The other one I play with and use for reviews. I had tried to get back to "root66" by just flashing it over the CM10. I should have read into it more...

I luckily found this post, followed the directions, but it would not work for me... I was having trouble in ODIN and the program would not flash the second bootchain unless I:

1: Flashed the first bootchain as described.

2: Unplugged my device while leaving it in "Downloading Mode".

3: Exited ODIN and then restarted it.

4: Plugged my device back in while still in "Downloading Mode".

5: Flashed the second bootchain.

6: Repeated steps 2, 3, and 4.

7: Then flashed root66.

Issues Prior:

My Samsung Galaxy S3 was stuck in a boot loop and I tried everything.

1 in every 5 times, it would actually boot, but once the lockscreen came up, it froze and I had to pull the battery.

Other Issues:

Had to use a workaround (that might only be specific to my problem, but I thought I might share it just in case anyone else is having the same issue).

Questions

None anymore.

I could not have fixed my device without this. It is working fine now.

Thanks to PureMotive for all of his help.

I'm going to add these steps to the OP. Thanks for your help.

Helpercell said:
I have a soft bricked sgs3 verizon but the links to the files in this post dont work. Can I please getting working links.

The links are working.

droidstyle · Aug 23, 2012

Edit* found my answer thx.

Attreau · Aug 23, 2012

Hey all.....this post just saved my Galaxy S3. I made the mistake of trying to restore Bean's ICS Rom after having moved to the CM 10 nightlies and yes, I had unlocked the bootloader. Was getting a non-boot situation where it would just show the Galaxy Samsung screen and never continue past it. Performing the above and rather than installing the stock Verizon, I installed the rooted Verizon and did not do the "NAND erase all". I am extremely happy I brought it back to life!

Thanks,

Attreau

tekrhino · Aug 24, 2012

Big Thanks to the OP and all involved

This thread saved my SGSIII from brickedom!

Big THANK YOU to the OP and everyone involved in putting this thread together!

My Device was soft bricked when I messed with the NFC thread.
And all I did was edit my Build.prop file and attempted to reboot.

Thanks again!

punwik · Aug 25, 2012

Just wanna say thanx for the know how to get this done! I had tried to flash a cm10 rom and for some reason it did the same thing as the OP and changed my mounting to where my phone wouldnt boot! I tried everything with odin and CWM to know avail until I found this thread! Except in my case the first 2 files would not pass for me for ****! I finally said **** it I dont care if I brick it or not and I put the root66 file in the bootloader slot and hit start and it went through the whole install process and bingo it worked for some reason! Many many thanx to all the work put in on this!

Saved My A$$...

psycopanther · Aug 26, 2012

so glad this is helping many of you guys (and girls). remember to give thanks to OP

drbobmd · Aug 26, 2012

psycopanther said:
so glad this is helping many of you guys (and girls). remember to give thanks to OP

Nobody EVER forgets to thank the developers... Where do you think we are, Apple support?

eameda · Aug 26, 2012

I need some serious help here guys. I softbricked the phone because for some reason the ez unlock app didnt unlock the bootloader and I tried using this method to fix the error but everytime I get to the part where I flash root66 odin flashes boot and then recovery but once it gets to system.img.ext4 it fails. I (like the idiot I am) pulled the battery hoping it would flash again but not when i boot into odin mode on the phone it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I have no idea what to do. I am wondering if the file is corrupted or something. I also tried downloading it again but the only place i could find it was via the torrent. Any help would be appreciated.

drbobmd · Aug 26, 2012

eameda said:
I need some serious help here guys. I softbricked the phone because for some reason the ez unlock app didnt unlock the bootloader and I tried using this method to fix the error but everytime I get to the part where I flash root66 odin flashes boot and then recovery but once it gets to system.img.ext4 it fails. I (like the idiot I am) pulled the battery hoping it would flash again but not when i boot into odin mode on the phone it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I have no idea what to do. I am wondering if the file is corrupted or something. I also tried downloading it again but the only place i could find it was via the torrent. Any help would be appreciated.

Did you verify the md5 sums?

eameda · Aug 27, 2012

drbobmd said:
Did you verify the md5 sums?

How would I go about doing that?

droidstyle · Aug 27, 2012

You dont need this method for your issue. Flash the stock kernel, then flash root66 in odin. That should bring you back to life.

h311sdr0id · Aug 27, 2012

eameda said:
I need some serious help here guys. I softbricked the phone because for some reason the ez unlock app didnt unlock the bootloader and I tried using this method to fix the error but everytime I get to the part where I flash root66 odin flashes boot and then recovery but once it gets to system.img.ext4 it fails. I (like the idiot I am) pulled the battery hoping it would flash again but not when i boot into odin mode on the phone it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I have no idea what to do. I am wondering if the file is corrupted or something. I also tried downloading it again but the only place i could find it was via the torrent. Any help would be appreciated.

I was wondering if you had gotten everything working. If you are still stuck, let me know. I think I might have something that might also help.

[HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)

Senior Recognized Developer

Senior Member

Senior Member

Inactive Recognized Developer

Inactive Recognized Developer

Inactive Recognized Developer

Senior Member

Member

Inactive Recognized Developer

Inactive Recognized Contributor

New member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Inactive Recognized Contributor

Inactive Recognized Developer

Similar threads

Top Liked Posts