As anyone received this ota yet? I don't want to unenroll from the beta stage and have to set my device up.
No!! I don't want to either.
Garner said:
As anyone received this ota yet? I don't want to unenroll from the beta stage and have to set my device up.
Click to expand...
Click to collapse
Final build seems to be built earlier than DP2. Two consequences:
1) You can not 'upgrade' from DP2 (NPF26F) to Final (NMF26F) with OTA, because it counts as downgrade.
2) If you flash final (NMF26F), it will still offer to upgrade to DP2 (NPF26F).
DP1 to Final is not offered either, because NPF26F is more recent, but you can flash OTA zip. I did with Flashfire.
elhana said:
Final build seems to be built earlier than DP2. Two consequences:
1) You can not 'upgrade' from DP2 (NPF26F) to Final (NMF26F) with OTA, because it counts as downgrade.
2) If you flash final (NMF26F), it will still offer to upgrade to DP2 (NPF26F).
DP1 to Final is not offered either, because NPF26F is more recent, but you can flash OTA zip. I did with Flashfire.
Click to expand...
Click to collapse
I flashed final NMF26F over DP2 NPF26F, then unenrolled from the beta. It did not wipe my phone, because I wasn't running beta firmware when I unenrolled. That took care of the System Update notification.
elhana said:
Final build seems to be built earlier than DP2. Two consequences:
1) You can not 'upgrade' from DP2 (NPF26F) to Final (NMF26F) with OTA, because it counts as downgrade.
2) If you flash final (NMF26F), it will still offer to upgrade to DP2 (NPF26F).
DP1 to Final is not offered either, because NPF26F is more recent, but you can flash OTA zip. I did with Flashfire.
Click to expand...
Click to collapse
So we continue to wait for the final build OTA? This is now wednesday thought we would have seen it by now 😶
Garner said:
So we continue to wait for the final build OTA? This is now wednesday thought we would have seen it by now 😶
Click to expand...
Click to collapse
Maybe we'll have to wait until the next security patch next year ! (in jan 2017)
This has got me thinking, the final build was the Maintenance release 1. What if we won't get a final because our current build is newer? And we will get another beta heading towards Maintenance release 2? (From Twitter)
Well that explains why manually flashing the OTA didn't do anything! I enrolled in the beta purely to get the final build quickly rather than waiting for the gradual roll-out. It's odd that this beta is a later build but the security patch date is from November when the release version is December. I don't really want to wipe to get back to the "older" version - am I stuck with betas until the next big release?
Last night I un enrolled from the beta and the phone updated itself to N5D91L and I did NOT lose any data.
A few minutes after that happened it gave me the 7.1.1 notification and after downloading and verifying the 7.1.1 build it would not auto install. I downloaded the OTA from google and sideloaded it with no problems what so ever. My phone is now running NMF26F with 0 issues and no loss of data.
Crazy Chuckster said:
Last night I un enrolled from the beta and the phone updated itself to N5D91L and I did NOT lose any data.
A few minutes after that happened it gave me the 7.1.1 notification and after downloading and verifying the 7.1.1 build it would not auto install. I downloaded the OTA from google and sideloaded it with no problems what so ever. My phone is now running NMF26F with 0 issues and no loss of data.
Click to expand...
Click to collapse
Can I just clarify, you went from DP2 to 7.0 OTA without losing any data at all?
LanguageSoez said:
No!! I don't want to either.
Click to expand...
Click to collapse
Why not?
Sent from my Nexus 5X using XDA-Developers mobile app
surrealjam said:
Can I just clarify, you went from DP2 to 7.0 OTA without losing any data at all?
Click to expand...
Click to collapse
No, it very much wipes it. Just did it myself and now have the "joy" of setting everything back up from scratch.
Sigh.
Noiz said:
No, it very much wipes it. Just did it myself and now have the "joy" of setting everything back up from scratch.
Sigh.
Click to expand...
Click to collapse
Thanks. Sorry you have to go through that pain.
surrealjam said:
Can I just clarify, you went from DP2 to 7.0 OTA without losing any data at all?
Click to expand...
Click to collapse
That is correct!
Crazy Chuckster said:
That is correct!
Click to expand...
Click to collapse
Hmm. Think I'll leave it but thanks for confirming. Your experience seems to contradict what others (and Google) say will happen. Maybe you're a lucky chap!
Still on DP2 has anyone else had the update yet?
Garner said:
Still on DP2 has anyone else had the update yet?
Click to expand...
Click to collapse
Nope. Doesn't exist yet sadly, or certainly not to my knowledge.
Related
Hello all,
I'm in the android beta program with my Pixel C and I've been on 7.1.1 for a couple of months, and now that's it's officially released, I've been waiting for it to come over the air for nearly 10 days now. I'm still on 7.1.1 but with the November security patch (NPF26H). I've got myself forcing the check for updates several times a day now lol. I'm in the midwest of America. Just wanting to know if I should keep patient or if there might be something wrong with my device finding the update.
Thanks!
I'm having the same problem so it's not your Pixel C. For some reason Google hasn't pushed out the update yet.
I was using the beta also, locked bootloader and everything and never got it. I just ended up flashing it manually since the files are available on Google's site.
Mine wont get it either and when i try to manual OTA it says I cant install an older version.
Also having this issue, and I do not wat to do a factory reset...
Sideloading OTA says the time stamp is Nov 4th, which it says is older than the Beta on my device. Anyone else getting this?
The final release is version NMF26H. The last preview is NPF26H. Is there any difference between the builds?
Paul1201 said:
The final release is version NMF26H. The last preview is NPF26H. Is there any difference between the builds?
Click to expand...
Click to collapse
To be honest, I don't think there are, aside from the security patch for December. My tablet really works fine, I'm just wondering why I'm not getting the update.
I'm hoping this update will fix the sluggishness since the last update.
Sent from my LG-H850 using Tapatalk
I got the update yesterday. I didn't do anything, it got pushed to my device on it's own. Hopefully, that will be the case for you guys, as well. Also, I left the beta program.
The Horak said:
I got the update yesterday. I didn't do anything, it got pushed to my device on it's own. Hopefully, that will be the case for you guys, as well. Also, I left the beta program.
Click to expand...
Click to collapse
Same here. Can't see a difference to last beta. Did you recognized something?
TheBready said:
Same here. Can't see a difference to last beta. Did you recognized something?
Click to expand...
Click to collapse
No. Not yet.
Just got mine yesterday evening. I'm in the beta program and had the DP on and got the OTA for 7.1.1 if that matters to anyone.
I have a quick question for those that are a lot smarter than I.
Still nothing for me on the 8.1.0 OTA December update. I have an unlocked Pixel 2 XL and an unlocked OG Pixel XL. I was running the Beta on my OG Pixel and I unenrolled from the Beta and factory reset. Waited 24 hours for a stable version of Android Oreo.... still nothing and it is still showing that I'm on 8.1.0 with the November security patch. Also, when I reset my phone or power back on it's still showing that my phone is on the Beta. I have no idea what's going on with it.
Would any of you guys/gals have any other suggestions? I'm not comfortable with flashing or anything like that since I've never done it before. Should I just wait patiently because it will come eventually?
Thanks.
Shrews824 said:
I have a quick question for those that are a lot smarter than I.
Still nothing for me on the 8.1.0 OTA December update. I have an unlocked Pixel 2 XL and an unlocked OG Pixel XL. I was running the Beta on my OG Pixel and I unenrolled from the Beta and factory reset. Waited 24 hours for a stable version of Android Oreo.... still nothing and it is still showing that I'm on 8.1.0 with the November security patch. Also, when I reset my phone or power back on it's still showing that my phone is on the Beta. I have no idea what's going on with it.
Would any of you guys/gals have any other suggestions? I'm not comfortable with flashing or anything like that since I've never done it before. Should I just wait patiently because it will come eventually?
Thanks.
Click to expand...
Click to collapse
I got my Dec 5th patch update last night, so I'm sure it's only a matter of time for you.. If you're not comfortable flashing, than I would say just wait it out. It shouldn't be long.
What the poster above me said, just wait you will eventually get it. They roll it out in stages so they don't overload the servers. We all like instant gratification, which is why a lot of people flash it when it is released, but you will get it.
COMTB said:
What the poster above me said, just wait you will eventually get it. They roll it out in stages so they don't overload the servers. We all like instant gratification, which is why a lot of people flash it when it is released, but you will get it.
Click to expand...
Click to collapse
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Shrews824 said:
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Click to expand...
Click to collapse
When you unenroll, it will send you an OTA. Did you get that OTA? You mentioned you factory reset, but that's not what actually takes you off of the beta.
thacounty said:
When you unenroll, it will send you an OTA. Did you get that OTA? You mentioned you factory reset, but that's not what actually takes you off of the beta.
Click to expand...
Click to collapse
No, I did not get an OTA. I've checked on the site and it says that my device is no longer enrolled, however when I restart my phone (from a powered off standpoint) it still says I'm enrolled in the Beta. I check for an update and it says I'm up to date, yet it's running 8.1.0 with the November 5th security patch.
Sorry for so many questions, but I just thought I might be missing something. It's really not that big a deal to me because I know it will come eventually, but I just wondered why it was doing that. I reached out to Google via the chat and they said wait 24 hours for a stable version however it's been well over 24 hours and still nothing. I've unenrolled the device from previous beta's and have never had to wait. The OTA would immediately show up and I was good to go.
Is it safe to take the actual ota while rooted/TWRP/custom kernel? Will it just replace the boot partition or will it fail? I'm thinking I should do a flash all with the -w removed of the 8.1 instead of letting it go the ota. I just got the notification for it.
Shrews824 said:
Any idea on why my original Pixel XL is still showing that I'm in Beta though? That's really what's confusing me.
Click to expand...
Click to collapse
DId your OG Pixel XL get the officialy release?
COMTB said:
DId your OG Pixel XL get the officialy release?
Click to expand...
Click to collapse
No, it hasn't received the latest 8.1.0.
Shrews824 said:
No, I did not get an OTA. I've checked on the site and it says that my device is no longer enrolled, however when I restart my phone (from a powered off standpoint) it still says I'm enrolled in the Beta. I check for an update and it says I'm up to date, yet it's running 8.1.0 with the November 5th security patch.
Sorry for so many questions, but I just thought I might be missing something. It's really not that big a deal to me because I know it will come eventually, but I just wondered why it was doing that. I reached out to Google via the chat and they said wait 24 hours for a stable version however it's been well over 24 hours and still nothing. I've unenrolled the device from previous beta's and have never had to wait. The OTA would immediately show up and I was good to go.
Click to expand...
Click to collapse
At this point I would sideload and hope the Check for Update is fixed in January as expected.
thacounty said:
At this point I would sideload and hope the Check for Update is fixed in January as expected.
Click to expand...
Click to collapse
Well, I had mentioned in the original post that I'm not extremely comfortable doing that so I may just wait it out.
I have a question in regards to getting the OTA updates.
I'm in Australia and got my pixel 2 xl on a plan with Telstra as they are the exclusive carrier here. But I use a Vodafone sim in the phone.
Will this cause me to not get the OTA updates?
My 6X just received an OTA. The security patch level went from March 1st to Oct 5th. The EMUI version was updasted to 5.0.1. So far so good, I haven't used it much.
Akopps said:
My 6X just received an OTA. The security patch level went from March 1st to Oct 5th. The EMUI version was updasted to 5.0.1. So far so good, I haven't used it much.
Click to expand...
Click to collapse
But, those updates are gradual? since my cell phone has not received it
I have gotten an OTA update as well. Not sure if it's going to remove my root or not so I'm not going to update
patrick8996 said:
I have gotten an OTA update as well. Not sure if it's going to remove my root or not so I'm not going to update
Click to expand...
Click to collapse
Same here.
Yep it will remove you current root... Cause i just updated too it a few hours ago which i did not have root but i had my bootloader unlock. And yep my bootloader is locked ... I have always herd ota updates doeisnt relock the bootloader???
Not going too unlock it again cause i was waiting for 8.0 if and when it comes anyways. That and i have my phone setup the way i want it not going threw it again at the moment lol..
iamshadow2008 said:
Same here.
Click to expand...
Click to collapse
You can't update without removing root
iamshadow2008 said:
Same here.
Click to expand...
Click to collapse
You need to remove root, flash stock boot and stock recovery before you download the ota for installation.
Just updated but now Google Assistance no longer works and fail to connect.
I have to clear Google app all data to make it run
e20140 said:
Just updated but now Google Assistance no longer works and fail to connect.
I have to clear Google app all data to make it run
Click to expand...
Click to collapse
Factory reset..
Wow. Two system updates in the last 10 days. Just updated BLN-L24C567 to B366 from B365. Security patch is Nov. 6.
I guess this makes Huawei/Honor phones a lot better than Lenovo Moto phones. Once I recommended my father to buy a (Lenovo) Moto X Pure. The phone received updates something twice a year (!), and its Nougat update came 13 months (!) after the official Nougat release, and maybe 10 months after when Lenovo promised this update would be available. Huawei has a better track record than Lenovo IMHO.
13 months is a lot, and yes, Huawei/Honor has been better in the recent years when it comes to updates
Indeed. They give update if want to else simply discard. btw see what Apple was doing with regular updates.. they admitted and was a let down for many (but accepting it needs some real guts for a brand like Apple)
Who knows other OEMs who gives regular updates are doing similar things
edit: scratch that
Im sorry...this is probably a dumb question, but can't confirm one way or another, even when searching...
I was under the assumption when I signed up for 8.1 beta, that when the official release rolled out it's automatically install and I'd be back to the official version and then keep getting the monthly security updates.
I haven't gotten the January update and it still says I'm enrolled on the website. I understand if unenroll before the official release, my phone will be wiped... Does this still apply, assuming I'm on the final release?
Screenshot attached of info. Thank you for any help!
InfiniteReality said:
Im sorry...this is probably a dumb question, but can't confirm one way or another, even when searching...
I was under the assumption when I signed up for 8.1 beta, that when the official release rolled out it's automatically install and I'd be back to the official version and then keep getting the monthly security updates.
I haven't gotten the January update and it still says I'm enrolled on the website. I understand if unenroll before the official release, my phone will be wiped... Does this still apply, assuming I'm on the final release?
Screenshot attached of info. Thank you for any help!
Click to expand...
Click to collapse
If you unenroll before the official release, the yes, your phone would have been wiped. However, you should be ok now. This is from reading things in the P2XL forums, not personal experience.
Badger50 said:
If you unenroll before the official release, the yes, your phone would have been wiped. However, you should be ok now. This is from reading things in the P2XL forums, not personal experience.
Click to expand...
Click to collapse
Thanks for the reply! That's my assumption as well, I just can't 100% confirm it. It wouldn't be the worse thing if it wiped it, but would rather not have to copy 100gb worth of stuff just in case.....and would rather not have to set it up again.
Anyone 100% know?
Took the gamble anyways, so wanted to update in case anyone else happened to be searching for the same answer.
It does NOT wipe your phone, just have to make sure you are indeed are on the official release and all should be good.
Maybe this was posted already, but my search skills seem to be failing me at the moment. :silly:
Is there a way to do an in place OTA update from pie to Android 10 Q keeping Magisk root?
Or do I have to do the old way and revert pie, take the OTA, then apply the patched boot.img?
Thanks for any help!
You could revert and take the update or revert and flash Q via fastboot. Either way you'll have to root again after.
Pixel 3 XL, Yep, Crashed It.....
..... Again.
What I usually do is grab the current months image (in this case november), move the boot.img to my device, patch it with Magisk, move it back to my computer. Grab the OTA for the current month, sideload via fastbootd, after successful reboot I just go back into fastboot and flash the patched_boot.img.
Sounds like a lot, but usually takes only a few minutes after the downloads are complete.
In case anyone was wondering, now that Magisk is updated to 20.1, I was able to do an in place OTA upgrade from Android 9 to Android 10 following the Magisk tutorial here: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
My laziness paid off and I only waited a couple of months! :laugh:
ilikecl said:
In case anyone was wondering, now that Magisk is updated to 20.1, I was able to do an in place OTA upgrade from Android 9 to Android 10 following the Magisk tutorial here: https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
My laziness paid off and I only waited a couple of months! :laugh:
Click to expand...
Click to collapse
Has your Pixel taken the January 2020 update yet?
statustray said:
Has your Pixel taken the January 2020 update yet?
Click to expand...
Click to collapse
Yup. Did an in-place OTA upgrade for the Jan 2020 update as well.
ilikecl said:
Yup. Did an in-place OTA upgrade for the Jan 2020 update as well.
Click to expand...
Click to collapse
I'm with vzw, and my device has not listed the January 2020 update. In fact, via OTA, I am on:
Build number: QP1A.191005.007
statustray said:
I'm with vzw, and my device has not listed the January 2020 update. In fact, via OTA, I am on:
Build number: QP1A.191005.007
Click to expand...
Click to collapse
I'm on Visible, which should be the same as VZW.
But I guess maybe Visible doesn't have to go through testing the bloatware that comes on VZW builds before releasing the OTA...?
Dunno.
ilikecl said:
I'm on Visible, which should be the same as VZW.
But I guess maybe Visible doesn't have to go through testing the bloatware that comes on VZW builds before releasing the OTA...?
Dunno.
Click to expand...
Click to collapse
Yeah that very well could be. I'm going to check my better half's phone and see if her has taken a new OTA yet. We're both vzw with google edition phones - my model is Pixel 3 XL, and hers is Pixel (OG).
Thanks.