Below are a list of all known Nexus 5 OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file on my website, http://randomphantasmagoria.com, in case Google pulls it down in the future.
OTA Updates - hammerhead
Current firmware: Android Android 6.0, Build MRA58N
MRA58N from MRA58K - https://android.googleapis.com/pack...74e.signed-hammerhead-MRA58N-from-MRA58K1.zip
------------------------------------------------
MRA58K from LMY48M - https://android.googleapis.com/pack...402b.signed-hammerhead-MRA58K-from-LMY48M.zip
------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack...ed-hammerhead-LMY48M-from-LMY48I.79fa6114.zip
------------------------------------------------
LMY48I from LMY48B - https://android.googleapis.com/pack...ed-hammerhead-LMY48I-from-LMY48B.1207c77d.zip
------------------------------------------------
LMY48B from LMY47D - https://android.googleapis.com/pack...rhead-LMY48B-from-LMY47D-restricted-radio.zip
LMY48B from LMY47D - https://android.googleapis.com/pack...d-hammerhead-LMY48B-from-LMY47D-fullradio.zip (Use this if the one above won't flash)
LMY48B from LMY47I - https://android.googleapis.com/pack...rhead-LMY48B-from-LMY47I-restricted-radio.zip
-------------------------------------------------
LMY47I from LRX21O - http://android.clients.google.com/p...d-ota-LMY47I-from-LRX21O-radio-restricted.zip
LMY47I from LRX21O - http://android.clients.google.com/p...mmerhead-ota-LMY47I-from-LRX21O-fullradio.zip (Use this if the one above won't flash)
LMY47I from LRX22C - http://android.clients.google.com/p...d-ota-LMY47I-from-LRX22C-radio-restricted.zip
LMY47I from LRX22C - http://android.clients.google.com/p...mmerhead-ota-LMY47I-from-LRX22C-fullradio.zip (Use this if the one above won't flash)
-------------------------------------------------
LMY47D from LRX21O - http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip
LMY47D from LRX22C - http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip
-------------------------------------------------
LRX22C from KTU84P - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip
LRX22C from KTU84Q - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-KTU84Q.a7e2eebf.zip
LRX22C from LRX21O - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip (Original, may not flash for most people)
LRX22C from LRX21O - http://android.clients.google.com/p...rhead-LRX22C-from-LRX21O.radio-restricted.zip (Attempt to fix #1, may or may not flash.)
LRX22C from LRX21O - http://android.clients.google.com/p...d-hammerhead-LRX22C-from-LRX21O-fullradio.zip (This should flash for everyone)
-------------------------------------------------
LRX21O from KTU84P - http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
LRX21O from KTU84Q - http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
-------------------------------------------------
KTU84Q from KOT49H - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KOT49H.9cad7d26.zip
KTU84Q from KTU84M - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KTU84M.21e068a8.zip
KTU84Q from KTU84P - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KTU84P.a32b2f45.zip
-------------------------------------------------
KTU84P from KTU84M - http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip
-------------------------------------------------
KTU84M from KOT49H - http://android.clients.google.com/p...ed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
-----------------------------------------------
KOT49H from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KFS78N.2a79b8f6.zip
KOT49H from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KQS81M.f3dc7925.zip
KOT49H from KRT16M - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KRT16M.b3d1f307.zip
KOT49H from KOT49E - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KOT49E.537367d5.zip
----------------------------------------------
KOT49E from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KFS78N.777bedc5.zip
KOT49E from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KQS81M.79448efe.zip
KOT49E from KRT16M - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
----------------------------------------------
KRT16M from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KRT16M-from-KFS78N.c6defefd.zip
KRT16M from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KRT16M-from-KQS81M.ea9d0ad5.zip
SPECIAL THANKS
Nevvty
fevan
El Daddy
TheManii
switch85
xdatastic
GabrielGPP
emuneee
kvidli
EthanFirst
HackerWolf
mazsuper
msinkovich
zero_x3
oldblue910 said:
As with so many Nexus devices in the past, I'm going to be tracking OTA update URLs for the Nexus 5 both in this thread and on randomphantasmagoria.com. The first post will be updated with each OTA and if you get an OTA update on your Nexus 5 that I don't have listed here, please get the URL and post it here for the community!
VERY IMPORTANT
When the Nexus 5 launches, it will most likely have an immediate OTA update available the first time you turn it on. Please DO NOT accept this OTA update without getting some information for me first! Too often, people get excited when they turn on their device for the first time and see an update. They accept the update and before we know it, we end up losing all data on the firmware that the device ships with.
When you get your Nexus 5 and turn it on for the first time, please gather the following info before applying that out-of-the-box OTA update:
1. The values of ro.build.fingerprint and ro.build.date.utc from /system/build.prop.
2. The baseband version (can be found in Settings | About Phone)
3. The bootloader version (can be found by booting into fastboot mode, the bootloader version will be displayed on screen).
4. The filename for the out-of-the-box OTA ZIP file (if any). This file can be found in /cache or you can check logcat for the full URL. Either one works.
If you need help with any of this, I'll be more than happy to assist! After we have this information locked down, feel free to apply the OTA update out of the box and enjoy your new device!!
Click to expand...
Click to collapse
Thank you, added you to the index.
subscribing. nice to see oldblue here as well
oldblue910 said:
As with so many Nexus devices in the past, I'm going to be tracking OTA update URLs for the Nexus 5 both in this thread and on randomphantasmagoria.com. The first post will be updated with each OTA and if you get an OTA update on your Nexus 5 that I don't have listed here, please get the URL and post it here for the community!
VERY IMPORTANT
When the Nexus 5 launches, it will most likely have an immediate OTA update available the first time you turn it on. Please DO NOT accept this OTA update without getting some information for me first! Too often, people get excited when they turn on their device for the first time and see an update. They accept the update and before we know it, we end up losing all data on the firmware that the device ships with.
When you get your Nexus 5 and turn it on for the first time, please gather the following info before applying that out-of-the-box OTA update:
1. The values of ro.build.fingerprint and ro.build.date.utc from /system/build.prop.
2. The baseband version (can be found in Settings | About Phone)
3. The bootloader version (can be found by booting into fastboot mode, the bootloader version will be displayed on screen).
4. The filename for the out-of-the-box OTA ZIP file (if any). This file can be found in /cache or you can check logcat for the full URL. Either one works.
If you need help with any of this, I'll be more than happy to assist! After we have this information locked down, feel free to apply the OTA update out of the box and enjoy your new device!!
Click to expand...
Click to collapse
Any reason your not just requesting a system dump of the out of the box firmware?
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Any reason your not just requesting a system dump of the out of the box firmware?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good question. Basically it comes down to the fact that system dumps aren't official and you can never be guaranteed that what you're getting is pure and unmodified. Because of that, they're pretty much useless for me.
For a shipping firmware that just gets updated upon first boot, I just want the info. It's much faster for someone to just type out the info I need rather than dumping the system, zipping it, uploading it, downloading it and hitting a hex editor to get the bootloader and baseband versions from the dumps.
I'm sure someone will post a system dump, but unless it's an OTA or a set of official fastboot images from Google, I don't really have any use for them.
Sent from my GT-I9505G using Tapatalk
Gotcha
Sent from my XT1080 using XDA Premium 4 mobile app
Alright guys, the Nexus 5 order pages are live. If anyone buys one, PLEASE get the info I need (listed in the first post) before applying the out-of-the-box OTA update. Thank you!!
oldblue910 said:
Alright guys, the Nexus 5 order pages are live. If anyone buys one, PLEASE get the info I need (listed in the first post) before applying the out-of-the-box OTA update. Thank you!!
Click to expand...
Click to collapse
Will do. Just ordered my white 32GB with 2 day shipping. I live in WV and know from the N4 release that they have a facility in Lexington, KY where it will most likely ship from.
*subscribing*
wvcadle said:
Will do. Just ordered my white 32GB with 2 day shipping. I live in WV and know from the N4 release that they have a facility in Lexington, KY where it will most likely ship from.
*subscribing*
Click to expand...
Click to collapse
Thank you very much. Much appreciated. Also, once you get that info, apply the out-of-the-box OTA update and then get the same info for the updated firmware as well, please!
oldblue910 said:
Thank you very much. Much appreciated. Also, once you get that info, apply the out-of-the-box OTA update and then get the same info for the updated firmware as well, please!
Click to expand...
Click to collapse
Will do.
wvcadle said:
Will do.
Click to expand...
Click to collapse
You're the man. Thanks, dude!
https://support.google.com/nexus/answer/3507867?hl=en&ref_topic=3415518 said:
The new Nexus 5 comes with Android 4.4 pre-installed. Note that you will be prompted to install a small update when you set up your device.
Click to expand...
Click to collapse
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
TheManii said:
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
Click to expand...
Click to collapse
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
efrant said:
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
Click to expand...
Click to collapse
Same here
Sent from my Nexus 10 using Tapatalk 4
efrant said:
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
Click to expand...
Click to collapse
Well that would require waiting a custom rec to be released first, generally people here are so impatient they'll flash a rom and when they realize it's a dos 4.0 image they'll just come and complain because no factory images are available
---------- Post added at 04:09 PM ---------- Previous post was at 03:36 PM ----------
https://groups.google.com/forum/?fromgroups#!topic/android-building/JVLaFRoJxFk said:
the kitkat release build (KRT16M) for the Nexus 5--which will be tagged with android-4.4_r1
Click to expand...
Click to collapse
Whatever the initial rom is, it will likely OTA to KRT16M
TheManii said:
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
Click to expand...
Click to collapse
Is it possible to set up the device with no network connection and avoid any initial OTA update?
I'm thinking not, first post states it could be pre-downloaded and in the cache folder...
koriflame said:
Is it possible to set up the device with no network connection and avoid any initial OTA update?
Click to expand...
Click to collapse
Possibly...you can definitely try. :good:
Sent from my Galaxy S4 Google Play Edition using Tapatalk
My N5 will be showing up Monday afternoon. I'll pull the OTA link if it hasn't been posted by then.
El Daddy said:
My N5 will be showing up Monday afternoon. I'll pull the OTA link if it hasn't been posted by then.
Click to expand...
Click to collapse
And all the info on the shipping firmware!! Keep in mind that, like the N7 2013 WiFi, there may be two OTAs out of the box. The first one will be forced during the setup screen. That one will convert the ROM from dev-keys to release-keys, then once that one is in and you set up your device, it'll probably get a normal OTA to KRT16M.
I hope there's a custom recovery available by Monday. Otherwise we may lose that initial devkeys->releasekeys OTA because it's forced.
If there is a custom recovery, make sure you don't boot the system normally the first time. Instead, the first time you turn it on, boot it into fastboot mode (power + volume down). Note the bootloader and baseband versions on screen. At that point, unlock the bootloader, boot the custom recovery (use fastboot boot recovery.img so you don't overwrite the stock recovery), and do a nandroid. Provide that Nandroid backup, please!
Once that's done, stay in the custom recovery and do an adb shell. Dump the radio if you can. I can help you with that if you don't know how.
After that, boot her up normally, accept the forced OTA and after it applies, DO NOT let it boot up again. Once it reboots, hold down volume down as it reboots so it'll go back into fastboot mode. Note if the bootloader version changed. Boot your custom recovery again (use fastboot boot) and this time do an adb pull on the log files in /cache/recovery. The devkeys->release keys OTA filename should be in there. Post that.
After that, boot her up, set her up, and get the OTA link to the KRT16M OTA, and then tell us the new baseband and bootloader versions for KRT16M. Thanks everyone for offering to help. If there is a custom recovery by Monday that'll be awesome. If not, we may lose the devkeys->releasekeys OTA file. :/
Sent from my Galaxy S4 Google Play Edition using Tapatalk
oldblue910 said:
And all the info on the shipping firmware!! Keep in mind that, like the N7 2013 WiFi, there may be two OTAs out of the box. The first one will be forced during the setup screen. That one will convert the ROM from dev-keys to release-keys, then once that one is in and you set up your device, it'll probably get a normal OTA to KRT16M.
I hope there's a custom recovery available by Monday. Otherwise we may lose that initial devkeys->releasekeys OTA because it's forced.
If there is a custom recovery, make sure you don't boot the system normally the first time. Instead, the first time you turn it on, boot it into fastboot mode (power + volume down). Note the bootloader and baseband versions on screen. At that point, unlock the bootloader, boot the custom recovery (use fastboot boot recovery.img so you don't overwrite the stock recovery), and do a nandroid. Provide that Nandroid backup, please!
Once that's done, stay in the custom recovery and do an adb shell. Dump the radio if you can. I can help you with that if you don't know how.
After that, boot her up normally, accept the forced OTA and after it applies, DO NOT let it boot up again. Once it reboots, hold down volume down as it reboots so it'll go back into fastboot mode. Note if the bootloader version changed. Boot your custom recovery again (use fastboot boot) and this time do an adb pull on the log files in /cache/recovery. The devkeys->release keys OTA filename should be in there. Post that.
After that, boot her up, set her up, and get the OTA link to the KRT16M OTA, and then tell us the new baseband and bootloader versions for KRT16M. Thanks everyone for offering to help. If there is a custom recovery by Monday that'll be awesome. If not, we may lose the devkeys->releasekeys OTA file. :/
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
Hmm, I didn't know about the forced OTA during setup. Does it reboot the device or somehow just switch the keys?
Anyway, I'll do what I can. Hopefully, I can keep my excitement in check and remember to do all these things!
Related
Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter
If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.
pcrussell50 said:
Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter
Click to expand...
Click to collapse
Buff McBigstuff said:
If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.
Click to expand...
Click to collapse
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.
Buff McBigstuff said:
If I'm not mistaken they normally do otas before images. You might be the first one to get this one. Get the url.
Click to expand...
Click to collapse
hmmm, not sure how to get the url. the message was a system message, not an email with a link. the message says "Android 5.1.1 System Update Downloaded and Verfied..." i'm rooted with root permissions on ES file explorer, i can look for the ota but i'm not sure where they are kept after they are downloaded.
-peter
cam30era said:
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.
Click to expand...
Click to collapse
This was cut and pasted from the google website list of images about a minute and a half ago. can you tell me which one is 5.1.1 for att:
5.0 (LRX21O) Link af4520213c1a3e2b3dd811aef030b87b e028f5eab0952d0df60c63d6095b56c1c6f8e474
5.0.1 (LRX22C) Link a95f291164b5b438b5fc9e77c222d703 ff173fc66eca5a27b34ae28a9b69f9ad7f4d3b80
5.1.0 (LMY47D) Link 4d99d16bae3c5a638268731a5d27062e 6c44d4021142ffaa2197fb1308996a8846a79e26
5.1.0 (LMY47E) Link 7c50606b7d68ddd1b8a81d544ec59aff cf3131641c2bda2eba54bcc0108ce0325327f58e
5.1.0 (LMY47I) Link d6e750e58938de3b8516a4718c491d9c c8afc588e44ec087e8b98c1d6ed3ed565a9b9644
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
Click to expand...
Click to collapse
cuz if LMY47Z is for AT&T too, the "(For Sprint, USC ONLY)" bit was making me think otherwise.
-Peter
pcrussell50 said:
This was cut and pasted from the google website list of images about a minute and a half ago. can you tell me which one is 5.1.1 for att:
Code:
5.0 (LRX21O)Linkaf4520213c1a3e2b3dd811aef030b87be028f5eab0952d0df60c63d6095b56c1c6f8e474
5.0.1 (LRX22C)Linka95f291164b5b438b5fc9e77c222d703ff173fc66eca5a27b34ae28a9b69f9ad7f4d3b80
5.1.0 (LMY47D)Link4d99d16bae3c5a638268731a5d27062e6c44d4021142ffaa2197fb1308996a8846a79e26
5.1.0 (LMY47E)Link7c50606b7d68ddd1b8a81d544ec59affcf3131641c2bda2eba54bcc0108ce0325327f58e
5.1.0 (LMY47I)Linkd6e750e58938de3b8516a4718c491d9cc8afc588e44ec087e8b98c1d6ed3ed565a9b9644
5.1.0 (For T-Mobile ONLY) (LMY47M)Link0469ca2018c923498cc603baae4fd6485228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z)Linkc8fe950ad9e861120a1074825b92cfba33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E)Link9ea32a7ff1751afa2a16214ac23ef000b542b88a0ad478110f9f111dd32b62a1cb65b9d5
-Peter
Click to expand...
Click to collapse
There is only one LMY47Z. It says "For Sprint and USC only". Same build AT&T is pushing via OTA.
At&t rolled out the ota for at&t the zip is already available on xda for a few days now I sideloaded it two days ago. The factory image has not yet been posted on Google's site.
Edit: I wouldn't use the image that is posted on Google because even though it has the same build number the boot.img and radio are most likely different.
manup456 said:
At&t rolled out the ota for at&t the zip is already available on xda for a few days now I sideloaded it two days ago. The factory image has not yet been posted on Google's site.
Edit: I wouldn't use the image that is posted on Google because even though it has the same build number the boot.img and radio are most likely different.
Click to expand...
Click to collapse
I installed the OTA. Fastboot flashed back to 47D. Then after a few days flashed the 47Z factory image. They are identical. Same boot.img and same radio.
cam30era said:
I installed the OTA. Fastboot flashed back to 47D. Then after a few days flashed the 47Z factory image. They are identical. Same boot.img and same radio.
Click to expand...
Click to collapse
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.
manup456 said:
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.
Click to expand...
Click to collapse
Yes, same 101R radio. No idea why Google identifies things like they do.
i am rooted, but with stock recovery and have not edited any system files. can i go ahead and install this OTA, since it's already downloaded and verified according to the system updater?
-peter
pcrussell50 said:
i am rooted, but with stock recovery and have not edited any system files. can i go ahead and install this OTA, since it's already downloaded and verified according to the system updater?
-peter
Click to expand...
Click to collapse
you are rooted. just that in itself changes system files silly :silly:
cam30era said:
AT&T is pushing LMY47Z via OTA. Factory image file has been available for some time on the Google website.
Click to expand...
Click to collapse
simms22 said:
you are rooted. just that in itself changes system files silly :silly:
Click to expand...
Click to collapse
i had a feeling... thanks for confirming. i thought maybe just a root without any other changes might be like renaming the att splash so it doesn't happen on bootup.
-peter
AT&T 5.1.1 system update OTA, whats preventing the install?
manup456 said:
So you have this radio?
Edit: I ask because why would they put for sprint only on google's image download site. Kinda makes no sense to me at all, but you could be 100% correct I never flashed the image files off google's site.
Click to expand...
Click to collapse
pcrussell50 said:
Got 5.1.1 system update message but I'm on att? And when I check the list of stock android images, there is no 5.1.1 for att. Is it possible they are pushing ota's before they make the new image available to developers? Sounds odd to me.
I'm also rooted (but with stock recovery), so it sounds like I can't do the ota? I also have a Fi request out there. Or can I? I'm rooted but I haven't changed any system files. Can I do the ota rooted but with stock recovery and unmodified system files?
Should I unroot and try to get the ota?
-peter
Click to expand...
Click to collapse
I've had the 5.1.1 system update notice for a few days and finally clicked "install" - it counts down to reboot, then instead of rebooting it says "system up to date" with the current time stamp.
I am rooted, unencrypted, Franco kernel, stock 5.1 ROM.
I assume the root and/or un-encryption is somehow preventing the system updates? Is there any way to stop the system update notification?
Thanks.
I took a dive and did the update. My phone is now in a wonky state. Its still at 5.1. Every time I power on my phone, it does the applications countdown like its indexing all the apps.
(Unencrypted, ElementalX, 5.1)
garyHal said:
I took a dive and did the update. My phone is now in a wonky state. Its still at 5.1. Every time I power on my phone, it does the applications countdown like its indexing all the apps.
(Unencrypted, ElementalX, 5.1)
Click to expand...
Click to collapse
Do you mean you tried to install the OTA? If so, it won't install for you. You have to have be stock (encrypted kernel, no root, stock recovery). Your best option is to fastboot flash the factory image.
cam30era said:
Do you mean you tried to install the OTA? If so, it won't install for you. You have to have be stock (encrypted kernel, no root, stock recovery). Your best option is to fastboot flash the factory image.
Click to expand...
Click to collapse
Yeah, I tried to install the OTA. I heard it wasn't going to work. I just expected the "verification" step to fail before it tried to install. Apparently something fubar'd.
How do we get rid of the dang system update message?
Sent from my Nexus 6 using Tapatalk
ryan141 said:
How do we get rid of the dang system update message?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I did it by long pressing on the notification and selecting 'i' which took me to the Google Play services App notifications. Then I selected Block and the notification went away.
thrasher9 said:
I did it by long pressing on the notification and selecting 'i' which took me to the Google Play services App notifications. Then I selected Block and the notification went away.
Click to expand...
Click to collapse
Doesn't that kill all of the google play services notifications?
I was hoping someone could help me out with this......
I've been getting this irritating "Android System Update" (screenshot attached) week after week.
I'm rooted (unlocked bootloader), running stock 5.1.1
This update keeps showing up and when I go to install it, the phone reboots, then it goes it TWRP. I'm assuming this hasn't installed correctly because it keeps coming back.
Does anyone know how to get rid of this or install it correctly. It's becoming quite annoying when it pops up time after time.
Thank you-
Install the update manually or block OTAs.
nhizzat said:
Install the update manually or block OTAs.
Click to expand...
Click to collapse
How do I install manually?
That's what I'm trying to find out
http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919
You can't take OTA if you are rooted.
jj14 said:
http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919
You can't take OTA if you are rooted.
Click to expand...
Click to collapse
Thank you.
So I just need to find the security patch and manually install it?
Now where to find it, LOL
I'd start by reading the stickies at the top of the thread list... Good readng.
this update would probably be LMY48I, for the stagefright patch.
what is your current build number?
IINexusII said:
this update would probably be LMY48I, for the stagefright patch.
what is your current build number?
Click to expand...
Click to collapse
LMY47Z (screenshot attached)
I have Verizon.
I thought the builds were carrier specific.
This is what I found:
https://developers.google.com/android/nexus/images#mysid
MVLJR said:
This is what I found:
https://developers.google.com/android/nexus/images#mysid
Click to expand...
Click to collapse
The link you posted is for Galaxy Nexus (not N6). It is the same page, but a different location. You need https://developers.google.com/android/nexus/images#shamu
@IINexusII is likely correct that the update you received is LMY48I. So you should be able to flash that
MVLJR said:
So I just need to find the security patch and manually install it?
Click to expand...
Click to collapse
See the end of the first post on the link that I shared above
Didgeridoohan said:
I'd start by reading the stickies at the top of the thread list... Good readng.
Click to expand...
Click to collapse
IINexusII said:
this update would probably be LMY48I, for the stagefright patch.
what is your current build number?
Click to expand...
Click to collapse
jj14 said:
The link you posted is for Galaxy Nexus (not N6). It is the same page, but a different location. You need https://developers.google.com/android/nexus/images#shamu
@IINexusII is likely correct that the update you received is LMY48I. So you should be able to flash that
See the end of the first post on the link that I shared above
Click to expand...
Click to collapse
Thank you all very much for your help.
I'll try to patch one of these updates this weekend when I have some time off.
I'm the gatekeeper for all that is Android OS in my family. Myself, my Mom and now my Dad all have Nexus 6' and I've rooted us all. So I install it on my phone first and then the same with theirs.
I was so happy I found a fix for the MLB At Bat app and their stupid blackout rules.
This is just great, been having the same issue and versions
This covered everything I had at the moment!
I applied the update tonight, sick of those damn OTA prompts.
This is where I got mine from, but still not sure if I chose the right one:
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
Installed the download from:
LVY48F (5.1.1 Project Fi bugfix update 20150910)
It says Project Fi only, but I have no idea what that is. I didn't see an option for LVY48I, so I went with LVY48F.
Did I do this right?
Want to make sure I didn't screw up my phone.
I tried installing the OEM ROM from here, but it failed while trying to flash it via TWRP recovery:
https://developers.google.com/android/nexus/images#shamu
"5.1.1 (LMY48I)"
Anyone?
MVLJR said:
I tried installing the OEM ROM from here, but it failed while trying to flash it via TWRP recovery:
https://developers.google.com/android/nexus/images#shamu
"5.1.1 (LMY48I)"
Click to expand...
Click to collapse
Latest factory image is LMY48M
Here is guide how to flash factory image. http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thank you!
I flashed the Pure Nexus ROM this past weekend and so far, so good. Loving some of the features not included in stock.
Afternoon all, just wondering if anyone could help on a quick problem - my Nexus 6 keeps prompting me to update but when I do it hangs after the reboot with what I assume is the recovery error message (red exclamation mark). I'm already on build LMY48I on 5.1.1, which I was under the impression was the September 2015 security patch. I'm fully stock, not rooted or any other mods. I am abroad currently, which I wouldn't imagine has any effect?
Could anyone offer any help on this or steer me in the right direction for further information.
Thanks in advance.
Latest build is LMY48M. OTA may fail because of corrupted download.
You may wanna update your signature.
Yeah, OK, thanks, not been around these parts for awhile.
Would you mind letting me know how I would go about getting a fresh download of the update using OTA?
Thank for the reply.
Still booting normally? Bootloader locked?
When you get to error with Android logo with tummy open press Power then VolumeUp this will show more details about the error. Write everything down.
Hi, sorry for for delay in replying. Bootloader is locked, boots normally when not trying to apply this update.
Next time I try to update I'll log the error messages and revert back here, thanks for your help.
gardy09 said:
Hi, sorry for for delay in replying. Bootloader is locked, boots normally when not trying to apply this update.
Next time I try to update I'll log the error messages and revert back here, thanks for your help.
Click to expand...
Click to collapse
If you're overseas you may be getting an incorrect build, not quite sure how that works
Strangely I thought it might have something towards do with being in Spain. I'll factory reset when I get home and see if that works.
Me too
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
soccerguy243 said:
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
Click to expand...
Click to collapse
two way.. update to the latest, or long press the update then oresspress the white circle that appears in the right, then press disable notifications. but i thing updating to the is most important.
simms22 said:
two way.. update to the latest, or long press the update then oresspress the white circle that appears in the right, then press disable notifications. but i thing updating to the is most important.
Click to expand...
Click to collapse
When I go to settings, about phone, it shows I àm running 5.1.1 which is the latest version. But ht I still get the notification.
soccerguy243 said:
When I go to settings, about phone, it shows I àm running 5.1.1 which is the latest version. But ht I still get the notification.
Click to expand...
Click to collapse
There have been serveral updates with version number 5.1.1. What you need to check is the build number.
The latest are LMY48M (most people), LYZ28K (T-Mobile) or LVY48F (Project Fi).
---------- Post added at 10:03 ---------- Previous post was at 10:01 ----------
soccerguy243 said:
Sorry to bump an old thread but the OP describes the EXACT problem I am having. Repeat system update update notifications. It says its downloaded but it goes to error when apply the update. I first got the notification in Qatar. I am unlocked and rootwd nexus 6 but running stock 5.1.1.
How can I get rid of the incorrect build?
Click to expand...
Click to collapse
Ah, just re-read your first post. You can't take an OTA-update, since you're rooted. You need to flash a factory image (or relevant parts of one).
Check the stickies for instructions...
Didgeridoohan said:
There have been serveral updates with version number 5.1.1. What you need to check is the build number.
The latest are LMY48M (most people), LYZ28K (T-Mobile) or LVY48F (Project Fi).
---------- Post added at 10:03 ---------- Previous post was at 10:01 ----------
Ah, just re-read your first post. You can't take an OTA-update, since you're rooted. You need to flash a factory image (or relevant parts of one).
Check the stickies for instructions...
Click to expand...
Click to collapse
I have 47Z installed. I'll use nexus root toolkit to get the latest. Thanks SO MUCH!
Evening all and sorry for delayed response. I've called Google today and they were no help whatsoever, the person I spoke to didn't even know the difference between Android versions and build numbers, I had to explain it to her. Is there any way of checking or finding out what build is being pushed to my phone? Also, will I be able to update to 6.0 when it arrives if I haven't sorted this problem ie how to clear this potentially corrupted download? Am I correct in thinking that I need to be on LMY48M and not on LMY48I - thanks in advance.
gardy09 said:
Evening all and sorry for delayed response. I've called Google today and they were no help whatsoever, the person I spoke to didn't even know the difference between Android versions and build numbers, I had to explain it to her. Is there any way of checking or finding out what build is being pushed to my phone? Also, will I be able to update to 6.0 when it arrives if I haven't sorted this problem ie how to clear this potentially corrupted download? Am I correct in thinking that I need to be on LMY48M and not on LMY48I - thanks in advance.
Click to expand...
Click to collapse
Have you ever found out more details about update error? Press Power then Volume Up on error screen.
Will do it now, hang on...
This is the error message I get...
gardy09 said:
This is the error message I get...
Click to expand...
Click to collapse
At this point you have few choices.
File bug report and wait for resolution.
Try Factory Reset. Using PC try fastboot format userdata and format cache.
Unlock bootloader and flash factory image. Might just well go straight to 6.0 MRA58K. You will loose all your private data either way. Backup all your private stuff.
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
gardy09 said:
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
Click to expand...
Click to collapse
Here is guide how to flash factory images http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
gardy09 said:
So have downloaded the MRA58K build of 6.0, attempting to sideload via ADB, device seen, reboot bootloader, into recovery, use ./adb sideload 'file.zip' but getting a footer and signature error. Any help would be greatly appreciated.
And how the hell does one update a 5 year old signature on XDA!?
Edit - so just reading around and there are two issues I've noted 1) that I'm going from LMY48I straight to MRA58K and missing out LMY48M or 2) that the factory images can't be sideloaded, they need to use the fastboot scripts. Any ideas what could be causing my errors?
Click to expand...
Click to collapse
You'll have to find the update from ur current version to the new version. You'll probably have to get LMY48M, didn't see one from I
Sent from my Nexus 6 using Tapatalk
Guys i have nexus 6 but i am not getting any OTA since April , last time i got April security patch (7.0.0 NBD92G)
but when i check on https://developers.google.com/android/ota it shows OTA images till june so
how can i flash that OTA image ?? i have lock bootloader and is there any chance of phone brick ??
Do a Google search for sideloading ota images. It's actually pretty easy. I'm unlocked running a rom so I can't give you a step by step off the top of my head.
nissan skyline said:
Guys i have nexus 6 but i am not getting any OTA since April , last time i got April security patch (7.0.0 NBD92G)
but when i check on https://developers.google.com/android/ota it shows OTA images till june so
how can i flash that OTA image ?? i have lock bootloader and is there any chance of phone brick ??
Click to expand...
Click to collapse
The instructions are on the download page for the OTA and I have pasted them below. You don't need an unlocked bootloader and there is always a chance that something could go wrong when flashing your phone but this method seems pretty safe.
To update a device using one of the OTA images below, you need the latest adb tool. You can get it from the Android SDK Platform-Tools package, which you can download here.
Don't forget to either add adb to your PATH environment variable or change into the directory containing the executable.
Also be certain that you've set up USB access for your device, as described in Run Apps on a Hardware Device.
To apply an OTA update image:
Download the appropriate update image for your device below.
Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link.
With the device powered on and USB debugging enabled, execute:
adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device instead, and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
For security, you should disable USB debugging when the device is not being updated.
Were you able to sideload the OTA? I tried on the 8th but got an error -- footer error. I'm on 7.1.1 and attempted to load N6F27E.
Adb sideload
I tried same method. Kept getting various errors.
Finally, I gave in. Phone needed to be cleaned out anyway. So, I used wugs.. Unlocked and rooted
I then used flashfire to go from 7.0 to 7.1.1 to 7.1.1 June.
Did not want to take chances. So just did updates in monthly order. I used the flash zip or ota option.
Everything went perfect. Done in five minutes.
Now, obviously. You can always relock and unroot w wugs. But, I left it alone. Hope this helps.
I also have a rooted nexus 6 via Wugs toolkit but I'm stuck on 7.0. where did you get the zip for 7.1? im relatively new too root exploration. Also idk if this is the right forum to ask this but while I'm here i was also curious if anyone has had any lagging, wifi and some blue tooth issues running 7.0 & if 7.1 is any better of experience.? Thanks for your time and consideration!!
Here is a link to gdrive with ota zips. Not reall great at this. So, hopefully you can download. I have not experienced any of the issues you have. None https://drive.google.com/drive/folders/0B1PLXsZI0UyjTGJEVDFaRy1ITms?usp=sharing
Liftkit said:
I also have a rooted nexus 6 via Wugs toolkit but I'm stuck on 7.0. where did you get the zip for 7.1? im relatively new too root exploration. Also idk if this is the right forum to ask this but while I'm here i was also curious if anyone has had any lagging, wifi and some blue tooth issues running 7.0 & if 7.1 is any better of experience.? Thanks for your time and consideration!!
Click to expand...
Click to collapse
https://developers.google.com/android/ota
Edit:I see that this URL already appears in the first post. Hmmm...
Sideloading the OTA is by far the simplest way of upgrading. You keep everything - data, apps, etc. You lose root, but that's easy to reinstall.
I'm currently on N6F26Q. Could I jump straight to June OTA or do I need to downgrade to 7.0 and then go back to 7.1.1 N6F27E?
NCtwin said:
I'm currently on N6F26Q. Could I jump straight to June OTA or do I need to downgrade to 7.0 and then go back to 7.1.1 N6F27E?
Click to expand...
Click to collapse
OTAs are complete packages. You can sideload the latest one directly.
Maybe that's why I keep getting an error when trying to use Wug to update. I'll do the sideload option and see what happens. Thanks a lot.
I went to the downloads page and my bill number nbd92g ends at 7.0 any suggestions?
---------- Post added at 08:28 PM ---------- Previous post was at 08:13 PM ----------
pckarma112 said:
I tried same method. Kept getting various errors.
Finally, I gave in. Phone needed to be cleaned out anyway. So, I used wugs.. Unlocked and rooted
I then used flashfire to go from 7.0 to 7.1.1 to 7.1.1 June.
Did not want to take chances. So just did updates in monthly order. I used the flash zip or ota option.
Everything went perfect. Done in five minutes.
Now, obviously. You can always relock and unroot w wugs. But, I left it alone. Hope this helps.
Click to expand...
Click to collapse
what is your build #
Liftkit said:
I went to the downloads page and my bill number nbd92g ends at 7.0 any suggestions?
---------- Post added at 08:28 PM ---------- Previous post was at 08:13 PM ----------
what is your build #
Click to expand...
Click to collapse
Take a backup and then sideload N6F27H, Jul 2017. You lose nothing, you boot back into pretty much what you had before, but with security enhancements and a few minor feature improvements.
And before you do any more, read my first sentence again.
*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