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.
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.
Hi, when i reverted back to android 11 from android 12 beta 1 my play store system update is stuck on January patch. How do i get to the latest security patch? i've checked for update but nothing happens.
Is this after the June update? Mine is currently on May 1st after the June update. If unlocked I would try dirty flashing a full image. If locked, sideload the latest OTA via recovery.
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Same here with Pixel 4
gm007 said:
I'm having the same issue since the first android 12 preview,when downgrading to android 11, google play system update stuck at January,i tried many ways but no luck.
Click to expand...
Click to collapse
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
v12xke said:
Did you try flashing the full image and allowing a data wipe (fresh install). I'm guessing you tried dirty flashing it already. @2WildFirE
Click to expand...
Click to collapse
I said everything
I had to ask also in Google pixel community https://support.google.com/pixelpho...gle-play-system-update-stuck-at-january?hl=en
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
2WildFirE said:
Yes I tried all tips, Google Support doesn't know to help.
It's an downgrade issue when come from 12
Click to expand...
Click to collapse
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
2WildFirE said:
I suspect it is a server problem, it seems as if the pixels are still marked as beta and are therefore not getting an update.
Click to expand...
Click to collapse
I suspect people don't want to lose their data by properly wiping & restoring their phone to its factory state.
U don't know how often I did a full factory image flash.
But nothing worked!
v12xke said:
When you reflash your phone using a full image, it wipes and formats your partitions, returning it to out of the box condition. That is the sole purpose of unlocking the bootloader and flashing a full factory image. There is nothing residual after flashing this way, so it cannot be a downgrade issue. I also agree the Google Pixel community is totally useless and laughable.
Click to expand...
Click to collapse
I met the same issue with 4a5g. I tried flashing 5 times but issue still come. Google play services system update will automatically display 1 jan 2021 when i log in google account ( the account i was enroll to using android 12beta via OTA, but i've cancelled android 12beta)
I think issue need to be resolve by google or we can use other google account.
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
So that mean, we need to enroll pilot update 12beta again via OTA or flashing, right?
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Strange how it is behind. I thought new beta versions came out after the general release so they could roll the new security release into the beta. This would mean A12 beta would also be current. But I also haven't been running the betas for a couple years. Interesting.
2WildFirE said:
After opt in Android 12 Beta again, Google Play System Updates working on Android 12.
Today received the update from April to May
Click to expand...
Click to collapse
Please share your solution with android 11.
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
The solution on Android 11 is to simply install the "Main components" APK from APK mirror
It's basically you're just updating manually.
Main components APKs - APKMirror
Main components APKs - APKMirror Free and safe Android APK downloads
www.apkmirror.com
2WildFirE said:
Sorry mate, no solution for Android 11 yet.
Only works so with Android 12 Beta
So thinking if Android 12 goes out live for all, our problem is solved.
Click to expand...
Click to collapse
There is a solution check my post.
Alexisnotfrommars said:
There is a solution check my post.
Click to expand...
Click to collapse
This isn't a solution. It only change the date not more or less!
Hi everyone.
Can somebody help me to solve the problem?
I'm on android 11 with magisk 24.3
I like it and I don't want to install android 12.
The system auto update is off.
I always swipe away the splash message when the system ask me to upgrade to android 12. But one week ago this message informed me that the update has already been downloaded (I don't know, how it was hidden downloaded) and will be installed after the reboot. But I do not need it and I don't want android 12.
Then I flashed android 11 to the both slots (slot_a & alot_b) without wiping (-w was deleted in all-flash.bat ).
After this I flashed a boot patched by magisk to the both slots.
And I solve my problem. I did the reboots a few times to check that I'm on android 11 and there are no splash message with asking to update.
But...
One week later I see the same splash message informed me that the update has already been downloaded and will be installed after the reboot.
So after the next reboot the android 12 will be installed.
And now I don't know what else I can do?
Why it is possible the hidden downloading of android 12?
Tell me how to do not install the android 12 after the next reboot of my Pixel 4 XL?
Thanks in advance.
@v8088v
In dev options you can opt out of automatic system updates. I know it works because I don't take/allow OTA's and never get prompts after toggling. Also make sure your device is not registered for beta or DP's. If you ever did register, you need to manually de-register.
v12xke said:
@v8088v
In dev options you can opt out of automatic system updates. I know it works because I don't take/allow OTA's and never get prompts after toggling. Also make sure your device is not registered for beta or DP's. If you ever did register, you need to manually de-register.
Click to expand...
Click to collapse
thanks for your reply but the option "automatic system updates" In dev options was always disabled. And I've never been registered for beta or DP's.
Hello,
I'm currently on 14.0.3.0.TKBEUXM on my Mi 11 5G. Device had been using a custom ROM/root in the past, but after facing some inconveniences I decided to go back to the "official" MIUI ROM. Also removed root. So, as far as I know, automatic updates are out of the question now.
Some months ago I manually upgraded into 14.0.3.0.TKBEUXM through "Settings > About Phone > MIUI Version > Choose update package"
Now that 14.0.5.0 EEA is out, I tried updating the same way but I'm getting the "Can't verify update: Can't flash this ROM" error.
I assumed that in order to update to 14.0.5.0, I needed to upgrade into 14.0.4.0 first, but I'm still getting the same error.
Also, I've seen that there's an incremental update file but I'm assuming that it can only be used to upgrade from 14.0.4.0 to 14.0.5.0 which I can't use since I'm still in 14.0.3.0. Am I downloading the wrong package?
So, what other options do I have?
I honestly just want to upgrade to the latest version in order to have the latest Android Security Updates. I recall there being Fastboot/Recovery methods to upgrade, but I wanted to ask you guys first since I am not sure if my data will be wiped using those methods.
Any help is deeply appreciated.