Just got my automatic Google Project Fi 6.0 update. Currently downloading. Will update you guys once finished.
Excited.
wrxphantom said:
Just got my automatic Google Project Fi 6.0 update. Currently downloading. Will update you guys once finished.
Excited.
Click to expand...
Click to collapse
ok, so what? its the same ota that everyone is getting..
wrxphantom said:
Just got my automatic Google Project Fi 6.0 update. Currently downloading. Will update you guys once finished.
Excited.
Click to expand...
Click to collapse
Build MRA58K?
It's taking longer than expected, huh?
cam30era said:
Build MRA58K?
Click to expand...
Click to collapse
Gerle said:
It's taking longer than expected, huh?
Click to expand...
Click to collapse
simms22 said:
ok, so what? its the same ota that everyone is getting..
Click to expand...
Click to collapse
It is the Project Fi 6.0 Version not the standard MRA58K 6.0 update.
This is a Project Fi ONLY 6.0 update.
It took a while because it kept giving me an error which ended up being because I was rooted. All I had to do was unroot and the update installed.
Sent from my Nexus 6 using Project Fi
wrxphantom said:
It is the Project Fi 6.0 Version not the standard MRA58K 6.0 update.
This is a Project Fi ONLY 6.0 update.
It took a while because it kept giving me an error which ended up being because I was rooted. All I had to do was unroot and the update installed.
Sent from my Nexus 6 using Project Fi
Click to expand...
Click to collapse
Well the info you posted shows MRA58k and the same radio.
Yeah its a unified build now... And its been available for weeks? If this was something different, google would have the image up on their webpage...
wrxphantom said:
It is the Project Fi 6.0 Version not the standard MRA58K 6.0 update.
This is a Project Fi ONLY 6.0 update.
Click to expand...
Click to collapse
Yes, there is a specific update OTA for the Fi-specific build on 5.1.1. There is another specific update for the T-Mobile build, and yet another OTAs for the general Nexus build (everyone else.) But all those OTAs result in the same destination build, MRA58K, which is unified.
Can confirm its a unified build
Sent from my Nexus 6 using XDA Free mobile app
Related
My 6p shipped with build MDA89D. I know that build L is out and expected the OTA but software update says I have the latest update. Flashing the factory image wipes all data and I just got this set up, so I'd rather not do that. How long does it usually take to get the OTA or is there a link I can sideload directly from?
luminaldust said:
My 6p shipped with build MDA89D. I know that build L is out and expected the OTA but software update says I have the latest update. Flashing the factory image wipes all data and I just got this set up, so I'd rather not do that. How long does it usually take to get the OTA or is there a link I can sideload directly from?
Click to expand...
Click to collapse
I'm on TMO and the build that I got updated to was MDB08K. What is this L build you speak of?
mgorman said:
I'm on TMO and the build that I got updated to was MDB08K. What is this L build you speak of?
Click to expand...
Click to collapse
Actually, looks like there's an M too. Factory images for Nexus 6p devices: https://developers.google.com/android/nexus/images?hl=en
mgorman said:
I'm on TMO and the build that I got updated to was MDB08K. What is this L build you speak of?
Click to expand...
Click to collapse
The latest build is ' MDB08L '. I received the OTA 2 days ago and I'm on TMO.
@OP: OTA roll out in batches. It takes time.
Google announced the Android 7
https://www.android.com/versions/nougat-7-0/
has anyone got it yet?
some guys on g+ posted screenshots of the ota
Nope
Sent from my Nexus 5X using XDA-Developers mobile app
FUHHHKKKK..
spent all day at work today setting up pure nexus with elemental and other sound mods/xposed/etc, only for this to happen today.
Anxiously awaiting factory images to be released.
Do we need to leave the beta program to install with wipe or will it update over the beta do you think?
lukeaddison said:
Do we need to leave the beta program to install with wipe or will it update over the beta do you think?
Click to expand...
Click to collapse
Will update over the beta
lukeaddison said:
Do we need to leave the beta program to install with wipe or will it update over the beta do you think?
Click to expand...
Click to collapse
You'll get ota update without wipe. But I will do factory reset after all those dirty flashes
7.0
Ladies and gentlemen. He is here
Getting the update now...
Sent from my Nexus 5X using Tapatalk
noidea24 said:
FUHHHKKKK..
spent all day at work today setting up pure nexus with elemental and other sound mods/xposed/etc, only for this to happen today.
Anxiously awaiting factory images to be released.
Click to expand...
Click to collapse
Only Android guys can do this...
d14r1 said:
View attachment 3850887View attachment 3850888
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
What about the update size?
Update: Yes it's true I got it
I also have it now in the UK
the guys who have just got the update, are you rooted on the dev preview?
crian said:
the guys who have just got the update, are you rooted on the dev preview?
Click to expand...
Click to collapse
Not me
just enroll into the beta and you'll get the update to the latest, final, nougat 7.0
You all suck! im hitting f5 every few seconds looking for a factory image and cant find one yet!
i havent been this excited since the first time i touched a boob!
OTA showed up. Downloaded it and .. it goes to TWRP!
I'm rooted! OTA won't work
Arghhhhhh
Preview site return 404
https://developer.android.com/preview/download.html
Factory images should be here, right?
https://developers.google.com/android/nexus/images
OTA link (from DP5): https://android.googleapis.com/pack.../669d3f9d14ba1f79840304dd1f19dc8024830573.zip (saw it on a Reddit post)
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
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.
December images for Android 8.1 Oreo
Official factory images
Official full OTA images
Build OPM1.171019.011 - non-operator-specific
Nice. Upgrade time
Anyone capture any OTAs?
So it's a zip c. I just wipe and flash I. TWRP?
isnt that dev preview link?
nvm Google updated the page
flex360 said:
isnt that dev preview link?
Click to expand...
Click to collapse
Its the Final Build
Anyone on Verizon locked bootloader...enroll in the beta program and you will automatically get the official version
https://www.google.com/android/beta
flex360 said:
isnt that dev preview link
Click to expand...
Click to collapse
DP images were opp1 to opp4. These are release images, opr6.
Tylog said:
Its the Final Build
Click to expand...
Click to collapse
Whats the difference between System images and Factory images?
This link shows the System images. So we can have final build with flashing these images?
Kisakuku said:
Android 8.0 - Oreo
Official factory images
Build opr6.170623.011 - Telstra, Rogers, TMoUS, Sprint, USCC, Project Fi
Build opr6.170623.012 - other carriers
Click to expand...
Click to collapse
which one is Verizon? i am guessing the "other carriers"?
Why the images aren't available here? https://developers.google.com/android/images
fletch33 said:
which one is Verizon? i am guessing the "other carriers"?
Click to expand...
Click to collapse
Yes.
Kisakuku said:
Yes.
Click to expand...
Click to collapse
Thanks
It says developer preview when image is clicked upon to download.
Installed, clean flash, apps uddated and smooth like butter !!
matlear said:
Installed, clean flash, apps uddated and smooth like butter !!
Click to expand...
Click to collapse
Were you rooted?
ithehappy said:
It says developer preview when image is clicked upon to download.
Click to expand...
Click to collapse
You can't expect perfection from a Google roll-out ) The point is, these are release builds, but the site still hasn't been fully updated.
Successfully flashed the update and kept my apps and data by removing the -w from flashall.bat
Sent from my Google Pixel XL using XDA Labs
Just got OTA for beta
EDIT: Leaving the below link, but it's confirmed as garbage. Looks like Google sent out a bad OTA and they're retracting it now. :|
From OPP4:
https://ota.googlezip.net/packages/.../80cafb69c50be0fb6ed197998bd7434b26155355.zip
Note: While my device got the OTA update notification, it's refusing to actually update to that build, complaining about a manifest mismatch - so YMMV on this link.
GroovinChip said:
Successfully flashed the update and kept my apps and data by removing the -w from flashall.bat
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
did you flash the system image and do that, and over what version did you flash?
I'm looking to do this from 7.1.2, but wasnt sure if it would work, or how to do it properly. Any help in how you do it would be appreciated!