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...
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
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
Unless he is willing to manually update, there are only a few options. One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA. The other is borrowing a SIM from a different carrier for a few minutes, trying to update the system in settings, and then switching the SIM back. This will sometimes trigger an OTA. Finally, a more drastic measure would be to do a factory reset. Other than that he will just have to wait.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
NoobInToto said:
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
Click to expand...
Click to collapse
I'm in the same boat ?
v12xke said:
One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA.
Click to expand...
Click to collapse
Didn't work.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
My wife's Nexus 5X on T-Mobile just got Oreo a few days ago. I'm still waiting (but hopeful) for my Nexus 6P update. Neither of us were rooted or beta.
I was stuck on the August security patch too. I didn't realize it until September and then October rolled around.
I'm also on TMobile. I ended up just ended up manually updating. Worked without issue.
The last update I received was the August 1st patch. Is the unlocked version just being overlooked, or am I not receiving new updates?
I haven't gotten any updates either.
allenrb2 said:
The last update I received was the August 1st patch. Is the unlocked version just being overlooked, or am I not receiving new updates?
Click to expand...
Click to collapse
The last update to the u1 devices is AQH3. I have no idea why they havent updated.
Your options are do nothing, install a regular G950U rom and live with horrible carrier bloat and a package disabler, or root and run something debloated (done yourself or use a rom) and have 80% battery.
partcyborg said:
The last update to the u1 devices is AQH3. I have no idea why they havent updated.
Your options are do nothing, install a regular G950U rom and live with horrible carrier bloat and a package disabler, or root and run something debloated (done yourself or use a rom) and have 80% battery.
Click to expand...
Click to collapse
Just got an update today. It's funny, because a couple of days ago I reached out to Samsung of America, but didn't hear back. So I reached out to several Android reporting sites, and then all of a sudden we get an update.
allenrb2 said:
Just got an update today. It's funny, because a couple of days ago I reached out to Samsung of America, but didn't hear back. So I reached out to several Android reporting sites, and then all of a sudden we get an update.
Click to expand...
Click to collapse
Oh yea? To what? I've seen nothing in the normal release channels so it would be great to get some info on what is coming
Just received November security update on my unlocked U1. AQK2 is the latest release
just recieved the latest update with nomber security patch on my unlocked g950u1
Is it normal if I still haven't gotten the November update?
Is it possible to download and flash somehow?
mabk said:
Is it normal if I still haven't gotten the November update?
Is it possible to download and flash somehow?
Click to expand...
Click to collapse
try to check the updates manually, at least that's what i did
Yep, checked manually. Nothing.
I had an issue getting updates when I used Odin to install unlocked fw and didn't wipe afterwards. Is that the case here?
You can always go to Updato.com and search for G950U1 to dl and install from there.
I received the November security patch update last night as well.
installed the update on my s8+ while having substratum layers applied. stupid system keeps crashing, even on safe mode. had to restore to factory settings.
waldo98 said:
I received the November security patch update last night as well.
Click to expand...
Click to collapse
Which carrier are you on?
It's ironic the unlocked version from them gets the least attention
mabk said:
Yep, checked manually. Nothing.
Click to expand...
Click to collapse
Did you try updating using WiFi? That's what I had to do, it wouldn't update over data.
Just got the 11.30.2017 update as well. S8 unlocked version running on Tmobile.
any newssss anyone?? im not getting it...
Emorandum said:
any newssss anyone?? im not getting it...
Click to expand...
Click to collapse
Unlocked models are the last to get update, best case scenario month from now, worst up to three monts, i got the september security patch on 28th december and AQL1 mid january.
All I have is the December update.
If you have went along with installing the Oct, 2018 update, and you have a Sprint variant, but you have service with another carrier, please report here your experience. Thanks a lot.
LOVE ME PLEASE said:
If you have went along with installing the Oct, 2018 update, and you have a Sprint variant, but you have service with another carrier, please report here your experience. Thanks a lot.
Click to expand...
Click to collapse
Might do it tonight if nobody reports. I have Sprint with Verizon sim.
LOVE ME PLEASE said:
If you have went along with installing the Oct, 2018 update, and you have a Sprint variant, but you have service with another carrier, please report here your experience. Thanks a lot.
Click to expand...
Click to collapse
I'm interested to know as well!
ceelos218 said:
Might do it tonight if nobody reports. I have Sprint with Verizon sim.
Click to expand...
Click to collapse
Best of luck my friend. It seems as though it should go well, but Sprint and Essential seem to be desperate to patch this situation.
Oktober Update
Developer Settings/ Essential Noch-Settings
Set default for all applications
Set per application
I record an unintentional reboot of the system after this update, but otherwise ist all stable and OK here in Austria.
I have the sprint one and everything works fine. Consistently.
No issues here. Update took longer to install than I expected, but everything working fine on my end (straight talk/at&t sim)
italiangi said:
I'm interested to know as well!
Click to expand...
Click to collapse
backed up my data. grabbed Oct 2018 OTA from Essential's site
rebooted in recovery, sideloaded OTA
after reboot, SIM still unlocked
I can't speak for downloading the OTA from the phone itself, but the above steps worked for me
I flashed via BTS, and twrp + magisk. Then I found I lost wifi. Cannot start WIFI.
Also, I uses TWRP-SEP.img. Or I will have no touch. Any hint?
very smooth battery life improved very slightly mostly standby time and speaker min volume has decreased quiet a bit which is a very nice change and now we even got notch settings which is pretty dope in my opinoin
i was hoping notch settings would fix wabbitemu's incompatibility, but it didnt.
I'm on a Sprint running TMobile anyone confirm I won't be locked out again?
Sent from my Moto Z3 Play using Tapatalk
kenbrownstone said:
I'm on a Sprint running TMobile anyone confirm I won't be locked out again?
Click to expand...
Click to collapse
I have sprint phone using t mobile. Never had any issues
kenbrownstone said:
I'm on a Sprint running TMobile anyone confirm I won't be locked out again?
Click to expand...
Click to collapse
If you're already on September, update and you're not "simlocked" you should be fine updating to Oct, build. I have a Sprint variant, and I have service through T-Mobile. After I updated to September, build I got "simlocked". Thanks to the XDA modem swop, I unlocked my device, and updated to September, build without issues.
The only problem I am having after updating to September, build, is after attempting to root my device. I lose the ability to connect to WiFi. But after re-flashing my device fastboot, I am able to connect WiFi. Anybody else?
I have the unlocked version, but am using Sprint. Still waiting for the October update. Or new cables to arrive so I can sideload it. Whichever comes first. (Just got this phone Monday. It's my first USB c device. Ah, the new accessories to invest in too...)
Any changelog or improvement?
Hi there i have the unlocked sprint variant, im on pie so it is safe to update to the oct update? I heard the locking problems on september update. Thanks for your time
gilbertoperezx1 said:
Hi there i have the unlocked sprint variant, im on pie so it is safe to update to the oct update? I heard the locking problems on september update. Thanks for your time
Click to expand...
Click to collapse
If you have service through another carrier other than Sprint, and you have a Sprint variant, Essential Phone, and you haven't updated to September, update, but you would like to update to October, update, I wouldn't update to October update.
But if you have already updated to September, update, without issues? You should be fine updating to October.
If you ultimately want to update, and you unfortunately get "sim-lock" ? There are very credible fixes available in the threads of XDA for the essential phone to unlock the notorious SIM lock issue. Good luck!
Hi there I just updated to october update from Android Pie realese and I have a sprint variant PH1 unlocked and still fully unlocked. It is working great. Now I just need root it again. Thanks for all the support