Database Develop

Nexus 6 (Verizon) still running MOB31H (6.0.1). Should I manually update via OTA?

I've got a Nexus 6 with Verizon Wireless. It is purely stock: I have never rooted or modified the phone in any way other than accepting the standard OTA updates pushed out by Google/Verizon.
I've been patiently waiting for the OTA update to upgrade my phone to Nougat, but I haven't seen any updates in over a month. My phone is currently running MOB31H (6.0.1) which, according to the Google Factory Images page is the security update from October 2016. However, according to the same page there have been two security updates in November (MMB31C and MOB31K), and there have been two versions of Nougat released since then (NBD90Z and NBD91P). My phone has not seen any of these updates, despite repeatedly checking for updates via the settings menu.
I've got a few questions along these lines:
1) I've seen rumors about trouble with Nougat, which suggests maybe Verizon/Google have been delaying a widespread roll-out. However, I have not seen anything posted recently about this (latest reports are from early October), and what I did see seemed focused on other phones (not the Nexus 6). Are there any known issues with Nougat running on the Nexus 6 that would make me want to delay upgrading manually?
2) Is it unusual for my Nexus 6 to still be running 6.0.1 with the October security update? Shouldn't it have at least received the November security updates? Have others experienced this issue?
3) If I download the OTA directly from Google and sideload the update, will this disable the automatic OTA updates in the future? I'd like to at least apply the November 6.0.1 security updates to keep my phone secure.
4) If I want to update my phone to Nougat manually, can I simply download the OTA for Nougat and follow the instructions Google includes for sideloading the OTA update? Or do I have to download the entire 7.0 factory image and install that image? I have experience installing the factory images (I have a Nexus 10 that I've had rooted for a while, so I've gotten good at installing the factory images whenever a new image is released) but it is still a bit of a pain and I would prefer the OTA updates for my phone if I can.
4a) If I can update via the OTA, can I pick the latest OTA (NBD91P), or do I have to go incrementally (install NBD90Z first then update to NBD91P)?
5) Only tangentially related question: I've noticed that Google has included the month and year on more recent factory images, but is there any way to determine the exact date that an image was released? For example: I see there are two November OTA updates for Nexus 6, how can I tell if MOB31K was released this morning vs. November 2? If it was released this morning that may explain why I haven't seen the update yet, but if it was released November 2 I would be surprised I haven't seen the update yet.
Thanks in advance for any help.

1. Verizon has no control over updates on this device. That said, no major issues with the stock ROM.
2. Not unusual at all. When I received my N6 earlier this year it stopped updating after the latest Android 5.0.1 update. I had to flash an Android 6.0.1 image manually.
3. No.
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
5. No way to tell outside of paying attention here, since someone will inevitably announce the release of the latest version. Of course, once you've installed the latest image, OTA updates should continue as usual if you don't modify the firmware like most of us do.

Thanks for the helpful reply! One quick follow-up:
Strephon Alkhalikoi said:
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
Click to expand...
Click to collapse
I will likely follow your advice regarding updating from the full factory image instead of the OTA. My main limitation is my two-factor authentication. Because I haven't rooted, it is a pain to transfer some of that from one device to another (in some cases it requires disabling two-factor authentication and re-enabling it on each site, and I have at least 12 website that are using two-factor authentication on my device). I need to make sure that I don't accidentally lose the authentication tokens.
If I get lazy, or just want to "risk" using the OTA: Can I use either OTA image (the one from October or November) to upgrade from 6.0.1 to 7.0? Or does the one from October apply a full update and the November is just an incremental update intended to by applied to an existing 7.0 build?

Both are full updates. I'm not sure as to how well your current data will transition over to Android 7.
I would look into finding a means of backing up your authenticator.

Cannot manually install OTA and no OTA updates available

I just bought a new R1 HD Prime version. It's on 6.1, and the wireless update is showing that no updates are available. So I've tried manually downloading the OTA updates and applying them from local storage using the wireless update app, but I get an error message when attempting to do so (Signature verification failed). How am I supposed to update this phone? It's completely stock.
The only thing I've noticed is that the build time of what's on my phone is slightly different than what the 6.4 OTA says it's supposed to be updated from:
My build - BLU_R0010UU_V6.1_GENERIC 17-06-2016 14:53
OTA build - BLU_R0010UU_V6.1_GENERIC_6.0_20160617-1456
Notice the build time is different by 3 minutes. Is that maybe the source of the problem I'm having? I'm honestly at a loss here and I really want to get this phone updated.

Found out what the problem was with the manual OTA...I committed that cardinal sin of not opening up the zip file and realized I needed to extract update.zip I'm still not sure why the wireless update wasn't getting the OTA from 6.1 to 6.4, but once I was able to manually update to 6.4 I got the subsequent OTAs.

[SOLVED] How to roll back to 6.0 after updating to 7.0 with HFF ?

Hey guys !
After getting into so many troubles to finally manage to do the Nougat update with Huawei Firmware Finder I realised something :
No TWRP, which means no root (please don't mention KingRoot...) and no Xposed. The last one, I can get used to, but the other two...
So I tried to rollback to Marshmallow using HFF, but I couldn't get any of the two rollback updates files to be downloaded through the proxy. I also tried to rollback to the last B130 available using the dload method, but the recovery (stock, of course) failed to install firmware.
I managed to download a previous update (which wasn't meant to be used to rollback) with HFF proxy, but once the system rebooted to recovery to install the firmware, I got the same error as before.
Am I stuck with Nougat and no proper root ?
Thank your for your time and your help.
EDIT : Didn't find how, but found an unofficial TWRP and modded SuperSU working with EMUI 5/Nougat. Just gave it a go myself and it's working. For those interested : https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356

[help!] ota updates not working after rolling back from P

Hi...
I joined the beta program for nokia 7 plus and recieved the developer preview but it had so many bugs that i couldnt cope with so i requested the rollback ota and it rolled me back to oreo april 1 and its stuck there
So i downloaded the ota updates and installed it manually through adb commands
But then i recieved the rollback ota again and rolled me back to april 1 update :crying:
How to fix that

You need to download may June and July and push them Via ADB from this thread.
I'm on July now.
https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774

BigD18t said:
You need to download may June and July and push them Via ADB from this thread.
I'm on July now.
https://forum.xda-developers.com/nokia-7-plus/development/ota-nokia-7-plus-ota-links-t3818774
Click to expand...
Click to collapse
When i tried that i recieved the rollback ota once again

Ramy3r said:
When i tried that i recieved the rollback ota once again
Click to expand...
Click to collapse
Disable automatic updates in Developer option.. You will see every little that update is available (downgrade to april), but just ignore it until we recieve august update... This bug is reported and noticed

Ramy3r said:
When i tried that i recieved the rollback ota once again
Click to expand...
Click to collapse
As above just disable auto update and ignore the message when it appears, I still get it twice a day, hopefully they will push another update soon for the August security which should clear it.

Problem is solved...

Thanks guys yesterday i received the updates

Unable to update my Nokia 7 Plus to the latest Android Pie

So 2 month ago, I had registered for the developer Preview of Android 9 on the official website. Got the regular updates until September 1st. Yesterday, we got the official release of the android Pie and I tried to download it. After downloading the 1.4GB update and restarting my phone, it says that the update failed. But when I attempt to check for the latest update, it tells me that I have the latest release and the date the last security patch is on 1st September. Customer care wasn't of any help, so I was hoping you guys would know what's going on here
Cheers

try to clear data of google services framework, restart your phone and check again

Happened to me as well as my cousin who was on Oreo. It shows update failed but we are both on Android 9 with build number 3.22C (0WW_3_22C).
After checking out the new build, there is no change in latest beta and the Android 9 update, I think they have pushed the same ROM with some certifications. All the bugs that was on last beta still persists on this stable build.