What You'll Need: A Working 🧠, PC/RDP with any Linux GUI distro, Knowledge of basic commands in Linux, Understanding of English.

• If you're feeling a bit lazy to install a Linux distro, you can also use Gitpod. Keep in mind, though, it might be more challenging.

sudo apt update -y
sudo apt install default-jdk git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev x11proto-core-dev libx11-dev libreadline6-dev libgl1-mesa-glx libgl1-mesa-dev python3 make sudo gcc g++ bc grep tofrodos python3-markdown libxml2-utils xsltproc zlib1g-dev libncurses5 python-is-python3 libc6-dev libtinfo5 ncurses-dev make python2 repo cpio kmod openssl -y

❗The video Guide for this tutorial can be found here : Open in YouTube

1. ✅ Downloading Part. (Only for samsung)
2. ✅ Compiling Part (Universal for any device).
3. ✅ (❗ Samsung Specific) How to disable kernel securities from the menuconfig..?
4. ✅ How to make your kernel supports with APatch..?
5. ✅ Compilation Process.
6. ✅ (FINAL) How to put the compiled kernel, inside our boot.img..?

tar xvf Kernel.tar.gz; rm Kernel.tar.gz

• Problem :
  
• Solution :
  

• ⚠️ For other devices, You can find them by your OEM's sites or from your OEM's official GitHub repos.

• Before making a build script, we must download compilers to build the kernel.
• if you own a Snapdragon/Mediatek device, I recommend you to use Google's Compilers.
• You can clone them using this command : (❗only for every Snapdragon/Mediatek devices from any OEM)

cd ~
git clone https://github.com/ravindu644/Toolchains_by_Google.git

• Or, If you prefer Qualcomm's own compilers rather than Google's, you can clone them using this command :

cd ~
git clone https://github.com/ravindu644/Toolchains_for_Snapdragon.git

• Or, If you prefer Proton clang to compile the kernel (Qualcomm and Mediatek), Jump to this Guide : Click here

Notes : (Samsung exynos specific) If your device is exynos, Open the "README_Kernel.txt" and download the toolchains by Googling the values for "CC" and "CROSS_COMPILE". You can find them easily from the Google Opensource or github.

• For an Example :
  
  

• Now, Open the terminal from your Kernel source's folder and create a new file called build.sh using this command :

touch build.sh

• Open the newly created build.sh and make that file looks like this : (⚠️ This code is only for Snapdragon and Mediatek devices and not for Exynos)
• The reason for that is, Snapdragon and Mediatek kernel sources only supported to compile to a seperated directory called "out".
• Here's the code : ⬇️

#!/bin/bash
clear
export ARCH=arm64
export PLATFORM_VERSION=13
export ANDROID_MAJOR_VERSION=t
ln -s /usr/bin/python2.7 $HOME/python
export PATH=$HOME/:$PATH
mkdir out

ARGS='
CC=$HOME/Toolchains_for_Snapdragon/llvm-arm-toolchain-ship-10.0/bin/clang
CROSS_COMPILE=$HOME/Toolchains_for_Snapdragon/aarch64-linux-android-4.9/bin/aarch64-linux-android-
CLANG_TRIPLE=aarch64-linux-gnu-
ARCH=arm64
'
make -C $(pwd) O=$(pwd)/out ${ARGS} clean && make -C $(pwd) O=$(pwd)/out ${ARGS} mrproper #to clean the source
make -C $(pwd) O=$(pwd)/out ${ARGS} a52q_eur_open_defconfig #making your current kernel config
make -C $(pwd) O=$(pwd)/out ${ARGS} menuconfig #editing the kernel config via gui
make -C $(pwd) O=$(pwd)/out ${ARGS} -j16 #to compile the kernel

• ❗If your Device is Samsung Exynos, It does't supports the compiling kernel in a separate directory. So, the code must be like this :

#!/bin/bash
clear
export ARCH=arm64
export PLATFORM_VERSION=13
export ANDROID_MAJOR_VERSION=t
ln -s /usr/bin/python2.7 $HOME/python
export PATH=$HOME/:$PATH

ARGS='
CC=$HOME/path/to/clang/bin/clang
CROSS_COMPILE=$HOME/path/to/gcc/bin/aarch64-linux-android-
CLANG_TRIPLE=aarch64-linux-gnu-
ARCH=arm64
'

make ${ARGS} clean && make ${ARGS} mrproper #to clean the source
make ${ARGS} YOUR_DEFCONFIG #making your current kernel config
make ${ARGS} menuconfig #editing the kernel config via gui
make ${ARGS} -j16 #to compile the kernel

• Edit the PLATFORM_VERSION value to your Android version.
• Edit the ANDROID_MAJOR_VERSION value to your Android version's codename.
• Edit CC value with the path to the clang's [bin folder]/clang.
• Edit CROSS_COMPILE value with the path to the GCC's [bin folder]/aarch64-linux-android-
• Replace YOUR_DEFCONFIG to your current defconfig which is located in arch/arm64/configs.

• if you found these variables : CROSS_COMPILE, REAL_CC or CC, CFP_CC in your "makefile" ; remove them from the "Makefile"
• search "wrapper" in your makefile. If there's a line related to a python file, remove that entire line/function too.
• Search CONFIG_CC_STACKPROTECTOR_STRONG and replace it with CONFIG_CC_STACKPROTECTOR_NONE

• To fix the "symbol versioning failure for gsi_write_channel_scratch" error : Click here
• Also, you will faced an error called scripts/gcc-version.sh: line 25: aarch64-linux-gnu-gcc: command not found if you used the Google's compilers, You can fix them too using this commit : Click here
• To force load the vendor modules in some devices (Universal) ⚠️ (This fixes various hardware related issues after installing a custom kernel) - Click here

chmod +x build.sh

./build.sh

• Additional notes : Press space bar to enable/disable or enable as a module .

• Image :
  
  

• Image :
  
  

• If you can't find them (01 and 02) in the "→ Kernel Features", they are located in the "→ Boot options".

• Image :
  
  
• As I mentioned at the beginning of this guide, your must use your brain..! 🧠

• Image :
  
  

• Image :
  
  

• Image :
  
  

• Image :
  
  

• Image :
  
  
  
  ❗Additional Notes : To force load the vendor/system modules in some devices, use this commit (⚠️ This fixes various hardware related issues after installing a custom kernel) - Click here

• Image :
  
  

• Image :
  
  

• When you see "configuration written", stop the compilation process with Ctrl+C and replace the content of ".config" with your desired defconfig.

• ℹ️ The compiled kernel will be located at arch/arm64/boot.

• If you encounter errors during the compilation process, it's advisable to search for these errors on GitHub and find a solution.

- Use exact build number to download the firmware.

• Image :
  
  

  ---

• Kernel without GZIP compression :
  
  
• Kernel with GZIP compression :
  
  
  
  

• If your split_img has a boot.img-dtb + Uncompressed Kernel => Use "Image".
• If your split_img has a boot.img-dtb + GZIP compressed Kernel => Use "Image.gz".
• If your split_img don't has a boot.img-dtb + uncompressed Kernel => Use "Image.gz-dtb".
• If your split_img don't has a boot.img-dtb + GZIP compressed Kernel => Use "Image.gz-dtb.gz".

tar cvf "DEVICE NAME (APatch Support).tar" boot.img

• Proof :