Seems very quiet?!?
Based on release history, they are released anywhere from the 1st to the 7th of each month.
Wondering myself if they are going to wait to release for Google I/O next week.
Monday, May 7th has my bet! :good:
May 5, 2018 is not posted yet. You can download it to sideload on the 4th or 5th from this link: https://developers.google.com/android/ota
May 5th, but don't quote me!
I vote may 8th when Google I/O starts. Also hopefully the second developer preview of Android P
It's always the first Monday of the month. That has not occurred yet.
TonikJDK said:
It's always the first Monday of the month. That has not occurred yet.
Click to expand...
Click to collapse
This
Sent from my Pixel 2 using Tapatalk
I'm running stock rooted with magisk. Can I take the OTA and then re-root it again? or I have sideload or is there a different process? thanks
patt2k said:
I'm running stock rooted with magisk. Can I take the OTA and then re-root it again? or I have sideload or is there a different process? thanks
Click to expand...
Click to collapse
You can unrooted completely, then side load the OTA, or, fastboot the factory image with the -w removed from the flash-all.bat file, then just flash twrp and magisk again when finished. I personally don't like going the OTA route, this is my method every month for updating if you want to have a look :good:
Badger50 said:
You can unrooted completely, then side load the OTA, or, fastboot the factory image with the -w removed from the flash-all.bat file, then just flash twrp and magisk again when finished. I personally don't like going the OTA route, this is my method every month for updating if you want to have a look :good:
Click to expand...
Click to collapse
Dude, your running stock still? If I flashed the new stock image sans the -w over top of AquariOS, will it boot??
CyberpodS2 said:
Dude, your running stock still? If I flashed the new stock image sans the -w over top of AquariOS, will it boot??
Click to expand...
Click to collapse
Brother Cyber! How ya been bruh?! Yep, I went back to stock. It should boot, however, you may want to restore your stock backup first :good:
The post three above mine is the correct answer. Clean, easy and zero failures. You will have issues trying to unroot in most cases. Not worth it.
...But we still dont have a fully functioning twrp . and i dont think its gonna decrypt the new security patch
dlb4all said:
...But we still dont have a fully functioning twrp . and i dont think its gonna decrypt the new security patch
Click to expand...
Click to collapse
Guess we'll find out on Monday. What makes you say that outa curiosity? ?
Badger50 said:
Guess we'll find out on Monday. What makes you say that outa curiosity? ?
Click to expand...
Click to collapse
just a pessimistic guess and many years of experience . but hey , lets hope im wrong
TonikJDK said:
It's always the first Monday of the month. That has not occurred yet.
Click to expand...
Click to collapse
That might be true but in past months there has been official mentions of the monthly update by this point.
I'm hoping for some battery life fixes or, at the very least, not getting any worse.
Badger50 said:
You can unrooted completely, then side load the OTA, or, fastboot the factory image with the -w removed from the flash-all.bat file, then just flash twrp and magisk again when finished. I personally don't like going the OTA route, this is my method every month for updating if you want to have a look :good:
Click to expand...
Click to collapse
i just flash the ota in twrp lol, easy as it gets
dlb4all said:
...But we still dont have a fully functioning twrp . and i dont think its gonna decrypt the new security patch
Click to expand...
Click to collapse
it takes 2 seconds to turn off security while u update lol..
Related
It's been a long time and im just not sure. I tried to do the auto update for 6.0.1 but it brought me to recovery so i just rebooted.
Kainzo said:
It's been a long time and im just not sure. I tried to do the auto update for 6.0.1 but it brought me to recovery so i just rebooted.
Click to expand...
Click to collapse
You can't take an OTA if you have root and/or a custom recovery anyway. You need to remove root first. The best way to update if you're rooted is by flashing the factory images. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
You can't take an OTA if you have root and/or a custom recovery anyway. You need to remove root first. The best way to update if you're rooted is by flashing the factory images. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Oh I see, I bought the phone used, so i'll probably just stay on 6.0.0
Kainzo said:
Oh I see, I bought the phone used, so i'll probably just stay on 6.0.0
Click to expand...
Click to collapse
It's pretty easy to take it back to stock so you can use the built in updater.
Heisenberg said:
It's pretty easy to take it back to stock so you can use the built in updater.
Click to expand...
Click to collapse
Understood, but if they're planning on pushing these security updates monthly, thats a big turn off to do monthly D:
Kainzo said:
Understood, but if they're planning on pushing these security updates monthly, thats a big turn off to do monthly D:
Click to expand...
Click to collapse
If you stay stock it's all automated. If you keep root it only takes a few minutes to update. The choice is yours of course, just want to make sure you're fully informed. If you stay on 6.0 you're going to miss out on several security patches, and features too.
Kainzo said:
Understood, but if they're planning on pushing these security updates monthly, thats a big turn off to do monthly D:
Click to expand...
Click to collapse
Not if you go custom ROM that updates every 3 weeks. Pure Nexus is my choice on all 3 devices. Never going back to stock. FCK that
Sent from my Nexus 6P using Tapatalk
here is the link for reference: https://developers.google.com/android/images
I have a Google play Store phone, but since I have a Verizon SIM it installed the Verizon firmware and so I have to wait until they release. I had hoped this wouldn't happen with Verizon stating they would release the same time as Google, but here I am.
Sent from my Pixel XL using Tapatalk
http://www.androidpolice.com/2016/1...-nmf26o-rolling-today-possibly-android-7-1-1/
Eager for this update!
Are all 3 on the same version now?
ahent said:
I have a Google play Store phone, but since I have a Verizon SIM it installed the Verizon firmware and so I have to wait until they release. I had hoped this wouldn't happen with Verizon stating they would release the same time as Google, but here I am.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I am in the same boat... It should be available shortly (or so I hope). No reason to believe otherwise this soon after release. :good:
I guess it looks like O is for the V version. I wish they would just label this stuff every time.
https://developers.google.com/android/ota#marlin
OTA is up.
7.1.1
Can this OTA be flashed over NPF26J?
New features are also included
From JCASE:
dePixel8 has been patched with the 7.1.1 update. Please dont ask for further support.
JAYNO20 said:
Can this OTA be flashed over NPF26J?
Click to expand...
Click to collapse
The full factory images are available so yes. Just remember to remove the -w command from the script so it won't wipe your data.
Rydah805 said:
The full factory images are available so yes. Just remember to remove the -w command from the script so it won't wipe your data.
Click to expand...
Click to collapse
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
JAYNO20 said:
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
Click to expand...
Click to collapse
I didn't try, sorry. I'd assume it'd work but I couldn't be sure as I already flashed the full image.
JAYNO20 said:
Can this OTA be flashed over NPF26J?
Click to expand...
Click to collapse
Try it out and let us know ?
I personally do fully images. Only have like 6 apps installed lol pretty quick set up
JAYNO20 said:
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
Click to expand...
Click to collapse
Yes it can. I just did it without problem.
---------- Post added at 01:33 PM ---------- Previous post was at 01:33 PM ----------
AmesCell said:
Are all 3 on the same version now?
Click to expand...
Click to collapse
There's only one version available for December.
cam30era said:
Yes it can. I just did it without problem.
Click to expand...
Click to collapse
Excellent!
Hey all, quick question and sorry if this should be in a different section...
I have the VZW Pixel, but used beups depixel8 for bootloader unlock. I am running stock NDE63V with a T-Mobile Sim. Can I flash the factory image with leaving out the bootloader? Or can I go ahead and just flash the whole image without the -w command.
Thanks!
Installing now, this better fix my lack of bluetooth in the car or I'm going to be sad.
Mrbobrowitz said:
Hey all, quick question and sorry if this should be in a different section...
I have the VZW Pixel, but used beups depixel8 for bootloader unlock. I am running stock NDE63V with a T-Mobile Sim. Can I flash the factory image with leaving out the bootloader? Or can I go ahead and just flash the whole image without the -w command.
Thanks!
Click to expand...
Click to collapse
Just take out the -w. I just did and all is good. ??
Sent from my Pixel XL
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?
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
scrin378 said:
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
Click to expand...
Click to collapse
No, ADB sideload will fail. 8.1 DP2 is on a newer branch than December 8.1 stable. You could install via fastboot or wait until Google pushes the OTA for preview users.
Sent from my Nexus 5X using Tapatalk
Opt out beta tester
mr.joshuanice said:
Opt out beta tester
Click to expand...
Click to collapse
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
luk.giak said:
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
Click to expand...
Click to collapse
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
scrin378 said:
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
Click to expand...
Click to collapse
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
No, i opt out from beta program, and then i get official version..i lose my data, but nothing special, most of pics, docs, etc...is on the cloud storage ..so no big deal for me.. good luck with patience
whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
luk.giak said:
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
Click to expand...
Click to collapse
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
whpsnp said:
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
Click to expand...
Click to collapse
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
luk.giak said:
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
Click to expand...
Click to collapse
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
whpsnp said:
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
Click to expand...
Click to collapse
:good:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Sent from my Nexus 6P using Tapatalk
OT
As a side note for all people who do not want to unlock the bootloader. Please consider at least to:
* activate developer options (tapping 7 times on the build number under phone information)
* enter developer options and activate 1) Debug USB and 2) Enable OEM Unlock
As you probably know, the nexus 6p is subject to the bootloop of death. It is hardware based and, when it happens, the only way to give a second life to the Nexus 6p is to flash a special boot.img (or kernel) that enable only 4 cores (over 8). You can perform this procedure only if you can unlock the bootloader. Hence, only if you have previously enabled the two options above (debug USB and Enable OEM Unlock).
---------- Post added at 07:17 PM ---------- Previous post was at 07:05 PM ----------
Ulver said:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Click to expand...
Click to collapse
Google is really messing up with OTAs. You should consider to manually flash a factory image or to adb sideload a full OTA (available on the official website).
Same situation for me, i get ota 8.1 ~ 10 December then 8.1 dp2 ota. And for now no ota I am still on security update from November...
One question, if im rooted, can i flash full OTA with flashfire??
sideload the DP2 to Final ota (Dec patch).
Then unenroll your device from beta, you will get an update (Jan patch)
https://android.googleapis.com/pack.../105818de493dde2bb290a13474a367f78ac6122f.zip
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 ?