yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] prdog1:
The thing is did she actually get the upgrade. Check baseband. If she had custom recovery would have got the update but would not actually flash. If it flashed there was something wrong with her original root flash. :cool:
[Verizon Samsung Galaxy S III] suprdave2:
I figured out what it was. There are no steps in this thing for actually unlocking your bootloader - this was the problem. The bootloader must be unlocked :) EZ-Unlock did it fine
[Verizon Samsung Galaxy S III] Joey22688:
the bootloader unlock (optional) is in step 3, you should be able to flash a custom recovery without unlocking it first using the provided files

the md5 failed on me once when I tried to flash the rom, I just restarted it and tried again and it passed
[Verizon Samsung Galaxy S III] prdog1:
You can flash recovery without unlocking but will need to get Triangle Away to fix your flash count. :cool:
[Verizon Samsung Galaxy S III] suprdave2:
Well, I'm not sure what to provide besides evidence from my phone :) Very strange that mine acts this way if it's not supposed to.

Here's what Odin tells me when EZ-Unlock says my bootloader is unlocked:

Here's what it tells me when EZ-Unlock says my bootloader is *locked*:
[Verizon Samsung Galaxy S III] prdog1:
Not supposed to be hooked to Odin unlocked. It don't know what to do. Once unlocked you broke all signature checks. You only use Odin to flash Image and Boot chain. After that never need Odin again till want to go back to stock or start over and upgrade again. :cool:
[Verizon Samsung Galaxy S III] suprdave2:
I know that you only use Odin to flash images. I was just showing that for my particular phone my bootloader has to be unlocked first before I can flash the recovery image.

Regardless it works great now. This was actually the third time I went through this flash cycle in order to provide this output. It is consistent in wanting the bootloader to be unlocked first.
[Verizon Samsung Galaxy S III] prdog1:
I've done every leak that has been released and have had no problems. It is not the phone it is the phone operator. Odin prefers you to be stock. It knows nothing about unlock. It does not see lock or unlock. It sees a usb hookup and that only. :cool:
[Verizon Samsung Galaxy S III] suprdave2:
Can you explain more thoroughly then what this error means?

"<ID:0/004> FAIL! (Auth)"

Understanding what that error means may help me understand what EZ-Unlock is doing to the phone to make Odin not show that error when it's unlocked. There is a clear cause and effect relationship between the two with the process I am going through.

I know you mentioned "Once unlocked you broke all signature checks" - Which signature checks are you referring to?

Here's the exact steps I am taking:

* Boot phone to Odin mode

* Open Odin 3.07

* Select VRBLK3_Bootchain_CWM.tar.md5 in the PDA slot (Note that the md5 checks Odin performs pass in the output I provided earlier)

* Click Start

* It fails with "<ID:0/004> FAIL! (Auth)", and the phone shows a similar error on the screen about: Secure auth failed: recovery

* Reboot phone, download EZ-Unlock from the play store click Unlock

* Boot phone back to Odin mode, retry the above, and it works without error.

Edit: Also, if my bootloader is not unlocked, if I try to boot to recovery I get the following error: "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." Same as on this thread: http://www.droidforums.net/forum/ga...software-not-authorized-verizon-wireless.html
[Verizon Samsung Galaxy S III] Noyankees44:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

I don't know much about Sammy devices yet, but I am completely stock and get the same thing if I try and flash a recovery. I will try unlocking the bootloader first and see if that helps. I can't do any mods right now because of this though. Very frustrating...

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] vudugan:
My apologies if this has been mentioned (search this thread did not find anything). I used the no wipe k3 last week then took the ota afew days ago. I just happened to go to playstore via my pc and wanted to check for app updates. To my surprise it stated "Apps installed on Vodafone Samsung SCH-I535" not sure if its anything to worry about or not. I had already decided to go back to stock with a full wipe due to the possibility of getting a replacement from Verizon for other recent issues.

Can someone who has used the regular stock image listed in OP tell me if this does the same on their playstore using a pc? If I have to send my phone back, I don't want to leave any traces of tampering like flashing and whatnot, Thanks
[Verizon Samsung Galaxy S III] prdog1:
If you took the OTA that would be Verizon that did that since you no longer are on K3. :cool:
[Verizon Samsung Galaxy S III] vudugan:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

Would that be considered normal? I've had this phone since released and pretty sure I started flashing by the end of July. I can't say for sure if it was listed as a Vodafone then but I do know that my ROM of choice only listed the SCH-1535 in which I thought was the norm.

Tap'n on vzGS3 'Beans Buildz'
[Verizon Samsung Galaxy S III] prdog1:
Rom Dev may have Vodaphone in the buildprop somewhere. Same as if you flash wallet and don't change it back shows up as a Nexus. :cool:
[Verizon Samsung Galaxy S III] zmedhaug:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

Your not rooted. Or your boot loader is locked.

---------- Post added at 05:25 PM ---------- Previous post was at 05:22 PM ----------

Your not rooted. When you took the OTA you lost root. root. Then unlock your boot loader again.
[Verizon Samsung Galaxy S III] suprdave2:
Incorrect. I am rooted, and have always been rooted.

I have not taken the OTA.

The issue at play here is others saying your bootloader does not have to be unlocked in order to flash the recovery image. I have found on my own that I *have* to have my bootloader unlocked in order to not only flash, but also boot into recovery.

Others are saying this is not normal - but it seems normal for my phone.
[Verizon Samsung Galaxy S III] open1your1eyes0:
In an effort to prevent people from being stuck off the OTA path, I will shortly be removing the VRBMA2 4.1.2 factory image from OP as it is just an early pre-OTA leak. Just want let everyone know in case any of you still need to download those files for any reason.
[Verizon Samsung Galaxy S III] prdog1:
I just flashed the full wipe K3 Image and it let me OTA fine with no crashes or reboots. :cool:
[Verizon Samsung Galaxy S III] open1your1eyes0:
Please be informed the VRBMA2 factory image has now be removed. As noted in the OP FAQ, if you have just received the OTA for 4.1.2 (build VRBMB1) and would like to root, flash a custom recovery, and/or unlock your bootloader please refer to this thread only for the process: Link
[Verizon Samsung Galaxy S III] ddrum2000:
Re: [GUIDE] Jelly Bean Factory Images ***UPDATED 02/06/13***

Will be the no wipe MB1 be added to this thread?
[Verizon Samsung Galaxy S III] open1your1eyes0:
Unfortunately not, we are having difficultly acquiring the factory image for VRBMB1. Until we have this I have no way of making one.
[Verizon Samsung Galaxy S III] ddrum2000:
Re: [GUIDE] Jelly Bean Factory Images ***UPDATED 02/06/13***

Thanks for the update.
[Verizon Samsung Galaxy S III] brb198:
I have flashed stock and getting stuck on the 4G LTE screen. Coming from CM 10.1, flashed lean kernel and got a soft brick. Any ideas?
[Verizon Samsung Galaxy S III] BoxyBox:
Is there any reason why I shouldn't just flash a root injected stock image with Odin and then just use EZ-Unlock and EZ-Recovery to unlock bootloader and install custom recovery? It seems like this method requires using Odin at least 2 times and will just trip the flash counter with extra effort. I'm not trying to be an asshole; I'm just trying to understand what the difference is...
[Verizon Samsung Galaxy S III] prdog1:
You could if there was a 4.1.2 image available. The one that is out there is an unsupported leak and is bad. It is not the OTA image. If want 4.1.2 revert to k3 and take OTA. There is an update available but it is not the recommended way to go. It is for those to lazy to do the update correctly. :cool:
[Verizon Samsung Galaxy S III] BoxyBox:
I was actually just looking for a 4.1.1 image, so I could make a quick backup of stock K3 and then install the new Synergy build since it's based on K3 anyway.
[Verizon Samsung Galaxy S III] prdog1:
Synergy is based on 4.1.1. At least for the next couple of days and then will be based on 4.1.2. :cool:
[Verizon Samsung Galaxy S III] BoxyBox:
Ah, thanks :)
[Verizon Samsung Galaxy S III] suprdave2:
Just use CleanRom: http://xdaforums.com/showthread.php?t=1832070

It's essentially a stripped stock 4.1.2. - you get to choose what apps you want in it.

"CleanROM is based on the latest Verizon released I535VRBMB1 Jellybean 4.1.2 Base and is De-Odex!"
[Verizon Samsung Galaxy S III] tihsllub:
brickety brick brick

So I flashed the ma2 factory image to my phone and it changed my phone model in info to the galaxy nexus. So I downloaded the lk3 factory image and tried to flash it with mobile Odin. And mobile Odin I guess downloaded the maguro add on so when I clicked check my phone bricked.
[Verizon Samsung Galaxy S III] prdog1:
Use real Odin and flash Real K3. Then take OTA and root and unlock as instructed. Short cuts don't always pay. Usually Maguro comes from flashing Wallet but never tried flashing any update via shortcut. I ran MA2 for awhile and mine always showed as Verizon S3. :cool:
[Verizon Samsung Galaxy S III] tihsllub:
brickety brick brick

Hahahaha. Did you not read that its bricked? Its a paper weight. Gonna send it to that mobiletech joint and get it jtagged back into action.
[Verizon Samsung Galaxy S III] prdog1:
Didn't see where it is actually bricked. Have black screen an nothing. We appreciate you sending us the work down here in Texas. Every little bit helps. Next time use real Odin and will be good to go. ;):cool:
[Verizon Samsung Galaxy S III] marcustaz:
I just picked up a riffbox... yet to unbrick anything yet. :)
[Verizon Samsung Galaxy S III] tihsllub:
brickety brick brick

Yeah I'm no going to use mobile Odin for anything again. I have no purpose to flash via device. I had my doubts when I saw that my GS3 said it was a galaxy nexus I had my doubts that mobile Odin would pick the right addons for flashing. Its cool tho. I got a jig coming. We'll see if its a completely hard brick or it just needs a little coaxing to get into download mode. It still charges a battery so I think its just asleep. I am using my other GS3 until I get my daily driver first.

---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------

Really. That actually makes sense because I don't think I restored my buildprop after modifying it to install wallet.
[Verizon Samsung Galaxy S III] tihsllub:
Re: [GUIDE] Jelly Bean Factory Images ***UPDATED 02/06/13***

I don't mind sending my home state some money. And I realized my mistake I made. I restored my backup with the nexus build prop and forgot that my baseband was for a nexus.
[Verizon Samsung Galaxy S III] tihsllub:
Re: [GUIDE] Jelly Bean Factory Images ***UPDATED 02/06/13***

So I tried to a jig to force it in to download mode. Um no. Definite hard brick. :/ damn I really didn't want to send it in.
[Verizon Samsung Galaxy S III] apophis9283:
What is the point of flashing the stock rom first.
[Verizon Samsung Galaxy S III] prdog1:
None if you are on OTA. If not have to Odin to stock to get the OTA. :cool:
[Verizon Samsung Galaxy S III] apophis9283:
I tried flashing a recovery and it failed. So figuring that out now.
[Verizon Samsung Galaxy S III] prdog1:
I know others have tried just flashing recovery and failed also. Also depends if rom has updater disabled by script or removing the required apks. :cool:
[Verizon Samsung Galaxy S III] apophis9283:
Im coming from the nexus so, I want to make sure I have all my eggs in one basket. This should be fun lol
[Verizon Samsung Galaxy S III] prdog1:
It is much easier than it looks. About 20-30 minutes if have all your files ready ;):cool:
[Verizon Samsung Galaxy S III] apophis9283:
Im reading it and all but cant flash the custom recovery so I can flash the other stuff

edit think I got it
[Verizon Samsung Galaxy S III] tihsllub:
When I had to flash cwmt to my other phone it wouldn't let me on the latest ota from Verizon. So I flashed my original f2 ICS ROM from my dump off my other phone and unlocking the boot loader and flashing recovery was easy.

---------- Post added at 11:54 AM ---------- Previous post was at 11:53 AM ----------

If you want cwmt the easiest way for me was to direct download from the sight and just flash it via ez recovery. Hard to mess that part up.
[Verizon Samsung Galaxy S III] prdog1:
That is because the old root methods don't work on JB. Also can't use EzRecovery till you have root and need recovery to get root. This tutorial works fine. I have done it several times. There would be an easier way but the Odin image for OTA was never leaked. This is the only current option to have latest unlocked and rooted full firmware. :cool:
[Verizon Samsung Galaxy S III] Haro912:
Just wanted to let everyone know I just did this and it hard bricked in odin. This method is not completely safe.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You just might be one of the first people to say this method hard bricked your phone. Which step did you get to when this happened? What is your phone doing now?
[Verizon Samsung Galaxy S III] tihsllub:
You can flash a recovery via Odin. You just have to convert the Image.

---------- Post added at 07:29 PM ---------- Previous post was at 07:26 PM ----------

So no one has ever dumped the OTA of the latest firmware?
[Verizon Samsung Galaxy S III] rusty.gh:
haro912. Seriously? Hundreds of followers find this method easy and full proof.

but hey it didn't work for u so post this crap? Hardbrick? Its near impossible to hardbrick the s3

Maybe you should buy a new Facebook home phone and forget about root.
[Verizon Samsung Galaxy S III] greatdaneduke:
Time and Time and Time again it worked flawlessly for me.
[Verizon Samsung Galaxy S III] Joey22688:
dont think so, might be better to move to clean rom if you want an update
[Verizon Samsung Galaxy S III] tihsllub:
Yea I had to do that with her phone. Her phone won't allow OTA. I had to Odin the updates in the beginning. It says can't connect to server at this time. I just flashed the latest cleanrom on her phone just so she would have the update.

Sent from my.........
[Verizon Samsung Galaxy S III] US Marine:
Any ETA on the 4.1.2 no-wipe? My phone keeps bugging me about the OTA update, and it's getting annoying...lol
[Verizon Samsung Galaxy S III] open1your1eyes0:
No ETA, just take the OTA and follow this procedure afterwords to get everything back: Link here
[Verizon Samsung Galaxy S III] US Marine:
After doing the update, I got a message upon reboot saying the update failed, but everything seems to be updated. Strange...
[Verizon Samsung Galaxy S III] open1your1eyes0:
Completely normal this is because you had custom recovery. Stock recovery couldn't pass on the successful update flag to the OS so it doesn't know if it updated properly or not. It will fail but update anyways.
[Verizon Samsung Galaxy S III] Noyankees44:
Ok so i have been trying to flash recovery. I have tried multible downloades. Nothing works. it will not flash in odin. I am on latest 4.1.2

Odin gives this:

<ID:0/007> Added!!

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Initialzation..

<ID:0/007> Get PIT for mapping..

<ID:0/007> Firmware update start..

<ID:0/007> recovery.img

<ID:0/007> NAND Write Start!!

<ID:0/007> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

Phone says:

SECURE CHECK FAIL : RECOVERY

what can i do to fix this?
[Verizon Samsung Galaxy S III] tihsllub:
OK did you unlock your boot loader?

Sent from my.........

---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------

If so how do you know its unlocked? You should flash the rooted factory image than flash the recovery than run the superuser unlocked boot loader zip.

Sent from my.........
[Verizon Samsung Galaxy S III] Noyankees44:
Can you flash the bootloader unlock from stock recovery or is there a file for odin?

Sorry i am used to htc stuff...
[Verizon Samsung Galaxy S III] tihsllub:
Your best bet is to flash the rooted factory image first. You need root to unlock boot loader and flash a custom recovery.

Sent from my.........
[Verizon Samsung Galaxy S III] open1your1eyes0:
Please note that all 3 steps are required if you are following this guide. You cannot skip step 1 and go to flashing the recovery. If you already did step 1 in the past and then took the OTA, the OTA removes the small mods I made in step 1 to allow you to flash a custom recovery. If you already have a working ROM and just want a custom recovery/root/unlocked bootloader, please follow my other guide instead: Link Here
[Verizon Samsung Galaxy S III] Noyankees44:
Ahh i was under the impression that step one was just for if you were still on ics. I will perform it then try again.
[Verizon Samsung Galaxy S III] _sadpanda:
I went from stock ICS rooted (the old/original method) and CWM to 4.1.2 OTA using the combined guide...

Guide works but the waiting for Odin to show green between flashes is a MUST. Maybe for some that goes without saying but for noobs it should just be a part of the instructions as it would probably save the bunch of hassle /posts.

The other Gotchya I had was I tried to use TWRP first and it was a no go. CWM worked flawlessly. Stick with which ever backup you started with and follow the guide. Thanks OP for yet another great guide.
[Verizon Samsung Galaxy S III] tihsllub:
OP you should create a YouTube video with audio and link it to this forum thread.

Sent from my.........

---------- Post added at 09:19 PM ---------- Previous post was at 08:25 PM ----------

Also if you want cwm touch go to clockwork mod in your browser navigate through ROM manager scroll down to your device long press the touch version save file. Then use ez recovery click custom navigate through the files and click when you see your .IMG then its flash time. Easiest way to get cwmt without buying it.

Sent from my.........
[Verizon Samsung Galaxy S III] gadget069:
Just wanted to make sure I can do this, i need to downgrade from stock unrooted 4.1.2 VRBMB1 to 4.1.1. Can use the file found in the OP Stock VRBLK3 Factory Image with No Data Wipe to do this? New to the i535.

Thanks.
[Verizon Samsung Galaxy S III] prdog1:
Why do you want to downgrade.:confused::cool:
[Verizon Samsung Galaxy S III] gadget069:
I'm going to run this phone on pageplus and for this to work i need to downgrade from 4.1.2 to 4.1.1 for the flashing to work.
[Verizon Samsung Galaxy S III] prdog1:
Well that image is semi-stock. Not sure that it matters but has a different boot chain. Can try it or find the full wipe stock image that is untouched. :cool:
[Verizon Samsung Galaxy S III] gadget069:
Found a stock image, thanks.
[Verizon Samsung Galaxy S III] m-cat:
Just followed everything and my phone it bootlooping at the 4g lte screen. Any thoughts as to how to fix this?
[Verizon Samsung Galaxy S III] Ryno77:
Pull battery, boot into recovery and factory reset.
[Verizon Samsung Galaxy S III] m-cat:
When I press volume up+home and the power all it does is vibrate once, shows the samsung logo for a split second then does nothing.

Edit: Got in to recovery and factory reset, after about 5 minutes on the boot animation it finally booted up. THANKS!!
[Verizon Samsung Galaxy S III] prdog1:
I recommend to start over. if you were on 4.1.2 OTA you are using wrong thread. :cool:
[Verizon Samsung Galaxy S III] Ryno77:
No blue across the top that says something about recovery?
[Verizon Samsung Galaxy S III] tihsllub:
OK I noticed on the OTA that when you boot into recovery its really picky. You hold the the volume+ power and home button. When it vibrates let go of the power button and continue to hold volume + and home. Then let go when you see the blue type at the top of Samsung logo. That's my little trick.

Sent from my.........
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I notice this same behavior too. Idk when it started but this is the only way I can get into recovery from a cold boot.
[Verizon Samsung Galaxy S III] Dudenell:
I've been using this version for a few months and noticed a few days ago that there was an update release (4.1.2), my phone still hasn't downloaded the OTA. I guess my question is how would I obtain the OTA? Can I just download it and dirty flash over 4.1.1 and still retain root / bootloader? Sorry I haven't done this in quite a while and forgot the whole process.
[Verizon Samsung Galaxy S III] prdog1:
Have to Odin 4.1.1 K3 back to stock. Take OTA and then root and unlock using this thread.

http://xdaforums.com/showthread.php?t=2046439

:cool:
[Verizon Samsung Galaxy S III] SempaiMatt:
Flash the stock root 4.1.2 from this thread:

http://xdaforums.com/showthread.php?t=2178482

Grab the 4.1.2 modem and rpm from post #3 as well.
[Verizon Samsung Galaxy S III] jedimyndtryx:
If you flash a custom ROM on a Verizon S3 do you lose the SIM unlock? Im currently using a rooted VZW S3 with stock 4.1.1 on AT&T. Thanks.
[Verizon Samsung Galaxy S III] tihsllub:
You shouldn't. Its a system unlock that allows u to use a different sim card. Just make a backup and then try it. Although if you Odin or Kies it will erase it.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Heads up guys I have one more factory image that I should be posting in a few days (and likely going to be my last as well). It's the one we've been missing this whole time on the latest OTA we are currently on version I535VRBMB1.
[Verizon Samsung Galaxy S III] prdog1:
Kewl. Make it a bit easier on the noobs and maybe they will finally update. :p:laugh::cool:
[Verizon Samsung Galaxy S III] speedingcheetah:
Which way is best?

I am soon to get a replacement S3 which i assume will come stock 4.1.2.

I was reading this thread (LINK)and it does something different, flash boot chains and stuff...

I am confused as to which will work...without tripping the warning message thing at boot...
[Verizon Samsung Galaxy S III] prdog1:
That is right one. :cool:

http://xdaforums.com/showthread.php?t=2046439
[Verizon Samsung Galaxy S III] quadracer06:
SWEEEET!! I have been waiting for this one! I love using these on my wife's phone because she likes the stock, but needs the root. We use our Verizon Unlimited Data plan/ TrevE's WifiTether as our sole source of home internet :) usually burn through about 30 gigs each/ month!

Thank you thank you thank you!!
[Verizon Samsung Galaxy S III] GRBlitz:
Why your last?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Open, according to this thread Samsung-Updates has the VRBMB1 file posted. Just a heads up.
[Verizon Samsung Galaxy S III] prdog1:
Kewl downloading now incase I bork my ****. :laugh::cool:
[Verizon Samsung Galaxy S III] Ryno77:
Quite sure he's on the s4 but I'm not sure if that's the reason?
[Verizon Samsung Galaxy S III] linuxthinker:
I'm pulling that MB1 image now. What do I need to do to convert it to a no-wipe image? Happy to do the changes; just let me know (or point me in the right direction) for what needs to be done. Thanks!
[Verizon Samsung Galaxy S III] prdog1:
If Open isn't gonna continue Mr Robinson has his Route66 method posted for MB1

already. It works just as well. :cool:

http://xdaforums.com/showthread.php?t=1984436#
[Verizon Samsung Galaxy S III] quadracer06:
How about the new VRBMD3?!?
[Verizon Samsung Galaxy S III] pvcdroid:
Looking forward to your work on this MD3 update and hoping I won't have to revert to stock. Please keep us posted.

---------- Post added at 10:51 AM ---------- Previous post was at 10:11 AM ----------

Just after posting this I looked at my phone and the update to MD3 was ready. I lost root though.