[LG Optimus G Pro] culot:
[/COLOR]

Without a device to test on, I'm shooting blanks in the dark. For someone with the device, and the inclination to experiment, this should be simple. With the first two builds I posted it was booting; with the second build all the partitions were loading fine; SELinux was roaring up like whoa; there is really very little to be figured out here.

Take a look at the blastagator g2 TWRP repos on Github, take in the e980 & gproj-common repos from CyanogenMod's cm-11.0 repos (I've had Selinux issues with using cm-12.0 with G2 TWRP builds, though oddly no Selinux issues with Volt TWRP builds). Maybe peep what I've done my repos, and pick through all the commits where I've broken stuff, which should be easy, because you as a device-holder can test; especially peep the twrp.fstab and thermal control stuff, because I think I've got that close or right on.

Really, this should be a simple project that takes very little time to bring to complete fruition. F2FS support would even be simple to add to the kernel, allow the userdata and cache partitions to take advantage of that uppity zippidy booyah (in @Snepsts name I pray, amen).

Using the same formula, I got the latest TWRP running on an LG Volt in just a couple of hours (though without touchscreen, working on it... eventually). And I should mention I'm a rank amateur who less than 6 months ago never even used a smartphone before. :P If I can do it, so can any number of y'all.

This is where I started: go there and fuss shiz up.

- Always make sure to Lokify or open_bump.py your recovery images. This is what takes care of the security errors on boot.

- Testing these custom 'recovery.img's is relatively safe. If one doesn't boot, you can just boot into your Android system like normal, and then use Flashify or whatever to flash a previously working recovery back. No sweat off your gall, no damage done. Using the features *inside* the recovery can be risky, just because they might not all work properly yet (pretty sure most work flawlessly though, the file backup and restore stuff, the flashing stuff, the *vital* stuff), and I recommend you take a backup in non-my-TWRP, then copy that backup off-device. That way you are guaranteed satisfaction if the grit hits the fan. At least do a Titanium Backup. Stay safe.

(If would be beneficial to enable Fastboot mode, IMO, but I do not know how to do that on the Gpro (I did it once on accident, forgot how).)

If you need any help, I got'cha back.

EDIT:

If this call to action doesn't bear green peaness and country goodness, y'all can flood me with logs from either the 2nd or 3rd (last?) builds I posted, and I can see what I can do. Instead of just fixing things, I've also been feature twiddling, which surely resulted in the last build not booting.

Try the 2nd recovery image i posted, and post the dmesg, then reboot out of TWRP and into Android, and do a Bugreport, which will contain the last_kmsg, and perhaps other helpful hardware info (mostly that last_kmsg). Those are logs I can use, those are the meaty ones -- along with the TWRP recovery.log.

If you don't know how to pull logs: get Minimal ADB.

Do this after you boot into TWRP:

adb shell cat /proc/last_kmsg > lastkmsg_0001.log

If the last_kmsg command comes back and say there is no last_kmsg, then you can do this:

adb shell cat /proc/kmsg > kmsg_0001.log

This will run until you close the window or unplug your device's USB connection, as the KMSG continually is logging whatever is going on -- but it also can store valuable older data in it, stuff that might not be privy to dmesg, which you'll run after this. I recommend just unplugging it after it runs for like 30 seconds, then replug the USB in.

adb shell dmesg > dmesg_0001.log

Also apparently you can use the app "syslog" from the play store and check "last kernel log" to provide the log. Not tried it, but might be easier. Supposedly "It takes multiple logs, scrubs the personal data, and zips them for you... Makes it nice and easy." I'm not sure what personal data there is to scrub, so if that's a concern that'd be the way to go. The personal data issue is only concerning the BUGREPORT command, which picks up all kinds of logs -- the dmesg, last_kmsg, and TWRP recovery.log contain nothing personal (nothing personal).

Do this after you reboot out of TWRP and into Android:

adb bugreport > bugreport_0001.log

I *think* that'll provide about as much information as possible to figure it out. Unless someone else takes the reins. Whatever. Y'all provide logs and I'll give it another whirl.