Nathan I followed your steps and I succeeded on building my kernel and making the zip file. My problem now is I cant flash it, I keep getting errors. I tried to tar it and other methods but they are not working.
[REFERENCE] How to compile an Android kernel
- Thread starter nathanchance
- Start date
just got lucky today 
i had compile my kernel successfully its for Asus Zenfone 3 (snapdragon). I used AIK for unpacking and repacking unfortunately after flashing the image it doesn't boot it just redirects me to fastboot mode.
i had compile my kernel successfully its for Asus Zenfone 3 (snapdragon). I used AIK for unpacking and repacking unfortunately after flashing the image it doesn't boot it just redirects me to fastboot mode.Hey, first thanks for this tutorial.
Here is my problem, when I try to make clean (or same make 0=out clean), i've an error, I haven't understoop something in the earlier steps but i don't know what.
Screen which should show what i've done :
Here is my problem, when I try to make clean (or same make 0=out clean), i've an error, I haven't understoop something in the earlier steps but i don't know what.
Screen which should show what i've done :
Hey, first thanks for this tutorial.
Here is my problem, when I try to make clean (or same make 0=out clean), i've an error, I haven't understoop something in the earlier steps but i don't know what.
Screen which should show what i've done :
You need to run the make commands in the root of your kernel source, not the configs folder.
Hey, so i've tried to compile this kernel (for Z2_row) : https://github.com/mracar07/android_kernel_zuk_msm8996/tree/8x-caf/
Unfortunately i've some errors when I compile, the defconfig file i've selected is : z2_row_defconfig but the file length is around 4400lines when if i am right generaly defconfig file (i've try to seen the length on some other kernels for other devices) are more around 600 lines. so Have I chosen the bad defconfig file ? (link: https://github.com/mracar07/android_kernel_zuk_msm8996/tree/8x-caf/arch/arm64/configs)
Unfortunately i've some errors when I compile, the defconfig file i've selected is : z2_row_defconfig but the file length is around 4400lines when if i am right generaly defconfig file (i've try to seen the length on some other kernels for other devices) are more around 600 lines. so Have I chosen the bad defconfig file ? (link: https://github.com/mracar07/android_kernel_zuk_msm8996/tree/8x-caf/arch/arm64/configs)
That looks like the correct config, your errors are probably unrelated to that.
Most developers just copy the generated .config file to the configs folder, which is why it is really big. Other developers and companies choose to use the savedefconfig target so that instead of getting a giant defconfig, you get one that only has the values that were changed from the default. The kernel automatically fills in the gaps with the default values.
Need help
Sir,
I have merged gcc compiler.h and also device not booting with gcc7 commit but still device is not booting with gcc 7 olny with gcc 4.9
Plz help
Sir,
I have merged gcc compiler.h and also device not booting with gcc7 commit but still device is not booting with gcc 7 olny with gcc 4.9
Plz help
NepoRood
Recognized Contributor / Retired Forum Moderator
Source: https://GitHub.com/AndroiableDroid/android_kernel_LYF_LS5015
I have booted oreo when compiled kernel using uber 4.9.4 but when I tried to compile a rom lineage rom not booting when I replaced kernel it booted
krasCGQ
Inactive Recognized Contributor
Sounds like your build (boot.img) script where the problem occurs.Now i have new problem
Sent from my Redmi Note 4 using XDA Labs
Holy flippering buckets thank you on another level, I really needed that toolchain information to port some of my binaries pretty sure its all i need. tyty.
pretty sure its all i need. tyty.
My device having kernel source for nougat (msm8916)
Can any one tell me about
How to make my kernel source compatible with Oreo?
Any help highly appreciated
If the questions is already asked
Then please provide me a link
Thanks
Can any one tell me about
How to make my kernel source compatible with Oreo?
Any help highly appreciated
If the questions is already asked
Then please provide me a link
Thanks
First thing first, Thanks for the guide.
Am new to development and have just started building ROMs. All I have worked till now is the device and vendor tree.
I just wanted to ask, if I can use the Stock Motorola kernel as a base for Lineage or AOSP ROMs. Are there any obvious changes I have to make for LOS or AOSP?
Provide any links to that (if exists), or simple Yes/No would also be fine for me to start digging up more information in right direction.
Thanks
Am new to development and have just started building ROMs. All I have worked till now is the device and vendor tree.
I just wanted to ask, if I can use the Stock Motorola kernel as a base for Lineage or AOSP ROMs. Are there any obvious changes I have to make for LOS or AOSP?
Provide any links to that (if exists), or simple Yes/No would also be fine for me to start digging up more information in right direction.
Thanks
You have to wait for your manufacturer to release their kernel source for Oreo
tripLr
Senior Member
If a device has a Oreo 8 or any other stock image , and you get root, or can download the OEM Rom image,
Can you extract the kernel and the build config?
Then build based on the build config?
kernelnewbies.org has instructions
If you're trying to see if a bug is fixed, you probably want to duplicate the configuration on your running kernel. That config file is stored somewhere in /boot/. There might be several files that start with config, so you want the one associated with your running kernel. You can find that by running
cp /boot/config-`uname -r`* .config
Edit. Any reason we can build a kernel on the rooted device? With shell root access?
Can you extract the kernel and the build config?
Then build based on the build config?
kernelnewbies.org has instructions
If you're trying to see if a bug is fixed, you probably want to duplicate the configuration on your running kernel. That config file is stored somewhere in /boot/. There might be several files that start with config, so you want the one associated with your running kernel. You can find that by running
cp /boot/config-`uname -r`* .config
Edit. Any reason we can build a kernel on the rooted device? With shell root access?
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
1
sorry I haven't tried, I'm also newbie. I will try first and may tell you if success -
240Introduction
Hello everyone, I will be going over how to compile a kernel from beginning to end!
Prerequisites:
- A Linux environment (preferably 64-bit)
- Knowledge of how to navigate the command line
- Common sense
- A learning spirit, there will be no spoonfeeding here
What this guide will cover:
- Downloading the source
- Downloading a cross compiler
- Building the kernel
- Flashing the kernel
What this guide will NOT cover:
- Setting up a build environment (plenty of existing Linux installation guides)
- Adding features to the kernel (plenty of git cherry-picking guides)
I know this has been done before but on a cursory search, I have not seen a guide that was recently updated at all.
1. Downloading the source
2. Downloading a cross compiler
3. Compile the kernel
4. Flash the kernel
Tips and tricks
Receiving help
I am happy to answer anything that I touched on in this guide. I may point you to another thread if it's better suited but I don't mind off topic (within reason) within the thread. I also want this to be a collaborative effort; other developers, if you have something to add, correct, or improve upon, please let me know!
I am particular in how people ask for help. I do NOT respond to posts asking for a hand out ("How do I fix this?", "Please fix this!", etc.). I only respond to posts with clear logs and steps that you have tried. Basically, show me that you have read this guide and have a specific issue. I am not here to hold your hand through this, this is a developers' forum.20Compile Android Pie kernels for the Pixel (XL) and Pixel 2 (XL)
Google added a new compat vDSO on Android Pie for 32-bit userspace, which requires a 32-bit toolchain (commit). As a result, if CROSS_COMPILE_ARM32 is not set, your build will error.
After setting your main CROSS_COMPILE in step 1, clone this toolchain (or another compatible arm toolchain) next to the aarch64 one (if in the toolchain folder after running 'export CROSS_COMPILE', type 'cd ..'). Move into the 32-bit toolchain folder using cd then run
Example:Code:export CROSS_COMPILE_ARM32=$(pwd)/bin/<toolchain_prefix>
Code:export CROSS_COMPILE_ARM32=$(pwd)/bin/arm-linux-androideabi-
Then continue on with the rest of the steps.98
Unfortunately, my time nowadays is limited between my job, school, and more important open source projects.
However, compiling with GCC 9.2.0 is the same as compiling with GCC 4.9.4, you point the CROSS_COMPILE variable at the GCC 9.2.0 toolchain (or use PATH and update the CROSS_COMPILE prefix to match) and go from there. There are probably going to be new warnings that you will need to solve and there are potentially some other commits that you will need to pick to get a boot off.
If anyone else wants to pitch in and write something up, I'd be happy to add it to the OP.
