[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] LineageOS 16.0

steadfasterX

Recognized Developer
Nov 13, 2013
5,570
14,795
263
OK guys. This update is BIG.

Not only bc it includes a lot of stuff but also the complete way how I build changed in the background.
I have done dozens of tests to ensure it will not do any bad but well.. there is a always a chance right..
Unifying our device tree makes it much easier to maintain and to add other not-yet added models - while it comes with the risk something goes wrong when it comes to blobs.

As this is the very first round of my unified device tree I would highly recommend doing the following (I have done that in my manual builds but you get it from jenkins - so there is a tiny little chance of bad luck .. ):

Pre-Cautions | Flashing instructions

  1. Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
  2. Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
  3. Flash LOS - DO NOT choose to reboot afterwards - stay in TWRP.
  4. TWRP menu: "Mount" --> choose "System"
  5. From a terminal execute:
    Code:
    adb shell md5sum /system/etc/firmware/venus.mbn
  6. Compare the value (last 4 characters is fully enough) with these:
    If you flash:
    h815, f500, h818, h819 it should be: ebc5d32c651bf061787e82258cf78a3c
    h810, h811, h812, ls991, us991, vs986 it should be: 78e5cf520d0de4a413ef1cfa7bbbe713
    WARNING: If that checksum is NOT as it should be: DO NOT PANIC! simply FLASH the PREVIOUS LOS version BEFORE booting!. This will ensure you will not blow a fuse.
    While the above test should be considered safe: If you are unsure about this procedure: WAIT before flashing until someone (or I) had done the above quick test from the builds jenkins is providing at my leech server.
  7. Whenever an error occurs while flashing in TWRP (e.g "E1001: Failed to update system image.Updater process ended with ERROR: 7")
    or if the above checksum does not match:
    provide the recovery.log (FAQ #4 A)!!
    ... then flash the previous LOS version to get back to life.


New builds are cooking...

build errors can happen .. so it might take longer until everything completes (as I can fix build issues tomorrow first if any)

In progress (in that order):

Live - View: https://lets.binbash.it:8800/job/LG-G4/job/LOS-16.0/job/Build all LGE-G4 models/workflow-stage/

  • H810

Done:
  • H815 (a re-build to patch the gapps issue* is required - until then use the workaround as described)
  • H811 (a re-build to patch the gapps issue* is required - until then use the workaround as described)
  • H815 UsU (a re-build to patch the gapps issue* is required - until then use the workaround as described)
  • VS986
  • H812

Noteworthy Changes:
  • All models moved from dedicated trees to an unified device tree. While doing that I fixed/added fingerprints, missing infos and more.
    Oh yea and ALL (relevant) models have been added (while I do not build all of them atm .. but now it will be easy to build if someone (or I) wants to).
    If you have one of these models: ls911, f500, us991 and want to have a model specific ROM release: let me know the model and a "+1 to build" notice as a post here. I will decide to add them to the list then. A current full run takes approx ~ 10 hours so who cares :p
    (u may noticed: I exclude h819 here as no one use that.. it even not had received official MM so.. I guess no interest for that anyways?!)

  • Voice mic sensitivity increased when on speaker

  • tons(!) of kernel fixes & optimizations thx to @kessaras . That includes e.g the graphic driver as well (thats why I keep staying with opengl and not switched to skiagl as I first planned to)

  • Selinux = Enforced . I have tested encryption here as well which goes fine (after adding all req policies obviously)
    If you encounter issues try this first:
    Code:
    adb shell
    su
    (or adb root when enabled)
    setenforce permissive
    Try again and if the issue is gone when in permissive mode: provide me a logcat as described here

  • Selinux = Enforced policies have been added and tested for:
    - LOS root-addon downloaded from today (16.0, arm64 ofc)
    - open_gapps-arm64-9.0-nano-20190709
    - even when I do not support it: Magisk 19.3

  • QCRIL db is now writable. Once your phone boots / RIL starts you receive an updated collection of emergency numbers (i.e. 911 for the US etc). Until now these updates went to hell as the DB is readonly (as it sits in the system partition). I fixed that in a way that it starts now with a base DB and will create a writable copy to /data which then can get updated.

  • One of the most noteworthy changes is ofc: RIL. It is fixed now and .. tbh .. it is not 100% clear why :D We fixed and implemented so many things in that time range that it is impossible to say what exactly fixed it. but who cares? it does not crash anymore and that solves a lot of lagging and issues we had.

  • Since ages all LOS builds should pass SafetyNet (I tested for h815 already) but if not - let me know and share your model and a logcat while trying to pass safetynet as it turns out it was a "should". The testing on that was a bit tricky as when you install magisk it will pass it perfectly (not surprisingly) but google play is still showing as certified even when magisk has been uninstalled completely afterwards (which was the way I tested). Another thing is that the device certification check does not happen immediately when you open the play store - it can take a minute or more (and it happens silently). in the meanwhile everything looks just nice (all apps are shown). Last but not least testing requires a full cleared play store. Long story short: a fix comes asap

  • PLATFORM_SECURITY_PATCH: 2019-07-05

  • and others ... and all the details

IMPORTANT:

Keep in mind that almost all pie ROM's sharing the same common device tree (or main parts of it), same model device trees and for sure the same kernel - so you can enjoy most fixes for any pie ROM available..
The above fixes are brought to you by the Suicide Squirrel Team :victory:

ok enough of words, just one more thing:
FLASH and ENJOY that ultra stable, fast, smooth and best pie build for LOS - ever :)


.-
 
Last edited:

busattovini

Senior Member
OK guys. This update is BIG.

Not only bc it includes a lot of stuff but also the complete way how I build changed in the background.
I have done dozens of tests to ensure it will not do any bad but well.. there is a always a chance right..
Unifying our device tree makes it much easier to maintain and to add other not-yet added models - while it comes with the risk something goes wrong when it comes to blobs.

As this is the very first round of my unified device tree I would highly recommend doing the following (I have done that in my manual builds but you get it from jenkins - so there is a tiny little chance of bad luck .. ):

Pre-Cautions | Flashing instructions

Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
Flash LOS - DO NOTchoose to reboot afterwards - stay in TWRP.
TWRP menu: "Mount" --> choose "System"
From a terminal execute:
Compare the value (last 4 characters is fully enough) with these:
If you flash:
h815, f500, h818, h819 it should be: ebc5d32c651bf061787e82258cf78a3c
h810, h811, h812, ls991, us991, vs986 it should be: 78e5cf520d0de4a413ef1cfa7bbbe713
WARNING: If that checksum is NOT as it should be: DO NOT PANIC! simply FLASH the PREVIOUS LOS version BEFORE booting!. This will ensure you will not blow a fuse.
While the above test should be considered safe: If you are unsure about this procedure: WAIT before flashing until someone (or I) had done the above quick test from the builds jenkins is providing at my leech server.
Whenever an error occurs while flashing in TWRP (e.g "E1001: Failed to update system image.Updater process ended with ERROR: 7")
or if the above checksum does not match:
provide the recovery.log (FAQ #4 A)!!
... then flash the previous LOS version to get back to life.



New builds are cooking...

build errors can happen .. so it might take longer until everything completes (as I can fix build issues tomorrow first if any)

In progress (in that order):

Live - View: https://lets.binbash.it:8800/job/LG-G4/job/LOS-16.0/job/Build all LGE-G4 models/workflow-stage/

H815
H811
H815 UsU
VS986
H812
H810


Done:
N/A


Noteworthy Changes:
All models moved from dedicated trees to an unified device tree. While doing that I fixed/added fingerprints, missing infos and more.
Oh yea and ALL (relevant) models have been added (while I do not build all of them atm .. but now it will be easy to build if someone (or I) wants to).
If you have one of these models: ls911, f500, us991 and want to have a model specific ROM release: let me know the model and a "+1 to build" notice as a post here. I will decide to add them to the list then. A current full run takes approx ~ 10 hours so who cares :p
(u may noticed: I exclude h819 here as no one use that.. it even not had received official MM so.. I guess no interest for that anyways?!)


Voice mic sensitivity increased when on speaker


tons(!) of kernel fixes & optimizations thx to @kessaras . That includes e.g the graphic driver as well (thats why I keep staying with opengl and not switched to skiagl as I first planned to)


Selinux = Enforced . I have tested encryption here as well which goes fine (after adding all req policies obviously)
If you encounter issues try this first:

Try again and if the issue is gone when in permissive mode: provide me a logcat as described here


Selinux = Enforced policies have been added and tested for:
- LOS root-addon downloaded from today (16.0, arm64 ofc)
- open_gapps-arm64-9.0-nano-20190709
- even when I do not support it: Magisk 19.3


QCRIL db is now writable. Once your phone boots / RIL starts you receive an updated collection of emergency numbers (i.e. 911 for the US etc). Until now these updates went to hell as the DB is readonly (as it sits in the system partition). I fixed that in a way that it starts now with a base DB and will create a writable copy to /data which then can get updated.


One of the most noteworthy changes is ofc: RIL. It is fixed now and .. tbh .. it is not 100% clear why :D We fixed and implemented so many things in that time range that it is impossible to say what exactly fixed it. but who cares? it does not crash anymore and that solves a lot of lagging and issues we had.


Since ages all LOS builds should pass SafetyNet (I tested for h815 already) but if not - let me know and share your model and a logcat while trying to pass safetynet


PLATFORM_SECURITY_PATCH: 2019-07-05


and others ... and all the details



IMPORTANT:
Taking a backup before is recommended - always
A "REGULAR CLEAN FLASH" is REQUIRED with this build (as several things changed in system partition).
See the FAQ of this thread how to do a "regular clean flash": https://forum.xda-developers.com/g4/development/rom-lineageos-16-0-t3929082/post79502871


Keep in mind that almost all pie ROM's sharing the same common device tree (or main parts of it), same model device trees and for sure the same kernel - so you can enjoy most fixes for any pie ROM available..
The above fixes are brought to you by the Suicide Squirrel Team :victory:

ok enough of words, just one more thing:
FLASH and ENJOY that ultra stable, fast, smooth and best pie build for LOS - ever :)


.-
OMG, I'm so excited! Thank you so, so much aaaaaaa

YOU ARE ****ING BRILLIANT

Sent from my LG-H815 using XDA Labs

---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------

seems process didn t succeed for h815
Oh, what happened?!

Sent from my LG-H815 using XDA Labs

---------- Post added at 11:52 PM ---------- Previous post was at 11:08 PM ----------

I can't wait! ? Now I'm kinda anxious.

Sent from my LG-H815 using XDA Labs
 
Last edited:
  • Like
Reactions: jjcdennis

grigione

Member
Dec 12, 2011
14
0
0
Hello,I have a LG G4 H815EU and I made an update to Ofiicial Nougat V29a (with locked bootloader) about one year ago.I would wish to move to Android 9 by Lineage OS 16,can you tell me what are steps to get and install it?Thanks
 
Last edited:

steadfasterX

Recognized Developer
Nov 13, 2013
5,570
14,795
263
Maybe is not important but my MAC address is 02:00:00:00:00:00 (that's bad)
actually that IS VERY important ;)
Pls wait for and flash the newest pie upgrade currently building. It has this (WiFI and BT MAC issues) addressed..

Wow big update! cant wait to flash it =) Now that selinux is enforced, is there a way like this build can be official ? I'm not sure but i kinda remember that this was one of the reasons. Also ı dont know if it goes official something will change for us but just being curious :D Big Thanks !!
I created a new FAQ for that: https://forum.xda-developers.com/showpost.php?p=79502871&postcount=2 --> FAQ #3 ;)

Oh, what happened?!
just a jenkins build error. I wrote that this might happen as I changed so much under the hood.. Fixed anyways and H815 is up already, H811 soon as well and the rest follows as described.


.-
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,570
14,795
263
OK guys. This update is BIG.
[........]
Note:
Unfortunately I found a little bug already while the build progress is still running. It has been fixed but only for those not build yet.
If you have one of the the following devices and you want to use google play (there is F-Droid pre-installed btw ;) )
then you should read and follow: the gapps issue* workaround
  • H815
  • H811
  • H815 UsU

All others will have the fix included already.
Sorry for the inconvenience


.-
 

sbasil

Senior Member
Aug 2, 2011
1,285
768
113
Espoo
Great work again. :) However, I installed the newest version, but can't get Wifi to work. It connects but doesn't work (IMEI and IMEI SV are both unknown). Older version works just fine. Anyone else facing the same problem with H815?
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,570
14,795
263
Great work again. :) However, I installed the newest version, but can't get Wifi to work. It connects but doesn't work (IMEI and IMEI SV are both unknown). Older version works just fine. Anyone else facing the same problem with H815?
regular clean flash done as described in the FAQ?
MAC address shown?

provide a logcat as described in the FAQ

.-
 
  • Like
Reactions: raptorddd

sbasil

Senior Member
Aug 2, 2011
1,285
768
113
Espoo
regular clean flash done as described in the FAQ?
MAC address shown?

provide a logcat as described in the FAQ

.-
regular clean flash done as described in the FAQ? - Yes

MAC address shown? - Yes

provide a logcat as described in the FAQ - Ok. Will do that when I can (asap).

I attached a couple of screenshots of the "IMEI situation."
 

Attachments

  • Like
Reactions: jjcdennis

steadfasterX

Recognized Developer
Nov 13, 2013
5,570
14,795
263
regular clean flash done as described in the FAQ? - Yes

MAC address shown? - Yes

provide a logcat as described in the FAQ - Ok. Will do that when I can (asap).

I attached a couple of screenshots of the "IMEI situation."
regarding WiFi:
do u had tried setting selinux to permissive?
and try that as well: settings -> system -> advanced -> reset options -> reset WiFi, mobile & bluetooth (will delete all those settings obviously!)
after that do a reboot and connect again.

regarding Imei:
what happens when you type "*#06#" in the dialer app? does it show your imei? do you have cell service/call etc working?

.-
 
Last edited:

jjcdennis

Senior Member
Jun 20, 2015
268
79
48
Toronto
Hate to ask, but for a flash from steadfasterX's 15.1 unofficial lineage to this 16.0 image is a full clean flash required, as per the installation instructions on page 1?
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,570
14,795
263
BTW, why don't you like Magisk? Do you think it's bad for LineageOS?

Sent from my LG-H815 using XDA Labs
Never said that I do not like it ;) Its a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.

so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..

.-
 

busattovini

Senior Member
Never said that I do not like it ;) Its a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.

so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..

.-
Oh, I got it. Thank you! Please, would you tell me how to install the LOS root-addon?!

Sent from my LG-H815 using XDA Labs
 
Last edited: