My HowTos for the ASUS Zenfone 8

Contents

1. My HowTos for the ASUS Zenfone 8
   1. Contents
   2. Introduction
   3. News
   4. History
   5. Instructions to compile the OmniROM for the ASUS Zenfone 8
      1. How to compile the OmniROM for the ASUS Zenfone 8
      2. How to compile the OmniROM 12 for the ASUS Zenfone 8
      3. How to compile the OmniROM 13 for the ASUS Zenfone 8
      4. How to compile the OmniROM 14 for the ASUS Zenfone 8
      5. Infos for building an Android 14 based Custom ROM image in Q1 2024 or later
      6. How to compile the OmniROM 15 for the ASUS Zenfone 8
      7. How to compile the OmniROM 16 for the ASUS Zenfone 8
   6. Instructions to compile other Custom ROMs for the ASUS Zenfone 8
      1. How to compile other CustomROMs for the ASUS Zenfone 8
      2. Compiling /e/ for the ASUS Zenfone 8 using the docker image
      3. How to compile LineageOS 22.x for the ASUS Zenfone 8
      4. How to compile /e/ based on Android 15 for the ASUS Zenfone 8
      5. How to compile the official LineageOS 22.2 for the ASUS Zenfone 8
      6. How to compile the crDroid CustomROM for the ASUS Zenfone 8
      7. How to compile the evolutionX Custom ROM for the ASUS Zenfone 8
      8. How to compile the evolutionX Custom ROM for the ASUS Zenfone 8 with kernelSU
      9. How to compile LMODroid 6.x for the ASUS Zenfone 8
      10. How to compile the iodeOS 4.x for the ASUS Zenfone 8
      11. How to compile the iodeOS 6.x for the ASUS Zenfone 8
   7. Instructions to compile TWRP for the ASUS Zenfone 8 
      1. How to compile TWRP for the ASUS Zenfone 8
      2. How to compile the image for TWRP 3.7.0.12-1 w/ the bootctl binary
      3. How to create a TWRP image for LineageOS based ROMs using a script
   8. Instructions to compile OrangeFox for the ASUS Zenfone 8
      1. How to compile the OrangeFox Recovery for the ASUS Zenfone 8
      2. How to create a OrangeFox Recovery using the OrangeFox Recovery Builder 2024
      3. How to create a OrangeFox Recovery for LineageOS 22.x or newer on the ASUS Zenfone 8 using the OrangeFox Recovery Builder 2024
   9. Instructions to compile a recovery for LineageOS 21.x or newer running on the ASUS Zenfone 8
      1. How to use TWRP if LineageOS 20.x is installed
      2. How to create a TWRP recovery image for the ASUS Zenfone 8 running a LineageOS 22.x based OS
      3. TWRP images for ASUS Zenfone 8 with /e/
   10. Trouble Shooting Guides for compiling OS image or recoveries
       1. Some hints for repo sync troubleshooting
       2. Some hints for fixing errors building an Custom ROM Android image
   11. Misc
       1. How to re-install the Android OS from ASUS on the ASUS Zenfone 8
       2. ASUS Zenfone 8 Firmware Download
       3. How to boot the ASUS Zenfone 8 into the bootloader using the physical buttons
   12. Links
       1. Files mentioned in the HowTos
       2. Other Android related files
       3. Links for the ASUS Zenfone 8
       4. Distributions for the ASUS Zenfone 8

Introduction

News

History

Instructions to compile the OmniROM for the ASUS Zenfone 8

How to compile the OmniROM for the ASUS Zenfone 8

How to compile the OmniROM 12 for the ASUS Zenfone 8

How to create an OmniROM image with MicroG

How to compile the OmniROM 13 for the ASUS Zenfone 8

How to compile the OmniROM 14 for the ASUS Zenfone 8

Infos for building an Android 14 based Custom ROM image in Q1 2024 or later

Infos for building a Custom ROM image in Q1 2024 or later

---

Notes:

The info below are for building the OmniROM 14 for the ASUS Zenfone 8. But I assume that this is also true for other AOSP based Custom ROMs.
brunch and breakfast are commands defined in the init script for OmniROM and may not be available in other Custom ROMs


Credits

Thanks to the OmniROM developer for this hint.

---

Attempting to create a new OmniROM image based on Android 14 using the well-known parameter for the command lunch in Q1 2024 or later may fail with this error:

[ OmniRom 14 Dev - xtrnaw7@t15g /data/develop/android/OmniROM_14.0 ] $ lunch omni_zenfone8-user

Invalid lunch combo: omni_zenfone8-user
Valid combos must be of the form <product>-<release>-<variant>
[ OmniRom 14 Dev - xtrnaw7@t15g /data/develop/android/OmniROM_14.0 ] $


This is because Google changed the naming conventions for Android releases created with Google's repositories in QPR2 (QPR = Quarterly Platform Releases; QPR2 for Android 14 is the Android Security Patch android-14.0.0_r29 from 05.3.2024) :

It's now necessary to specify a specific version to create a new image using the commands lunch and brunch (see envsetup.sh).

To get the necessary values for the lunch and brunch command check the entries in the file AndroidProducts.mk for your device:

[ OmniRom 14 Dev - xtrnaw7@t15g /data/develop/android/OmniROM_14.0 ] $ cat ./device/asus/zenfone8/AndroidProducts.mk
PRODUCT_MAKEFILES := \
    $(LOCAL_DIR)/omni_zenfone8.mk

COMMON_LUNCH_CHOICES := \
    omni_zenfone8-ap1a-user \
    omni_zenfone8-ap1a-userdebug \
    omni_zenfone8-ap1a-eng

The example above is for a ASUS Zenfone 8; the file used for other phones is most probably in a different directory, of course)


So the commands lunch and brunch to build the OmniROM 14 image for an ASUS Zenfone 8 are now:

lunch omni_zenfone8-ap1a-user

brunch zenfone8 ap1a user


(use the parameter eng or userdebug instead of user for one of the other flavours of the ROM image).

The version string used, ap1a, is part of the build_id for the current security patch level: 




(see here: https://source.android.com/docs/setup/reference/build-numbers#source-code-tags-and-builds)


To check whether an AOSP source tree uses the new version definition, check whether the repository build/release exists, e.g:


[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $ repo info build/release
Manifest branch: refs/tags/android-14.0.0_r29
Manifest merge branch: refs/heads/android-14.0
Manifest groups: default,platform-linux
----------------------------
Project: platform/build/release
Mount path: /devpool001/develop/OmniROM_14.0/build/release
Current revision: b63ef38d4ff1ced7ed8c16733b2b19c8d421aff8
Manifest revision: refs/tags/android-14.0.0_r29
Local Branches: 0
----------------------------
[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $


In an AOSP source tree using the old version definitions the output looks like this:

[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0_patch_2024-02-05 ] $ repo info build/release
Manifest branch: refs/tags/android-14.0.0_r27
Manifest merge branch: refs/heads/android-14.0
Manifest groups: default,platform-linux
----------------------------
error: project build/release not found
[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0_patch_2024-02-05 ] $


I wrote a little script, print_security_patch, to print the current Security Patch level and build id for an AOSP based repository tree.
This script works for repositories that were last updated before Q1 2024 and after Q1 2024.

The script was only tested with the repositories for OmniROM 14 but I think it should work with every AOSP based repository tree.


Usage:

[ OmniRom 14 Dev - xtrnaw7@t15g /data/develop/android/OmniROM_14.0 ] $ /data/develop/android/scripts_on_linux/print_security_patch  -h

print_security_patch - print the security patch and the the build id used in an repository tree for AOSP

This script works for repositories that were last updated before Q1 2024 and after Q1 2024.
The script must be executed at the top level in a repository tree for AOSP

[ OmniRom 14 Dev - xtrnaw7@t15g /data/develop/android/OmniROM_14.0 ] $

Examples

executed in the top level of an Android repository tree using the old definitions

[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0_patch_2024-02-05 ] $  /data/develop/android/scripts_on_linux/print_security_patch ; echo "RC=$?"
The repository uses the old definitions
The current security patch is "2024-02-05"
The current build_id is "UP1A"
RC=1
[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0_patch_2024-02-05 ]


executed in the top level of an Android repository tree using the new definitions

[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $  /data/develop/android/scripts_on_linux/print_security_patch ; echo "RC=$?"
The repository uses the new definitions
The current security patch is "2024-03-05"
The current build_id is "ap1a"
RC=0
[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $


sourced in in the top level of an Android repository tree using the new definitions

[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $ .  /data/develop/android/scripts_on_linux/print_security_patch
The repository uses the new definitions
The current security patch is "2024-03-05"
The current build_id is "ap1a"

[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $ echo $RELEASE_PLATFORM_SECURITY_PATCH
2024-03-05

[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $ echo $BUILD_ID
ap1a

[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $ echo $REPO_FORMAT
new

[ OmniRom 14 Dev - xtrnaw7@t15g /devpool001/develop/OmniROM_14.0 ] $

The script can be downloaded from here: print_security_patch

Update 09.04.2024/bs

There is now a new version of the script available - see How to print the security patch level used in repositories or ROM image zip files for details.


Notes

Note that as of 29.03.2024 the command breakfast does not work anymore in repository trees with the new version definitions.

See How to compile the OmniROM 14 for the the ASUS Zenfone 8 for general instructions how to create your own Custom ROM image with OmniROM 14.

How to compile the OmniROM 15 for the ASUS Zenfone 8

How to compile the OmniROM 16 for the ASUS Zenfone 8

Instructions to compile other Custom ROMs for the ASUS Zenfone 8

How to compile other CustomROMs for the ASUS Zenfone 8

Compiling /e/ for the ASUS Zenfone 8 using the docker image

How to compile LineageOS 22.x for the ASUS Zenfone 8

How to compile /e/ based on Android 15 for the ASUS Zenfone 8

How to compile the official LineageOS 22.2 for the ASUS Zenfone 8

How to compile the crDroid CustomROM for the ASUS Zenfone 8

How to compile the crDroid CustomROM for the ASUS Zenfone 8

crDroid is another LineageOS based CustomROM for Android phones. The ASUS Zenfone 8 is not officially supported by crDroid, but it is not that difficult to compile a crDroid OS image for the ASUS Zenfone 8.

To compile the crDroid 11.x CustomROM for the ASUS Zenfone 8 these commands are necessary:


# create the directory for the repositories with crDroid
#
mkdir /devpool001/develop/crdroid11

cd /devpool001/develop/crdroid11


# init the repository tree
#
repo init -u https://github.com/crdroidandroid/android.git -b 15.0 --git-lfs

# synchronise the repositories
#
repo sync


# Add the necessary repositories for the ASUS Zenfone 8
#

mkdir -p .repo/local_manifests

cat >.repo/local_manifests/roomservice.xml <<EOT
<?xml version="1.0" encoding="UTF-8"?>
<manifest>

  <project path="device/asus/sake"   name="LineageOS/android_device_asus_sake" remote="github" revision="lineage-22.2" />

  <project path="vendor/asus/sake"   name="TheMuppets/proprietary_vendor_asus_sake"  remote="github" revision="lineage-22.2" />

  <project path="kernel/asus/sm8350" name="LineageOS/android_kernel_asus_sm8350" remote="github" revision="lineage-22.2" />

</manifest>
EOT


# sync the repositories for the ASUS Zenfone 8
#
repo sync LineageOS/android_device_asus_sake

repo sync LineageOS/android_kernel_asus_sm8350

repo sync TheMuppets/proprietary_vendor_asus_sake


# correct some files in the repositories
#

# replace "armv8-a" with "armv8-2a"
#
cp device/asus/sake/BoardConfig.mk device/asus/sake/BoardConfig.mk.org
sed  -i -e  "s/armv8-a/armv8-2a/g" device/asus/sake/BoardConfig.mk

# remove duplicate paths
#
if [ ! -r device/asus/sake/sepolicy/vendor/genfs_contexts.org ] ; then
  cp device/asus/sake/sepolicy/vendor/genfs_contexts device/asus/sake/sepolicy/vendor/genfs_contexts.org
  sed -i \
      -e "s|^genfscon sysfs /devices/platform/soc/17300000.qcom,lpass/wakeup|# genfscon sysfs /devices/platform/soc/17300000.qcom,lpass/wakeup|g" \
      -e "s|^enfscon sysfs /devices/platform/soc/188101c.qcom,spss/wakeup|# enfscon sysfs /devices/platform/soc/188101c.qcom,spss/wakeup|g" \
      -e "s|^enfscon sysfs /devices/platform/soc/5c00000.qcom,ssc/wakeup|# enfscon sysfs /devices/platform/soc/5c00000.qcom,ssc/wakeup |g" \
      device/asus/sake/sepolicy/vendor/genfs_contexts
fi

# init the environment
#
source build/envsetup.sh

# prepare the environment
#
lunch lineage_sake-bp1a-user

# start the build
#
brunch lineage_sake-bp1a-user


Check the result

xtrnaw7@t540p:/devpool001/develop/crdroid11$ ls -ltr out/target/product/sake/*zip
-rw-r--r--. 1 xtrnaw7 xtrnaw7 1334328430 Aug  3 12:20 out/target/product/sake/crDroidAndroid-15.0-20250803-sake-v11.7.zip
xtrnaw7@t540p:/devpool001/develop/crdroud11$




I have successfully installed the image on an ASUS Zenfone 8:





Notes

To get the build_id for the lunch and brunch command, bp1a in the examples above, use the script print_security_patch, e.g.:

xtrnaw7@t540p:/devpool001/develop/crdroid11$ print_security_patch
Retrieving the security patch level for the repository at "/devpool001/develop/crdroid11" ...
The repository uses the new definitions
The current security patch is "2025-05-05"
The current build_id is "bp1a"
xtrnaw7@t540p:/devpool001/develop/crdroid11


I have done some basic tests but I have not thoroughly tested the crDroid image for the ASUS Zenfone 8 - this is more or less just a proof of concept and an example of creating a LineageOS based CustomROM for a phone that is supported by the LineageOS but, not the by LineageOS based CustomROM.


see the section How to compile the OmniROM for the ASUS Zenfone 8 for HowTos to compile the OmniROM for the ASUS Zenfone 8.

see the section How to compile other CustomROMs for the ASUS Zenfone 8 for a list of sections with instructions to compile other custom ROMs for the ASUS Zenfone 8 (e.g. LineageOS 22.x, /e/, crDroid, evolutionX, etc)
The entry also contains a list of sections with instructions to create TWRP or OrangeFox recovery images for the various custom ROMs.


see How to compile the evolutionX Custom ROM for the ASUS Zenfone 8 with kernelSU for instructions to add KernelSU-Next to the OS image (the instructions in that HowTo also work for the crDorid ROM)

see How to create a OrangeFox Recovery for LineageOS 22.x or newer on the ASUS Zenfone 8 using the OrangeFox Recovery Builder 2024 for instructions to create an OrangeFox recovery for LineageOS based CustomROMs for the ASUS Zenfone 8 using the OrangeFox Recovery Builder on github.com.

How to compile the evolutionX Custom ROM for the ASUS Zenfone 8

How to compile the evolutionX Custom ROM for the ASUS Zenfone 8

evolutionX is another LineageOS based CustomROM for Android phones. The ASUS Zenfone 8 is not officially supported by evolutionX, but it is not that difficult to compile a evolutionX OS image for the ASUS Zenfone 8.

To compile the evolutionX CustomROM for the ASUS Zenfone 8 these commands are necessary (see also the evolutionX wiki):


# create the directory for the repositories for evolutionX
#
mkdir /devpool001/develop/evolutionX

cd /devpool001/develop/evolutionX


# init the repositories for evolutionX  (vic = Android 15)
#
repo init -u https://github.com/Evolution-X/manifest -b vic --git-lfs


# create the manifest file with the repositories for the ASUS Zenfone 8
#
mkdir -p .repo/local_manifests

cat >.repo/local_manifests/asus_sake.xml <<EOT
<?xml version="1.0" encoding="UTF-8"?>
<manifest>

  <project path="device/asus/sake"   name="LineageOS/android_device_asus_sake" remote="github" revision="lineage-22.2" />

  <project path="vendor/asus/sake"   name="TheMuppets/proprietary_vendor_asus_sake"  remote="github"/>

  <project path="kernel/asus/sm8350" name="LineageOS/android_kernel_asus_sm8350" remote="github" revision="lineage-22.2" />

</manifest>
EOT


# synchronize the repositories
#
repo sync -c -j4 --force-sync --no-clone-bundle --no-tags


# prepare the build environment
#
lunch lineage_sake-bp1a-userdebug


# start the build
#
m evolution


Check the result

[xtrnaw7@t540p evolutionX]$ ls -l out/target/product/sake/EvolutionX-*zip
-rw-r--r--. 1 xtrnaw7 xtrnaw7 2362271330 Aug  5 06:59 out/target/product/sake/EvolutionX-15.0-20250804-sake-10.7-Unofficial.zip
[xtrnaw7@t540p evolutionX]



I have successfully installed the image on an ASUS Zenfone 8:




ASUS_I006D:/ $ getprop | egrep -i "evol|fingerprint"
[persist.sys.pihooks_FINGERPRINT]: [google/panther_beta/panther:16/BP31.250523.010/13667654:user/release-keys]
[ro.bootimage.build.fingerprint]: [asus/twrp_I006D/I006D:99.87.36/SP2A.220405.004/xtrnaw707262051:eng/test-keys]
[ro.build.fingerprint]: [asus/WW_I006D/ASUS_I006D:13/TKQ1.220807.001/33.0210.0210.332:user/release-keys]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.evolution.build.version]: [EvolutionX-15.0-20250804-sake-10.7-Unofficial]
[ro.evolution.device]: [sake]
[ro.evolution.display.version]: [v10.7-20250804]
[ro.evolution.version]: [15.0]
[ro.evolutionlegal.url]: [https://evolution-x.org/legal.php]
[ro.hardware.fingerprint]: [goodixfp]
[ro.odm.build.fingerprint]: [asus/WW_I006D/ASUS_I006D:13/TKQ1.220807.001/33.0210.0210.332:user/release-keys]
[ro.product.build.fingerprint]: [asus/WW_I006D/ASUS_I006D:13/TKQ1.220807.001/33.0210.0210.332:user/release-keys]
[ro.system.build.fingerprint]: [asus/WW_I006D/ASUS_I006D:13/TKQ1.220807.001/33.0210.0210.332:user/release-keys]
[ro.system_ext.build.fingerprint]: [asus/WW_I006D/ASUS_I006D:13/TKQ1.220807.001/33.0210.0210.332:user/release-keys]
[ro.vendor.build.fingerprint]: [asus/WW_I006D/ASUS_I006D:13/TKQ1.220807.001/33.0210.0210.332:user/release-keys]
[ro.vendor_dlkm.build.fingerprint]: [asus/WW_I006D/ASUS_I006D:13/TKQ1.220807.001/33.0210.0210.332:user/release-keys]
ASUS_I006D:/ $



Notes

see the Evolution WIki for the supported build flags. To use a build flag, simply export the flag as environment variable before starting the build, e.g

to disable GAPPS use

export WITH_GMS=false


Note that I do not know why the security patch in the EvolutionX GUI on the phone is 1. July 2025. Google did not release a new patchset in July 2025. The patchset info in the source code is:

xtrnaw7@t540p:/devpool001/develop/evolutionX$ print_security_patch
Retrieving the security patch level for the repository at "/devpool001/develop/evolutionX" ...
The repository uses the new definitions
The current security patch is "2025-05-05"
The current build_id is "bp1a"
xtrnaw7@t540p:/devpool001/develop/evolutionX$


Note that the script print_security_patch also prints the build_id that must be used in the parameter for the lunch and brunch commands ( bp1a in this example)


I have done some basic tests but I have not thoroughly tested the evolutionX image for the ASUS Zenfone 8 - this is more or less just a proof of concept and an example of creating a LineageOS based CustomROM for a phone that is supported by the LineageOS but, not the by LineageOS based CustomROM.


see the section How to compile the OmniROM for the ASUS Zenfone 8 for HowTos to compile the OmniROM for the ASUS Zenfone 8.

see the section How to compile other CustomROMs for the ASUS Zenfone 8 for a list of HowTos with instructions to compile other custom ROMs for the ASUS Zenfone 8 (e.g. LineageOS 22.x, /e/, crDroid, evolutionX, etc)
The entry also contains a list of sections with instructions to create TWRP or OrangeFox recovery images for the various custom ROMs.


Note that the OS image for the ASUS Zenfone 8 created with these instructions does not contain KernelSU.

see How to compile the evolutionX Custom ROM for the ASUS Zenfone 8 with kernelSU for instructions to add KernelSU-Next to the OS image.

see How to create a OrangeFox Recovery for LineageOS 22.x or newer on the ASUS Zenfone 8 using the OrangeFox Recovery Builder 2024 for instructions to create an OrangeFox recovery for LineageOS based CustomROMs for the ASUS Zenfone 8 using the OrangeFox Recovery Builder on github.com.
 

How to compile the evolutionX Custom ROM for the ASUS Zenfone 8 with kernelSU

How to compile the evolutionX Custom ROM for the ASUS Zenfone 8 with kernelSU

The section How_to_compile_the_evolutionX_Custom_ROM_for_the_ASUS_Zenfone_8 contains the instructions to compile the evolutionX custom ROM for the ASUS Zenfone 8.
The OS image created with these instructions does not contain kernelSU, unlike the official builds for evolutionX for other phones.


To compile the evolutionX for the ASUS Zenfone 8 with kernelSU, these instructions can be used:


The repositories for kernelSU can not be used to add kernelSU to the evolutionX image for the ASUS Zenfone 8 because the current kernelSU sources no longer support the kernel version used on this phone.

Therefore, Instead of the original kernelSU source, we use the source for KernelSU-Next: KernelSU-Next supports the old kernel versions out of the box.

To add KernelSU-Next to the OS image, change the working directory to the top directory with the repositories for evolutionX and then execute these commands (see also https://kernelsu-next.github.io/webpage/pages/installation.html)

(These commands only need to be executed once to add the KernelSU-Next repository to the repositories for evolutionX)


# change the current working directory to the kernel source directory
#
cd ./kernel/asus/sm8350

# retrieve the setup script for KernelSU-Next and execute it (the script installs and configures the KernelSU-Next repository)
#
curl -LSs "https://raw.githubusercontent.com/KernelSU-Next/KernelSU-Next/next/kernel/setup.sh" | bash -


# add the necessary compile flag for KernelSU-Next to the Makefile
#
cp drivers/kernelsu/Makefile  drivers/kernelsu/Makefile.org

( echo "ccflags-y += -DKSU_NEXT" ; cat drivers/kernelsu/Makefile.org ) >drivers/kernelsu/Makefile


The build the image for the boot partition:

# init the build environment (if not already done)
#
source build/envsetup.sh


# create the boot image
#
mka clobber; mka bootimage



If the build of the boot image is successfull, the boot image is in the file

out/target/product/sake/boot.img


To test the boot image (assuming evolutionX is currently installed on the phone):

adb reboot bootloader ;  fastboot boot out/target/product/sake/boot.img


This command boots the phone from the just created boot partition image into the OS installed on the phone.


To check if KernelSU-Next is working, download and install the KernelSU-Next app from https://github.com/KernelSU-Next/KernelSU-Next/releases/:

KERNELSU_NEXT_APK="KernelSU_Next_v1.0.9_12797-release.apk"

# download the apk to the PC
#
wget -O "${KERNELSU_NEXT_APK}"  "https://github.com/KernelSU-Next/KernelSU-Next/releases/download/v1.0.9/${KERNELSU_NEXT_APK}"

# install the apk on the phone using "adb shell" on the PC (or copy the apk to the phone and install it using the Android GUI)
#
cat "${KERNELSU_NEXT_APK}" | adb shell pm install -S echo $( stat -c "%s"  "${KERNELSU_NEXT_APK}" )


If everything is okay, the app should look like this:




Now simply create a new OS image with KernelSU-Next using the standard build commands:

# init the environment (if not already done)
#
source build/envsetup.sh

lunch lineage_sake-bp1a-userdebug

m evolution


Notes

To build an OS image without KernelSU-Next, delete the line

ccflags-y += -DKSU_NEXT

in the file

./kernel/asus/sm8350/drivers/kernelsu/Makefile

and recreate the image.

Please note that the environment variables in the session where the build is started are not inherited by the process executing make to compile the kernel.


To change the name of the ZIP file with the OS image for builds with enabled KernelSU-Next add the lines

ifeq ($(WITH_KSU_NEXT),true)
EVO_VERSION := ${EVO_VERSION}-ksu
endif

to the file

./vendor/lineage/config/version.mk

before the line starting with

LINEAGE_VERSION :=

and define the environment variable

WITH_KSU_NEXT=true

before starting the build (The string -ksu can be replaced with any other string).



The boot.img file created for the evolutionX Custom ROM can also be used to add KernelSU-Next to other ROMs for the ASUS Zenfone 8 based on LineageOS 22.2 that are using the same kernel sources (like crDroid 11.7)

As of 09.08.2025 the current version of the KernelSU-Next app is 1.0.9 - it's recommended to check https://github.com/KernelSU-Next/KernelSU-Next/releases/ for a newer version of the apk (use the link "Show all n assets" on that page to see the apks)

There is no pre-compiled kernelSU image for the kernel used in the evolutionX Custom ROM (kernelSU only supplies precompiled kernels for Linux Kernel 5.10 or newer).

To create a kernel without kernelSU, delete the line

ccflags-y += -DKSU_NEXT

in the file drivers/kernelsu/Makefile and recreate the kernel


TroubleShooting

To stop or start the KernelSU-Next app in a shell, these commands can be use:

# stop the KernelSU-Next app
#
am force-stop com.rifsxd.ksunext

# start the KernelSU-Next app
#
am start -n com.rifsxd.ksunext/.ui.MainActivity


If KernelSU-Next is not working at all or not working as expected you can enable kernel debug messages:

To compile the kernel with debug code add the statements

CONFIG_DYNAMIC_DEBUG=y
CONFIG_DEBUG_KERNEL=y
CONFIG_KSU_DEBUG=y


to the kernel config file and recompile the kernel. In the source for the ASUS Zenfone 8 the file with the kernel config is:

/devpool001/develop/OmniROM_16.0/kernel/asus/sm8350/arch/arm64/configs/vendor/zf8_defconfig

The final kernel config used to compile the kernel is in the file:

/devpool001/develop/OmniROM_16.0/out/target/product/zenfone8/obj/KERNEL_OBJ/.config


If the kernel was built with the options

CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y

the config is available while the kernel is booted:

cat /proc/config.gz | gzip -d > kernel.config


To enable the filesystem

/sys/kernel/debug

add the option

CONFIG_DEBUG_FS=y

to the kernel config.

Note that in my tests the kernel from the OmniROM 16 for the ASUS Zenfone 8 did not boot a kernel compiled with this setting


----

How to compile LMODroid 6.x for the ASUS Zenfone 8

How to compile the iodeOS 4.x for the ASUS Zenfone 8

How to compile the iodeOS 6.x for the ASUS Zenfone 8