7.1.1 factory images are live and Verizon says they're starting to push out today.
http://www.droid-life.com/2016/12/05/android-7-1-1-update-factory-images-goes-live-pixel-nexus/
http://www.droid-life.com/2016/12/05/verizon-says-pixel-updates-arrive-today-build-nmf26o/
https://developers.google.com/android/ota#marlin
Link to OTA is up
Downloading
No more depixel8
http://forum.xda-developers.com/pixel/help/psa-android-7-1-1-update-blocks-depixel8-t3513549
I unlocked my Verizon Pixel XL using dePixel8 then manually flashed the 7.1.1 stock image. Will I be unable to unlock the bootloader if I lock it?
mister2sc said:
I unlocked my Verizon Pixel XL using dePixel8 then manually flashed the 7.1.1 stock image. Will I be unable to unlock the bootloader if I lock it?
Click to expand...
Click to collapse
No. Do NOT lock it....ever
dablitzkrieg said:
No. Do NOT lock it....ever
Click to expand...
Click to collapse
This guy has the right idea ?
Sent from my Pixel XL using Tapatalk
I took the update last night. Now my Bluetooth in the car stopped working. It connects but no sound goes through the car.
Erase the pairing and start again
I will give that a try when I get off of work
iceman4357 said:
https://developers.google.com/android/ota#marlin
Link to OTA is up
Click to expand...
Click to collapse
I unlocked my bootloader and have a pixel xl from Verizon. I wanted to root and have twrp. I'm new to the whole command prompts to update. Should I do this OTA or use one of the ROM's under the other section that someone has posted?
Wonder if with all the production pressure the Verizon phones not yet delivered will have the update and be unable to be unlocked?
Related
So i unrooted my 6p yesterday and then locked my bootloader today, how long will it take for the notification for an update to pop up?
Im running 6.0.1 with Build Number MTC20F
I am in the UK, my provider is Vodafone, if that makes a difference.
I havent upgraded to android N yet, but from reading, you need to be enrolled in the Android Beta program to get the OTA as of now. Also the bootloader being locked or unlocked shouldn't make a difference.
DeathGrind said:
I havent upgraded to android N yet, but from reading, you need to be enrolled in the Android Beta program to get the OTA as of now. Also the bootloader being locked or unlocked shouldn't make a difference.
Click to expand...
Click to collapse
Cheers, I keep hearing about people getting the update, and all sources keep saying different things, one site says its released and 6p users can get it and another will say its still rolling out. Same goes for the bootloader, one site says it makes a difference and the other will say it doesn't. Guess ill have to wait. Again, cheers.
So, I just went through and made my phone stock MTC20F, but bootloader is still unlocked, enrolled for the beta program at https://www.google.com/android/beta?u=0, and check system updates and instantly got the update to download. So i can confirm that your bootloader doesn't matter and you need to be enrolled.
sid.parmar said:
So i unrooted my 6p yesterday and then locked my bootloader today, how long will it take for the notification for an update to pop up?
Im running 6.0.1 with Build Number MTC20F
I am in the UK, my provider is Vodafone, if that makes a difference.
Click to expand...
Click to collapse
You don't need to re-lock the bootloader or unroot to accept the OTA. You just need to flash stock recovery.
dratsablive said:
You don't need to re-lock the bootloader or unroot to accept the OTA. You just need to flash stock recovery.
Click to expand...
Click to collapse
So ur saying that you can accept the OTA while rooted? Will this work with dp5 rooted with encryption and just revert to stock recovery? (BC right now I'm on the newest twrp)
Sent from my Nexus 6P using XDA-Developers mobile app
ArmStrongDickPunch said:
So ur saying that you can accept the OTA while rooted? Will this work with dp5 rooted with encryption and just revert to stock recovery? (BC right now I'm on the newest twrp)
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
If your system is modified, then the OTA won't work. This works with a systemless root.
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
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Sadly no.
Thanks I had a feeling
Have you even tried?
Scott said:
Have you even tried?
Click to expand...
Click to collapse
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
cam30era said:
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
Did this myself. Unlocked bootloader, rolled back from Q to O. Was unable to flash OTA (with locked bootloader), due to being older.
So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk
ahent said:
So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....
Thanks, I hope it just pushes OTA I don't want to mess with flashing it. By the time I get around to flashing it January may be out and it will be a moot point.
Sent from my Pixel XL using Tapatalk
cam30era said:
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
---------- Post added at 09:02 PM ---------- Previous post was at 09:01 PM ----------
cam30era said:
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....
Click to expand...
Click to collapse
IMHO I think the band 4 issues is pseudo.. since it does not update the radio or boot at all.. Unless its a "setting" that's changed that makes it work.
clockcycle said:
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
Unlocked bootloader definitely makes a difference, you can't flash a factory image without it.
Click to expand...
Click to collapse
mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Return the phone if you can and get another one. Odds are that the stock on the shelves hasn't been updated yet.
Sent from my Pixel XL using XDA Labs
As the subject? ?
Wondering the same myself. I have not.
Someone did mention on an Android site that the beta users should see the OTA pushed in the next few days.
iceman4357 said:
Wondering the same myself. I have not.
Someone did mention on an Android site that the beta users should see the OTA pushed in the next few days.
Click to expand...
Click to collapse
I've known it take over a week to appear ?
I think they prioritise all the older builds first then push it to us beta users ?
I'll not taking it until there's a way to unlock the bootloader Verizon's March ota update boo. It was too late when the Verizon rep was setting this phone up..
Sent from my Pixel XL using Tapatalk
sykoj82 said:
I'll not taking it until there's a way to unlock the bootloader Verizon's March ota update boo. It was too late when the Verizon rep was setting this phone up..
Click to expand...
Click to collapse
Its been relocked since last fall. It ain't happening man. Very sorry.
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse
Doubt it will wipe. But you could flash the whole image removing the -w from the bat file.
iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse
You can't.
Sent from my Pixel using XDA-Developers Legacy app
---------- Post added at 05:00 PM ---------- Previous post was at 04:59 PM ----------
TonikJDK said:
Doubt it will wipe. But you could flash the whole image removing the -w from the bat file.
Click to expand...
Click to collapse
Only if you are bootloader unlocked.
Sent from my Pixel using XDA-Developers Legacy app
just flash the system img only
pretty simple
I just got the 7.1.2 image OTA on my Pixel XL and Project Fi. My wife's Pixel hasn't got it yet.
Never used an OTA always flash image simple and no problems, I remember in the past sometimes battery drain etc after installing a OTA
no joy yet here on Google Store Pixel XL on Verizon.
Stevez48 said:
no joy yet here on Google Store Pixel XL on Verizon.
Click to expand...
Click to collapse
I've been seeing delays in the Verizon rollout with this OTA, not sure why. I have a vzw Pixel however I'm on Project Fi and got the ota almost immediately. I'm not sure if that changes it or not, however.
We also need separate threads or disclaimers for those with locked bootloaders and those unlocked. To say just flash the image instead of sideloading the ota is ludicrous if the bl is locked. That simply can't be done.
aspexil said:
I just got the 7.1.2 image OTA on my Pixel XL and Project Fi. My wife's Pixel hasn't got it yet.
Click to expand...
Click to collapse
Was your pixel on beta release 2?
Garner said:
Was your pixel on beta release 2?
Click to expand...
Click to collapse
No. It was at v7.1.1 stock.
aspexil said:
No. It was at v7.1.1 stock.
Click to expand...
Click to collapse
Ahh right this thread was intended for people on the beta release ?
I haven't received the OTA yet, I'm on beta 2. I downloaded the update and tried to sideload it, but the installation failed because it says that the beta 2 is a newer build and it won't downgrade. I guess I'll just wait until the OTA from my carrier.
sideloaded the OTA file over Beta 2 tuesday morning and all went fine...have at it! :good:
iceman4357 said:
has anyone flashed the OTA over the beta? Wondering if it will wipe the phone or not.
Click to expand...
Click to collapse
nozzleman_85 said:
sideloaded the OTA file over Beta 2 tuesday morning and all went fine...have at it! :good:
Click to expand...
Click to collapse
Impossible.
Sent from my Pixel using XDA-Developers Legacy app
Haha yes. Not possible at all to load the existing OTA on the beta build. Google has to release a separate OTA build which it hasnt yet
bobby janow said:
Impossible.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://developer.android.com/preview/download.html
You'll need an unlocked bootloader to flash the images.
You can also sign up for the ota program without an unlocked bootloader being required:
https://g.co/androidbeta
skaforey said:
https://developer.android.com/preview/download.html
You'll need an unlocked bootloader to flash the images.
You can also sign up for the ota program without an unlocked bootloader being required:
https://g.co/androidbeta
Click to expand...
Click to collapse
Thanks!
My phone is not here yet, should arrive today, so I'm going to hold off until I decide that I'm keeping it.
I will enroll my OG Pixel though!
Deleted
Salval said:
That isn't for our devices.
Click to expand...
Click to collapse
They just haven't updated that yet. The system images are available for the 2 and 2 XL so it certainly is for our devices.
I have flashed 8.1 on my XL but it seems to just sit at the Google logo. Verified the checksum so I know the download is fine. Any ideas?
clnzx2 said:
I have flashed 8.1 on my XL but it seems to just sit at the Google logo. Verified the checksum so I know the download is fine. Any ideas?
Click to expand...
Click to collapse
How long you been waiting at the google logo? May take awhile for it to load up
20 minutes+
It doesn't show my new Pixel XL 2 in the ota beta list, just my old Pixel XL.
OTA's are not ready yet for the 2 line - they require manual flash.
But, for what it's worth, I (re)enrolled my OG Pixel and the OTA has not dropped yet.
---------- Post added at 12:35 PM ---------- Previous post was at 12:35 PM ----------
OTA's are not ready yet for the 2 line - they require manual flash.
But, for what it's worth, I (re)enrolled my OG Pixel and the OTA has not dropped yet.
clnzx2 said:
20 minutes+
Click to expand...
Click to collapse
That's kinda long
Images seem bad, flashed successfully and get a device corrupt error. Flash back to 8.0 and things work just fine again. No luck flashing the OTA as well from 8.0 (OPD1.170816.010)
beerbaronstatic said:
Images seem bad, flashed successfully and get a device corrupt error. Flash back to 8.0 and things work just fine again. No luck flashing the OTA as well from 8.0 (OPD1.170816.010)
Click to expand...
Click to collapse
Same here
clnzx2 said:
Same here
Click to expand...
Click to collapse
Color me three!
Whew...thought I had a bunk device.
Welp.
Is it stable? Anything annoying?
Is HDR processing faster as they say it should be?
To those asking "is it stable" or "what's changed" - I don't believe anybody has successfully gotten 8.1 on their Pixel 2 XL yet. I'm with those above who get the red "corrupt" screen and then essentially hangs on a google logo. I went back to the bootloader to reinstall 8.0.
Has anyone tried sideloading the ota file?
https://developer.android.com/preview/download-ota.html
Pixel 2 XL is in the beta list now for the enrollment. I haven't received the update yet though
It boots
Sent from my Pixel 2 XL using Tapatalk
danon.brown said:
It boots
Click to expand...
Click to collapse
OTA or factory image?