[ROM][ALL VARIANTS] LineageOS-14.1 for LG V20 [Weeklys']

[cnjax]

I know that LG did something funky here to disable the fastboot commands. Anyone knows what I need to do to load recovery? I have H918 10u that I got refurbished from ebay. I did unlock the phone but its just not flashing or just booting to recovery.

target reported max download size of 536870912 bytes
sending 'recovery' (29100 KB)...
OKAY 0.681s
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.700s

You need to check out the laf exploit thread to achieve root and get twrp installed

Sent from my LG-H910 using XDA Labs

 

[x86cpu]

I know that LG did something funky here to disable the fastboot commands. Anyone knows what I need to do to load recovery? I have H918 10u that I got refurbished from ebay. I did unlock the phone but its just not flashing or just booting to recovery.

target reported max download size of 536870912 bytes
sending 'recovery' (29100 KB)...
OKAY 0.681s
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.700s

You need to check out the laf exploit thread to achieve root and get twrp installed

Plus after, since you are h918 and higher than 10p, you'll need to flash the 15.1 LineageOS. 14.1 won't every support it. Check my unofficial thread, and make sure you flash the 10p version.

 

[egenesis]

Plus after, since you are h918 and higher than 10p, you'll need to flash the 15.1 LineageOS. 14.1 won't every support it. Check my unofficial thread, and make sure you flash the 10p version.

Holy cow!! This keeps getting worse. Wondering why LG wants to make things harder for user when it does not even have much market. I would think they would make it par with One Plus and try to let users do whatever they want rather than trying to compete with Samsung. Anyways thanks!! I wanted to go 14.1 just for more stability, but seems like that's not the case anymore.

 

[Exabyter]

I have the kernel code for Oreo for our devices. Nothing yet, however Lineage is looking to add into the charter a change that requires OTG to work if stock did. Which means.... to go official it'll have to work. So if it doesn't, it'll never to official. Still working on it for Oreo, but unfortunately 14.1 here it's probably slowed down.

Any progress on this issue for Oreo??

Thanks

---------- Post added at 10:27 AM ---------- Previous post was at 10:06 AM ----------

Holy cow!! This keeps getting worse. Wondering why LG wants to make things harder for user when it does not even have much market. I would think they would make it par with One Plus and try to let users do whatever they want rather than trying to compete with Samsung. Anyways thanks!! I wanted to go 14.1 just for more stability, but seems like that's not the case anymore.

Device makers are under a lot of pressure legally and financially from customers, companies and regulators to keep devices secure and not make it easy to trojan devices, circumvent DRM and so on.

The voice of ROM hackers and tinkerers is tiny by comparison so actually most companies would be expected to follow the dollars, and not the ROMing community.

Which is why it's so nice when some vendors pay more attention to us. But as companies like OnePlus get more popular and start trying to woo the US and corporate market (see recent news on this), expect their policies to get more restrictive too. LG just reached that point years earlier.

 

[x86cpu]

Holy cow!! This keeps getting worse. Wondering why LG wants to make things harder for user when it does not even have much market. I would think they would make it par with One Plus and try to let users do whatever they want rather than trying to compete with Samsung. Anyways thanks!! I wanted to go 14.1 just for more stability, but seems like that's not the case anymore.

It's due to r ARB01. You cannot flash anything pre-10p. There video drivers were updated, so it does require different blobs.

However... my unofficial 15.1 is fairly stable. I'm running it daily too. To me it is not stable than 14.1. "official" status does not necessarily mean stable.

---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------

Any progress on this issue for Oreo??

Thanks

If this is OTG working for 15.1, that was fixed about a month ago. Encryption works but is "wonky" (sometimes requires a battery pull). Everything is ready to go official, just some last things to tidy up.

 

[Hondroid]

With "h918", x86cpu means the model of the v20, you have.... There are some models on the market... us996, h918, vs997, h910, 990ds, vs995...
You can check that, by pulling the battery out... There should be a sticker like this, where you can read the model-type:

https://i.imgur.com/gZO5KpA_d.jpg?maxwidth=640&shape=thumb&fidelity=medium

After you checked that, just post the model-name here...

With "10p", x86cpu means the original software version, you came from. In original OS you can check that, by going to the settings/about the phone, but now you are already at a custom rom and i have no idea how to check that after flashing.

I know its an h918 but im pretty sure im not on 10p bc i rooted and flashed WETA over a year ago.

 

[CM-Tester]

I know its an h918 but im pretty sure im not on 10p bc i rooted and flashed WETA over a year ago.

Flashed the newest TWRP?
Wiped before flashed the nightly?
Try flash/root with addonsu if you don't need magisk.

 

[CM-Tester]

Short Update:
Dirty Flash with the newest nightly (20180715) on us996 (with TWRP) was no problem (After it, wiped cache and dalvik). Everything seems to be smooth.

PS.
Security Patch Level is 05.06.2018 (5. June)

 

[Exabyter]

Short Update:
Dirty Flash with the newest nightly (20180715) on us996 (with TWRP) was no problem (After it, wiped cache and dalvik). Everything seems to be smooth.

PS.
Security Patch Level is 05.06.2018 (5. June)

The last time I updated (I am also using a US996) I just used the built in LOS updater which downloaded the zip file, rebooted to recovery (I'm using TWRP), invoked the flash via TWRP and restarted, all with one button push. ?

I assume it's just doing a dirty flash as well, have no idea if it wipes cache/dalvik, but I have a feeling it does not.

 

[CM-Tester]

The last time I updated (I am also using a US996) I just used the built in LOS updater which downloaded the zip file, rebooted to recovery (I'm using TWRP), invoked the flash via TWRP and restarted, all with one button push.

I assume it's just doing a dirty flash as well, have no idea if it wipes cache/dalvik, but I have a feeling it does not.

I think it didn't (just the dirty flash). But after an update it is always better to wipe cache/dalvik, so there are less problems after it.

 

[CM-Tester]

Update:

The battery life is WAY BETTER after the dirty flash to the newest us996 nightly!!!
Before, i was on an January 2018 nightly...

Thanks @x86cpu, very good job

 

[almony8]

Where can I find a build for ls997 that is from may 2017? I'm told it's hard to find but I really need a copy of it

 

[CM-Tester]

Is there still a bluetooth issue (sending/receiving files from phone to another phone) with the july builds?

 

[Exabyter]

I can't get the "Portable WiFi Hotspot" feature to work no matter what settings I try.

Is this a known problem on this device??

TIA


EDIT: I just tried the same feature on my LG G4 running an older build of LOS 14.1 (completely different mobile carrier) and it doesn't work either. Shows "error" next to the on/off button just like my v20.

I'm beginning to think that feature was someone's idea of a bad joke.

 

[CM-Tester]

I can't get the "Portable WiFi Hotspot" feature to work no matter what settings I try.

Is this a known problem on this device??

TIA


EDIT: I just tried the same feature on my LG G4 running an older build of LOS 14.1 (completely different mobile carrier) and it doesn't work either. Shows "error" next to the on/off button just like my v20.

I'm beginning to think that feature was someone's idea of a bad joke.

On my us996 with 20180715 weekly the Hotspot is running without any problems...

 

[Exabyter]

On my us996 with 20180715 weekly the Hotspot is running without any problems...

Very interesting. I have similar problems on my G4 (h811) running 2017-11-28 nightly (Gapps pico) and my v20 (US996) running 2018-07-01. (microG)

Any suggestions for what string(s) to look for in logcat to troubleshoot this? Below is a filtered/cleaned up logcat snippet at ERROR level. Note that in some cases the "set country code" apparently succeeded:

[DEVICE INFO]
build.board: MSM8996
build.bootloader: unknown
build.brand: lge
build.cpu_abi: arm64-v8a
build.cpu_abi2: 
build.device: us996
build.display: lineage_us996-userdebug 7.1.2 NJH47F 20180701 dev-keys
build.fingerprint: lge/elsa_nao_us/elsa:7.0/NRD90M/162831845a3a3:user/release-keys
build.hardware: qcom
build.host: a6f9ad0f807c
build.id: NJH47F
build.manufacturer: LGE
build.model: LG-US996
build.product: elsa_nao_us
build.radio: unknown
build.serial: LGUS99617964d33
build.tags: release-keys
build.time: 1530423031000
build.type: user
build.user: root
version.codename: REL
version.incremental: 7323eade16
version.release: 7.1.2
version.sdk_int: 25


[LOG LEVEL: ERROR]

[GOT LOTS OF THE FOLLOWING LINE, REMOVED ALL BUT THIS ONE FOR BREVITY]

07-30 10:50:09.562 W/ResourceType(3680): No package identifier when getting name for resource number 0x00000000



07-30 10:50:11.245 W/WindowManager(2442): Attempted to remove non-existing token: android.os.Binder@a28af0f

07-30 10:50:12.590 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:12.591 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:13.260 W/WindowManager(2442): Attempted to remove non-existing token: android.os.Binder@61979ff
07-30 10:50:13.369 E/ActivityManager(2442): applyOptionsLocked: Unknown animationType=0
07-30 10:50:13.490 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:13.491 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:13.550 W/TileUtils(21342): Found com.android.settings.Settings$PaymentSettingsActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
07-30 10:50:13.554 W/TileUtils(21342): Found com.android.systemui.tuner.TunerActivity for intent Intent { act=com.android.settings.action.EXTRA_SETTINGS } missing metadata 
07-30 10:50:14.037 W/AlarmManager(2442): Unrecognized alarm listener com.android.server.wifi.scanner.SupplicantWifiScannerImpl$2@960108a
07-30 10:50:14.037 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:14.046 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:14.058 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:14.070 W/NetworkIdentity(2442): Active mobile network without subscriber! ni = [type: MOBILE[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: VZWINTERNET, failover: false, available: true, roaming: false, metered: true]
07-30 10:50:14.077 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.here.app.maps/com.here.app.trafficprobegen.WifiIntentReceiver
07-30 10:50:14.215 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:14.221 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.vonglasow.michael.satstat/.GpsEventReceiver
07-30 10:50:14.221 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:14.221 E/WifiHAL (2442): Event processing terminated

07-30 10:50:15.143 E/SoftApManager(2442): Failed to set country code, required for setting up soft ap in 5GHz
07-30 10:50:15.147 E/WifiController(2442): WifiControllerSoftAP start failed
07-30 10:50:15.149 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:15.149 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:15.150 E/WifiHAL (2442): Event processing terminated

07-30 10:50:15.442 E/WifiMonitor(2442): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-30 10:50:16.061 E/WifiHW  (2442): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
07-30 10:50:16.204 W/WifiNetworkHistory(2442): Upgrading network 0 to android.uid.system:1000
07-30 10:50:16.206 W/WifiNetworkHistory(2442): Upgrading network 1 to android.uid.system:1000
07-30 10:50:16.206 W/WifiNetworkHistory(2442): Upgrading network 3 to android.uid.system:1000
07-30 10:50:16.207 W/WifiNetworkHistory(2442): Upgrading network 2 to android.uid.system:1000
07-30 10:50:16.340 W/AlarmManager(2442): Unrecognized alarm listener com.android.server.wifi.scanner.SupplicantWifiScannerImpl$2@960108a
07-30 10:50:16.341 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:16.365 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:16.367 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:16.372 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:16.380 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:16.381 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:16.391 W/NetworkIdentity(2442): Active mobile network without subscriber! ni = [type: MOBILE[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: VZWINTERNET, failover: false, available: true, roaming: false, metered: true]
07-30 10:50:16.394 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.here.app.maps/com.here.app.trafficprobegen.WifiIntentReceiver
07-30 10:50:16.421 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:16.424 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:16.424 E/WifiHAL (2442): Event processing terminated
07-30 10:50:16.441 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.vonglasow.michael.satstat/.GpsEventReceiver

07-30 10:50:17.350 E/SoftApManager(2442): Failed to set country code, required for setting up soft ap in 5GHz
07-30 10:50:17.351 E/WifiController(2442): WifiControllerSoftAP start failed
07-30 10:50:17.352 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:17.352 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:17.353 E/WifiHAL (2442): Event processing terminated
07-30 10:50:17.683 E/WifiMonitor(2442): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-30 10:50:18.445 W/WifiNetworkHistory(2442): Upgrading network 0 to android.uid.system:1000
07-30 10:50:18.445 W/WifiNetworkHistory(2442): Upgrading network 1 to android.uid.system:1000
07-30 10:50:18.446 W/WifiNetworkHistory(2442): Upgrading network 3 to android.uid.system:1000
07-30 10:50:18.447 W/WifiNetworkHistory(2442): Upgrading network 2 to android.uid.system:1000
07-30 10:50:18.604 W/AlarmManager(2442): Unrecognized alarm listener com.android.server.wifi.scanner.SupplicantWifiScannerImpl$2@960108a
07-30 10:50:18.605 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:18.610 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:18.611 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:18.613 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:18.620 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:18.621 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:18.633 W/NetworkIdentity(2442): Active mobile network without subscriber! ni = [type: MOBILE[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: VZWINTERNET, failover: false, available: true, roaming: false, metered: true]
07-30 10:50:18.638 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.here.app.maps/com.here.app.trafficprobegen.WifiIntentReceiver
07-30 10:50:18.680 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.vonglasow.michael.satstat/.GpsEventReceiver

07-30 10:50:18.746 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:18.746 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:18.747 E/WifiHAL (2442): Event processing terminated

07-30 10:50:19.689 E/SoftApManager(2442): Failed to set country code, required for setting up soft ap in 5GHz

07-30 10:50:19.696 E/WifiController(2442): WifiControllerSoftAP start failed
07-30 10:50:19.701 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:19.702 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:19.702 E/WifiHAL (2442): Event processing terminated

07-30 10:50:20.005 E/WifiMonitor(2442): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-30 10:50:20.944 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:20.945 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:21.039 W/WifiNetworkHistory(2442): Upgrading network 0 to android.uid.system:1000
07-30 10:50:21.040 W/WifiNetworkHistory(2442): Upgrading network 1 to android.uid.system:1000
07-30 10:50:21.041 W/WifiNetworkHistory(2442): Upgrading network 3 to android.uid.system:1000
07-30 10:50:21.041 W/WifiNetworkHistory(2442): Upgrading network 2 to android.uid.system:1000
07-30 10:50:21.158 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:21.165 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:21.165 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:21.633 E/ActivityManager(2442): applyOptionsLocked: Unknown animationType=0

07-30 10:50:21.725 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:21.725 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]

07-30 10:50:31.032 W/IInputConnectionWrapper(23328): finishComposingText on inactive InputConnection
07-30 10:50:31.032 W/IInputConnectionWrapper(23328): finishComposingText on inactive InputConnection
07-30 10:50:31.032 W/IInputConnectionWrapper(23328): finishComposingText on inactive InputConnection
07-30 10:50:31.049 W/IInputConnectionWrapper(23328): finishComposingText on inactive InputConnection

07-30 10:50:33.121 W/WindowManager(2442): Attempted to remove non-existing token: android.os.Binder@d33c1

 

[x86cpu]

On my us996 with 20180715 weekly the Hotspot is running without any problems...

2.4 or 5? 5 has been known is not working at the moment.

 

[CM-Tester]

2.4 or 5? 5 has been known is not working at the moment.

I checked it fastly a minute ago,- it is set to 2,4 in my device.

 

[Exabyter]

2.4 or 5? 5 has been known is not working at the moment.

Interesting. I tried both actually on both devices - no go.

I'll double-check 2.4 again tonight.

(Pity tho - 2.4 is ridiculously congested in my neighborhood. I've had hardware hotspots in the past that were so overwhelmed by all the signals around here on 2.4 ghz that they would shut down a couple minutes after power up because they couldn't find clear air to transmit on)

 

[CM-Tester]

Interesting. I tried both actually on both devices - no go.

I'll double-check 2.4 again tonight.

(Pity tho - 2.4 is ridiculously congested in my neighborhood. I've had hardware hotspots in the past that were so overwhelmed by all the signals around here on 2.4 ghz that they would shut down a couple minutes after power up because they couldn't find clear air to transmit on)

Ok i checked it again with my laptop and HotSpot of the V20 us996 (2,4 GHz)... It runs