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?
Related
Those who are using Indian soak test before and now using official release in India.... Do you notice any changes?
Sent from my XT1068/69 using XDA Premium 4 mobile app
Soak Testers didn't get the final OTA and will not get it. Reason is, the final OTA rolled out today is the same one soak testers got. They just got it a little early. You can see in the screenshots that everything under About Phone is same in soak test version and final version.
So does this in theory then mean that those of us who installed the captured soak test from the other thread will not need to use any other captures in the future and be able to use the ota update just fine without any chances of bricks etc
bla7e said:
So does this in theory then mean that those of us who installed the captured soak test from the other thread will not need to use any other captures in the future and be able to use the ota update just fine without any chances of bricks etc
Click to expand...
Click to collapse
Correct. It is like we got the final OTA a little early.
Sri2702 said:
Correct. It is like we got the final OTA a little early.
Click to expand...
Click to collapse
Cool so we won't have any worries about our phones bricking if we do an ota as is then I guess? Then that puts me at ease of mind.
bla7e said:
Cool so we won't have any worries about our phones bricking if we do an ota as is then I guess? Then that puts me at ease of mind.
Click to expand...
Click to collapse
What do you mean by "we do an ota as is"?
Sri2702 said:
What do you mean by "we do an ota as is"?
Click to expand...
Click to collapse
I mean we'll be able to download ota's without worries of getting our phones bricked because of it being from soak. I remember reading the other day someone was talking about how if we want to be able to use ota we'd have to use a stable capture first in order to be able to use ota. It seems that won't be an issue though since soak and stable are the same with just different release dates so we shouldn't have to worry about that right? Sorry for being silly here. I'm not exactly an ape man when it comes to tech but I'm not feeling the need to fiddle around with roms and bootloaders on this phone when I shouldn't really need to
bla7e said:
I mean we'll be able to download ota's without worries of getting our phones bricked because of it being from soak. I remember reading the other day someone was talking about how if we want to be able to use ota we'd have to use a stable capture first in order to be able to use ota. It seems that won't be an issue though since soak and stable are the same with just different release dates so we shouldn't have to worry about that right? Sorry for being silly here. I'm not exactly an ape man when it comes to tech but I'm not feeling the need to fiddle around with roms and bootloaders on this phone when I shouldn't really need to
Click to expand...
Click to collapse
Well, it was me who said that the other day. That time the official update hadn't rolled out and we thought it would be a newer system version. But, now that it's released; we now know that it is the exact same OTA, so no problems for future updates either. It's like we never installed soak.
Sri2702 said:
Well, it was me who said that the other day. That time the official update hadn't rolled out and we thought it would be a newer system version. But, now that it's released; we now know that it is the exact same OTA, so no problems for future updates either. It's like we never installed soak.
Click to expand...
Click to collapse
Yea i suspected something like that was going on when I saw that new thread about the stable and people were saying everything's exactly the same but just wanted some sort of confirmation. Now the only thing that I don't know if it'll affect anything in the future is that my build number on 4.4.4 was kxb now it's lxb (unless k stands for kitkat and l for lolipop lol. dunno) but i don't think it would be a problem since the system version has only the numbers changed and everything else is as it was on kitkat. Seems like the indian release works on european xt1068's as well contrary to what I read some people were saying but I guess it depends on some things...
bla7e said:
Yea i suspected something like that was going on when I saw that new thread about the stable and people were saying everything's exactly the same but just wanted some sort of confirmation. Now the only thing that I don't know if it'll affect anything in the future is that my build number on 4.4.4 was kxb now it's lxb (unless k stands for kitkat and l for lolipop lol. dunno) but i don't think it would be a problem since the system version has only the numbers changed and everything else is as it was on kitkat. Seems like the indian release works on european xt1068's as well contrary to what I read some people were saying but I guess it depends on some things...
Click to expand...
Click to collapse
Funny, but you're right. The Build number on KitKat was "KXB21.85-23" on mine, but now it's "LXB22.46-28".
Sri2702 said:
Funny, but you're right. The Build number on KitKat was "KXB21.85-23" on mine, but now it's "LXB22.46-28".
Click to expand...
Click to collapse
Well that pretty much solved all questions I had regarding lolipop on my moto g. Now the only mystery that remains is if the indian update works just fine when you install it on a eu moto g (well you need to manually install from recovery doe doesn't detect it in the ota screen) why is the eu xt1068's update nowhere to be talked about. All I've seen is india brazil and so on but eu is so silent that even babies can sleep
bla7e said:
Well that pretty much solved all questions I had regarding lolipop on my moto g. Now the only mystery that remains is if the indian update works just fine when you install it on a eu moto g (well you need to manually install from recovery doe doesn't detect it in the ota screen) why is the eu xt1068's update nowhere to be talked about. All I've seen is india brazil and so on but eu is so silent that even babies can sleep
Click to expand...
Click to collapse
That´s a mystery for sure!
The only difference between the indian and the european XT1068 is the fact, that the indian version has 16 gb of memory,european model has 8gb.
But there must be something more that differs! In europe even a soaktest is rumored,surveys were sent,so everthing looks like we have to wait in europe for a few more days/weeks.
But why? In another thread I considered that Motorola is afraid of being taken to court or something by european users if something doesn´t work right. European laws are tough. Isn´t that a bit far out?
Or are there any technical differences between these models which are barely known?
Wolfcity said:
That´s a mystery for sure!
The only difference between the indian and the european XT1068 is the fact, that the indian version has 16 gb of memory,european model has 8gb.
But there must be something more that differs! In europe even a soaktest is rumored,surveys were sent,so everthing looks like we have to wait in europe for a few more days/weeks.
But why? In another thread I considered that Motorola is afraid of being taken to court or something by european users if something doesn´t work right. European laws are tough. Isn´t that a bit far out?
Or are there any technical differences between these models which are barely known?
Click to expand...
Click to collapse
Aside from the ram I highly doubt there's any real difference since when I got mine in the first few days of fiddling around it had the hindi, korean and pinyin keyboards which i disabled so I don't think that would be the case....I mean why would most eu phones need these inputs from the get go. As far as laws go I can't really see much reasoning there either since it's a 130-50eu phone so they can't really have much to complain and unless it somehow magically bricks the device I doubt there would be many if any at all issues...Dunno doe. I'm not motorola so i have no idea what's going on through their heads but it's just kinda silly to me considering that everything's running fine on mine at least without any factory resets or anything....could be just me doe. On another note I think one of my little gripes about lollipop is that it doesn't hide the signal bar for my secondary sim when it's inactive and just shows it. Is this just for me or does everyone have that cuz I didn't pay attention to that on screenshots the last few days
Did some one backed up latest Indian Lollipop rolled on 23 Jan in TWRP in recovery mode and uploaded somewhere? Please share.
cmahendra said:
Did some one backed up latest Indian Lollipop rolled on 23 Jan in TWRP in recovery mode and uploaded somewhere? Please share.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t3002426
Sri2702 said:
http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t3002426
Click to expand...
Click to collapse
The link is old version uploaded on 14 January. I am asking about 23 January version with new Baseband ver 1032.3105
cmahendra said:
The link is old version uploaded on 14 January. I am asking about 23 January version with new Baseband ver 1032.3105
Click to expand...
Click to collapse
The 14th Jan one does have 1032.3105.
EDIT: Looking at a screenshot in that thread, it doesn't have the above mentioned version.
Weird though, I have installed the same version, but using a .zip captured by one soak tester. How could the version be different, when the update is same?
Sri2702 said:
The 14th Jan one does have 1032.3105.
EDIT: Looking at a screenshot in that thread, it doesn't have the above mentioned version.
Weird though, I have installed the same version, but using a .zip captured by one soak tester. How could the version be different, when the update is same?
Click to expand...
Click to collapse
Yes, weird but there is reason. MD5 of old link and new capture matched perfect. Update in link by you and new both are same. Looks like Motorola fooled everyone and rolled same update again.
Anyways! Can anyone share TWRP backup of this version?
some apps bugs ..
Some apps like fifa 15 ut and some others are not supported for locked device and while installing from play store it showed error 505.
Stop making such threads...use the search option instead.
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
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
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...
Does anyone have a reasonable explanation as to why one isnt getting certain updates?
The only available update I have is the December 2017 one, but afaik that one is riddled with bugs, and I don't rly feel like risking it. The January never popped up, yet alone february and march one. I've tried all those possible "tricks" with Google Services, from data clean up, signing up for the beta program, factory reset; nothing worked.
I've been told by the support to wait for the batches to arrive; 3 times now.. On the Mi Forums I've been told to sacrifice goats to Chthulu.
My disappointment is immeasurable, and my day is ruined.
Download and flash the fastboot ROM by Mi Flash Tool.
Zoldannah said:
On the Mi Forums I've been told to sacrifice goats to Chthulu.
My disappointment is immeasurable, and my day is ruined.
Click to expand...
Click to collapse
LOL! Well, did you do it?
You can try the miflashtool method.
LouisMuruu said:
LOL! Well, did you do it?
You can try the miflashtool method.
Click to expand...
Click to collapse
An entire stock. Did not work ??*
I've never done flashing before, I'm nutorious for ****ing things up. Why can't I just get the OTA the way it's mean to be received ffs
Zoldannah said:
An entire stock. Did not work ??*
I've never done flashing before, I'm nutorious for ****ing things up. Why can't I just get the OTA the way it's mean to be received ffs
Click to expand...
Click to collapse
You are probably on nougat. You need to update to the december Version (oreo preparation) and then you can update to march from there.
The OTA updates are incremental updates from a specific firmware version so you have to go through the sequence of all the updates. You can't just jump over several in one go.
t-bon3 said:
The OTA updates are incremental updates from a specific firmware version so you have to go through the sequence of all the updates. You can't just jump over several in one go.
Click to expand...
Click to collapse
I've seen ppl saying they've got both dec + jan simultaneously.. But I guess this explains it; Thanks babes!
Well, can I ask why are you so special ??
shubham8 said:
Well, can I ask why are you so special ??
Click to expand...
Click to collapse
Special in a sense of being mentally challenged; self degradation. Don't worry, I'm not being condescending ?