[G3 Android Development] autoprime:
not that I don't believe you... but are there posts showing users getting bricked after trying autorec? and when you say "bricked"... since the G3 is unbrickable... do you mean they end up in "QHSUSB_DLOAD 9008" mode where they can just reflash TOT partitions with LG DIAG Tool... or what?

autorec simply flashes a downgraded aboot.img (bootloader), laf.img (download mode) and flashes TWRP. the downgraded aboot.img is what gives everyone the ability to use BUMP. laf.img is downgraded because for download mode to work aboot and laf need to match the same version (10L, 20C etc).

if on stock 30B kdz with temp root... I would have assumed one could run autorec (I personally just flash everything manually but people love 1-click tools that don't explain how they work) to downgrade aboot/laf allowing BUMP ability again. Problem is... another part of the puzzle to get stock kernel/boot.img actually booting after the downgraded aboot from AutoRec... the stock boot.img needs to be bump'd because the new boot.img signatures from L and M aren't what the downgraded aboot.img is expecting... it wants an old KK-style signature or it wants BUMP... so BUMP it is. Anyway... due to stock boot.img not being BUMP'd by AutoRec the phone would not be able to boot into Android BUTTTTT AutoRec also flashed TWRP and the user should be able to boot into TWRP and then flash my modem-hybrid, bootv2 and the SuperSu 2.52 zips for perm root.

Not sure there is a way to keep perm root if not flashing my repacked boot.img... so if you're on 30B KDZ and want root.. it's very possible you'll need to do the AutoRec steps for the ability to run custom boot.img's. So if this is true... I'm not really sure why anyone would try to take the 30B KDZ THEN try to root/twrp... vs having that all sorted before stepping up to M. Of course.. there may be a way to root 30B KDZ flashers without a custom boot.img.... but until I'm able to get M on my own G3 (D851) I'm unable to test things and have to go completely by what's reported in this thread. :eek: ;)

SO.. I'm curious if people on 30B KDZ using AutoRec actually checked to see if they could boot into TWRP... of if they just couldn't boot back into Android (due to lack of BUMP'd boot.img) and assumed the phone was bricked. If someone can confirm that even TWRP doesn't work and the phone actually is bricked... then that would mean that the downgraded aboot.img does not like the 30B sbl1 and dbi partitions... which would mean that in addition to downgrading aboot and laf... users would have to also downgrade sbl1 and dbi. But again... until I can confirm that users are actually bricking after AutoRec and not just failing to boot into Android.. those extra steps may not even be needed.

AutoRec funny business aside... the steps below will guarantee permanent root for those on 30B with no TWRP....

The manual steps to downgrade bootloader would be to download the aboot, dbi, laf and sbl1 images from here - http://downloads.codefi.re/autoprime/LG/LG_G3/D855/stock_partitions/10A_16G

(Ignore that the folder says 16G.. it'll work for both 16 and 32GB users)

Also grab TWRP from here - https://dl.twrp.me/d855/

And also grab the bootv2, modem-hybrid and supersu 2.52 zips from the OP.

Place all 5 .img files + 3 zips on your internal storage

adb shell
su
dd if=/sdcard/4-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/12-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/2-sbl1.img of=/dev/block/platform/msm_sdcc.1/by-name/sbl1
dd if=/sdcard/3-dbi.img of=/dev/block/platform/msm_sdcc.1/by-name/dbi
dd if=/sdcard/twrp-2.8.7.0-d855.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

at that point you have downgraded the entire bootstack and installed twrp. you can now reboot into TWRP by typing : "reboot recovery" into the adb shell you still have open (no quotes).

Once in TWRP you can flash the bootv2, modem-hybrid and supersu zips. You should have a rooted 30B at that point.

Seems like the long way for perm root on 30B tho... KDZ flashes are for those who don't want root (or I guess also for people who like to do things the long way). ;)

Hopefully this helps someone out there. If someone feels this info can help someone else out.. link them to this post rather than giving them just the steps for a fix.. maybe a few will learn some things :good:

(i'm not saying it's impossible to root 30B without touching bootloader/boot.img... but until someone has a breakthrough the only way for perm root at the moment would be the steps described above).