WARNING #1: Messing with boot partitions can be dangerous. Don't try it if you don't know what a BRICK means!
WARNING #2: You must flash a BUMP recovery before trying it, I recommend @blastagator one!
WARNING #3: It only supports BUMP kernels, so, checkout with your rom maintainer before flashing!
/* *** Disclaimer * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. Please do some research * if you have any concerns about features included in these packages * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. * BOOM goes the Dynamite */
If you're on CM-12.1, CM-13.0 or even LP STOCK, you'll need flash a boostacks, but why use hybrid?
Hybrid bootstacks were made thinking on stability and being as closest as possible to stock.
All of them, use the most recent aboot/laf & modem compatible. Also, devices without official lollipop have here a workaround:
-D803 variant has its own package, that brings KK files, with a modified d801 lp baseband.
-L22 variant has its own package, that brings KK files, with a modified d802 lp baseband.
Also, if you are still not satisfied, I made a WIKI with many infos about bootstacks, that you can found on my github or the most important parts here:
D803 (KK + LP BASEBAND)
D805/6 (SAME PACKAGE FOR THESE TWO VARIANTS)
F320K/L/S (ONE PACKAGE FOR EACH VARIANT)
L22 (KK + LP BASEBAND)
What is bootstack?
It's a set of images, that are essential for your device. These hybrid bootstracks use all the images from lollipop, except aboot, which is from kitkat. So, we can have bump working with LP partitions.
What is in it? (Except D803 & L22)
-Laf (LP) (BUMP)
-Persist (LP) (Except LS980)
Which roms it works?
CM-12.1, and any rom based on it. (Except RR with stock kernel. Workaround: Custom kernel.)
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 and L22 are available, if they're stuck on KK?
-D803 is using D803 KK bootstacks, except by the modem, that is the same from D801, but, edited with D803 modem 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.
More info about files: github.
- @Rashed97 , for all his work, and the original zip packages.
- @Drgravy , for the updated bump packages, that I use as base.