Database Develop

[REF] Nexus 5 Stock OTA URLs

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!

Repeat update notification

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

Nexus 6 Official June OTA flash help !!

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.

October OTA Update 4BQJ2 is out

Just got my OTA update notification. Update went smoothly (sorry, forgot to check file size before updating. Confirmed BlueBorne vulnerability is fixed.

Not sure if this is unique to me, but post-update, my phone is now telling me my SD card is unsupported and asking me if I want to format. Really hoping to avoid backing up a 200GB card, formatting and restoring this weekend. Not sure if anyone else is having this issue too or if just my luck to have to deal with, but just a warning out there to those who may decide they want to unmount their SD cards before updating.

FWIW, my device seems to be running just a bit smoother after a day of use. No noticeable change in battery life. Pleased with the update so far.

quick newbie question, I have the G935A , fully stocked, but using it on a Canadian network, I was told I won't get the update via OTA so I installed Smart Switch, but it also says my device is up to date which has the May security patch installed (that's what it came with when I bought it last month). Any idea where I can find just the OTA patch and update the phone ?

bestjsg said:
quick newbie question, I have the G935A , fully stocked, but using it on a Canadian network, I was told I won't get the update via OTA so I installed Smart Switch, but it also says my device is up to date which has the May security patch installed (that's what it came with when I bought it last month). Any idea where I can find just the OTA patch and update the phone ?
Click to expand...
Click to collapse
If you aren't running on an AT&T network, you might seriously consider switching to the U firmware. Of course, Samsung conveniently forgets the U firmware exists too, so that might not gain you a whole lot at the moment.

I have the U firmware and I've been checking for updates, but nothing (I'm on the August security patch). Is there a way to force the update or use Odin or side load it? My phone was originally built for the Sprint network, then the previous owner flashed it to work on AT&T. I was not able to get any updates (was stuck on the May security patch). I used Odin to put the U firmware on it and then got 3 security patch updates after that.

caferacer73 said:
I have the U firmware and I've been checking for updates, but nothing (I'm on the August security patch). Is there a way to force the update or use Odin or side load it? My phone was originally built for the Sprint network, then the previous owner flashed it to work on AT&T. I was not able to get any updates (was stuck on the May security patch). I used Odin to put the U firmware on it and then got 3 security patch updates after that.
Click to expand...
Click to collapse
The U firmware always lags the carrier firmware. August is sadly the current date for the unlocked devices for now.

All I had to do was be patient. I got the newest update (4BQJ5 - November security patch) this morning.

November update

https://developers.google.com/android/ota
I've update via adb.
Swiping via Soli seems much improved for me when using the music player.

What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.

ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
I followed the below steps. This is assuming you are already rooted on October patch level and want to maintain root.
1) Downloaded the factory images for the Nov update (https://developers.google.com/android/images) to the PC.
2) Extracted the zip file (make sure to extract the zip file inside the first one. That zip contains the .img file which we will need in step 4 ).
3) Edited the flash_all.bat file to remove '-w' parameter so that the data is not wiped.
4) Copied the 'boot.img' to the phone and used magisk manager to patch the boot file (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching).
Copied the patched 'magisk_patched.img' from the phone to the PC.
NOTE: I also disabled all magisk modules before the next steps. This is just to ensure that custom module don't mess up the update (have seen this with the Oneplus 7 PRO android 10 update when i had that device)
5) Reboot phone into bootloder and connect to PC
6) Flashed the update by running the flash_all.bat file (make sure to remove the '-w' parameter before flashing so that DATA is not wiped). I did run into issue where the vendor.img failed at flashing but a change of USB cable fixed that (I have seen this issue before. some cables just don't work in fastboot/adb).
7) Once the flashing completes the phone reboots and does some update after booting up.
8) Again reboot into bootloader. Flash the boot with the 'magisk_patched.img' that was copied in step 4.
Code:
fastboot flash boot magisk_patched.img
I always flash it on both the a & b partitions by using below command.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
9) Reboot the phone. At this point you have ROOT with Magisk and your custom kernel would be gone since stock/patched boot.img would have replaced it. You can re-flash your kernel (make sure the kernel has been updated for the November security update). Also at this point you can enable any modules that you may have disabled before the update.

I got november update now from ota..

Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
---------- Post added at 09:23 AM ---------- Previous post was at 09:21 AM ----------
meek2100 said:
Does anyone know why the Pixel 4 has 3 update files? Is there a specific version need for a specific carrier or something?
These are all Nov 2019 Factory/OTA update files for the Pixel 4.
QD1A.190821.007.A3
QD1A.190821.014
QD1A.190821.014.C2
Click to expand...
Click to collapse
Actually I just found the answer here: https://support.google.com/pixelphone/thread/18553639?hl=en
Pixel 4 (XL):
US (ATT & Verizon): QD1A.190821.014.C2
US (TMobile, Sprint, Google Fi) & UK carriers: QD1A.190821.014
All other carriers (AU/JP/CA/TW/US): QD1A.190821.007.A3

ExcuseTheN00b said:
What is the best way to do the OTA with Magisk root and custom kernel installed? It has been a very long time since I have rooted a phone and did any OTA.
Click to expand...
Click to collapse
The post above (post #3) that says to use the factory image isn't wrong, but it isn't the easiest method either.
You can side-load the OTA image. You can do this on a phone with a locked or unlocked bootloader and you don't need to modify any files to prevent it from wiping the phone. It's just like the OTA update and will not wipe the phone.
You can find the files and directions directly from Google. https://developers.google.com/android/ota
Once the update is done, you will need to reroot the phone using the standard modified boot image method and then reflash your custom kernel (after making sure it has been updated to the latest OTA version). Just be aware that while the actual flashing time is much shorter than taking the OTA normally, it may have to optimize all of the apps during the initial boot. Unfortunately it doesn't give you any indication this is going on (unlike during a normal OTA update) and therefore people tend to get impatient and reboot during the initial boot. Don't do this. Just be patient and let the phone do it's thing. My phone took about 20 minutes to boot initially after side-loading the Nov update because I have a decent number of apps that it had to optimize.

Oops, nevermind. fixed

How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.

Spookymyo said:
How do I get into bootloader mode? I can get into fastboot mode fine. But when I execute the command 'fastboot flashing unlock' the command prompt just shows waiting for device.
Click to expand...
Click to collapse
Instructions here
https://developers.google.com/android/ota

Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?

xxaarraa said:
Anyone experiencing "improved camera quality" that was listed in the change log? What are we looking for specifically?
Click to expand...
Click to collapse
Pure speculation on my part, but I wonder if Google didn't tweak the auto-white balance due to the complaints about how the phone handled white balance in pictures with a predominantly red color.

Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Sent from my Pixel 4 using Tapatalk

BubbaGumprc said:
Apparently Google killed the manual update your phone function again. At least on my pixel 4. Seemed to happen to me all the time on the pixel 3 too. Anyone else have the same issues?
Click to expand...
Click to collapse
I had the same issue, the check update function did not work on my P4. It was working great on my P3.

Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.

sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed

sn0warmy said:
Ugh! I got antsy and manually flashed the November factory image and now my face unlock is completely broken. I've tried rebooting, deleting face data + creating a new one in different lighting environments 5+ times now. No matter what I do the phone will not recognize my face anymore. It was working flawlessly on the October patch.
Now I'm afraid broken face unlock is one of the reasons Google delayed the role out of the November patch. Not a happy camper right now.
EDIT: I had to revert back to the October patch (full wipe) to get face unlock working again.
Click to expand...
Click to collapse
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine

Does this undo the tweak to get Google pay to work with magisk? Or will we have to re do it?

ahsank128 said:
that's, odd, i updated to november, and my phone is spot on, I've yet to face an issue, or if i have i havent even noticed
Click to expand...
Click to collapse
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
thehartk said:
Make sure you picked the correct image for your phone variant.
My phone came with build 007, installed a different one and it broke the face unlock. Installing back 007 restored it.
Im on November and face unlock works just fine
Click to expand...
Click to collapse
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.

sn0warmy said:
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Look here: https://support.google.com/pixelphone/thread/18742521?hl=en

sn0warmy said:
hm... When I flashed the November image I did full wipe. Mybe this time I'll try without wipe and see if it retains proper face unlock from the October image.
Yeah, I was on 10.0.0 (QD1A.190821.007, Oct 2019) before clean flashing 10.0.0 (QD1A.190821.014, Nov 2019). I'm now back on 10.0.0 (QD1A.190821.007, Oct 2019) to get face unlock working again.
I wonder if I should be flashing 10.0.0 (QD1A.190821.007.A3, Nov 2019), instead? That ".A3" is giving me pause though.
Google really needs to label/identify these factory images better like they used to with (unlocked US) or (verizon) etc.. This is confusing.
Click to expand...
Click to collapse
Yes flash the .007.A3 if you were on the .007 before. I went through the same problems with the .014 too but .007.A3 fixed it.