Database Develop

Need Help about MM Security Patches

Good Evening! I opened this thread to ask if someone could give me an hopinion about a problem I had on mu Nexus 6 after going back to MM from Android N preview. So today I unenrolled my device and I received a Marshmallow OTA, which was said to be the last one available. But as soon as I updated my Nexus, I saw they sent me the OTA with July's Security patch. I tried to wait and see if september's update would show up but nothing in 2 days. Is it normal and have I just to wait or is it a problem? Have you had same experiences?
P.S. I wiped data and everything soon after updating back to MM.

Does it matter if it's the July patch? These security issues are not those that normally happen to users who don't download warez apps. Use Google Play, and you're safe.
But if you want the most recent version, the download the latest OTA from the Google OTA page, and sideload it.

istperson said:
Does it matter if it's the July patch? These security issues are not those that normally happen to users who don't download warez apps. Use Google Play, and you're safe.
But if you want the most recent version, the download the latest OTA from the Google OTA page, and sideload it.
Click to expand...
Click to collapse
Yes, you're actually right about it, security patches are more or less the same for normal users. Let's say, my first worry is about Android Nougat update, because my stock updater does not seem to work properly these last days after I went back to MM. So I thought it might be a matter of time.

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.

Any way to force 8.1 OTA on Project Fi X4?

Greetings, I have a Project Fi Android One X4. Two days ago I went back to Project Fi Oreo stock after being rooted in order to receive the OTA. I received the January, February, and March security updates. But once I attempt to get the April one with 8.1, the system says I am up to date. I attempted to sideload the April OTA but got the message many get about not being able to mount. I know that these updates are not rolled out all at once, but I see many here in the forum already got it. Is there any way I can force the OTA? Thanks in advance for the help!

I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.

jfalls63 said:
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
Click to expand...
Click to collapse
Same issue for me. The ADB sideload/SD card problem doesn't make sense.

Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.

ptn107 said:
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
Click to expand...
Click to collapse
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.

rczrider said:
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
Click to expand...
Click to collapse
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.

Thanks for all the responses! I see that I am not the only one with this issue. I think that like jfalls63 said, of we don't get the update in the coming days we will have to wait for the full firmware release. It is not convenient since I want to root and wanted to do it in 8.1, but there is not much we can do about it if we cannot find an alternative.

QWZR II said:
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Click to expand...
Click to collapse
You're right; I haven't had any reason to do either since the update and it wasn't until after I posted that I saw another thread mentioning this issue. Sure enough, same is true for me.
Still, the update was pushed to one of our phones only a couple of days ago, so if they pulled it, it's only been within the last 72 hours or so.

I'm experiencing a similar thing (https://forum.xda-developers.com/moto-x4/help/oreo-8-1-update-stuck-loop-t3788293), so this seems to be a prevalent problem.
When I have time, I'll go through the Moto forums and see if anyone has any helpful information.

I'm on Fi and I received the 8.1 update just fine. I haven't unlocked my bootloader yet to root it, but otherwise I'm on the gravy train. Once they release a full sized firmware I plan to reflash to get my space back, and then root.

The only solution i've found to get the OTA to work (verified by others as well as my self)
Reboot after each fail and try again - if you watch the screen the % complete will increase each time before fail, eventually ending in a successful upgrade! (At which time your phone is now more secure than ever - USB file transfer won't work with a lock screen pin/pattern/fingerprint.

N960FXXS8FUC4 april 2021 update ?

So guys I'm on android 10 one ui 2.0 the very first version of it dec 2019
And just decided to get the newer version of 2.0 the jan or feb patch but the ota update comes up with april 2021 update
N960FXXS8FUC4 this is I think 2.5 one ui the very latest version, do Samsung delete older updates off the sever now and just push the latest updates?I'm 17 updates behind I was expecting to be able to update 1 by 1
Instead of being forced to jump to the very latest version in 1 hit

Bump for help guys please help guys this forum Is dead i know due to the note 9 being old but i would really appreciate the help
Maybe I should remake this thread and put it into the s20 section because that forum is not dead?

I don't believe Samsung delete previous OTA updates from their servers.
OTA updates are incremental, in other words each update will apply changes from a specific previous version to update it to a specific newer version.
So for example a recent over the air (OTA) update would be for 8FUC4 to update to 8FUD1, this update would only be downloaded by your phone if it was on 8FUC4, also when the phone reboots to install the update it again checks that the current software is, in this example 8FUC4 and will only install the update if 8FUC4 is the currently installed software.
If you update automatically in this manner then it's one upgrade at a time I believe.
If you want to update in one jump to a particular firmware then you would need to manually download a specific "full firmware " from an independent website such as Sammobile, usually approximately 4Gb in size to your pc and then flash thus full firmware using ODIN software

My phone uk note 9 unlocked doesn't update each fw one at time like I would like ,im currently 17 updates behind and when I go to update via ota its skips all 16 updates and offer me to install the lastest version of android so Samsung must delete the old firmware from the fota servers