Last night we announced that the Samsung Galaxy S3 came along with a Locked bootloader! Nothing has changed with that. However we now have root thanks to some developers over at Rootzwiki! They have come up with a signed boot.img that includes root. The method is similar to the methods for other versions of the Galaxy S3. You will need to flash the modified boot.img in ODIN from there you will be able to push your Custom Recovery to the phone via ADB. The only downfall to this method that i can see is that the boot.img is 1.6GB! If you can manage to get it downloaded you should be good to go. Check out the source link for Download links and full instructions.

This is a good first step! Instructions Here

Jumping with excitement as I read from the screen of my Galaxy Nexus that the FedEx man had followed the directions that I had left taped to my door and placed my shiny new phone on the back porch, I frantically began to search all over the web for a root method! I had already known that the international Galaxy S3 was easily hackable and was already sporting root and custom recovery. I figured surely Verizon subscribers will see the same sort of thing for their device. Boy was I wrong. I quickly discovered a thread over at XDA filled with lots of disgruntled customers. They were pretty upset that they had been singled out! It appeared as if their devices were the only SGS3s in the world with a locked bootloader! Yes that’s right the International version, AT&T, T-mobile, and Sprint versions all have unlocked bootloaders. The Verizon version is the only version to have a protected bootloader.

The other US carrier versions of the SGS3 were pretty easily rooted just by flashing a custom boot.img in ODIN. This method does not work on the Verizon version because Verizon has added a security check, which means we won’t be able to flash any unsigned images. This doesn’t mean that the crafty development community won’t come up with a workaround. In fact they are working on that very thing. Some of the developers who would be responsible for a root method don’t even have the device in hand yet and were writing code without a device. I have to believe that someone will solve this issue within the coming days or even better within the coming hours. For more info on the progress being made check the source link.

Via DroidForums