So the wave of the Oct. Security Update for the H918 is out. This new version is completely safe to update since this is still ARB 1 (See attached pictures).
Is it strictly security, or are there any UI/UX bugfix or additions?
nfc problem
bro , your nfc working ? i dont know why my nfc wont turn enable.. im using lg h918 v20 upgrade to oreo but the nfc wont enable.. when i click enable they turn disable quickly.. any solution ?
Ak7J4 said:
So the wave of the Oct. Security Update for the H918 is out. This new version is completely safe to update since this is still ARB 1 (See attached pictures).
Click to expand...
Click to collapse
I got this notification for a system update and I just rooted about a week ago.
Since im rooted can I accept and install the system update. If yes how do I do this in twrp. Will I loose root?
pvaldeben said:
I got this notification for a system update and I just rooted about a week ago.
Since im rooted can I accept and install the system update. If yes how do I do this in twrp. Will I loose root?
Click to expand...
Click to collapse
If you accept, the phone will go into a bootloop since the stock recovery has been replaced by twrp. So don't accept the update. Reflashing the ROM would stop the bootloops if you just so happen to accept it.
Mnementh666 said:
Is it strictly security, or are there any UI/UX bugfix or additions?
Click to expand...
Click to collapse
To me I believe its just strictly security tbh since I haven't noticed anything else. I will see if performance has been improved or not
Ak7J4 said:
To me I believe its just strictly security tbh since I haven't noticed anything else. I will see if performance has been improved or not
Click to expand...
Click to collapse
Cool. I won't stress it then. Thanks
pvaldeben said:
I got this notification for a system update and I just rooted about a week ago.
Since im rooted can I accept and install the system update. If yes how do I do this in twrp. Will I loose root?
Click to expand...
Click to collapse
Actually I did accept it when I first saw the notification then when I realized I was rooted (about 4 years without root) the phone booted in to TWRP and I freaked out ... so I moved the slider to see TWRP was asking to enter some sort of password or key for it to continue. but then I saw the cancel button and I cancened and it took me back to the main TWRP screen where I just rebooted the system without issues.
The only reason I rooted was because OREO battery life was 10 % per hour weather I touched or did not touch the phone. I thought this security patch might have battery optimizations.
But thanks for your replay, I'm going to stay away from this system update since I'm rooted not. I guess I got luck and not bricking my phone.
20G Security Update Changelog
FYI
Software versions & updates: LG V20
Android Security Bulletin—October 2018
Related
Right now I'm using 5.0.1
Kernel 3.4.0
Build Number LRX21Y
Software D85020f
Security Version MDF v1.1 Release 2
Am I completely up to date? Thanks guys.
Newest version is this
It updates security and adds volte
insanenyc said:
Newest version is this
It updates security and adds volte
Click to expand...
Click to collapse
My phone won't let me update it OTA or through LG tools. Keeps saying this phone has been suspected of rooting. I tried factory reset but it gave me the same result. How can I update and get around this thing knowing I was rooted? I'm not even sure how it knew because I went to stock without adding any accounts or apps -_-
jlgarr86 said:
My phone won't let me update it OTA or through LG tools. Keeps saying this phone has been suspected of rooting. I tried factory reset but it gave me the same result. How can I update and get around this thing knowing I was rooted? I'm not even sure how it knew because I went to stock without adding any accounts or apps -_-
Click to expand...
Click to collapse
Follow my G3 back to stock guide.
Sent from my iPhone using Tapatalk
I know.. I know... No OTAs with root... It was a security update so I didnt think much about it until it actually hit me...
It was truly a mistake. I just got back into android after a few years hiatus.
Is there a way to go back without losing anything? Any kind of help would be appreciated!
Stock rom marshmallow. XT1540 1gb. Have TWRP.
Thank you!!
NZed said:
I know.. I know... No OTAs with root... It was a security update so I didnt think much about it until it actually hit me...
It was truly a mistake. I just got back into android after a few years hiatus.
Is there a way to go back without losing anything? Any kind of help would be appreciated!
Stock rom marshmallow. XT1540 1gb. Have TWRP.
Thank you!!
Click to expand...
Click to collapse
Just wipe caches and reboot...
I have rooted device with twrp installed, Do i need to flash stock firmware to update security patch update??
Because i have noticed that any kind of official update failed when we try to flash it on rooted device
amritmalviya said:
I have rooted device with twrp installed, Do i need to flash stock firmware to update security patch update??
Because i have noticed that any kind of official update failed when we try to flash it on rooted device
Click to expand...
Click to collapse
You need to be 100% completely stock to an OTA... Stock recovery, stock kernel, stock system partition... How you get there is up to you.
acejavelin said:
You need to be 100% completely stock to an OTA... Stock recovery, stock kernel, stock system partition... How you get there is up to you.
Click to expand...
Click to collapse
How to get stock system partition?
amritmalviya said:
How to get stock system partition?
Click to expand...
Click to collapse
Really? Restore your pre-root backup with TWRP or flash the stock images from the General Discussion section.
Remember that we do not have images for the latest security patches on some models yet, if you go back to stock, take an OTA, and root, ROM, or do something nasty to your device, there may be NO WAY to recover until, or even if, newer factory firmware images become available.
These updates are just security updates, they are not bug fixes in any way (at least from what has been shown), so there is no real world benefit to applying them if you don't need too. Security updates are mostly just feel good propaganda anyway.
acejavelin said:
Really? Restore your pre-root backup with TWRP or flash the stock images from the General Discussion section.
Remember that we do not have images for the latest security patches on some models yet, if you go back to stock, take an OTA, and root, ROM, or do something nasty to your device, there may be NO WAY to recover until, or even if, newer factory firmware images become available.
These updates are just security updates, they are not bug fixes in any way (at least from what has been shown), so there is no real world benefit to applying them if you don't need too. Security updates are mostly just feel good propaganda anyway.
Click to expand...
Click to collapse
Does a security patch update release mean preparation of naugat for our device?????
Or its just useless?
amritmalviya said:
Does a security patch update release mean preparation of naugat for our device?????
Or its just useless?
Click to expand...
Click to collapse
A security update has no correlation to a Nougat update, we are not getting it, even if we were it would have zero correlation to it... Except you would like need to have it to take the next OTA.
As far as being useless, no it isn't... it does contain some security update, which although they are not really important shouldn't be ignored without a reason, and being rooted/modified MAY be significant enough reason but that is your call. I would read the release notes, if it is just security updates it's probably worth skipping for now, if it is bug fixes or other updates then it is probably worth it to take but use caution modifying your system because you cannot flash a firmware that is older successfully and we don't have the "new" firmware versions yet.
Many users including me got the system update notification. I didn't updated it then. Now the notification is not there any more and system update says you're phone is up to date with 5.1.5.
Is it true that 5.1.6 is not available anymore?
see the response from other users https://forums.oneplus.com/threads/oxygenos-5-1-6-ota-for-the-oneplus-6.849450/page-128
JerryGoyal said:
Many users including me got the system update notification. I didn't updated it then. Now the notification is not there any more and system update says you're phone is up to date with 5.1.5.
Is it true that 5.1.6 is not available anymore?
see the response from other users https://forums.oneplus.com/threads/oxygenos-5-1-6-ota-for-the-oneplus-6.849450/page-128
Click to expand...
Click to collapse
Hmmmm... I am on 5.1.6. maybe there is an update to 5.1.7. with June '18 security patch incomming?
To be honest, I am very satisfied with 5.1.6.
They're going to push an update with the bootloader bypass fix included.
yeah i hope this does not cause issues, for us that have twrp and rooted, get ur backups ready, we may have to format data
t2jbird said:
They're going to push an update with the bootloader bypass fix included.
Click to expand...
Click to collapse
is it the official statement from them?
JerryGoyal said:
is it the official statement from them?
Click to expand...
Click to collapse
That an update will be rolling out shortly? Yes.
JerryGoyal said:
Many users including me got the system update notification. I didn't updated it then. Now the notification is not there any more and system update says you're phone is up to date with 5.1.5.
Is it true that 5.1.6 is not available anymore?
see the response from other users https://forums.oneplus.com/threads/oxygenos-5-1-6-ota-for-the-oneplus-6.849450/page-128
Click to expand...
Click to collapse
Same here I didn`t make the update and update notification has gone
Chat showing the reason for the pulled update.
Looks like there was a "freeze issue," and a hotfix will be rolling out shortly.
Had it a few days now, no issues here.
Afraid to jinx myself but I have no issues on 5.1.6 rooted with TWRP installed since Saturday.
oos.5.1.6, have no issue so far, root, twrp, exposed, custom kernel.
I have no issues at all.
But some people on OP forums are going nuts about it. But to be fair, I have seen at least hundreds of different bugs that I don't have. Have no idea what those guys are doing with their phones.
Actually I have only noticed one small problem, the keyboard remains under the notification shade when trying to respond to an SMS. That's it. No big deal.
I just got ota update released again, it is 1.15 GB, i will wait with update.
I am located in Eastern Europe. Good luck
Have received the notification.
Can confirm the size.
Will not install it for now.
I am on Android Pie, so i don't know what's up with people who have Android 10 already installed.
underdoq said:
I am on Android Pie, so i don't know what's up with people who have Android 10 already installed.
Click to expand...
Click to collapse
I'm also on Pie. I have received the notification am the size is what you mention (1.15gb) but since is brting problematic, I will not install for now.
I just got it too, should i update?
Just installed!
Everything is fine not any big bug that worth mentioning!
It can lag a bit if you wont make a factory reset afterwards
Came directly from pie 10.0.20.0 everything is fine i think ots safe to install
AnonymousAL said:
Just installed!
Everything is fine not any big bug that worth mentioning!
It can lag a bit if you wont make a factory reset afterwards
Came directly from pie 10.0.20.0 everything is fine i think ots safe to install
Click to expand...
Click to collapse
Is it the same update as few days ago?
11.0.4? If yes ,then I wonder why they stop the OTA just to start it over without changing/fixing anything...
It's like xiaomi devs are a bunch of amateurs who doesn't own this device therefore unable to test their updates and just hope for the best when they release one...
Yes it's the same 11.0.4.0
AnonymousAL said:
Yes it's the same 11.0.4.0
Click to expand...
Click to collapse
Thanks for the reply!
gonna update until they pull it back again
I'm on Q from the first update - 11.0.2.0 - which is running without major bugs, just a bit worse battery usage and less maximum brightness They don't offer me any update yet.
digitri said:
I'm on Q from the first update - 11.0.2.0 - which is running without major bugs, just a bit worse battery usage and less maximum brightness They don't offer me any update yet.
Click to expand...
Click to collapse
There's a process for applying the OTA or a fastboot image you can use to upgrade.
I expect you'll get a OTA offer soon anyway. I just missed it last time but got it now. OTA from 10.0.20.0
Thread closed
Please use existing threads like this
strongst
Forum Moderator
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Thanks it works great
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
I still cannot get it to work. Installed, but I still get the error about cannot enroll.
Mine was working before I downgraded from DP3 back to Android 10.
AwkwardUberHero said:
I still cannot get it to work. Installed, but I still get the error about cannot enroll.
Mine was working before I downgraded from DP3 back to Android 10.
Click to expand...
Click to collapse
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Displax said:
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Click to expand...
Click to collapse
Thank you so much for the link to this!
I reported it as an issue right after I saw it, but had not heard back.
I appreciate you linking me.
This fixed my problem with face unlock. Thanks so much ?
What does this do exactly? My wife's face unlock works but she has a constant notification to re-enroll. I told her if she did that it most likely wouldn't work unless she factory resets. Honestly the notification being there annoys me more than her but she refuses to factory reset. I would just try it and see if it was my phone but I'll be sleeping in the backyard if I screw hers up for any length of time....lol
Worked perfectly on my phone! Spreading the word! Thanks for the module!
https://twitter.com/kingbri_aahs/status/1258148276513189888
Displax said:
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Click to expand...
Click to collapse
Hey man thanks, I tried it. It didn't work for me. I wish you nothing but the best of luck with this fix bro. It's really needed. I miss my camera lol
Displax said:
it seems like this is another related problem, but has a different reason.
This is in known issues: https://developer.android.com/preview/release-notes#user-facing_issues
Click to expand...
Click to collapse
Anyone know if this will be fixed or are we stuck using 11 previews and betas if we want face unlock? I sent my pixel in under warranty like a lot of people suggested. Just got an update “device not repaired no issues found”.
This worked for me, Pixel 4 not XL
On may factory image
Thanks
TechOut said:
Anyone know if this will be fixed or are we stuck using 11 previews and betas if we want face unlock? I sent my pixel in under warranty like a lot of people suggested. Just got an update “device not repaired no issues found”.
Click to expand...
Click to collapse
i fixed this problem coming from android 11 by flashing january factory image .... works perfect again..... your welcome
It's working for me aswell on May version. Could you explain where Is the problem? What does this module?
tmoore3496 said:
i fixed this problem coming from android 11 by flashing january factory image .... works perfect again..... your welcome
Click to expand...
Click to collapse
So you are still on January update till know ?
I did the same here and worked but when i tried to update normally with OTA, the problem come back to me again
So I'm using January update and refusing update my phone for this reason
Okay there seems to be a lot of confusion from people in this thread so while I am not the OP I will try to clear things up.
Some people are having face unlock issues that can first be observed when setting the device up after flashing April and/or May images. During set up, it will say something along the lines of "Could not enroll face ID" or "Hardware not available" if dirty flashing one of the updates.
Some of us are having this issue even if we never upgraded to the Android R Developer Preview 3 or 4.
Others of us are having the issue after trying the DP 3/4 then rolling back to Android 10, April or May update.
The last monthly update that did not have Face Unlock issues for any of the above affected is March.
This module is created to help fix that and get Face Unlock working again and it is a Magisk Module that requires root to install.
However, a small few are still having issues even after trying this module (from my understanding).
You do not need this module if your face unlock works on April/May updates because this seems to be a kernel related issue that only affect some for a weird reason that I am too lazy to research right now. I'm sure this will be updated in the coming months.
So if you're Face Unlock doesn't work on April or May update, try this module. If it still doesn't work, you can use the March update and Face Unlock will work. There are no feature changes between now and March update. The March update include the auto dark mode, and the other feature drops from that month. Both April and May are only security patches and very minor fixes. While it is not the latest security patch you still have all the latest features.
Awesome!
Worked perfect on my pixel 4 xl. Flashed dev preview and got the enrollment error. Thanks for your module! working like a charm on May update
fuadtaufiq said:
So you are still on January update till know ?
I did the same here and worked but when i tried to update normally with OTA, the problem come back to me again
So I'm using January update and refusing update my phone for this reason
Click to expand...
Click to collapse
yeah April, May update breaks it, but magisk module fixes it. Temporary fix until Google fixes it.
anyone tried this on Jun update...
i will try, no need to wait
will report back...
---------- Post added at 04:14 PM ---------- Previous post was at 04:03 PM ----------
Adnansaeedhamed said:
anyone tried this on Jun update...
i will try, no need to wait
will report back...
Click to expand...
Click to collapse
i can confirm this working perfectly with me in Jun update
Hi! This happened to me today:
I installed the Android 11 Public Beta 1 today from June Android 10 version. I have an unlocked 4 XL. I flashed (trough fastboot) the June update and my facial recognition got broken. I did factory reset it but nothing was fixing it. I went back to Android 11 Public Beta 1 and it worked. Then I downloaded and flashed January Android 10 version and it is working right now. Will update if after setting it up and updating it to last update will still work.
basically what this does is patches sepolicy and adds the files required for face unlock. If you run a dmesg when trying to enroll there is something blocking the process from finding the files(likely sepolicy)