yashsingh1/xdaforums huggingface dataset:
[Verizon LG G4] steadfasterX:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/

About LineageOS:

LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the Suicide Squirrel and LineageOS Github repos.

If you would like to contribute to do not hesitate to submit patches :)

**** These builds are for UsU'd devices only ****

UsU? http://bit.do/unlockg4​

Requirements

Your device need to be unlocked by UsU

Your bootloader stack should be on

latest MM with ARB-2

(see FAQ #20 for how to upgrade your bootloader stack)

Latest TWRP - PREVIEW build: click

Clean modem partition (so no UsU baseband flashed) - see Installation topic for details

Installation

If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.

If you have no backup: TWRP flashable MM modems (N will not work)

Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!

Flash LOS

Flash GApps (8.1 - ARM64) if you like to use google apps

Flash SuperSU / Magisk if you want root

Boot (will take long on first boot!)

Enjoy

Download

Get your builds from my leech server

http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/

Note:

Builds are updated as soon as possible.

There is no build cycle

.

Information pertaining to your device is displayed accordingly.

The current build is the latest for your device.

Known issues:

blobs update needed (nothing you can do - must happen in the ROM)

Check the current issues at the github tracker (feel free to help, provide logs etc!)

Credits

LineageOS

ThePiGuy

kessaras

steadfasterX

and more..

Sources

LineageOS

Kernel

device tree

build manifest

XDA:DevDB Information

lineage-usu-vs986, ROM for the Verizon LG G4

Contributors

steadfasterX, ThePiGuy, kessaras

Source Code: https://github.com/Suicide-Squirrel/local_manifests/tree/los-15.1

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.10.x

ROM Firmware Required: latest ARB-2 MM firmware

Based On: pure LineageOS

Version Information

Status: Alpha

Created 2018-06-20

Last Updated 2019-07-10
[Verizon LG G4] steadfasterX:
Reserved
[Verizon LG G4] Yoyodude1124:
So for this rom I am supposed to use the MM modem, not the N modem as stated in the Unlock thread?
[Verizon LG G4] steadfasterX:
Its clearly stated in this OP.
[Verizon LG G4] lkeeler:
I Installed it yesterday, so far almost everything works out of the box, I've tested:

-4G LTE

-Roaming

-Phone Calls

-Wi-fi

-Bluetooth

-GPS

-Both cameras

The only thing that doesn't work is the flashlight button in the quick settings, although it works in the camera app.

I was unable to test NFC and wireless charging since I no longer have the original back cover.

As a side note, it fails Google's Safety Net even after completely removing root support from LOS, so banking apps are gonna be an issue.
[Verizon LG G4] steadfasterX:
As long as this ROM is in permissive mode you will never pass safety net for sure. This is listed in the known issues in the OP. Torch is a known issue as well and have been added to the same link of the OP. As far as I know NFC will not work in any custom ROM at least it doesn't even in aoscp
[Verizon LG G4] bablossss:
Hello everyone. Tell me how to switch to CDMA
[Verizon LG G4] ANDROID2468:
I see you got phone calls to work. Do you still have Verizon?
[Verizon LG G4] lkeeler:
No, I'm on Virgin Mobile.
[Verizon LG G4] steadfasterX:
New build up

Happy leeching ;)
[Verizon LG G4] ANDROID2468:
Is the blobs fixed yet?
[Verizon LG G4] steadfasterX:
Still working on this.. It's not a quick task ;)

if you want to help :

Flash this Rom and tell me if it boots for you because for me it doesn't but I do not have your model here to test :

http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/
[Verizon LG G4] ANDROID2468:
Ok i will try it tonight! I understand that it's not easy to build something from the ground up! I appreciate that someone is willing to develop firmware for a 3 year old phone that's lock down!
[Verizon LG G4] cowsngrass:
Installed on my VS986 running MM 27c with 2BA bootstack (as in FAQ #20; verified FAQ #26)

No Gapps yet, but did flash SuperSU.

Booted quickly, no bootloops.

Tested camera, browser on Wi-Fi… looks good so far!

But, as usual there is no cell service- the phone isn’t seeing the SIM card.

This is the first LOS Oreo that would boot for me, so thank you! :)
[Verizon LG G4] steadfasterX:
wow great! didnt expect that it even boots.. yea cool the blobs I use are taken from 2BA!

for the SIM:

dialer: type *#06# (do you see your imei?)

settings: phone info -> do you see your imei? do you see your mobile phone number?
[Verizon LG G4] ANDROID2468:
the experimental rom did not boot for me. it was close the welcome screen pop up for a couple seconds
[Verizon LG G4] steadfasterX:
then its very likely the firmware. whats yours?

.
[Verizon LG G4] cowsngrass:
*#06# I get MEID, which is a different number from the IMEI

Settings> System> About phone> Status> SIM status: both IMEI and phone number show correctly
[Verizon LG G4] steadfasterX:
thats... weird.. is the IMEI correct when going to the imei boot screen? --> poweroff phone, disconnect USB, press vol+up and vol+down the same time

.
[Verizon LG G4] cowsngrass:
IMEI boot screen shows correct IMEI with barcode.

Serial number is blank with a short barcode.
[Verizon LG G4] Online Gravy:
I've tried flashing both MM modems on my vs986 buit i still have no signal. I'll have to check the IMEI to make sure its the same as the one on the sticker
[Verizon LG G4] Prayerwimp:
I have the 2ba modem installed and still the sim card does not recognize. Is there anything else I might try? What carrier are you using?
[Verizon LG G4] ANDROID2468:
What carrier do you have?
[Verizon LG G4] steadfasterX:
short update about the current state

somewhen in the past..

while updating this ROM with newer blobs I tested to boot it ofc. Once booted I got no signal but well I thought not a big deal as this might be a temporary issue.

Rebooted to my own model's ROM (h815 - arbv0) and still no signal. wth.. I tried to find out what happened but it was not possible the time I had it. So after digging around for some hours I send it back to LG for repair (which went well, thx again ILAPO).

That happened months ago and I was scared to try further with the vs986 (booting it).

as some of you may had noticed I released a fix for video lagging on UsU'd devices (see UsU thread) and due to this release I found out that the blobs from within the ROM blew fuses. I was able to "fix" that (kind of) but that explains why I had the same issue as described above.

TLDR;

It is hard to develop for a ROM which I cannot even test if it boots. IF - not sure though - I find the time to go on with updating the blobs to vs986 I will not be able to test it. You are safe as your devices will have an ARB level of 2 anyways for everything (not just the bootloader) but I am not.

This makes development not easier as you may can think of and I would need logs while booting and such. so I am not sure if someone here is willing to do that ... or should I just abandon it?

Up to you guys/girls :)

.-
[Verizon LG G4] ANDROID2468:
I will help you test it. Thanks for still working on with this phone. Funny how the ILAPO problem can still be turned into a good thing.;)
[Verizon LG G4] Online Gravy:
I can test builds and and get you any logs you want
[Verizon LG G4] Prayerwimp:
I do not have service at this time. The phone originally had a Verison sim card and that will not identify. I assume it does not have to be active to identify the sim card. Also, I put a Tracfone sim card from another phone into my VS986 and it did not identify that either. So I am wondering if I should try other carriers.

---------- Post added at 06:35 PM ---------- Previous post was at 06:27 PM ----------

So which modem are you using? And which rom?
[Verizon LG G4] ANDROID2468:
I wouldn't if I were you. what I heard, some VS986 does not work at all with sims and custom roms right now. but if you are going to try other carriers, I would try t-mobile since the device tree for this rom was ported from H811.
[Verizon LG G4] Online Gravy:
i have a staight talk sim right now. its not activated but the phone would still see signal. im thinking the rom is corrupting the efs, similar to whats happening with the lineage os 16 builds for the verizon s5
[Verizon LG G4] Online Gravy:
definitely not efs corruption. stock still works fine so the problem is with the rom
[Verizon LG G4] steadfasterX:
ok thx so lets see.

First of all I need a full log catched directly after boot (as fast as possible - which the following cmds ensure if you do it right)

Second.. well ensure you have USB debugging enabled :P and you have to follow the steps briefly (e.g boot fresh is curious important).

The following is meant for a Linux host system like FWUL and will not work on Windows:

Flash the latest experimental build

Ensure you have the 2BA modem partition flashed (without baseband package)

Ensure you are rooted by either the official LOS root-addon or Magisk and that this works:

adb shell "su -c echo I am root"

Power off Android.

Open a terminal and execute (yes 2 ">>" here):

while true; do adb shell su -c dmesg -c ; done >> dmesg.log

start a second terminal (yes 1 ">" here):

while true; do adb logcat -b radio; done > radio.log

start a third terminal (yes 1 ">" here):

while true; do adb logcat -b all; done > full.log

That means you will have 3 terminal windows open all running a different log command.

None of them should print anything on the screen as they store everything in those files.

Now

start up Android and ensure you have the USB cable connected to FWUL/your Linux

After Android has fully booted let this run for about 2 min (not more!) then "CTRL + C" each of the terminal commands and upload the logs.

I prefer gists on github (gists.github.com) but you can also comment the github issue and drag and drop the logs in your comment

If for any reason you do not have or want to have a github account attach the log in a comment here. This will produce a bit of work on my site as I would download and re-upload it to the issue then...

.-
[Verizon LG G4] Online Gravy:
Ill try to get these as soon as possible
[Verizon LG G4] steadfasterX:
I have removed the "do not flash" one rn.

sure the above commands will work with any Linux and there is nothing required to install (as long as you have adb running there)

.-
[Verizon LG G4] ANDROID2468:
Those commands don't seem to work. can you put it in a Bash Script or something? do the logs get save to the phone because I can't find them? adb does work because I'm able to do an adb reboot. and also, I can't fully boot in the experimental rom, it boot loops.
[Verizon LG G4] steadfasterX:
They are stored in the same folder where you start the command . But when the experimental does not start it won't help.

Ok try the latest "normal" vs986 LOS release then
[Verizon LG G4] ANDROID2468:
here are the logs:

full.log

radio.log

dmesg.log

I had to run dmesg.log command as root. if anyone is providing logs and you are rooted with magisk, use this command for the dmesg.log:

while true; do adb shell su -c dmesg -c ; done >> dmesg.log
[Verizon LG G4] Online Gravy:
posted my logs on the github issue, hope they help
[Verizon LG G4] steadfasterX:
thx yea maybe.. but lets go on first in permissive mode:

http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/

download & do the whole procedure again with: lineage-15.1-20190409-UNOFFICIAL-vs986_usu_permissive.zip

.-
[Verizon LG G4] ANDROID2468:
Ok I will try it later
[Verizon LG G4] ANDROID2468:
here are the logs:

full

radio

dmesg
[Verizon LG G4] steadfasterX:
thanks!

sorry to bother that much.. but .. can you do the same with the LOS pie version as well?

It has several enhancements regarding the rild workaround (still sometimes needs 2 min to come up though) but most important it better detects the rild state and triggers a restart of it until it works.

but waaaait.. ok ok.. the video lagging fix also avoided RIL from working and here its exactly the same (same error regarding etc/firmware files - if you do not understand this, NP, I'm just thinking loud ;) ).

so.

I guess you are (bootloader stack) on 2BA is that true?

EDIT:

If that's the case and your ARE on 2BA (only then!! fuses will be blown if not!):

Flash the latest PIE - but before booting:

download & extract the file: vs986_2BA_system_etc_firmware_

venus-only

.7z from here

mount system in TWRP

adb push venus* /system/etc/firmware/

(if that fails your adb is too old and you must push every file from the 7zip file one-by-one)

boot & grab the logs as usual - even when it works :)

.-
[Verizon LG G4] ANDROID2468:
Ok, I will provide logs later today, I would do it sooner if I had my phone cable on me :).

And yes, I'm on 2BA.
[Verizon LG G4] ANDROID2468:
ok so I got the logs but before I post them I have one question.

does the permissions matter for those files? and if so, what are the permissions?

edit

here are the logs before the blob update:

radio

full

dmesg
[Verizon LG G4] steadfasterX:
What do you mean by "before blobs"? you mean those above are the logs before replacing the venus files ?

No the permissions shouldn't matter here ( iirc and as long as you use adb push)
[Verizon LG G4] ANDROID2468:
Yes, that's what I meant, sorry about that.

Give me 30 minutes and I'll post the other logs . This did not fix it just to let you know.
[Verizon LG G4] ANDROID2468:
here are the logs of after replacing the venus files:

full

radio

dmesg
[Verizon LG G4] ANDROID2468:
[MENTION=5545101]steadfasterX[/MENTION]

I got bored and I extracted LOS 16 and 2BA and I started comparing them, and I found something...

The file system/vendor/firmware/BCM4339_003.001.009.0117.0621_LGE_P1_VZW.hcd is missing!

on the device tree, it's listed under proprietary-files.txt but it's not in the rom.

The rom just has the EU versions of those files.

BCM4335_003.001.009.0117.0620_LGE_P1_EU.hcd and BCM4339_003.001.009.0117.0620_LGE_P1_EU.hcd
[Verizon LG G4] steadfasterX:
perfect! so venus is fixed then. so we got one step further:

if you can replace the file /system/etc/firmware/cpp_firmware_v1_8_0.fw in the ROM with the one from 2BA and do the whole log grabbing again

nope that is another story and is only WiFi related. When we have issues on WiFi (like frequencies and such) we can use that one but I would say not atm.

.-
[Verizon LG G4] ANDROID2468:
I sent the logs on the issues_oreo git hub. it was faster that way.

https://github.com/Suicide-Squirrel/issues_oreo/issues/21
[Verizon LG G4] steadfasterX:
Fully ok . We can continue there anyways . (I have answered there already)
[Verizon LG G4] songohan_nery:
I cant record video with this ROM :(, any solution?
[Verizon LG G4] ANDROID2468:
Try the latest experimental build. It works fine there.
[Verizon LG G4] steadfasterX:
This thread has been marked deprecated.

I moved everyone to the generic LOS 15.1 thread here instead: general LOS all-in-one thread

Ensure you write your model and that you have an UsU model when asking questions there.

If you are on the Verizon carrier ensure you track the current issue state here.

Also ensure you subscribe that all-in-one-thread to get news i.e. when new builds arrive.

.-
[Verizon LG G4] ANDROID2468:
I flash it from firmware 2BA to the newest experametal build

And I did a system wipe and factory reset
[Verizon LG G4] steadfasterX:
yea serial is empty always. hmm.. ok so ur EFS seems to be fine.

... but when you see a different IMEI in the dialer (*#06#) it means your misc partition is likely screwed (I had the same issue while my UsU journey when flashing a stock firmware).

try this:

write down the full IMEI you see in the dialer

do a SALT basic backup

open a terminal in the backup folder

type:

strings misc* | grep THEIMEIYOUSEEINDIALER

(replace the word "THEIMEIYOUSEEINDIALER" with the IMEI you saw in the dialer)

uhm so why does it work for [MENTION=8829307]cowsngrass[/MENTION] but not for you then.. really weird.

[MENTION=8829307]cowsngrass[/MENTION] you said something about MM 27c but 2BA bootloader what does that mean? I know only about 2BA firmware..

.
[Verizon LG G4] ANDROID2468:
Maybe my zip file is corrupted

Here's my check sum

Md5: 8711fce276e5fa1614e33213352128cf

Sha1: 3ac30462590045ae0fdbc85d9c6d489cb0be9668
[Verizon LG G4] cowsngrass:
I install ROMs from my working 6.0 Marshmallow which is version VS98627c_00, according to SALT and my phone. That version persists after flashing the files from the kdz for VS9862BA (FAQ #20) and checking it out on SALT. The modem I flash after the ROM is from the SALT backup of my working, UsU'd (before FAQ #20 flashings) 6.0 VS98627c Marshmallow.

Also, I meant "2BA bootstack"... sorry! I don't understand everything I know...:o:o

Let me start over:

In the terminal I entered the correct IMEI. The result was the number I entered (the correct IMEI). It was on 2 lines, in red.

Then I realized you probably intended for me to enter the number I got from *#06#, which is not the IMEI. When I did that, there was no result

I rebooted the phone and dialed *#06# and got the correct IMEI. I did it again 3 more times and got the wrong number all three times.

I'll do another SALT backup and try to do what you asked correctly this time.

I apologize for all this unnecessary gobbledygook on the thread.

Update: did a fresh backup and ran the command in terminal.

Using the number I get when I dial *#06#, the command did nothing.

Using the correct IMEI returns the correct IMEI twice, on two lines.

Update: I restored back to my good MM, then reinstalled lineage, OpenGapps (Pico ver.), & SuperSU. Whatever I did wrong in the earlier install is now corrected because *#06# returns the correct IMEI, every time.

Still no cell service or SIM recognition.
[Verizon LG G4] ANDROID2468:
Do you have cell service now? Can you make phone calls?
[Verizon LG G4] cowsngrass:
No.

I've had this problem with every ROM I've tried to install.

The phone will not "see" my SIM card.
[Verizon LG G4] ANDROID2468:
I have a temporary solution for phone calls but it's not a good one. Since cell data work's on the unofficial LOS 15 and AOSP you can use a voice over ip service like Google voice but you can't call 911 with it! Only do this if it is your secondary phone (if you don't have Verizon don't wory about this, phone calls will work for you)
[Verizon LG G4] cowsngrass:
Thanks! I do use a VOIP called Ooma, which works on my phone's Wi-Fi (no 911).

Fortunately, this is not my daily phone, and the Marshmallow I restore to is nicely rooted and debloated. I just want a new ROM!:laugh:

I'm betting [MENTION=5545101]steadfasterX[/MENTION] will figure this out for all of us!:good:

Thanks again.
[Verizon LG G4] steadfasterX:
ok so to sum this up:

you had 27c and flashed the bootloader stack of 2BA and then the modem of 27c again.

result: LOS boots

I guess you restored the misc and modemst* partitions from your backup? That would explain why IMEI works now.

When you say that you restored back to MM (27c) what exactly do you had restored? fastboot? which partitions and how?

[MENTION=7806151]ANDROID2468[/MENTION] as you are on 2BA pls flash the modem of 27c and let me know if LOS boots up then.

For the missing signal I will need logs but one thing after the other.. Btw anyone tested LOS 14.1 on this phone? same issues?

.
[Verizon LG G4] ANDROID2468:
Ok I will try it later, it's kinda weird something like that would change since it's still marshmallow
[Verizon LG G4] cowsngrass:
In TWRP, I restored the TWRP backup of my working vs98627c MM (which has the vs9862BA bootloader stack).

I did not restore the misc and modemst* partitions from my backup, but I'm willing to try it:)

Then I re-installed the Lineage ROM:

Wiped system, dalvik, cache, and formatted data

TWRP flashed the ROM and OpenGapps

fastboot flashed my vs98627c modem.bin file

rebooted to TWRP

wiped cache & dalvik

booted system

IMEI showed with *#06#. Dialed again several times and it showed IMEI properly.

Now, after leaving the phone on and charging for several hours, dialing *#06# returned the MEID as it did yesterday!

After rebooting, *#06# shows IMEI again.

This is crazy!

You're probably done for the night, but I think I'll TWRP back to my working MM and reinstall LOS from there. This time I won't flash the 27c modem after flashing the ROM. See what happens.
[Verizon LG G4] steadfasterX:
ok so now as your IMEI is fine we can go on with debugging the signal issue:

1) set your preferred mobile type to 2G, wait 2min

2) if still no signal: search mobile network and if u see ur carrier set it manually, wait 5min

3) if still no signal: set it back to automatic, wait 5min

4) if still no signal: reset APN to default, enable flight mode, disable flight mode, wait 2min

5) if still no signal: change the preferred mobile type to any of the other options there, wait after each change 2min

6) if still no signal:

adb shell

su

(alternative: enable developer options -> enable root/adb only. Then: adb root; adb shell)

now enable flight mode, wait 1min

logcat -b all -c
logcat -b radio

now disable flight mode, wait 2min before CTRL+C to cancel the logcat

Copy the whole console output and paste it http://bpaste.net

-
[Verizon LG G4] cowsngrass:
Here's the log: https://bpaste.net/show/b5c51182ce4c

None of the above steps had any effect.

Sorry it took so long... had to figure out how to setup adb on my linux:o
[Verizon LG G4] steadfasterX:
wooah really ;) I think u must have a copy of FWUL ;)

anyways so that doesn't help.

do this instead:

adb shell
su
(alternative: enable developer options -> enable root/adb only. Then: adb root; adb shell)

stop ril-daemon
logcat -b all -c
start ril-daemon
logcat -b radio

wait 1min before CTRL+C to cancel the logcat

Copy the whole console output and paste it http://bpaste.net
[Verizon LG G4] cowsngrass:
https://bpaste.net/show/cfbf8fa5fb43

a few more of these and I might just get this terminal stuff figured out!
[Verizon LG G4] ANDROID2468:
it still won't boot 27c and I even tried a different modem the 28a one but now sometimes it boots into recovery after it crashes
[Verizon LG G4] steadfasterX:
For you we need an insecure kernel.

Is there any ROM which boots for you?
[Verizon LG G4] ANDROID2468:
yes, it only crashes on the experimental build. both los and aoscp boot for me but no phone calls with my Verizon sim
[Verizon LG G4] steadfasterX:
I assume you are using windows so do this first in the terminal (not needed on Linux/FWUL):

mode con lines=32766

and ENTER. it sets the buffer in your terminal to the max possible which is needed due to the log verbosity.

flash experimental LOS in TWRP

boot to fastboot

extract the attached boot image and flash it in fastboot (fastboot flash boot boot_debug.img)

on boot (when you see the boot anim):

adb shell dmesg
(if it fails try until you get output)
adb logcat -d

Copy the

all

the content (must be a lot) of that terminal screen to: http://bpaste.net

.
[Verizon LG G4] ANDROID2468:
here you go

https://bpaste.net/show/7da84fc425cb