What is it? How does it differ from OK1?
Monthly security updates?
Nope,.. has the same date from 2015 which is odd because that's the reason I went through all the trouble of un rooting for the OTA. Even the Android version is the same as well.
speaking of security updates, anyway to update that manually if samsung is too lazy to push it out?
If it's a carrier specific phone then you can't do anything until they release their version of the update.
Their version meaning: Samsung has to release an update, then the carrier takes it and adds their own apps and bloat, test it (prohably) and then release it.
Related
Would anyone like to chime in about rumored first OTA update for the Atrix? Will webtop improvements be updated through OTA firmware upgrades?
Also, how soon has Motorola issued updates for their phones in the past? At&T?
It pushed to my phone last night (3/30/2011) but I'd like to know what it plans to do before I tell it to run.
Hello,
I own a SM-N910W8 which unfortunately hasn't received any security updates since May. What are my options on getting a firmware which has the latest October security patch?
Can I flash the latest SM-N910T stock firmware?
Are there any custom roms which will have the latest security patch?
Thanks,
Kilree
If i'm not mistaken, Security patch's should update on their own.... When the manufacturer releases them. Google updates monthly, sometimes twice monthly. Samsung, I don't think they care about it tbh. I have June 1st on my note 4 running stock 6.0.1.. I'm about to backdate, then root and Custom Rom. Then from now on i'm buying Direct from Developer.
After doing a little research. Oct Patch is being pushed now by Samsung. Even Verizon has it... They are usually the last to get any updates pushed to the public. So check with them, check your OTA. You should be able to update with it. (it's a big one, bug fixes and other stuff for the Note 4 as well. )
As Verizon users know a new OTA was pushed yesterday 02/16/17 the update is safe to take if you have a unlocked bootloader you will need to reflash TWRP and root you will lose both after updating
Haven't seen a new OTA on Verizon.
@Shiftydogit, build no. anything?
I'm guessing it is not showing on anyone who manually upgraded with the latest Google OTA files. Not sure about the regular Google update files, but probably checks the system version ether way for 7.1.1, NOF26V and the latest (February) security version.
sliding_billy said:
I'm guessing it is not showing on anyone who manually upgraded with the latest Google OTA files. Not sure about the regular Google update files, but probably checks the system version ether way for 7.1.1, NOF26V and the latest (February) security version.
Click to expand...
Click to collapse
Its all determined by the IMEI and ICCID. The images from Google and VZW are now identical. I got the OTA push and Im on the latest Google OTAs. They simply don't roll out OTAs to everyone at the same time .
Newer than February security patch 7.1.1 NOF26V? What's the build number? I'm 100% stock on NOF26V and can't pull an OTA at this time.
Shiftydogit said:
As Verizon users know a new OTA was pushed yesterday 02/16/17 the update is safe to take if you have a unlocked bootloader you will need to reflash TWRP and root you will lose both after updating
Click to expand...
Click to collapse
Have you rerooted? Idk if I have much reason to, since I rooted mostly for tethering, but I'm curious about the reliability in that
Soccerdude588 said:
Have you rerooted? Idk if I have much reason to, since I rooted mostly for tethering, but I'm curious about the reliability in that
Click to expand...
Click to collapse
Not at the moment been to lazy to reflash TWRP lol
farfromovin said:
Newer than February security patch 7.1.1 NOF26V? What's the build number? I'm 100% stock on NOF26V and can't pull an OTA at this time.
Click to expand...
Click to collapse
NOF26V is the newest OTA. NOF26W is for Rogers. NOF26V was pushed a few weeks ago and includes the February Security patches. I'm assuming those getting it on 2/17 were either late, or part of the 7.1.2 beta program.
Just got this phone yesterday evening and am starting to get it set up...
It is an XT1607 (US Unlocked)...
I want to stay on Marshmallow...
Which update do I stop at to prevent Nougat from installing on the phone?
There is an update available with version number MPIS24.241-2.35-1-13...
The phone is currently on version MPI24.241-2.35-1 with the July 1, 2016 security patch...
Thank you...
My build number is MPIS24.241-2.35-1-13 and I am on android version 6.0.1 with February 1, 2017 security patch, so I think that is what you'll get if you update. I just checked for system updates and it says my software is up to date. I don't think anyone has reported getting nougat on the XT1607 yet.
NoobNeutralizer said:
I want to stay on Marshmallow...
Which update do I stop at to prevent Nougat from installing on the phone?
Click to expand...
Click to collapse
Motorola Update Services (com.mototrola.ccc.ota)
I was wondering how many and what updates everyone else have received and when?
I'm currently on the April 2017 security update and I received that in early June I believe.
I'm hoping Huawei can at least be excused by the fact they're working on an Oreo update instead of doing security updates and bug fixes (highly doubtful though). Mine is a Nordic unlocked model by the way.
So are anyone else receiving security updates?
Not here, in Spain. The thing is, I don't see any security patch coming till next EMUI version arrives, hopefully before the end of the year.
Not sure if this helps, but I found some way opening another security gap
As far as I figured out, you need 3 files for the update to work:
update.zip
update_full.zip (or update_full_WAS-XXX_hw_eu.zip)
update_data_full_public.zip
I am sure, FirmwareFinder or any other tool might come in handy doing so. The next thing you'd need would be TWRP which is available as some beta build somewhere on this forum. Then you'd have to unlock the bootloader and root your device to get TWRP on it. I'd recommend doing some research on this as you might have to get some code for "fastboot oem unlock"...
Flash the files listed above the way they're listed.