Database Users

[Q] stock rooted Lollipop OTA fails?

All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!

moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.

Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.

Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?

moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.

DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.

venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?

moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.

Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?

[INFO] [GUIDE] [HOW TO] Nexus 6 OTA help desk

Here is a dedicated thread for Q&A and general info on OTA's for the Motorola Nexus 6. Please feel free to discuss all things OTA related and ask any questions you may have.
*Bootloader lock status has no effect on OTA pass or fail.*
To summarize, an OTA (Over The Air) is a software update pushed to nexus devices directly from Google. You will receive a notification when one is available for your device. The files are generally large in size and downloading via WiFi is recommended.
With Android 5.0 and up, OTA updating has changed significantly from previous versions. In the past, you could be stock, rooted, with stock recovery and OTA's would flash successfully. This is no longer possible in lollipop. Absolutely no system or kernel modifications can be present in order for the OTA to flash. This means that if you have unencrypted the stock kernel, the OTA will fail. The phone must be in a "out of box" state.
As always, you are not required to take the OTA as there are other options available. If you are already rooted, unlocked and using a custom recovery, you can use an updated custom ROM provided by the amazing development community here at XDA. Factory images are released by Google prior to OTA's being pushed out so most, if not all, of the custom ROMs are updated before you'll even see an OTA notification. Also, there are stock, rooted ROMs available as well.
*Factory images*
You can always update or return to stock via factory images direct from Google. Link to this guide provided in post #2
*Sideloading*
Another feature available to use is the sideload option. With the use of a few simple ADB commands, you can apply the OTA via sideload. Sideloading will require connecting to your PC and a working ADB/fastboot connection. Directions for sideloading are in post #3.
*Updating while rooted, unlocked, and having a custom recovery via fastboot*
This is quite simple with basic knowledge of fastboot/ADB. Download the factory image, extract the system image and flash with fastboot. Then flash TWRP and SuperSU again. You can also flash the boot image if desired. However if you are unencrypted, this will encrypt the device.
Many, MANY thanks to the development community, themers, modders and other talented people here at XDA.
Thanks @El Daddy for guidance and advice.​

Helpful links:
*Please hit the thanks button for the OP's of the XDA threads below if the threads were helpful in any way.*
Beginners guide:
Thanks @xBeerdroiDx
http://forum.xda-developers.com/showthread.php?t=2948481
Setting up and using ADB and fastboot:
Thanks @rootSU
http://forum.xda-developers.com/showthread.php?t=3006500
Factory images installation instructions:
(Including the fastboot flash method for flashing individual images):
Thanks @Mr hOaX
http://forum.xda-developers.com/showthread.php?t=2954008
OTA files:
Thanks @oldblue910
http://forum.xda-developers.com/showthread.php?t=2906493
*For rooted/unlocked users only*
OTA zip files and radio files (TWRP flashable):
Thanks @Q9Nap
http://forum.xda-developers.com/showthread.php?t=3066052
Radio thread (fastboot flashable):
Thanks @zephiK
http://forum.xda-developers.com/showthread.php?t=2969380​

Directions for sideloading
*These directions are based on Android SDK, Windows OS and a 100% stock Nexus 6*
This is just a simple, well known, user guide to using sideload.
Make sure your SDK is updated!​
Download the OTA file to your PC, rename it to update.zip and transfer into the platform-tools folder of your SDK.
Connect your Nexus to your PC with your OEM USB cable.
Hold shift and right click on platform-tools folder and select open command prompt here.
Type: adb devices
If your serial number comes up, you are good to go. If not, check out your drivers in device manager. You may need to manually point your PC to their location. Also, you may need to uninstall any other Android drivers that are not associated with your Nexus.
Type: adb reboot bootloader
Select recovery mode from your phone using the volume down key. Once you've highlighted recovery mode, press power to select it.
It looks like a restart but the the dead android appears with red exclamation point. When that happens, hold power button and press volume up once.
Once in recovery, use the volume down key to select apply update from adb and push power to select it.
When your phone says now send file,
type: adb sideload update.zip
If all goes well, you'll see things progress and your Nexus will restart when complete. If you encounter the device not found error after beginning, unplug your USB and reconnect. I had to do it twice, but it works.

How do we install ota zip

if you are running stock you should be able to use wug toolkit and have it flash this zip file

What about stock-ish? I'm assuming since I'm rooted with my device unencrypted, that I can't flash this, right?

Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.

knitler said:
Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.
Click to expand...
Click to collapse
Were you completely stock?
Sent from my Nexus 6 using XDA Premium 4 mobile app

instructions for mac
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5

I have a modded boot image and it failed to install. Guess ill have to nuke and start over to get this OTA in place.

http://www.androidpolice.com/2015/0...gs-android-5-1-ota-roundup-for-nexus-devices/ I just want to flash the radio but it looks line it's 20 MB bigger than the last

Is anyone creating a flashable zip that works with TWRP?

@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).

I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?

I think I'm on the same situation as edif30
Stock image
rooted
unlocked bootloader
TWRP recovery
How can i sideload w/o losing root?

edif30 said:
I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?
Click to expand...
Click to collapse
You could flash the 5.0.1 factory image except for the userdata.img and radio.img and side load the OTA. Or you can wait for the 5.1 factory image and remove the "-w" from the flash-all script.
You will lose root and TWRP. but your data will remain intact.

So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?

stevexyz0 said:
So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?
Click to expand...
Click to collapse
Yep, just use ADB sideload.

So I had stock 5.0.1 with a custom kernel. I flashed the stock boot.img from the factory image using TWRP and I unrooted from in the SuperSU app, so I should be stock all around except for recovery. When I try to flash the OTA in TWRP it gives the following error message:
Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys or google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy01130854:eng/test-keys.
Any idea why TWRP would think I was running 5.0.2?

cam30era said:
@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).
Click to expand...
Click to collapse
Mine too but how long did it stay on the GOOGLE screen before booting?

Installing 5.0.2 on rooted tablet

So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff

viper2ko said:
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
Click to expand...
Click to collapse
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.

So if I get this right, OTA breaks also when recovery is stock, but supersu installed, modified hosts and gps.conf file

jshamlet said:
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
Click to expand...
Click to collapse
Only changed I have made are installing ad away

viper2ko said:
Only changed I have made are installing ad away
Click to expand...
Click to collapse
The HOSTS file came with the stock image. It counts, unfortunately. (I'm also an Adaway user)

Modify /system, you don't OTA. Period.
Just download the Nexus image and flash just system.img, not the batch file.

Can I flash the system.img in TWRP or do I need to flash the stock recovery?
And will this upgrade me from 5.0.1 to 5.0.2 without losing anything except for root?
Thanks!

^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.

yosmokinman said:
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
Click to expand...
Click to collapse
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.

flyinion said:
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
Click to expand...
Click to collapse
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.

magnumlove said:
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
Click to expand...
Click to collapse
Oh I wasn't going to do a fresh install (i.e. wiping everything), just flash that system.img or modify the batch file to remove the "-w" flag and just run that. I'm wary of running 3rd party ROMs now after I couldn't play movies through Play Movies that were downloaded to the device instead of streamed. Something to do with copy protection I guess

It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.

Telyx said:
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Click to expand...
Click to collapse
Assuming this was in reply to me? I'm not worried about losing anything. I've done the whole back it up and wipe between ROMs a ton on my OG Droid and Galaxy Nexus. In this case it's a worry that Play Movies for instance will detect that it is not a stock ROM/image and will disallow playing downloaded versions of movies in the app. I.e. you can download vs. stream for offline playback. I nearly found out the hard way (night before leaving on a vacation) that I couldn't play downloaded versions (it will download but not play them) when I for instance installed AOKP to my Nexus 7. As best I could tell from a bunch of Googling, it's something to do with copy protection.

It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.

Telyx said:
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Click to expand...
Click to collapse
Ah ok. Well, I ended up using fastboot to flash the system.img last night and looks like I'm good to go. I tried unrooting (SuperSU remove root function) and changing betterbatterystats to a non-system app first but the OTA still failed. Yeah I learned how to use the basic adb/fastboot stuff when I got my Galaxy Nexus and again with the N7. I figured that way if I totally broke something I'd know how to fix it, and all the fancy tools weren't around when the GNex first came out (at least I don't think they were).

I dirty flashed scrosler's 5.0.1 ROM when I got the 5.0.1 OTA notification, but when the 5.0.2 factory image was posted I fastboot flashed the system.img from that and rerooted. Naturally, less than half a day or so later, scrosler posted his 5.0.2.

So for someone that's not really too experience with fastboot, could someone post a step by step?
Where would I get the system.img?

Check the sticky threads for guides. Read and reread then get started on setting up the Android SDK. Once complete, type in the commands letter for letter.

5.1 Update with TWRP / Unlocked Bootloader

Hello,
Is it possible to update from 5.0 to 5.1 if i have unlocked the bootloader? I also have TWRP. I downloaded the 5.1 update, but when i want to install it the phone reboots and i get into TWRP menu. Is there any way to flash the OTA update without losing my current data on the phone?
Thank you!

Dealing with the same problem here.
IIRC TWRP automatically handled OTA updates in the past but it doesn't seem to be working anymore.

What was the procedure you were using before? You just installed as a normal zip from TWRP ?

For the ota to work you have to be 100% stock system, recovery, and kernel. I'd just flash the system and boot images from 5.1 in fastboot to update.
Sent from my Nexus 5 using XDA Free mobile app

So sad. I will lose all the stuff I have on the device.

tzeus said:
So sad. I will lose all the stuff I have on the device.
Click to expand...
Click to collapse
Not if you just flash the System and Boot images and remove -w from the Flashall.bat command to prevent the wipe instead of using the OTA. If you use the OTA, you will have to be stock as the previous posted stated, which since you are rooted with a custom recovery, would require you to flash the stock image, wiping your device, before you could run the OTA. This is the result of a change in the way Android 5.+ authenticates, which is why it worked previously. It now checks the whole partition, and one byte out of place will abort it.
That said, you can always backup your phone (which is a good thing to do anyway before flashing/upgrading) to prevent data loss.
Edit: Actually, thinking about it, I think Wugs added a No Wipe option to his toolkit, just flash System and Boot images from there is likely easiest for you.

Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?

tzeus said:
Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?
Click to expand...
Click to collapse
To be clear, you do not need to relock your bootloader. You can just flash 5.1 and then root and install a custom recovery like TWRP again, yes. If you are not familiar, Wug's NRT make this a breeze. Once you get 5.1 installed, just hit root. It will install the latest TWRP version and root/install SuperSU and Busybox for you.

I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?

tzeus said:
I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?
Click to expand...
Click to collapse
No, download the image and extract it. See this, http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app

Help to get N preview 3 installed from a custom rom with no pc just TWrp

Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk

iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).

DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.

messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684

DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?

jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk

jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.

superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?

flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!

I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk

So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app

GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.

x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?

I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...