[LG V30 Guides, News, & Discussion] sneak:
[MENTION=3250376]ChazzMatt[/MENTION] - I didn't know your "settings images" were just the normal settings.. for some reason I thought it was something else.. my mistake.. It's cool you posted it but I'll definitely look through those myself. I actually enjoy setting all the things up..

Anyways I made a log of everything I did (not a guide, just a documentation of any issues I ran into during this experience). Hopefully it's thorough and I missed nothing, but I was a bit distracted and going from room to room as well.. trying to get things working properly because I did have a few issues. However, all issues that I did have revolved around the inability for my computer to recognize the phone while the phone was in bootloader mode. I was able to successfully do everything from another computer. Trying different USB ports on my own PC (USB 2 and 3, front and rear panel) as well as the other identical cable that came with the one I ordered didn't work. I have no other Type C cables in my reach.

I noticed by the way that either Android 8 or Android 8 specifically for the V30 has Facebook and Instagram installed by default -- how disgusting :eek:

[MENTION=4068271]forgiven90[/MENTION] - maybe this will help resolve whatever issues you had?

As a re-cap the phone I purchased was the LS998 V30+ from monstertechbids on eBay...

Powered OFF the phone

Held VOLUME UP and plugged in USB cable to enter download mode

ran LGUP from this post

Flashed US99810c_03_1216.kdz in PARTITION DL mode using LGUP

Clicked "Select All" then "OK" and clicked "Yes" on partition change warning

At this point I noticed the phone's screen was black and every 5 or so seconds for a brief moment (half a second or less) the well known "broken android" icon would appear and underneath in white text was "no command". I ignored this and proceeded.

Initiated master reset as explained here

Skipped everything possible for initial Android setup and confirmed software version of US99810c with security patch from December 1, 2017

Powered OFF the phone

Held VOLUME UP and plugged in USB cable

Flashed US99820b_03_0524.kdz in UPGRADE mode using LGUP

"Error: ox4, Not support cross model download LS998 to US998"

Closed LGUP and attempted to flash again thanks to this post

"Error: ox4, Not support cross model download LS998 to US998"

Closed LGUP, unplugged and REBOOT the phone (back to normal boot) using VOLUME DOWN and POWER keys (pressing/holding power didn't work)

Held VOLUME UP and plugged in USB cable to enter download mode THEN ran LGUP and attempted flash again

"Error: ox4, Not support cross model download LS998 to US998"

Flashed US99820b_03_0524.kdz in PARTITION DL mode using LGUP thanks to this post

Clicked "Select All" then "OK" which resulted in the successful flash of US99820b_03_0524.kdz

Maybe whether or not we must choose PARTITION DL rather than UPGRADE for a successful flash of Oreo US998 is dependent on which KDZ we choose to flash? (Again, I was using US99820b_03_0524.kdz)

Skipped everything possible for initial Android setup and confirmed software version of US99820b with security patch from May 1, 2018

Put the phone in Photo Transfer Mode after enabling developer menu, OEM unlock and USB debugging

"adb devices" confirms connection after allowing the computer through the phone's prompt

"adb reboot bootloader" successfully boots to bootloader

Here's where I run into issues.

"fastboot flash unlock new_unlock.bin" resulted in "< waiting for any device >"

Tried multiple USB2 and USB3 ports on the front and rear of my PC and the other identical cable that came in the mail today, which I ordered specifically for this phone

Was initially using my old, leftover installation of ADB (15 second installer here on XDA) but also tried removing adb from the environment variables (to ensure I was using the ones I was about to try instead of the one I had already installed years ago) and using Google Minimal ADB and Minimal XDA ADB.

My old ADB installation had a slightly different error (technically) of "< waiting for device >" (basically same thing)

None of these ADBs are able to list/see devices once the phone is in bootloader

Selected "Power Off" from phone and it left bootloader and did a normal boot instead of powering off

Confirmed OEM unlock and USB debugging is enabled and tried again but resulted in same error

Connected to another PC and allowed the PC on the phone for USB debugging

Successfully flashed new_unlock.bin and unlocked the bootloader

Due to distraction I forgot to type "fastboot reboot" and disconnected the phone or something, so I held power and volume down until the phone reboot

Skipped everything possible for initial Android setup and made sure OEM unlock was not available after enabling developer menu

"adb reboot bootloader"

"fastboot flash recovery twrp.img" (Using this version)

Resulted in this error: "FAILED (status read failed (Too many links))"

Tried another USB port and it successfully flashed TWRP to the recovery partition

"fastboot boot twrp.img" resulted in the phone booting into normal boot instead of TWRP

Tried using a boot to recovery app, forgetting IT REQUIRES ROOT :silly:

Got TWRP-3.2.3-7-default.img instead of the one I was using and tried flashing it to recovery partition and now it boots into TWRP just fine

Swiped to allow modifications then backed up system partition (I don't have a microSD so I transferred it through USB to the computer)

Factory Reset

"Wipe Data", "Format Data" then typed "yes" and proceeded

Got the mount errors mentioned in the instructions so I reboot to recovery via TWRP as instructed

Swiped to allow modifications then repeat step from 2 bullet points ago. Worked this time!

As instructed, reboot to recovery again. Swiped to allow modifications

Mounted the device to transfer the backup to the computer, but for some reason it booted into the normal boot mode so I switched it from Photo Transfer Mode to File Transfer Mode

Took the opportunity to place Magisk-v17.3.zip, no-verity-opt-encrypt-6.0.zip and lg-rctd-disabler-1.0.zip onto the device

Unlocked developer menu again and enabled USB debugging while also allowing the PC through phone's prompt

"adb reboot recovery" then swiped to allow modifications

Flashed Magisk, encryption disabler and root check disabler

Reboot to system

Installed a root checker and it required an update to Google Play Services to work, which I allowed and it still would not detect a rooted device

Ran Magisk and was invited by prompt to update Magisk Manager (I accepted) and update Magisk to version 18 (I declined)

Clicked on the SafetyNet Check and it was successful

Tried root check again and it successfully displayed as rooted, immediately

Great, now that's all done and hopefully people will see the potential issues by looking through that story of my journey converting the LS998 to US998, unlocking the bootloader, rooting the phone, etc...

[MENTION=3250376]ChazzMatt[/MENTION]

My questions:

Is it okay to allow the Magisk app to update Magisk to version 18?

Was it ever discovered how to remove or "remove by replacing with a blank image or something else" that nag screen about the bootloader being unlocked?

If I use LGUP to flash a KDZ I don't need to clear any caches or re-flash Magisk? This is important because I don't know why I can't access the phone in it's bootloader state on my PC and I can't always use that other PC.

I saw a post but can't find it anymore about how to remove the factory installed apps we don't want on the phone (I think it was via adb). Any idea on this?

For now I'm going to try to nandroid with TWRP and attempt a KDZ flash of the latest Oreo version via LGUP. After this I'll try putting in those Magisk modules for call recording and the other things.

EDIT: Well I tried using the reboot to recovery app and it presented me with the broken droid and "No command" text but this time it's not blinking on intermittently... it's stuck there. I tried using adb to reboot to recovery and it results in the same "No command" screen.