Database Users

Stock FRF72 -> FRF83 OTA

I'm not taking credit, but the OTA update from FRE72 to FRF83 can be found here:
forum.xda-developers.com/showpost.php?p=6926438&postcount=116
If someone would root it, that would be greatly appreciated.

Just use Cyanogen's quick rooter.

mortzz said:
Just use Cyanogen's quick rooter.
Click to expand...
Click to collapse
Are you sure it works?

I'll look into that, but to even install the FRF83 update I believe I need to install the stock recovery image beforehand. Since I'm not overly in the mood to do that, I'm happy to wait for a pre-rooted one to pop up.
Thanks for the suggestion, however.

link verified, just waiting for this long boot.
Everything looks good!

SBERG117 said:
Are you sure it works?
Click to expand...
Click to collapse
Quite sure:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As always, do a NANDroid first.

What was your process? Did you have to use stock recovery, or a custom one? is your WiFi working on FRF83? Were you rooted with FRF72 beforehand?

mortzz said:
Quite sure:
As always, do a NANDroid first.
Click to expand...
Click to collapse
Cool, just did a nandroid.
So i just put both FRF83 and froyo rooter on my ROOT and flash both? (frf83 first) Its that simple?
Thnx.

SBERG117 said:
Cool, just did a nandroid.
So i just put both FRF83 and froyo rooter on my ROOT and flash both? (frf83 first) Its that simple?
Thnx.
Click to expand...
Click to collapse
This is assuming you've already upgraded to FRF83. The stock builds won't flash through a custom recovery.
There's an pre-rooted update.zip floating around that you can just flash on top of whatever 2.2 build you have:
http://forum.xda-developers.com/showpost.php?p=6926772&postcount=301

thanks to mortzz
that piece is what I look for over that long thread...

mortzz said:
This is assuming you've already upgraded to FRF83. The stock builds won't flash through a custom recovery.
There's an pre-rooted update.zip floating around that you can just flash on top of whatever 2.2 build you have:
http://forum.xda-developers.com/showpost.php?p=6926772&postcount=301
Click to expand...
Click to collapse
Im on rooted FRF72 build. I have a custom recovery. I mean if its not gonna work for me then thats cool, I'll wait. Just trying to learn myself something . lol

SBERG117 said:
Im on rooted FRF72 build. I have a custom recovery. I mean if its not gonna work for me then thats cool, I'll wait. Just trying to learn myself something . lol
Click to expand...
Click to collapse
It doesn't matter what 2.2 version you're on. You can flash that update.zip and you'll be on rooted FRF83.

mortzz said:
It doesn't matter what 2.2 version you're on. You can flash that update.zip and you'll be on rooted FRF83.
Click to expand...
Click to collapse
Cool thnx for the link. Appreciate the help. Guess im one of the first guinea pigs for it. lol . Lets see what happens...

If you loose the drivers for frf83 ( adb devices doesn't show phone, fastboot devices the same).
Just flash Cyanogen's Froyo rooter and your phone will get recognized.

timal said:
If you loose the drivers for frf83 ( adb devices doesn't show phone, fastboot devices the same).
Just flash Cyanogen's Froyo rooter and your phone will get recognized.
Click to expand...
Click to collapse
Im good. Everything works fine, install went smooth. No hiccups or anything. I installed right over FRF72, no wipe, all settings retained. Couldnt have asked for a easier install. lol

Got myself up to FRF83 from rooted FRF72. I did:
pushed the FRF72 > FRF83 update zip to /sdcard/update.zip
pushed cyanogent's quick root zip to /sdcard/
Reboot into the boot loader
flashed stock recovery
rebooted into recovery
installed the update.zip
rebooted into the boot loader
flashed ra-1.7 recovery
rebooted into recovery
installed cyanogen's quick root
rebooted into FRF83 for the first time

randalla0622 said:
Got myself up to FRF83 from rooted FRF72. I did:
pushed the FRF72 > FRF83 update zip to /sdcard/update.zip
pushed cyanogent's quick root zip to /sdcard/
Reboot into the boot loader
flashed stock recovery
rebooted into recovery
installed the update.zip
rebooted into the boot loader
flashed ra-1.7 recovery
rebooted into recovery
installed cyanogen's quick root
rebooted into FRF83 for the first time
Click to expand...
Click to collapse
I didnt need quick rooter to install, does it make a difference? What will it do that the install itself wont?

This file works for me going from (nonrooted) FRF72 -> FRF83

FRF83 help
Here is my situation:
I was running FRF72 and saw that (at the time) the only way to upgrade to FRF83 was rolling back to FRF50.
I then downloaded the stock rom for the T-mobile N1 and passimg.zip to restore it.
I then tried to upgrade to ERE36B by using the update.zip method. This failed and I would see the message: "E:Can't open/cache/recovery/command" followed by an "E: Error in /sdcard/update.zip" Since this did not work I used the passimg.zip method to upgrade.
I am now on ERE36B but when I try to "update.zip" the FRF50 rom I am still seeing "E:Can't open/cache/recovery/command" and "E: Error in /sdcard/update.zip"
I know for sure I did not name the .zip file wrong (update.zip.zip)
Does anyone have any advice for updating to FRF50 from ERE36B or from ERE36B to FRF83?
Thanks!

DPUVince said:
Here is my situation:
I was running FRF72 and saw that (at the time) the only way to upgrade to FRF83 was rolling back to FRF50.
I then downloaded the stock rom for the T-mobile N1 and passimg.zip to restore it.
I then tried to upgrade to ERE36B by using the update.zip method. This failed and I would see the message: "E:Can't open/cache/recovery/command" followed by an "E: Error in /sdcard/update.zip" Since this did not work I used the passimg.zip method to upgrade.
I am now on ERE36B but when I try to "update.zip" the FRF50 rom I am still seeing "E:Can't open/cache/recovery/command" and "E: Error in /sdcard/update.zip"
I know for sure I did not name the .zip file wrong (update.zip.zip)
Does anyone have any advice for updating to FRF50 from ERE36B or from ERE36B to FRF83?
Thanks!
Click to expand...
Click to collapse
make sure you dont have two or more update files on your card.

S3 Now available in clockwork recovery

The S3 has been added to supported devices​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

anyone else having issues flashing CWM Touch from recovery? I can't get it to take even though it successfully completes.

contradude said:
anyone else having issues flashing CWM Touch from recovery? I can't get it to take even though it successfully completes.
Click to expand...
Click to collapse
You downloaded the d2spr version from download.clockworkmod.com?
Sent from my SPH-L710 using Tapatalk 2

:O i know two of those phones!
did the cwm on the connect and lucid

shabbypenguin said:
:O i know two of those phones!
did the cwm on the connect and lucid
Click to expand...
Click to collapse
When are we gonna get an update on the prevail?
Sent from my SPH-L710 using xda premium

Can't backup ROM, "sd marker not found"
Any ideas?

It said that to me when trying to use the app to backup but I did it manualy and it worked fine.

Any advantage/disadvantage of flashing the new CWM through ROM Manager, or manually through ODIN? Btw, do you flash this through ODIN or (old) CWM since this is a .img file?

Just so ppl know, you can find all CWM Recoveries here:
http://download.clockworkmod.com/recoveries/
Our device is d2spr
Towards the bottom you'll find the CWM Touch Recovery, I flashed the img using Mobile Odin and it's working fine
Sent from my SPH-L710 using Tapatalk 2

fergie716 said:
Just so ppl know, you can find all CWM Recoveries here:
http://download.clockworkmod.com/recoveries/
Our device is d2spr
Towards the bottom you'll find the CWM Touch Recovery, I flashed the img using Mobile Odin and it's working fine
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ah... flashed it through mobile ODIN... thanks for the tip, Fergie!

MinimalistChris said:
Ah... flashed it through mobile ODIN... thanks for the tip, Fergie!
Click to expand...
Click to collapse
No problem!
Another tip, backups made with the older CWM recovery (the unofficial one, the one you probably flashed after rooting initially), those older backups may not be compatible with the newer, official versions. I'm using the latest CWM Touch 5.8.4.6 and it seems to backup system and data differently
Sent from my SPH-L710 using Tapatalk 2

Can't seem to get the .img to flash when using mobile odin... I tried to click on Recovery then find the file, but it doesn't list the file, only the folders I have available. Am I doing something wrong?

klarthur said:
Can't seem to get the .img to flash when using mobile odin... I tried to click on Recovery then find the file, but it doesn't list the file, only the folders I have available. Am I doing something wrong?
Click to expand...
Click to collapse
If you downloaded the CWM img file rename it to just "recovery.img" then put it on the root of your SD
Open up Mobile Odin, Select "Open File", then select your recovery.img (I put it on Internal Storage)
After you select your recovery.img, before you select Flash Firmware, it should list the recovery.img in the recovery slot
Then you should be all set. Select Flash Firmware and after it flashes you should automatically be rebooted into recovery (I suggest making a backup ASAP just to be safe)

Phew... Glad to see there is a fix... I thought I was losing my freaking mind when I tried backup of my rom....
EDIT: something is borked...not right ...frustrated user...mad.mad.mad :crying::crying::crying:
Sent from my SPH-L710 using xda premium

Mobile Odin didn't help me much... could I install the touch recovery.img through adb? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 ?

wpjessie said:
Mobile Odin didn't help me much... could I install the touch recovery.img through adb? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 ?
Click to expand...
Click to collapse
The mobile Odin way did not work for me. After I flashed the img file, rebooted and tried to do a backup using Clockwork mod, the phone rebooted and gave me the same errors as posted above! ???Help???
EDIT: Duplicated this same error/issue on my second GS3...so it is definitely CWM related...also..cannot "see" or view the backups on the phone via the Rom Manager app either..very frustrating...hope those smarter than me can fix...I am willing to assist in any way... thanks

I flashed the new touch cwm in the unofficial recovery and it works, but doesn't stick, reverts back to the old recovery after a reboot???
Sent from my SPH-L710 using xda premium

This may be a dumb question but, couldn't we just install ROM Manager and flash the CWM recovery with it, like I used to do on my EVO 4G?

w8setter said:
I flashed the new touch cwm in the unofficial recovery and it works, but doesn't stick, reverts back to the old recovery after a reboot???
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
the team epic guys has set us up with a recovery that would stick cause the first samsung ota automatically reverted to their own recovery instead of cwm. maybe this issue is related. it just keeps overwriting what you flashed thinking that it's a bad (Samsung) recovery. don't know for sure as i haven't tried it yet.

gtpdjw said:
It said that to me when trying to use the app to backup but I did it manualy and it worked fine.
Click to expand...
Click to collapse
that defeats the purpose of this new, "supported" recovery as i would like the option to flash things and manage backups via rom manager.
jf11time said:
This may be a dumb question but, couldn't we just install ROM Manager and flash the CWM recovery with it, like I used to do on my EVO 4G?
Click to expand...
Click to collapse
thats what i did.
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
mine sticks, just rebooted 2 times, and after booting into recovery again still version 5.8.4.6 which is latest.
installed via rom manager
about to try touch

4.2.2 update

Will the 4.2.2 OTA for my Nexus 7 take away root access?
Sent from my Nexus 4

Yes.
http://forum.xda-developers.com/showthread.php?t=2144330
There's a long thread on 4.2.2 already.

What about the bootloader? Will it relock it? Or is it left alone?
Sent from my Nexus 4

Also, I was just reading through that thread and it said if you have SuperSU that it won't unroot. Is that true? Or do I need to use ota rootkeeper? I know that thread may have the answers I'm looking for, but I'm too tired to read through it all. I ask all these questions because I have no computer to reroot and reunlock the bootloader with.
Sent from my Nexus 4

Slender Troll said:
Also, I was just reading through that thread and it said if you have SuperSU that it won't unroot. Is that true? Or do I need to use ota rootkeeper? I know that thread may have the answers I'm looking for, but I'm too tired to read through it all. I ask all these questions because I have no computer to reroot and reunlock the bootloader with.
Sent from my Nexus 4
Click to expand...
Click to collapse
Afaik it won't relock your bootloader.
Sent from my HTC One X

I flashed back to stock.
Flashed the update
Flashed a SuperSU.zip
Rebooted
Then reinstalled twrp through goo.Im app
When I flashed update I lost root and recovery
And all is good again
Sent from my Nexus 7 using XDA Premium HD app

Slender Troll said:
Will the 4.2.2 OTA for my Nexus 7 take away root access?
Sent from my Nexus 4
Click to expand...
Click to collapse
I was on JOP40D (4.2.1) Stock, rooted, with CWM 6.0.2.3. I downloaded this OTA file http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip from the link in the other 4.2.2 thread (http://forum.xda-developers.com/showthread.php?t=2144330)
I booted into CWM, and flashed the downloaded ZIP file as normal
When I told CWM to reboot, CWM warned me the update would flash stock Recovery and do I want to STOP this from happening and I said YES.
It then said I had lost root, and do I want to restore root, and I said YES.
It then booted into Android and continued with the upgrade.
I now have 4.2.2 stock installed (JDQ39), and still have root and custom recovery, and an unlocked bootloader.
From what I have read, if you 'sideload' the update using ADB, or do a normal OTA update, you will lose root and custom recovery. However, using the steps above will keep root and recovery for you

What if I'm using TWRP?
Sent from my Nexus 4

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
im in the same boat,
im on 4.1.2 twrp what do i need to do to get to 4.2.2? just use that ota root keeper?

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
TWRP is same to CMW, but for sure you should install Voodoo OTA Rootkeeper, backup SU then flash the 4.2.2 update.zip. Finally, open Voodoo and restore the backup SU --> your Root is kept. Just in case you need to verify root will work or not. Go to Play Store, install Root Checker (joeykrim) and check your root permisson.
I updated my N7 to 4.2.2 without removing root by these steps above.

Benjoy Ericsson said:
TWRP is same to CMW, but for sure you should install Voodoo OTA Rootkeeper, backup SU then flash the 4.2.2 update.zip. Finally, open Voodoo and restore the backup SU --> your Root is kept. Just in case you need to verify root will work or not. Go to Play Store, install Root Checker (joeykrim) and check your root permisson.
I updated my N7 to 4.2.2 without removing root by these steps above.
Click to expand...
Click to collapse
Can I do this without a computer?
Sent from my Nexus 4

Slender Troll said:
Can I do this without a computer?
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, if you can put your 4.2.2 OTA update.zip in your N7 Internal Storage.
Maybe by downloading the zip through wifi connect.

Benjoy Ericsson said:
Yes, if you can put your 4.2.2 OTA update.zip in your N7 Internal Storage.
Maybe by downloading the zip through wifi connect.
Click to expand...
Click to collapse
Wi-Fi connect? And where do I put it once I have it?
Sent from my Nexus 4

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
I don't think it matters...
I used TWRP to flash the update.
Afterwards, the bootloader was still unlocked... but had been updated from 4.13 to 4.18.
And I had to reflash TWRP as the update had wiped it out, effectively resetting recovery back to Googles default recovery.
Rgrds,
Ged.

Slender Troll said:
Wi-Fi connect? And where do I put it once I have it?
Sent from my Nexus 4
Click to expand...
Click to collapse
This is OTA link for N7 Wifi Only.
Connect to wifi, download the 4.2.2 update.zip to your internal storage from this link http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (anywhere is ok, be sure to remember the path). Reboot your N7 to recovery mod (TWRP), choose install and browse to where you put your zip in internal storage.

Benjoy Ericsson said:
Connect to wifi, download the 4.2.2 update.zip to your internal storage from this link http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (anywhere is ok, be sure to remember the path). Reboot your N7 to recovery mod (TWRP), choose install and browse to where you put your zip in internal storage.
Click to expand...
Click to collapse
Just to clarify, I can leave it in the download folder?
Sent from my Nexus 4

So I'm in recovery and at the part where it gives me the option to flash. Is there anything I need to do or back up before I flash the OTA so that I don't lose root?
Sent from my Nexus 4

Success!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk HD

Just downloaded the OTA zip, went to recovery and tried "install" (both checkmarks to check md5 and zip off) and got FAILED! The device booted normally afterwards. I copied file via USB cable in standard media mode... what am I doing wrong? On 4.2.1, stock, rooted, 16gb Wifi only N7.

dalanik said:
Just downloaded the OTA zip, went to recovery and tried "install" (both checkmarks to check md5 and zip off) and got FAILED! The device booted normally afterwards. I copied file via USB cable in standard media mode... what am I doing wrong? On 4.2.1, stock, rooted, 16gb Wifi only N7.
Click to expand...
Click to collapse
Try downloading it using Wi-Fi from the link above, and then back everything up. what recovery are you using? I left the zip in the download folder, so I wouldn't lose it.
Sent from my Nexus 4

Firmware-update JLS36I (Android 4.3.1) Nexus 7 2013 LTE available

This morning I was suprised to find a new update for my Nexus 7 2013 LTE; it brings the Android-version to 4.3.1
No changelog found yet...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?

Jacktheskipper said:
Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?
Click to expand...
Click to collapse
It's broken my root, though that's probably because I used the OTA update rather than flashing in recovery.

I got it too.
in the update file a some changes at:
keymaster / keystore
camera firmware
framework
services and telephony-common
what exactly has changed I do not know.
root + recovery need to be flashed again. but no problems.

if root and recovery need to be flashed again, did you just do the ota update from the sytem or did you sideload the zip and flash it from recovery?

I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan

jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
You won't be able to until someone puts out a custom ROM for Flo/Deb.

jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.

jak3z said:
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.
Click to expand...
Click to collapse
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!

jmone said:
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!
Click to expand...
Click to collapse
That was totally unnecessary,

I've updated European nexus in Russia without any problem
Have a trwp recovery and supersu binary. Check ota survivalable mode in supersu and just apply update. Trwp updates all stuff. Root works, recovery didn't check for now

jak3z said:
That was totally unnecessary,
Click to expand...
Click to collapse
Thanks.... Next time!

Update :lost trwp recovery and need to flash it again.
Отправлено с моего...

oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

keplenk said:
oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
You can run the OTA perfectly fine, you will lose Root and Recovery after you OTA, but you can get back those 2 anytime you want. Grab the CF-Auto-Root of chainfire (its on the Android Original Dev forum) and you will get root back.

keplenk said:
or can i just update while rooted?
p
Click to expand...
Click to collapse
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.

Jacktheskipper said:
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.
Click to expand...
Click to collapse
http://download.chainfire.eu/supersu

1. Go into SuperSu settings to enable survival mode.
2. Download the OTA directly on your Nexus as you would without root and restart to install.
3. It will be installed by TWRP, root will be kept, but TWRP will be gone.
4. Reflash TWRP in Fastboot.

[VK810] Official Kit Kat Update Information

We're all in the process of receiving and installing this update, and there are many questions about recoveries, rooting, etc. This is a thread to gather all the info we know so people don't have to be searching through tons of posts.
(I'm in the process of installing now, so I'll answer as many of these questions as I can. I will also update the OP with info from other users. If anything I state is untrue, please post and let me know.)
Can I take the update while rooted?
Yes! If you are on 4.2 and rooted but on STOCK RECOVERY, you can take the OTA and keep root.
Can I take the update with TWRP installed?
No! You will bootloop into recovery.
Is there an alternative/manual/TWRP method of installing?
Yes, see below post.
How am I supposed to update if I installed TWRP?
See below post, "README if you are currently on JB4.2.2"
Alternative method: "download flashify from the play store, backup twrp, then flash the recovery.img from OP. No pc needed & 100% pain free." Thank you to 86shelby. Then take the OTA.
Can I root the 4.4 version?
As of 8/26, yes! Stumproot works with the Bruteforce method. http://forum.xda-developers.com/show....php?t=2850906
Can I downgrade from 4.4 to 4.2?
Yes
If anyone else has questions they'd like posted, please let me know, and I'll put them in.

NOTE: If you want root/twrp in KK4.4.2, you'll need to pre-root in JB4.2.2 before OTA update(towelroot works in JB4.2.2, but not in KK4.4.2)
Looks like Stumproot works with KK4.4.2
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
Do one of the options below:
A) If you still want 4.4.2 via Verizon OTA, flash stock recovery
Go into TWRP, restore stock recovery via link below
http://forum.xda-developers.com/showpost.php?p=52975059&postcount=65
B) If you want to stop the bootloop, and flash 4.4.2 via TWRP backup from below...
Go into TWRP, wipe OTA partition (which signals the device to keep going into recovery)
http://forum.xda-developers.com/showthread.php?p=51749086#post51749086
Click to expand...
Click to collapse
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)​
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
If you have TWRP installed, you'll need to flash stock recovery. Either (A)
restore stock recovery only, or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
NOTE: some people have problems with OTA even after restoring stock recovery. You'll have to restore using the (B) method, and lose everything
[*]If you want root in 4.4.2, you'll need to apply root BEFORE OTA (via towelroot, ...?). root is allowed during OTA, will be maintained after OTALooks like stumproot works
Apply OTA, hope nothing goes wrong
Yay!
Click to expand...
Click to collapse
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
Root ? (Towelroot isn't working though)
Flash 4.2.2 aboot.img and TWRP.img
A) Upload aboot.img from 4.2.2 to device, then do
Code:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
B) Follow steps in TWRP thread to install TWRP
Click to expand...
Click to collapse
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Install TWRP (see section above)
Get 4.2.2 TWRP backup from here and restore
or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
Click to expand...
Click to collapse
​

Guess I got lucky - never got around to installing the custom recovery. I MEANT to do that....

https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot

So this is what I get when I check for update. I'm stock unrooted I even did a FDR. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1080 using Tapatalk

Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.

modus81 said:
Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.
Click to expand...
Click to collapse
have you tried other root methods?
ioroot, or this root below? (
http://forum.xda-developers.com/showthread.php?t=1886460&highlight=4+2+2

paperWastage said:
https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot
Click to expand...
Click to collapse
How do I install this?
Sent from my VK810 4G using Tapatalk

gfullwr70 said:
How do I install this?
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
you don't. go through Settings-> System update

paperWastage said:
you don't. go through Settings-> System update
Click to expand...
Click to collapse
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk

gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Same here

Flashing comletely stock via .kdz file
I'm getting the 0X13E error. Does anyone have the the process for this? I saw a different thread that directed to a droidreviews.com website but one of the files it said to download, my Chrome browser scanned as malicious so I stopped pursuing that route.

ssinn said:
Same here
Click to expand...
Click to collapse
gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
Thanks this is what I was looking for. I'll give it till tonight to see if the ota shows up then I'll try this method.
Sent from my XT1080 using Tapatalk

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?

prana22 said:
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?
Click to expand...
Click to collapse
first one.... my tablet wasn't able to find an OTA on 4G LTE (on t-mobile's network), but wifi works fine

Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
That's interesting, and good to know. Can anyone else verify this? I didn't think the update would go through if you were rooted. Now I might downgrade through kdz again and root before I take the OTA.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
go flash TWRP, make backup of stock and share it please?

How can I revert to stock recovery in OSX? All I see is the LG Mobile tool for windows?