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
Related
guys
http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=14836&pid=107979
asus said they cancelled this update due to unstable update...
1st i dont know what is unstable in this version[same as previous and new bug of call screen animation
2nd lol which update came without new bugs?
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
luisoman2000 said:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
Click to expand...
Click to collapse
ya same here..but what they will do to unlocked phones/??
ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
ansebovi said:
guys
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
Click to expand...
Click to collapse
That was my first guess as well
TheSSJ said:
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
Click to expand...
Click to collapse
no i am asking about bootloader[can they lock it somehow if we flash next ota]
Harfainx said:
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
Click to expand...
Click to collapse
so how can we update from here after ??? need to modified by someone for flashing ???
jaysus145 said:
That was my first guess as well
Click to expand...
Click to collapse
ya my 1st thought too,, haha
ansebovi said:
so how can we update from here after ??? need to modified by someone for flashing ???
Click to expand...
Click to collapse
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Harfainx said:
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Click to expand...
Click to collapse
well i am from sony device..they release main update of android..and 1 bug fix,thats all...so we dont care..and no need to worry about relocking issues..
this is the first asus device...man they releasing update for every 10days..i thought we could apply just like that..but since they didnt gave unlocked bootloader tool ,i got these doubt..
and thanks for info..
so i must wait for zips which is modified for unlocked bootloader[if they trying to relock]
I honestly doubt they're going to find a way to relock it with an update, but who knows what voodoo they may come up with.
Either way, we'll grab the updates and get them ready to be flashed quickly. It's a simple process.
I highly doubt he will do anything regarding unlocking/locking bootloader. because:
1. last year they released their official tool to unlock zenfone 4,5,6 bootloader after 3-4 months of release.
2. This year when they launched the zf2 in US they hold contest and developer events via xda. Now xda is a place where no one keeps their bootloader locked. so they knew exactly where they are releasing and advertising the product.
So I dont think they would even bother about this bootloader . Maybe it is an unstable build in terms of their quality test.
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Everthings here http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Even if your phone gets here on a newer version (it won't), you could always downgrade everything and unlock from there. =)
Shakalaka has backups of everything going back to like version 2.12 or 2.13.
MatteXperiaU said:
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
Click to expand...
Click to collapse
Problem is they can't support any ROM that isn't official on the zenfone. They'll pass you off. Like most manufacturers.
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
damian5000 said:
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
I downloaded the appropriate OTA the other night, so if ASUS pulls the file, I still have it and can share it on Dropbox and/or Copy.
I get the phone today! So hopefully tonight I get the OTA up to 2.18 and then wait to see what upcoming 2.20 has to offer. If we can still unlock the BL with 2.20, I will let that OTA happen. Similarly if we find out that those who unlocked their bootloaders can't take the update (at that point I will cry a little, if there is no official way to unlock BL released with the update ).
If both scenarios above are false, then I will apply my downloaded 2.19, unlock the bootloader, then accept 2.20.
Best one could do eh?
---------- Post added at 07:24 ---------- Previous post was at 07:19 ----------
ansebovi said:
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
Click to expand...
Click to collapse
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
joel.maxuel said:
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
Click to expand...
Click to collapse
no i didnt mean it will relock,..
but the unlocked needed some file right..it modifies something right? ...and it is not present in old things..so can old fw run on unlocked bootloader? [or would it get bootloop or damage bootloader]
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
Mayor news, Nougat Preview is open now, check this thread for more information.
https://community.zteusa.com/message/73727
Go there and register and have some Nougat fun.
EDIT : this is an important information mentioned in the main thread back in Z-Community, so KEEP THAT IN MIND or ask question before proceeding and i mean don't ask them here
Important disclaimer: There is a likelihood that personal data on your device may be lost during the software upgrade process, so a complete backup is highly recommended prior to this upgrade. Furthermore, the ability to roll back from Nougat to Marshmallow will not be supported.
Click to expand...
Click to collapse
UPDATE 12-12-2016
Re: Axon 7 (A2017U) US Nougat Preview
aerospaceman aerospaceman Employee Dec 12, 2016 1:28 PM (in response to aerospaceman)
Hello Community Members. We have received an overwhelming response to our Nougat preview. At this time new applications are closed. If you have been chosen to participate you will be receiving an e-mail with further instructions within the next few days. Thank you to everyone who submitted their application!!
Your Z-Community Team
Click to expand...
Click to collapse
They say there's an NDA, but the actual agreement can't be seen while signing up...? Anyway good luck to people who signs up!
kgptzac said:
They say there's an NDA, but the actual agreement can't be seen while signing up...? Anyway good luck to people who signs up!
Click to expand...
Click to collapse
So that means that anyone who signs up isn't gonna be able to tell us if MiFavor is gone or not with Nougat? That's all I want to hear.
I also want to know if the t-mobile wifi calling and other memory/power management optimization situation has improved. Hopefully the NDA allows that (likely not, lol)
Who knows what the NDA will and will not allow - all you are doing right now is signing up to be a part of the experiment. Not everyone who signs up will be accepted (I hope I am accepted)
Signed up. We will see what happens.
I applied but probably won't get update. I am already rooted with unlocked bootloader.
i think we need a stock rom tool via fastboot or qfil. actually zte said that they would give but there is no news about it.
so i have to wait. i think @DrakenFX or @Unjustified Dev will make it which can be flash via TWRP
Signed up, we'll see.
It won't void warranty for anyone asking.
I signed up. I love beta testing new OS's.
Sent from my ZTE A2017U using Tapatalk
kgptzac said:
I also want to know if the t-mobile wifi calling and other memory/power management optimization situation has improved. Hopefully the NDA allows that (likely not, lol)
Click to expand...
Click to collapse
Power management needs to be fixed, encryption would be nice, and this weird issue where you can't use your photos from google photos as wallpapers.
kgptzac said:
They say there's an NDA, but the actual agreement can't be seen while signing up...? Anyway good luck to people who signs up!
Click to expand...
Click to collapse
After you apply, they will pick who they accept. After you get accepted, then you get the NDA to sign or not sign. If you choose to sign it, then your IMEI gets added to the list and they push out all the extra updates. You can basically refuse at any point up to when you get updates (since apparently you can't go back to Mashmallow).
I unlocked my bootloader... can i still get in on this?
spacemanvt said:
I unlocked my bootloader... can i still get in on this?
Click to expand...
Click to collapse
You should ask that question at the zte community. but probably not.
spacemanvt said:
I unlocked my bootloader... can i still get in on this?
Click to expand...
Click to collapse
Apparently the previous OTAs haven't checked for unlocked bootloader, so unless they changed that for this OTA, you should be able to get it.
http://forum.xda-developers.com/showpost.php?p=70006569&postcount=16
abdi7451 said:
Apparently the previous OTAs haven't checked for unlocked bootloader, so unless they changed that for this OTA, you should be able to get it.
http://forum.xda-developers.com/showpost.php?p=70006569&postcount=16
Click to expand...
Click to collapse
But how do we get back to stock recovery so we can flash the updates?
Signed up. Hoping the beta starts soon. Can't wait to see if they moved from MiFlavor or not.
borijess said:
But how do we get back to stock recovery so we can flash the updates?
Click to expand...
Click to collapse
1- boot to TWRP
2- Tap Mount
3- Check SYSTEM-READ-ONLY
4- Wipe Dalvik, Cache, Data and System
5- Flash my B29.StockSystem
6- Reboot (there's probably going to be a message about NO OS , just ignore and slide to reboot.
Once full boot, reboot back to Recovery to check if stock recovery is in place and reboot if it is..
Signed up.
However I have a question. I own A2017U model but if i reside outside of U.S. does it disqualify me to participate?
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
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?