yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] open1your1eyes0:
You can but there is no reason to. No-Wipe fixed is just a fixed version for the original No-Wipe image I posted earilier. If you used the Wipe image then no fix is required as it worked correctly from the start.

EDIT: Unless you're intending to flash root/recovery, then yes you will indeed need the No-Wipe fixed image first and follow through with the rest of the steps after.
[Verizon Samsung Galaxy S III] gbruyn:
How do I go from K1 the new newest K3? Do I follow the directions from the start or can I just do it a faster way?
[Verizon Samsung Galaxy S III] kazarp:
I did the first time I downloaded it, but a second download fixed it for me.
[Verizon Samsung Galaxy S III] open1your1eyes0:
There's a lot of traffic on the server at this time as you can imagine quite a few people are grabbing the new file so just try a couple times till it matches.

Just follow all 3 steps in the guide exactly as you see it.
[Verizon Samsung Galaxy S III] skrypj:
Thanks for the reply
[Verizon Samsung Galaxy S III] fanto3k4:
That is what I plan on doing. I will flash NO WIPE over my WIPED then root/recovery... Thanks
[Verizon Samsung Galaxy S III] FAUguy:
Pleased to report that the new K3 Fix version does correct those issues (T-9 trace, black email app, Help).

But one issue not fixed is that the calendar on the phone no longer will sync and populate with my Facebook calendar events.

I just went to FB (using PC) and created a test event. It synced to the Note 2, but not the GS3 using the new K3 Fix ROM.

Anyone else want to test this out?

On a side note, I actually liked the black email app over the white one. Looked more professional in my opinion and easier on the eyes.
[Verizon Samsung Galaxy S III] shafty023:
FYI, I was having a crash which resulted in a google apps core process FC'ing. I traced it down to the Internet app not being able to sync my Gmail bookmarks.

Log below

E/BookmarksSync( 7717): The client is trying to modify a root folder. Ignoring, but this should not happen.
W/dalvikvm( 7717): threadid=14: thread exiting with uncaught exception (group=0x4182c438)
E/AndroidRuntime( 7717): FATAL EXCEPTION: SyncAdapterThread-1
E/AndroidRuntime( 7717): java.lang.NullPointerException: The parent id must not be null.
E/AndroidRuntime( 7717):	at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204)
E/AndroidRuntime( 7717):	at com.google.chrome.bookmarks.sync.api.data.SyncableItem$Builder.setParentId(SyncableItem.java:46)
E/AndroidRuntime( 7717):	at com.google.android.syncadapters.bookmarks.BookmarksSyncAdapter$CommitHandler$CursorParser.parse(BookmarksSyncAdapter.java:1092)
E/AndroidRuntime( 7717):	at com.google.android.syncadapters.bookmarks.BookmarksSyncAdapter$CommitHandler$CursorParser.parseAndValidate(BookmarksSyncAdapter.java:989)
E/AndroidRuntime( 7717):	at com.google.android.syncadapters.bookmarks.BookmarksSyncAdapter$CommitHandler$CursorParser.parseNextNItems(BookmarksSyncAdapter.java:1256)
E/AndroidRuntime( 7717):	at com.google.android.syncadapters.bookmarks.BookmarksSyncAdapter$CommitHandler.handle(BookmarksSyncAdapter.java:909)
E/AndroidRuntime( 7717):	at com.google.android.syncadapters.bookmarks.BookmarksSyncAdapter.innerPerformSync(BookmarksSyncAdapter.java:634)
E/AndroidRuntime( 7717):	at com.google.android.syncadapters.bookmarks.BookmarksSyncAdapter.onPerformLoggedSync(BookmarksSyncAdapter.java:246)
E/AndroidRuntime( 7717):	at com.google.android.common.LoggingThreadedSyncAdapter.onPerformSync(LoggingThreadedSyncAdapter.java:33)
E/AndroidRuntime( 7717):	at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:254)

This started after applying the latest no-wipe fix. I fixed the issue by simply clearing data on the Internet app which cleared the database and allowed the sync to proceed as normal. Just passing along the info in case anyone else runs into this.
[Verizon Samsung Galaxy S III] 1000cleverlines:
So I did this fix, and it keeps showing the hint to swipe across the screen to open the message. Any way to fix it?
[Verizon Samsung Galaxy S III] duglas:
I was on K2 with ROOT and SU all working fine, I just downloaded K3 NO WIPE and installed it.. K3 is working fine but I lost Root and SU, so I booted back to CWM and ran the same file as before (SU-bootloader) and it says signature verification failed.. I redownloaded it just in case and ran it again but same thing..

I read every post since the release of K3 on here and say only 1 person who had the same issue but I did not see a reply or fix..
[Verizon Samsung Galaxy S III] open1your1eyes0:
There's no way to fix it as Jelly Bean is not intended to have the lockscreen missed notifications. The only thing you can do is what we did before by the disabling the "Help" app entirely in your Application manager.

Please download #3 and #4 and try to flash them separately and let me know. If it's a case with the file I'll reupload it but it was working last time I tried.
[Verizon Samsung Galaxy S III] huterfi:
Absolutely awesome. I tried the fix and guess what it worked. Quit complaining and enjoy. You don't have to worry about losing all of your data! :highfive: to open1your1eyes0
[Verizon Samsung Galaxy S III] 1000cleverlines:
Darn, that sucks. I loved that feature. I just ended up restoring that original file for now, maybe someone will find a fix for it...
[Verizon Samsung Galaxy S III] zfly9:
Do I need to go past step 1?

Thanks so much for the tutorial. It worked very well.

My question is, do I need to go past step 1? I tried to search the thread for it and I saw it was asked but not answered. Sorry if I missed it.

Thanks!
[Verizon Samsung Galaxy S III] droideris1:
any reason to flash this one over the last K3 no-wipe version if I dont see any weird bugs?

Only thing I notice is that the stock email screen is black, which i dont use. I also prefer it black over white anyway
[Verizon Samsung Galaxy S III] open1your1eyes0:
Step 2 and step 3 only required if you wish to root your device and have CWM or TWRP recovery.

If you don't mind the helper text lockscreen bug, and the swype on the official Samsung keyboard not working (if you even use it) you should be fine.
[Verizon Samsung Galaxy S III] droideris1:
i use swiftkey (which is incredible) so i dont even know if the samsung keyboard is messed up, and it doesnt affect me if it does.

The help app is disabled/frozen on my phone, so I dont see that bug either. Guess I'm all set!

Now I just have to wait for leak #5 :good:
[Verizon Samsung Galaxy S III] Snazarian:
Well what if we want root on the STOCK recovery....thats kinda what the word stock means. If the OP calls this "Stock Jelly Bean Factory Images with Root, Custom Recovery, Unlocked Bootloader and No Data Wipe", it sounds like the Factory Images have had root injected. Not looking to start a fight but if I have to swap out the recovery for a custom one, then its not really stock anymore, is it?

Is there a STOCK VRBLK3 image with root,,,,,,,,or can we use the 1click rooting tool that was released a couple months ago on this image??

Thanks
[Verizon Samsung Galaxy S III] open1your1eyes0:
Unfortunately with Jelly Bean the previous root tool method has been patched and no longer works through the OS. Hence the only workaround is flashing root through recovery, but since stock recovery is not capable of such an option a custom recovery like CWM or TWRP is required. There are prerooted images out there that leave stock recovery but in my personal experience it's always a good idea to root it yourself since you know where it's coming from. Feel free to explore other options in this section but I personally recommend it as a good idea to have a custom recovery for backup/flashing purposes in case you ever choose to in the future.
[Verizon Samsung Galaxy S III] Snazarian:
I appreciate the guidance, but I would if i could. Its a company phone and i would like it to be as close to stock as possible. Im in the IT team and if i have to give up my phone to a user in a moments notice i would like to be able to just 'wipe' and hand it over to a user. dont want to sit there and be flashing things while a supervisor is over my shoulder.
[Verizon Samsung Galaxy S III] awalkerz:
I may be wrong but I don't think a wipe removes root. Anyone confirm?
[Verizon Samsung Galaxy S III] open1your1eyes0:
In that case your interest is probably not to root as well since it will still be left there if you reset the phone.

A regular factory reset/wipe from the device will not remove it, you are correct. However, flashing the factory images does remove it since you are overwriting the system partition to stock (where root is kept).
[Verizon Samsung Galaxy S III] BigErnM:
Disabling the help app is pretty easy in application manager and makes the lockscreen notification bubbles work like they used to. Unless you use the help app a lot, there isn't much downside to doing it that way.
[Verizon Samsung Galaxy S III] dunderball:
Just flashed this and all seems more or less the same since J1. The only exception I see is that the lock screen has a tiny little lock on it which seems a little silly. Everything else is about the same.
[Verizon Samsung Galaxy S III] dunderball:
Now on K3, when I get a text message, I no longer get the text message 'circle' on the lock screen. I used to be able to hold and swipe this circle and it would go directly to the text message.

Any idea if this is new in K3? I did not see this in K1 at all.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Have gotten this asked several times already so I added it to OP FAQ. Short story, it was a bug in all my previous No-Wipe images which I fixed (among many others) with the new K3 image (the original K3 had the same bug).
[Verizon Samsung Galaxy S III] cnlson:
sad tiding to report, not that it matters to me but the samsung keyboard, while showing the swipe feature checked and un-uncheckable in the settings does not swype on the newest version. But i never use it so no harm to me

of the rest

Lock Screen help text not going away even after swiping the action multiple times - use face/pattern so no idea

T9 Trace feature (basically Swype) on the Samsung keyboard does not work at all - not working for me

E-Mail app is always black background even with power savings off - never use it, gmail all the way

Media and/or Android System is at high usage and lowers battery life - no problem on any of your roms, but on this one initially i thought i was having the problem but it was only happening for the first 6 minutes after the reboot when it was syncing everything. after that, no problem
[Verizon Samsung Galaxy S III] open1your1eyes0:
I recommend to redownload K3 No-Wipe Fixed and try it again as almost all users so far mentioned they were resolved with the fixed image. Also, although you don't use the other features just briefly enable them to test if it's just that one bug or they are all still there.
[Verizon Samsung Galaxy S III] dunderball:
Thank you, now my lock screen is completely back to normal. Btw, I had Help frozen before I flashed and it seems to not have any negative effects.

No clue as to why Verizon/Samsung would get rid of the notification bubbles. It's a little ridiculous and I sort of prefer not to use a 3rd party messaging app.
[Verizon Samsung Galaxy S III] xluryan:
Has anyone managed to get rid of the ongoing WiFi notification? I know before on stock roms it was a sql setting called "wifi_offloading" or something like that. But I can't seem to find it in this rom. Any ideas?
[Verizon Samsung Galaxy S III] AuthPineApple:
Kinda Crap Mods will take care of this.
[Verizon Samsung Galaxy S III] Ryno77:
Is anyone else seeing this? I googled this problem and others have it but I have not seen it in the s3 forum.... Wondering if I should do a factory reset?
[Verizon Samsung Galaxy S III] countryfolk07:
Its got something to do with latitude in Google maps. Following location in the background. I turn it off, and have never had any issues.
[Verizon Samsung Galaxy S III] Ryno77:
Yeah, unchecking location history also fixes it. I don't understand why Google wants to know my location 1000 times in one hour. In my opinion they need an update to fix this.
[Verizon Samsung Galaxy S III] chisledice:
Loaded this up and got stuck with constant radiating 4G LTE boot screen... jumped into CWR and did a factory reset and all was good. Weird coming back to this from being on CM10 for the last few months since a few nightlies and then the monthlies.

Thanks again for the awesome write up and files!:good:
[Verizon Samsung Galaxy S III] SteveGrandRapids:
Wow . . . I was dl number 628 this morning on the FIXED No Wipe . . . . :good:

EDIT: After installing the FIXED No Wipe, I continually get the help notifications, even though they are marked "do not show again", and the notifications in the Help app is not turned on . . . not only the opening screen help window, but notifications help window, app help window, etc . . . keep repeating even after dismissing them with the Do Not Show Again checkmarked . . .:(

. . . went to DISABLED mode for Help apk . . . .
[Verizon Samsung Galaxy S III] tailsthecat3:
I use this. http://db.tt/KUFzszGI

Has worked for me on every leak.
[Verizon Samsung Galaxy S III] DarthCivicus:
I have tried to install this ROM twice and both times it says it is not valid verizon software. Is there a step that I am missing? I have stock rom prior and currently with recovery and unlock from EZ Recovery and unlocker.

Is there anything else I should be doing?
[Verizon Samsung Galaxy S III] RedBullet:
Is this the build we re rumored to be getting on Friday?
[Verizon Samsung Galaxy S III] xluryan:
After flashing I installed ADW Launcher Ex. Now every time the phone boots it asks which launcher I want as the default, even though I select 'Always' use ADW.

Any ideas? Seems as though it's not got permission to write the default apps??
[Verizon Samsung Galaxy S III] open1your1eyes0:
Please be informed the VRBLK3 has just been approved by Verizon as the official Jelly Bean OTA build.

Details + Support Documentation - ETA 12/14/2012 (This Friday)

Spread the word and tell your friends to get theirs early here. ;)

News
[Verizon Samsung Galaxy S III] FAUguy:
That's good news, I'll post it over on PhoneArena.

Just a question...if a person currently running ICS HE does the OTA to the JB K3 rom, could they still do Steps 2 & 3 to root and unlock bootloader with recovery?
[Verizon Samsung Galaxy S III] Gareee:
Sweet! Thanks for passing that news on!
[Verizon Samsung Galaxy S III] fredb:
I had already installed VRBLK1 with custom recovery and SU. Can I do the official OTA on Friday over what I have now and get back to 100% stock this way?

I do not need to keep the custom recovery but will want to reactivate SU later.
[Verizon Samsung Galaxy S III] FAUguy:
If the past is any indication, the OTA update will require you to be on version HE, as it checks to make sure you are on the last "approved" version before downloading and installing the update.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Unfortunately not, my K3 No-Wipe in Step 1 has a small mod that allows you to flash a custom recovery. You won't be able to on the official OTA or the official Wipe image (which is why I mention not to use it in this guide). But very simple, all you have to do if follow all three steps and you will be all set. :good:

Unfortunately the OTA won't be pushed to your device if you have any build newer than the last OTA for ICS version VRALHE since the newer leaks were never intended for release. My recommendation is to just refollow my guide with the new VRBLK3 image this time and you will be the same as OTA but able to gain root and custom recovery.
[Verizon Samsung Galaxy S III] FAUguy:
Ok, but what if a person did the K3 OTA, then your K3 No-Wipe. I guess that would work then to allow CWM, root and unlocking bootloader ?
[Verizon Samsung Galaxy S III] open1your1eyes0:
Certainly can do that and it will work fine but it's a little redundant for two reasons:

The OTA build is 100% identical to the factory image

Flashing the No-Wipe would clear out any build you had before so it doesn't even matter what build you are coming from

Just FYI, to save time for you guys.
[Verizon Samsung Galaxy S III] FAUguy:
I agree, but just wanted to verify.

But at least if a person did do the K3 OTA, they could still follow your guide (starting with the K3 no-wipe) and gain root.

I posted about it here:

http://www.phonearena.com/news/Jelly-Bean-update-coming-to-Verizons-Samsung-Galaxy-S-III_id37600
[Verizon Samsung Galaxy S III] open1your1eyes0:
Thank you sir! Phonearena is actually one of my favorite Android news sites. :)

Absolutely, the great thing about Samsung devices is you can go back and forth between all builds old and new thanks to ODIN. So yes, just follow all three steps and they will get root, custom recovery, and unlock their bootloader. :good:
[Verizon Samsung Galaxy S III] open1your1eyes0:
Added two more questions to FAQ in OP
[Verizon Samsung Galaxy S III] Ryno77:
So, what about any updates after this will they install if your on the modified leak?
[Verizon Samsung Galaxy S III] Gareee:
I see there are two recovery options.. twrp or clockwork.. I've used clockwork on my old droidx.. any benefits or advantages to using twrp instead?

Considering taking the plunge now that the ota has been confirmed.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Definitely should as long as you install a custom recovery since the custom recovery image I have posted restores the original VRBLK3 bootchain back as well.
[Verizon Samsung Galaxy S III] US Marine:
Hmmm..wonder what this means.
[Verizon Samsung Galaxy S III] droidian1441:
Can we use the same method to get custom recovery and unlocking bootloader and root if we accept the OTA? Im on VRBLK3 but i am curious. :P
[Verizon Samsung Galaxy S III] Gareee:
I'm guessing they didn't want to let the cat out of the bag until they made a grand official announcement.
[Verizon Samsung Galaxy S III] open1your1eyes0:
Refer to last FAQ I just added. :)
[Verizon Samsung Galaxy S III] droidian1441:
Well damn. That sucks. Luckily we have the imges you built. Thanks! :D
[Verizon Samsung Galaxy S III] Gareee:
I see post 8 links to a .tar.md5 file instead of a tar.tar file.

I'm guessing this is to force people to actually use md5 to check it?

My downloads passed, so I just rename download 8 to the tar.tar extension, instead of the .tar.md5?

After googling some, it seems some people prefer twrp, some still prefer clockwork. It sounds like twrp does not suport aroma, or was tat an older version I was reading about?
[Verizon Samsung Galaxy S III] open1your1eyes0:
tar.md5 is actually an extension that ODIN uses to check if a file is corrupt or not. If you rename it to just .tar (.tar.tar doesn't matter because it only uses one .tar) it will flash in ODIN and ODIN will not check if a file is corrupt. Whenever you use just .tar files without checking MD5 manually, you can run the risk of flashing a corrupt file, in effect possibly bricking your device unless you manually check that the MD5 matches. A lot of people don't know about MD5's so I use .tar.md5 files for ODIN to check for them and not allow flashing if the MD5 doesn't match. Hope that clarifies a bit. It's more of a safety feature.
[Verizon Samsung Galaxy S III] Gareee:
Good to know! I'll change it back to the original file name then. We didn;t have odin around back when I was rooting and working on our droidx phones... looks like the tools available are much better now!

Though I'm familiar with clockwork, it sounds like twrp is preferred now. Do you know it it is aroma compatible, or do you have to stick with clockwork for that?
[Verizon Samsung Galaxy S III] nraines:
Flashing factory image in Odin taking a very long time

I'm on Step 1 and currently flashing the Stock VRBLK3 Factory Image. I'm new to Odin, so I'm not sure if I'm just being impatient or flashing a factory image normally takes a long time. I haven't gotten any errors, but I started flashing over 20 minutes ago and it's still on the "NON-HLOS.bin" step. Any advice? Thanks
[Verizon Samsung Galaxy S III] PeteyNice:
How to remove/disable VZ Navigator?

I searched through this thread and did not see it mentioned. I can disable other Verizon apps using the usual method but VZ Navigator does not give me the option to disable. I can only "force stop" and "uninstall updates". Is there another trick to it?
[Verizon Samsung Galaxy S III] countryfolk07:
Has anyone done both versions? If so anyone notice if the capacitive buttons react differently between versions. I'm asking because in flashing ROMs I've noticed the old no wipe versions keep the buttons of if you just touch the screen. All other ROMs the buttons come on any time you touch screen, which is a waste in my opinion. I think it may have something to do with the CSC directory. Just wondering if anyone has noticed. Have not heard this ever brought up.

EDIT: I know the old no wipe doesn't have the CSC folder. I assume the new version does because people talking about the little lock on the lock screen, which is a CSC folder issue.
[Verizon Samsung Galaxy S III] JDBSC1:
K3 is all setup and backed up, thanks for that.

Couple of things

1) I liked the bug where the email was in night mode (Black with white lettering). Any way to get this back?

2) Noticed Super User was back. I decided to go with TWRP this time is it some how tethered to that? Its not really a big deal but I was using Super SU because I read it was better for JB. When I went to delete SU it was only able to be disabled.
[Verizon Samsung Galaxy S III] mjdavis871:
I have heard that this is a known issue with adw...I was having the same issue on a different rom

Sent from my Eclipsed Galaxy SIII
[Verizon Samsung Galaxy S III] tailsthecat3:
So does anyone think we'll see the sms quick reply option?? Doesnt work with TW mms on vrblk3, right??(didnt for me anyway) A friend on sprint with 4.1.1 says he has the quick reply option. waiting for a screenie.

Edit: but he must've been confused cause it isnt working.

the quick reply is just about the only JB option I wanted... #SadFace
[Verizon Samsung Galaxy S III] prdog1:
@Open. Something bad in TWRP bootchain. Tried several times to load TWRP. Odin multiple times and Odin TWRP chain several times and would not boot to TWRP. Odined CWM boot chain and it booted to recovery. Then Odin TWRP again and it stuck. Beats the hell out of me Homie. :cool:
[Verizon Samsung Galaxy S III] open1your1eyes0:
Just redownloaded and flashed on my device. Both work fine and boot immediately into the recovery via the usual key combo. You may want to redownload the file and flash again. Verify the MD5 as well.
[Verizon Samsung Galaxy S III] cnlson:
google now is more intense on this. but honestly i see much better battery life on this than ICS.
[Verizon Samsung Galaxy S III] tailsthecat3:
I have noticed and the lights stay off when touching the screen. I disable the lights altogether though so it's not much of a bother. What's the deal with the new no wipe version? Think it should be flashed over the first vrblk3 that we flashed?
[Verizon Samsung Galaxy S III] rusty.gh:
Ti backup

That option is not available in all apps. Verizon especially loves there navigator

To kill it you need to follow directions 1,2, & 3 then install titanium backup and freeze navigator
[Verizon Samsung Galaxy S III] FAUguy:
The K3 Fix No-Wipe is still K3, but has integrated some fixes that were unintentionally left out when the first K3 no-wipe was posted.

All I did was install the new K3 over the original one, then did step 2 and 3 for CWM, root, bootloader.
[Verizon Samsung Galaxy S III] prdog1:
I was going by Odin MD5 verification. Never changed download. Odin K3/Odin CWM good. Odin K3/ Odin TWRP bad. Odin K3/Odin CWM/Odin TWRP good. Just sayin. Was up to 6 on flash counter testing it. All tested per standard key combo on stock K3. All combinations require Triangle Away which works as advertised. :cool: