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.

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.

System Updates

I recently bought the XZ1c and have been downloading the System Updates. Every time I install one, I get a notification that a new update is available. I've noticed that the most recent ones start with 41.3.x.x.xxx; mine starts with 41.1.x.x.xxx. It seems like I have to download every update in-between before I get to the current one. Is there a way I can jump right to the newest?
I found a site called http://www.xperiablog.net that lists all the System Updates. They have a couple links to the newest updates, but they're for International models, like Brazil or Middle East.
Thanks,
-Adam

Adam O'Blivion said:
I recently bought the XZ1c and have been downloading the System Updates. Every time I install one, I get a notification that a new update is available. I've noticed that the most recent ones start with 41.3.x.x.xxx; mine starts with 41.1.x.x.xxx. It seems like I have to download every update in-between before I get to the current one. Is there a way I can jump right to the newest?
I found a site called http://www.xperiablog.net that lists all the System Updates. They have a couple links to the newest updates, but they're for International models, like Brazil or Middle East.
Thanks,
-Adam
Click to expand...
Click to collapse
Use Xperifirm and newflasher to flash the latest firmware. Some links to help you
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
http://www.xperiablog.net/2018/01/2...-firmware-for-xperia-xz-premium-xz1-and-more/
https://www.reddit.com/r/SonyXperia/comments/78utla/newflasher_tutorial/

If I'm not mistaken, you will have the latest release, installing via xperia companion in your PC

rsk_kelkar said:
Use Xperifirm and newflasher to flash the latest firmware. Some links to help you
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
http://www.xperiablog.net/2018/01/2...-firmware-for-xperia-xz-premium-xz1-and-more/
https://www.reddit.com/r/SonyXperia/comments/78utla/newflasher_tutorial/
Click to expand...
Click to collapse
Cool, I'll check 'em out. The last update I installed was 47.2.A.0.306; it also installed Pie 9.0 during that update. I no longer get a notification that there's a new update available, but I noticed on some site that the latest software update, which was released last month (October) is 42.3.x.x.xxx. Is this true? Thanks.

Verizon Note 9 March security patch rolling out OTA

Just got a notification for update 6 on my VZW Note 9. This should be build 1CSC1 with the March security patch included. I haven't had a chance to update my phone yet.
Also, I sideloaded builds CSAA and the current CSB3 that I'm on now, via stock recovery and SD card and I'm receiving official OTA's from my carrier. I know some were worried they may not receive official OTA's if they sideloaded those builds. I'm just re-confirming what others such as Mr. Orange have said that you will be back on the official OTA train being on the sideloaded CSB3.

Thank you. I am waiting for an update since I sideloaded Pie last month.

CliftonFoster said:
Thank you. I am waiting for an update since I sideloaded Pie last month.
Click to expand...
Click to collapse
Yeah, no problem. Just wanted to get it up asap to let those who still worried about not getting official OTA's anymore because of sideloading, that they will still get official OTA's as long as they're on CSB3. Here's a screenshot of the about screen with the new build running, I didn't update till recently.

The big question is whether or not Substratum/Swift Installer is still working with this update.

Guyinlaca said:
The big question is whether or not Substratum/Swift Installer is still working with this update.
Click to expand...
Click to collapse
Still working on my end

tgee0907 said:
Still working on my end
Click to expand...
Click to collapse
Please help if anyone knows an answer to my issue. I have a Verizon note9 I updated from oreo to pie manually through recovery now I am no longer getting ota updates,even if I search for them. I was told that side loading pie would not effect later OTA's . Is there a way to fix it or I somewhere I can download the updates and install through recovery would be ok too. But can't find them anywhere.

Azag Thoth said:
Please help if anyone knows an answer to my issue. I have a Verizon note9 I updated from oreo to pie manually through recovery now I am no longer getting ota updates,even if I search for them. I was told that side loading pie would not effect later OTA's . Is there a way to fix it or I somewhere I can download the updates and install through recovery would be ok too. But can't find them anywhere.
Click to expand...
Click to collapse
Which version of pie are you still on? CSAA? If still on CSAA, you'll have to install the CSB3 pie build. The CSAA to CSB3 zip to put on your SD card and flashed through stock recovery can be found here within the Note 9 threads. Once you're on CSB3, you'll get OTA update notifications for the next couple OTA updates.

Justinphxaz said:
Which version of pie are you still on? CSAA? If still on CSAA, you'll have to install the CSB3 pie build. The CSAA to CSB3 zip to put on your SD card and flashed through stock recovery can be found here within the Note 9 threads. Once you're on CSB3, you'll get OTA update notifications for the next couple OTA updates.
Click to expand...
Click to collapse
Odin files for April CSD1 build are listed in another post.

Does anyone happen to have a link for that CSB3 zip

Azag Thoth said:
Does anyone happen to have a link for that CSB3 zip
Click to expand...
Click to collapse
Why Not Odin To Latest April Patch CSD1 build

Venom0642 said:
Why Not Odin To Latest April Patch CSD1 build
Click to expand...
Click to collapse
I do not have Odin setup and have never used it . Plus do not have access to a computer at this time. Also would just like to flash it off sd card and start getting my ota updates again. I have the file but it keeps aborting not sure what the issue is .my sd card is encrypted do I have to decrypt it before flashing the update?

Alright got the file (cbs3) and flashed from recovery, and then my ota updates started coming in so I am all updated and life is good. Now I'd I could just figure out why a week ago I stop being able to download apps or update installed apps from xda (from here) not sure what happen or why but when I try it starts to go through the motions ana them I get download failed. Any ideas would be greatly appreciated. I have tired all the usual fixes, clear cache and data uninstall and reinstall xda app,no help...