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

[zxyzgt]

Thank you. Look forward to @steadfasterX's help!

 

[steadfasterX]

Please help.

I just flashed LOS16 (kept its bootloader stack as it is) on my vs986 (USU'd, running LOS15 without any issue) successfully. After I flashed magisk from TWRP, it entered into the OS without any problem. But once I granted the root privilege to Titanium backup, it rebooted automatically.
Now it can't go to the OS (stuck on the LG logo screen) and it can't go to TWRP using Power+volumn down comb (stuck on the recovery mode loading... screen). How can I fix it? Please help.

This sounds not like a LOS issue but a hardware one.
first of all we should eliminate the wrong placed wordings:

the bootloader stack (or in short just "bootloader") is a set of partitions which are responsible to actually boot up to the state where you see the LG logo.
fastboot itself is part of that for example.
... but e.g. recovery (i.e. TWRP/SHRP) or the download mode are NOT part of the bootloader (stack) though which I saw mixed up in a previous user's answer.

so now that this is clear you should try to find out the root cause of your problem:

first, read the UsU FAQ , especially #14 !
if you flash TWRP you should try the ilapo version with 2cpu then 4cpu first: http://leech.binbash.rocks:8008/TWRP/ILAPO-O/ it does not matter that it is been made for Oreo.
If TWRP does not boot with the regular TWRP image but boots with one of these (see the correct key combo in the UsU OP) then you are catched by the ILAPO.
Keep in mind that you have to boot to TWRP directly after flashing (power off after flashing, then turning on and boot directly to TWRP by the key combo).

so to sum up, ensure that:
- it does NOT boot to recovery when flashing the regular TWRP
- if it boots to recovery with the ILAPO twrp image

All details about the ILAPO and possible workarounds are described in the link of FAQ #14.

.-

 

[zxyzgt]

This sounds not like a LOS issue but a hardware one.
first of all we should eliminate the wrong placed wordings:

.-

Thank you so much for your guidance. I agree with you. After flashed with LOS16, there was no problem entering into OS. It even fixed the issue for flashlight which was from LOS15 :good::good::good:. I guess there was something wrong with Magisk since it bootlooped immediately after magisk granted root to Titanium.
But I will try your way. Thanks again and fingers-crossed.:fingers-crossed:

 

[steadfasterX]

Thank you so much for your guidance. I agree with you. After flashed with LOS16, there was no problem entering into OS. It even fixed the issue for flashlight which was from LOS15 :good::good::good:. I guess there was something wrong with Magisk since it bootlooped immediately after magisk granted root to Titanium.
But I will try your way. Thanks again and fingers-crossed.:fingers-crossed:

Yes trying without magisk is always the first option but as you mentioned in one of the previous posts that your device now just boots directly to fastboot ...



Sent from my OnePlus 6T using XDA Labs

 

[owlery_hk]

dont think this is G4 specific, but is there a way to separate the rotation suggestion and keyboard switcher options?
i am trying to get the keyboard switcher on the right and the rotation suggestion on the left.

 

[Knowbody42]

Please test your phone with one of the following apps and refresh AGPS data . They are like swiss army knifes (you know MacGyver?)

SatStat
GPS, sensor and network status.
A diagnostic tool that displays data reported by sensors in the phone.
GPS and other location providers:
Refresh AGPS data (if supported by phone) either manually, or when a new data connection is detected.

GPS Status & Toolbox
GPS Status & Toolbox is a simple program to show all the GPS and sensor data of your phone. It is designed to be simple, yet effective. It helps you to see what is happening while the GPS is trying to acquire your locations and can be used as a simple compass, as a leveling tool. It will measure the phone’s speed and acceleration, the brightness or the air pressure (if your phone has the necessary sensors.) The program also supports basic navigation functions that are useful when you are out in the wild. The app has four main screens plus it can display a system notification to show GPS data.
Keep your GPS fast: Reset or download A-GPS data regularly for faster updates.

I found out what the problem was: It seemed to be the antennas.

Before, SatStat was showing zero satellites found.
Then I replaced the back frame with the antennas, and now it's finding satellites and getting a location fix.

 

[zxyzgt]

Yes trying without magisk is always the first option but as you mentioned in one of the previous posts that your device now just boots directly to fastboot ...

I got updates: Good news and bad news.

Good news: ILAPO-2cpu_twrp-3.2.3-PREVIEW-144_g4_O.img works! Finally I am able to see TWRP interface. Thank you, @steadfasterX.

Bad news: still got stuck at LG logo when tried to enter LOS. I reflashed LOS (MM modem first of course), no luck. Just saw some errors in TWRP:
Magisk addon.d failed.
Can't find magisk binaries ....

But it continued to overwrite the ROM partition and succeed.
After I restarted, it still got stuck with LG logo.

I also tried magisk uninstaller in TWRP, it is said magisk not found...
I don't know what to do.
Is there any specific ROM to try? Or is there something wrong with the boot.img

 

[masemoel]

I got updates: Good news and bad news.

Good news: ILAPO-2cpu_twrp-3.2.3-PREVIEW-144_g4_O.img works! Finally I am able to see TWRP interface. Thank you, @steadfasterX.

Bad news: still got stuck at LG logo when tried to enter LOS. I reflashed LOS (MM modem first of course), no luck. Just saw some errors in TWRP:


After I restarted, it still got stuck with LG logo.

I also tried magisk uninstaller in TWRP, it is said magisk not found...
I don't know what to do.
Is there any specific ROM to try? Or is there something wrong with the boot.img

Have you tried to disable the 2 big cores in Lineage's boot.img?

Sent from my LG-H815 using XDA Labs

 

[Le-Kube]

Hello, I just followed the guide to upgrade my H815 from stock to the latest lineage OS 16.
First of all, many thanks for the work (both of the guides and the OS), 'im so glad i can keep on using my G4 and give it a new life.

I am still in the process of adapting but there is 2 simple features I can't get to work :
-"turn on the flash light by long push on power button with screen off"
"smart lock" (by geolocalisation)
Are those features supposed to work ? and if yes do you have any recommendations on the how ?

I have a final question that may be dumb, but, can (and should) I use my phone with apps like my bank app and paylib ? (maybe i need to "unroot it or smth ?)

Thanks again for the work, Long Live the G4

 

[steadfasterX]

I got updates: Good news and bad news.

Good news: ILAPO-2cpu_twrp-3.2.3-PREVIEW-144_g4_O.img works! Finally I am able to see TWRP interface. Thank you, @steadfasterX.

Bad news: still got stuck at LG logo when tried to enter LOS. I reflashed LOS (MM modem first of course), no luck. Just saw some errors in TWRP:
Magisk addon.d failed.
Can't find magisk binaries ....

But it continued to overwrite the ROM partition and succeed.
After I restarted, it still got stuck with LG logo.

I also tried magisk uninstaller in TWRP, it is said magisk not found...
I don't know what to do.
Is there any specific ROM to try? Or is there something wrong with the boot.img

ok. you didn't followed my advice completely. so again. slowly. one by one:

1. when TWRP boots with the ILAPO version but does NOT boot when you flash the regular TWRP version your device has a hardware damage!
2. if that is the case you have to follow FAQ #14 of the UsU thread. in that FAQ you find a link to the ILAPO thread which explains everything around it.
3. start clean. that means follow FAQ #2 of this thread and do a "full clean flash" of LOS ! This is crucial important before doing anything else.
4. in that ILAPO thread you see several options how to workaround your hardware issue without any guarantees how long that will work. its a hardware damage which cannot be solved by software.
5. the first thing you might try from that thread is following the X cores guide which is linked there as well. that guide will help you in modifying the boot image of any ROM you like to disable CPU cores which CAN help in extending the life of your phone. so in terms of LOS you would extract the boot image from the LOS zip and follow that mentioned guide to create a 2 or 3 or 4 CPU boot image out of it.
6. if that boot image has been flashed (TWRP -> img or in fastboot flash boot ..) and LOS actually boots this is another proof that you get catched by the ILAPO but you might can work with that for while. Keep in mind that disabling cores will decrease performance obviously but better then nothing.
7. DO NOT FLASH MAGISK before EVERYTHING is working as it should!
8. DO NOT FLASH GAPPS before EVERYTHING is working as it should!

Hello, I just followed the guide to upgrade my H815 from stock to the latest lineage OS 16.
First of all, many thanks for the work (both of the guides and the OS), 'im so glad i can keep on using my G4 and give it a new life.

I am still in the process of adapting but there is 2 simple features I can't get to work :
-"turn on the flash light by long push on power button with screen off"
"smart lock" (by geolocalisation)
Are those features supposed to work ? and if yes do you have any recommendations on the how ?

I have a final question that may be dumb, but, can (and should) I use my phone with apps like my bank app and paylib ? (maybe i need to "unroot it or smth ?)

Thanks again for the work, Long Live the G4

the flash light is an issue related to the camera and mentioned in the known issues linked in the OP. here the exact one: https://github.com/Suicide-Squirrel/issues_pie/issues/26
smart lock by geo is a google feature not a LOS one. if you encounter issues it might be GAPPS related. always use the same or better older version of GAPPS as the ROM date.

.-

 

[Le-Kube]

the flash light is an issue related to the camera and mentioned in the known issues linked in the OP.
smart lock by geo is a google feature not a LOS one. if you encounter issues it might be GAPPS related. always use the same or better older version of GAPPS as the ROM date.

Ok thanks, I tried to research for "flash" and "flash light" in the thread but number of result not related to the flashlight threw me off. Guess no more quick access to flash light, no big deal.

If I want to use an older version of GAPPS, do i need to wipe the whole system again or is there a way to only wipe GAPPS ?

 

[zxyzgt]

Have you tried to disable the 2 big cores in Lineage's boot.img?

Sent from my LG-H815 using XDA Labs

Creating 2 core boot.img now. Thanks for the heads up.:good:

---------- Post added at 10:18 AM ---------- Previous post was at 10:15 AM ----------

ok. you didn't followed my advice completely. so again. slowly. one by one:

1. when TWRP boots with the ILAPO version but does NOT boot when you flash the regular TWRP version your device has a hardware damage!

8. DO NOT FLASH GAPPS before EVERYTHING is working as it should!
.-

Thank you for your help! It is a hardware related issue. I am creating 2-core boot.img now. Hopefully it works

 

[steadfasterX]

New builds are cooking...

I have added a test in my jenkins build process to ensure that the unified device tree is working as it should.
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.

Nevertheless:
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:

   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: d1f6fe863643b1e8d1e597762474928c
   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 - without harming your device.
8. if instead (as we all expect) all went well and you had opengapps before - ensure you reflash gapps

Cooking order & LIVE cooking view

• H815
• H811
• H815 UsU
• VS986
• H812
• H810

Live - View:

• Normal view: https://shebang.binbash.rocks:8800/...0/job/Build all LGE-G4 models/workflow-stage/
• Blue Ocean: https://shebang.binbash.rocks:8800/...-G4/LOS-16.0/Build all LGE-G4 models/activity (click at the top line )

Noteworthy Changes:

Flashing method: "REGULAR CLEAN FLASH" is REQUIRED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(See the FAQ #2 of this thread how to do this)


Thanks (again) to @aoleary for his continues work on kernel and other parts!

• complete re-work of the thermal handling, throttling and performance increase
  The kernel handles hotplug of all cores if needed (just HIGHLY optimized now), while frequencies will be handled by the resurrected thermal-engine service.
  Fully explained:
  • KERNEL
  • DEVICE TREE
  
  Before, when I had started a video capture it was like I could cook a meal on the G4 after 5 min latest.
  Now its getting just warm. Ofc that comes with a little drawback as when reducing frequencies the system will get slower - but not as as slow as when unplugging the whole core(s) (which was the case before my changes).
  That means optimized throttling (as integrated in the above experiment build) is better for your performance then hotplugging (current stable LOS).
  At least it should.
  
  If you encounter any overheat or lagging issues or just being curious how this thermal stuff works grab/monitor the log while/after doing high cpu usage tasks:
  
  

  adb logcat -b all | grep -i "thermal"

• h815/h815_usu: switching back to LTE, GSM/WCDMA instead of just LTE, WCDMA for the preferred network.
  
  
• switching to Anxiety I/O scheduler
  
  
• revert rounded corners
  
  
• platform security patch: 2020-05-05
  
  
• Note: do not flash GAPPS newer then the build date. Recommended is to switch to a life without google anyways (see FAQ #9) but if you rely on Google then use GAPPS which are released at least 1-10 days before the build date. If you flash later versions it MIGHT work but a lot of weird issues can happen so better avoid it.
  
  
• ...... and more. Read "Full details"
  
  
  
• Full details:
  kernel: commits
  g4-common tree: commits
  g4 unified tree: commits
  closed issues (if any): github issue tracker
  LOS: all merged changes since last build
  

IMPORTANT:

• If you encounter issues try this first:
  

  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 -> on step 3 I need the SELINUX log (option D)
  
  
• Taking a backup before is recommended - always
  

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.. :victory:

ok enough of words, just one more thing:
flash and enjoy this lightning fast, even more secure, coooooool(ing) and simply beautiful new LOS version - ever


.-

 

[jovanv]

New builds are cooking...

[*]complete re-work of the thermal handling, throttling and performance increase
The kernel handles hotplug of all cores if needed

A quick question: will there be any problem to devices with disabled cores at boot? With your saying "if needed" I understand that there should not be serious troubles but you would know better

 

[steadfasterX]

A quick question: will there be any problem to devices with disabled cores at boot? With your saying "if needed" I understand that there should not be serious troubles but you would know better

This build actually will help all devices , ilapo or not



Sent from my OnePlus 6T using XDA Labs

 

[jovanv]

This build actually will help all devices , ilapo or not
Sent from my OnePlus 6T using XDA Labs

Can confirm! Two days with this great ROM on my ILAPO device (after disabling the big cores in boot.img) and no problems at all. And the battery life seems very good, better than before (February version of this ROM) but need more days to have a better estimate.

 

[tullyp]

New 20200515 build working with RIL cell service on my Verizon VS986. You can actually watch cores go in and out of use in Kernel Auditor shortly after boot (really cool! ).

Still no incoming caller ID. But caller ID comes right back if I flash back to stock (worked 3 times). I am assuming this is a Verizon issue somehow connected to VoLTE. I am on prepaid plan, and VoLTE is deactivated for Prepaid by default, but what I am wondering is if all Verizon calls go thru LTE now anyway, as CDMA is supposed to be decommissioned, and Verizon just doesn't announce it.

All happened after our local towers went down for a day (switch over to VoLTE maybe?). Verizon wants to know what update I have on my phone when I called in for customer service, and of course I can't tell them I'm on a custom ROM.
tullyp

 

[Thordgar]

maybe, maybe not.. I'm rare of free time atm.. It seems though that this does not happen on @aoleary ROM's so it should be fixable.. was it an UsU'd device btw? If so can you try one of his ROMs and see if it works there?

Hi @steadfasterX, finally I had time to try aoleary's custom roms and today I installed your last LOS (15/05).
On every rom (except H-ROM maybe because it's a modified stock) the phone is stuck in 3g (no 2g and no 4g).
I tried both 20p and 29a modem with the same result.
I'm using an officially unlocked H815.

Can you help me? Thanks.

 

[ThePsymoon]

Since this morning, I have an issue with mobile network connection on my h815. I was still running on the CALMDOWN experimental build (with was working very well), and I notice limited network connectivity (emergency calls only, no internet access). I tried to restart, shutdown and switch on and off airplane mode and it did not solve the issue. Sometimes, the network connection was working during few seconds (enough to load a web page), but stop working just after. In the status bar, the phones seems to be connected to the network, but without data.

I don't know if it can be related, but yesterday, my phone froze when I was loading a webpage, over 4G. I had to remove battery (the system was unresponsive, even power button). Afterward, it was working ok and I did not notice anything special yesterday evening.

In order to try to solve the issue, I installed the new build (20200515), with regular clean flash. The system is working properly, but mobile connection issue is not solved. Calls are not working. Should I try to perform a full clean flash?

I don't know if the issue is hardware or software... (I would guess soft as it sometimes works during few seconds...) Is there a way to get a log?
Thanks in advance for your support.

Edit: the issue is likely related to my mobile operator which seems to have some troubles in my area today. I will update this post in the coming hours/days...

Edit2 : I confirm the issue is related to my mobile operator.

 

[quetzaltr]

Hi. Once I asked aeolary in telegram group he directed me you to ask. My question was if we have any chance to configure boot (start up and turn off) options can we change boot order entriees in init files which we can extract boot partition via twrp for configure boot order make more passive for g4. I meant for example diable big core at system start may reduce maximum briggtness etc. For sometimes my phone cannot success start up the system so phone turn of itself but my battery’s health very bad though may you should judge this first @steadfasterX