September security updates being posted - Nexus 6 General

MOB31E is up now (along with first Nougat patch for those other devices)
https://dl.google.com/dl/android/aosp/shamu-mob31e-factory-051e2d25.zip

so we still remain in 6.0.1?

thetransit123 said:
so we still remain in 6.0.1?
Click to expand...
Click to collapse
Yes, still Marshmallow. Oddly, this one is named differently than the last couple monthly security updates. It does follow that mid-July performance numbering system.

The 6p is still on 6.0.1 too. So don't get too discouraged!

Tried to download the sept security update and the google ota link and files not there: 404. That’s an error. That’s all we know.

ryancell said:
Tried to download the sept security update and the google ota link and files not there: 404. That’s an error. That’s all we know.
Click to expand...
Click to collapse
I had that earlier too, but it's working now.

Preparing for nougat?

we probably wont get nougat until they release the "pixel phones"

i can see two new image same time for shamu, i can understand Google.

/system/etc/hosts
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.

Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
I'm using Magisk's superuser and systemless AdAway on the new update with no problems.

JimSmith94 said:
I'm using Magisk's superuser and systemless AdAway on the new update with no problems.
Click to expand...
Click to collapse
some links, please?
thanks

gothy.gothy said:
some links, please?
thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
http://forum.xda-developers.com/showthread.php?t=2190753

AlexX-DE said:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
http://forum.xda-developers.com/showthread.php?t=2190753
Click to expand...
Click to collapse
Thanks

Can anyone tell me the difference between MMB30W and MOB31E? I was going to sideload the September OTA, but not sure which one I am supposed to use. Haven't found any details anywhere. I'm currently on MMB30R, but I hadn't noticed there were multiple images released each month when I've sideloaded until now so not sure if I'm supposed to be on that image or not?

gill30 said:
Can anyone tell me the difference between MMB30W and MOB31E? I was going to sideload the September OTA, but not sure which one I am supposed to use. Haven't found any details anywhere. I'm currently on MMB30R, but I hadn't noticed there were multiple images released each month when I've sideloaded until now so not sure if I'm supposed to be on that image or not?
Click to expand...
Click to collapse
MMB has the radio that the carriers have agreed on, it's for their own version of Marshmallow. MOB has a newer radio. If you sideload it anyway, use the most recent.

If I am currently on M0B30W Project Fi, I see there are two builds below mine...which version below would I update to for the security patches safely if I'm stock?
6.0.1 (MMB30W) or 6.0.1 (MOB31E)

Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
No issue, but i did the usual...booted into twrp and deleted a couple of unneeded keyboards to make space.

ryancell said:
If I am currently on M0B30W Project Fi, I see there are two builds below mine...which version below would I update to for the security patches safely if I'm stock?
6.0.1 (MMB30W) or 6.0.1 (MOB31E)
Click to expand...
Click to collapse
Either one will work. They are exactly the same except for the radio. The MMB images contain an older radio that carriers have approved and the MOB images contain a newer radio that hasn't been approved by carriers yet. You could try the MOB image and if the radio performance isn't up to par you could extract the one from the MMB image. I've always used the MOB images and haven't had any radio issues, but I'm not on Project Fi...

Voight Kampff said:
anyone experiencing issues with adaway (or a custom /system/etc/hosts file) and this image? MOB31E appears to be a minor bump, but i thought i'd ask around before nuking my main device.
Click to expand...
Click to collapse
Nope, but I always delete useless preinstalled junk to make space.

Related

OJ6 update now available

Battery optimization and security updates.
I see no difference at all between this new update and the previous one. Can somebody state the differences if there is any please?
Probably part of the new "monthly" update schedule for security fixes. It's only 150.55 MB. Looks like it fixed the most recent Stagefright vulnerabilities.
poit said:
Probably part of the new "monthly" update schedule for security fixes. It's only 150.55 MB. Looks like it fixed the most recent Stagefright vulnerabilities.
Click to expand...
Click to collapse
I believe they sent another update to handle the stagefright. This one claimed Battery improvements so we will test and see
al3azim said:
I believe they sent another update to handle the stagefright. This one claimed Battery improvements so we will test and see
Click to expand...
Click to collapse
I think OG5 was supposed to fix the stagefright vulnerabilities but it didn't, there were new vulnerabilities discovered which you can test for using stagefright detector. OJ6 takes care of the new vulnerabilities.
poit said:
Probably part of the new "monthly" update schedule for security fixes. It's only 150.55 MB. Looks like it fixed the most recent Stagefright vulnerabilities.
Click to expand...
Click to collapse
poit said:
I think OG5 was supposed to fix the stagefright vulnerabilities but it didn't, there were new vulnerabilities discovered which you can test for using stagefright detector. OJ6 takes care of the new vulnerabilities.
Click to expand...
Click to collapse
Ok, thank you. Hopefully they got it this time around
Anyone rip out the update to add to current roms.
Sent from my 0x1 Note 4...... I love tep
kaos420 said:
Anyone rip out the update to add to current roms.
Sent from my 0x1 Note 4...... I love tep
Click to expand...
Click to collapse
If this update is the same type of update the N5 got then no you can't "add" this ota to current roms. It is a very complex patch that envolves actually patching all of the system files in the rom. I would need somebody to pull the ota zip from their phone and upload it and i will be able to give you a definite answer. But I can almost guarantee this ota is in fact a patch and therefore will be impossible to use for dev purposes. Speaking from my experience with the N5 ota which i quickly learned upon extracting and looking at the ota zip for it.
tx_dbs_tx said:
If this update is the same type of update the N5 got then no you can't "add" this ota to current roms. It is a very complex patch that envolves actually patching all of the system files in the rom. I would need somebody to pull the ota zip from their phone and upload it and i will be able to give you a definite answer. But I can almost guarantee this ota is in fact a patch and therefore will be impossible to use for dev purposes. Speaking from my experience with the N5 ota which i quickly learned upon extracting and looking at the ota zip for it.
Click to expand...
Click to collapse
Where is the file located?
tx_dbs_tx said:
If this update is the same type of update the N5 got then no you can't "add" this ota to current roms. It is a very complex patch that envolves actually patching all of the system files in the rom. I would need somebody to pull the ota zip from their phone and upload it and i will be able to give you a definite answer. But I can almost guarantee this ota is in fact a patch and therefore will be impossible to use for dev purposes. Speaking from my experience with the N5 ota which i quickly learned upon extracting and looking at the ota zip for it.
Click to expand...
Click to collapse
only reasaon i asked is came from note 3. we had a small update that was able to be flashed over current setup. but im sure someone will grab it.
After update i can't flash recovery via odin . Stuck on stock until i figure this one out
Anyone else having horrible speeds like this? Before I could get at least 13 down and sometimes even over 20 but this is horrible. We got a new prl version with this update too so I don't know if that's why. Well for some reason I can't post a pic but I only got 4 down and not even 1 full Meg up.
Sent from my SM-N910P using XDA Free mobile app
My wifi was slow downloading even after a fresh restart so i odin back to og and all good again
No wifi problems here. Speedtest reports the usual 35 down and 3 up. I'll check LTE when I get in a decent signal area. I'm on OJ6 with the 030 prl
Sent from my SM-N910P using Tapatalk
1midniterider said:
Where is the file located?
Click to expand...
Click to collapse
Cache folder
bonebeatz1234 said:
After update i can't flash recovery via odin . Stuck on stock until i figure this one out
Click to expand...
Click to collapse
Any update on rooting and recovery after updating?
poit said:
No wifi problems here. Speedtest reports the usual 35 down and 3 up. I'll check LTE when I get in a decent signal area. I'm on OJ6 with the 030 prl
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Same here. Wifi is the same and same prl. The weird thing was my signal didn't seem to really change simply driving around where normally it would be better.
Sent from my SM-N910P using XDA Free mobile app
To get the update zip do this. First you MUST be on the stock odexed OG5 rom. Next go to Settings | System update and check for updates or it may prompt you that an update is available automatically. simply download the update but DO NOT install it. Last, root your phone if you aren't already by odin'ing the latest TWRP recovery then flash a pre-rooted OG5 kernel in recovery and reboot. You will also need to flash the latest SuperSu binaries or download SuperSU from google Play and install it and then use that to install the binaries. Once you have proper root, use a root file browser (I recommend root explorer) and look in the root directory for a folder named "fota". The ota will be a zip file with a file name that is a mix of numbers and letters or it will be named "update.zip". It will be over 100mb in size. Copy that zip to your phone's internal storage or sd card and then upload that zip file and pm me the link. I will check it out. I'm pretty sure the update contains security updates that require "patching" the system files. This means the update.zip will be impossible to use for updating custom roms. We will have to wait for the tar ball.
Patch7 said:
Any update on rooting and recovery after updating?
Click to expand...
Click to collapse
I couldn't flash twrp recovery because it wouldn't work. I used cwm to get going again . The thing is i couldn't find it for sprint note 4 so i used a different model tar file not recommended unless you know what you doing . My touchscreen was not accurate after i flashed that recovery but i already knew it. I had to use dialer code *#2663# then i was rooted and back on custom rom.
Does this fix the damn crash to lock screen?

Marshmallow 6.0.1 security update released, April 2016 (MMB29X)

Available at:
https://developers.google.com/android/nexus/images#shamu
At a minimum it should fix the CVE-2015-1805 vulnerability. If you see any other changes post here.
The bootloader and the radio are the same as mmb29v.
najoor said:
Available at:
https://developers.google.com/android/nexus/images#shamu
At a minimum it should fix the CVE-2015-1805 vulnerability. If you see any other changes post here.
Click to expand...
Click to collapse
I'm not seeing that under Shamu Firmware. There is some stuff for it under Binaries, but not Firmware.
UPDATE:
Its showing up now.
This should be the list of the patches in this update. It's the April security bulletin.
https://source.android.com/security/bulletin/2016-04-02.html
MMB29X
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas
MMB29X
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas
So, I was on the 6.0 Build for a long time but finally decided it was time to update. I moved up to this build and have had some issues. Before I just replaced the Hosts file to get ad blocking. But with the 6.0.1 builds the System is full. Easy workaround was creating a symlink to a hosts file that is placed in /sdcard/ But in this build it seems like it isn't doing any ad blocking. Anyone have any ideas why?
Thanks
Basically I have 3 wants aside from stock, I don't root so I can keep Android Pay, I want ad-blocking, and edit the Build.prop to net.tethering.noprovision=true
Hello all. Has anyone gotten V4A to work with this latest update? I flashed the latest version and ended up locked at the Google Screen. Thank God for backups.
Sent from my Nexus 6 using XDA-Developers mobile app
electrojas said:
Hello all. Has anyone gotten V4A to work with this latest update? I flashed the latest version and ended up locked at the Google Screen. Thank God for backups.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
v4a has been working on most builds. you could have been doing something wrong or missing sonething
electrojas said:
Hey all. Ive been off the scene since July. I finally got my replacement N6. As soon as I turned it on, It had this update rarin to go so I installed it. Is this going to have any effect on unlock, root, custom recovery? I ask because it is brand new stock untouched other than the update.
Thanks Fellas
Click to expand...
Click to collapse
No, its a Nexus. But look into the new SuperUser by Chainfire, it is systemless now. So version 2.67 or higher. Also the system partition is full now. You cant write to it without deleting a couple of items first like unused keyboards.
I have seen so many new versions of Viper, and as I said in my previous post I turned on my phone from brand new, fast boot, unlocked bootloader and rooted. I installed TWRP, version 3001. So at this moment I am stock rooted with TWRP version MMB29X. Can anyone kindly point me to the best and correct TWRP flashable version of Viper? Without V4A, I feel like I have half a phone. Thanks to anyone who can give me a hand. Peace guys.
Sent from my Nexus 6 using XDA-Developers mobile app
electrojas said:
I have seen so many new versions of Viper, and as I said in my previous post I turned on my phone from brand new, fast boot, unlocked bootloader and rooted. I installed TWRP, version 3001. So at this moment I am stock rooted with TWRP version MMB29X. Can anyone kindly point me to the best and correct TWRP flashable version of Viper? Without V4A, I feel like I have half a phone. Thanks to anyone who can give me a hand. Peace guys.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well I did what we all need to do and just kept diggin. Turns out wugfresh updated the toolkit for the new updates, I had to reinstall the newest TWRP, and flash the latest V4A. Killer. This is the best app there is for Android by far.
Sent from my Nexus 6 using XDA-Developers mobile app
MMB29X factory image just got updated in the last day or so.
New:
https://dl.google.com/dl/android/aosp/shamu-mmb29x-factory-99e985b9.tgz
Original:
shamu-mmb29x-factory-ef4cbb75.tgz
No idea why or what changed. I'm on slow internet at the mo so can't check. Maybe just changed one of the included scripts ?
xdatastic said:
MMB29X factory image just got updated in the last day or so.
New:
https://dl.google.com/dl/android/aosp/shamu-mmb29x-factory-99e985b9.tgz
Original:
shamu-mmb29x-factory-ef4cbb75.tgz
No idea why or what changed. I'm on slow internet at the mo so can't check. Maybe just changed one of the included scripts ?
Click to expand...
Click to collapse
Its include only two changed apk. Everything else - same.
New Google Play services 9.0.86
Displax said:
Its include only two changed apk. Everything else - same.
New Google Play services 9.0.86
Click to expand...
Click to collapse
Could you extract and share the play services apk please
xdatastic said:
Could you extract and share the play services apk please
Click to expand...
Click to collapse
https://mega.nz/#F!B01wWDRT!W-GlR70PgY-iCuRrtg9azw
But it is odexed apk, so can't be uploaded on http://www.apkmirror.com

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

Nougat is here for Verizon devices!

I look at my system updates, and I see this! I couldn't believe it! Nougat is finally here!
Just checked and received it as well!
Has somebody captured the OTA file?
Can we root the android nougat?
I had Verizon before. They are known for doing updates late and completely messed up. At least they aren't late this time. I'm just miffed that they dropped it before RETUS.
G4liant said:
Has somebody captured the OTA file?
Click to expand...
Click to collapse
I had every intention to but I was so excited that I forgot before I updated. If no one else does and I can find a stock file to go back to MM, I will try.
shawnsac2000 said:
Can we root the android nougat?
Click to expand...
Click to collapse
On Verizon no. And probably never will be able to.
That sucks
ironbesterer said:
I had every intention to but I was so excited that I forgot before I updated. If no one else does and I can find a stock file to go back to MM, I will try.
Click to expand...
Click to collapse
You do not need root to read most system files.
It used to be in /cache but deletes itself after the flash.
aviwdoowks said:
You do not need root to read most system files.
It used to be in /cache but deletes itself after the flash.
Click to expand...
Click to collapse
I know. Since I flashed it, I couldn't pull the ota through logcat.
My update is having issues. Tried a handful of times and would get "update could not be verified" or something similar after the download would complete update. When it doesn't fail verification, the install fails after rebooting. wtf, I have tried the VZW/Moto software update program but it returns that I have the latest software. Guess that channel might not be updated yet.
teerout said:
My update is having issues. Tried a handful of times and would get "update could not be verified" or something similar after the download would complete update. When it doesn't fail verification, the install fails after rebooting. wtf, I have tried the VZW/Moto software update program but it returns that I have the latest software. Guess that channel might not be updated yet.
Click to expand...
Click to collapse
Is it an official ADDISON_VZW or is it a RETUS device?
ironbesterer said:
On Verizon no. And probably never will be able to.
Click to expand...
Click to collapse
What is the issue with the Verizon variant for root? I am willing to commit a good tip for a verifyable process to anyone that can do it in a reasonable timeframe. Anyone else willing to donate to the cause?
The bootloader can't be unlocked.
BillyBob3 said:
What is the issue with the Verizon variant for root? I am willing to commit a good tip for a verifyable process to anyone that can do it in a reasonable timeframe. Anyone else willing to donate to the cause?
Click to expand...
Click to collapse
Read here
Know jcase?
https://forum.xda-developers.com/z-force/help/root-verizon-t3507253
ironbesterer said:
Is it an official ADDISON_VZW or is it a RETUS device?
Click to expand...
Click to collapse
The device is official VZW. I also have the " device has failed verification" warning on start-up. I'm sure that's not helping things either...
BillyBob3 said:
What is the issue with the Verizon variant for root? I am willing to commit a good tip for a verifyable process to anyone that can do it in a reasonable timeframe. Anyone else willing to donate to the cause?
Click to expand...
Click to collapse
Mostly QCSB and the nearly impossible to exploit bootloader.
aviwdoowks said:
Read here
Know jcase?
https://forum.xda-developers.com/z-force/help/root-verizon-t3507253
Click to expand...
Click to collapse
What's his post number? I can't seem to find it.
FYI, I was able to upgrade to Nougat this morning using the VZW software upgrade assistant.
teerout said:
FYI, I was able to upgrade to Nougat this morning using the VZW software upgrade assistant.
Click to expand...
Click to collapse
So the N firmware is used by that?
Can you extract it somehow? Mac or PC?

last update (October security patch) is out

Last build for shamu (N6F27M) is available :
https://developers.google.com/android/ota#shamu
I'm out of the office today, anyone want to let me know if there's a new radio or bootloader?
Sent from my Glade[emoji768] Plugins
SynisterWolf said:
I'm out of the office today, anyone want to let me know if there's a new radio or bootloader?
Click to expand...
Click to collapse
Looks like bootloader is the same but there's a new radio, at least for Verizon.
ota received
So long and thanks for all the fish...
This is probably the last official update for our Nexus 6.
Anyone facing this problem?
rishabh1500 said:
Anyone facing this problem?
Click to expand...
Click to collapse
Worked fine for me. If you have modded your rom, then OTA will often fail.
I've been sideloading the OTA updates for months. Since Google made the check for updates function actually do something, thought I would go that route this time. It worked and immediately offered me an update. How can I verify that it's going to install NGI77B and not N6F27M? I'm on Verizon and currently on NGI55D.
I tried capturing a bug report and looking for the OTA link in the file but am not finding it. Maybe I should just sideload it.
HankStorm said:
I've been sideloading the OTA updates for months. Since Google made the check for updates function actually do something, thought I would go that route this time. It worked and immediately offered me an update.
Click to expand...
Click to collapse
same for me
HankStorm said:
How can I verify that it's going to install NGI77B and not N6F27M? I'm on Verizon and currently on NGI55D.
I tried capturing a bug report and looking for the OTA link in the file but am not finding it. Maybe I should just sideload it.
Click to expand...
Click to collapse
I guess that if your Verizon sim is in it, the "right" ota will automatically be downloaded
Now that the final patch has been issued what & when would make you all move over to a custom rom?
iluvatrix said:
Now that the final patch has been issued what & when would make you all move over to a custom rom?
Click to expand...
Click to collapse
next month I will try LOS
T-mo users, looks like we will never get an automatic update. Have you side-loaded the latest 7.1.1? Any issues?
Note10.1Dude said:
T-mo users, looks like we will never get an automatic update. Have you side-loaded the latest 7.1.1? Any issues?
Click to expand...
Click to collapse
Using T-mobile network via Ting - no issues seen so far with the sideloaded Oct 2017 OTA update.
iluvatrix said:
Now that the final patch has been issued what & when would make you all move over to a custom rom?
Click to expand...
Click to collapse
I bought N6 in October last year and have been using custom ROMs on it since day one.
First PureNexus and now currently DirtyUnicorns.
I plan on moving to LOS once nightlies start rolling out.
LOS == Lineage OS?
java007 said:
jNote10.1Dude said:
Using T-mobile network via Ting - no issues seen so far with the sideloaded Oct 2017 OTA update.
Click to expand...
Click to collapse
Using T-mobile network via Ting - no issues seen so far with the sideloaded Oct 2017 OTA update.
Click to expand...
Click to collapse
I was getting monthly security update notifications on my Nexus 6 while using Verizon, however that stopped since moving to T-Mobile in April/2017.
I'm staying stock for now, because it seems easiest to maintain Android Pay, Snapchat compatibility, etc.
Does anyone have a recommendation on which build to use if I sideload? Would that be "N6F27M" since the other October release states "Verizon" ?
EDIT: I went ahead and sideloaded N6F27M, which seems to be working fine with T-Mobile thus far.
- ooofest
Does N6F27M include security patch against new hole in WPA ?
No, it will be in November security patch but it's not sure that Nexus 6 will receive it...
I'm on Fi but my phone doesn't give me the opportunity to update N6F27M, it does not show that there is an OTA available.
Could it be that the phone was a Verizon overstock which I flashed to NGI55D manually when I first bought it?
I suppose I will have to sideload the OTA.
Edit: Never mind, it finally came through.
November security patch is out for pixel and 2015 nexus, no new build for our good old Shamu so we will have to keep it with Krack security breach or install custom rom...

Categories

Resources