Database Info

HOWTO: Compile your own kernel from source (WIP)

Updated. You can find an easier to use and more up to date version here:
http://rootzwiki.com/topic/8824-howto-compile-your-own-kernel-v-01/
Hey folks,
Figured I would throw this out there for those who may want to know just what goes into compiling a kernel, and possibly, doing it themselves. This is a WIP, and is more about how to compile, than how to make changes to source or customize your own kernel.
Needed:
Linux. For this case, we will assume Ubuntu 10.10, 64 bit. This can be done with 32 bit as well, but you will need a different cross compiler.
Download | Ubuntu
dsixda's kitchen. So that we can easily split and repack kernels.
https://github.com/dsixda/Android-Kitchen/archives/master
Source. You can use mine. Its fairly heavily tweaked, and compiles without any modifcations.
https://github.com/adrynalyne/kernel_htc-mecha
A cross compiler toolchain. Because I use 64 bit linux, I use a 64 bit cross compiler.
http://rapidshare.com/files/394529815/HikaRi_toolchain_4.4.4.tbz2
(Credit adwinp from XDA)
Introduction
First, we install Ubuntu. I won't be going through that, however. So, assuming we have Ubuntu already installed, and working, we are ready to dive right in.
First, we need a tool Ubuntu does not install by default. This is called git. From a terminal:
Getting Source Code
sudo apt-get install git
Once git is installed, we can grab our source. Using a terminal:
[[email protected] ~]$
code
Code:
mkdir android
cd android
mkdir kernels
cd kernels
git clone git://github.com/adrynalyne/kernel_htc-mecha.git
Depending on your connection, this could take a while.
This will create a kernel_htc-mecha directory under your /home/username/android/kernels folder.
Grabbing Toolchain
Now we will grab the toolchain. Download it, decompress it, and just leave it in the 4.4.4 directory. Move it to your android directory.
Grabbing and setting up the kitchen
Download the kitchen from the link given above, and decompress it. Rename it to kitchen. Move it to your android directory. Then from a terminal:
code
Code:
cd ~/android/kitchen
chmod 755 menu
./menu
This installs the kitchen and starts it up. Now the first thing we need to do is setup a working directory. Take a rom, any rom, and copy it to the ogiinal_update folder inside the kitchen. You can then setup your working folder.
Inside the working folder, delete boot.img. Grab, one of say, my kernels, and extract it. Take boot.img from the extracted contents and copy to the kitchen.
To split the initramfs (ramdisk) from the kernel, simply choose 0 from the menu, then 20. Hitting w will extract the kernel to a BOOT-EXTRACTED directory inside the kitchen (not working folder). Inside that folder, you will find the ramdisk and a zImage. The zImage is the kernel. We will stop there for now.
Compiling the kernel
First, we move to the kernel directory.
code
Code:
cd ~/android/kernels/kernel_htc-mecha
To compile the kernel, first we must have a configuration file ready. To do this:
code
Code:
make mecha-lte_defconfig
It will configure the system for compiling.
Now to compile the kernel:
code
Code:
make -j5 ARCH=arm CROSS_COMPILE=/home/username/android/4.4.4/bin/arm-none-eabi-
Where username is your, well, username and the number after j (thats a J) is the number of cpus +1.
Depending on the speed of your system. a zImage should be created within 3-30 minutes.
Packing the kernel
The zImage will be located under ~/android/kernels/kernel_htc-mecha/arch/arm/boot directory.
We will copy that zImage into the BOOT-EXTRACTED directory of the kitchen. Then, back at our menu for the kitchen, we hit 'b' to build the kernel. Within seconds, there is a new boot.img inside our Working folder. Now, remember my kernel package you downloaded? Well, time to kang the installer! The directory you unzipped contains a META-INF and system directory. You need both of those. Copy the boot.img in with those two folders.
So, our directory layout currently looks like so:
META-INF
system
boot.img
We need one more file, the wifi driver, from our compiled source.
Under ~/android/kernels/kernel_htc-mecha/drivers/net/wireless/bcm4329_204 you will find a file named bcm4329.ko. Copy this into system/lib of your new kernels installer directory.
Zip these three folders and give it a name. Now its ready to install.
A couple of things of note:
You almost always have to match the wifi driver with the kernel.
make clean mrproper will clean all the precompiled and temp fikes out of your source. This is recommended when making major source changes. Don't forget to remake your configuration after running it though.
Troubleshooting
There may be some files not found errors. Please be careful with these commands.
If the files not found are libcloog.so.0 and/or libmpfr.so.1, take a look below.
Code:
sudo ln -s /usr/lib/libcloog-debian.so.0 /usr/lib/libcloog.so.0
sudo ln -s /usr/lib/libmpfr.so.4 /usr/lib/libmpfr.so.1

Very nice write up, I've been looking into this for a while so its nice someone put it all together in one thread.
Sent from my NookColor using XDA Premium App

Nice Adrynalyne
Sent from my Thunderbolt using XDA Premium App

I love learning new things... Thanks for sharing knowledge!
For those of us that play in a Virtual Box, any notes about issues that may come up? I used to dual boot but decided that a vb is more time efficient for me.

Thanks a lot, i was wondering about this too.
Sent from my ADR6400L using Tapatalk

I'm really glad you've posted this. Time to play for those of us who are lazy (or busy)!

awesome. I love the android community's open-ness. Not only do you post your source, but you tell people how to use it...

Thank you so much for spending the time to write this, i have been googleing this and your write up is the best ive found.
I know this is a work in progress, but some ideas for future revisions, at least things that I have been wondering,
The files tweaked for overclocking, undervolting, and maybe some explanations on what goes into this.
Important files and maybe files we should not touch, (if there are any).
Just things I have wondered.
Thank you again!!!

Wow. Thank you for taking the time to write this up. Some of us really do appreciate it!

You sir, are a gentleman and a scholar.
You really are amazing at what you do. Sometimes I wonder when you sleep..

Uggg, I am running Ubuntu 10.10 64bit.
I have followed this step by step but I am getting the following error:
/home/scott/android/4.4.4/bin/../libexec/gcc/arm-none-eabi/4.4.4/cc1: error while loading shared libraries: libcloog.so.0: cannot open shared object file: No such file or directory
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2!
What package am I missing? I apt-get installed libcloog-ppl0.
Any help is appreciated.
Scott

UPEngineer said:
Uggg, I am running Ubuntu 10.10 64bit.
I have followed this step by step but I am getting the following error:
/home/scott/android/4.4.4/bin/../libexec/gcc/arm-none-eabi/4.4.4/cc1: error while loading shared libraries: libcloog.so.0: cannot open shared object file: No such file or directory
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2!
What package am I missing? I apt-get installed libcloog-ppl0.
Any help is appreciated.
Scott
Click to expand...
Click to collapse
Go to /usr/lib and tell me what the name of libcloog.so.? Is. There are bound to be growing pains with this, as I originally used Fedora 64 bit when I did this. Still, its doable on Ubuntu, because I have this same toolchain on Arch as well.
Let me know what the name of that file is. I will help all I can.
Sent from my ADR6400L using XDA App

adrynalyne said:
Go to /usr/lib and tell me what the name of libcloog.so.? Is.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Adrynalyne,
In my /usr/lib I have the following libcloog files:
libcloog.a
libcloog.so
libcloog-debian.a
libcloog-debian.so
libcloog-debian.so.0
libcloog-debian.so.0.0.0
libcloog-ppl.a
libcloog-ppl.so
libcloog-ppl.so.0
Hope this helps.... It has been a long time since I messed with Linux
Again, I am Ubuntu 10.10 64bit
Thanks again.

sudo ln -s /usr/lib/libcloog-debian.so.0 /usr/lib/libcloog.so.0
sudo ln -s /usr/lib/libmpfr.so.4 /usr/lib/libmpfr.so.1

Trying to run kitchen , when trying to setup working folder it doesnt appear to do anything, I hit 1 and it just sits there. I hit 0 for advanced options and it just sits there.
I have a rom in the right folder as a zip and extracted.
edit: guess you cant extract in windows and copy the files over .

happimeal said:
Trying to run kitchen , when trying to setup working folder it doesnt appear to do anything, I hit 1 and it just sits there. I hit 0 for advanced options and it just sits there.
I have a rom in the right folder as a zip and extracted.
Thanks
Click to expand...
Click to collapse
You arent supposed to extract the rom. The kitchen needs to.

Yes..
all the way to the make and got some errors
/home/jroncalli/android/4.4.4/bin/arm-none-eabi-gcc: 1: ELF

: not found
/home/jroncalli/android/4.4.4/bin/arm-none-eabi-gcc: 2: @: not found
/home/jroncalli/android/4.4.4/bin/arm-none-eabi-gcc: 3: Syntax error: ")" unexpected
CHK include/linux/version.h
SYMLINK include/asm -> include/asm-arm
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
CC scripts/mod/empty.o
/home/jroncalli/android/4.4.4/bin/arm-none-eabi-gcc: 1: ELF

: not found
/home/jroncalli/android/4.4.4/bin/arm-none-eabi-gcc: 2: @: not found
/home/jroncalli/android/4.4.4/bin/arm-none-eabi-gcc: 3: Syntax error: ")" unexpected
make[2]: *** [scripts/mod/empty.o] Error 2
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
Any ideas.

You need the lib32 stuff installed for Ubuntu. Not sure why, as its a 64 bit toolchain. I'm using full 64 bit Arch Linux and don't need to.

adrynalyne said:
You need the lib32 stuff installed for Ubuntu. Not sure why, as its a 64 bit toolchain. I'm using full 64 bit Arch Linux and don't need to.
Click to expand...
Click to collapse
Hmm, probably easier to just install 64 bit version, ....... doing that now.
Thank You.

Where was this guide all weekend lol
been waiting for this thanks bro
now if only i can find a guide to creating flashable .zips hmm
Sent from my ADR6400L using XDA Premium App

[ROM] Native Ubuntu on the Epic!

I got Ubuntu 13.04 to boot cleanly on my Epic! No chroot or VNC hacks involved!
This method loads a custom kernel using kexec and runs off a microSD card.
Check the end of the post for the kernel config and patches, xorg.conf, /etc/modules, the kexec zip, and a pre-built kernel.
I may eventually provide a pre-built root filesystem, but for now it's easy enough to build your own.
For the technically inclined, Debian, Arch Linux, MeeGo/Mer/Nemo/Tizen, Fedora, Gentoo, Slackware, and a few other distros should also work with this method.
Working as of March 30, 2013:
* Touchscreen, 10-point multitouch!
* Unaccelerated X11 with fbdev, framebuffer console disabled for cleaner boot.
* Charging, battery meter
* WiFi
* Sound! NB, the hack I used to get it working disables the codec shutdown sequence, which could affect battery life and prevent the phone from sleeping.
Partially working:
* Keyboard (incomplete layout; not sure what to do with Fn/3rd level key mapping)
* Cameras (recognized as V4L2 devices but VLC complains with "invalid pixel format" so the drivers probably need fixing)
* Sensors/autorotate (sensors recognized in kernel/X11/SDL, I'm working on auto rotation)
Not tested:
* Bluetooth
* GPS
* Calls/data: https://github.com/morphis/libsamsung-ipc
Step by step guide!
PREREQUISITES:
* An Epic 4G with a custom recovery and a microSD card. 2GB free space on the card recommended.
* A Linux computer. Sorry, Windows/Mac users, you're on your own.
Step 0: Get the files you need
Extract the contents of linux_epicmtd.zip to a new folder somewhere and change to that folder in your terminal.
Step 1: Partition your SD card
Please backup of the contents of your SD card before doing anything else.
You can do this by mounting USB storage, but I prefer to remove the card and put it in a USB card reader, that way it's harder to accidentally disconnect it and corrupt data.
What you want to do is shrink the FAT partition from a computer by 2GB and create a new ext2/4 partition out of that free space.
2GB should more than suffice for a minimal Ubuntu install, but if you intend to install Unity (ubuntu-desktop) or other big packages, you may need anywhere from 2GB to 4GB, or possibly more. Resize accordingly.
The following instructions assume the Linux partition you just created is labeled "Ubuntu" and the FAT partition you resized is labeled "microSD". If you don't label them, your mount points will be different.
Step 2: Install Ubuntu on the second partition
Code:
# Assumes your new Ubuntu partition is mounted at "/media/$USER/Ubuntu"
wget http://cdimage.ubuntu.com/ubuntu-core/daily/current/raring-core-armhf.tar.gz
tar xvf raring-core-armhf.tar.gz -C /media/$USER/Ubuntu
Step 3: Configure the filesystem
Code:
# to chroot into the ARM rootfs on a non-ARM computer:
sudo apt-get install qemu-user-static
sudo cp /usr/bin/qemu-arm-static /media/$USER/Ubuntu/usr/bin
sudo mount -o remount,dev /media/$USER/Ubuntu
sudo chroot /media/$USER/Ubuntu
# check /etc/apt/sources.list and make sure universe is enabled
apt-get update
apt-get dist-upgrade
# select your preferred desktop environment
apt-get install {k,x,l,}ubuntu-desktop e17 gnome-session-fallback plasma-active
adduser yournamehere
usermod -a -G audio yournamehere
passwd yournamehere
tzselect
# do anything else you want to do, exit the chroot, then run the following commands from your working folder:
sudo cp X11.txt to /media/$USER/Ubuntu/etc/X11/xorg.conf
sudo cp modules.txt /media/$USER/Ubuntu/etc/modules
adb pull /vendor/firmware/fw_bcmdhd.bin
adb pull /system/etc/wifi/nvram_net.txt
sudo cp fw_bcmdhd.bin nvram_net.txt /media/$USER/Ubuntu/lib/firmware
Step 4: Install the kernel, copy the kexec zip to your SD card, and boot!
Option 1: Use my pre-built kernel.
Code:
cp zImage /media/$USER/microSD
sudo tar xvf modules.tar.gz -C /media/$USER/Ubuntu
cp boot_zImage.zip /media/$USER/microSD
Option 2: Build the kernel from source.
Code:
sudo apt-get install build-essential git gcc-arm-linux-gnueabi libncurses5-dev
git clone git://github.com/CyanogenMod/android_kernel_samsung_epicmtd
cd android_kernel_samsung_epicmtd
git checkout cm-10.1
git apply ../linux_epicmtd.patch
export CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm
cp ../epicmtd_defconfig.txt .config
# make menuconfig if you want to enable the framebuffer console or customize anything
make -j8
sudo make modules_install INSTALL_MOD_PATH=/media/$USER/Ubuntu ARCH=arm
cp arch/arm/boot/zImage /media/$USER/microSD
cd ..
cp boot_zImage.zip /media/$USER/microSD
Reboot into recovery, install zip from sdcard, select boot_zImage.zip, and enjoy your new Ubuntu installation!

First! Very excited for this. Any screens available?
Sent from my Tangerine Dream Epic 4G using xda premium

Hmm can get my phone working on linux pretty flawlessly but my laptop just doesn't like it go figure. Anyways those are my issues [ would be cool if I could find someone to help me with my linux issues] but anyways this is pretty sweet .
Sent from my SPH-D700 using xda premium

Wow, did not see this coming! Gonna attempt this weekend. Awesome work
Sent from my MIUI V4 Epic 4G via Tapatalk 2 beta 5

How is 12.04 for PC in its current state? I'm on 11.10 and I would consider switching, if it wasn't buggy and what not.
Sent from my SPH-D700 using XDA

tdwp16 said:
How is 12.04 for PC in its current state? I'm on 11.10 and I would consider switching, if it wasn't buggy and what not.
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
In my honest opinion, Ubuntu sucks since the 9.x days. I would try out the gnome version of LMDE (Linux Mint Debian Edition). You will never want to go back.
Sent from my SPH-D700 using Tapatalk

I tried out the last Linux mint. I kept having problems with the music player freezing my computer. idk how but that's the only thing that did it. So I switches back yo Ubuntu after using mint for a year or two and just loaded gnome shell.
Sent from my SPH-D700 using XDA

tdwp16 said:
I tried out the last Linux mint. I kept having problems with the music player freezing my computer. idk how but that's the only thing that did it. So I switches back yo Ubuntu after using mint for a year or two and just loaded gnome shell.
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
LMDE is very different from the old mint.
Sent from my SPH-D700 using Tapatalk

I'll try it just because you said so marc. I'll just make another partition for it and play with it. If I like it I'll deff let you know.
Sent from my SPH-D700 using XDA

tdwp16 said:
I tried out the last Linux mint. I kept having problems with the music player freezing my computer. idk how but that's the only thing that did it. So I switches back yo Ubuntu after using mint for a year or two and just loaded gnome shell.
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
weird, i had the EXACT same issue with my last debian install. A while back, but still weird...

beltsnspoons said:
weird, i had the EXACT same issue with my last debian install. A while back, but still weird...
Click to expand...
Click to collapse
I have no clue what it was. I tried everything. Looked up solutions ant there were none. I reinstalled 3 times and it still did it
Sent from my SPH-D700 using XDA

tdwp16 said:
How is 12.04 for PC in its current state? I'm on 11.10 and I would consider switching, if it wasn't buggy and what not.
Click to expand...
Click to collapse
12.04 is actually quite stable. I think they finally got GNOME Fallback ("Classic") right as well - it's set up more like 10.10 with some usability improvements. I never really liked Unity, but it also felt more stable than the version in 11.10 did.

tdwp16 said:
I have no clue what it was. I tried everything. Looked up solutions ant there were none. I reinstalled 3 times and it still did it
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
You can always use vlc instead
Sent from my SPH-D700 using Tapatalk

marcusant said:
You can always use vnc instead
Click to expand...
Click to collapse
Correct me if I'm wrong, but I'm pretty sure they're referring to Debian and/or Linux Mint bugs on the desktop.
Somewhat off-topic, but with a guide this complicated, I don't expect many people to try it. The VNC hack still works, but it's too slow for me, which is the main reason I decided to boot natively.
On a somewhat related note, this can completely replace Android if you are so inclined, but unless you can figure out the internal storage, I still recommend booting from the SD card. You can permanently flash the kernel with Heimdall if you hate Android enough

Err... vlc
Sent from my SPH-D700 using Tapatalk

gTan64 said:
Correct me if I'm wrong, but I'm pretty sure they're referring to Debian and/or Linux Mint bugs on the desktop.
Somewhat off-topic, but with a guide this complicated, I don't expect many people to try it. The VNC hack still works, but it's too slow for me, which is the main reason I decided to boot natively.
On a somewhat related note, this can completely replace Android if you are so inclined, but unless you can figure out the internal storage, I still recommend booting from the SD card. You can permanently flash the kernel with Heimdall if you hate Android enough
Click to expand...
Click to collapse
I had a spell check error lol.
Sent from my SPH-D700 using Tapatalk

oh. em. gee.

awesome... When i finish with my epic i can turn it into a small little tablet now.
BtW, Debian beats the mint so hard... I hate Mint and Ubuntu so im glad those are not the only options.

Doing this right now, will report back with screenies soon.
Edit: everything went swimmingly up until step 3 (I know my way around linux but still pretty noobish):
[email protected]:~$ tar xvf /path/to/victory_patches.tar -C /path/to/
tar: /path/to/victory_patches.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
[email protected]:~$ cd android_kernel_samsung_victory
[email protected]:~/android_kernel_samsung_victory$ scripts/patch-kernel . /path/to/patches
bash: scripts/patch-kernel: No such file or directory
[email protected]:~/android_kernel_samsung_victory$ cp /path/to/victory_config.txt .config || make -C Kernel cyanogenmod_epicmtd_defconfig
cp: cannot stat `/path/to/victory_config.txt': No such file or directory
make: Entering directory `/home/xopher/android_kernel_samsung_victory/Kernel'
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/basic/hash
HOSTCC scripts/kconfig/conf.o
scripts/kconfig/conf.c: In function ‘conf_sym’:
scripts/kconfig/conf.c:159:6: warning: variable ‘type’ set but not used [-Wunused-but-set-variable]
scripts/kconfig/conf.c: In function ‘conf_choice’:
scripts/kconfig/conf.c:231:6: warning: variable ‘type’ set but not used [-Wunused-but-set-variable]
scripts/kconfig/conf.c:307:9: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result [-Wunused-result]
scripts/kconfig/conf.c: In function ‘conf_askvalue’:
scripts/kconfig/conf.c:105:8: warning: ignoring return value of ‘fgets’, declared with attribute warn_unused_result [-Wunused-result]
HOSTCC scripts/kconfig/kxgettext.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
make: Leaving directory `/home/xopher/android_kernel_samsung_victory/Kernel'
[email protected]:~/android_kernel_samsung_victory$ # Check hints.txt for customization tips.
[email protected]:~/android_kernel_samsung_victory$ make -C Kernel menuconfigmake -C Kernel -j8
make: *** Kernel: No such file or directory. Stop.
[email protected]:~/android_kernel_samsung_victory$ make -C Kernel -j8
make: /home/bbelos/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: Command not found
make: Entering directory `/home/xopher/android_kernel_samsung_victory/Kernel'
scripts/kconfig/conf -s arch/arm/Kconfig
make: Leaving directory `/home/xopher/android_kernel_samsung_victory/Kernel'
make: /home/bbelos/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: Command not found
make: Entering directory `/home/xopher/android_kernel_samsung_victory/Kernel'
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/generated/kernelversion.h
UPD include/generated/kernelversion.h
CHK include/generated/utsrelease.h
CC scripts/mod/empty.o
/bin/sh: /home/bbelos/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc: not found
make[2]: *** [scripts/mod/empty.o] Error 127
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2
make: *** Waiting for unfinished jobs....
UPD include/generated/utsrelease.h
make: Leaving directory `/home/xopher/android_kernel_samsung_victory/Kernel'
[email protected]:~/android_kernel_samsung_victory$
Sent from my MIUI V4 Epic 4G via Tapatalk 2 beta 5

You are using /path/to/patches... you need to put the path there...
Sent from my SPH-D700 using Tapatalk

Kernel Building Help

Wondering if anyone can give me a hand. I am trying to build the kernel from source and am running into a problem. What am I doing wrong?
First I obtain the kernel binary git log
git clone https://android.googlesource.com/device/lge/hammerhead
cd hammerhead
git log --max-count=1
I then made note of the commit message received
Then I downloaded kernel sources
git clone https://android.googlesource.com/kernel/msm.git
Then I downloaded prebuilt GCC
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6
Then I went to build
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
git checkout (with the commit message from earlier)
make hammerhead_deconfig
Then I get this error message
make: *** No rule to make target `hammerhead_deconfig'. Stop.
Not sure what I did wrong or how to resolve. Any suggestions? Thanks.

Dude, its hammerhead_defconfig not hammerhead_deconfig.
Check my SCRIPT

Gnome said:
Dude, its hammerhead_defconfig not hammerhead_deconfig.
Check my SCRIPT
Click to expand...
Click to collapse
I'll give that a go and should I perform that command in the hammerhead path or msm path?
Sent from my Nexus 5 using XDA Free mobile app

Chochiwpg said:
I'll give that a go and should I perform that command in the hammerhead path or msm path?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Do that in kernel patch itself..
Based on your post the Kernel Path is msm, so:
Code:
cd msm
then run the commands, dont forget to checkout the right branch, I think it's android-hammerhead-kk-mr2
Code:
git checkout android-hammerhead-kk-mr2

Gnome said:
Dude, its hammerhead_defconfig not hammerhead_deconfig.
Check my SCRIPT
Click to expand...
Click to collapse
Hey bud,
tried defconfig as well and got the exact same error message. Sigh

[HELP]Kernel building

Showing me this when i type
Code:
make -j4
scripts/kconfig/conf --silentoldconfig Kconfig
include/config/auto.conf:189:warning: symbol value 'elf32-i386' invalid for OUTPUT_FORMAT
include/config/auto.conf:271:warning: symbol value 'arch/x86/configs/i386_defconfig' invalid for ARCH_DEFCONFIG
include/config/auto.conf:617:warning: symbol value '-fcall-saved-ecx -fcall-saved-edx' invalid for ARCH_HWEIGHT_CFLAGS
*** Error during update of the configuration.
/home/pranav/android2/kernel/scripts/kconfig/Makefile:33: recipe for target 'silentoldconfig' failed
make[2]: *** [silentoldconfig] Error 1
/home/pranav/android2/kernel/Makefile:496: recipe for target 'silentoldconfig' failed
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop.
Click to expand...
Click to collapse
Trying to build it for Z3 MM Stock from Sony Copyright Archives

you have already configured toolchain?
if so, what are you using?
Then you must select defconfig, in case, shinano_leo_defconfig

Gustavo RD78 said:
you have already configured toolchain?
if so, what are you using?
Then you must select defconfig, in case, shinano_leo_defconfig
Click to expand...
Click to collapse
I have doomlord's toolchain..
This error only comes when i type that command at the end..
Following this Guide
http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276

pranavmali said:
I have doomlord's toolchain..
This error only comes when i type that command at the end..
Following this Guide
http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
Click to expand...
Click to collapse
Which kernel are you trying to build also is your build machine 64-bit?

HerroYou said:
Which kernel are you trying to build also is your build machine 64-bit?
Click to expand...
Click to collapse
Its a 32bit machine
Building MM Stock based kernel

pranavmali said:
Its a 32bit machine
Building MM Stock based kernel
Click to expand...
Click to collapse
There is the problem, you need a 64 bit machine.

First you need to configure the kernel by making the defconfig.
Then you need to specify architecture you're building for using ARCH command.
See here:
http://developer.sonymobile.com/kno...h-a-linux-kernel-from-sony-copyleft-archives/
Also I don't see a branch for 23.5.A.0.575 which is the latest public MM firmware for Z3, so you need to grab the source code for this version off http://developer.sonymobile.com/downloads/xperia-open-source-archives/

Kernel-Source_Nokia_1

Kernel Source of Nokia 1
(TA-1047/TA-1060/TA-1056/TA-1079/TA-1066)
LINK > https://github.com/DhirajSurvase/Kernel_Nokia_1_MT6737​
Instructions >
clone the source code
go to kernel dir
run "bash build.sh" command
ur compiled kernel will be under out/arch/arm/*

Official release of Nokia 1 Kernel sources available at https://www.nokia.com/en_int/phones/opensource

Hi,
We tried the official kernel and built it. After flashing the kernel, phone boot and it asked for a password. We gave password "1234" and it reboots and went in recovery.
Its always rebooting in recovery. We flashed the original boot image. Behavior did not change.
Is there any other recovery image we can use and flash the original boot image and bring the phone to working condition?
Thank You!
Mayur

DhirajMS said:
Kernel Source of Nokia 1
(TA-1047/TA-1060/TA-1056/TA-1079/TA-1066)
LINK > https://github.com/DhirajSurvase/Kernel_Nokia_1_MT6737​
Instructions >
clone the source code
go to kernel dir
run "bash build.sh" command
ur compiled kernel will be under out/arch/arm/*
Click to expand...
Click to collapse
Everyone, help me compile kernel from this source please. I can't do it, because i'm noobie for compile any sources.

ntnamkg said:
Everyone, help me compile kernel from this source please. I can't do it, because i'm noobie for compile any sources.
Click to expand...
Click to collapse
just clone it..
and hit "bash build.sh"

Thanks for respond. But, it is fail, below (some text):
make[1]: *** [scripts] Error 2
make[1]: Leaving directory `/home/namnt/Nokia1/Kernel_Nokia_1_MT6737-master/out'
make: *** [sub-make] Error 2
make: Leaving directory `/home/namnt/Nokia1/Kernel_Nokia_1_MT6737-master'
Click to expand...
Click to collapse
I try build on Ubuntu 14.04, 16.04 and Manjaro linux, all get this notice.

Ok

build.sh: line 35: make: command not found
build.sh: line 39: make: command not found
Click to expand...
Click to collapse
After run bash build get above notice. How to fix it? Thanks

ntnamkg said:
After run bash build get above notice. How to fix it? Thanks
Click to expand...
Click to collapse
apt-get install build-essential
would install make, gcc and other required tools.