Database Develop

[Q] Error while installing 5.0.1 update

Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help

saman0suke1 said:
Hi I just got the 5.0.1 update, I downloaded it and the phone rebooted itself, I got the installation screen and after 5 seconds I just got the word "error" and I had to restart it manually; the device is rooted, have anyone else had this problem? I would appreciate your help
Click to expand...
Click to collapse
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.

My Nexus 6 took 5.0.1 just fine, but my Nexus 7 does this same thing, running stock ROM/Bootloader/Recovery/etc. The ONLY thing done to it is the Fastboot OEM unlock, but I doubt that alone would stop it. I'm curious to know what resolves this ( other than downloading the factory image and flashing it without wiping the userdata )

Just got same error. I didnt even root phone, bought it today, it installed apps from backup of my previous Nexus 4 and OTA is failing.

cupfulloflol said:
With lollipop you can't take an OTA if you are rooted or running just about anything else modified (custom kernels, like ones that have force decrypt disabled also will cause it to error out).
You can still flash it manually by flashing the images. If you don't want to wipe, don't flash the userdata.img . Also, if you aren't currently encrypted, booting up with the stock kernel will force encrypt your device, so don't flash that if you want to stay that way. You can then re-root. There are more in depth instructions for doing this out there if you search around for them.
Click to expand...
Click to collapse
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!

saman0suke1 said:
So basically the only way is to flash the image manually? If I choose not to flash userdata.img my phone data (photos, contacts, apps, etc) won't be erased right? But I will lose root correct? Thanks!
Click to expand...
Click to collapse
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.

cupfulloflol said:
Correct, with Lollipop if you modify things you basically are then forced to manually take the updates. Not that big of a deal as you would likely be needing a PC to reinstall your custom recovery or re-root anyhow after the update.
Flashing userdata.img isn't necessary to update. Neither is recovery.img if you want to keep a custom recovery.
Also as I mentioned before, if you have disabled encryption on your device, if you flash the stock kernel (boot.img) and boot up with it you will re-enable forced encryption. You will need to flash a kernel with force encryption disabled if you want to keep running without encryption. If you haven't disabled encryption, or don't care if your device re-encrypts (this doesn't erase anything, just may take a few minutes on first boot) then this doesn't matter.
Click to expand...
Click to collapse
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!

saman0suke1 said:
Can I manually update without removing root first? Am I going to receive an error if I don't remove it? based on what you said, I will remove userdata.img and recovery.img and that will not wipe my data right? Do I have to decompress those files or the flash-all.bat will take care of that? Thanks!
Click to expand...
Click to collapse
I'm interested as well. Mine is rooted and I have encryption disabled, and I have TWRP on my phone. I tried to sideload the OTA update, but I can't get my phone to start sideload. I even flashed the stock recovery to get it to go, and no dice. What do I do next?

Anyone? I would appreciate the feedback, thanks!

sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.

cmh714 said:
sideload refers to adb as I understand it. thats NOT how you flash....you use fastboot to flash so you can do it all by hand or use one of the toolkits that script it for you.
Click to expand...
Click to collapse
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!

saman0suke1 said:
Thanks, I get that, however I wanted to know if I need to remove the root before installing the update and if I need to decompress the .zip with the .img files or the batch will do that? thanks!
Click to expand...
Click to collapse
If your doing from the PC you need to extract the zip file from within the image and then fastboot them. As for root, when you do it from fastboot I dont believe it matters as you will lose root anyway and need to re-root via flashing SuperSU.zip

Worked great! Thanks! Android 5.0.1 and root, no data deleted

Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!

Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.

naulsballs said:
Can you receive and install OTA updates with an unlocked bootloader? Everything else is stock, no disabled encryption or anything just unlocked bootloader.
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using XDA Free mobile app

saman0suke1 said:
Worked great! Thanks! Android 5.0.1 and root, no data deleted
Click to expand...
Click to collapse
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks

TOCS88 said:
Is it normal to not have received an update beyond 5.0? I have had a Nexus 6 since day one, no rooting of any kind and I have not received 5.0.1.
I have done the sideload method, but I really don't want to bother with it. I do however want some of these terrible bugs I am experiencing squashed. This phone is giving me lots of issues lately.
Thanks!
Click to expand...
Click to collapse
Try pulling your Sim card out and rebooting.

scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you're planning to stay rooted (meaning no OTA in future) system.img, boot.img and radio.img in any order.

scotbotmosh said:
Can you provide steps for this. I am in the same situation. I have the 5.0.1 image downloaded, just wondering what files and what order to flash. Thanks
Click to expand...
Click to collapse
If you use fastboot, just run these commands in terminal (I used windows, so in order to flash using fastboot, put the image that you downloaded for the update in the same folder where you have fastboot and open a terminal there) you can rename the .img files to whatever you like and replace those name in the commands below:
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
Then reboot it:
fastboot reboot-bootloader
Then flash these:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
And that's it. These commands are run while the phone is connected to the PC, you have to turn it on by pressing volume up + volume down + power.
Good luck.

[Q] Need stock recovery !

i need to do OTA update , already with twrp and root , so in order to do ota update i need to fastboot stock recovery !
upload a stock recovery.img if anybody having it.

download shamu image , extract to get the recovery.IMG

It's a Nexus load what you wish. Images here :
https://developers.google.com/android/nexus/images#shamu
Sent from my Google N6 on VZ

yes i know that , i thought rather downloading whole image if somebody could provide me the recovery image only well thanks. ill do it.

ashupulse said:
yes i know that , i thought rather downloading whole image if somebody could provide me the recovery image only well thanks. ill do it.
Click to expand...
Click to collapse
It needs to be more than just "stock recovery". It needs to be the exact version the ota will expect. So you'll have to download the matching image to your version you're on now...
Which if you're doing that, hadn't you just as well download the latest 5.1 image and just flash all that?

I would just flash the factory image..... less chance of a mess....

Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data

mymusicathome said:
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
Click to expand...
Click to collapse
I hear you. if anything, back in the days, we used to avoid the OTA. I'm not sure why everybody has such a hard on for it.
Sent from my Google N6 on VZ

Only ota I took was when my n5 forced one on me out of the box. Never intentionally took one since android 1.5

recovery from 5.0.1
rootSU said:
It needs to be more than just "stock recovery". It needs to be the exact version the ota will expect. So you'll have to download the matching image to your version you're on now...
Which if you're doing that, hadn't you just as well download the latest 5.1 image and just flash all that?
Click to expand...
Click to collapse
yes you are right actually i downloaded 5.1 exctracted recovery , flashed via fastboot.... and i hit error.
so lesson is recovery from 5.0.1 is needed.

ashupulse said:
yes you are right actually i downloaded 5.1 exctracted recovery , flashed via fastboot.... and i hit error.
so lesson is recovery from 5.0.1 is needed.
Click to expand...
Click to collapse
How are you flashing?

mymusicathome said:
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
Click to expand...
Click to collapse
When updated to 5.1 from 5.0.1 -- I had to do Factory Data Reset, since after update N6 was showing 32GB instead of 64GB.
Was there a way to avoid Factory Data Reset ? Thank you!

[Q] 5.1.1 stock update: Re-root and Unencrypt Q's

Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?

bovineyard said:
Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?
Click to expand...
Click to collapse
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.

cam30era said:
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.
Click to expand...
Click to collapse
i think with root but encrypted will do the update

HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.

cam30era said:
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.
Click to expand...
Click to collapse
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?

5.1.1 is NOT officially out for the nexus 6. it is in aosp though. thats two differing things. stock is on 5.1.

HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
The OTA package only looks at system.img and boot.img. Of course you need stock recovery to install it. And the "unroot" option inside SuperSU is insufficient. It leaves some traces around that will prevent the OTA from loading. Flash the stock system.img.
And afterwards, when unencrypting, you'll have to fastboot format userdata. Which will wipe your SDcard again.

HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
Bootloader status has no effect on the OTA.

I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?

ibraheeemz said:
I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?
Click to expand...
Click to collapse
As it says above, you cannot FLASH the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA

danarama said:
As it says above, you cannot receive the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA
Click to expand...
Click to collapse
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,

ibraheeemz said:
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,
Click to expand...
Click to collapse
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.

danarama said:
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.
Click to expand...
Click to collapse
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?

ibraheeemz said:
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?
Click to expand...
Click to collapse
No. Only factory reset or unlocking the bootloader loses data. System.img is the rom, flashing to /system. Boot.img is the kernel, flashing to /boot. if you flash these separately, userdata.img is not flashed to /data, so your /data partition remains in tact.
root doesn't touch /data either. Just /system

HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
How do you get root while leaving it encrypted?

Arfyness said:
How do you get root while leaving it encrypted?
Click to expand...
Click to collapse
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.

Evolution_Tech said:
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.
Click to expand...
Click to collapse
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?

Arfyness said:
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?
Click to expand...
Click to collapse
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.

edit - this was a duplicate. i can't delete it.

Evolution_Tech said:
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.
Click to expand...
Click to collapse
Oohhh, wait, so flash from fastboot, except flash SuperSU from TWRP? (update.zip style?) Is only the data partition encrypted then? If that's the case why are folks decrypting? Unlocking the bootloader requires it, but what is that required for?
And thank you loads BTW! I'm so far behind! I'm coming off 3 years of rooted, stable SGS3 stock, last updated to 4.1.2. There were no further stock updates that I wanted, (too many bugs) and everything was working so I left well enough alone.
(I probably would have messed about with CM and other roms, if I had not initially bricked the thing trying to put TWRP on... and had to send it for somebody to JTAG reprogram it. Thought about it several times, but never wanted to chance it again.)
Thanks again!

[Q] 5.1.1 OTA while rooted?

I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!

greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919

Evolution_Tech said:
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Click to expand...
Click to collapse
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?

greycobalt said:
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
Click to expand...
Click to collapse
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.

greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi hi. Made me smile. Thanks for that.

Evolution_Tech said:
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
Click to expand...
Click to collapse
I will definitely do this! Thanks. They haven't posted the Verizon 5.1.1 to the image site yet, so I'll have to wait a bit I guess. :-/ Thanks!
Didgeridoohan said:
Hi hi. Made me smile. Thanks for that.
Click to expand...
Click to collapse

adb sideload issue

Can someone explain this to me as to why https://android.googleapis.com/pack...amu-ota-LMY48I-from-LMY47Z-superblock-fix.zip gives me the following error shown in the attach picture?
Looks like it should match correctly but sideload is errorring out saying otherwise
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>adb shell getprop ro.build.fingerprint
google/shamu/shamu:5.1.1/LMY47Z/1860966:user/release-keys
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>

Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk

david279 said:
Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?

JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
Install the stock recovery in fastboot, you can download it from the factory images or just search for it
Sent from my Nexus 6 using Tapatalk

JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.

danarama said:
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.
Click to expand...
Click to collapse
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.

JimSmith94 said:
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.
Click to expand...
Click to collapse
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA

danarama said:
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
Click to expand...
Click to collapse
There is an LYZ28J factory image available, here > https://developers.google.com/android/nexus/images

danarama said:
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA
Click to expand...
Click to collapse
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?

JimSmith94 said:
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?
Click to expand...
Click to collapse
It will lose root, but you just flash supersu from recovery

I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..

doublejz said:
I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..
Click to expand...
Click to collapse
Just flash the system.img then