Related
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.
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.
It appears the official Nougat update for the VZW S7/S7 Edge has been spotted out in the open.
http://www.androidpolice.com/2017/0...7-edge-now-receiving-official-nougat-updates/
I'm going to wait and see how it goes before accepting it. So far, checking for an update, I am still told that my MM phone is up-to-date, so it hasn't been pushed out to my IMEI range yet apparently.
Here's a couple more articles about it being released starting today, and probably to the beta testers first:
http://www.droid-life.com/2017/03/06/verizon-galaxy-s7-edge-nougat-update-vru4bqa2/
http://www.androidauthority.com/verizon-samsung-galaxy-s7-edge-android-nougat-754903/
iBolski said:
It appears the official Nougat update for the VZW S7/S7 Edge has been spotted out in the open.
http://www.androidpolice.com/2017/0...7-edge-now-receiving-official-nougat-updates/
I'm going to wait and see how it goes before accepting it. So far, checking for an update, I am still told that my MM phone is up-to-date, so it hasn't been pushed out to my IMEI range yet apparently.
Click to expand...
Click to collapse
Not available for mine yet either. I am curious, are you running the Nougat Beta? I am, FYI.
TelloMan said:
Not available for mine yet either. I am curious, are you running the Nougat Beta? I am, FYI.
Click to expand...
Click to collapse
He said his Marshmallow phone is up to date, so he's not on the beta.
---------- Post added at 09:54 AM ---------- Previous post was at 09:50 AM ----------
I wonder if this only works for people on the official Nougat beta and not just the users that updated via update.zip. I was the official Nougat beta tester that uploaded the update zips for you guys. I'm currently on the U-firmware, but I could flash back to Verizon and check if enough people are interested. Then I could pull the Official update.zip again, and upload that as well.
CVertigo1 said:
He said his Marshmallow phone is up to date, so he's not on the beta.
---------- Post added at 09:54 AM ---------- Previous post was at 09:50 AM ----------
I wonder if this only works for people on the official Nougat beta and not just the users that updated via update.zip. I was the official Nougat beta tester that uploaded the update zips for you guys. I'm currently on the U-firmware, but I could flash back to Verizon and check if enough people are interested. Then I could pull the Official update.zip again, and upload that as well.
Click to expand...
Click to collapse
YES! That would be great, thank you. My concern is that we will be passed up on the official update because we took this Beta. Thanks!!
Their official update page shows the update as the most current release, and with today's date.
i dont see any confirmation anywhere that it was released, only that they updated the update page on the website. but at least is shows release is imminent.
TelloMan said:
Not available for mine yet either. I am curious, are you running the Nougat Beta? I am, FYI.
Click to expand...
Click to collapse
No, I'm not. I don't do anything with my phone if it isn't official and I wasn't part of the beta program. I would assume even beta users should get an update, although it might be a tad bit different than those of us still on official Marshmallow. That or you might have to flash back to the official Marshmallow before you can get the update. I have seen that happen on other phones where I was a beta tester, so I'm not sure how it will work with the S7s.
From what I recall hearing, the official beta testers will be updated to the official Nougat first. The issue is that most of the people using the beta are not official beta testers. They updated using my zips. I'll flash to Verizon at some point today and see if there is a newer release.
CVertigo1 said:
From what I recall hearing, the official beta testers will be updated to the official Nougat first. The issue is that most of the people using the beta are not official beta testers. They updated using my zips. I'll flash to Verizon at some point today and see if there is a newer release.
Click to expand...
Click to collapse
I updated using your zips and I am currently pulling down an OTA after checking for system updates.
I have a SM-G930U flashed to the SM-G930V and am getting the Verizon Nougat update right now.
I updated to beta using the zip as well. Just got my OTA for official!
I am on the PKC update from these forums and get the notification of the update. Keep getting a download unsuccessful error. Not sure if it is because I am not on WiFi
4GivenByChrist said:
I am on the PKC update from these forums and get the notification of the update. Keep getting a download unsuccessful error. Not sure if it is because I am not on WiFi
Click to expand...
Click to collapse
I'm also on PKC, but I flashed it myself. I've tried both data and wifi; keeps saying Download Unsuccessful, error code: 400. Also unsuccessful after restarting and powering off.
http://imgur.com/KmGR7Tc
http://imgur.com/ZKXznFR
EDIT: Wiping cache from Recovery solved my problem. Downloading now.
I got the beta here and am installing official nougat now. I have done a factory reset since flashing the beta. Perhaps doing a factory reset (but still remaining on beta) would clear you for the OTA? (Of course, back everything up before doing so.) I could also be totally wrong on resetting to get the OTA. Just a theory.
Updated to Nougat and so far, pretty darned good. No glaring issues. Only issue I have is in The Walking Dead: No Man's Land where all my player's portraits are dark as if no lighting was used. It wasn't this way under MM. I have noticed people with screen shots from the game with the same issue, so it might be an issue with the game itself.
UPDATE: The reason was the app cache. I just had to go to the TWD:NML app data and clear out the cache and all was good!
nrage23 said:
I have a SM-G930U flashed to the SM-G930V and am getting the Verizon Nougat update right now.
Click to expand...
Click to collapse
I have a 930U as well that I flashed to 930V. Does your Video Calling work? I activated Advanced Calling and HD Voice works but Video Calling does not. The option in my settings has the "HD Voice and Video Calling" option shaded out so I can't select it. I can only select "HD Voice only" so that's all that works. Do I need to call Verizon to try and fix this or is it a limitation from getting a 930U?
Could anyone confirm if you can enlarge others profile picture on LINE? I tried on the beta before and couldn't do it. Thanks in advance.
Can someone upload the OTA update to a mirror?
Is there anyway I can temporarily go back to Marshmallow on an unrooted stock Verizon GS7 edge? I did not anticipate that my encrypted SD Card would be mostly unreadable when updated to Nougat.
After choosing "Decrypt SD Card" in options, it runs a "Checking SD Card" loading screen. I left this for about 4 hours while I was busy, but it did not appear to make any progress when I returned. I will try again overnight.
However, after this I can use Solid Explorer to navigate to the SD Card, and see all my files, but cannot open them.
Thanks for any help even if that means telling me those files are unencryptable and I should just bite the bullet and reformat.
I got tired of hitting check for update and getting nothing. I used a VPN inside the usa on wifi and got the ota immediately.
Anyone gotten this build via OTA? I got impatient and flashed the factory images. Just curious about that weird build number...https://www.reddit.com/r/GooglePixe...nyone_seen_nhg47k_in_the_wild_might_or_might/
bjoostema said:
Anyone gotten this build via OTA? I got impatient and flashed the factory images. Just curious about that weird build number...https://www.reddit.com/r/GooglePixe...nyone_seen_nhg47k_in_the_wild_might_or_might/
Click to expand...
Click to collapse
I thought I was the only one, I didn't get the OTA yet either, I'm still waiting even though it's supposed to be out and Verizon normally has it ready to download immediately when they say it's ready on their software update page.
I haven't heard anyone on Verizon getting an OTA yet, which is odd like you implied. I wonder what they're holding off for. It also didn't mention the Android version bump in their notes.
Well that helps, I have a play store phone but Verizon service and I haven't been able to get OTA yet even when I tell it to go look. I guess I will have to wait until Verizon gets going on this. Taking the sim card out and rebooting does not help.
Sent from my BTV-W09 using Tapatalk
bjoostema said:
I haven't heard anyone on Verizon getting an OTA yet, which is odd like you implied. I wonder what they're holding off for. It also didn't mention the Android version bump in their notes.
Click to expand...
Click to collapse
I got the OTA, it's 7.1.2 and definitely the NHG47K
LaosPerson said:
I got the OTA, it's 7.1.2 and definitely the NHG47K
Click to expand...
Click to collapse
Are you able to grab the link?
rozyman17 said:
Are you able to grab the link?
Click to expand...
Click to collapse
Link for what? Sorry I'm confused lol.
Link for the OTA. I sideloaded the E build, but wouldn't mind putting on the K build
Any time there is an update I just grab it from https://developers.google.com/android/images. I haven't tried flashing the OTA from the page since I usually grab the full factory image (I don't mind starting over lol). I am on Verizon and my build number after I flash the factory image is N2G47E. There are no Verizon apps on the images , but during set up it will prompt to download all that Verizon crap-ware, which you can cancel or uninstall.
As of last night, Verizon has released the K build, which is not up on the developer site. Must be something in there that is better than the E build on their network. Just an FYI.
rozyman17 said:
Link for the OTA. I sideloaded the E build, but wouldn't mind putting on the K build
Click to expand...
Click to collapse
I did the same thing earlier this week. Just checked for updates and nothing. Hope I am not hosed lol.
I ended up with the Verizon version OTA last night (non rooted, google play phone on Verizon service). I did not notice any Verizon-ware installed on the phone, at least not yet. Seems pretty flawless so far.
Sent from my Pixel XL using Tapatalk
Anyone able to upload the OTA?
I would be concerned with the Verizon firmware locking the bootloader on Google Play store Pixels
I don't think that's how it works.
After the frustration it took for me to get stock 7.1.2 on my PXL, I'll wait to see how people like the K build before I consider going back to 7.1.1 so I can be recognized and offered the OTA.
No one has the OTA file yet? Assume that I can't to back to 7.1.1 to get this OTA? I sideloaded the E build earlier this week.
Trooper27 said:
No one has the OTA file yet? Assume that I can't to back to 7.1.1 to get this OTA? I sideloaded the E build earlier this week.
Click to expand...
Click to collapse
There's always loading the 7.1.1 factory image back, but you can only do that when unlocked. I just hope this is a one-off, because over time it might become 'a thing' if people who sideloaded are on a different release track as others'. It would be nice to know if this is just 7.1.2 with VZW branding, or if it gives better performance on Verizon's network, but evidently we're too dumb to understand exactly what's different between stock 7.1.2 and their version.
It seems to bounce back and forth, sometimes there is a Verizon specific firmware sometimes there isn't, but it would be nice to know before side loading how many branches of the firmware there will be.
Sent from my Pixel XL using Tapatalk
destruya1 said:
There's always loading the 7.1.1 factory image back, but you can only do that when unlocked. I just hope this is a one-off, because over time it might become 'a thing' if people who sideloaded are on a different release track as others'. It would be nice to know if this is just 7.1.2 with VZW branding, or if it gives better performance on Verizon's network, but evidently we're too dumb to understand exactly what's different between stock 7.1.2 and their version.
Click to expand...
Click to collapse
I am not unlocked so I have no option of doing that. I had no clue there would be a Verizon specific build or what I have not sideloaded earlier this week. Guess I have to learn patience LOL.
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?