Develop Bugs

[Q] OTA from 4.1.1 to 4.2.1 please help...

After getting the phone, I right away flash it with google's 4.1.1 ROM. After that I rooted it and fastboot enable with unlocked.
Since 4.1.2 came out in OTA, I have been unable to update it successfully.
I did get prompt asking me to update and when I agree, it will try to update and then reboot to update. However, the update will fail and I will still get stuck in 4.1.1. The failed update has not affected the phone in anyway. So I continue using it at 4.1.1.
Anyone can provide simple instructions on how to update to 4.2.1 without erasing all my data? Especially contacts and emails. I have read there are numerous ways like nandroid and titanium and so on. Then there are mention that I will need to root the phone again after updating and so on. This is really overwhelming for me. Too much information and not sure which direction to go.
Previously I used nexus toolkit to convert the phone to yakjuw (or something) and updated to 4.1.1. Can I use this nexus toolkit again for it? Or OTA is a better way to preserve DATA?
Very sorry if there is already a thread for this cause I can't find it. I am new to this forum and the amount of information especially in galaxy nexus section is overwhelming but at the same time AWESOME!. Great phone with great community support.

Do you have the stock recovery or clockwork?

ironside2011 said:
Do you have the stock recovery or clockwork?
Click to expand...
Click to collapse
I don't think I have the stock recovery. But that can be easily downloaded, right?
As for CWM, I don't think I have it installed. I tried to keep the phone as vanilla as possible. However, I have tried CWM on other android devices before and wouldn't mind installing this.

First off, check your accounts settings. Sync should be set up for both contacts and emails (you should have a gmail account, right?). So that's of no concern. Turn your phone off. Now hold both volume buttons and press power [fastboot mode]. Use volume keys to scroll so top says recovery, then press power. Now you'll see what recovery you have, either android or cwm. If it's android, then you can hold volume up and press the power button to get the menu, which includes reboot now. If it's stock recovery, perhaps the update failed because you're rooted. Try OTA Rootkeeper, hide your root, then clear google services framework, and try the update again, and see if it sticks.
You should find out what version you have, btw, yakju, takju, etc.. You can do this by opening maps, settings, then about.
O, and OTA will preserve data, toolkit will likely wipe all in order to flash whole rom, not just update. I'd say that the common wisdom is skip the toolkits until you fully understand what, how, and why they work in such and such a way.

bodh said:
First off, check your accounts settings. Sync should be set up for both contacts and emails (you should have a gmail account, right?). So that's of no concern. Turn your phone off. Now hold both volume buttons and press power [fastboot mode]. Use volume keys to scroll so top says recovery, then press power. Now you'll see what recovery you have, either android or cwm. If it's android, then you can hold volume up and press the power button to get the menu, which includes reboot now. If it's stock recovery, perhaps the update failed because you're rooted. Try OTA Rootkeeper, hide your root, then clear google services framework, and try the update again, and see if it sticks.
You should find out what version you have, btw, yakju, takju, etc.. You can do this by opening maps, settings, then about.
O, and OTA will preserve data, toolkit will likely wipe all in order to flash whole rom, not just update. I'd say that the common wisdom is skip the toolkits until you fully understand what, how, and why they work in such and such a way.
Click to expand...
Click to collapse
Ok..let me summarize:
1) Check whether phone is stock recovery or CWM.
2) If stock recovery then install OTA rootkeeper and try update OTA again.
3) if CWM recovery then .....restore back to stock recovery???

The easiest thing you can do is backup your phone. Get a toolkit for your phone. Download the factory image for your phone from Google and flash it. You will have 4.2.1 in a jiff.
Sent using xda premium.

[email protected] said:
The easiest thing you can do is backup your phone. Get a toolkit for your phone. Download the factory image for your phone from Google and flash it. You will have 4.2.1 in a jiff.
Sent using xda premium.
Click to expand...
Click to collapse
backup using? titanium? a bit troublesome when nexus does not have sdcard. Storage is almost full.

Platform
android:samsung-maguro-Galaxy Nexus
Device
samsung yakju
ClockworkMod Recovery v5.8.0.2
What's the best way to update now without losing data?

exactly.
abubin said:
Ok..let me summarize:
1) Check whether phone is stock recovery or CWM.
2) If stock recovery then install OTA rootkeeper and try update OTA again.
3) if CWM recovery then .....restore back to stock recovery???
Click to expand...
Click to collapse
3) fastboot flash recovery *recovery.img*, then you'd try the OTA.
Have you consulted: http://forum.xda-developers.com/showthread.php?t=1419170
and http://forum.xda-developers.com/showthread.php?t=1626895 ?
these two threads should be able to teach you almost the exact processes...
btw, just found this: http://forum.xda-developers.com/showpost.php?p=36050897&postcount=9
Even though that's takju, it should be identical to yakju.
And if confident that you havent modified anything other than recovery and root, id still try to flash the stock recovery and ota first.

abubin said:
After getting the phone, I right away flash it with google's 4.1.1 ROM. After that I rooted it and fastboot enable with unlocked.
Since 4.1.2 came out in OTA, I have been unable to update it successfully.
I did get prompt asking me to update and when I agree, it will try to update and then reboot to update. However, the update will fail and I will still get stuck in 4.1.1. The failed update has not affected the phone in anyway. So I continue using it at 4.1.1.
Anyone can provide simple instructions on how to update to 4.2.1 without erasing all my data? Especially contacts and emails. I have read there are numerous ways like nandroid and titanium and so on. Then there are mention that I will need to root the phone again after updating and so on. This is really overwhelming for me. Too much information and not sure which direction to go.
Previously I used nexus toolkit to convert the phone to yakjuw (or something) and updated to 4.1.1. Can I use this nexus toolkit again for it? Or OTA is a better way to preserve DATA?
Very sorry if there is already a thread for this cause I can't find it. I am new to this forum and the amount of information especially in galaxy nexus section is overwhelming but at the same time AWESOME!. Great phone with great community support.
Click to expand...
Click to collapse
OTA update will not work on a rooted phone. You will have to flash the actual 4.2.1 ROM.

It should work with OTARootkeeper, and hidden root, I've done it myself. (read above)

bodh said:
It should work with OTARootkeeper, and hidden root, I've done it myself. (read above)
Click to expand...
Click to collapse
I will use this method. I can find OTARootkeeper. But can't find hidden root apps.
Not sure which is the one:
https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot&hl=en
https://play.google.com/store/apps/details?id=com.troy1103.hideyourroot&hl=en

I guess i used the wrong words.. Open OTA Rootkeeper, select backup su, then temp un-root. You can download a rootchecker after this to check if your system shows as rooted or not rooted.

I tried to OTA update but failed.
First, I use OTA rootkeeper to hide root. After that I tried to update but the phone boot up to CWM and show update failed. So I then use nexus toolkit to change back to stock recovery. However, after doing that...when I check for update in the phone, it says no update.
After doing some reading, I try to update using manual method. Which is to boot into stock recovery and then choose update from cache. I have checked the update zip file in cache folder. Then I boot into stock recovery. But in stock recovery, I do not see any option to update from cache. I only see update from ADB or update from SDCARD (or USB...forgot). Tried both and it doesn't work.
The Nexus Toolkit must have restored my stock recovery back to the GSM phone that have SDCARD. Mine does not have SDCARD slot. I do not dare to restore from other recovery.img file. Anyone can point me to the right direction for a recovery.img that will not screw up my stock recovery or the phone at all?
Thanks.

The 'SDCARD' is the onboard storage, nothing wrong there
Easiest thing is to backup your data using Titanium Backup, flash the factory 4.2.1 image, reroot and then restore the backup

EddyOS said:
The 'SDCARD' is the onboard storage, nothing wrong there
Easiest thing is to backup your data using Titanium Backup, flash the factory 4.2.1 image, reroot and then restore the backup
Click to expand...
Click to collapse
So much hassle just for OTA. I guess now my only choice is to use this method. Thanks.

Ultimately, if you want the OTAs stay 100% stock. If you wanna root, go custom

Since you now have stock recovery, which is probably why the OTA failed [though there could be many reasons], Have you tried to clear Google services framwork data (under applications, all), to get the update notification and try again? If it stills fails, then at this point the others are right. Titanium backup method..Just skip the system apps in the backup, right guys?

What will interfere with OTA updates?

Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!

sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.

gooberdude said:
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.
Click to expand...
Click to collapse
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!

sashusmom said:
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!
Click to expand...
Click to collapse
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.

gooberdude said:
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.
Click to expand...
Click to collapse
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required

sashusmom said:
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required
Click to expand...
Click to collapse
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.

gooberdude said:
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.
Click to expand...
Click to collapse
Great info! Thank you Gooberdude! And I don't Jump .LOL. I just take it one step at a time....Smoothe, then if things are screwed up, I jump around!!! And call out for help!!! And duh- I forgot custom recovery is a problem.
I think I have access to both recoveries. Is that possible? I think I can get into the stock recovery by holding down the correct buttons sequence, but can get into Philz by using my cheat app that I really love, Flapps PowerTool. I'll review what I have and how to do the button sequence to pull up stock recovery and post back.
Thank you for the detailed instructions...Appreciate it. It will probably be awhile before kit kat is put out for our Note 8's anyway.
*********************************************************
Nope. Just Philz custom.

sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Here ya go http://forum.xda-developers.com/showthread.php?p=50156744
Sent from my SM-N900V using Tapatalk

Restoring Stock boot.img & Stock recovery.img then taking OTA

I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!

AndroidUzer said:
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
Click to expand...
Click to collapse
Wondering same thing. How to get update, the reroot without having to do a full return to stock first.

Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.

It worked!
Swizzle82 said:
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
Click to expand...
Click to collapse
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.

AndroidUzer said:
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
Click to expand...
Click to collapse
Hey, I've been searching through the forums trying to find the stock recovery/boot images for the last hour to no avail. Would it be possible for you to post links to where you found them? Thanks!
EDIT: Annnnnnnnnnd of course as soon as I ask, I find it in another thread I was reading http://forum.xda-developers.com/showpost.php?p=55359856&postcount=125

Where can i found the stock boot.image and stock recovery.img

bjg020683 said:
Where can i found the stock boot.image and stock recovery.img
Click to expand...
Click to collapse
Link in post just above yours...

Thanks

Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!

laoh said:
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
Click to expand...
Click to collapse
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!

AndroidUzer said:
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
Click to expand...
Click to collapse
Thanks for the lengthy explanation. Can I verify if what I'm trying to do is same as what you've done? Here's my situation.
- I have the stock LG 4.4.2 KK rom for D851. Not stock AOSP or CM or any other "custom ROM".
- It is rooted and have TWRP
- The only thing I've really done to the rom is to debloat - used Titanium to freeze lots of apps that came with the LG rom. I have not deleted any since I've read before that if you delete them, it will make it a pain to upgrade to newer Android versions.
So I've learned the hard way trying to update my phone from 4.4.2 to 5.0.1 LG rom.
- I took the OTA and tried to install it. Big mistake. I ended up in a TWRP bootloop. Had me cringing thinking I just lost everything until I found this post http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508 and fixed it with LG_G3_Flash2FixStuckRecovery.zip (flashed it with TWRP). What a godsend it was. Got me out of bootloop and I didn't have to do factory reset or anything. All my apps and data are intact just the way it was before I began OTA.
- So now I'm back to where I started originally before attempting to OTA to Lollipop.
If I'm reading correctly, what I need to do are:
- Unfreeze all apps
- Restore stock recovery (recovery.img) and boot file (boot.img) - this essentially reverses root and custom recovery. Use Flashify to do so.
- Flash the stock LG Lollipop update (btw - the phone says that the new ROM is already downloaded and ready to go but there's nothing in the cache folder... is there somewhere else I should be looking?)
- Before I reboot - I should flash SuperSU and TWRP which restores root and custom recovery
- Reboot phone, cross fingers.
Somewhere in the middle, am I reading that you need to restore LG stock Kitkat rom first (which I already am on), then update to Lollipop? I'm reading that from this part "This will allow you to go straight to "r" skipping "m" all together. If you are feeling brave and competent you could go straight to Lollipop..."
I'm confused here...
One last thing - Once I'm upgradded to Lollipop, is there an easy way to freeze all the apps I had frozen before instead of going one by one? I have the paid Titanium version but I can't figure out if it has a batch/mass freeze feature.
Thanks!!

No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!

AndroidUzer said:
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
Click to expand...
Click to collapse
I appreciate all of your advice. The thing is, I'm trying to upgrade to Lollipop... I'm already on Kitkat and not really interested in upgrading to a latter dot version of Kitkat.... It just seems like a difficult proposition to do OTA upgrade if you rooted and have non-stock recovery. Since I'm on tmobile d851 stock Kitkat (rooted with frozen apps), I should've never put put TWRP. I thought I might put custom ROM on it but never got around to it and since you pretty much lose wifi calling with non-Tmobile ROMs, I just never did... More of a pain now....

[Q] How do I update my rooted Nexus 7?

Hey guys I just got the Nexus 7 2013(Wifi) today for Christmas and I just rooted it with Nexus Root Toolkit, and I wanted to know how I can update to Android 5.0 without wiping it. I have Android 4.4.4 with the latest TWRP.

You didn't install a custom ROM? I have the same tablet, I also rooted mine. I updated to Jellybean and everything seems to be working, except I lost root and it's really annoying that I haven't found how to root it again without it being wiped erasing all my apps and data.

You can update it via OTA, but you will lose root.
Nexus7II_Lollipop

critofur said:
You didn't install a custom ROM? I have the same tablet, I also rooted mine. I updated to Jellybean and everything seems to be working, except I lost root and it's really annoying that I haven't found how to root it again without it being wiped erasing all my apps and data.
Click to expand...
Click to collapse
If u are only on jellybean, u might be able to just use the towelroot apk and not erase any data...

bigboolean said:
Hey guys I just got the Nexus 7 2013(Wifi) today for Christmas and I just rooted it with Nexus Root Toolkit, and I wanted to know how I can update to Android 5.0 without wiping it. I have Android 4.4.4 with the latest TWRP.
Click to expand...
Click to collapse
You can either:
(1) Wait for the OTA: hence no wipe of data
(2) Use the factory image and remove the wipe command (-w) (search for a how to, answered many times here)
(3) Use the OTA zip (not familiar with process, if it wipes or not, as I always use factory images but I guess there is a how-to in here as well somewhere!)
(4) ...
One thing you should take into account though is that for a major android version jump (e.g. 4.4.4 => 5) you should always consider to wipe.
In addition, questions go into Q&A section

You can install multirom. So you can keep the stock rom and install lollipop as well. Just have a look at the multirom thread on how to install it. It's quite easy.

There is zero reason not to do a clean install in your situation.
Flash the factory image, reflash twrp, flash su zip, done.

bigboolean said:
Hey guys I just got the Nexus 7 2013(Wifi) today for Christmas and I just rooted it with Nexus Root Toolkit, and I wanted to know how I can update to Android 5.0 without wiping it. I have Android 4.4.4 with the latest TWRP.
Click to expand...
Click to collapse
You just got it so why not take the wipe and just install the image from google?

[Q] Questions

Hi,
Is it possible to be on stock android while being rooted and keep getting ota? I was on 4.4.4 and was rooted, and when I got the ota I got an error and would not let me install.
Also, since im on cm11 now, is it possible for me to throw on Franco Kernel? Because I heard you could not use that for some reason.
Thanks.

Being rooted on stock firmware will not prevent OTAs from being pushed to you. It will likely prevent you from installing the updates due to changes to the /system and (probably) /recovery, which it seems like you experienced before on 4.4.4. The OTA will start to install but will have an error and abort when it detects that things are changed in your /system partition.
To get around this, one option is to do a full factory reset to get back to 100% stock (removes root/custom recovery AND user data). Some folks back stuff up by various methods, others just reinstall everything, it's up to you. Take the OTA and then root again with Chainfire Autoroot (CFAR).
You can also flash a stock /system and /recovery only, then take the update. Once you have the update, run CFAR.
Lastly, you can use the Factory Images and go straight to the version you want. I went from 4.4.4 to 5.0 and then from 5.0 to 5.0.1 with factory images and NO DATA LOSS. After downloading the image, unzip and edit the flash-all.bat file to remove the -w flag near the end. This tells the script to wipe the partitions before flashing them. Removing it will prevent the wipe, and preserve all your apps/data. Save the .bat file, put the N7 in bootloader and run the batch file. Once it runs (takes like 1-2 minutes), you can run CFAR to get root back on 5.0/.1.
As for the CM11 Kernel question, I have no idea. Someone else can touch on that.
Edit: also, you don't need to go from 4.4.4 to 5.0 to 5.0.1 with factory images, you can go straight from 4.4.4 to 5.0.1. Since you already flashed CM11, I'm guessing you wiped your data, so I would just use the factory image to 5.0.1 without editing the batch file and get a fresh install from there. The same methods described should work for future updates beyond 5.0.1, root methods pending.

Or you can do what a few of us have done--go to this thread:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
Follow the instructions to update your bootloader, make sure you're using TWRP 2.8.1.0 or newer, copy the ROM to your internal storage and flash with TWRP. (I wiped cache and Dalvik before and after flashing, but it apparently isn't necessary.) No data loss, working fine for 3 weeks now.

I checked about your last method, removing the w, and many have said that will mess with your android and you SHOULD NOT do it. Is that true?

Removing the "w" forces the install to not wipe. It could cause issues, but it also might not.