[Q] LG G2(F320L) not booting after OTA with stock recovery with TWRP aboot topic

Hi,
First of all i committed a mistake of thinking that with TWRP aboot + stock Recovery i will be able to do OTA upgrade, which made my phone not booting, undetectable by computer and majorly not getting the LG Flash download mode by pressing any combination of keys., Stucks at LG logo.

Device: LG-G2(F320L)
KDZ stock: F320L21V_00.kdz
1. Flashed this kdz using LG Flash Tool 2014.
2. Flashed from F320L_AutoRec.apk, the images only aboot, and recovery.
3. From DorimanX project generated the boot.img with StockROM(F320L21V_00.kdz) version bootimage RAMDISK.
Everything was fine., till then.

After that, i got the OTA pop up., So, thought of installing OTA. As I had already faced the TWRP bootloop once and in some post i remember i read flashing OTA needs stock recovery image. Here is the place I commited the mistake. So, signed the stock recovery with aboot of TWRP using loki_flash. Accepted OTA. Thats it.

From then, no booting, no recovery, no adb, no fastboot, and unfortunately NO LG DOWNLOAD MODE also it goes.
When i try to go TWRP, it stucks up after the initial TWP message.
And pressing some key combination, the device goes to LG service mode, and showing the IMEI and some list of 3 options in korean which i dont understand. By pressing any of the option device reboots and stucks with LG logo.
Even my device is not shown up in the ubuntu, when i checked "dmesg".
Can anyone help to get the device into Either download mode or fixing the boot.

[Q] Boot and aboot partitions... topic

Hi there and Merry Christmas.

I recently acquired a OnePlus One and I'm trying to understand it's boot process (every detail!).
There are 2 partitions, the boot and aboot. I copied them both to my computer.
I extracted the zImage and the Ramdisk from the boot partition.

Now what I don't understand is:

Is every boot partition having the same layout (Like ANDROID! header and such, or is that only the Little Kernel?)
When the phone is booting, what happens? What instructions does the processor run first? And how does it know?
How does it know how to extract the zImage, what is that zImage actually? Is it the same as the system kernel? Or is it a temp. kernel? Or is it only little kernel?...
Ramdisk is just a bunch of init scripts and init images and stuff, I suppose the processor loads the kernel which on turn activates the scripts?
But how? :)

And where does the aboot partition come into place?
There are no relations between boot and aboot as far as I can see?

There is also a init ELF executable in the Ramdisk, where can I find the source? Is it part of Little Kernel, or does the ramdisk
has nothing to do with it?

I know this thread is chaotic and excuse me for that :).

But my head is going to explode!