yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] prdog1:
This WiFi tether app works. If doesn't connect check reload drivers in settings. All other settings should work out the box. :cool:

http://xdaforums.com/showthread.php?t=1988735
[Verizon Samsung Galaxy S III] Kellic:
Anyone?
[Verizon Samsung Galaxy S III] open1your1eyes0:
The factory image does exactly as intended and returns your device software to factory condition (of course with the exception in this case of wiping your data). In other words, you will have to unlock the bootloader once again after flashing the image.
[Verizon Samsung Galaxy S III] guruffl:
I saw this information in the original post. "•After reboot your ROM will now be fully rooted and your Bootloader fully unlocked to allowing additional flashing of custom kernels/recoveries"

Does this entire process leave you with a full unlocked bootloader so you can flash roms like a crack flasher?

Thank you
[Verizon Samsung Galaxy S III] prdog1:
Yup. :cool:
[Verizon Samsung Galaxy S III] rayman121985:
What if I DO NOT have an SD card. I only have stock 16gb internal memory. Can I still root ect? Unlock bootloader? Thanks!
[Verizon Samsung Galaxy S III] Ryno77:
Yes. Save files to internal memory.
[Verizon Samsung Galaxy S III] Song0330:
Hmm...can some explain what just happened?

1. I went from a stock ICS VRBLI5 last year to custom ROM Touchwiz Jellybean (JellyWiz) 4.1.1 I535VRBLJ1

2. I followed the instructions under VRBLJ1 in the OP, intending go back to stock ICS and then manually trip the VZW software update to jellybean and VRBLK3.

3. Instead, after ODIN, I'm left with JB 4.1.1 and VRBLJ1
[Verizon Samsung Galaxy S III] SteveGrandRapids:
. . . try this thread to return to totally stock image to trip VZW update:

Return to Stock
[Verizon Samsung Galaxy S III] VinBertinelli:
ok im in a pickle here, i was running cm10 and my system was wiped and i cant get into recovery or android. my only option is to use odin. if i use this odin file, will i go back to stock without wiping my INTERNAL MEMORY (where the phone stores pictures, music, etc)??
[Verizon Samsung Galaxy S III] dscblu:
Re: [GUIDE] Jelly Bean Factory Image (Root/Recovery/Unlocked Bootloader) *UPDATED 12/

Read the op, the stock Odin file doesn't wipe your internal sd
[Verizon Samsung Galaxy S III] Zoandroid:
Hi,

I've been running your rooted stock ICS ROM on my S3 since you released it, with no problems. So I am looking at trying this ROM. But reading this thread from page one I keep seeing term I don't know - "HE" - as mentioned in "HE backup", "HE radio", etc. What does "HE" stand for? I'd like to read the whole thread before I jump on this.
[Verizon Samsung Galaxy S III] Ryno77:
Re: [GUIDE] Jelly Bean Factory Image (Root/Recovery/Unlocked Bootloader) *UPDATED 12/

HE is the last ota update before jelly bean. HE are the last two letters of the build.
[Verizon Samsung Galaxy S III] Zoandroid:
Oh, OK. Thanks!
[Verizon Samsung Galaxy S III] vetteguy112233:
I used this guide to update my phone when VRBLK1 was the most current. Can someone tell me the differences from VRBLK1 and VRBLK3?

I assume it's little bug fixes, but I've searched and can't find the answer (sorry if I've overlooked it).

My biggest issue with VRBLK1 is, no auto spacing between words when using the stock internet browser.

I've install Opera and the problem goes away, but for some odd reason I like the stock browser, has this been fixed and what other changes were made?
[Verizon Samsung Galaxy S III] Zoandroid:
The thing that led me to try Opera when I got my first Android device a few years back was this very issue (and it wasn't rooted, at first) coupled with serious lag when trying to type on a forum. I mean lagging several words behind what I was typing. Too frustrating to use. Opera was the only browser of several I tried that did not lag when typing. (Not that Opera is without its own quirks).

So I, too, would like to know if this issue is addressed in this ROM. I'm still reading the (whole) thread before flashing it.
[Verizon Samsung Galaxy S III] eatmybiglazer:
I feel stupid, I have followed steps 1 and 2, I am able to boot up into my Jellybean powered S3, but when I try to boot into recovery it shuts off. I see the logo with the "Custom" text under the unlocked symbol with the blue "Booting into recovery" text in the corner, but the phone just reboots shortly after entering that screen.

How shall I proceed?

EDIT: To clarify further, I have tried with both the LI and LJ images, ensuring I used the correct versions of all files involved.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Make sure you are entering recovery the right way, you have to let go of the power button at the right time or you will keep looping. See my quote below.
[Verizon Samsung Galaxy S III] eatmybiglazer:
Wow, that is some voodoo trickery. I must have just gotten lucky before because I was already rooted on the ICS image and recovery booting seemed easier. Thanks a lot for the support, I will go and play with my phone in the corner now.
[Verizon Samsung Galaxy S III] open1your1eyes0:
No trickery here, this is the original intended way from the manufacturer. If you are rooted in JB you can reboot into recovery from the OS as well just like you did in ICS. But that's the whole problem here is you are not rooted once you complete step one. Therefore to get into recovery mode at least until you can complete this guide and regain root, you have to do it the original way of booting the device up with the specific key combos. I hope this clarifies some things.
[Verizon Samsung Galaxy S III] xClementex:
For some reason, I keep getting the same problem. When opening the .tar.md5 in ODIN, I get "MD5 Hash is invalid" and it won't flash. I've tried redownloading the file multiple times and even tried the older version, and i'm still getting the same result. How can I fix this?
[Verizon Samsung Galaxy S III] open1your1eyes0:
Which file are you referring to and what link #? Anyone have the same issue?
[Verizon Samsung Galaxy S III] xClementex:
I've tried both VRBLJ1 and VRBLI5. Link #8
[Verizon Samsung Galaxy S III] josh995:
OK sorry if this has been asked...

I'm stock. I'm over rooting/flashing all that stuff. I don't plan on doing it anymore so I don't really care if my bootloader is not unlockable.

So can I just Odin the untouched version and have my GS3 be stock touchwiz jellybean?

Also, if I do that, and this isn't final, will I be able to OTA in the future? Thanks
[Verizon Samsung Galaxy S III] open1your1eyes0:
I just redownloaded VRBLJ1 Download #8 from Link 1 and I do not get the MD5 error.

Please download and run this MD5 checker: Link Here

Make sure the MD5 is C0AEA189C9F870BBEDC26D99810DCEA4.

Certainly for this purpose you can use it but please note that this image will also wipe your device entirely including the contents of internal storage (/sdcard partition).

If this isn't final you might not be able to OTA from this build but not to worry, when the factory image comes out for the OTA version I will be sure to update my thread with all the same then and you can just flash the OTA image then.
[Verizon Samsung Galaxy S III] Ryno77:
If you can't ota the stock Image will be posted so you can use Odin to push the update. Any updates after the final would ota like normal. I'm with you on the flashing and rooting.... This phone is fantastic stock. I am currently downloading the rooted image of this leak and seriously considering flashing as well... So I'm kind of in the same position you are. What you do here can be undone so it basically comes down to how bad you want jelly bean now. Someone correct me if I'm wrong but this is my understanding of this.
[Verizon Samsung Galaxy S III] cnlson:
Anyone got allshare cast to work?

Mine can see the dongle but it fails to connect.
[Verizon Samsung Galaxy S III] josh995:
Thanks. I just want make sure that if I Odin this, I won't be stuck on it forever...lol
[Verizon Samsung Galaxy S III] open1your1eyes0:
Had same issue. Run this app to reset your flash counter and works as new. [2012.11.08][ROOT] TriangleAway v2.36

Not sure why they required a counter check for Allshare Cast but that fixes it for sure.

Worst case scenario you can always flash the original VRALF2 ICS image and then just OTA one by one until you get to the last one (15-20 minutes tops).
[Verizon Samsung Galaxy S III] josh995:
Can we go backwards from this?

If so, I didn't even think about that. Thanks
[Verizon Samsung Galaxy S III] bennero:
Has anyone had the issue of the help text on the lock screen not going away?

Every time I get a message I have the stupid screen showing me how to unlock. I have reset every help option and the option in the lock screen settings. This is very annoying!
[Verizon Samsung Galaxy S III] open1your1eyes0:
You absolutely can. Don't you just love Samsung devices? (stares at Moto) ;)

There are a total of 3 messages, just click OK and then do the action it states right after and that one message will go away.

Swipe across the screen to unlock it, then lock it again

Swipe from an app icon at the bottom to launch the app, then lock it again

Receive an SMS when locked and screen is off, unlock it and swipe the notification circle with the SMS to open it
[Verizon Samsung Galaxy S III] bennero:
I just did exactly that and it still comes back :(. I turned off every help option too. Any other thoughts?
[Verizon Samsung Galaxy S III] open1your1eyes0:
I remember I had the same issue when I first got the phone back in July. I forgot what I did but I remember it took a few tries and eventually it goes away. Basically it wants you to do the action and once you do the action right after that specific message shouldn't come up anymore. It's tricky but try rebooting your phone, clear cache/dalvik cache in recovery, trying it a couple more times, eventually they go away.
[Verizon Samsung Galaxy S III] Snakehn:
I ran into the same issue, I disabled the help app from the application manager, that took care of the problem.
[Verizon Samsung Galaxy S III] josh995:
I am trying to flash this via Odin but it's saying Operation Failed All threads completed (succeed 0 / failed 1)

Just FYI I'm flashing the untouched one. I am completely stock. Thanks for any and all help

Edit: Huh, I switched USB ports and now it seems to be working fine...weird.
[Verizon Samsung Galaxy S III] Mulox:
So I am running stock VRBLK3 from the VZW OTA update. Quick Question: Step 1 of the guide: "Flashing the Factory Image" seems redundant, if I assume it is the same image that I already have. It sounds like I can skip and go right to step 2, installing a recovery, correct?
[Verizon Samsung Galaxy S III] prdog1:
Your on the wrong tutorial if on OTA. Need this one. :cool:

http://xdaforums.com/showthread.php?t=2046439
[Verizon Samsung Galaxy S III] Joey22688:
can we use super user apk instead of supersu?
[Verizon Samsung Galaxy S III] prdog1:
Use what is provided for root to prevent problems and having to do all over again. You or rom can and will change after the fact. Your trying to hack your device. Why change the hack. :cool:
[Verizon Samsung Galaxy S III] Zoandroid:
I'm loyally reading this entire thread, hoping to choose to flash this ROM at the end, and just read this. But this post would be a deal-breaker for me if it doesn't get fixed. I use an Otterbox Commuter case, which is an enormous pain in the donkey to remove. Battery pulling would be extremely inconvenient for me. I frequently connect to my Win7 PC via MTP for file transfers to and from both the Phone memory and Card memory (because so many apps default to the Phone memory as 'SD Card". I won't bore you ranting with my extreme hatred of losing USB Mass Storage

Did this issue get fixed sometime between this post last December and the current date?
[Verizon Samsung Galaxy S III] dyskinesia:
Re: [GUIDE] Jelly Bean Factory Image (Root/Recovery/Unlocked Bootloader) *UPDATED 12/

I sometimes see this when I connect on my stock rooted device.

In my case it always connects in installer mode. I simply toggle back to MTP (sometimes 2x) and it fixes it w/o battery pull or reboot.
[Verizon Samsung Galaxy S III] Zoandroid:
Thanks for the quick reply. :)

I've had this same issue with both my GS III and Acer A500 tablet, and the thing that helped the most was to make sure to only use the cable that came with the GS III when connecting either of them to my Win7 PC. The phone 'usually' doesn't give me any problems using that cable. The tablet, which ran TegraOwners ICS and now a JB ROM almost ALWAYS gives me grief, and what I have to do to make the tablet connect is:

unplug the cable

unmount the tablet's external SD card from the settings panel

remount the SD card

reconnect the cable

And if THAT still doesn't work, I then have to reboot the Win7 PC, then re-boot the tablet, then connect them with the cable, and it always works. I firmly believe it is a USB issue. I hate USB and wish something better would be developed to replace it. I've never had anything but problems since USB was developed years ago.

I'm up to post 956 in my reading, so decided to download all the files (over PC broadband) in preparation to try this. First try using DownThemAll Firefox plugin on the 1.2GB #6 file failed its MD5 verification. Second try with a straight "Save As" worked and the MD5 is good.
[Verizon Samsung Galaxy S III] Zoandroid:
May I suggest adding one more item to your FAQ on the OP?

Reading this one comes close:

But the real question I have would be worded:

If I have <your build or ROM version here>, if I flash this, root it, an unlock the boot loader, and then decide <insert your reason here> that I want to go back to <your build or ROM version here>, can I simply flash the nandroid I dutifully made of my previous ROM version before I began this project?

In my case, that would be the rooted stock ICS ROM I obtained here on XDA. The reason I ask is because I know sometimes (other Android devices I have read about in the past) a specific ROM can or can't be used/flashed with a specific bootloader, such as an ICS ROM requiring an upgrade from a Honeycomb bootloader to an ICS bootloader, for example. Would this new bootloader from JB interfere with my wanting to go back and flash an older ICS nandroid, and would I still be rooted if I did flash one of the (currently rooted) ICS nandroids again in place of this JB version?
[Verizon Samsung Galaxy S III] prdog1:
Can flash the Nandroid and still be stock rooted. It is not same as flashing the image. Image will relock and unroot. Flashing nand may fix simple problems but will not fix major such as wiping all partitions and may or may not fix data problems. Nandroid is just the rom portion of the image and not same as full OTA. :cool:
[Verizon Samsung Galaxy S III] Zoandroid:
Thanks PRDog1!

I've rooted 4 android devices and run custom ROMs on them, but I am far from fully understanding all the inner workings. :) Luckily we have you good folks to help us stay between the lines. :)

I'll give this a go later this evening.
[Verizon Samsung Galaxy S III] Zoandroid:
Can't enter ODIN mode??

When I try to enter ODIN mode, from full off, hold volume down plus hold Home, then also hold Power, my S III boots to the typical home screen, but there is a gray "SAFE MODE" message lower left on the display. I never saw any "disclaimer" to accept. What am I doing wrong?

Edit - OK, I made it work on the third attempt.
[Verizon Samsung Galaxy S III] prdog1:
Never seen the safe mode but have heard of it and has something to do with menu button. Correct for download mode is power/volume down and then home. :cool:
[Verizon Samsung Galaxy S III] Zoandroid:
That's what worked, on the third try. VOL DOWN + HOME + POWER

I got the JB ROM flashed. Now trying to enter ODIN mode again to do the recovery. Same problem. I hold those 3 buttons, it vibrates once, I see "Samsung" on the screen, it goes black, and I sit there forever holding the buttons until my fingers get tired. When it DID enter ODIN mode, it was very quick, like within 2 seconds. I've tried twice again this time with no luck. Maybe 3rd time's a charm?

YUP!!

So what is happening here? How come I have to do this exactly THREE TIMES to get it to work?

---------- Post added at 10:56 PM ---------- Previous post was at 10:40 PM ----------

Hey, I just averted a possible disaster with ODIN, and it is not mentioned in the Odin guide thread:

Once I had flashed Bootchain with Clockworkmod, the S III rebooted and appeared to be all set. But ODIN was still showing RESET! at the top, and the three buttons at the bottom for Start, Reset, and Exit were still grayed out. I wondered if something was wrong, so I was taking the time to note all this in the log I keep for the phone, recording this process of upgrading to JB. By the time I was done typing, I looked up again and Odin was now showing the green PASS!, its Messages showed All threads complete (succeed 1 / failed 0) and the buttons were again accessible.

So I guess even after the phone reboots from flashing the custom recovery, Odin is not finished yet? Someone might want to mention that at the end of the Odin guide, that you have to wait until these conditions appear before unplugging the USB cable. :)

---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------

Can I still use ROM Mgr to reboot to Clockworkmod Touch Recovery like I was doing in stock rooted ICS, instead of pressing buttons?
[Verizon Samsung Galaxy S III] sjmiller:
Re: [GUIDE] Jelly Bean Factory Image (Root/Recovery/Unlocked Bootloader) *UPDATED 12/

As soon as you see Samsung on the screen, release the buttons.

Scott
[Verizon Samsung Galaxy S III] Zoandroid:
So I can release ALL THREE buttons as soon as it vibrates, to go into ODIN mode?

BTW - to answer my question above, ROM Mgr. still works just fine for rebooting into Clockworkmod Touch Recovery. They should add a "reboot to ODIN mode" button. lol
[Verizon Samsung Galaxy S III] open1your1eyes0:
Please see following thread for details how to enter recovery mode: Link Here
[Verizon Samsung Galaxy S III] Zoandroid:
I have all three stages flashed, so I'm now running JB, with CWM Touch Recovery, and am rooted and unlocked! And all my apps seem to still work. :)) I am creating my first JB nandroid for the S III as I write this. ;)

THANKS!!! to those who worked so hard to give this to us!!

---------- Post added at 11:55 PM ---------- Previous post was at 11:26 PM ----------

Thanks, but I had read this, and it is how I first got into CWM Recovery after flashing this project. However, I am happy to report that ROM Mgr. option to reboot to recovery still works just fine (I don't like playing with the buttons). :)
[Verizon Samsung Galaxy S III] prdog1:
You will see that rom manager will cause you problems later. :laugh::cool:
[Verizon Samsung Galaxy S III] Zoandroid:
I know what you're saying. :) Back when I had my LG Ally I was an avid supporter on the bandwagon dissing ROM Mgr. because it bricked my Ally once and my only salvation was a very kind member of a different forum who met me in private chat and spent an hour walking me through downloading files and using ADB to fix it. Honestly, the only thing I do with ROM Mgr. now is use the boot to recovery button. I don't trust it to handle ROMS or nandroids. ;) And I have to use an older version at that, because the recent update for it broke the boot to recovery function as well, at least for the GS III.

Got me wondering if there is a "boot to recovery" / "boot to Odin" specialized app out there. My large dry fingertips and skinny buttons on the edges of phones don't get along very well. I left out the number of times my fingers slipped off the buttons while trying to hold them pressed last night in my search for what was going wrong. lol.

I see many folks like to use TWRP Recovery. I've never tried it. Does it by chance allow you to name a nandroid while creating it in recovery?
[Verizon Samsung Galaxy S III] prdog1:
TWRP rocks. Can name nandroid at time of backup and latest 2.4.0 has exFat external sd support.

For boot to recovery this app works fine and is much lighter. I use anytime rom doesn't have it baked in. :cool:

https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&feature=search_result
[Verizon Samsung Galaxy S III] Zoandroid:
This sounds worth trying. So to switch to TWRP, do I just use ODIN again to flash the download that included TWRP (#7 listed in the OP) over top of what I have now (using CWM Recovery) or is there more I have to do?

Edit - sorry I missed your reference to QuickBoot before. I'll use that. Thanks!
[Verizon Samsung Galaxy S III] prdog1:
For latest TWRP download GooManager from the market. hit menu button>install recovery script. It will download latest TWRP and auto flash. :cool:
[Verizon Samsung Galaxy S III] Zoandroid:
Easy TWRP Installation :)

I love things that are made easy!! :D I've got TWRP up an running and making its first nandroid. :)

THANKS!
[Verizon Samsung Galaxy S III] open1your1eyes0:
When the time comes, the time comes. And the time is now here. Stay tuned next week and our VZW devices will look mighty fine compared to the other US carriers. ;)
[Verizon Samsung Galaxy S III] Ryno77:
Re: [GUIDE] Jelly Bean Factory Image (Root/Recovery/Unlocked Bootloader) *UPDATED 12/

I like the way this sounds!
[Verizon Samsung Galaxy S III] Snakehn:
did you get a hold on that samsung suite software pack or add-on that they were announcing a few weeks ago for the S3?
[Verizon Samsung Galaxy S III] Joey22688:
Do you need the VRBLK3 bootchain when installing the latest twrp?

or can you just use that app mentioned above?
[Verizon Samsung Galaxy S III] prdog1:
Need to do full hack and unlock then can swap recoveries as much as you want. Once unlocked can flash at will. If flash recovery while still locked will have to start from scratch. :cool:
[Verizon Samsung Galaxy S III] open1your1eyes0:
Please be informed that I have updated the OP with the latest and first leak of 4.1.2 for the Verizon Galaxy S III build VRBMA2. I have also removed most links to builds below first OTA.
[Verizon Samsung Galaxy S III] dyskinesia:
Re: [GUIDE] Jelly Bean Factory Image (4.1.1 and 4.1.2) ***UPDATED 02/04/13***

Major differences between 4.1.1 and 4.1.2?

Happy on 4.1.1 but if 1.2 is stable and offers some goodies I'm in.
[Verizon Samsung Galaxy S III] Mulox:
My biggest concern with new releases is that some apps won't work. For example, I am running 4.1.1 and still can't get any Wi-Fi tether or hotspot app to work...
[Verizon Samsung Galaxy S III] dyskinesia:
Re: [GUIDE] Jelly Bean Factory Image (4.1.1 and 4.1.2) ***UPDATED 02/04/13***

All working for me.

There is an apk that was uploaded that worked for most people on Verizon

Think it was called toggle Wi-Fi hotspot. Easiest fix for me and cleaner than many of the other options.

In fact I just looked and previously I linked to it in this thread.
[Verizon Samsung Galaxy S III] prdog1:
There is also Android wifi tether in mod thread by Trev for those that are rooted. :cool:
[Verizon Samsung Galaxy S III] open1your1eyes0:
Here you go: Link :good:
[Verizon Samsung Galaxy S III] dyskinesia:
Re: [GUIDE] Jelly Bean Factory Image (4.1.1 and 4.1.2) ***UPDATED 02/04/13***

Post 960 for file I linked.
[Verizon Samsung Galaxy S III] prdog1:
We gotta full wipe anywhere. :cool:
[Verizon Samsung Galaxy S III] dyskinesia:
Re: [GUIDE] Jelly Bean Factory Image (4.1.1 and 4.1.2) ***UPDATED 02/04/13***

Or a changelog
[Verizon Samsung Galaxy S III] open1your1eyes0:
Uploading full wipe now may take 1-2 hours but just do a factory reset after flashing No-Wipe for now. Will be the same thing.
[Verizon Samsung Galaxy S III] Gareee:
Thanks for this update! ;)

Are there any known issues with this (Like the gallery or camera issues some have reported elsewhere?)