Hi,
First Monday in a new month and Google release a new security update (April 2017).
-> Download (NOF27D)
-> Download (N2G47E)
Source
Changelog
There's a D or E version. Am I missing something on mobile view?
There are three, and only one is labeled. So tired of this issue. I tweeted at them, last month the fixed it right away. Dunno if my tweet has anything to do with it.
Edit: Nevermind, I'm an idiot. They are labeled correctly. One is 7.1.1, other two are 7.1.2.
D 7.1.1
e 7.1.2
Sh0X31 said:
Hi,
First Monday in a new month and Google release a new security update (April 2017).
-> Download (NOF27D)
-> Download (N2G47E)
Source
Click to expand...
Click to collapse
Why would Google release 7.1.1 and 7.1.2 for Pixel? I was thinking that in April they would release 7.1.2 software update and not 7.1.1
7.1.1 (NOF27D, Apr 2017)
7.1.2 (N2G47E, Apr 2017)
Charkatak said:
Why would Google release 7.1.1 and 7.1.2 for Pixel? I was thinking that in April they would release 7.1.2 software update and not 7.1.1
7.1.1 (NOF27D, Apr 2017)
7.1.2 (N2G47E, Apr 2017)
Click to expand...
Click to collapse
In case 7.1.2 still has some bugs and someone would prefer to stick with 7.1.1? Doesn't hurt to have choices, it's a good thing!
roirraW "edor" ehT said:
In case 7.1.2 still has some bugs and someone would prefer to stick with 7.1.1? Doesn't hurt to have choices, it's a good thing!
Click to expand...
Click to collapse
Makes sense, but if my phone has 7.1.1 March update, then which version will be offered via OTA 7.11 or 7.1.2?
N2G47E finally brought WiFi call on Deutsche Telekom Germany (didn't use the N2G47J DT edition since I set up my phone with the unbranded version in the first place - what's the difference anyway?!).
Charkatak said:
Makes sense, but if my phone has 7.1.1 March update, then which version will be offered via OTA 7.11 or 7.1.2?
Click to expand...
Click to collapse
I'll let you know in about 5 minutes. Step 2 or 2 about halfway done.
edit: 7.1.2
bobby janow said:
I'll let you know in about 5 minutes. Step 2 or 2 about halfway done.
Click to expand...
Click to collapse
You already received OTA?
Charkatak said:
You already received OTA?
Click to expand...
Click to collapse
US DC area, already got 7.1.2 ota installed! :good:
Charkatak said:
You already received OTA?
Click to expand...
Click to collapse
Yes, about an hour ago. All done now and I'm on April 5th security and 7.1.2
Any of you that got OTA, were you running beta or public ver before the update? My phone at the moment has beta version.
Charkatak said:
Any of you that got OTA, were you running beta or public ver before the update? My phone at the moment has beta version.
Click to expand...
Click to collapse
I received the 7.1.2 OTA updated (USA, Boston area, AT&T). I've never had any of the beta versions on, I received the OTA update coming from the March 7.1.1 stock factory image.
Charkatak said:
Any of you that got OTA, were you running beta or public ver before the update? My phone at the moment has beta version.
Click to expand...
Click to collapse
I'm fully stock Verizon model locked bootloader on Project Fi. I believe that if you're on the beta it's a "later" build than the OTA 7.1.2 and you will not receive it. You will have to wait for an OTA from beta to release sometime in the future, or if you want rollback to the 7.1.1 March release and wait for the April OTA or sideload it. But that will wipe your device and you might not want to do that.
bobby janow said:
I'm fully stock Verizon model locked bootloader on Project Fi. I believe that if you're on the beta it's a "later" build than the OTA 7.1.2 and you will not receive it. You will have to wait for an OTA from beta to release sometime in the future, or if you want rollback to the 7.1.1 March release and wait for the April OTA or sideload it. But that will wipe your device and you might not want to do that.
Click to expand...
Click to collapse
Update: Your theory could be correct that beta version could be newer and the phone needs to wait for a beta build. When beta program ends, then phone will automatically get public build or I can cancel the enrollment myself.
Understood! When I enrolled into beta program a week ago, my phone installed: NPG47I. I thought that when public version (7.1.2) is released, the phone with beta software should get it too. Before I enrolled into beta, the phone was running 7.1.1 and after getting into beta, the phone received 7.1.2.
Hi all, sorry if this is a silly question but if I'm rooted with TWRP should I not do an OTA update?
If I do it will it go through fine and I will just lose those mods?
Dancube said:
Hi all, sorry if this is a silly question but if I'm rooted with TWRP should I not do an OTA update?
If I do it will it go through fine and I will just lose those mods?
Click to expand...
Click to collapse
I'd also like to know. I'm on Verizon version with an unlocked bootloader. I'm pretty sure I can't do any OTA's in order to save root right?
Changelog added in OP. Find it at the Google-Forum
Dancube said:
Hi all, sorry if this is a silly question but if I'm rooted with TWRP should I not do an OTA update?
If I do it will it go through fine and I will just lose those mods?
Click to expand...
Click to collapse
Jabawockee said:
I'd also like to know. I'm on Verizon version with an unlocked bootloader. I'm pretty sure I can't do any OTA's in order to save root right?
Click to expand...
Click to collapse
3rd post in the thread below. Just get the 7.1.2 image instead of the 7.1.1 that I mention in the post.
Pay attention to removing the -w from flashall bat file. That is how you save your dara and apps.
Second to the last post to reroot.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Related
I opt-in for Android Beta Program a while back (to get Android Nougat and now I'm on 7.1.1), however today is November 14ths and yet still no OTA update for November security patch...
Am I the only one who didn't get update?
Where do you find OTA image for beta? I'm in the same boat but I am rooted.
a1exus said:
I opt-in for Android Beta Program a while back (to get Android Nougat and now I'm on 7.1.1), however today is November 14ths and yet still no OTA update for November security patch...
Am I the only one who didn't get update?
I know I can apply update through fastboot, but still...
Click to expand...
Click to collapse
Most likely google isn't doing a separate update for just a security patch on dev preview 1... There will be a larger update to dev preview 2 sometime this month which I'm sure will also include the updated security patch.
biscuitownz said:
Where do you find OTA image for beta? I'm in the same boat but I am rooted.
Click to expand...
Click to collapse
I apologize, I was under impression ota is available, but after double checking it's only available for 7.0, not 7.1.1. Sorry)
Sent from my Nexus 6P using Tapatalk
FanDroid09 said:
Most likely google isn't doing a separate update for just a security patch on dev preview 1... There will be a larger update to dev preview 2 sometime this month which I'm sure will also include the updated security patch.
Click to expand...
Click to collapse
imo, monthly security update should still be *monthly*, but maybe it's just me..
a1exus said:
imo, monthly security update should still be *monthly*, but maybe it's just me..
Click to expand...
Click to collapse
DP1 was released Oct 19, with the October security update. DP2 will probably be out within the next week or so with the November security update. Which is about 1 month later...
Sure seems like *monthly* to me.
What more do you want?
November security patch
I have not enrolled in Beta program but I still did not receive the November security update for my Nexus 6P, is it me only or it has not been released yet? (I'm on N 7.0 version)
sorena88 said:
I have not enrolled in Beta program but I still did not receive the November security update for my Nexus 6P, is it me only or it has not been released yet? (I'm on N 7.0 version)
Click to expand...
Click to collapse
It has been released (nbd91k). Make sure your Google apps are up-to-date. You could also try clearing cache in recovery.
Or even sideload manually the ota (search google ota image angler)
How do I get latest December update? I'm on Verizon.
I wonder if we'll have to wait until end of the month again...
I'm still on December patch, even though it's January 25th already...
is it just me or did someone got January OTA?
a1exus said:
I'm still on December patch, even though it's January 25th already... is it just me or did someone got January OTA?
Click to expand...
Click to collapse
Here
I asked on several threads but no answer, so i try on this way
Im on 7.1.2 public beta, and still didnt get the official update...can i manually flash/sideload OTA image with adb over beta?? Thanks.
scrin378 said:
I asked on several threads but no answer, so i try on this way
Im on 7.1.2 public beta, and still didnt get the official update...can i manually flash/sideload OTA image with adb over beta?? Thanks.
Click to expand...
Click to collapse
Hello... The problem is:
The official build release date is older than the beta release date, so the OTA will likely fail...
You could unenroll from beta, recieve the 7.1.1 OTA and later take the 7.1.2.
Good luck... :good:
5.1 said:
Hello... The problem is:
The official build release date is older than the beta release date, so the OTA will likely fail...
You could unenroll from beta, recieve the 7.1.1 OTA and later take the 7.1.2.
Good luck... :good:
Click to expand...
Click to collapse
How do you mean "older"?? Beta is from march, and OTA is from april..i mean OTA 7.1.2
Sorry for noob questions...im new to nexus family
scrin378 said:
How do you mean "older"?? Beta is from march, and OTA is from april..
Sorry for noob questions...im new to nexus family
Click to expand...
Click to collapse
Yeah I was like WTF myself...
For final 7.1.2, it looks like the OTA has been built before the beta 2. Certainly no changes between beta 2 and final build.
As I said before, just unenroll from beta program, accept 7.1.1 OTA and you'll recieve 7.1.2 soon after...
Cheers...
5.1 said:
Yeah I was like WTF myself...
For final 7.1.2, it looks like the OTA has been built before the beta 2. Certainly no changes between beta 2 and final build.
As I said before, just unenroll from beta program, accept 7.1.1 OTA and you'll recieve 7.1.2 soon after...
Cheers...
Click to expand...
Click to collapse
And if i stay on beta will i receive further updates normaly, or do i have to leave beta program anyway..
scrin378 said:
And if i stay on beta will i receive further updates normaly, or do i have to leave beta program anyway..
Click to expand...
Click to collapse
To be honest, I don't know. On Google site, they say that beta users are supposed to get the final build first lol... Which is clearly not the case. On the Pixel devices, people are waiting as well...
Cheers...
scrin378 said:
I asked on several threads but no answer, so i try on this way
Im on 7.1.2 public beta, and still didnt get the official update...can i manually flash/sideload OTA image with adb over beta?? Thanks.
Click to expand...
Click to collapse
No, but you can flash the full 7.1.2 image over beta. You should have already received the stable version. Just un-enroll from the beta program, download the full image and flash. To keep your data, just remove the "-w" from the flash-all.bat.
Hi all
im currently running on the latest update which is july updates with android 8.0 and july security. i havent got any updates. when i go on to check software updates it says "your system is up to date" with android version: 8.0.0. and security patch level: July 5, 2017. any help will be great.
thanks
Your best bet would be too download the update manually. Do you have access to a computer?
Kermit404 said:
Hi all
im currently running on the latest update which is july updates with android 8.0 and july security. i havent got any updates. when i go on to check software updates it says "your system is up to date" with android version: 8.0.0. and security patch level: July 5, 2017. any help will be great. thanks
Click to expand...
Click to collapse
Manually update. Even if your bootloader is locked you can sideload a new OTA. Why wait?
Just leave the beta programm. Got the September patch 30 seconds after leaving. Also it won't make any difference until Google uploads the first Android 9 dev builds, wich probably won't come for the 6P anyway
I'd try to sideload the OTA manually if I were you. Using the stock recovery.
If that goes well then you are done.
Sent from my Nexus 6P
I also had to unenroll from the beta to get the Sept updates.
I'm on T-Mobile and have not received any September security patch. I am going to have to side load
ZombieUsr said:
I'm on T-Mobile and have not received any September security patch. I am going to have to side load
Click to expand...
Click to collapse
Was there a question in there somewhere? Yes is the answer.
v12xke said:
Manually update. Even if your bootloader is locked you can sideload a new OTA. Why wait?
Click to expand...
Click to collapse
is there any video on how to manually update. since im been trying its not helping when there is no tutorial on how to manually update
I'm experiencing the same issue. I already unenrolled & re-enrolled in the beta once to try to fix my battery issues and it's stuck at the July update. If I unenroll it again, will it wipe the phone?
thesebastian said:
I'd try to sideload the OTA manually if I were you. Using the stock recovery.
If that goes well then you are done.
Sent from my Nexus 6P
Click to expand...
Click to collapse
sideload OTA on mac is not working it still says ota is directory. but it did not send to my nexus 6p
Kermit404 said:
sideload OTA on mac is not working it still says ota is directory. but it did not send to my nexus 6p
Click to expand...
Click to collapse
Update your platform tools and try again. If you receive another error or the same one, post a screenshot.
Sent from my Nexus 5X using Tapatalk
anotherjmartin said:
I'm experiencing the same issue. I already unenrolled & re-enrolled in the beta once to try to fix my battery issues and it's stuck at the July update. If I unenroll it again, will it wipe the phone?
Click to expand...
Click to collapse
No, it won't be wiped.
Hello everyone
i managed to manually sideload OTA update to my nexus 6p. its officially working. all good. i had issues than managed to fixed it.
SlimSnoopOS said:
Update your platform tools and try again. If you receive another error or the same one, post a screenshot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
i did update platform and perform SIDELOAD OTA update. its working. thanks
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...
According to Google's bulletin page, the firmware images won't be available until tomorrow (December 5th). OTA updates usually roll out after the images are posted, so tomorrow will probably be our first chance to get a look at the new builds. There will be two patch levels this month: 12-1 and 12-5. The Nexus/Pixel builds should all be 12-5.*
- from http://www.androidpolice.com/2017/1...system-updates-go-live-tomorrow-december-5th/
hope they don't mess up battery life anymore like the November patch did...
Sent from my Pixel 2 using Tapatalk
November patch had no effect on my battery life. I don't know what fraction of devices were affected, but it certainly wasn't universal.
It seems like the stable version of 8.1 is rolling out today according to android authority, sorry can't post the link just yet.
Sent from my Pixel 2 using Tapatalk
https://www.androidauthority.com/android-8-1-oreo-stable-final-release-820097/ there it is...
Gesendet von meinem Pixel 2 mit Tapatalk
Anyone on the beta program got the update?
heiserhorn said:
Anyone on the beta program got the update?
Click to expand...
Click to collapse
It's not rolling out just yet. The factory images will probably be posted some time today or tomorrow, the OTA's will start going out a day or two later.
---------- Post added at 11:13 AM ---------- Previous post was at 10:31 AM ----------
Factory images and OTA zips are up!
https://developers.google.com/android/ota
---------- Post added at 11:19 AM ---------- Previous post was at 11:13 AM ----------
Lame, I'm on DP2 and the update fails because it's older than DP2...
mikeyinid said:
Lame, I'm on DP2 and the update fails because it's older than DP2...
Click to expand...
Click to collapse
You sideloaded?
heiserhorn said:
You sideloaded?
Click to expand...
Click to collapse
Yes, it failed. I had to opt out of the beta and go back to 8.0.0
Not a big deal for me, it only takes me 10 minutes to set my phone back up. I'm just curious if people on the beta will even get the OTA since the updater sees the 8.1 final as being older.
mikeyinid said:
Yes, it failed. I had to opt out of the beta and go back to 8.0.0
Not a big deal for me, it only takes me 10 minutes to set my phone back up. I'm just curious if people on the beta will even get the OTA since the updater sees the 8.1 final as being older.
Click to expand...
Click to collapse
Maybe we 8.1 DP2 will jump to 8.1 January Patch directly.
But generally Google takes 0-2 weeks to start moving people from Beta to Stable. So It would be extraordinary and update in 4 weeks.
Trying to sideload 8.1 from the .25 build and I get stuck at "Verifying package"
thesebastian said:
Maybe we 8.1 DP2 will jump to 8.1 January Patch directly..
Click to expand...
Click to collapse
It's not Jan, why would they have a January patch before Jan. The Pixel 2 arrived brand new with Sep 2017 but didn't get an Oct patch, The first security update for it was Nov.
I suspect that some might just get the 8.1 upgrade with the Dec 2017 patch included instead of just the Dec 2017 patch.
krelvinaz said:
It's not Jan, why would they have a January patch before Jan. The Pixel 2 arrived brand new with Sep 2017 but didn't get an Oct patch, The first security update for it was Nov.
I suspect that some might just get the 8.1 upgrade with the Dec 2017 patch included instead of just the Dec 2017 patch.
Click to expand...
Click to collapse
The Dec 2017 patch is 8.1
krelvinaz said:
It's not Jan, why would they have a January patch before Jan. The Pixel 2 arrived brand new with Sep 2017 but didn't get an Oct patch, The first security update for it was Nov.
I suspect that some might just get the 8.1 upgrade with the Dec 2017 patch included instead of just the Dec 2017 patch.
Click to expand...
Click to collapse
I was talking about the OTA from 8.1 DP2 to 8.1 non Beta.
If the 8.1 DP2 is newer than the just released 8.1, then the 8.1 DP2 will upgrade to another version. (Maybe in January, maybe before January).
This wouldn't be the first time Google push the ota from Beta to Stable in a delayer manner
MaxNXS said:
Trying to sideload 8.1 from the .25 build and I get stuck at "Verifying package"
Click to expand...
Click to collapse
I have the same issue. Anyone have a solution for this?
MaxNXS said:
Trying to sideload 8.1 from the .25 build and I get stuck at "Verifying package"
Click to expand...
Click to collapse
seos83 said:
I have the same issue. Anyone have a solution for this?
Click to expand...
Click to collapse
I had to relock my bootloader before it would sideload.
All updated fine after that
thesebastian said:
I was talking about the OTA from 8.1 DP2 to 8.1 non Beta.
If the 8.1 DP2 is newer than the just released 8.1, then the 8.1 DP2 will upgrade to another version. (Maybe in January, maybe before January).
This wouldn't be the first time Google push the ota from Beta to Stable in a delayer manner
Click to expand...
Click to collapse
Was this convo stemmed from the fact that you are enrolled in the beta and haven't seen the 8.1 final OTA yet? That is the case with me....
seos83 said:
I have the same issue. Anyone have a solution for this?
Click to expand...
Click to collapse
Are you rooted? I re-flashed the stock kernel/dtbo from November before sideloading the ota and had no issues
I was running DP2 and just got the official 8.1 OTA update. It was only about 45 megabytes, so they didn't change much.
Matterhorn said:
I was running DP2 and just got the official 8.1 OTA update. It was only about 45 megabytes, so they didn't change much.
Click to expand...
Click to collapse
Do you still get the beta popup when your phone boots?