Hi,
Its the fifth of March and Google released a new Update
Build: OPM1.171019.021
Bootloader: 8996-012001-1711291800
Radio: 8996-130091-1710201747
-> Changes
-> Download
-> Source
-> old Images
If you look at the Pixel XL, it looks like the N is for Verizon.
I received the NJH47B update. I'm in Canada on Koodo mobile
Who have a Google Play Devices from Germany/Europa and can tell me which one I have to download
I have a Pixel from Google, using it with AT&T in the U.S. Completely stock, but unlocked bootloader. I received the NJH47B OTA.
Did anyone verify that the 7.1.2 (NJH47B, Jun 2017) is for Verizon ?
Jilaman said:
Did anyone verify that the 7.1.2 (NJH47B, Jun 2017) is for Verizon ?
Click to expand...
Click to collapse
^
NHG47N is for verzion. Source is Pixel XL Thread you have to search
Pixel sailfish N2G47O to NJH47B incremental OTA (approx 50MB)
https://ota.googlezip.net/packages/.../66f44ab398d5c01e0c7fd951682a01d8d36a118a.zip
Code:
ota-required-cache=0
ota-type=AB
post-build=google/sailfish/sailfish:7.1.2/NJH47B/4021576:user/release-keys
post-build-incremental=4021576
post-timestamp=1495071184
pre-build=google/sailfish/sailfish:7.1.2/N2G47O/3852959:user/release-keys
pre-build-incremental=3852959
pre-device=sailfish
???
jss2 said:
I have a Pixel from Google, using it with AT&T in the U.S. Completely stock, but unlocked bootloader. I received the NJH47B OTA.
Click to expand...
Click to collapse
What's the point of fully stock but unlocked bootloader? Are you at least rooted?
Dude, can this be used on a rooted pixel via flashfire?
xdatastic said:
Pixel sailfish N2G47O to NJH47B incremental OTA (approx 50MB)
https://ota.googlezip.net/packages/.../66f44ab398d5c01e0c7fd951682a01d8d36a118a.zip
Code:
ota-required-cache=0
ota-type=AB
post-build=google/sailfish/sailfish:7.1.2/NJH47B/4021576:user/release-keys
post-build-incremental=4021576
post-timestamp=1495071184
pre-build=google/sailfish/sailfish:7.1.2/N2G47O/3852959:user/release-keys
pre-build-incremental=3852959
pre-device=sailfish
Click to expand...
Click to collapse
Sh0X31 said:
Hi guys,
So it's the first Monday in the month and Google release the June security update. But there are 4 different versions:
- NHG47N -> no description
- NJH34C -> Deutsche Telekom
- NJH47B -> no description
- NKG47L -> T-Mobile, Fi carriers, and Rogers
Source
Click to expand...
Click to collapse
NHG 27N can be root ?
From Droid Life: "The notes here for each Pixel update indicate that NHG47N is for Verizon models, NJH34C is for Deutsche Telekom, NKG47L is for T-Mobile, Fi users, and Rogers, while NJH47B is the generic build for everyone else."
This is the first time there is a T-mobile specific firmware right? I just switched to them from Verizon 2 months ago. Does anyone know what's different about the T-Mobile and Verizon firmwares?
Has anyone on Project Fi received the OTA yet? I have a Verizon Pixel, using it on Fi. Current May 5th version is the O build.
bobby janow said:
Has anyone on Project Fi received the OTA yet? I have a Verizon Pixel, using it on Fi. Current May 5th version is the O build.
Click to expand...
Click to collapse
O builds don't get the monthly security updates at same time as stable. You'll get it when the next preview/beta is ready.
Sorry, I think i read that wrong. I meant Android O. You mean N2G47O or whatever it is. I'll go hide back under my rock now.
xdatastic said:
O builds don't get the monthly security updates at same time as stable. You'll get it when the next preview/beta is ready.
Sorry, I think i read that wrong. I meant Android O. You mean N2G47O or whatever it is. I'll go hide back under my rock now.
Click to expand...
Click to collapse
Lol. Yes, that build, thanks. I almost posted the full image version thinking it looked like Android O I was asking about. I usually get the OTAs right away. I have a 5x on Android O which obviously is unlocked, so I might flash back to the May update to see if that device will get it. That's also on Fi but data only. The Pixel I have now is bootloader locked so all I can do is flash the full OTA sideload but I really don't want to do that. Not yet anyway.
bobby janow said:
Has anyone on Project Fi received the OTA yet? I have a Verizon Pixel, using it on Fi. Current May 5th version is the O build.
Click to expand...
Click to collapse
Did you ever get yours? I am also on Fi with a Verizon model and have not yet received it.
vansmack said:
Did you ever get yours? I am also on Fi with a Verizon model and have not yet received it.
Click to expand...
Click to collapse
No I haven't. No one on G+ has received it either on the Project Fi threads.
Sent from my Pixel using XDA-Developers Legacy app
I have an N2G47O Project Fi pixel that has been systemless rooted and now full unrooted. But it is failing to take this June update OTA. How can I get the update on my phone?
getut said:
I have an N2G47O Project Fi pixel that has been systemless rooted and now full unrooted. But it is failing to take this June update OTA. How can I get the update on my phone?
Click to expand...
Click to collapse
You made some change while rotted that it doesn't like. Best way is to clean it up once and for all. Run the flash all bat file from the full image.
But edit out the -w from the flashall bat file first. That will save your data, apps and settings. Then you will be all set going forward fir updates.
Related
Looks like there is a new update coming.
https://9to5google.com/2016/12/05/android-7-1-1-update-ota-nexus-pixel-december/
Interesting that it is coming to Verizon pixels but no factory images from Google yet. Curious to see if both models will always have the same updates or if sometimes Verizon models will have specific ones.
This is just the january patch due to be released on the 2nd of Jan
123cyborg said:
This is just the january patch due to be released on the 2nd of Jan
Click to expand...
Click to collapse
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
b00ster23 said:
For the official NMF26U update, the Verizon article can be found here https://www.verizonwireless.com/support/google-pixel-update/
Nothing listed here https://developers.google.com/android/ota to this point.
Would be curious if anyone took the update?
Click to expand...
Click to collapse
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
123cyborg said:
Dont think it was released. Usually security patches are released first monday of every month. Not sure why there is a delay
Click to expand...
Click to collapse
I'm guessing because of the New Year's Holiday the push was delayed. I would suspected it would have come out today. So if it's not out yet, then I'm maybe next Monday. That's if they stick with their current deployment scheme.
Two versions just posted, NMF26U and NMF26V.
sliding_billy said:
Two versions just posted, NMF26U and NMF26V.
Click to expand...
Click to collapse
Haha that was fast :laugh:
I'm on NMF26O. Nothing shows when I click check for updates on my phone. It's Verizon phone with root running on TMobile. Should I go ahead and sideload NMF26V?
and "NMF26V" is international?
thats the question, how can i identfy which one is my OTA file from Europe, version NMF26O
Not sure which version to use. Google phone on Verizon.
Cares said:
Not sure which version to use. Google phone on Verizon.
Click to expand...
Click to collapse
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
TonikJDK said:
Probably U.
In the past on the Nexus devices the earlier letter is the general release and the latter was for some specific carrier. My bet is the V version is a continuation of the Q fork from last month for some overseas carriers.
Edit. Over in the XL forum VZ customers and Vodephone are getting U OTA.
Click to expand...
Click to collapse
I got the OTA U on a Verizon phone activated on Project Fi. I'm thinking unless specifically you know to use V then the U update is the way to go if you want to sideload.
Google updated the image site, V is for Europe/O2 and U is for everyone else.
mrjiggywiggy said:
Google updated the image site, V is for Europe/O2 and U is for everyone else.
Click to expand...
Click to collapse
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
TonikJDK said:
I tweeted at them, said we needed to know. Baring a denial from Google I am going to take credit for that change. First time I ever saw them do that!
Click to expand...
Click to collapse
Well since you have their ear, perhaps you can tweet them to update the OTA images with descriptions. Only the full images have that. Not that it's hard to deduce but since some people sideload the ota rather than wait it might be nice.
fritzgerald said:
Just a heads up, I don't know if I did something wrong but I sideloaded the V update and now lost root. Let the phone boot after updating, fastbooted TWRP, deleated fstab, flashed SR5 and nothing but bootloops. I can reflash the V OTA and get my phone back but can't get root. At least not with SR5. Going to try flashing the U factory image (if it will let me) and see if that fixes it.
Edit:
Reflashed the V OTA, booted TWRP, flashed SR4, deleted fstab, flashed SR4 again, and phone boots fine with root.
Click to expand...
Click to collapse
I used 2.79 SR2 and didn't have any problems.
EE simlocked uk versions got nmf26u, i'd think if you have nmf26o then you have the current version for your carrier, which carrier is 'o'
is there a way right now to get the bootloader unlocked on a verizon pixel xl...... 7.1.1?
Well it's that time again VZW put out a new OTA anyone taken this yet what does it fix and is it worth it and I think all of us will be wondering is will it lock your bootloader Its unlocked
Me too, I got an OTA notification today, update size is 823.5 MB, don't know what build it is.
I have VZ Pixel, unlocked, stock rooted NMF260 with VZ service. Is it safe to install updates ? Please advice.
Thanks in advance.
azn6929 said:
Me too, I got an OTA notification today, update size is 823.5 MB, don't know what build it is.
I have VZ Pixel, unlocked, stock rooted NMF260 with VZ service. Is it safe to install updates ? Please advice.
Thanks in advance.
Click to expand...
Click to collapse
I think your safe I doubt Verizon would lock your bootloader. That would wipe your device again
@Shiftydogit, @azn6929 got hold of a screenshot? If yes, pls share.
As you can see OTA notification
My guess is it's probably another patch or possibly a kernel update who knows or bug fix one of the three
Here it is
azn6929 said:
Here it is
Click to expand...
Click to collapse
Might as well just do it lmao
So one of you said you are on nmf260. That is December. So i doubt this is a "new" update, you are just behind. Google only releases on the first Monday of the month. VZ uses the same exact releases. There is no special VZ version.
Update away.
TonikJDK said:
So one of you said you are on nmf260. That is December. So i doubt this is a "new" update, you are just behind. Google only releases on the first Monday of the month. VZ uses the same exact releases. There is no special VZ version.
Update away.
Click to expand...
Click to collapse
Brand new update came out yesterday last update was December as you can see
Shiftydogit said:
Brand new update came out yesterday last update was December as you can see
Click to expand...
Click to collapse
Holy cow, they are two months behind. I had no idea, that is nuts. It is the exact same as the Google December update, FWIW.
TonikJDK said:
Holy cow, they are two months behind. I had no idea, that is nuts. It is the exact same as the Google December update, FWIW.
Click to expand...
Click to collapse
Leave it to VZW to be behind on updates as they try to patch everything I think it's safe to update I'll probably do it tonight
Shiftydogit said:
Leave it to VZW to be behind on updates as they try to patch everything I think it's safe to update I'll probably do it tonight
Click to expand...
Click to collapse
That's the crazy part. It is the exact same as what Google released in December. The Pixel's are different...they are only using Googles updates. No changes, no bloat, no nothing.
TonikJDK said:
That's the crazy part. It is the exact same as what Google released in December. The Pixel's are different...they are only using Googles updates. No changes, no bloat, no nothing.
Click to expand...
Click to collapse
Then us VZW users may want to start checking Google for updates instead of waiting for VZW OTAs
Shiftydogit said:
Then us VZW users may want to start checking Google for updates instead of waiting for VZW OTAs
Click to expand...
Click to collapse
They are at the link below, posted the first Monday of each month. Dunno how you get them on an unlocked phone, I know it is doable...just dunno how.
https://developers.google.com/android/ota
EDIT: LOL, I'm an idiot. The instructions are right at the top of the page I linked to.
TonikJDK said:
They are at the link below, posted the first Monday of each month. Dunno how you get them on an unlocked phone, I know it is doable...just dunno how.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
You'd just download them then sideload the OTA via recovery or you can flash it via fastboot/ADB but if you have TWRP installed fastboot will replace it with stock recovery
OK so with update my phone lost TWRP and root other than that bootloader is still unlocked and everything seems fine
Also build number changed after update OK then
If you are getting a new Verizon OTA, it is late. My Verizon Pixel updated to NOF26V (Feb security patch), weeks ago. NOF26V is the most current image for Verizon Pixels.
I updated. New build is NOF26V. Everything seems to be fine. But root is gone. lol
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
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
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...