Development [Kernel][24.03.2023][Android 12] Kirisakura 3.0.1_T for Asus Zenfone 8 aka "Sake"

Search This thread

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,244
21,797
Update to 2.0.15

Hey guys and girls,


Here´s the next update.
Includes very few changes from 31.1010.0411.160.

The link to the latest firmware can be found following this link.


More changes in the changelog below:


Changelog:
- Linux-Stable upstream bumped to 5.4.228
- merge QCOM upstream up to latest one
- merge small updates to 31.1010.0411.160
- other improvements and tweaks please check github


Download:
Androidfilehost is currently broken. Zip is attached to this post



Instructions can be found in the OP!
But look at this post too :)

Have fun, enjoy the kernel and your phone.

Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
 

Attachments

  • Kirisakura_Sake_S_2.0.15.zip
    26.5 MB · Views: 58

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,244
21,797
Hey everyone,

Unfortunately some bad, but also good news following the bad ones.

My zf8 died while rebooting. It's probably some sort of hardware failure, as the device is completely dead. It can´t boot to edl by long pressing buttons, screen doesn´t do anything and when plugging it to a power source it stays completely cold as well as no LED.

The good news is that the device will be sent to repair once Chinese new year is over.

So until I have the device back to test there´s no update possible from my side.
 

Rokcy98

Senior Member
Sep 25, 2018
75
61
Italy
ASUS ZenFone 8
Hey everyone,

Unfortunately some bad, but also good news following the bad ones.

My zf8 died while rebooting. It's probably some sort of hardware failure, as the device is completely dead. It can´t boot to edl by long pressing buttons, screen doesn´t do anything and when plugging it to a power source it stays completely cold as well as no LED.

The good news is that the device will be sent to repair once Chinese new year is over.

So until I have the device back to test there´s no update possible from my side.
Sorry to hear that, hope for the best!

EDIT: if you prefer to continue the development, some of us could test the kernel for you, I could too. I really don't know if it's possible for you to work in this way, or if it's too complicated.

Otherwise, let's just wait for the device to come back (by the way, this is an issues that's regarding too many ZF8s, Asus should have said at least a word about this problem).
 
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,244
21,797
Sorry to hear that, hope for the best!

EDIT: if you prefer to continue the development, some of us could test the kernel for you, I could too. I really don't know if it's possible for you to work in this way, or if it's too complicated.

Otherwise, let's just wait for the device to come back (by the way, this is an issues that's regarding too many ZF8s, Asus should have said at least a word about this problem).
Yeah I´m hoping for the best as well. I guess I just need a bit of patience until it´s fixed.

I want to confirm myself that it wasn´t anything related to the kernel or I messed up on my own account. Generally I´m only working on devices I own and have physical access to.
So I´m waiting until my unit is fixed and then I´ll continue. :) Thanks for the offer though, I appreciate it.
 
  • Like
Reactions: Scalpos and Rokcy98

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,244
21,797
Check out who's back :)

Screenshot_20230222-125323895.jpg


PXL_20230220_111557416.jpg
 

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,244
21,797
Update to 3.0.0

Hey guys and girls,

Finally my phone is back from repair.
This release adds support for the latest A13 firmware 33.0210.0210.210.
Started from scratch and merged latest linux-stable and QCOM pretty cleanly. Afterwards added all previous features on top.

The link to the latest firmware can be found following this link.


More changes in the changelog below:


Changelog:
- Linux-Stable upstream bumped to 5.4.231
- merge QCOM upstream up to latest one
- improvements to RCU subsystem which result in lower power consumption (whether that´s noticeable for an end user is another question)
- other improvements and tweaks please check github


Download:
Androidfilehost is currently broken. Zip is attached to this post



Instructions can be found in the OP!
But look at this post too :)

Have fun, enjoy the kernel and your phone.

Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
 

Attachments

  • Kirisakura_Sake_T_3.0.0.zip
    26.6 MB · Views: 84
@Freak07 I flashed `Kirisakura_Sake_T_3.0.0.zip` using both FKM and EXKM, and both times my phone boots right to the bootloader screen :-(

(The screen that says "start" in big green letter at the top, not the fastbootd or recovery screen)

I was able to fix it by extracting the boot.img from the stock firmware, flashing that, then reinstalling Magisk. So, luckily my phone is fine, but the kernel won't boot.

The phone says it's running `WW_33.0210.0210.210` (`UL-ASUS_I006D-ASUS-33.0210.0210.210-1.1.26-2301-user.zip`).

Has anyone else had the same issue? How can I help you debug this?
 
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,244
21,797
@Freak07 I flashed `Kirisakura_Sake_T_3.0.0.zip` using both FKM and EXKM, and both times my phone boots right to the bootloader screen :-(

(The screen that says "start" in big green letter at the top, not the fastbootd or recovery screen)

I was able to fix it by extracting the boot.img from the stock firmware, flashing that, then reinstalling Magisk. So, luckily my phone is fine, but the kernel won't boot.

The phone says it's running `WW_33.0210.0210.210` (`UL-ASUS_I006D-ASUS-33.0210.0210.210-1.1.26-2301-user.zip`).

Has anyone else had the same issue? How can I help you debug this?
That usually happens when something is not matching up at all and the device crashes very very early during boot. Like flashing a non matching kernel to a firmware (e.g. a11 kernel to a12 firmware) or dts not matching the kernel.

If you´re running that specific firmware (latest a13 one with the versioning you posted) without any further changes, magisk modules etc, there´s no reason that should happen.
I guess there´s the small chance of a bad download or an unsuccessful flash. Otherwise I have no idea. Do you use a zenfone 8 flip? I don´t think the kernel would work on that.
If it boots right to the bootloader screen there´s also no chance to get any logs.


to get back to stock completely you also want to flash vendor_boot.img and dtbo.img. (as described in the FAQ)
 
  • Like
Reactions: NTICompass
That usually happens when something is not matching up at all and the device crashes very very early during boot. Like flashing a non matching kernel to a firmware (e.g. a11 kernel to a12 firmware) or dts not matching the kernel.

If you´re running that specific firmware (latest a13 one with the versioning you posted) without any further changes, magisk modules etc, there´s no reason that should happen.
I guess there´s the small chance of a bad download or an unsuccessful flash. Otherwise I have no idea. Do you use a zenfone 8 flip? I don´t think the kernel would work on that.
If it boots right to the bootloader screen there´s also no chance to get any logs.


to get back to stock completely you also want to flash vendor_boot.img and dtbo.img. (as described in the FAQ)
I am running the official A13 ROM from ASUS. I just have the Zenfone 8 (not the flip). I had no issues with your kernel on A12, so I don't know what the issue could be here. My first thought was that the download/zip file was corrupted, but if that were the case, then I assume it wouldn't flash at all.

When flashing, I thought I saw something weird, but I don't know if that's the issue or if that's normal (or if I am wrong about what I saw). I have Magisk installed (obviously) and when flashing in EXKM, I thought I saw "version 11" or something like that, when I am running Android 13. So I don't know if there is an issue with Magisk or how the kernel ZIP is detecting Magisk, or if what I saw was normal and not the issue.

Should I reflash `vendor_boot.img` and `dtbo.img` from the stock image? I just flashed (a Magisk patched) `boot.img` and the phone booted right up again. I guess I didn't fully read the FAQ, my bad.
 
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,244
21,797
I am running the official A13 ROM from ASUS. I just have the Zenfone 8 (not the flip). I had no issues with your kernel on A12, so I don't know what the issue could be here. My first thought was that the download/zip file was corrupted, but if that were the case, then I assume it wouldn't flash at all.

When flashing, I thought I saw something weird, but I don't know if that's the issue or if that's normal (or if I am wrong about what I saw). I have Magisk installed (obviously) and when flashing in EXKM, I thought I saw "version 11" or something like that, when I am running Android 13. So I don't know if there is an issue with Magisk or how the kernel ZIP is detecting Magisk, or if what I saw was normal and not the issue.

Should I reflash `vendor_boot.img` and `dtbo.img` from the stock image? I just flashed (a Magisk patched) `boot.img` and the phone booted right up again. I guess I didn't fully read the FAQ, my bad.
flashing the kernel.zip modifes boot.img, dtbo.img and vendor_boot.img, so to fully return to stock you need to flash all 3, otherwise you end up with a frankenstein configuration (which still works, but is not fully stock).

I think it´s possible for the zip to be a bad download and flash fine, but it´s extremely rare.
Here´s the md5sum of the zip on my phone, just downloaded from XDA that matches as well:
7babc5fdc298c606725ac1c17efbf29c

Which version of magisk are you using?
Can you install this app:
Use this app to flash the kernel.zip, take a log of the flash (it asks you after flashing) and share it with me?
 
flashing the kernel.zip modifes boot.img, dtbo.img and vendor_boot.img, so to fully return to stock you need to flash all 3, otherwise you end up with a frankenstein configuration (which still works, but is not fully stock).

I think it´s possible for the zip to be a bad download and flash fine, but it´s extremely rare.
Here´s the md5sum of the zip on my phone, just downloaded from XDA that matches as well:
7babc5fdc298c606725ac1c17efbf29c

Which version of magisk are you using?
Can you install this app:
Use this app to flash the kernel.zip, take a log of the flash (it asks you after flashing) and share it with me?
Thanks for trying to help, I've never had this issue before, it's weird. I hope I'm not bothering you :)

Magisk 25.2 (25200), I don't think there is a newer version unless you use an "unofficial" version.

Could the issue be something with slot A vs slot B? I'm pretty sure slot A contains the old A12 (with your 2.0.15 Kernel) and slot B (the current one) contains the latest A13. When re-flashing dtbo.img and vendor_boot.img, do I need to use "fastboot flash dtbo dtbo.img" or "fastboot flash dtbo_b dtbo.img"?

Anyway, using KernelFlasher did the same thing. ASUS logo appears, screen goes black (reboots) and then I get a screen with "START" in big, green letters (bootloader screen).

Here's the log from KernelFlasher: https://pastebin.com/KXW3kkck
 
Last edited:

Freak07

Recognized Developer / Recognized Contributor
Jan 2, 2011
6,244
21,797
Thanks for trying to help, I've never had this issue before, it's weird. I hope I'm not bothering you :)

Magisk 25.2 (25200), I don't think there is a newer version unless you use an "unofficial" version.

Could the issue be something with slot A vs slot B? I'm pretty sure slot A contains the old A12 (with your 2.0.15 Kernel) and slot B (the current one) contains the latest A13. When re-flashing dtbo.img and vendor_boot.img, do I need to use "fastboot flash dtbo dtbo.img" or "fastboot flash dtbo_b dtbo.img"?

Anyway, using KernelFlasher did the same thing. ASUS logo appears, screen goes black (reboots) and then I get a screen with "START" in big, green letters (bootloader screen).

Here's the log from KernelFlasher: https://pastebin.com/KXW3kkck
I just asked as there was a new canary version, but that didn´t give me troubles either.

The log from the flash looks good.
When reflashing stock images you never have to specify the slot in fastboot as it automatically flashes to the currently active slot.
The now inactive slot where the previous firmware was flashed to doesn´t matter. Except if something with your slots got messed up, but there´s no way to tell. If you manually switch slots, things can get messed up though.

I just tried again, started from clean stock images for the latest A13 firmware WW-33.0210.0210.210, flashed the kernel and all is fine. Something must be different on your end.
Don´t know if you run any mods, magisk modules or apps that alter some stuff, but it might be worth trying without.
 
I just asked as there was a new canary version, but that didn´t give me troubles either.

The log from the flash looks good.
When reflashing stock images you never have to specify the slot in fastboot as it automatically flashes to the currently active slot.
The now inactive slot where the previous firmware was flashed to doesn´t matter. Except if something with your slots got messed up, but there´s no way to tell. If you manually switch slots, things can get messed up though.

I just tried again, started from clean stock images for the latest A13 firmware WW-33.0210.0210.210, flashed the kernel and all is fine. Something must be different on your end.
Don´t know if you run any mods, magisk modules or apps that alter some stuff, but it might be worth trying without.
The fact that this is not working, makes absolutely no sense, it's so weird. I've never had this issue with older kernel versions.

The slot A vs slot B thing was just a thought, as I do not have any other ideas as to why it won't boot. I have never manually switched slots. I've tried everything I can think of, short of re-flashing the complete stock image. I really don't want to lose any data on my phone (yes, it's backed up, but re-configuring everything is annoying).

Thanks for trying to help me, but I think I will stick to the stock kernel for now. Maybe when the next update is released for A13, then I can try this kernel again.
 
  • Like
Reactions: Freak07

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    Kirisakura-Kernel for the Asus Zenfone 8

    Hello everyone,

    To keep it short: Here is Kirisakura - Kernel for the Asus Zenfone 8 aka Sake. The Zenfone line-up internal codenames are traditionally derived from alcoholic drinks. Two years ago the Zenfone 6 bore the title "Kirin". The Zenfone 7 was codenamed "Tequila".
    I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.

    Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
    If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
    However the kernel is built to keep battery life close to the same as you would experience the on stock kernel while being tuned to perform better in various UI related benchmarks. The same benches are used by google to verify and ensure UI smoothness on the Pixel devices. The scheduler is tuned to yield lower jitter and reduce jank frames.
    If that got your curious, I welcome you to continue reading if you´re still interested!


    This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.


    A very positive development. Google pushed for CFI and SCS to be enabled by default in the android-common kernel. In this years generation ( 5.4 linux kernel base/ SD 888 ) CFI and SCS are enabled by default. It was a lot of work to get these features working nicely on the kernel I did the years back. So it´s nice to see this is now there by default in everybody can profit from it.
    I put the explanations and links in hide tags here.

    Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features.
    The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
    If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features.

    Another security feature is Shadow Call Stack (SCS).
    SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
    ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
    If you´re interested here are a few good links:
    Google Security Blog explaining SCS.
    LLVM doc about SCS
    Android DOCs documenting SCS

    If reading about upstream in the paragraph above got you curious, have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
    Read more about the Release-Model following this link.
    This conversation on the LKML mailing list also shows the power of Linux-Stable and why it´s very beneficial to not just say it´s not worth and a potentiol source for bugs:
    Starting with the Initial Message , the following reply and a good summarizing statement.



    Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 888 that´s built into the different SKUs of the Zenfone 8.
    The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
    The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
    This kernel focuses amongst the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.

    The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
    A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
    A big thanks to all of them at this place!

    Now lets continue with a list of features in the next paragraph!


    Main Features:
    - Based on latest kernel sources from Asus for Android 12 and intended to be used on the latest Asus Stock-Firmware
    - compiled with Clang 14.0.7 and built with -O3 speed optimizations
    - Linux-Stable-Upstream included to 5.4.231
    - upstreamed CAF base for the Snapdragon 888 (qcoms internal codename "lahaina")
    - include important fixes/improvements from kernel/common
    - tune scheduler for improved jitter and less jank frames
    - reduce power consumption during deep sleep
    - remove logging while device is suspended
    - remove sleep debugging from Asus for release build
    - disable various debugging mechanisms for drivers which are not needed on a perf build (for example touchscreen, fingerprint reader, display, binder)
    - disable various debugging configs, that are not needed in a perf kernel build according to google.
    - disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
    - display tweaks to reduce power consumption on statically rendered images
    - disable unnecessary CPU errata for our specific SoC
    - disable per cgroup pressure tracking to reduce overhead
    - SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
    - free up RAM by removing reserved mem regions used only for debugging
    - implement LRNG (thanks @arter97, see arter kernel OP for more info )
    - Flashing the kernel will keep root!
    - Flashable via EXKM, FKM or TWRP (if available) on a rooted system!
    - Anykernel zip is based on the Anykernel3 release from @osm0sis


    EAS related features:
    - Implement dynamic WALT-Window size depending on current FPS, collecting information about CPU-Load to provide more precise information for the scheduler
    - EAS implementation patched up to latest CAF state
    - updates from kernel/common
    - scheduler updates from sd888/ 5.4 kernel
    - scheduler update from sony xperia 1 III kernel aiming to improve WALT

    CPU related features:
    - Power saving workingqueues enabled by default (toggleable in EXKM)
    - Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to use power efficient workingqueues. This compliments EAS in general
    - improvements to cpufreq/times/stats
    - vdso32 patches as found on Google Pixel devices (brief documentation here) (CAF 5.4 default, keep for documentation)
    - remove event debug logging
    - disable broken irq detection, disable debugmon
    - improve suspend/resume from audio driver (caf-upstream for audio-kernel)
    - cpuidle: wake only cpus for which qos has changed (this allows cores to keep idle states better)
    - disable debugging during sleep states as per qcom recommendation
    - remove RTB logging to reduce overhead
    - disable trace_printk as it shouldn´t be used on production/perf kernel builds
    - enable suspend_skip_sync to save power during suspend/resume
    - disable edac and coresight (following google on the pixel kernels)
    - disable jtagv8 debugging as recommended by qcom for perf builds to avoid potential power, performance and memory penalty
    - disable s2idle in favor of deep idle state -> improves deep sleep drain (google initially used 2idle for improved suspend/resume latency on pixel 3 and pixel 4, but disabled it on pixel 5. qcom followed suit for sd 888, but apparently didn´t see google reverting it on pixel 5. Other OEMs such as Xiaomi or OnePlus already disabled s2idle on their SD888 devices in favor of deep- read more about s2idle vs deep here)

    GPU related features:
    - GPU driver updated to latest CAF-State
    - gpu/kgsl improvements from pixel 4/pixel 5 kernel
    - add low_prio_worker thread for gpu driver (Improves performance when tearing down processes (eg, via LMK) and not blocking currently running UI from submitting work to the GPU

    File System related features:
    - upstream BFQ-MQ to latest state in linux-mainline and default to 128KB readahead
    - improve memory allocations in kernfs
    - ufs improvements from pixel 4/ pixel 5 kernel
    - improve GC as to not interfere while user interaction is happening and prevent possible jitter or latency spikes

    UI/UX/Usability related features from CleanSlate:
    - CleanSlate features made by @tbalden
    - Disclaimer: All CleanSlate features can be controlled via the free companion and config app found on CleanSlate thread here on the Zenfone 8 Forums on XDA. Please consider buying the premium versions if you enjoy using the CleanSlate features, to give a little something back to @tbalden.

    Network related features:
    - Wireguard Support (Details)
    - advanced TCP algorithms enabled
    - use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
    - includes new bbr
    - improved networking drivers from caf-upstream (especially wifi)
    - remove unnecessary wakelock from WLAN driver to reduce thousands of very short wakeups during a 7 hour deep sleep period
    - improved bluetooth performance (¹, ²)
    - Enable support for TTL spoofing

    Memory related features:
    - Speculative Page Faults left enabled (1. 2) (CAF 5.4 default, keep for documentation)
    - Fix various memory leaks in different subsystems
    - improved mm with patches from mainline
    - patches from kernel/common
    - improve memory allocations in various subsystems, video encode/decode, kernfs, cgroup
    - Backport to enable CONFIG_HAVE_MOVE_PMD (see here) , thanks @arter97
    - Backport to enable CONFIG_HAVE_MOVE_PUD (commit here) , thanks @arter97
    - free more RAM by removing unused reserved memory regions
    - mm: Micro-optimize PID map reads for arm64 (improves game performance, especially unity based games such as genshin impact)
    - MGLRU added (info here and here

    Security related features:
    - Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) (CAF 5.4 default, keep for documentation)
    - Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO (CAF 5.4 default, keep for documentation)
    - Shadow Call Stack (SCS) Security-Feature ( 5.4 default, keep for documentation)
    - enable init_on_alloc for even more security, more information can be found in the commit message (CAF 5.4 default, keep for documentation)


    Misc Features:

    Wakelock Blocker:
    - advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
    - please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
    - blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!

    Other features:
    - clean up asus drivers and fix a few warnings in kernel log
    - disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
    - fix several coding issues detected by newer Clang-Toolchains
    - enlarge dmesg size to ease debugging


    Flashing Guide, Download and Changelog

    Requirements:
    - unlocked Bootloader (this will void warranty and kill future OTA updates on all asus phones at the moment)
    - USB-Debugging in developer options enabled
    - latest adb and fastboot binaries
    - working adb and fastboot environment
    - magisk root
    - a backup of stock boot.img, vendor_boot.img and dtbo.img so you can go back to stock conditions (simplest way is TWRP or to extract from stock firmware)

    How to flash the Kernel:
    1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Asus Stock-Firmware. When the Zenfone 8 receives an OTA update it takes Asus a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
    Always make sure to run the firmware the kernel is built for!
    If you feel adventurous and try in advance, make sure you have a backup ready!

    2. Flash the kernel.zip via latest TWRP (if available), EXKM or FKM app and do a full reboot.

    3. Reboot and profit.


    DOWNLOAD:
    Download is located always in this folder:

    Important: Read after Download
    Please take a look at the second post after flashing the kernel!

    Changelog:
    Android 11

    1.0.0 Initial Release
    1.0.3 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85230887
    1.1.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85369421
    1.3.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85471991
    1.4.7 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85580815
    1.5.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85708459
    1.7.5 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85845707
    1.7.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-85845707
    1.7.9 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86004361

    Android 12
    1.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86200913
    1.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86219239
    1.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86221081
    1.0.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86546997

    2.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-86856077
    2.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87005047
    2.0.2 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87053951
    2.0.8 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87244107
    2.0.10 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87432111
    2.0.12 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87641841
    2.0.15 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-87944971

    Android 13
    3.0.0 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88195025
    3.0.1 https://forum.xda-developers.com/t/...asus-zenfone-8-aka-sake.4295287/post-88326835


    Donations:
    Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea :)
    If you like my work: http://paypal.me/freak07

    Credits:
    Asus for the development device, giving me the opportunity to create this project!
    @osm0sis for all his work, including the ak3 installer!
    @tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
    @LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
    @Captain_Throwback for all the mentoring and guidance!
    @Eliminater74 for bringing me into the game and the Inspiration
    @nathanchance for his upstream guidance and assistance
    @RenderBroken for helping me out
    @flar2 for all his work
    @joshuous for all the help he provided to me in the past!
    @arter97 for giving me advice
    @kdrag0n for his help and advices!
    @topjohnwu for magisk!


    Source Code: https://github.com/freak07/Kirisakura_SAKE_Zenfone_8
    9
    Update to 1.7.5

    Hey guys and girls,


    I hope everyone is having a good day or starting into one. Here´s the next update.
    The kernel is updated for the latest firmware:
    30.12.112.36. Make sure to update to the latest firmware before flashing the kernel to have no compatibility issues.

    The link to the firmware can be found here:


    More changes in the Changelog below:


    Changelog:
    - Import zenfone8_zs590ks.MR1-30.12.112.36 source code
    - Linux-Stable Upstream to 5.4.155
    - Merge CAF (QCOM) upstream
    - remove logging while device is suspended
    - improvements to deep sleep power consumption (ufs driver, auto hibernate)
    - reduce auto suspend delay in various other drivers
    - improvements on various subsystem like memory management, bluetooth, display, gpu etc
    - implement LRNG (thanks @arter97, see arter kernel OP for more info )
    - updates from kernel common for several subsystems
    - updated ak3 zip, thanks to @osm0sis


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    8
    Update to 1.0.8

    Hey guys and girls,


    Alright so here´s the next update. The asus source for the new updates didn´t contain anything that we didn´t already have by merging CAF and linux-stable upstream.

    However it was time for an update.

    After flashing the kernel.zip there will be a magisk module in magisk manager called AK3 Helper Module. Do not delete it.

    The link to the latest firmware can be found here:
    [/URL]


    More changes in the Changelog below:


    Changelog:
    - Linux-Stable upstream bumped to 5.4.182
    - use prebuilt clang 14.0.2
    - CAF-Upstream
    - wifi driver updated with caf-upstream
    - update f2fs fsck spoof


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07
    8
    Check out who's back :)

    Screenshot_20230222-125323895.jpg


    PXL_20230220_111557416.jpg
    8
    Update to 2.0.8

    Hey guys and girls,


    Here´s the next update.
    Source was updated for 31.1010.0411.113.
    Details in the changelog below.

    The link to the latest firmware can be found following this link.


    More changes in the Changelog below:


    Changelog:
    - Import kernel source from 31.1010.0411.113
    - Linux-Stable upstream bumped to 5.4.209
    - merge latest CAF-Upstream
    - import SSG IO scheduler from samsung galaxy s22 and set as default option
    1. -> asus switched to mq-deadline, which doesn´t work that well under load
    2. -> default google/qcom mq-bfq is a pretty gigantic driver
    3. -> ssg was developed by samsung to fit android needs, be compact should reduce overhead compared to the other two options and reduce cpu cycles
    - implement display change, that might lead to reduced power consumption
    - use prebuilt clang 14.0.7
    - update f2fs fsck spoof
    - other improvements and tweaks please check github


    Download:



    Instructions can be found in the OP!
    But look at this post too :)

    Have fun, enjoy the kernel and your phone.

    Donations are not mandatory but very welcome.
    If you like my work and want to buy me a coffee/green tea to keep development going: http://paypal.me/freak07