Database Develop

Will Nexus 6 get OTA updates if rooted and custom recovery is installed?

I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
shelooga said:
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well
Click to expand...
Click to collapse
sheloga is correct. You'd have to revert back to full stock or wait for someone to make a flashable zip.

Can't you just flash the stock recovery and take the OTA? Or do you have to fully unroot and reflash the factory image?

I would like to pay close attention time to this thread because that is one is the main questions that I have. I hear so many different solutions towards this. I usually wait for a flashable zip but I would want to see someone either wrote a write up or make a video. Subscribed.

My understanding (from looking at the lollipop OTA updater-script) is it checks EVERY file for changes, including other partitions. You must be 100% stock with nothing extra in system (SuperSU apk or busybox etc).

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.

BLUF: wait until OTA is made available in a recovery flash method. 90% of the time the OTA updates are patching security holes and other less important features.
Having been with a handful of different android devices in the past several years, I've always gone the route of flashing from recovery vs. OTA.
The LG G3 for example had an OTA just recently that broke rooting. It was fixed by a Dev, but that's the only update found in OTA.
Sent from my Nexus 6 using XDA Free mobile app

Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.

simms22 said:
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.
Click to expand...
Click to collapse
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?

wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
no thoughts.
i just flash aosp hours after it appears there. or just wait for @rascarlo to add it to his rom, then i flash

HyperM3 said:
Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
After Android 5.0, you can't sideload the OTA file if you have made any changes to the system partition. You need to be completely stock to take OTA. You can just download the new factory images and extract the various img files from it and just flash those manually in ADB, thereby overwriting your modified system partition with the new factory system image (you can skip overwriting the userdata if you want to preserve your data). No need to revert back to stock (old image) and then take OTA - unnecessary step.

HyperM3 said:
Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?

gwojo22 said:
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?
Click to expand...
Click to collapse
From google
https://developers.google.com/android/nexus/images

hlxanthus said:
From google
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately

waqar.qu said:
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately
Click to expand...
Click to collapse
You need to install ADB and fastboot. After that, you can use the 'fastboot' command directly from Terminal. I've found that the easiest way to update Lollipop on my Nexus 6 is to:
Download image from Google
Decompress the archive, AND the second archive which was contained within the first one. Note: The recovery, boot, and system images are in the second archive.
Open Terminal, change directory to the extracted folder, and run these commands (they skip overwriting the userdata partition):
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
fastboot reboot-bootloader (VERY IMPORTANT TO DO THIS STEP)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
You need to restore root at this point; you can use these instructions if you're unfamiliar with the procedure.

[Q] Rooted 5.0.1, OTA update to T-mo 5.1 offered, failed. How to proceed?

Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!

a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.

So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.

RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/

Any outstanding reason to take the April update?

I updated my N6 when I got it a few weeks ago, then unlocked loader, installed TWRP and rooted with NRT.
I am pretty darn happy with the way everything works as it is right now.
Yesterday, my phone downloaded the April update and prompted me to install it.
As I understand, you must flash factory and unroot to take the updates.
That said, is there any overwhelming reason to go through all that for (what seems) a minor update?
I am tempted to just wait for N to be finalized and flash the new image once available and "keep on keeping on."
A lot of you are worlds more experienced than I am and I am interested in your opinions.
Should I or shouldn't I?
TIA.

There are security updates... If you want them or not is up to you.
What I and many others do (rooted, TWRP, custom kernel) is to use the latest factory image and update by flashing individual parts of it through fastboot. In the update from march to april (MMB29V to MOB30D) I only flashed boot.img, radio.img and system.img. The rest was untouched or I didn't want to update it (i.e. custom recovery).
Check out this thread: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Follow that to set up your workspace and follow method 2 when flashing. Only flash the parts you want, but always leave out userdata.img unless you want to wipe your data. Also skip the factory reset in the end...
You will need to reroot when done, but that is just a matter of booting into TWRP (and that you should do anyway) and flashing the SuperSU zip.

nunjabusiness said:
... I am interested in your opinions...
Click to expand...
Click to collapse
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.

NLBeev said:
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.
Click to expand...
Click to collapse
Interesting idea. I am encrypted too, does that matter?

NLBeev said:
There is a thread of Danvdh. He makes a Stock lite ROM after every update incl. root access.
Now you have TWRP you could monthly download and flash the new lite ROM.
Click to expand...
Click to collapse
i am using Danvdh's Stock Lite ROM MMB29X. he has not updated to MOB30D. now say if i wanted MOB30D can i do the below steps?
flashing individual parts of it through fastboot
flashed boot.img, radio.img and system.img.

No reason at all.....its like saying you have some pirated version on Windows 10 and you would have to reinstall windows 8.1 to take a 19kb security patch. We have been running these OS with intentional security breaches (root) for many years..... Y start to worry about it now?
Additionally there will probably never again be a feature released that would necessitate such drastic measures. IMO.....sall incremental anymore.

so your opinion is to just roll with Danvdh's updates as they come?

iluvatrix said:
i am using Danvdh's Stock Lite ROM MMB29X. he has not updated to MOB30D. now say if i wanted MOB30D can i do the below steps?
flashing individual parts of it through fastboot
flashed boot.img, radio.img and system.img.
Click to expand...
Click to collapse
There only a few changes (bootloader, modem).
Better wait for the May update of Danvdh.
I think you can flash the new boot, radio and system. But that includes the bloatware that Danvdh will remove.

How to update R1 to the latest OTA Update?

Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!

KyleStilkey said:
Hey All,
I'm looking for some help nito update this device to the latest OTA update. I have installed TWRP 3.0.2.0 that came with the dirtycow method. The device found the latest updated released in the past few days but when going to install it, it brings up the TWRP (which is how it should install). Now I don't mind if I can't grab this latest version due to whatever reason, but how would I go about updating the device? Currently it's running the stock version 6.1 6/17/2016.
Sorry if this has been answered somewhere, but still kinda new with Android devices and the whole rooting process. I'd like to be able to keep TWRP if at all possible and keep this device updated. Also I saw there was a updated TWRP released, how would I go about updating the recovery?
Thanks a lot for the help anyone can give!
Click to expand...
Click to collapse
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here

mrmazak said:
As long as you have twrp installed, you can install the modified update 8.3 i just finished.
==>>it is here
Click to expand...
Click to collapse
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.

KyleStilkey said:
Already tried it and it doesn't work. She uses the phone to play Pokemon Go and sadly the modified version you've made gives the error that the device or software is not supported. I believe this is due to the method you are using to remove the ads and custom changes made to the ROM, which I don't personally care if the phone has them or not. I'm wanting to install OTA updates without any heavy modifications made, just the ability to keep TWRP but have an updated phone.
Click to expand...
Click to collapse
Will be redoing the patch again and making not pre-rooted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.

mrmazak said:
Will be redoing the patch again and making not predicted version. But if your app is not working on the modified 7.4.2 there is nothing I can do.
Click to expand...
Click to collapse
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.

KyleStilkey said:
I see V8 but do not see a 7.4.2 on there.
EDIT: Nevermind I found it, will try the modified 7.4.2 and get back to you.
Click to expand...
Click to collapse
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom

mrmazak said:
Non-rooted rom finished. uploaded to android file host.
Link and description in my other post.
==>>Unrooted rom
Click to expand...
Click to collapse
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.

KyleStilkey said:
I want to say thank you a lot, this worked wonderfully! Only issue is Google Plus doesn't work (not a huge deal for the wife) but everything else is working great!
One last question, what is the recommended TWRP to use with this phone, I currently have the 3.0.2.0 Vampire version installed.
Click to expand...
Click to collapse
I have seen it mentioned that Google + does not work on 8.3 in general not just this modified one.
That recovery is the one I use and has advantage over the other one (lopestom's versio) in that in recovery you can use external sdcard and also mtp connection.

[ROM] TWRP Flashable Stock Builds

*FILES REMOVED UNTIL FURTHER NOTICE, AS USERS ARE HAVING CONNECTION ISSUES AFTER FLASHING*
Here are the latest stock retail builds packaged into TWRP flashable format.
You can use these files to upgrade and downgrade stock builds safely, as they do not include gpt (partition table) or bootloader.
Usage is simple:
Copy file to device storage
Reboot into TWRP
Flash zip
Profit!
Please remember to hit the "THANKS" button if these files help you!
NOTES:
Dm-verity and force encryption have been disabled in the boot images, and unlocked device/dm-verity warnings have been disabled in the logo images.
Do NOT attempt to apply standard OTAs over these builds; they will fail.
If you get an OTA for a build that's not yet available, please share it!
How To Pull An OTA update:
Download the update
Power off and boot into TWRP
Go to Advanced > File Manager
Navigate to /cache
There will be a Blur_Version_blah.zip file
Copy to internal storage or sdcard
Copy from internal storage or sdcard to PC (optional, recommended)
Upload to Drive, Mega, or whichever file sharing service you choose
Share the link!
If you're rooted/modded and want to prevent potential auto updating, you can wipe /cache to remove the file.
DOWNLOADS:
CREDITS:
Android
Lenovorola
@tal.aloni for SparseConverter posted here:
https://forum.xda-developers.com/showthread.php?t=2749797
@erfanoabdi for imgpatchtools posted here:
https://forum.xda-developers.com/an...ev-img-patch-tools-sdat2img-ota-zips-t3640308
@A.S._id for img repack tools posted here:
https://forum.xda-developers.com/showthread.php?t=2600364
@xpirt for sdat tools posted here:
https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952

Please tell me these actually work. I am desperate for any ROM for the XT1710-01 variant. I will go as far as paying.

Thank you so much,it works on xt1710-08 well,just backup EFS in trwp just in case of no signal,after flash this rom in twrp,restore EFS and enjoy it.Also,you can root it with flashing magisk

So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Are these 7.1.2 yet?
THANKS

KeepingItCuttingEdge said:
Are these 7.1.2 yet?
Click to expand...
Click to collapse
It's still 7.1.1. See the attached screenshot.

KeepingItCuttingEdge said:
So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Click to expand...
Click to collapse
Any response to these questions, OP?
I am in the same boat.

New builds are up
KeepingItCuttingEdge said:
So the 118-19-6 is good for the XT1710-01 Retail directly from Motorola?
I'm on the stock 118-9 version, Security Update of July 1st, and Android 7.1.1. No OTA update available when I check.
Are these 7.1.2 yet?
THANKS
Click to expand...
Click to collapse
There is no 118-9 version.
pizza_pablo said:
Any response to these questions, OP?
I am in the same boat.
Click to expand...
Click to collapse
There is no 118-9 version.
If I knew, I would answer.
These files are are made from official fastboot files shared by @Junior Passos.
Check out his afh page for albus here: https://androidfilehost.com/?a=show&w=files&flid=195559

Q9Nap said:
New builds are up
There is no 118-9 version.
There is no 118-9 version.
If I knew, I would answer.
These files are are made from official fastboot files shared by @Junior Passos.
Check out his afh page for albus here: https://androidfilehost.com/?a=show&w=files&flid=195559
Click to expand...
Click to collapse
This is from a US unlocked Z2 Play.
The model number is XT1710-01.
Are the listed firmware versions proper for my model?

pizza_pablo said:
This is from a US unlocked Z2 Play.
The model number is XT1710-01.
Are the listed firmware versions proper for my model?
Click to expand...
Click to collapse
Dude, what did I just say? I DON'T KNOW.
I'm sure it will work, but it may take you off your official upgrade path.
And with no fastboot file available for your current software version, I would take a full TWRP backup and copy to pc for safekeeping before trying anything.
Welcome to Flashing 101

Q9Nap said:
*removed*
Due to lack of interest.
Click to expand...
Click to collapse
Noooo, please restore! I've been using the steps and files provided to get rid of the annoying "an update is available" notifications on my rooted XT1710-09!
And yesterday a new one has appeared...

Indeed please restore it can't hurt having it up here

We don't even have custom roms, this is the closest we can get for now. Please post more builds!

Q9Nap said:
*removed*
Due to lack of interest.
Click to expand...
Click to collapse
I'm going to buy my z2 play bike at the end of the year and it's a shame not to have an updated lite rom. Probably you should be doing a good job.
It would be nice to have a rom lite for ALL MODEL with deodex, delete more apps OTA / CCC / CCE, OTA process is deleted, remove a lot of the background services collect and send data on the type of phone (DropBox, MotoCare , MotoConntect, Drive and etc).

ilgrosso said:
Noooo, please restore! I've been using the steps and files provided to get rid of the annoying "an update is available" notifications on my rooted XT1710-09!
And yesterday a new one has appeared...
Click to expand...
Click to collapse
Lars1703 said:
Indeed please restore it can't hurt having it up here
Click to expand...
Click to collapse
f.baio said:
We don't even have custom roms, this is the closest we can get for now. Please post more builds!
Click to expand...
Click to collapse
Guth13 said:
I'm going to buy my z2 play bike at the end of the year and it's a shame not to have an updated lite rom. Probably you should be doing a good job.
It would be nice to have a rom lite for ALL MODEL with deodex, delete more apps OTA / CCC / CCE, OTA process is deleted, remove a lot of the background services collect and send data on the type of phone (DropBox, MotoCare , MotoConntect, Drive and etc).
Click to expand...
Click to collapse
Updated the OP with the latest retail build NPSS26.118-19-11.
Unlike most carrier unlocked moto devices, which tend to have multiple upgrade paths for different regions, the albus seems to have only one upgrade path for the retail variant so far.
Someone correct me if I'm wrong, and please post the OTA files for alternate upgrade paths if you have them; directions are in the OP.
I have linked the tools I use to create these at the bottom of the OP.
You can use these tools and info in their threads to reverse engineer the stock build and modify it to your liking.

Thank you so much now i can have the latest update for my rooted moto thanks a lot

I have an unlocked Moto Z2 Play XT1710-01 and this is the latest update I am seeing:
NPSS26.118-24-6
https://drive.google.com/file/d/1IUG-o0HWCgFGyNwX3aWzd4oqhHAzK25T/view?usp=sharing
EDIT:
I think i now understand the file name structure and that it includes the date. My updated was from 6/26 and your updated was from 11/19. I just updated to the newest. Thank you for doing this!

sirkuttin said:
I have an unlocked Moto Z2 Play XT1710-01 and this is the latest update I am seeing:
NPSS26.118-24-6
https://drive.google.com/file/d/1IUG-o0HWCgFGyNwX3aWzd4oqhHAzK25T/view?usp=sharing
EDIT:
I think i now understand the file name structure and that it includes the date. My updated was from 6/26 and your updated was from 11/19. I just updated to the newest. Thank you for doing this!
Click to expand...
Click to collapse
The file name structure doesn't have anything to do with the date it was made afaik.
That update is for "albus_c" and not "albus". I'm not sure what the difference is.
Apparently, there are multiple upgrade paths after all.
Flashing this will likely take you off your current upgrade path, but it is safe, so you can always go back to your previous stock build if you want.

Q9Nap said:
Updated the OP with the latest retail build NPSS26.118-19-11.
Unlike most carrier unlocked moto devices, which tend to have multiple upgrade paths for different regions, the albus seems to have only one upgrade path for the retail variant so far.
Someone correct me if I'm wrong, and please post the OTA files for alternate upgrade paths if you have them; directions are in the OP.
I have linked the tools I use to create these at the bottom of the OP.
You can use these tools and info in their threads to reverse engineer the stock build and modify it to your liking.
Click to expand...
Click to collapse
Thanks @Q9Nap!
I've attempted to follow your instructions about applying OTA via TWRP, but that fails because of mismatching thumbprint - which sounds odd since I've downloaded and attempted to flash on exactly the same device...
Anyway, I'll try soon to flash the full stock ROM, after download from the link you've re-posted.

New update NOT PATCHED YET NPSS26.118-19-14
https://drive.google.com/file/d/1df6c3cWDU0mxt__mFhL-GiqzQzLWdKrD/view?usp=drivesdk
Contains November security updates
This has not yet been patched please wait for OP to do So

@Q9Nap can you put a tutorial on here telling us how to make a update flashable