[GUIDE]A Noob Guide On Building Your Own Custom Kernel (ARM & ARM64 & MTK)

What does the thread need ?


  • Total voters
    41
  • Poll closed .
Search This thread

HatchetEgg

Senior Member
Jul 9, 2012
422
87
48
Redmi Note 8
Yes. All these commands should work on any 64 bit Linux distros including Linux Mint (well, at-least on all debian based distros. In Redhat based distros, some commands under the section " SETTING UP YOUR BUILD ENVIRONMENT" will be different.
In my opinion, this is one of the best guide for beginners. Thanks to @3lambda. Btw, to the best of my knowledge, commands like, makeconfig, menuconfig, xconfig etc. are not required (especially for the beginners) as long as you have a proper defonfig for your device (correct me if I'm wrong?).

I actually been using your kernel on my S5, would you know where I can find the latest kernel sources for the g900f? I looked on the official site for samsung, but there's nothing later than marshmallow.
 
  • Like
Reactions: sunilpaulmathew

sunilpaulmathew

Recognized Developer
Nov 7, 2015
1,824
5,559
153
Kochi (Currently in Prague)
smartpack.github.io
I actually been using your kernel on my S5, would you know where I can find the latest kernel sources for the g900f? I looked on the official site for samsung, but there's nothing later than marshmallow.
Hi...
In the official site (sammobile), you won't find anything later than marshmallow, since Samsung never released a nougat update for klte. The one and only up-to-date nougat kernel source available for klte is the one maintained by LineageOS team. All others including my source are based on LOS source. If you need, feel free to take my source. It also contains all the commits from lineage OS source. Btw, nice to know that ur using my kernel.
 
Last edited:

HatchetEgg

Senior Member
Jul 9, 2012
422
87
48
Redmi Note 8
Hi...
In the official site (sammobile), you won't find anything later than marshmallow, since Samsung never released a nougat update for klte. The one and only up-to-date nougat kernel source available for klte is the one maintained by LineageOS team. All others including my source are based on LOS source. If you need, feel free to take my source. It also contains all the commits from lineage OS source. Btw, nice to know that ur using my kernel.

Thanks I consider using your sources, once I'm out of the newbie stage, maybe if you need any help or support with yours. I would be willing to help.
 
  • Like
Reactions: sunilpaulmathew

ergo911

Senior Member
Feb 5, 2009
210
99
0
Hi, what do I have to setup differently for mediatek arm64? It's a mt6735.

Edit: silly question - if andutu shows android 5.1 32bit but cpu is 64bit, is the kernel also 32bit then?:silly:

Thanks, great tutorial ?
 
Last edited:

lzzy12

Senior Member
Mar 21, 2017
202
338
0
Hi, what do I have to setup differently for mediatek arm64? It's a mt6735.

Edit: silly question - if andutu shows android 5.1 32bit but cpu is 64bit, is the kernel also 32bit then?:silly:

Thanks, great tutorial

Well, according to me to know, if the kernel is 64 or 32 bit is to see where is the _defconfig file is located.. If it is in arch/arm64/configs, then it is 64 and if it is in arch/arm/configs then 32bit
 
  • Like
Reactions: ergo911

sunilpaulmathew

Recognized Developer
Nov 7, 2015
1,824
5,559
153
Kochi (Currently in Prague)
smartpack.github.io
I was wondering were is the next place to go to improve my kernel building skills?

If you already expertise in building, I recommend you to do....
1. clone the source of your current ROM kernel (or any other up-to-date custom kernel source for your ROM)
2. cherry-pick (or manually add: I recommend this in the beginning so that you can understand what is really happening) some features (like a cpufreq govs, or something else)
3. build
4. Flash and test on the top of your ROM
5. and repeat :p

don't hesitate to cherry-pick the codes from other devs repos (ofc, with proper credits)
and if it is worth testing, don't forget to share with other members and publish the source... ;)
(once you share a kernel to the community, we, the proud xda folks will give you many opportunities to become better by asking feature requests) :p

This is what I did in the beginning and, so, my recommendations to all the beginners.
 
Last edited:
  • Like
Reactions: psxda97

ergo911

Senior Member
Feb 5, 2009
210
99
0
Well, according to me to know, if the kernel is 64 or 32 bit is to see where is the _defconfig file is located.. If it is in arch/arm64/configs, then it is 64 and if it is in arch/arm/configs then 32bit
Yeah, the right deconfig is in arm64 directory.
 

psxda97

Senior Member
Nov 1, 2015
206
71
0
If you already expertise in building, I recommend you to do....
1. clone the source of your current ROM kernel (or any other up-to-date custom kernel source for your ROM)
2. cherry-pick (or manually add: I recommend this in the beginning so that you can understand what is really happening) some features (like a cpufreq govs, or something else)
3. build
4. Flash and test on the top of your ROM
5. and repeat :p

don't hesitate to cherry-pick the codes from other devs repos (ofc, with proper credits)
and if it is worth testing, don't forget to share with other members and publish the source... ;)
(once you share a kernel to the community, we, the proud xda folks will give you many opportunities to become better by asking feature requests) :p

This is what I did in the beginning and, so, my recommendations to all the beginners.

That was one hell of an advice :)
 

HatchetEgg

Senior Member
Jul 9, 2012
422
87
48
Redmi Note 8
@3lambda

Hello,

I noticed an error in the guide under section 4 on line "When these step are done make sure you are in kernel folder in terminal and type ". build.sh" (the dot at the beginning is essential don't forget it!)"

For me entering the command .build.sh in terminal did not work. However I added ./build.sh and it executed the shell commands within the file correctly.
 

sunilpaulmathew

Recognized Developer
Nov 7, 2015
1,824
5,559
153
Kochi (Currently in Prague)
smartpack.github.io
There is a "space" between the "." and build.sh. The proper command is ". build.sh", not ".build.sh". and yes, "./build.sh" also do the job...
(not only the "dot", the in-between "space" is also very important) :p
@3lambda

Hello,

I noticed an error in the guide under section 4 on line "When these step are done make sure you are in kernel folder in terminal and type ". build.sh" (the dot at the beginning is essential don't forget it!)"

For me entering the command .build.sh in terminal did not work. However I added ./build.sh and it executed the shell commands within the file correctly.
 
Last edited:

3lambda

Recognized Contributor
Dec 6, 2012
1,755
1,458
133
Clermont-Ferrand
Xiaomi Mi 8
@3lambda

Hello,

I noticed an error in the guide under section 4 on line "When these step are done make sure you are in kernel folder in terminal and type ". build.sh" (the dot at the beginning is essential don't forget it!)"

For me entering the command .build.sh in terminal did not work. However I added ./build.sh and it executed the shell commands within the file correctly.

What's your kernel name folder ?
Because if the kernel folder you work on is named msm8890 for exemple in terminal you should be in "msm8890" and command ". build.sh" will work

But both yours and mine method work tho ;)
 

HatchetEgg

Senior Member
Jul 9, 2012
422
87
48
Redmi Note 8
What's your kernel name folder ?
Because if the kernel folder you work on is named msm8890 for exemple in terminal you should be in "msm8890" and command ". build.sh" will work

But both yours and mine method work tho ;)

Ah OK that is interesting, well I was using the command within the Kernel folder, since that is where build.sh was located. Well for my kernel sources anyway.

I have managed to build a kernel, but I'm researching on how you configure anykernel, to set it up so I can make a flashable zip.

Since Sunilpaulmathew kindly let me use his sources, I'm looking into the scripts to see if I can figure it out.
 
Last edited:

3lambda

Recognized Contributor
Dec 6, 2012
1,755
1,458
133
Clermont-Ferrand
Xiaomi Mi 8
Ah OK that is interesting, well I was using the command within the Kernel folder, since that is where build.sh was located. Well for my kernel sources anyway.

I have managed to build a kernel, but I'm researching on how you configure anykernel, to set it up so I can make a flashable zip.

Go in @0smosis thread for anykernel or look a already made any kernel zip for inspiration :)

Envoyé de mon HTC M8w en utilisant Tapatalk
 

noob4598

Senior Member
Jun 26, 2015
670
316
0
35
Timmonsville
What's your kernel name folder ?
Because if the kernel folder you work on is named msm8890 for exemple in terminal you should be in "msm8890" and command ". build.sh" will work

But both yours and mine method work tho ;)
Sometimes I have trouble with the . and / commands executing bash scripts so I got in the habit of executing with "bash". The trouble probably comes from trying to build a kernel using Ubuntu 16.04 for armv7l on my Samsung Galaxy Note 4. Haven't quite figured out how, or if it's even possible, to cross compile using the target as host build system. Also, I think Samsung may have left out some drivers or something......anyway, if anyone has any advice or knowledge that would be greatly appreciated. This is a great guide btw.....by far the most noob friendly. Thank you @3lambda
 

3lambda

Recognized Contributor
Dec 6, 2012
1,755
1,458
133
Clermont-Ferrand
Xiaomi Mi 8
Sometimes I have trouble with the . and / commands executing bash scripts so I got in the habit of executing with "bash". The trouble probably comes from trying to build a kernel using Ubuntu 16.04 for armv7l on my Samsung Galaxy Note 4. Haven't quite figured out how, or if it's even possible, to cross compile using the target as host build system. Also, I think Samsung may have left out some drivers or something......anyway, if anyone has any advice or knowledge that would be greatly appreciated. This is a great guide btw.....by far the most noob friendly. Thank you @3lambda

I didn't understood all your problem etc
Anyway send me a pm I'll try to help you
 

sunilpaulmathew

Recognized Developer
Nov 7, 2015
1,824
5,559
153
Kochi (Currently in Prague)
smartpack.github.io
Ah OK that is interesting, well I was using the command within the Kernel folder, since that is where build.sh was located. Well for my kernel sources anyway.

I have managed to build a kernel, but I'm researching on how you configure anykernel, to set it up so I can make a flashable zip.

Since Sunilpaulmathew kindly let me use his sources, I'm looking into the scripts to see if I can figure it out.

You can add any basic terminal commands (such as copy: cp, move/rename: mv; remove: rm etc) to the shell script. Although my build script seems bit complicated (since I'm building for 5 variants using the same script), it basically do the following things...
1. Export ARCH and Toolchain
2. creating the output folders (mkdir output_xxx)
3. Building zImage (make -C $(pwd) O=output_xxx msm8974_sec_defconfig VARIANT_DEFCONFIG=msm8974pro_sec_klte_xxx_defconfig SELINUX_DEFCONFIG=selinux_defconfig && make -C $(pwd) O=output_xxx)
4. Copying zImage into the anykernel directory (cp output/arch/arm/zImage anykernel_xxx/)
5. Making anykernel flashable zip (cd anykernel_xxx/ && zip -r9 Kernel_name.zip *)

Btw, feel free to pm me for any further assistance. I'm happy to help anyone...
 
  • Like
Reactions: 3lambda

SubwayChamp

Senior Member
Aug 6, 2016
2,552
1
1,154
173
I have a kernel v. 3.10.72 still lollipop, I ported some roms (5.1) for my device but I can´t upgrade to MM cause there is not or I don´t find a kernel source for this model Alcatel OT 5022E (mt6580), Is this the end of the way or is there some method to upgrade? Thanks in advance
 

lzzy12

Senior Member
Mar 21, 2017
202
338
0
I have a kernel v. 3.10.72 still lollipop, I ported some roms (5.1) for my device but I can´t upgrade to MM cause there is not or I don´t find a kernel source for this model Alcatel OT 5022E (mt6580), Is this the end of the way or is there some method to upgrade? Thanks in advance
U mean, u have the kernel sources??
 

Top Liked Posts

  • There are no posts matching your filters.
  • 85
    1. INTRODUCTION:​

    This is a guide to build your own custom kernel. Although I'm still a "noob" at this,
    I've struggled a lot to build one as all the guides which I followed were not very clear.
    So I hope this will be clear enough and as noob friendly as possible!

    You will learn how to:

    - Build a kernel for arm and mediatek devices (arm64 coming soon)
    - Add feature
    - Basic use of git

    Requirements:

    - A computer running any distribution of linux 64 bit (Unbuntu, archlinux etc) as the Primary OS or a Virtual Machine (I used BBQ linux x64)
    - Space on your HDD (On my Virtual Machine I set 40GB, set yours according to how many kernels you want to build) The minimum space for a kernel source (and its compiled code) is about 2 GB
    - Minimal linux knowledge (Terminal, Commands etc)
    - Your Brain
    - And finally patience

    2. SETTING UP YOUR BUILD ENVIRONMENT:​

    - Open your terminal and type "sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2"

    (The command can be different depending upon your linux distribution)

    - Then type "gcc"

    If "gcc" is already installed, you should see "gcc : fatal error : no input file"

    - Then type "make"

    If "make" is already installed, you should see "make: *** no target specified and no makefile found. stop."
    (In your native language)

    - Then type "git"

    If "git" is already installed, you should see bunch of basic git commands

    Now you're almost ready to start building your kernel!

    Toolchains:

    There are several types of toolchains (GCC, Linaro and few custom made ones)
    Warning : Not every single device kernel will boot (or even compiles) with older or newer GCC

    - For ARM:

    We'll be using GCC 4.7 in this tutorial (link : https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/ )

    -Open terminal and type: "mkdir kernel"(Type the name you want, I used "kernel")

    -Then type "cd kernel" (the name which you used above)

    -Then type "git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7"

    -Wait till it finishes.


    - For ARM 64:

    For ARM 64 you need a 64 bit kernel compiler (there's "aarch64" in the name for telling that's a 64 bit compiler)

    Exemple : https://releases.linaro.org/archive/13.07/components/toolchain/binaries/gcc-linaro-aarch64-linux-gnu-4.8-2013.07-1_linux.tar.xz


    3.DOWNLOADING SOURCE FILES FOR YOUR DEVICE:​

    Now you have to find a github that contains your kernel source.
    Search on Google or XDA to find a kernel github repo for your device.

    A kernel github looks like this: "https://github.com/atxoxx/android_kernel_samsung_msm8974/tree/xenomTW"

    On the upper left side you can see branch: completed by a name
    These are the different versions of the kernel/project (generally can be for testing, android version etc)

    QUICK EXPLANATION OF FILES/FOLDERS:

    - /arch/arm/configs : contains the config files for device (where you add option like new governors, features etc)
    - /output/arch/arm/boot/ : Where zimage is stored (will explain that later)
    - build.sh : Script to make the building much easier (will explain how it works later)
    - /arm-cortex-linux-gnueabi-linaro_5.2-2015.11-2 : I put the toolchain in my kernel source making it easier to find (your kernel's toolchain name may be different)

    If you don't have your kernel source yet, you need to download it.

    Open terminal and make sure that you are in "kernel" folder (the one you previously created)

    Then type in terminal : "git clone "URL of the github kernel" -b "name of the branch" "

    For Example : "git clone https://github.com/atxoxx/android_kernel_samsung_msm8974 -b xenomTW"

    Good! Now you have your kernel source!

    4.BUILDING:​

    For an easier way you can go to the location using your file explorer to : "/home/"name of your session"/kernel"

    You'll see two folders (The Toolchain and The Kernel Source)

    Go into your kernel source folder.

    - For ARM:

    Copy paste this:

    #!/bin/bash

    export ARCH=arm
    export CROSS_COMPILE="path to your toolchain" (it have to end by something like "nameofarch-something-")

    mkdir output

    make -C $(pwd) O=output "name of defconfig and variant if needed"
    make -j4 -C $(pwd) O=output

    Explaination:

    - #!/bin/bash: Tells the script to run in shell command
    - export ARCH=arm: Defining which kernel architecture type it is (For example arm64 etc)
    - export CROSS_COMPILE= : Locate where the toolchain is, it has to match the exact path to it and the dash ("-") in the end is really important ! (Almost everyone makes an error at this part!!!)
    - mkdir output: Create a directory for storing compiled zimage
    - make -C $(pwd) O=output : Defining defconfig for guiding kernel compilation (will explain later)
    - make -j4 -C $(pwd) O=output: where the building start, "-j4" is how fast it'll compile, you have to setup this number according to your CPU !
    - cp output/arch/arm/boot/Image $(pwd)/arch/arm/boot/zImage: This one is for moving image into the second path (thanks @Has.007 for this infromation)

    Example :

    #!/bin/bash

    export ARCH=arm
    export CROSS_COMPILE=$(pwd)/arm-cortex-linux-gnueabi-linaro_5.2-2015.11-2/bin/arm-cortex-linux-gnueabi-

    mkdir output

    make -C $(pwd) O=output msm8974_sec_defconfig VARIANT_DEFCONFIG=msm8974_sec_ks01_skt_defconfig SELINUX_DEFCONFIG=selinux_defconfig
    make -j4 -C $(pwd) O=output

    cp output/arch/arm/boot/Image $(pwd)/arch/arm/boot/zImage

    - For ARM 64:

    Copy paste this:

    #!/bin/bash

    export ARCH=arm64
    export CROSS_COMPILE="path to your toolchain" (it have to end by something like "nameofarch-something-")

    mkdir output

    make -C $(pwd) O=output "name of defconfig and variant if needed"
    make -j4 -C $(pwd) O=output

    Explaination:

    - #!/bin/bash: Tells the script to run in shell command
    - export ARCH=arm64: Defining which kernel architecture type it is (For example arm64 etc)
    - export CROSS_COMPILE= : Locate where the toolchain is, it has to match the exact path to it and the dash ("-") in the end is really important ! (Almost everyone makes an error at this part!!!)
    - mkdir output: Create a directory for storing compiled zimage
    - make -C $(pwd) O=output : Defining defconfig for guiding kernel compilation (will explain later)
    - make -j4 -C $(pwd) O=output: where the building start, "-j4" is how fast it'll compile, you have to setup this number according to your CPU !
    - cp output/arch/arm/boot/Image $(pwd)/arch/arm/boot/zImage: This one is for moving image into the second path (thanks @Has.007 for this infromation)

    Example :

    #!/bin/bash

    export ARCH=arm64
    export CROSS_COMPILE=$(pwd)/gcc-linaro-aarch64-linux-gnu-4.8-2013.07-1_linux/bin/aarch64-linux-gnu-

    mkdir output

    make -C $(pwd) O=output msm8974_sec_defconfig VARIANT_DEFCONFIG=msm8974_sec_ks01_skt_defconfig SELINUX_DEFCONFIG=selinux_defconfig
    make -j4 -C $(pwd) O=output

    cp output/arch/arm/boot/Image $(pwd)/arch/arm/boot/zImage

    - For Mediatek:

    Copy paste this:

    #!/bin/bash

    export CROSS_COMPILE="path to your toolchain" (it have to end by something like "nameofarch-something-")
    export ARCH=arm ARCH_MTK_PLATFORM=
    make "name of defconfig and variant if needed"
    make -j4

    Explaination:

    - #!/bin/bash: Tells the script to run in shell command
    - export CROSS_COMPILE= : Locate where the toolchain is, it has to match the exact path to it and the dash ("-") in the end is really important ! (Almost everyone makes an error at this part!!!)
    - export ARCH=arm ARCH_MTK_PLATFORM=: Defining which kernel architecture type it is (For example arm64 etc) "ARCH_MTK_PLATFORM=" is for specifying which mediatek platform it is
    - make _defconfig : Defining which defconfig to use (will explain later)
    - make -j4: where the building starts, "-j4" is how fast it'll compile, you have to setup this number according to your CPU !

    Example :

    #!/bin/bash

    export CROSS_COMPILE=$(pwd)/arm-eabi-4.8/bin/arm-eabi-
    export ARCH=arm ARCH_MTK_PLATFORM=mt6580
    make pixi4_4_8g1g_defconfig
    make -j4

    When these step are done make sure you are in kernel folder in terminal and type ". build.sh" (the dot at the beginning is essential don't forget it!)

    If it compiles without any problems:

    Wait till it finishes (it'll say something like "zimage is ready")

    If you followed arm and arm64:

    Then go to "/Output/arch/arm/boot/" to find your zimage.

    If you followed mediatek:

    Then go to "/arch/arm/boot/" to find your zimage.

    Caution : Not all kernel build Zimage, it can build image or other compressed image

    If in case you have any errors:

    Check and see what it says, generally it'll tell you where the error is.

    If the text is going too fast reduce the -j number as explained above.

    For reference I compile with an AMD Phenom X4 3.4GHz,Samsung HDD and 8GB of RAM and it takes around 10min to build

    It is recommanded to type in the terminal "make clean && mrproper" before compiling again​

    5.MAKING THE KERNEL BOOT:​

    You have 2 solutions here:

    1) You can use @osm0sis anykernel method, which is explainded here: "https://forum.xda-developers.com/showthread.php?t=2670512" (A huge shoutout to him!)

    OR

    2) You can unpack the boot.img (from the same rom (CM, touchwizz,sense etc) and android version) and swap Zimage in it explained here : "https://forum.xda-developers.com/showthread.php?t=2073775" (thanks again to @osm0sis !)

    Before flashing the kernel which you've made, backup your "stock" boot.img and Then flash your kernel and see if it boots!


    6.HOW TO ADD FEATURE TO KERNEL WORK:​

    Here starts the most interesting part! Now let's see how it works:

    Basically you can add: Governors, IO Schedulers, Overclock the CPU & Many Tweaks...
    Checkout the github section (Section 7) to see how to add them properly.

    Here's an exemple for adding a governor (this one is called Intellimm) : https://github.com/gugu0das/android...mmit/7186ee60c171b06ea3a027e8383be392d3186bb1

    The text in the blue box is the commit description (generally tells you about the changelog, general information and who originally made the commit)

    The other text boxes tell you about where and which files have been modified/changed.

    Everything in green indicates what has been added.

    Everything in red indicates what has been deleted.

    We can see in the first 2 text boxes that in "arch/arm/configs/" "msm8974_sec_defconfig" and "cm_msm8974_sec_defconfig" have been modified.

    Between the lines 140 and 141 of this files this text has been added : "CONFIG_CPU_FREQ_GOV_INTELLIMM=y"
    (This line is for enabling Intellimm when you're compiling your kernel)

    Same technique applies to the other text boxes (what has been added and deleted and it's location)

    Depending on the features you add, more or less files can be modified, added or deleted.

    So to sum it up, a Commit let's you see all the changes which have been made and everything else!

    7.GUIDE TO GITHUB:​

    For this, I'll direct you over to this awsome guide made by @eagleeyetom !

    8.GPL (IMPORTANT !!!):​

    The Rules as they apply on XDA

    As XDA has no legal power to uphold the GPL (and frankly we want to stay as far away from doing so as possible), we can’t force any of our users to abide by the GPL. However it is in XDA’s interests as well as the interests of our developer-base to ensure all GPL-derived materials hosted or linked on XDA comply fully with the GPL.

    GPL-derived materials that do not come with the complete sources used to compile the GPL components are considered warez, and will be treated as such under forum rule 6 and 9.
    If you use GPL components, but do not make any modifications to them whatsoever, you should provide a link to the original source of your GPL code.
    Sources accompanying a release should be complete, and contain all the necessary source code for any modules, scripts or definition files. Complete sources will be defined as those which compile correctly and completely against the platform for which the software is distributed, and which contain any and all modifications made to the released General Public Licenced code. The source code supplied should be the exact version for which the source code is being requested, complete with all modifications.

    EXAMPLE: Here’s a bit of code that could be used as a template to post your releases

    <Kernel Or Author Name> <Kernel Nr>:
    <Source>|<ReadMe>|<Credits>|<Other>

    The Very Quick Summary of General Public License (GPL)

    The text of the GPL Licence itself will be used to reach any final conclusion regarding any disputes over GPL Licenced materials. The above is a summary of what XDA expects of members using GPL code, and the complete text can be read at the GNU website.



    The GPL states that anyone who modifies GPL licenced code is required to make available the sources used to compile it. This is to further improve and encourage collaborative work, as well as to ensure that the best code possible is produced, and to encourage peer-review of all work. This benefits both developers and end users in numerous ways, including:

    Allowing anyone to verify the code they are trusting with their data, and its authenticity
    Encouraging community collaboration to produce faster fixes and updates, and better code
    Helping bring new developments from other devices and fields to your own, letting you benefit from new code that wouldn’t have been available without this sharing.
    The GPL imparts great freedom for GPL end users. It ensures innovation is never stifled and no project is dependent upon any single developer.

    It is in everyone’s interest for the GPL to be adhered to, as it gives us all better ROMs, better transparency, and a better atmosphere for developers to work together to make great code.

    THANKS :

    - @ravish_919 : For testing and correcting this guide :p
    - @karkasss : As my friend and support ;)
    - @gugu0das : For helping me a lot when I tried to build my kernel ;)
    - @eagleeyetom : For his awsome github guide :)
    - @kirito9 : Huge thanks to him for providing mediatek guide ! ;)
    - @F4uzan : Huge thanks to him for giving me a lot of useful information to fill this guide ! ;)
    - @sunilpaulmathew : For providing an advanced method to rename your kernel ! :D
    - @RendyAK and @DroidThug : For correcting me about "#!/bin/bash" ;)
    - All the developers for their hard work !
    - XDA and The Community!
    32
    TIPS AND TRICKS​

    1. You can use a copy of a defconfig file with different setup :

    Usage : Use a "stock" one and use another one with esperimental feature for testing without altering original defconfig

    Exemple : copy "stock" defconfig and in copied one add a governor see if it compile and work

    How to do : Create a second build.sh with modified defconfig name !

    2. Change kernel name and version :

    Simple method :
    Edit this line "CONFIG_LOCALVERSION="-" after - in your defconfig

    Exemple : CONFIG_LOCALVERSION="-XenomTW-3.2.6"

    Advanced method :​
    1. Add the name after "EXTRAVERSION" (e.g: EXTRAVERSION = -XenomTW-3.2.6) in the 'Makefile' (line 4) which will be found in the root folder..
    2. Edit the last two sections ("const char linux_banner[] =" and "const char linux_proc_banner[] =") of 'init/version.c".

    e.g. Change this to
    const char linux_banner[] =
    "Linux version " UTS_RELEASE " (" LINUX_COMPILE_BY "@"
    LINUX_COMPILE_HOST ") (" LINUX_COMPILER ") " UTS_VERSION "\n";

    const char linux_proc_banner[] =
    "%s version %s"
    " (" LINUX_COMPILE_BY "@" LINUX_COMPILE_HOST ")"
    " (" LINUX_COMPILER ") %s\n";

    To something like this :
    const char linux_banner[] =
    "Linux version " UTS_RELEASE " (XenomTW)"
    "(" LINUX_COMPILER ") " UTS_VERSION "\n";

    const char linux_proc_banner[] =
    "%s version %s"
    " (XenomTW)"
    " (" LINUX_COMPILER ") %s\n";

    More to come...
    9
    Thread Updated with mediatek support !
    Keep in mind that's a basic guide on how to compile kernel :)
    It will be better over time, with more details, tips and tricks etc
    Also arm64 support is coming soon

    I'll make video soon too, I need to train my english accent before
    And thanks to all people who contributed or helped this guide ! ;)
    stay tuned
    8
    Ok guys !
    I was really busy these past times, I train myself to have a better english accent for making videos
    Also 64 bits compiling will come soon stay tuned :)
    8
    What people think about videos too ?
    Like a series of guide
    For example one for basic build
    One for explaining how to implement a feature
    One that explain common issue/bug etc ?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone