I"m running the official LOS 18.1, installed from the lineageos.com site. I installed it earlier in the year. Now that the 7 Pro has moved to official OOS12 I thought it would be a good time to update the vendor files from the final official OOS 11 release, 11.0.9.1. The About menu on the phone reported the vendor security patch level as February 1, 2022.
I downloaded the ROM from the OnePlus support web site, extracted the payload using payload_dumper, and followed the instructions, replacing seventeen .img files with the versions from the OOS 11.0.9 build. When I rebooted I checked the patch level. It's still February 1, 2022.
So, I have questions. Has anything changed? Did OnePlus not make any security-related fixes to the vendor files between February and August? I'm just curious if there is any way to bring these files up to OnePlus's final version, to make the phone as secure as possible since I intend to use this phone till the wheels fall off. Thanks in advance.
Related
I have a one plus one and have:
LineageOS version 14.1-20170403-NIGHTLY-bacon
I’ve been getting notifications to download LineageOS updates which are named nightly.
How do I install these updates on my phone? Is there a good youtube video I can follow?
Do I need to install only the latest update or all of them? (There are currently 4 the earliest one being April 10, 2017 and the latest is May 8, 2017) http://i.imgur.com/pAlDSmW.png
Thanks guys!
Download the latest one and once done it will show install. Then it will boot into recover and run a script all by itself you have nothing to do basically
Update: I now managed to incrementally sideload to the latest Oreo from the June Nougat I was stuck on.
Pixel purchased through Project FI. NOT rooted, bootloader LOCKED.
Summary on what worked for me:
-Was stuck on the June Nougat build some months now: 7.1.2 build NKG47L, Jun 2017, T-Mobile, Fi Carriers, and Rogers)
Sideloaded NKG47M (Jul 2017, T-Mobile, Fi carriers)
reboot
Sideloaded NKG47S (Aug 2017, T-mobile, Fi carriers, and Rogers)
reboot
Sideloaded OPR1.170623.026 (Sep 2017, Fi/Canada)
reboot
Sideloaded OPR1.170623.027 (Oct 2017, Fi/Canada)
reboot
I should note that at no point between the incremental OTAs was I offered an update. It was "Your system is up to date" the whole time. I understand some people are still waiting for the Oreo OTA but I should have at least been offered the July & August Nougat updates seeing as how the phone is not rooted, bootloader locked, no changes to system???
Anyhow, I'm now on the latest Oreo build and all is working fine so far. Maybe this post can help somebody with similar issue of not knowing which Oreo OTA to start off with coming from NKG47S
Hi,
I'm having trouble selecting an Oreo OTA file to sideload onto my Pixel. Here some background:
The google pixel is the first of my many android devices I have not rooted or unlocked the bootloader. I intend to keep it that way.
The Pixel in question was purchased directly from Google through Project Fi (when i registered for Project Fi). It is still running a project Fi sim.
The device is not rooted and the bootloader is locked.
Up until today (October 11th) the latest build version was NKG47L of 7.1.2 (with the June security updates. It has been showing "system up to date" and today I finally decided to sideload the most recent Nougat updates myself.
First I sideloaded NKG47M (Jul 2017, T-Mobile, Fi carriers), rebooted and then sideloaded NKG47S (August 2017, T-Mobile, Fi Carriers, and Rogers).
All went well and I'm now on the latest stable Nougat release.
I was hoping that sideloading the OTA updates would somehow get rid of this "system up to date" absurdity I've been having since the June build and offer me an update to Oreo. No such luck.
I'm sick of waiting and would like to sideload the Oreo OTA. I do NOT want to unlock bootloader, root or join the beta program.
The build naming has changed with the Oreo OTA files available from google and I'm completely lost as to which to sideload on my 7.1.2 NKG47S.
Aside from the carrier specific files obviously NOT for my original Google Project Fi device there are these 8.0.0 OTA files available:
- OPR6.170623.012, Aug 2017
- OPR1.170623.026, Sep 2017, Fi/Canada
- OPR3.170623.007, Sep 2017
- OPR3.170623.027, Oct 2017, Fi/Canada
- OPR3.170623.008, Oct 2017
The main thing that confuses me here is that there is no August build OTA file for 8.0.0 that specifies Project Fi as a carrier. I understand i need to go incrementally from the latest Nougat to the first Oreo for my device but I'm lost as to whether I should go with the August OPR6 build which does not specify any carriers or to go with the September build (OPR1) which lists project Fi carrier.
Anybody here can provide me with more insight or possibly have already sideloaded Oreo OTA onto a 7.1.2 NKG47S Pixel?
Go to settings>system>about phone and post your build number for me.
Milly7 said:
Go to settings>system>about phone and post your build number for me.
Click to expand...
Click to collapse
My current build number is in the OP.
It's NKG47S
jetfin said:
My current build number is in the OP.
It's NKG47S
Click to expand...
Click to collapse
Tough call. You said you purchased through Fi so I would try the Fi otas
Milly7 said:
Tough call. You said you purchased through Fi so I would try the Fi otas
Click to expand...
Click to collapse
Yeah, thanks, that's what I ended up gambling on and it worked fine. Going to update the OP.
Got this phone on eBay a few weeks ago. I love it but when I set it up, it thinks it has the latest updates.
Click "Check for Updates"
"Your system is up to date"
Android version 9, Security patch level December 1, 2018
Software version is Q910UM25a
Using a Koodo sim. Tried a Fido one too. Same thing.
Tried the LG Mobile Support tool, get a message saying "Your device has the latest software available from the LG Mobile Support Tool.
Anyone have any ideas? Thanks!
Normal versions are Q910UM20x not 25. Usually LG name 25,29,28 beta firmwares. You need flash 20 full(full OTA) firmware. But where find fullflash i dont know.
I seem to be in the same boat. Picked up two of these previous display model devices.
One is running Q910UM11c (Android 8.1.0, September 2018 patch level) and prompting for an update to 25a, the other is already running 25a.
I'll attempt to capture the OTA on the one still running 11c. I doubt it will help, but it can't hurt.
EDIT: I'll include the build build numbers here just in case they're useful for anything.
Q910UM11c, build OPM1.171019.026
Q910UM25a, build PKQ1.180904.001
skyblaster said:
I seem to be in the same boat. Picked up two of these previous display model devices.
One is running Q910UM11c (Android 8.1.0, September 2018 patch level) and prompting for an update to 25a, the other is already running 25a.
I'll attempt to capture the OTA on the one still running 11c. I doubt it will help, but it can't hurt.
EDIT: I'll include the build build numbers here just in case they're useful for anything.
Q910UM11c, build OPM1.171019.026
Q910UM25a, build PKQ1.180904.001
Click to expand...
Click to collapse
Same boat, mate! I on Q910UM25a, build PKQ1.180904.001 with Dec 2018 security patch. Wish I could find a way to move to regular build. But information is almost non-existent on this device.
I manually flashed the latest update for the Pixel 2, RP1A.201005.004.A1, followed by modifying the boot image with Magisk Manager and flashing that, followed by EX Kernel P2-4.09. When I go into About phone, Android version, I see:
Android version
11
Android security update
October 5, 2020
Google Play system update
December 1, 2020
Kernel version
4.4.223-ElementalX-P2-4.09
Build number
RP1A.201005.004.A1
Shouldn't the security update also be December? What could I have done wrong? Is the Android security update in the boot / kernel image or what is it part of?
Security updates have stopped as of October for this device
I read that there's a serious Jan. 2021 security update on the latest phones from Google, and Pixel 2 people don't get it. I'm still using my Pixel 2, but I'm being very careful how I use my phone now.
jasonbiggs said:
Security updates have stopped as of October for this device
Click to expand...
Click to collapse
So just to confirm, you're seeing exactly the same versions listed in About phone, Android version that I listed in the initial post?
Just finished flashing my pixel 2 back to full stock (Build No RP1A.201005.004.A1) so thought id have a look and it's showing October 5, 2020 for security patch also. Ran the OTA updater but says up to date with same patch date also, looks like October was it's last patch.
The last security update I see is June 1, 2022, which is to install Android 13, which I don't really want. Since there is a a new wifi calling exploit found, is there a way to get the security updates without installing A13 or does Goolge have the deck stacked and I'm essentially forced to upgrade? I live in a rural area and without wifi calling, I have no service.
I think your best bet would be to install a security patch via Magisk if you can find one. Also, maybe a kernel would offer what your looking for?
graysky said:
Since there is a a new wifi calling exploit found
Click to expand...
Click to collapse
First of all the exploit was fixed with the latest update a few days ago! The exploit was discovered, fixed and published by Google. That's the usual way a chip manufacturer deals with it and there' no reason why it should be unsecure to use the latest firmware. BTW: No device was attacked.
Security patch level June '22? You want the latest patch level without installing the corresponding firmware? For what purpose? A new security patch = updated firmware and without an updated firmware you don't have any patches. That's it.
Edit: Some background information. Your installed patch level is set in your boot.img. In theory you'll need a patched boot.img with another patch level (unlocked bootloader required => all data gets wiped!). But your device isn't then more secure than before!!
So it's clear in my head, the OS is firmware and the latest security patches rely on the latest OS to function, correct?
graysky said:
So it's clear in my head, the OS is firmware and the latest security patches rely on the latest OS to function, correct?
Click to expand...
Click to collapse
yes
WoKoschekk said:
yes
Click to expand...
Click to collapse
Thanks!
Interesting. I installed all the available updates and the is no March update, which I thought was needed to fix the exploit. The most recent update is from Feb 5, 2023. This is a 6A phone.