[Verizon Samsung Galaxy S III] h311sdr0id:
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.