The purpose of this project is to increase efficiency of the Pixel 6 series devices by merging functional patches with minimal bloat.
If you submit bug reports without a log, you may be prosecuted...or executed.
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
To install kernel on a rooted device with EXKM/FKM
- Download ZIP and flash using the manual flasher in the app
To manually flash kernel updates
-Download ZIP for kernel and the current boot.img
-Use the below commands to flash from bootloader/fastboot
-fastboot reboot fastboot
-fastboot flash vendor_dlkm vendor_dlkm.img
-fastboot reboot bootloader
-fastboot flash dtbo dtbo.img
-fastboot flash boot boot.img
-fastboot flash vendor_boot vendor_boot.img
actually @RetroTech07 is right here. You should restore stock images via fastboot/fastbootd to avoid issues.
In the case of boot.img, dtbo.img and vendor_boot.img you probably can flash the kernel.zips over the other without running into any issue.
But since vendor_dlkm.img gets flashed on this device as well and sits on the super partition, you want to flash back the stock vendor_dlkm.img via fastbootd (not via any kernel manager while the phone is running!). The reason for that: While flashing vendor_dlkm in fastbootd, the vendor_dlkm partition actually gets resized to their original size inside the super partition.
While the device is running and either a kernel.zip containing a vendor_dlkm.img is flashed or a vendor_dlkm.img is restored via the option in EXKM/FKM app, vendor_dlkm.img is only dd´ed to the partition, essentially cutting a bit of the original size off, as the resizing part that´s happening when flashing via fastbootd is not happening there.
It´s not a problem in itself, as all vendor_dlkm.img´s shipped by the custom kernels available are smaller than the vendor_dlkm from stock firmware is.
However when hopping between kernels, I´d always restore the stock images via fastboot/fastbootd.