[LG V20 Guides, News, & Discussion] vitus13:
I'm running into an issue around step 3, part 4 or 5 and I'm hoping someone can decipher what's going on. I have a VS995 and I'm starting from a clean slate by using the patched LGUP to flash VS99512A_06_1114_ARB00.kdz and then doing a factory reset. From there I follow the instructions and everything goes well until step 3. At step 3, part 2 it never boots back to the lockscreen and just hangs at the (static-obscured) verizon screen forever. I am able to get to TWRP by issuing an 'adb reboot recovery' however, so I press onwards. When I get to step 3, part 5 there is a note to verizon users that this boot might take >20 minutes, so (after I wait 20 minutes to be sure) I follow the verizon-specific steps to restore the bootbackup.img. It took me a bit to realize that, after step 3, part 5, I had in fact reached the lock screen - it was just obscured by the static mentioned in post #2 of this thread. No big deal, I cleared it as described. I did execute step 3, part 6 even though it's essentially the same steps as the verizon note from step 3, part 5. But I did it anyway to be safe.

However, at step 3, part 7 the 'adb reboot recovery' command does not get me back to TWRP a second time. Instead of rebooting to TWRP it reboots to the system lockscreen again. I re-executed step 3 from the beginning and again when I got to step 3, part 7 it did not reboot to TWRP, but instead booted to the system lockscreen. So I set about running step 3 a third time, but this time ensured I captured the logcat logs from the very first moment after booting after installing SuperSU. The following lines seem to indicate that something went wrong with the first-boot work that SuperSU does:

Ignore the preceding line numbers, those are so you can correlate to my full notes.

134 01-01 00:39:05.170 1234 1234 I launch_daemonsu: (service) start
135 01-01 00:39:06.771 1346 1346 I launch_daemonsu: (service) /su not mounted yet
136 01-01 00:39:06.908 1356 1356 I launch_daemonsu: (service) copying boot image backups from /cache to /data
137 01-01 00:39:08.027 1424 1424 I launch_daemonsu: (service) loopsetup(/data/su.img):
138 01-01 00:39:09.389 1490 1490 I launch_daemonsu: (service) abort: mount failed

Now, the Verizon-specific instructions in step 3, part 4, mention to wipe the cache after flashing SuperSU. The logcat lines suggest that SuperSU had stashed some backups in the cache during the install procedure. Maybe related?

Here are my full notes. Apologies for the stream-of-consciousness writing / lots of typos. I was more focused on writing everything down than on grammar.

1	NOTES:

2	Flash KDZ
3	factory reset
4	skip everything in OOBE, no sim
5	Enable developer options
6	screen on while charging
7	don't check apps installed via adb
8	step 1 works as planned
9	run 'run-as con' and 'chmod' from step 1 shell
10	adb install terminal apk
11	run 'applypatch' from terminal emulator
12	logcat output indicates to run step 2
13	run step 2, phone reboots to fastboot, vibration starts
14	run step 3, phone reboots to LG, still vibrating, vibration frequency lowers a few times
15	phone continues to verizon boot screen (verizon logo + four colored dots on white background), still vibrating
16	logcat during this time:
17	07-29 21:45:59.277 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
18	07-29 21:46:00.278 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
19	07-29 21:46:00.889 928 1066 D ThermalEngine: ACTION: CLUSTER - Setting CLUSTER[0] to voltage 925 freq = 1593600
20	07-29 21:46:00.889 928 1066 D ThermalEngine: ACTION: CLUSTER - Setting CLUSTER[1] to voltage 1005 freq = 2150400
21	07-29 21:46:01.278 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
22	...
23	7-29 21:48:22.333 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
24	07-29 21:48:22.397 1050 1050 I ServiceManager: Waiting for service AtCmdFwd...
25	07-29 21:48:23.333 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
26	07-29 21:48:23.398 1050 1050 I ServiceManager: Waiting for service AtCmdFwd...
27	07-29 21:48:24.333 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
28	07-29 21:48:24.398 1050 1050 I ServiceManager: Waiting for service AtCmdFwd...
29	07-29 21:48:25.000 958 1372 D audio_hw_spkr_prot: spkr_calibration_thread: wsa speaker idle 301,minimum time 1800
30	07-29 21:48:25.334 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
31	07-29 21:48:25.398 1050 1050 I ServiceManager: Waiting for service AtCmdFwd...
32	07-29 21:48:26.035 928 1066 D ThermalEngine: ACTION: CLUSTER - Setting CLUSTER[0] to voltage 925 freq = 1593600
33	07-29 21:48:26.036 928 1066 D ThermalEngine: ACTION: CLUSTER - Setting CLUSTER[1] to voltage 985 freq = 2073600
34	07-29 21:48:26.334 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
35	07-29 21:48:26.399 1050 1050 W Atfwd_Sendcmd: AtCmdFwd service not published, waiting... retryCnt : 1
36	07-29 21:48:27.335 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
37	07-29 21:48:28.335 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
38	07-29 21:48:28.399 1050 1050 I ServiceManager: Waiting for service AtCmdFwd...
39	...
40	07-29 22:04:37.704 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
41	07-29 22:04:38.704 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
42	07-29 22:04:39.704 1089 1173 E slim_daemon: [NDK] bindNDKSensors: Sensor server is unavailable.
43	07-29 22:04:4
44	Left it in this state for 20 minutes. This is where I previously flashed bootback.img again.
45	This time round I just tried a normal reboot via 'adb reboot'. still vibrating at LG screen.
46	proceeds to verizon four-dots screen. still vibrating. logcat back to showing above messages.
47	Ran 'adb reboot recovery', this brought me to red exclaimation mark screen. still vibrating.
48	Waiting. LG screen, vibrating.
49	Waiting. This time it went to TWRP. Still vibrating.
50	Vibration stopped after I hit cancel on the password prompt in TWRP.
51	Wipe > format data > yes
52	Following VS995 instruction variant:
53	adb push supersu
54	4.1. flash super su
55	4.2. wipe > format data > yes
56	4.3. wipe > advanced > dalvik,data,cache > yes
57	4.4. reboot > system
58	red ! and vibrating, waiting. LG screen, vibrating. no static. waiting.
59	quick screen flash to black. LG screen, vibrating. no static. waiting.
60	Verizon logo with four dots. no static. waiting.
61	logcat is complaining about the sensor server again.
62	Since I'm now at step 3 part 5, I'll following the VZW-specific advice here and pull battery / go to fastboot.
63	flashed bootbackup.img. fastboot reboot
64	LG screen, vibrating. waiting.
65	static, verizon screen w/ four dots behind static. waiting.
66	static, something is going on back there, can't tell what. no logcat yet.
67	22:23. 22:25. 22:27. 22:29. 22:32. 22:35. 22:43. Still no logcat. Trying fastboot again.
68	Pull battery. fastboot.
69	fastboot flash boot bootbackup.img
70	fastboot reboot
71	LG screen, vibrating. waiting
72	static verizon screen, vibrating. waiting
73	movement behind the static, like last time. vibrating. waiting.
74	This time I thought to try locking screen to clear static. sure enough that did it.
75	Skipped everything in OOBE.
76	developer mode. Disable updates. enable usb debugging.
77	step 3, part 6 is to flash bootbackup.img. Doing it again anyway, to be safe. Graceful poweroff via OS.
78	fastboot flash boot bootbackup.img
79	rastboot reboot
80	LG, vibrating, waiting.
81	static, verizon, waiting.
82	lock, clear static, unlock
83	step 3, part 7
84	adb reboot recovery
85	LG, vibrating,
86	static, behind static is something black. vibrating, waiting.
87	LG, vibrating.
88	static, verizon, vibrating. system lockscreen (static).
89	clear static, still vibrating!?
90	adb reboot recovery again
91	LG vibrarting
92	static, black background, vibrating. waiting.i
93	22:55. no logcat.
94	22:57. tried lock button in case TWRP had launched but was obscured by static. No effect.
95	22:58 LG screen, vibrarting, verizon screen, static, logcat, system lockscreen (static, no vibrating)
96	adb shell pm list packages | grep -i su --->> no root.
97	adb reboot recovery
98	LG, vibrating
99	black static, vibrating, waiting
100	LG, vibrating, lockscreen w/ static & vibrating
101	Going back to beginning of step 3, not sure what went wrong.
102	adb reboot bootloader
103	vibrating, bootloader
104	step3.sh. Lots of OKs, noticed a typo near last line: boott.img
105	LG, vibrating. waiting.
106	verizon, vibrating, no static. waiting. logcat complaining of sensors.
107	adb reboot recovery
108	red !, vibrating, waiting
109	LG, vibrating, waiting
110	TWRP launches, so far so good. vibrating
111	Hit cancel for password, vibrating stops. Swipe to allow modifications
112	4.1.adb push supersu
113	4.1.install supersu
114	4.2.wipe data
115	4.3.wipe dalvik,data,cache
116	4.4.reboot
117	red !, vibrating, waiting
118	LG, vibrating 23:17
119	verizon, no static, vibrating
120	logcat is complaining about sensor server.
121	adb reboot recovery
122	red !, vibrating, waiting
123	LG, vibrating, waiting
124	TWRP. didn't ask for password, stopped vibrating when swipe for modification
125	no sign of su binary under /system. Not sure if it's supposed to be there or not
126	Setup logcat to tee to a file, so I can inspect early reboot logs after flashing su/rebooting
127	4.1. install supersu
128	4.2. wipe data
129	4.3. wipe dalvik,data,cache
130	4.3. reboot system
131	red !, vibrating, waiting
132	LG, vibrating, waiting
133	verizon screen, vibrating, waiting
134	01-01 00:39:05.170 1234 1234 I launch_daemonsu: (service) start
135	01-01 00:39:06.771 1346 1346 I launch_daemonsu: (service) /su not mounted yet
136	01-01 00:39:06.908 1356 1356 I launch_daemonsu: (service) copying boot image backups from /cache to /data
137	01-01 00:39:08.027 1424 1424 I launch_daemonsu: (service) loopsetup(/data/su.img):
138	01-01 00:39:09.389 1490 1490 I launch_daemonsu: (service) abort: mount failed
139	pull battery -> fastboot
140	fastboot flash boot bootbackup.img
141	fastboot reboot
142	LG, vibrating
143	verizon, static, vibrating, no logcat yet
144	OOBE? Because I wiped /data? No logcat during OOBE :(
145	Back in OS. At least logcat has given me something to ask about on XDA.

I also note that at the end of step3.sh, there's a typo: boott.img, which should be boot1.img line prior lines.