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?

MotoX OTA Update - XT1060 Blur_Version.212.166.3.ghost_verizon.Verizon.en.US .zip

Edit: The attached zip in post #2 in a minor update the original 4.4.4 release for XT1060 FXZ. Below are the instructions. This is NOT the Full 4.4.4 OTA update.
Instructions to flash
1.) Move zip file from /cache folder to /sdcard folder if you received OTA (Zip file in 2nd post if you do not have it.)
2.) To be safe, disable xposed framework (if you have it running).
3.) Reboot into bootloader
4.) Use mfastboot to flash stock recovery (if not running it)
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
5.) Boot into recovery from bootloader
6.) Hold Power + Up Button to get recovery menu.
7.) Flash zip file from sdcard.
8.) When complete reboot, then boot into bootloader.
9.) Use mfastboot to flash custom recovery (aka twrp)
mfastboot flash recovery <twrp file name>.img
Click to expand...
Click to collapse
10.) Reboot and enable xposed framework.
11.) Done.
Another suggestion by @KidJoe
After mfastboot flash recovery <recoveryyouwant>.img its long been suggested to do a mfastboot reboot-bootloader then go into recovery, before doing anything else.
We've seen many instances where skipping the reboot-bootloader and enter recovery giving symptoms like the flash of recovery didn't work... (i.e. "old" recovery was still on the phone)
Click to expand...
Click to collapse

just received the update as well but haven't installed

Zip attached.

Maintenance update.

Maintenance update. Does not break root.

911 bug fix, as mentioned in three other threads

WhammyDroid said:
Zip attached.
Click to expand...
Click to collapse
You flash this through RSD lite? I couldn't flash it through my TWRP recovery on my Moto X Developer Edition.
Cindy

cindylike24 said:
You flash this through RSD lite? I couldn't flash it through my TWRP recovery on my Moto X Developer Edition.
Cindy
Click to expand...
Click to collapse
I believe you have to have stock recovery to flash.

dannyxiii said:
I believe you have to have stock recovery to flash.
Click to expand...
Click to collapse
Well then, I'll have to put this on my to do list for when I get home tonight. No biggie.
Cindy

It's far, far more than a 911 bug fix ... there's 2500 lines in the updater script, touching dozens (if not hundreds) of app and files.

Does this require removal of root/xposed or just needs stock recovery?

TheDave1022 said:
Does this require removal of root/xposed or just needs stock recovery?
Click to expand...
Click to collapse
I generally disable xposed and flash stock recovery but root should be fine. Anyone have a copy of the stock recovery? I'm on the dev edition. OTA's are so infrequent on this device that I forget where I stash the stock recovery all the time.

I got the notification last night, and hid it this morning (turned off notifications for the Moto Updater app). I am on an XT1060 Moto Maker, with an unlocked bootloader. In the past I've flashed /system and /recovery to update (from 4.4.2 to 4.4.4) with the OTA, then reflashed TWRP and flashed SuperSU from there. Do I need to do all that, or just stock recovery?
I do have Xposed, Cerberus and App Ops installed as System Apps, I believe.

I found the recovery for myself at the following link:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
Might help someone else...You can verify your build by going to About phone. I had Build number KXA21.12-L1.26

Maverick0984 said:
I found the recovery for myself at the following link:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
Might help someone else...You can verify your build by going to About phone. I had Build number KXA21.12-L1.26
Click to expand...
Click to collapse
That's the exact model number on my phone! Thank you for putting this link up there!!
Cindy

For some reason, I cannot use either mfastboot or fastboot to flash the stock recovery. When flashing it, I get the android icon with the red triangle.
Its been a while since I have had to flash back to stock recovery. What am I missing? I have the stock recoverystored for the last official FXZ.

when android with red triangle appears, press vol up for 3 seconds and you will be given option to flash from sd card.

Well, this has locked me out of re-flashing custom recovery, which - of course - means there's nothing that can be done beyond that.
Any version of TWRP up to, and including, the latest flashes without error ... but when you boot, it's still got stock recovery on it.
So no way to root, apply supersu, or do anything.
---------- Post added 3rd June 2015 at 12:04 AM ---------- Previous post was 2nd June 2015 at 11:37 PM ----------
Anyone got the fxz for this yet?

Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP and develop these steps)
So the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.

FYI... its already confirmed that you do NOT have to disable Xposed... All you need is stock recovery.
See -> http://forum.xda-developers.com/moto-x/moto-x-qa/ota-custom-recovery-t3124492

Root / Unlock Bootloader without removing encryption!

I am not very good at making good step by step instructions but Lots of others are.
Here are the steps that I used.
Unlock bootloader via normal means
Flash chainfire boot img from here
Flash Twrp
Boot into Twrp and click mount and mount /system/
ADB Push supersu Zip file to /system/
Twrp install SuperSu.zip
Reboot
Profit

Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?

Hi
Evo_Shift said:
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Click to expand...
Click to collapse
Wish I tried that first, turned off encryption now, although could re-encrypt.
Yes this should work. TWRP doesn't support decryption, which means any files copied to the phones user storage that we might want to install by TWRP (such as SuperSU), can't be seen by TWRP, as it can't decrypt the user data, so it can't be installed from recovery.
However, the system partition isn't encrypted, so pushing a file to the system, will allow TWRP to read it and install SuperSU. Of course you can't do things like full back ups as there probably isn't enough space on the system file system, so you need the user storage area for that, so you would need that decrypted for larger files so that TWRP can gain access.
Regards
Phil

Don't forget adb sideload for installing zips without using internal storage

Use Oem Unlock?

fastboot oem unlock
Yes

How does this affect using Android Pay?

Rado_vr6 said:
How does this affect using Android Pay?
Click to expand...
Click to collapse
Same as other rooted/unlocked devices it doesn't work.

So you can root while keeping encryption enabled? I need encryption for work, but root is a MUST have. Would like to verify before I order. Thanks.

I was under the impression that flashing the chainfire boot img disables encryption?
Did you fastboot into TWRP (no flashing/installing needed) Code = fastboot boot twrp-2.8.7.0-bullhead.img and then adb push supersu?

I've done what the op had and I have root with encryption.
Sent from my Nexus 5X using XDA Free mobile app

I also want to agree. I just tried to unlock tethering without full root, but ran into issues. So to fix my issues, I just decided to follow the ops steps and root the phone. After adding the image, I was unable to push supersu due to adb not working in twrp. However, I rebooted the phone and saw the encryption password on boot. Once the os was loaded, I went into settings -> security and noticed the phone was set to encrypted. Looking through the program list, supersu installer was in the list and worked perfectly. Thanks op.
Sent from my Nexus 5X using XDA Free mobile app

How long does the device take to boot up? I've been sitting at the boot animation for a while now.

You can have root access through SuperSU with encryption enabled. I have it running just fine with encryption enabled. What you do have to have turned off is dm-verity. With dm-verity enabled, modification to the system partition are "not allowed".
And Chainfire's modified boot image has 3 main modifications:
1. A modified sepolicy with SELinux provisioning for SuperSU
2. dm-verity turned off
3. forceencrypt for data partition disabled. Basically disabled forced default encryption, but you can still encrypt.

Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?

Camp As A Champ said:
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Click to expand...
Click to collapse
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.

dbrohrer said:
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
Click to expand...
Click to collapse
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?

Camp As A Champ said:
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Click to expand...
Click to collapse
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.

This worked for me too - I tried to:
>adb push supersu.zip /system/
... Then in TWRP install -> select /system/supersu.zip
But this failed for some reason... However, this worked:
>adb sideload supersu.zip
Then reboot, and restore Thanks a lot! Didn't want to give up encryption either...

dbrohrer said:
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
Click to expand...
Click to collapse
Will I be able to do this through TWRP or should I just use ADB to flash the image files? Sorry for all the questions, this is my first nexus phone and I'm getting used to all the new methods
Nevermind, got everything to work, thanks for the help though

Rooted Nexus 6P - Possible to get OTA updates?

I recently unlocked the bootloader and rooted my Nexus 6P and just this evening received an update for the November Security Update. This downloads fine but when the phone reboots to install, it just goes to TWRP and doesn't install.
This is most likely incredibly simple and stupid for me even to ask, but is it possible to install one I've unlocked/rooted?
Any advice will be much appreciated.

You need the stock recovery to take otas Thats why it won't work
Sent from my Nexus 6P using XDA Free mobile app

Before, it initiates an update install. It checks root status. If it finds the device is rooted then it stops OTA install, to prevent any further damage to the phone.

In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Sent from my Nexus 6P using Tapatalk

Thanks for the quick answers guys. Many thanks.

rborg said:
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you have gone as far as unlocking and rooting your phone, then you must have decided to go with some sort of ROM. If you do that, youll actually "typically" get the updates quicker from the developer than OTA. Just saying. And you dont lose your mods.

Does anyone have the stock recovery img handy? Should be easy to get OTA's with flashify that way.

HyperM3 said:
If you have gone as far as unlocking and rooting your phone, then you must have decided to go with some sort of ROM. If you do that, youll actually "typically" get the updates quicker from the developer than OTA. Just saying. And you dont lose your mods.
Click to expand...
Click to collapse
I was hoping to stay stock and use xposed when it is ready. So, no, I haven't gone that far in a long time.
Sent from my Nexus 6P using Tapatalk

The best way to get the ota updates for you would be to download the factory image from Google and Fastboot flash. If you dont wipe user data you should be able to keep most of your settings. You will also need to reflash chainfire's boot Img.

rborg said:
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Click to expand...
Click to collapse
Here is what I do. So long as you do not flash or wipe userdata, this method should maintain all your app data and settings:
1. Download files:
* Latest factory image from: https://developers.google.com/android/nexus/images?hl=en and extract .img files to a folder on your computer with fastboot.
* Modified boot.img from: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 and extract boot.img to the same folder (I usually rename it to modifiedboot.img so I have have the original boot.img and modified images in the same folder).
* Latest version of TWRP from: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976 (direct link: https://dl.twrp.me/angler/) to the same folder
* Systemless SuperSU from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (do not unzip) to /sdcard/download folder on phone
2. Flash .img files using the following commands:
fastboot flash bootloader bootloader.img [using current name of bootloader image - not necessary if no change to bootloader from prior factory image]
fastboot reboot-bootloader
fastboot flash radio radio-angler.img [using current name of radio image - not necessary if no change to radio from prior factory image]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot modifiedboot.img
fastboot flash recovery twrp-2.8.7.x-angler.img [replace x with the current version]
3. Boot into recovery (TWRP), flash SuperSU.zip from /sdcard/download, wipe davlik and regular caches and reboot to system.
Upon reboot, Android will optimize all of your apps, so the first boot will take a while. However, the whole process usually takes me about 20 minutes - perhaps a bit more if I do a TWRP backup before upgrading (recommended).
---------- Post added at 10:25 AM ---------- Previous post was at 10:12 AM ----------
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP

rsmolen said:
Here is what I do. So long as you do not flash or wipe userdata, this method should maintain all your app data and settings:
1. Download files:
* Latest factory image from: https://developers.google.com/android/nexus/images?hl=en and extract .img files to a folder on your computer with fastboot.
* Modified boot.img from: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 and extract boot.img to the same folder (I usually rename it to modifiedboot.img so I have have the original boot.img and modified images in the same folder).
* Latest version of TWRP from: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976 (direct link: https://dl.twrp.me/angler/) to the same folder
* Systemless SuperSU from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (do not unzip) to /sdcard/download folder on phone
2. Flash .img files using the following commands:
fastboot flash bootloader bootloader.img [using current name of bootloader image - not necessary if no change to bootloader from prior factory image]
fastboot reboot-bootloader
fastboot flash radio radio-angler.img [using current name of radio image - not necessary if no change to radio from prior factory image]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot modifiedboot.img
fastboot flash recovery twrp-2.8.7.x-angler.img [replace x with the current version]
3. Boot into recovery (TWRP), flash SuperSU.zip from /sdcard/download, wipe davlik and regular caches and reboot to system.
Upon reboot, Android will optimize all of your apps, so the first boot will take a while. However, the whole process usually takes me about 20 minutes - perhaps a bit more if I do a TWRP backup before upgrading (recommended).
---------- Post added at 10:25 AM ---------- Previous post was at 10:12 AM ----------
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
Click to expand...
Click to collapse
Thanks. This is helpful, even though it makes me feel like a baby. It's sad, considering we old-timers have been flashing **** that, at the time, seemed more complex. Or maybe it didn't. Never bricked a windows CE device. This isn't really 'complex' anyway. Just feels like far too many steps. I want a twrp flashable image, simply.
Sent from my Nexus 6P using Tapatalk

rborg said:
Thanks. This is helpful, even though it makes me feel like a baby. It's sad, considering we old-timers have been flashing **** that, at the time, seemed more complex. Or maybe it didn't. Never bricked a windows CE device. This isn't really 'complex' anyway. Just feels like far too many steps. I want a twrp flashable image, simply.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just use a custom rom and update as it gets updated.
More features, updated more often, flashable.
Easiest way to go.

Phazmos said:
Just use a custom rom and update as it gets updated.
More features, updated more often, flashable.
Easiest way to go.
Click to expand...
Click to collapse
Uhh how is flashing a custom ROM easier than just fastboot flashing system.img and vendor.img?

Cares said:
Uhh how is flashing a custom ROM easier than just fastboot flashing system.img and vendor.img?
Click to expand...
Click to collapse
Uhhh the most obvious answer would be no other peripherals required.

Phazmos said:
Uhhh the most obvious answer would be no other peripherals required.
Click to expand...
Click to collapse
Think about that for a second...you would have needed fastboot already to get a custom recovery onto your phone in the first place. You are flashing an entire ROM versus 2 files so it takes longer already. You'll need to update more files on first boot. Not faster or easier so not sure where your argument comes from.

Cares said:
Think about that for a second...you would have needed fastboot already to get a custom recovery onto your phone in the first place. You are flashing an entire ROM versus 2 files so it takes longer already. You'll need to update more files on first boot. Not faster or easier so not sure where your argument comes from.
Click to expand...
Click to collapse
Sorry, but if ya think it's slower or harder to download a rom and flash it, I don't know what to tell ya.

I really just want stock + xposed. So, I should really be looking for flashable security updates. Rooting doesn't necessarily imply that someone wants a custom ROM. *Not* needing a custom ROM to customize the OS is what xposed is all about. Making this choice doesn't mean we are idiots.
Sent from my Nexus 6P using Tapatalk

rborg said:
I really just want stock + xposed. So, I should really be looking for flashable security updates. Rooting doesn't necessarily imply that someone wants a custom ROM. *Not* needing a custom ROM to customize the OS is what xposed is all about. Making this choice doesn't mean we are idiots.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Xposed is very unstable. Most of the time causes reboots.

rsmolen said:
[/COLOR]
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
Click to expand...
Click to collapse
Did anyone try this? Did it work? I am rooted but I have stock recovery (instead of flashing TWRP I just booted into it with fastboot for the SU install). Do I still need to flash the stock boot and recovery img's? I'm not sure what changes when SU is intalled. Thanks!
Edit - Does the "full unroot" button on SuperSU work? Is this all I would need to do since I did not permanently flash TWRP?

just did this. works perfectly. all data still there.
thanks!!!

New update to fix voLTE 911 bug...

So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
EDIT: Link to the zip
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA

I don't believe so.
In the past you either had to go back to stock or wait on someone to create a compatible update for rooted devices.

Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.

Can you add what variant and build you are using before the update? Also the build afterwards?

KapilFaujdar said:
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Click to expand...
Click to collapse
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?

gghose said:
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
Click to expand...
Click to collapse
Yeah I can't find anything in that folder either.

I received the update and applied it. I am not rooted.
I have the XT1687 model.
My current build number is NPN25.137-35

My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?

bvsbutthd101 said:
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
Click to expand...
Click to collapse
If you have systemless supersu, you should just be able to apply the update after reverting to stock recovery.

So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA

glight0 said:
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
Click to expand...
Click to collapse
OK, so I tried flashing recovery.img from stock firmware build 33. But the OTA update will not install, instead I get an error after downloading and rebooting (red triangle at recovery mode).
So I tried fully reverting to stock firmware but I decided to skip over erasing userdata. Afterward the OTA downloaded and installed successfully. Keeping userdata does not seem to have caused an issue.
My problem now though is how to get root back without having to wipe userdata after re-flashing TWRP.
Or is this not possible and if I want to root I must first wipe userdata so that TWRP can read internal memory?

bvsbutthd101 said:
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).

If your using a custom recovery flash the stock recovery, then go to the stock recovery and using your computer flash using adb sideboard command. I assume you already know how to do this. Hope that helps.
gghose said:
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
Click to expand...
Click to collapse

I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone
There's a workaround to disable the "advanced LTE" or whatever it was called, so I did that. But in the meantime until a more "user friendly" means of updating is available, is there a way I can get rid of this nag screen? Way back on an earlier device (Samsung Charge?) I remember manually editing a "build.prop" file or something to match the latest version so I wouldn't keep getting the software update nag. Is there something that will do the same here, or is there a system app I can freeze in TiB?
My best guess is freezing "Moto Actions 03.022.1.4-N" because it's showing "(updated)" on the side.

rellim113 said:
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone .
Click to expand...
Click to collapse
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip

glight0 said:
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
Click to expand...
Click to collapse
Strange, reflashed the stock recovery and adb can't see it (adb devices returns nothing). And when trying to install it via the normal OTA way, the stock recovery tries to install but ends with an error.

That's what happened to me when I tried reverting to stock recovery and then trying to install update from phone Settings app.
I ended up having to revert to stock rom to get ota to apply with settings app. But now I am trying to root again but after installing TWRP data is encrypted again. So looks like I will have to wipe data before re-rooting.