yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jg00d3:
I too am getting a signature verification failed on both root only and root+bootloader. All other steps prior to it work fine.

I am able to boot into recovery and I used CWM and copied boot root only and root + bootloader .zip files to my sd card.

My recovery mode at the top says "Android system recovery <3e> and I scroll down to the apply update from external storage option. when I hit the power button to ok the update from external storage i chose the .zip file.

If I choose the CWM-SuperSU-v0.00.zip file I get this message:

--Install /sdcard ...

Finding update package...

Opening update package...

Verifying update package...

E:failed to verify whole-file signature

E:failed to verify whole-file signature

E:signature verification failed

Installaion aborted.

If I run SuperSU_Bootloader.zip I only get the E:signature verification failed.

Thanks in advance for your help.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Okay so because many of you guys are reporting the signature verification issue. I have reuploaded #3 and #5 files that I just tested both working on my device using CWM. If you are still have trouble, trying to choose "install zip from sdcard" then "toggle signature verification", then try to flash it again. I can confirm they are both working so if you're still having trouble after that, try redownloading the file again.
[Verizon Samsung Galaxy S III] dixonba:
Still get signature verification failed with the #5 with _FIXED...flashing with cwm. Going to try the other recovery.

---------- Post added at 04:05 PM ---------- Previous post was at 03:43 PM ----------

It was never booting into CWM. Unchecked the auto reboot and was able to go directly to cmw after flashing.

---------- Post added at 04:21 PM ---------- Previous post was at 04:05 PM ----------

Ok. So here is the deal. If you allow you phone to boot without entering recovery it automatically flashes the stock recovery. Gotta have cmw disable the autoflash when it exits the first time.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Have figured out what is happening and it appears Custom Recovery is being overwritten if you allow the phone to boot into the OS after flashing your custom recovery. This didn't happen on the original factory images but I have updated the guide with proper steps now to fix this for the OTA.
[Verizon Samsung Galaxy S III] donrocko77:
You guys are amazing.. Ive had this phone 5 minutes and im going to pimp it out!!! Ive flashed the my E4GT 50 times and done a few S3s but didnt know if I should take the OTA. CM10, AOKP, AOSP here I come!
[Verizon Samsung Galaxy S III] SrgWallopy:
Probably the dumbest thing you will answer, in oden when you say flash, i flash it as "bootloader" right? and i throw the .taz in that one? correct?

Because of course the tutorial for ODIN on that site says, in the file name it will say PDA CSC, Bootloader yada yada but in your filenames they say none of these. And i'd rather not "fuc#$$#" something up... :D
[Verizon Samsung Galaxy S III] macdroid01:
Is there an easier way to just root?

Last time I followed a method by noxiousninja here where I just run a script after downloading samsung drivers and plugging in my phone. One button press. Is there.. or will there.. be a method like this, for rooting S III with the official (stock) JB?? It is not that I am lazy I just do not want to mess anything up. I may get into custom ROMs later but for now I can not get in to this with my phone. Rooting is the deepest I can go at this point. I want to keep it as simple as possible. Thanks all!
[Verizon Samsung Galaxy S III] SrgWallopy:
Sadly, no. As technology progresses they will only make it harder for us to do our "business". Unlike back in the old days where like on Windows Phone 3 you could just connect it type in a simple command and you were rooted. Now you have to do so much.
[Verizon Samsung Galaxy S III] Ryno77:
You ONLY flash using the PDA section unless something explicitly says to flash in another part of Odin. For everything in this thread it's the PDA section.
[Verizon Samsung Galaxy S III] Quacker:
Link for Samsung drivers is broken, but they can be found here. Click "see all downloads," then the software tab, then the EXE button.

Edit: Nevermind... it appears to be working again. You can get the latest version of the drivers with that link, though.
[Verizon Samsung Galaxy S III] bgs_piece:
I never accepted any of the OTA updates from Verizon so would I just be able to use your process here:

http://xdaforums.com/showthread.php?t=1974114
[Verizon Samsung Galaxy S III] n07y0ur5:
Is one better than the other???

I just Unlocked/Rooted/Updated from ICS to JB using VRBLK3. The following day the ota came out.

Should i factory wipe and get the ota. I guess the question is, is the ota better than the VRBLK3 that i have now.

If so whats the easiest way I can update to it while preserving root???
[Verizon Samsung Galaxy S III] longboardskier:
I went through this method and did root only and it worked like a charm. If I wanted to go back and unlock the bootloader would I only have to flash the unofficial bootchain and use the bootloader only option? Or would I have to do the whole process over again?
[Verizon Samsung Galaxy S III] oppis300:
I was same boat... I used OTA Root Keeper and was able to OTA and keep root and unlocked bootloader
[Verizon Samsung Galaxy S III] open1your1eyes0:
VRBLK3 factory image and the OTA are the same.

Not necessary. Just download the Unlocked Bootloader only zip file to your SD card and flash in your custom recovery.
[Verizon Samsung Galaxy S III] TommyTFC:
After the recent OTA update I had to reflash CWMR. I then downgraded the radio after the recent OTA update. I don't understand what the boot chains do. Should I ODIN the MD1 or the MD3 boot chain?
[Verizon Samsung Galaxy S III] joshua5683:
No problem, you don't get the prompt to disable recovery flash in twrp, only in cwm so you're fine. Are you getting the same error as earlier with CleanROM? You flashed SuperSU_Bootloader_FIXED.zip right? Make sure you complete every step in this guide before you start flashing, to see if you're rooted see if you have the Superuser or SuperSU app in your app drawer. And make sure the CleanROM zip md5 matches. If you don't know how to do that I can tell you

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] wrigbone:
Someone please help me out here...really frustrated. I got up to the step where I flash SuperSU_Bootloader_FIXED and when I needed to Disable recovery flash I think I hit yes but wasn't sure so I tried to hit the back button but I think the screen registered the choice above "no". The phone rebooted and about phone showed VRBMD3 although supersu shows up in the apps. I tried to go through all the steps from the beginning but I can't get into CWMR even though I'm getting no errors. Do I have to factory reset because of my mistake? Please help ASAP.
[Verizon Samsung Galaxy S III] Stvnx7:
I am getting the same error.

I did flash the SuperSU Bootloader zip, and I can see SuperSU installed.

I checked the md5 on the CleanROM on my SDCard vs. the MD5 in located here:

http://www.scottsroms.com/downloads.php?do=file&id=394

I am not sure what's going wrong.
[Verizon Samsung Galaxy S III] zachf714:
You reboot after flashing the zip right the. You flash the stock bootchain
[Verizon Samsung Galaxy S III] Stvnx7:
I did flash the stock bootchain, but I can't remember if I rebooted after installing the SuperSU zip file.
[Verizon Samsung Galaxy S III] zachf714:
You need to reboot so the partitions can rebuild
[Verizon Samsung Galaxy S III] Stvnx7:
Thanks - I'm a bit confused. Should I reboot after the SuperSU or after the stock bootchain? Or both?

[EDIT]

Also, what do I reboot into? Recovery, normal boot, or ODIN?

Sorry for all the questions.

[/EDIT]
[Verizon Samsung Galaxy S III] zachf714:
Both :)
[Verizon Samsung Galaxy S III] Stvnx7:
Thanks! In class right now but will do this after.
[Verizon Samsung Galaxy S III] Stvnx7:
I am sure I followed everything to a T this time. I'm going to try another ROM.

---------- Post added at 04:41 AM ---------- Previous post was at 04:03 AM ----------

Well, I am not sure why CleanROM wasn't working, but LiquidROM installed just fine.

I know that there is a thread on how to restore the phone to stock. I was wondering if I could get the stock ROM back w/o losing the root / unlocked bootloader. Or do I have to simply have to go with the Jelly Bean Factory Image (http://xdaforums.com/showthread.php?t=1974114) and then do the root / unlock process again?
[Verizon Samsung Galaxy S III] joshua5683:
The only way to do that is to flash a stock rooted zip, you'll find those in android development, or you could flash the factory image and root again

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] wrigbone:
Helping Hand

Hey everyone - I just wanted to take some time from my busy life to thank and hopefully help out some of my fellow man. I think a lot of people hit on run on here and that kinda sucks. Everyone will say they have too much going on but don't we all.

First I want to thank open1your1eyes0 for providing us an opportunity to take control of our device and guys like techspecs and SlimSnoopOS for stepping up and helping when they can. All the thanks meters and donations could never pay for the amount of time and effort that goes into something like this. You just gotta enjoy what your doing and feel good knowing your fingerprints are on a lot of devices and it made a lot of people happy :D

I've been reading a lot on these forums the past few days trying to root my phone and do it right. There is apparently a back lash from developers against the so called "newbs" because of how they come in and think they are entitled to "full service" just because someone made this available online. I think some people feel that if you put it up here you should be making sure it's bug free and help every person out that tries to whip through the process and goofs it up. There is nothing perfect (bug free) in the tech world and there are so many variables that come into play with something like this it's amazing that we can even get something this good. From myself on behalf of the newbs a lot of the seemingly demanding and/or rude posts come from fear, frustration, and uncertainty and I apologize for myself probably being guilty of that.

So - that being said. I would like to try to add some helpful info here for the next hit and run newb :silly:

I am rooted and rocking with a stock S3 and a downgraded radio(modem)

. After a lotta sittin on the fence maybe thinking this was overly dangerous I took the plunge last night. It did not go without incident however and I had to trouble shoot some things on my own. I had to go back and read the whole thread to look for a solution to my screw-up and learned a few things that may be helpful.

A lot of people watch the video first and there are some issues with it...

In the video the guys says "this time when Odin shows reset pull the battery" during the install of Clockwork (recovery) and then it shows him go to the phone and do that while Odin displays Reset. Some other folks had issues with this early on in this thread and everyone thinks they are doing the button combos wrong when trying to get into recovery. You must wait until Odin displays "Passed" before the battery. I had to let it sit for quite few minutes when it seemed like nothing was happening and it was done.

Be careful with the touch version of Clockwork. I ended up using the volumn buttons to be safe after my scew-up.

When reading through here be forewarned there is a lot of misinformation and half truths.

If you are just wanting to root your phone for control and because Verizon's latest OTA screwed up your data. Just follow the OP instructions to the T and then get the I535VRBMB1_firmware.zip which is the last radio and flash that in recovery (Clockwork or TR).

Thanks Again!
[Verizon Samsung Galaxy S III] Stvnx7:
Yea. I'm loving Liquidsmooth so I will stick with it.

Thank you for the help!
[Verizon Samsung Galaxy S III] open1your1eyes0:
Just an FYI for everyone: Verizon Pulls Latest Galaxy S3 Update After Reports of Connectivity Issues, is Working With Samsung on a Solution
[Verizon Samsung Galaxy S III] zachf714:
I have a question guys.. Can I install recovery with goomanager after I unlock
[Verizon Samsung Galaxy S III] nicholi2789:
Yes absolutely. That's the easiest way to install TWRP. As long as you rooted and unlocked the bootloader first.
[Verizon Samsung Galaxy S III] terrorblade23:
delete
[Verizon Samsung Galaxy S III] Biker1:
For TWRP Recovery 2.4.3.0 (Download this to your computer) - Link

MD5: 4B993052BB4905647FBD8B44E6096214

I'm having an issue with entering Recovery Mode during Rooting process.

I installed Recovery via Odin successfully.

I pulled the battery and pressed:

Power

Home

Vol up

Screen said:

Recovery Booting....

Samsung Custom w/an Unlock Emblem onscreen,

then the S3 Boots normally without entering custom Recovery.

I dl the custom recovery above several times, and installed via Odin several times.

Update:

Finally was able to get into TWRP Recovery.

The ms I saw the Recovery Booting in Blue in the upper left, I released the 3 buttons.

I thought I did that previously?

Anyway, I'm in Recovery and that's what counts ;)
[Verizon Samsung Galaxy S III] bigb78:
Simple question, for a old newbie that has been out of the root game for a while...

I am back, due to the OTA update that killed my data/sms reception.

I am about to root, so I can revert back to the old (April) software.

Step 6.... what bootchain do I want to install, to regain the old version?

Currently I am 4.2.1 - Baseband V #I535VRBLMD3. Do I use the MD3 in step 5/download 6 and then fix my OTA issue later, or do I just use the MB1 for Step 5, and that fixes the OTA update?

Thanks for the help! LOVE THIS SITE!

Edit: Found the MB1 Firmware for the modem, installed that ZIP, kept the stock OTA and I assume the MD3 Boot chain. Should be good?

Edit Edit: All seems great to my novice root skilz. :)
[Verizon Samsung Galaxy S III] Pegleg2060:
Thank you for the detailed post. It must have taken a lot of time and I just wanted to let you know it was really appreciated by my Wife and I.
[Verizon Samsung Galaxy S III] royta:
My downloaded file is filename.tar.tar (.tar extension), but when I hover over the "LINK", it shows filename.tar.md5 (.md5 extension). What extension should the downloaded file be? .tar or .md5? The md5 checksum checks out with the filename.tar.tar name.

Thanks. I'm anxiously awaiting to use my GS3 but need to root it so I can transfer apps & app settings over from my X2 with TitaniumBackup Pro.

Thanks!!
[Verizon Samsung Galaxy S III] bigb78:
What link are you referring to?

I did my S3 last night, no issues. All downloaded perfectly and I have root. I flashed the older firmware to get the working radio, now I can call and text again from my house! :) Thanks guys!
[Verizon Samsung Galaxy S III] royta:
The links in the OP for the two files to be flashed using odin.
[Verizon Samsung Galaxy S III] bigb78:
Sorry, I was vague in the question.

From OP, you mean the Recovery Download and the Boot Chain download links in step 1?

I downloaded the CWD Recovery and both 4.1.2 boot chain links and all came out .md5. You on a Mac?
[Verizon Samsung Galaxy S III] royta:
Nope...windoze xp. It comes out as a .tar.tar, regardless if I click the link or right click and save as.
[Verizon Samsung Galaxy S III] royta:
I'm going to stick with the .tar.tar, as that's the only way the md5 checksum matches. A .tar.md5 doesn't match for me. I even tried downloading wtih my phone and it was the .tar.tar.

I'm a bit confused on the the ODIN process. What am I supposed to do between Step 2 and Step 3? The beginning of Step 3 says to boot into ODIN mode, but the end of Step 2 doesn't say anything about rebooting. Am I supposed to power down the phone with the power button and power it back up into ODIN mode? How do I reboot at the end of Step 5? Power button again?

Thanks again!!!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Odin recognizes ".tar" and ".tar.md5" files. I suggest you make sure it reads "filename.tar" and not ".tar.tar" when you flash.

Don't be confused. When you open Odin, "auto-reboot" and "F. Reset Time" are enabled. When you flash the bootchain, it will automatically reboot. You do have to power down and boot back into download mode again in between each step.
[Verizon Samsung Galaxy S III] royta:
Are you sure I should remove the .tar extension? I figured I would leave it, as the first .tar would be considered a part of the filename. The entire filename including extension is VRALEC.bootchain.tar.tar. For some, the filename including extension is VRALEC.bootchain.tar.md5. The filename would be "VRALEC.bootchain.tar" followed by either a .md5 or .tar extension.

Although, the md5 checksum checks out either way. Still, I'm not too excited to brick my phone.

EDIT - Ok, I opened my eyes and saw there was a video. The steps are perfectly clear now. Though I'm still not sure what to do wtih the file extensions.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You could redownload the files on another computer. I just downloaded them on my MBP and the bootchain downloads as "vralec.bootchain.tar.md5" Same goes for the VRB bootchains and for the CWM tar. That's what I've always gotten on my MBP and my Windows XP.
[Verizon Samsung Galaxy S III] royta:
Google Chrome gave me the correct file extensions. I'm rooted and my apps & app settings are restored.

Thanks.

EDIT 6/18 - Just to clarify, both MS Internet Explorer and the stock JB 4.1.2 browser gave the file name a .tar extension. Google Chrome gave it the correct .md5 extension. Though, I'd bet the .tar would have worked too, after all, the contents of the packaged file is the exact same.
[Verizon Samsung Galaxy S III] RBarnett09:
From my understanding there is an even newer OTA, build number JZ054K.1200VRBME1, out there floating around that is newer than build number JZO54K.I535VRBMB1 that many people still have on their Galaxy S3.

If I rooted and unlocked the bootloader with this method, and then took the OTA when it comes through, will my phone be bricked?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Source?

No you would not brick. If you do not remove any System Apps and leave it stock then the OTA would only remove root and lock the bootloader.
[Verizon Samsung Galaxy S III] RBarnett09:
My bad, wrong build number.

It was build number JZ054K.I535VRBMD3.

Some people DID receive this OTA, but not many.

Just looked again and found out Verizon pulled the OTA back because it "crippled" the LTE connectivity and had several other issues.

Source: http://www.ubergizmo.com/2013/06/verizon-pulls-samsung-galaxy-s3-update-due-to-connectivity-issues/
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Ahh, it's all good.
[Verizon Samsung Galaxy S III] bgs_piece:
If I'm still on rooted VRBLK3 firmware, do I need to take the 2 ota's to get to BMD3 and then follow procedure in OP or do I need to take the first OTA, go through this process and then take the 2nd OTA and do this again?

Also, is there a pre-rooted version of the most recent OTA that can be installed and not go through this process?
[Verizon Samsung Galaxy S III] Biker1:
You may want to upgrade to MB1 instead, as MD3 has issues and has been pulled.

Download MB1 factory image to your pc and install via Odin

There's a tar.md5 which retains the stuff in your internal memory if you'd like.

Install the MB1 bootchain in the op, Root & Unlocked Bootloader, as well as the the Recovery of your choice, VRALEC boot chain, etc. in the op.

(Just follow the steps in the op)

The factory image will take 6 or so minutes.

The Rooting,Unlocking, Bootloader and Recovery will take a few minutes, and you'll be done.

There may be a faster, easier way, but I'm not sure of it.
[Verizon Samsung Galaxy S III] RBarnett09:
Do NOT take the MD3 update if you get it. You'll have issues like crazy.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] afextwin:
I just picked up an i535 to play around with, I've been rocking an i515 for the last year.

I took the MB1 update and then the MF1 update, should I Odin back to 4.1.1, take MB1 and then get off OTA, or should I just hold tight and wait for an MF1 bootchain? Or can I use heimdall to provide a bootchain? I would love to help but I'm not quite sure how :P

edit: I followed the guide with a small exception, I downloaded TWRP 2.5.0 d2spr tar file from openrecovery's website as the version linked in OP does not work with latest OTA. I also had to leave auto reset ticked on and as soon as the phone reset i held vol up+home. i released both buttons when i saw the small blue text in the upper left hand corner and twrp loaded. right now i've found that the su+bootloader fixed zip does flash su but does not unlock the bootloader, i got an error. so i'm about to try the unlock bootloader stand alone file. will edit post when done.
[Verizon Samsung Galaxy S III] anothen:
Thanks!

Just got my S3 today and this was a great guide! I've had several HTCs in a row and this ODIN process is a whole new world to me. Thanks for the great guide!
[Verizon Samsung Galaxy S III] zachf714:
Myself to with the HTC stuff .. Samsung stuff is a little easier to develop for
[Verizon Samsung Galaxy S III] wrigbone:
Is is safe to say that until I flash VRBMF1 bootchain I'm gonna get the nag from Verizon to update software? I just did the modem but don't see anyone putting a bootchain out there, just the full ROM (Which I am also considering).
[Verizon Samsung Galaxy S III] open1your1eyes0:
If anyone can pull the VRBMF1 update.zip from their /cache for me I can create the bootchain for you guys.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If you don't want to receive the OTA notification, freeze the " sdm 1.0" system app.
[Verizon Samsung Galaxy S III] jhentges:
ODIN wont recognize phone

Hey Everyone, So I am also new to Samsung have had all HTC Phones, I have the DNA now and am familiar with rooting them, but this is new to me.

SO I have everything downloaded ready to go, have USB debugging tried different ports and have everything set up correctly at least I think so, but odin wont detect the phone in downloading mode at all.

Would it have anything to do with maybe the HTC drivers installed on my computer with HTC sync?

Thanks!

---------- Post added at 11:02 AM ---------- Previous post was at 10:34 AM ----------

Never mind got it, I just kept unplugging it and plugging it back in and it worked, ODIN is kind of touchy isn't it?
[Verizon Samsung Galaxy S III] cybertec69:
Yea, same here, waiting for the VRBMF1 bootchain.

Had some issues today updating, updated to the new VRBMF1 ROM today, I am unlocked and rooted, well everything went fine, then when I went to reboot my device upon reboot I got the dreaded yellow triangle with the Not supported by Verizon software message, so I used ODIN to reflash the original image, and phone updated each software update one step at a time, now I am on the Verizon official VRBMF1 software, updated by Verizon. Phone is Locked and unrooted, would like to root and unlock again, but will not do so without the new VRBMF1 bootchain.

---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------

You need to have the samsung windows drivers installed.
[Verizon Samsung Galaxy S III] ericsdeadinside:
Where is the update.zip located?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If you deferred the OTA, its in /Cache like Open1your1eyes0 posted.
[Verizon Samsung Galaxy S III] PDAnuby:
Still no go for VRBMF1
[Verizon Samsung Galaxy S III] zachf714:
If you need for MF1 use Beanstown's casual app
[Verizon Samsung Galaxy S III] PDAnuby:
Can you please elaborate a little, I came here the last time to get root for Verzion VRBMB1, I just upgraded OTA to MF1 and came back to see if there was an update. I am not familiar with Beanstown's casual app and have not read all 83 pages on this post. thanks.