| Variant | Aboot/Laf Version | Bootstacks Version | Loki/Bump Support | Assert zip |
|---|---|---|---|---|
| D800 | KitKat | Lollipop | Only Bump | Yes |
| D801 | KitKat | Lollipop | Only Bump | Yes |
| D802 | KitKat | Lollipop | Only Bump | Yes |
| D803 | KitKat | KitKat | Only Bump | Yes |
| D805/6 | KitKat | Lollipop | Only Bump | Yes |
| F320K/L/S | KitKat | Lollipop | Only Bump | Yes |
| L22 | KitKat | KitKat | Only Bump | Yes |
| LS980 | KitKat | Lollipop | Only Bump | Yes |
| VS980 | KitKat | Lollipop | Only Bump | Yes |
-FAQ-
What is bootstacks?
It's a set of images, that are essential for your device. These hybrid bootstracks use all the images from lollipop, except aboot & laf, that are from kitkat. So, we can have bump working with LP partitions.
What is in it? (Except D803 & L22)
-Aboot (KK)
-Dbi (LP)
-Laf (LP) (SIGNED WITH BUMP)
-Modem (LP)
-Persist (LP) (Except LS980)
-Rpm (LP)
-Sbl1 (LP)
-tz (LP)
Which roms it works?
CM-12.1, and any rom based on it.
CM-13.0, and any rom based on it.
LP STOCK, and any rom based on it.
What is assert?
Assert is a command line in zip script, it checks if you're flashing a compatible bootstrap with your device.
Why it only supports bump?
Because I updated all the aboot files to KK, and only JB supports loki.
Why you updated aboot to KitKat?
Because KK bootloader is more reliable, and I can merge the original kernel cmdline.
I can't enter in recovery, why?
My aboot files are the most recent KK versions, some of them have a new way to enter in recovery:
-Old Way: Hold power + vol down, then, release and hold power + vol down again.
-New Way: Hold power + vol down, then, release and hold vol up + vol down.
How D803 & L22 bootstacks are available, if they're stuck on KK?
-D803 is using D803 KK bootstacks, except by the baseband, which is the same from D801, but, edited with D803 radio files.
-L22 is using L22 KK bootstacks, except by the baseband, which is the same from D802, but, edited with L22 radio files.
Why Laf isn't giving secure booting error, if we're using LP version?
As everybody knows, until now, we were using KK Laf + KK Aboot. This was because new LP images have a new image signature. So, to make it boot on KK Aboot, I broke LP signature (Extracting the ramdisk and packing it again) and then I bumped it using [open_bump] (http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595).
Attention! Devices stuck on JB will not be add! Ex: L-01F DOCOMO
Have any issue?
[Report Here] (https://github.com/danielstuart14/bootstacks/issues)
[XDA THREAD] (http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219)