jeudi 20 août 2015

[BOOT][CAF][ALL-VARIANTS] G2 Hybrid Bootstacks



Hi, everybody! Today I'm bring up here, my hybrid bootstacks packages.

WARNING: Messing with boot partitions can be dangerous. Don't try it if you don't know what a BRICK means!


Code:


/*  *** 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 this KERNEL
* 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
*/


Why use hybrid boostacks?
If you're on cm-12.1, you'll need flash a boostacks, but why use hybrid?
Hybrid flash zips, were made thinking on stability and closest possible to stock.
All of them, use the most recent aboot/laf & modem compatible. Also, devices without official lollipop, have here a workaround:
-D805/6 variant has its own package, that brings lp files from d802 with a modified lp baseband.
-D803 variant has its own package, that brings KK files, with a modified lp baseband. (WIP, NEED A TESTER)
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:


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 & laf, that are from kitkat. So, we can have bump working with LP partitions.

What is in it? (Except D803)
-Aboot (KK)
-Dbi (LP)
-Laf (KK)
-Modem (LP)
-Rpm (LP)
-Sbl1 (LP)
-tz (LP)

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 & D805/6 bootstacks are available, if they are stuck on KK?
-D805/6 share the same hardware with D802, except MODEM. So, it uses D802 bootstacks and an edited D802 baseband with d805 modem files. Also, the KK aboot/laf are from D805, this way it doesn't mess kdz update.
-D803 is using D803 KK bootstacks, except by the modem, that is the same from D801, but, edited with D803 modem files.

More info about files: github.

DOWNLOADs: On my website.

Thanks to:
- @Rashed97 , for all his work, and the original zip packages.
- @Drgravy , for the updated bump packages, that I use as base.



Aucun commentaire:

Enregistrer un commentaire