Database Users

November security update is up

OTA's and factory images have been posted for November security updare.
https://developers.google.com/android/ota
Three versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon

With the BIG warning on the page about be sure to backup all your Photos and Personal data before applying the Update, does this means that it will delete all your data for just applying an OTA update? I understand that for applying the Full Factory images but does it really wipes the data applying just the OTA updates?
Sorry, but this being my first Nexus/Google phone what I know for OTA updates was just a simple process that doesn't delete anything on the phone, and I just want to be sure how it is here before I proceed, thanks in advance.

erasat said:
With the BIG warning on the page about be sure to backup all your Photos and Personal data before applying the Update, does this means that it will delete all your data for just applying an OTA update? I understand that for applying the Full Factory images but does it really wipes the data applying just the OTA updates?
Sorry, but this being my first Nexus/Google phone what I know for OTA updates was just a simple process that doesn't delete anything on the phone, and I just want to be sure how it is here before I proceed, thanks in advance.
Click to expand...
Click to collapse
Best to back up your data, just to be safe. But I personally sideloaded "U" without any issue. Nothing lost.

cam30era said:
Best to back up your data, just to be safe. But I personally sideloaded "U" without any issue. Nothing lost.
Click to expand...
Click to collapse
Yeah, I understand the risks when updating anything so I always do a backup of the most important stuff just in case, but as you know it's not the same to have to do a Full backup/restore. I needed to be sure but if you did it and you are fine then with what I already have backed up I should be fine too, thanks.

I just restored to stock my L and then checked for updates before rooting.
It said I'm already up to date.
I'll try again in a little while before rooting.
But simply being "unlocked" might be what is preventing me from grabbing an update. Not sure.

CZ Eddie said:
I just restored to stock my L and then checked for updates before rooting.
It said I'm already up to date.
I'll try again in a little while before rooting.
But simply being "unlocked" might be what is preventing me from grabbing an update. Not sure.
Click to expand...
Click to collapse
You can download the update(s) from the Google dev site and adb sideload of fastboot flash the factory image (if your bootloader is unlocked). No need to wait for the OTA, if you don't want to...

Whats the difference between builds NDE63U, NDE63V and NDE63X?

Got a vzw pixel that BL unlocked. Safe to flash the 63X? I saw @jcase said vzw would not do an OTA that relocked your BL. Just wondering if anyone else flashed the 63X build.

armandocorti said:
Whats the difference between builds NDE63U, NDE63V and NDE63X?
Click to expand...
Click to collapse
U-> 11/1 sec patch
V-> 11/5 sec patch
X-> 11/6 sec patch

cam30era said:
U-> 11/1 sec patch
V-> 11/5 sec patch
X-> 11/6 sec patch
Click to expand...
Click to collapse
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.

CZ Eddie said:
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
Click to expand...
Click to collapse
http://source.android.com/security/bulletin/2016-11-01.html

Was going to flash the factory image system but it looks like the process has changed.... More files and slot a and b.
Anyone know the proper way to manually flash the system.img?

cam30era said:
You can download the update(s) from the Google dev site and adb sideload of fastboot flash the factory image (if your bootloader is unlocked). No need to wait for the OTA, if you don't want to...
Click to expand...
Click to collapse
Yes, I realize I can typically install my own updates.
But as of right now, nobody truthfully knows which phone should have which build. P is so far looking Verizon Only.
Nobody I know of on Verizon has the H or L images.
So I'd rather be safe than sorry and let my phone CHOOSE it's update, and it did not so I mentioned that here to prevent others from restoring to stock and trying for an OTA
Anyways, it's just a payload.bin file. Not the same android image as the older files. I'm actually not sure how to install a payload.bin.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
cam30era said:
http://source.android.com/security/bulletin/2016-11-01.html
Click to expand...
Click to collapse
Yeah, I get that there are security patches.
But what I'm asking you is to tell us how you know those security patches correspond with the different builds.
I skimmed the page but didn't notice anything saying one way or the other.

CZ Eddie said:
Yes, I realize I can typically install my own updates.
But as of right now, nobody truthfully knows which phone should have which build. P is so far looking Verizon Only.
Nobody I know of on Verizon has the H or L images.
So I'd rather be safe than sorry and let my phone CHOOSE it's update, and it did not so I mentioned that here to prevent others from restoring to stock and trying for an OTA
Anyways, it's just a payload.bin file. Not the same android image as the older files. I'm actually not sure how to install a payload.bin.
Click to expand...
Click to collapse
My vzw pixel shipped with 63H.

jaxenroth said:
My vzw pixel shipped with 63H.
Click to expand...
Click to collapse
Then you're the only person on the board so far who has an H build on Verizon:
http://forum.xda-developers.com/pixel-xl/help/build-pixel-t3489990/page2
Could you please post in that thread to let others know?
I wonder if you got a non-Verizon phone.

CZ Eddie said:
[/COLOR]
Yeah, I get that there are security patches.
But what I'm asking you is to tell us how you know those security patches correspond with the different builds.
I skimmed the page but didn't notice anything saying one way or the other.
Click to expand...
Click to collapse
Valid question. @jcase has clearly stated that "X" would prevent VZW bootloader unlock. Regarding U and V, and which is 11/1 and which is 11/5, I don't know for sure. But it's clear from the Google dev link that each of the 3 builds include an incremental increase in patches.

"clearly stated that "X" would prevent VZW bootloader unlock."
Those durty basturds.
And that's why I didn't get a VZW phone.
<<----- VZW hater gets to hate on VZW yet again. :laugh:

JustusIV said:
Was going to flash the factory image system but it looks like the process has changed.... More files and slot a and b.
Anyone know the proper way to manually flash the system.img?
Click to expand...
Click to collapse
I guess i will do an adb sideload of the OTA.
I have never done it this way, but it looks like others have done this, and the boot-to-root still works.

with the newest radio being in the v .. i would speculate that its u world v north america and x verizon
corrected radio
Sent from my marlin using XDA Labs

CZ Eddie said:
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
Click to expand...
Click to collapse
"The previous U and V versions were a few days older and are simply there for legacy reasons."
Source > http://www.androidcentral.com/google-posts-latest-pixel-images-november-security-patch

Can I rollback the 7.1.1 December update?

I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?

mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Sadly no.

Thanks I had a feeling

Have you even tried?

Scott said:
Have you even tried?
Click to expand...
Click to collapse
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.

cam30era said:
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
Did this myself. Unlocked bootloader, rolled back from Q to O. Was unable to flash OTA (with locked bootloader), due to being older.

So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk

ahent said:
So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....

Thanks, I hope it just pushes OTA I don't want to mess with flashing it. By the time I get around to flashing it January may be out and it will be a moot point.
Sent from my Pixel XL using Tapatalk

cam30era said:
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
---------- Post added at 09:02 PM ---------- Previous post was at 09:01 PM ----------
cam30era said:
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....
Click to expand...
Click to collapse
IMHO I think the band 4 issues is pseudo.. since it does not update the radio or boot at all.. Unless its a "setting" that's changed that makes it work.

clockcycle said:
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
Unlocked bootloader definitely makes a difference, you can't flash a factory image without it.
Click to expand...
Click to collapse

mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Return the phone if you can and get another one. Odds are that the stock on the shelves hasn't been updated yet.
Sent from my Pixel XL using XDA Labs

January security update is posted

OTA links > https://developers.google.com/android/ota
factory image links > https://developers.google.com/android/images
V is for O2, U is for everyone else.

cam30era said:
Pixel XL OTA link > https://dl.google.com/dl/android/aosp/marlin-ota-nmf26v-7bda3acb.zip
Pixel XL factory image link > https://dl.google.com/dl/android/aosp/marlin-nmf26v-factory-e6bda208.zip
Click to expand...
Click to collapse
2 versions again.... NMF26U and NMF26V.

Are we to assume that the "V" version is for the Verizon variant?

Mrbobrowitz said:
Are we to assume that the "V" version is for the Verizon variant?
Click to expand...
Click to collapse
Not necessarily. We'll have to wait until Google adds additional information.

Per Verizon, They're pushing out U (https://www.verizonwireless.com/support/google-pixel-xl-update/)

Damn two versions! Which one should be downloaded, for Indian models?

I've updated my SDK, V is failing to flash for me...

Rydah805 said:
I've updated my SDK, V is failing to flash for me...
Click to expand...
Click to collapse
Sideload or fastboot? What error?

cam30era said:
Sideload or fastboot? What error?
Click to expand...
Click to collapse
Fastboot. Just says can't update bootloader and radio and quits. Sideload just flashed but said an error with the cache partition was detected but did complete.

So V is for non Verizon units?

Kookitza said:
So V is for non Verizon units?
Click to expand...
Click to collapse
Not clear yet, V could be for non american devices orrrrrrr, V can be for anybody non Verizon...

Rydah805 said:
Not clear yet, V could be for non american devices orrrrrrr, V can be for anybody non Verizon...
Click to expand...
Click to collapse
Ok, so you reccomend to wait a bit?

Rydah805 said:
Fastboot. Just says can't update bootloader and radio and quits. Sideload just flashed but said an error with the cache partition was detected but did complete.
Click to expand...
Click to collapse
Try to double click the image-marlin-nmf26v.zip that's inside the factory image zip.

Kookitza said:
Ok, so you reccomend to wait a bit?
Click to expand...
Click to collapse
Totally up to you. My bootloader is unlocked so I can switch versions without wiping data easily. If your bootloader is unlocked, you should be able to do this too.

jz987 said:
2 versions again.... NMF26U and NMF26V.
Click to expand...
Click to collapse
ithehappy said:
Damn two versions! Which one should be downloaded, for Indian models?
Click to expand...
Click to collapse
Kookitza said:
So V is for non Verizon units?
Click to expand...
Click to collapse
FWIW: both "U" and "V" have the same radio. But we still don't know what markets each update is intended for.

"U" is apparently for Verizon.
http://www.droid-life.com/2016/12/27/pixel-xl-android-update-nmf26u/
Sent from my Pixel XL using Tapatalk

FWIW, I just finished flashing the "V" version via fastboot flash-all command with removing the -W flag on my unlocked VZw version and everything booted up just fine with the updated version.

I'm curious as to whether or not anything other than the security update is included
Sent from my Pixel XL using Tapatalk

cam30era said:
Not necessarily. We'll have to wait until Google adds additional information.
Click to expand...
Click to collapse
I do wish they were clearer and doing this straight away I mean we aren't mind reader's Google!...Guess I'll just wait for the ota anyway it's only security no biggy.

Roxas598 said:
I do wish they were clearer and doing this straight away.
Click to expand...
Click to collapse
I agree

[Q] Anyone on the 7.1.2 BETA BUILD received the final 7.1.2 OTA yet?

As the subject? ?

Wondering the same myself. I have not.
Someone did mention on an Android site that the beta users should see the OTA pushed in the next few days.

iceman4357 said:
Wondering the same myself. I have not.
Someone did mention on an Android site that the beta users should see the OTA pushed in the next few days.
Click to expand...
Click to collapse
I've known it take over a week to appear ?
I think they prioritise all the older builds first then push it to us beta users ?

I'll not taking it until there's a way to unlock the bootloader Verizon's March ota update boo. It was too late when the Verizon rep was setting this phone up..
Sent from my Pixel XL using Tapatalk

sykoj82 said:
I'll not taking it until there's a way to unlock the bootloader Verizon's March ota update boo. It was too late when the Verizon rep was setting this phone up..
Click to expand...
Click to collapse
Its been relocked since last fall. It ain't happening man. Very sorry.

has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.

iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse
Doubt it will wipe. But you could flash the whole image removing the -w from the bat file.

iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse
You can't.
Sent from my Pixel using XDA-Developers Legacy app
---------- Post added at 05:00 PM ---------- Previous post was at 04:59 PM ----------
TonikJDK said:
Doubt it will wipe. But you could flash the whole image removing the -w from the bat file.
Click to expand...
Click to collapse
Only if you are bootloader unlocked.
Sent from my Pixel using XDA-Developers Legacy app

just flash the system img only
pretty simple

I just got the 7.1.2 image OTA on my Pixel XL and Project Fi. My wife's Pixel hasn't got it yet.

Never used an OTA always flash image simple and no problems, I remember in the past sometimes battery drain etc after installing a OTA

no joy yet here on Google Store Pixel XL on Verizon.

Stevez48 said:
no joy yet here on Google Store Pixel XL on Verizon.
Click to expand...
Click to collapse
I've been seeing delays in the Verizon rollout with this OTA, not sure why. I have a vzw Pixel however I'm on Project Fi and got the ota almost immediately. I'm not sure if that changes it or not, however.
We also need separate threads or disclaimers for those with locked bootloaders and those unlocked. To say just flash the image instead of sideloading the ota is ludicrous if the bl is locked. That simply can't be done.

aspexil said:
I just got the 7.1.2 image OTA on my Pixel XL and Project Fi. My wife's Pixel hasn't got it yet.
Click to expand...
Click to collapse
Was your pixel on beta release 2?

Garner said:
Was your pixel on beta release 2?
Click to expand...
Click to collapse
No. It was at v7.1.1 stock.

aspexil said:
No. It was at v7.1.1 stock.
Click to expand...
Click to collapse
Ahh right this thread was intended for people on the beta release ?

I haven't received the OTA yet, I'm on beta 2. I downloaded the update and tried to sideload it, but the installation failed because it says that the beta 2 is a newer build and it won't downgrade. I guess I'll just wait until the OTA from my carrier.

sideloaded the OTA file over Beta 2 tuesday morning and all went fine...have at it! :good:
iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse

nozzleman_85 said:
sideloaded the OTA file over Beta 2 tuesday morning and all went fine...have at it! :good:
Click to expand...
Click to collapse
Impossible.
Sent from my Pixel using XDA-Developers Legacy app

Haha yes. Not possible at all to load the existing OTA on the beta build. Google has to release a separate OTA build which it hasnt yet
bobby janow said:
Impossible.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse

June security update is out for Pixel 3a

Installing the update right now. It'll be the first security update for Pixel 3a.
Here's a link with more details and download links, no 3a specific fixes in the June patch.
https://9to5google.com/2019/06/03/pixel-june-19-security-patch/

Thanks. I checked around 9 EDT but nothing new. Still locked so sideloaded.

I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?

dhoang said:
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
Click to expand...
Click to collapse
I don't believe so but... Try and let us know how it turns out. I think the bootloader and stuff is different so I think you need factory image
Sent from my Pixel 3a using Tapatalk

Is it save to update if you're rooted?

jmtjr278 said:
I don't believe so but... Try and let us know how it turns out. I think the bootloader and stuff is different so I think you need factory image
Click to expand...
Click to collapse
It does not work. It was running for a bit then an error message"missing config CONFIG NETFILTER_XT_MATCH_QTAGUID". Oh well I tried. I guess I will have to wait until Google officially includes 3a in it beta program.

BehelitOutlaw said:
Is it save to update if you're rooted?
Click to expand...
Click to collapse
Yup. Works just fine. Just fastboot the modded boot.img provided by @pbanj afterwards and your good to go
Sent from my Pixel 3a using Tapatalk

Your running the old boot.img? Do you know if there is a problem with altering the new boot.img with magisk?
jmtjr278 said:
Yup. Works just fine. Just fastboot the modded boot.img provided by @pbanj afterwards and your good to go
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse

Archangel said:
Your running the old boot.img? Do you know if there is a problem with altering the new boot.img with magisk?
Click to expand...
Click to collapse
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
jmtjr278 said:
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
https://drive.google.com/file/d/1eQ9QXQqYeQityqCR2fk2jgBt7UKBA_5P/view?usp=drivesdk
Here is the one I made. Enjoy
Sent from my Pixel 3a using Tapatalk

dhoang said:
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
Click to expand...
Click to collapse
No. Cannot go back to pie. I had a discussion with Google rep today. She said soon as the Q beta for this month comes out, we will be able to go back to Android Pie as normal. There is an issue on their side. Here's what my error was when trying to sideload back to Pie on my VZW Pixel 3a

Perfect thanks brother! Saves me some time.
jmtjr278 said:
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
https://drive.google.com/file/d/1eQ9QXQqYeQityqCR2fk2jgBt7UKBA_5P/view?usp=drivesdk
Here is the one I made. Enjoy
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse

sd_N said:
No. Cannot go back to pie. I had a discussion with Google rep today. She said soon as the Q beta for this month comes out, we will be able to go back to Android Pie as normal. There is an issue on their side. Here's what my error was when trying to sideload back to Pie on my VZW Pixel 3a
Click to expand...
Click to collapse
Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.
Sent from my Pixel 3a using Tapatalk

jmtjr278 said:
Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
He has a VZW Pixel 3a. You can't fastboot a factory image with a locked bootloader. You can only sideload an OTA so he will need to wait in order to unenroll from the beta. Couple more days I think at the most.

Anyone else feel like the Multi tasking UI on the 3a has become faster after the update? Feels snappier to me

Rage1ofakind said:
Anyone else feel like the Multi tasking UI on the 3a has become faster after the update? Feels snappier to me
Click to expand...
Click to collapse
I think so. I have noticed you can swipe up from a bigger portion of the screen to show the appdrawer too. Now I can swipe up from the lower row of icons, and I think that before the update I had to swipe from the icon menu.

How do you even sideload the OTA ? When I do adb reboot recovery I just get a no command screen :/
EDIT: NVM Figured that out. When I sideload the OTA, I just get a signature verification failed error. I have a Tmobile 3a
Edit 2: I am dumb. I had the full image instead of OTA. Getting the OTA worked.

So i download the latest modded version on from pnabj "PQ3B.190605.006" then install it using this method "fastboot flash boot "whatever the boot.img is named" from the root guide and thats it?

oscar1823 said:
So i download the latest modded version on from pnabj "PQ3B.190605.006" then install it using this method "fastboot flash boot "whatever the boot.img is named" from the root guide and thats it?
Click to expand...
Click to collapse
If you have updated to the June security version and want to obtain root, then yes, flash the specific modified boot image. Then open the Magisk app and patch your boot image to complete the process.

12paq said:
If you have updated to the June security version and want to obtain root, then yes, flash the specific modified boot image. Then open the Magisk app and patch your boot image to complete the process.
Click to expand...
Click to collapse
Im already Rooted with magisk.

oscar1823 said:
Im already Rooted with magisk.
Click to expand...
Click to collapse
What are trying to do with the previously mentioned modified image?