[General Topics] MotoJunkie01:
As more solid development comes forth, in addition to some general housekeeping & maintenance of existing development threads, this device will have easy to locate guides, mods, kernels, and hopefully, a functional & easy to install TWRP custom recovery. I recently ported a TWRP build for the Zone 3. Now getting permanent and seamless installation should follow. The same goes for the Domestic SIM Unlock (DSU) mod to which you referred in your post. The problem now with the DSU mod is that I formulated it during the very early days of the Zone 3, when Build VS425PP2 was still available as an OTA update to the initial release firmware. As firmware builds progressed, and the maintaining of root access became increasingly problematic with each passing build, we slowly began to surmise that firmware downgrading (by modding LG UP device flashing protocols.), was the only known methodology by which to regain root access on many builds. So, going back to the DSU Mod we mentioned, that Mod was dependent, among other things, on the Partition Index Table & baseband firmware structure of the PP2 Build. If you are familiar with downgrading stock firmware packages, then you'll recall that while downgrading can be usually be performed safely & efficiently, with no great concern of the risk of hard bricking a device. However, downgrading also brings me to my point -- and a consistent phenomenon which occurs across pretty much all of the manufacturer spectrum -- once a partition index table update has been flashed to the eMMC of a smart device, there is no unringing the proverbial bell. For example, while it is certainly feasible to downgrade from a newer build to an earlier build, the partition index itself can never be reverted back to that earlier build. And this isn't generally a negative factor. Updated partition indexes are normally a positive thing, and bring many updates in security features, performance standards, etc. Example: the A/B partitioning system incorporated into the release of Android 7.0 Nougat, which allows for seamless and in the background OTA installations without the need for an immediate reboot. But in certain isolated situations, the DSU Mod being the case in point, I am currently unable to replicate the mod due to changes in size & format of /fsg, /ssd, /modemst1, /modemst2, and /fsc -- changes which simply cannot be reverted to their original, initial firmware release state. Thanks to the hard work of Devs like [MENTION=8236433]Astr4y4L[/MENTION], at least cellular & data connectivity have been fixed in scenarios involving downgrading. Even now, another perfect example of this involves the Zone 3 members who own a device which shipped with PP5 firmware builds. Downgrading from that particular build caused screen resolution bugs, video driver failures, a failure of cellular communications, among other things. Last I heard [MENTION=8236433]Astr4y4L[/MENTION] was decompiling the application bootloader and has made some recent developments and headway on those issues.

Yes I've rattled on long enough. But, due to our upcoming revised and revisited downgrading/rooting tutorials, this paragraph was the best way to get new & old thread members up to speed on things.