I can't seem to get the OTA security updates. Maybe this is my problem. My build number is NMF26F which is for everything but Verizon. The build I should have is 7.1.1 (NUF26K, Feb 2017, Verizon Only). How should I correct?
Sideload the OTA image via the instructions here...
https://developers.google.com/android/ota
Related
Yes, I do know I have created about a million forums on this. So now it's being merged into one. I going to list my problems.
1. June 23, 2017 was the date I rooted my device. It was a summer day, at home, with fastboot, and TWRP.
2. October 10, 2017 was the date I regretted rooting my device when I got an OTA update. After trying on this day for hours to finally get unrooted, then get the stock ROM. After all of this, I had missed the OTA.
3. November 22, 2017 (today) I still haven't gotten a OTA update notification. I have been checking every day and trying every method, and still, no OTA.
Now what I need: How to get the XT1607 recovery back, and get the OTA update back. I am still on the February Security update.
Help, please.
lometon said:
Yes, I do know I have created about a million forums on this. So now it's being merged into one. I going to list my problems.
1. June 23, 2017 was the date I rooted my device. It was a summer day, at home, with fastboot, and TWRP.
2. October 10, 2017 was the date I regretted rooting my device when I got an OTA update. After trying on this day for hours to finally get unrooted, then get the stock ROM. After all of this, I had missed the OTA.
3. November 22, 2017 (today) I still haven't gotten a OTA update notification. I have been checking every day and trying every method, and still, no OTA.
Now what I need: How to get the XT1607 recovery back, and get the OTA update back. I am still on the February Security update.
Help, please.
Click to expand...
Click to collapse
I don't have an answer but wonder if the incremental OTA (which is definitely not Android 7.1) has sufficient benefits to warrant the effort. Yep, several security oriented patches but the exposures are small for most (albeit not all).
I signed up to be a beta tester about a week ago and I've yet to receive any 8.1 update. I participated in the one for 8.0 and received the updated within 24 hours of release? My boot loader is locked and I've never had to manual flash any updates. Anyone else in my position?
Have you got the Nov security patch? If so, you will need to wait for DP2 to be sent OTA.
I am also waiting for DP2 OTA, and while it seems that other people are getting it, I am here still stuck with stock 8.0 with Nov. patch
Just checked, I'm on the November patch as well.
I'm on dp1 and still not receiving dp2 ota
No DP2 ota for pixel now, have to wait.
I've got the update notification
But it keeps failing to install
hi everyone,
since i side loaded Android 8.1 image i didint receive any security update! i check for updates regularly but there is no updates !
what should i do ?
fully stock locked bootloader.
lastest patch 5 january.
I just bought another nexus 6p( was enrolled into beta program ). I did flash the latest image from google, and yeah, seems like the last ota security patch is from january. Can someone confirm this ? I forgot to look at my last nexus 6p.
Latest sec Update february 5th here...but flashed myself due to unlocked and rooted...
I updated to Oreo OTA on Sunday. Have February security patch installed.
Sent from my Nexus 6P using Tapatalk
do you guyes know to to downgrade to 8.0??
i've manually flashed all the missing updates i think its the only way.
Yeah, something about the beta program of 8.1 froze updates at the January security patch for me as well.
I ended up dirty flashing the release 8.1 system image and everything works fine now, still don't get OTA update notifications though.
A few days ago, I did get the march 5 security update, after flashing this image 8.1.0 (OPM3.171019.016, Mar 2018) from google .
after flashing all the missing updates , OTA updates started to roll out as normal to me
Hey there,
Right now I have December 1 2017 Security patch (NPJS25.93-14-13) Installed on my device, and I haven't been updating my device through OTA because of fear of getting hardbricked & always Installed latest update via Fastboot without wiping data.
But Right now for Feb 2018 security patch I couldn't find any verified firmware for this device even after 2 months of release, so my Question was should I take OTA for this patch? I have latest GPT + Boot-loader which comes with December 1 (2017) patch. So Should I take OTA for Feb 1 Patch (NPJS25.93-14-15) which fixes Karck vulnerability? Thanks!
siddhesh9146 said:
Hey there,
Right now I have December 1 2017 Security patch (NPJS25.93-14-13) Installed on my device, and I haven't been updating my device through OTA because of fear of getting hardbricked & always Installed latest update via Fastboot without wiping data.
But Right now for Feb 2018 security patch I couldn't find any verified firmware for this device even after 2 months of release, so my Question was should I take OTA for this patch? I have latest GPT + Boot-loader which comes with December 1 (2017) patch. So Should I take OTA for Feb 1 Patch (NPJS25.93-14-15) which fixes Karck vulnerability? Thanks!
Click to expand...
Click to collapse
here you can find feb. patch link :- https://androidfilehost.com/?fid=818070582850507483
I was on Oreo 85.13 pre-release...then I unlocked bootloader...and installed pixel experience...but meanwhile I formatted all data which ihave backed up..then I installed twrp flashable with June security patch zip..and I was on Android 7..then I flashed pixel experience..now..if I want to back on Oreo stock and to lock bootloader..what should I have To do...???I heard somewhere you need stock Oreo ROM zip where I can find one...???is that same one which we have used in manually updating to Oreo... please reply...
As far as I know the only stock Oreo zip we have is the OTA, which can't be used to flash firmware. We need the full firmware file before we're able to flash stock ROMs via fastboot.
Anyway, I'm also curious if there are any differences for the unlocking/flashing/backup process starting at the official Oreo we have now, and if going back to it later is the same as it is with Nougat.
The stock US OTA update can be found here: https://technoplanners.blogspot.com...tock-update-for-moto-g5-plus-OPS28.85-13.html
This can be side-loaded to upgrade after you've flashed Nougat with one caveat. Nougat has to be at Build number NPNS25.137-92. If your Nougat ROM has the June security patches (Build number NPNS25.137-93) you'll be SOL since the manifest specifies the pre-req for the update. So the fools at Motorola released the June update for Nougat, then released Oreo at the same security patch level and won't let you apply the update. Real geniuses.
nvrpayretail said:
The stock OTA update can be found here: https://technoplanners.blogspot.com...tock-update-for-moto-g5-plus-OPS28.85-13.html
This can be side-loaded to upgrade after you've flashed Nougat with one caveat. Nougat has to be at Build number NPNS25.137-92. If your Nougat ROM has the June security patches (Build number NPNS25.137-93) you'll be SOL since the manifest specifies the pre-req for the update. So the fools at Motorola released the June update for Nougat, then released Oreo at the same security patch level and won't let you apply the update. Real geniuses.
Click to expand...
Click to collapse
That's not quite correct; the build required for this Oreo OTA that's currently around is NPNS25.137-92-14 (June 2018 security patch for Brazil and Indian devices). The NPNS25.137-93-14 patch you mentioned is the June 2018 patch for EU, US and Asian devices, which means the Oreo patch for those devices isn't around yet.
To the opening poster, as previously mentioned, you will have to wait for the OPS28.85-13 stock fastboot ROM to be leaked. You must lock with a stock firmware as new or newer than your current bootloader. You cannot downgrade bootloaders via fastboot anyway and it's really not recommended to downgrade.
The US patch is available (Blur_Version.28.51.16.potter.retail.en.US.zip). It can be downloaded from the link I provided.
Correction: My bad. Didn't realize "92" indicated India and "93" indicated US. Evidently the referenced download is labeled wrong