yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Srambo217:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

I asked this in another thread but I want to clarify this here since I'm using this leak-

Could one flash I535VRBLK3 over VRBMA to revert back to an 'official' release? Would I need to wipe my data or could I leave it intact?

I'm not having issues with VRBMA, just curious.

Galaxy SIII - Thanks Appreciated!

My Podcast*-*http://bit.ly/WWSXbz

My Blog*-*http://bit.ly/SrqMNr
[Verizon Samsung Galaxy S III] joshkoss:
personally, i'd wipe.
[Verizon Samsung Galaxy S III] prdog1:
Technically when flashing firmware should not have to. The Image should and will format all partitions that have not been modded. Although this is modified to not wipe data. I actually flash the full wipe versions before I flash the modified root versions. :cool:
[Verizon Samsung Galaxy S III] dbaps:
What is the purpose of "root only" in Step 3

Step 3 - Rooting Your ROM and Unlocking Your Bootloader

If you would like Root Only (Main Download #3 to your SD Card)

If you would like Unlocked Bootloader Only (Main Download #4 to your SD Card)

If you would like Both Root and Unlocked Bootloader Main (Download #5 to your SD Card) ***RECOMMENDED***

Why is the option, "root only" listed here? I'm a newbie but thought that any custom rom required an unlocked boot loader. So is "root only" listed here in case you are starting with an unlocked boot loader that is not rooted?

If you only root and do not unlock the boot loader, is there functionality lost?

Is "root only" just for having root with the stock image?

Thanks everyone.
[Verizon Samsung Galaxy S III] schneid:
Root only allows use of things like Tibackup, apps that give more functionality with root access.
[Verizon Samsung Galaxy S III] prdog1:
Root only is for those that want to remain stock but run some apps that require root. :cool:
[Verizon Samsung Galaxy S III] banditsw:
deleted
[Verizon Samsung Galaxy S III] Ryno77:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

http://androidheadlines.com/2013/03...android-4-1-2-update-to-the-galaxy-s-iii.html
[Verizon Samsung Galaxy S III] open1your1eyes0:
Unfortunately, my source does not yet have access to the file for this build, it seems Verizon is cracking down lately. But not to worry. When the OTA comes you can still get root, custom recovery, and unlocked bootloader through my other method: Link Here. The only thing I will have to do is update Step 5 with the VRBMB1 Bootchain when it arrives. Should not be too hard and that step is optional anyways.
[Verizon Samsung Galaxy S III] krazie1:
4.1.2 the OTA is Rolling Out! http://www.droid-life.com/2013/03/05/verizon-galaxy-s3-update-to-android-4-1-2-already-rolling-out/
[Verizon Samsung Galaxy S III] banditsw:
Software update prompt

I am running the rooted BLK3 build via the method used in this thread. I just got a software update prompt. I am not sure the consequences of accepting, so I deferred the update for a couple of days. I would like to retain root, unlocked bootloader etc. Should I not update? Thanks.

Read the OP's prior post and other thread re: retaining root with OTA, but not sure about the bootchain?
[Verizon Samsung Galaxy S III] prdog1:
Wait at least till the devs deem it safe. Without Multi Window suite your not getting much. :cool:
[Verizon Samsung Galaxy S III] open1your1eyes0:
Don't worry about it. You can go ahead and update and as per my previous post just follow that thread (without Step 5). I will be updating Step 5 in a few days (maybe even tonight) to include the new bootchain but the updated bootchain is optional and can be flashed at anytime so no need to hold back for now.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Also this is not included in the changelog but with 4.1.2 you can now customize per contact Message Ringtones (now in addition just like you could Phone Call Ringtones before).
[Verizon Samsung Galaxy S III] banditsw:
Started the update, but it rebooted into twrp (where I am now)...Please advise. Thanks.

EDIT: Rebooted the phone and now a software update is in progress in the notification bar
[Verizon Samsung Galaxy S III] prdog1:
Can't update with custom recovery. It will download but not install. :cool:
[Verizon Samsung Galaxy S III] banditsw:
Thanks...I see....I was thinking of doing the following:

1. Use ez recovery app to get stock recovery back

2. OTA Update

3. Use open1your1eyes0 instructions in other thread to get back my beloved root, unlocked bootloader, custom recovery

4. Profit
[Verizon Samsung Galaxy S III] open1your1eyes0:
For those of you who just got the VRBMB1 OTA please refer to this guide how to restore root, custom recovery, and/or unlocked bootloader.
[Verizon Samsung Galaxy S III] open1your1eyes0:
For those of you who updated early to VRBMA2 (4.1.2) build

, unfortunately you won't be able to get the OTA as that build was never designed for public release.

The process to update is going to be a little longer and trickier since we don't have a full factory image yet, but here's how you do it:

You will have to download this manual update to VRBMB1 to your internal storage (/sdcard) and a copy to your external SD Card if you have one as well, first!

Then flash back down to VRBLK3 (4.1.1) build using just

Step 1

of the instructions from the OP.

As soon as it's complete you will get a bunch of crashes,

don't worry, this is normal

, and you won't be able to use device until you do the following.

Just pull the battery when you get the crashes/force closes, boot into recovery and flash that manual update you downloaded earlier to your internal storage.

This should update you to the new VRBMB1 OTA and you should have no crashes now.

Afterwords just follow this guide to restore root, custom recovery, and/or unlocked bootloader.
[Verizon Samsung Galaxy S III] krime922:
If we do your above method we can flash the update w/o being on a custom recovery?
[Verizon Samsung Galaxy S III] banditsw:
OP, does coming from

rooted

BLK3 as found in this thread affect the update?

I got a 402 code error when trying to take the OTA from stock rooted BLK3, as found in this thread. I flashed stock recovery as suggested in the previous post. The OTA downloaded, after which a prompt to update came up.

I agreed to update, the phone rebooted into stock recovery, but about midway through, the little green android laying down displayed a triangle on top. The phone proceeded to reboot without updating. When I looked in "System Update" in the settings panel, it said update failed with error code 402.

Thought I would post in this thread because I think others on this ROM may be experiencing the same issue. Thanks.
[Verizon Samsung Galaxy S III] open1your1eyes0:
It was designed for stock recovery actually but I tested on CWM. Should work but let me know if you face any issues.

VRBLK3 is exactly the build that the OTA was made for. It will just unroot you if you're rooted and it will say failed but when you check About Phone you will see it did actually complete the update.
[Verizon Samsung Galaxy S III] banditsw:
Thanks for the reply. However, I am still on BLK3. Would either of the following affect the OTA update- unlocked bootloader, Kinda Craps mods?
[Verizon Samsung Galaxy S III] open1your1eyes0:
Kinda Crap mods will make it fail since it modded your system partition. And OTA can't approve overwriting the mods. You're either going to have to restore the original backup that Kinda Crap mods did (there's an option when you launch it) or if you erased that backup folder already then you're going to have to reflash VRBLK3 like from the OP of this thread over again.
[Verizon Samsung Galaxy S III] banditsw:
Thanks for the reply. So I should just 1) flash the BLK3 image as found in the OP, 2) take the OTA update, and 3) follow the instructions in your other thread, Root OTA Jelly Bean 4.1.2?

Thank you.
[Verizon Samsung Galaxy S III] open1your1eyes0:
If you still have that backup that KindaCrap Mods makes (should be in internal storage folder called "kindacrap") preferred to just restore it since it'll be tons quicker. But otherwise if you don't have it then yes, do that.
[Verizon Samsung Galaxy S III] droideris1:
you said yet... meaning you'll have one soon? I love your no wipe images, they are so freaking easy to flash!

Will we be getting one of those in the near future?
[Verizon Samsung Galaxy S III] open1your1eyes0:
Only time will tell.
[Verizon Samsung Galaxy S III] droideris1:
the suspense might actually kill me
[Verizon Samsung Galaxy S III] jimmyj352:
VRBLK3 to VRBMB1

Hey everyone - I hope I didn't miss this throughout the thread, but if I'm on VRBLK3 (rooted, unlocked bootloader, running ClockworkMod), can I get to VRBMB1 through the OTA or another way? If so, what's the best method to do this?

Thanks for your help!

-- Jim
[Verizon Samsung Galaxy S III] open1your1eyes0:
You should be able to as long as you have no mods installed on your system partition. Just check for Software Updates in About Phone and follow this guide afterwards. Link Here
[Verizon Samsung Galaxy S III] jimmyj352:
Thanks for the quick response - do I need to lock the bootloader or anything first before taking the OTA?

-- Jim
[Verizon Samsung Galaxy S III] open1your1eyes0:
Nope. Not required, the OTA will relock it for you as it flashes.
[Verizon Samsung Galaxy S III] jimmyj352:
Cool - thank you very much for the quick answer and your hard work on this awesome thread!!

-- Jim
[Verizon Samsung Galaxy S III] banditsw:
OP, I flashed the BLK3 image using ODIN. What I found curious was that icons for 3 apps remained in my app drawer-- ez recovery, titanium backup, and XDA.

Is this unusual? My understanding is that by flashing the BLK3 image without wiping data, it wipes everything except for the internal sd card...

I just went ahead and took the OTA, and thereafter rooted, added custom recovery, and unlocked the bootloader according to the OPs other thread, and so now I am on stock rooted BMB1 odexed, but just curious why the 3 apps mentioned above were not wiped.

Thanks.
[Verizon Samsung Galaxy S III] noname4me:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

Without wiping data means that it doesn't wipe non system partitions or user data.
[Verizon Samsung Galaxy S III] banditsw:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

Thanks for the reply. But I also had other apps which were wiped when I used Odin to flash the tar file. Wondering why those were wiped and the three mentioned above were not.

Edit: just remembered I may have done a factory reset and installed those 3 apps before Odin. Sorry. Getting old and forgetful. :-p
[Verizon Samsung Galaxy S III] skbgiants:
Yeah, thought I could take the OTA then re-root ect, but after downloading, it boots into recovery, asked to flash unnamed update.zip which I did, but the file isn't valid.

I'm running 4.1.1 VRBLK3.

Guess I'll wait to see if the non-data wipe 4.1.2 OTA hits here. Thanks OP!
[Verizon Samsung Galaxy S III] Joey22688:
I couldnt even update to 4.1.1 on ota before so not going to even bother

but I do have a question, when the 4.1.2 no wipe rom is put up here

right now I have 4.1.1 rooted, unlocked, and with twrp

would flashing 4.1.2 no wipe get rid of the custom recovery and relock the phone? (I assume everything else would be fine and untouched minus the root)
[Verizon Samsung Galaxy S III] skbgiants:
I don't believe so. You should retain your recovery and the phone should be unlocked.
[Verizon Samsung Galaxy S III] prdog1:
The no wipe wipes everything except user data same as OTA. Will lose root, recovery.and be relocked.:cool:
[Verizon Samsung Galaxy S III] skbgiants:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

Yes. Totally correct yet I can't take the OTA for some reason. I'd like to, so I can save my data settings etc w no wipe and just re-root but the ota isn't working for me.
[Verizon Samsung Galaxy S III] prdog1:
.

If will not update if have custom recovery. There is a stock recovery available some where. I've been doing this for years and have never seen or flashed an OTA.
[Verizon Samsung Galaxy S III] banditsw:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

New camera on bmb1 has the best face feature
[Verizon Samsung Galaxy S III] jackdubl:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

Saw that yesterday. That's the main new feature I wanted to try out.
[Verizon Samsung Galaxy S III] Zoandroid:
On other devices in the past I learned there were files I could freeze or remove to prevent Verizon's OTA announcement from popping up. Could you tell me how to do that on the S3 using this ROM? (I'm still on 4.1.1 VRBLK3)
[Verizon Samsung Galaxy S III] skbgiants:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

Thank you! I will either flash the stock recovery or most likely wait for the no data wipe. Honestly I should just wipe and do things the right way. With titanium back up its really not that difficult.
[Verizon Samsung Galaxy S III] prdog1:
SDM and FWUpdate apks. :cool:
[Verizon Samsung Galaxy S III] Zoandroid:
Perhaps it would be best to rename them? Thanks!
[Verizon Samsung Galaxy S III] prdog1:
Either way works. :cool:
[Verizon Samsung Galaxy S III] Zoandroid:
I wasn't sure where to find them so I did a search in the whole file system and found them in system/app. Renamed both extensions to PKA.

Thanks! :)

---------- Post added at 12:34 PM ---------- Previous post was at 12:30 PM ----------

I suppose I should ask if this update is anything cool? The notice said it takes 8 minutes, so I figure it can't be very large. I never flashed the last posted file here because the thread dialog didn't sound like it had anything that interested me.
[Verizon Samsung Galaxy S III] prdog1:
If you run stock rooted there are a couple things new like best face camera and ability to have separate ringtones on calls and messages. Not sure what else as I only have stock long enough to flash it. I run roms so I usually update the firmware and wait for the devs to build using the new base. With the firmware you get the radios, kernel and supporting firmware. Although these can usually be obtained as separate flashables. :cool:
[Verizon Samsung Galaxy S III] Noyankees44:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

I just too 4.1.2 ota on a completely stock device. I attempted to flash a recovery from Odin. It just fails. Is there common reason for this? I have installed the Samsung drivers and everything following this guide.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] dunderball:
I'm unable to reach internal storage from stock recovery. It appears I had to copy the update.zip to external sd card. I'm flashing back to MA2 just so I can move the file over.
[Verizon Samsung Galaxy S III] Joey22688:
just use titanium backup (or really any app that can freeze installed apks) and freeze sdm v1.0
[Verizon Samsung Galaxy S III] bennero:
You my friend are a saint! That worked perfect!
[Verizon Samsung Galaxy S III] Ryno77:
So, how is it?
[Verizon Samsung Galaxy S III] tailsthecat3:
This worked perfectly the first time around but this time i just can't get the recovery to flash. I keep getting a failed status in odin and the phone tells me it's insecure or something like that. I've downloaded the file twice but i haven't tried the twrp recovery tar. I had to come into work, stupid work getting in the way of life. I also tried different usb ports. As i was driving in i thought i would try the no data version later, since i already went clean with the full blown stock file, then i would try flashing recovery again.

Any input on this? Am i making an obvious error somewhere? Thanks for these, openyoureyes, appreciate your efforts!

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

Sorry, didn't respond til now. Yes that worked a few days ago.
[Verizon Samsung Galaxy S III] josh995:
Working great, so smooth, really loving it.

I don't think this is going to be the final version, it seems a TAD buggy. Like this morning, I had it on the charger until it was fully charged. I took it off the charger and the screen came on like normal, but then I pressed the lock button and the screen would shut off, but would come back onto the lock screen.

I had to swipe to unlock the phone and then put it back to sleep for it to stop. Strange.

Also, my maps usage is unusually high under battery settings. Anyone know what that could be about? I'm running the completely stock non-rooted Jelly Bean
[Verizon Samsung Galaxy S III] skennelly:
For some reason, neither recovery image will install properly. Now I cannot unlock and root.
[Verizon Samsung Galaxy S III] tailsthecat3:
+1

Same. I used the untouched version. After work i may try the no data version then repeat the process.

---------- Post added at 09:45 AM ---------- Previous post was at 09:17 AM ----------

Curious. Did you flash the untouched or no data version?
[Verizon Samsung Galaxy S III] droidstyle:
Why dont you guys listen to the op and flash the no wipe version??
[Verizon Samsung Galaxy S III] tailsthecat3:
Wanted fresh. Why, is it literally impossible to flash the recovery after the untouched version? Been tinkering with android for years, it's fun.

Also, thanks for your invaluable input.
[Verizon Samsung Galaxy S III] droidstyle:
Point is follow directions or dont post... :silly:

Edit*

You can still wipe data from stock recovery and start fresh.
[Verizon Samsung Galaxy S III] tailsthecat3:
Ah yes, classic. Is it lonely up there on your pedestal? Gimme a break, dude.

Again, thanks for your invaluable input.
[Verizon Samsung Galaxy S III] josh995:
Agreed.

Anyone have an idea on why maps usage is so high?
[Verizon Samsung Galaxy S III] droidstyle:
Pedestal? No im not lonely at all...actually quite the opposite. Why are you so offended by constructive criticism?? The op put the factory link up for dev purposes...he spicifically states to use the no wipe version. My advice is to try the no wipe version then wipe data from stock recovery. If your still having issues then report them here. Now were both clogging this thread because of your inability to follow direction. Wasnt trying to be a ****, but if you insist on carrying this conversation out lets keep it via pm's. Sorry open1your1eyes for derailing the thread....normally not my style. :o

---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------

I believe its a issue with the latest maps version ...atleast a few others reported having that issue. Might try rolling back to a previous version and see if it goes away.
[Verizon Samsung Galaxy S III] tailsthecat3:
Thanks dude! :) :D :thumbup: :p
[Verizon Samsung Galaxy S III] FAUguy:
With J1 installed two days ago. Right now I've got 15% battery remaining, and the up time has be 1 day 4hr. But the Maps is showing 19% usage with an awake time of 15 min, even though I haven't used the app at all. Screen shows 17% usage with 2 hours on time.

Still, my biggest complaint is that while using any browser, that the long press to Paste dosnt show most of the time in forums boxes like this, and the arrow curser jumps around when trying to edit.
[Verizon Samsung Galaxy S III] josh995:
Could the higher maps usage than we're used to be because of Google Now? Isn't it checking where you are quite frequently?
[Verizon Samsung Galaxy S III] tailsthecat3:
It does. I don't use Google now and am not seeing an excessive use of maps. Yeah the prefetcher service runs sometimes but if i see that, i force close it.
[Verizon Samsung Galaxy S III] FAUguy:
I've turned off Google Now and will see if that makes a difference once the battery is charged up.
[Verizon Samsung Galaxy S III] tailsthecat3:
Be sure that location reporting is also off. I believe the option is inside of maps.

Unrelated Edit: safe to say that we probably won't see the notification quick reply options for touchwiz.
[Verizon Samsung Galaxy S III] josh995:
That's too bad, I really liked the quick reply when I was using cm10

Another thing I found kinda glitchy is the new Samsung keyboard is kind of laggy. I type fast and what I type takes a while to show up on the screen. Anyone have any ideas on what it could be?
[Verizon Samsung Galaxy S III] tailsthecat3:
I'm just assuming it won't be in a tw fw since it hasn't been implemented as of yet. Of course there are workarounds-if one should be so inclined.
[Verizon Samsung Galaxy S III] skbgiants:
Actually, will there be a no-wipe 4.1.2? I'm on VRBLK3 rooted of course, and I even with a stock recovery I can't take the OTA? I've even downloaded the update.zip and tried to flash that way to no avail.

Any suggestions? I suppose I should just do it correctly and wipe everything and start from scratch.

Thanks!
[Verizon Samsung Galaxy S III] rusty.gh:
what?

Dude read OP. The 4.1.2 no wipe is available now.

Only reason I haven't is because of mods & I'm lazy.
[Verizon Samsung Galaxy S III] skbgiants:
Re: [GUIDE] Jelly Bean Factory Images (4.1.1 and 4.1.2) ***UPDATED 02/06/13***

I meant the official OTA 4.1.2 VRBMB1
[Verizon Samsung Galaxy S III] skbgiants:
THANK YOU!
[Verizon Samsung Galaxy S III] suprdave2:
Still can't get a custom recovery to flash. I've searched for my error and several others have posted the same thing with no answers besides "try the download again".

This is several months later, another download, still same error. I know I've got to be doing something wrong.

The phone is in Odin mode. I open Odin 3.07, click PDA, select "VRBLK3_Bootchain_CWM.tar.md5", and click Start. Odin does its thing then says "FAIL". On the phone it shows "secure check fail".

Someone please let me know what I am doing wrong! :good:
[Verizon Samsung Galaxy S III] prdog1:
Did you flash the full image first. Are you on 4.1.1/4.1.2 OTA. Need more info. :cool:
[Verizon Samsung Galaxy S III] rusty.gh:
is it failing on md5 check

If Odin fails on md5 check you have to re download the file

Try using another browser to download file
[Verizon Samsung Galaxy S III] suprdave2:
I promise it's not the download - the error says nothing about md5 not matching.

This is 4.1.1 stock rooted. Here's what I did with this guide to get 4.1.1:

Step 1 - Flashing the Factory Image

Download and Install USB drivers (Main Download #1)

Download and extract ODIN v3.07 (Main Download #2)

Download the Stock Factory Image with No Data Wipe (Image Download #1)

Boot phone into ODIN mode (See here for how-to)

Flash the flash the factory image using ODIN v3.07 (See here for guide on flashing)

After reboot you should now be on Jelly Bean with all your apps, data, and storage contents in tact

This is where I have stopped. I am now trying to follow Step 2 to get CWM Touch and this is where I am running into the error. Again, this is not a corrupt download issue, at least not on my end. I feel like I am missing an important step in between 1 and 2 before I can put the CWM file into the PDA section and flash it, but nothing is listed in this guide.
[Verizon Samsung Galaxy S III] Gareee:
We followed the original 4.1.1 instructions for unlocked rooted.

I did add the new camera/gallery a week ago as well to my phone.

We are getting the push for 4.1.2 finally as of yesterday. (Man that took them ages!)

To update to 4.1.2, I update from the new zip, flash clockwork again, and then reinstall su?

The instructions on page 1 are great for the initial installation and rooting, but for this incremental update not so clear.

I just want to verify the process of this update before proceeding.
[Verizon Samsung Galaxy S III] sahmbo1:
The wife's s3 was on this flash/root process. She got the OTA update yesterday, updated and when it finished she still had CWM and root still intact.

I on the other hand was on the leak, had to downgrade to LK3, flash the update, flash the LEC boot chain, flash CWM, boot loader, root and restore MB1 boot chain.

It's not bad and you may get lucky like my wife.