[General Topics] Astr4y4L:
Problem with that was that the whole bootchain is signed by Lg and so when we fooled with aboot at all we changed the check-sum of the file.

Header + Code-size + Lg's signing key = the checksum....

if you look .. Oh about page 20 -something of this thread and just read all the way through to present you will see that we've tried modifying the aboot before but since it's not going to match the original then the Sum will be different resulting in No-Boot or Secure-Boot-Error-1004 or Secure-Boot-Error-1008 ...

as for compiling custom aboot from source...

well , tried that too...

mostly the problem is that from the system on a chip it securely boots the Secondary bootloader [MiniOS]

The s.b.l then has the function to boot the application boot loader [aboot]

which is the first part of our rom ...

according to everything I've found our only hope for fastboot functions is to replace aboot with aboot'functioning" by patching our current aboot or by compiling a different aboot binary.

Which Brings me back to the problem that the aboot has to be signed..

They used to have a method for early G2 and stuff developed by @codefire

i think it was , and it was run as a service, that [ Bumped ]

your boot .img files and caused them to be signed by Lg as far as your phone cared...

But thanks to an adventurous Neewb who discovered how the service worked, out came[ OPENBUMP.PY ]

Google-search it..

and at that Point It became PUBLIC Disclosure and LG noticed...

Yes Guys , the Tech's over at LG watch XDA too...LOL

and so then they patched that hole. so the story go's ...

and so thats why I'm trying to work-out a way to just use the aboot from another LG device Namely the G2. because if I can get the phone to allow a LG-G2 aboot in the place of the one it's accustomed to we can at said point Nuke /laf [ zero'd .img]

and then instead of booting into Download mode, we get fall-back which defaults to the fast-boot environment.

---> Astr4y4L takes a deep breath...

which on the G2 the fastboot binarys located in aboot didn't have crippled functions and we can then say fastboot flash bla bla bla

or fasboot boot bla bla bla

so you see the Problem remains....

WE NEED A COPY OF LG'S SIGNING KEY

generick snakeoil keys don't work

personal signing keys even purchased from a key authority wouldn't work...

Has to be LG.

so i'm going to continue to try to replace the individual pieces of the firmware swapping with other stock bits to get the features we desire without killing the signed state of the firmware...

I Have extracted the latest "un-extractable" -kdz G2 firmware from the Verizon model's .kdz file and extricated the aboot partition.

I want to test it on a device , and if after the replacement the device boots then we will be all alot happier installing twrp and root and what-ever

But I only have one working [TEST] device at the moment and I'm also developing what i've already got trying to gain full GSM functionality in a flashable package..

so I will not be testing the extracted aboot or any aboot or boot chain modification for a while...

also keep being drawn to figure out the K3 root issues, those poor K3 owners are F***ED at the moment and now my good buddy @MotoJunkie01 has had his K3 melt-down so I'm going to be focused on trying to help him back to life on the K3...

I could link you to my G2 aboot and you can write it to a zone3 or older K4 and let us know how it turn's out...

you'd save a bunch of waiting for me to ever get all the way back around to it...