NOT FOR T-MOBILE LG V30/V30+ H932 OR ANYTHING OTHER THAN H930/H930G!
however, if you find an exploit to flash this to an unlocked bootloader H932 then have at it!
don't forget to unlock your bootloader first: http://developer.lge.com/resource/mo...yId=CTULRS0702
if LG's bootloader unlock page says your device isn't eligible, then you are officially screwed!
you must use fastboot to flash it to your recovery partition, from there, do the factory reset button dance
i have no idea how to do that so tell a friend
warning: if you boot the OS after flashing recovery, it will just replace it with stock recovery!
solution: swipe to enable modifications in TWRP after accepting factory reset screen (it won't actually wipe your device, twrp will ignore the request)
if you are having trouble with that, you can flash twrp to boot partition instead, and probably get away with flashing your boot image to recovery.
using it backwards like this, you will default boot into twrp, then you can select reboot -> recovery to get into your rom. it's just like having a GRUB menu, ha!
you should have an extra copy of boot.img for your current rom if you want to go this route!
- OTG storage
- Mass Storage mode (legacy sdcard as flash drive mode!)
- no-verity-opt-encrypt-6.0.zip (download here)
- f2fs (requires a custom kernel to boot, LG does not have it enabled in stock)
- exFAT sdcards
- NTFS (via OTG storage)
- time/date? (be sure to set your timezone correctly)
- STABILITY - LG really sucks at kernel modifications and any small thing could cause a NULL pointer exception and crash
- Magisk stable (root that puppy, MAKE BACKUPS FIRST!)
- SuperSU (don't flash it with Magisk lol)
- Backing up EFS and emailing it to me so I can sell to the highest chinese bidder
will probably never work:
- Encryption - LG's proprietary encryption is beyond my capabilities - it is possible to support encryption on custom ROMs however.
you can flash no-verity-opt-encrypt then format your data partition to disable encryption (i think?)
LG might just encrypt it regardless, who knows
you can disable LG's root checker daemon/service by flashing this cool zip https://build.nethunter.com/android-...rctd-disabler/
crashes can be diagnosed by entering back into recovery immediately after the crash and doing adb pull /sys/fs/pstore then uploading pstore folder for me to stare at in confusion
when all is tested and happy, I will close this thread, submit it to twrp.me, and open an official TWRP thread.
thanks for your participation
special thanks to @wolfgart for providing factory images to work off, and doing all the dangerous pre-alpha testing for me, and allowing me to use SSH to talk to his device.
SOURCES (never trust a man without them)
device tree: https://github.com/jcadduono/android_device_lge_h930
- should it be called h930? officially it is called joan/joan_global_com
- should I make it a unified device and have it automatically populate with correct model by reading serial number (H930 vs H930G) or just have it H930 for simplicity
- should I update the f2fs driver to f2fs-stable upstream
- should I include crypto libs and qseecomd for custom ROMs to use HW encryption (may cause delayed startup/longer boot in TWRP for everyone else)
- should I just hand this off to someone who actually owns the device to maintain themselves
- should I log out of XDA and go back to playing World of Warcraft for another few years