Database Info

[Guide] - How to compile the CDMA kernel source and Flash it to your phone (Updated)

You should do a nandroid backup and reboot your phone before trying to flash anything to your phone. This how to involves flashing directly to mtd2, if you don't know what you are doing then please use one of the custom roms available in the Sticky Wiki.
#### Update One Fixed scripts
#### Update Two Added instructions to compile and install the wlan.ko module
#### Update Three Fixed get-CDMAHero-source.sh typo
#### Update Four Added Instructions for Jaunty repo's for Ubunut 9.10
First off i would like to give credit to all the people who have made information and scripts available. I used bits and peices of info and tools written by and or made available by these people.
Armin Coralic http://blog.coralic.nl for creating some nice scripts and making them available
chuckhriczko for helping me out in the middle of the night.
LoxDev for creating a wonderfull how to about creating img's and zip's
tkirkton for helping out with enabling legacy jaunty repos to install java 1.5
Second I am writing this How To, so a complete newbie would be able to understand.
REQUIREMENTS....
Ubuntu Desktop 9.04 or better 32bit (cause thats what i used)
Android SDK (Needed to push and pull files as well as shell access to the phone. You will need to set this up by following the instructions found at http://www.android.com)
Legacy repo's enabled in apt to allow java 1.5 to install
Root access. I ran all commands below as root
I created a dir called "heroc" in my /root directory.
Download zip file below and unzip it in the heroc dir that you should have created.
STEPS
.5 Enable Legacy Repo's to allow java 1.5 to install (below is a cut from tkirktons post on page 7)
Code:
in Ubuntu 9.10, the Java 1.5 package doesn't even list. Here's what I had to do to get it to load:
1. Access a repository from the previous build (9.04 Jaunty will work: commands to put into /etc/apt/sources.list -
deb [URL]http://mirrors.us.kernel.org/ubuntu[/URL] jaunty main restricted universe multiverse
deb [URL]http://mirrors.us.kernel.org/ubuntu[/URL] jaunty-backports main restricted universe multiverse
deb [URL]http://mirrors.us.kernel.org/ubuntu[/URL] jaunty-security main restricted universe multiverse
deb [URL]http://mirrors.us.kernel.org/ubuntu[/URL] jaunty-updates main restricted universe multiverse
2. Set the max age higher than the default. This can be accomplished by editing the /etc/apt/apt.conf.d/20archive. Here's what my lines in that file look like:
APT::Archives:MaxAge "2880";
APT::Archives:MinAge "2";
APT::Archives:MaxSize "1000";
Making these two changes should work...although I have the Intrepid, Hardy and Dapper repositories in mine as well (didn't know which one would work, so I overkilled it).
Run the script again after making the changes and let me know if it works.
.
to update just run
Code:
# apt-get update
1. Create your work environment by running createandroidRepo.sh. This will take some time depending on your internet connection. Make sure you are in the heroc dir.
Code:
# unzip Scripts.zip
# chmod a+x *
# ./createAndroidRepo.sh
This will create a dir call my android and setup all the files and programs needed to compile the kernel. This will take some time to complete.
2. You need to download the source using the get-CDMAHero-source.sh
Code:
# ./get-CDMAHero-source.sh
This will download the source, and extract it to its own directory.
3. you will need to have your .config file handy for the next steps. If you don't have it then you will need to get it by doing the following
Code:
# adb pull /proc/config.gz /root/heroc/config.gz
# gunzip config.gz
The first command will pull the gzipped config from your phone and place it into the heroc dir. the second command will extract the file as "config"
4. This is where it gets fun. We now have everything downloaded and are going to start the process of compiling our kernel.
Code:
# cd heroc_ef05d31a
# export ARCH=arm
# export CROSS_COMPILE=arm-eabi-
# export PATH=$PATH:~/heroc/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin
# make menuconfig
After you run "make menuconfig" it will bring up a the config menu for our kernel. Go to the bottom and select "Load an alternate configuration file". It will then prompt you to select the config file you want to use. You will need to point it to where you have the config file. So type in "/root/heroc/config"
After you have loaded the config file you can edit what ever you want. however if you don't know what do disable or enable then i wouldn't mess around to much.
Next you will need to save your config file. Choose "Save an alternate configuration file", and save it as "/root/heroc/heroc_ef05d31a/.config"
You can now exit menuconfig
5. Time To Compile the kernel and wlan.ko module
Code:
# make
# export KERNEL_DIR=/root/heroc/heroc_ef05d31a/
# cd myandroid/system/wlan/ti/sta_dk_4_0_4_32/
# make
The kernel will take some time. go grab a drink and have a snack. If all goes well you should end up with a zImage file in "~/heroc//arch/arm/boot/". After the kernel is compiled you need to compile the wlan.ko module by executing the last three commands
6. Next we need to copy the zImage back to the heroc dir
Code:
# cp /root/heroc/heroc_ef05d31a/arch/arm/boot/zImage /root/heroc/zImage
7. Ok so now we need to get the boot image from our phone. We need this cause it has more than just the kernel. I contains the ramdisk image as well. and we need to take the boot image and decompress it and remove the old kernel and add our new compiled kernel, then recompress it to newboot.img
Code:
# adb shell
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
# exit
# adb pull /sdcard/mtd2.img /root/heroc/mtd2.img
# mv mtd2.img boot.img
The first two commands will open a terminal shell to your phone and copy the boot image to your sdcard. the last two commands will pull the the boot image from your phone, place it in your heroc dir and rename the file to boot.img
8. Now we will split apart the boot.img using some scripts.
Code:
# ./extract-kernel.pl boot.img
# ./extract-ramdisk.pl boot.img
# rm boot.img-kernel
# cp zImage boot.img-kernel
# ./mkbootfs boot.img-ramdisk | gzip > ramdisk-boot
# ./mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000
The first command extracts the stock kernel from boot.img. The second command extracts the ramdisk from boot.img. The third command will delete the stock kernel. the fourth command renames our zImage to boot.img-kernel. The fifth command takes boot.img-ramdisk folder and zips it up into ramdisk-boot. The sixth comand takes our kernel (renamed to "boot.img-kernel") and ramdisk-boot and combines it back to form a new file called newboot.img.
9. Now we need to flash our "newboot.img" file to our phone. You should reboot your phone before flashing this will insure that you don't get any out of memory errors and will keep your phone from booting into fastboot (Thx Obelisk79).
Code:
# adb push newBoot.img /sdcard/newBoot.img
# adb shell
# cat /dev/zero > /dev/mtd/mtd2 (you may get an error here. don't worry about it)
# flash_image boot /sdcard/newBoot.img
# reboot
The first command will push your boot image to the phone. the second command will bring up shell access to your phone. the third command will zero out mtd2 and get it ready to write your image. the fourth command will flash boot(mtd2) with newboot.img. the last command will reboot your phone
10. After the phone reboots we need to get the wlan.ko file to the phone so that wireless will work
Code:
# adb push /root/myandroid/system/wlan/ti/sta_dk_4_0_4_32/wlan.ko /sdcard/wlan.ko
# adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cp /sdcard/wlan.ko /system/lib/modules/wlan.ko
# exit
Now you have a kernel that you compiles with everything work with the exception of power mgmt.

Just as soon as i figure out how to make an update.zip i will post instructions on how to do this

Added it to the CDMA Hero Guides wiki article.

gu1dry said:
Added it to the CDMA Hero Guides wiki article.
Click to expand...
Click to collapse
dang you beat me to it.

Not sure why, but had to run dos2unix on the the first script, not sure if it is all of them, but it was giving me the error
/bin/bash^M: bad interpreter: No such file or directory
Click to expand...
Click to collapse
dos2unix took care of the issue. Also Thanks for the guide, greatly appreciated!!!

make sure you run the script with the "./" , also you may need to chmod +x the files.

Is there a way to get this to run on the Emulator? I tried to specify the zImage after I compiled it but it won't boot when specifying it. Or will that not work for the HTC zImage?

Excellent guide. Can't wait to try it.

blehzz said:
Is there a way to get this to run on the Emulator? I tried to specify the zImage after I compiled it but it won't boot when specifying it. Or will that not work for the HTC zImage?
Click to expand...
Click to collapse
Check out this link

Check out this link
Click to expand...
Click to collapse
Thanks will have a look. Seems to be the Android kernel and not the HTC kernel though, but will read further into it

blehzz said:
Thanks will have a look. Seems to be the Android kernel and not the HTC kernel though, but will read further into it
Click to expand...
Click to collapse
not sure but i think this will work for you
Code:
# emulator -kernel /path/to/your/zImage

First script didn't work for me on ubuntu. Copying and pasting line by line works.

i'll repack the scripts again

not sure but i think this will work for you
Click to expand...
Click to collapse
that's what i tried... emulator never runs when i specify that zImage it built successfully.

Has anybody tried this yet with Ubuntu running under VMware on a PC running Windows? I know that (in theory) VMware's USB compatibility is spectacularly good (it somehow manages to give the guest OS direct ownership and control of the host PC's USB root hub), but up to now I've only tried it to run XP/32 under Vista/64 and Windows 7/64.
FYI, you can download VMware player for free (as in beer) and use it to run Ubuntu 9.04 with their complete blessing. Just make sure you download a guest OS that configures the hardware (memory, cpu, etc) the way you want it to be, because changing the hardware config is one of the few things you genuinely can't do with the free player. If someone here has the full version (and can find somewhere to host it so the bandwidth charges didn't eat him alive), he could even create an Ubuntu distro that's already set up and configured to build Android kernels for others here to download and use.

To use the first script: open up Synaptics, then download "tofromdos". Now, run "fromdos createAndroidRepo.sh", and it should work then

ROM?
Can someone post how to compile a kernel, and make a ROM, and put it all together in a update.zip? Would be really REALLY nice!
Jason(bikcmp)

Thanks for this guide I'm compiling a kernel right now Just a question, how do I change the kernel version name... like you did in that one screenshot?

bikcmp said:
Can someone post how to compile a kernel, and make a ROM, and put it all together in a update.zip? Would be really REALLY nice!
Jason(bikcmp)
Click to expand...
Click to collapse
Its coming

bikcmp said:
Can someone post how to compile a kernel, and make a ROM, and put it all together in a update.zip? Would be really REALLY nice!
Jason(bikcmp)
Click to expand...
Click to collapse
its in general options in menuconfig.

[KERNEL] CIFS + UTF8 NLS support for the official HTC Desire Froyo kernel

with the release of the source code for the bravo kernel this has become redundant
to be able to directly access my stuff on samba shares i made a _patch_ for the cifs code in 2.6.32.15 and built cifs.ko and nls_utf8.ko with arm-eabi-4.4.0
i thought i'd share them here in case it was of use to anyone else
this is how i installed them:
Code:
(boot into recovery mode)
$ adb shell mount /system
$ adb push cifs.ko /system/lib/modules
$ adb push nls_utf8.ko /system/lib/modules
$ adb shell chmod 644 /system/lib/modules/*.ko
$ adb shell "cd /system/lib/modules; ln -s . 2.6.32.15-gf9c0527"
$ adb shell umount /system
(reboot)
this is how i tested them:
Code:
sh-3.2$ su
sh-3.2# modprobe nls_utf8
sh-3.2# modprobe cifs
sh-3.2# busybox mount -t cifs -o user=<username>,password=<password>,uid=1000,gid=1015,file_mode=0775,dir_mode=0775,iocharset=utf8,nodfs //10.0.1.2/public2 /sdcard/smb/public2
(1015 is the gid of 'sdcard_rw')
--
cifs_bravo_2.6.32.15-gf9c0527.zip
cifs_bravo_2.6.32.15-gd96f2c0.zip

Hey cheers for this will try it out
Sent from my C64

just tried
init_module 'cifs.ko' failed (Exec format error)

epyon1873 said:
init_module 'cifs.ko' failed (Exec format error)
Click to expand...
Click to collapse
as stated above it works with the stock htc kernel, which is 2.6.32.15-gf9c0527
check the output of uname -r

snq- said:
as stated above it works with the stock htc kernel, which is 2.6.32.15-gf9c0527
check the output of uname -r
Click to expand...
Click to collapse
Thx find htc kernel is 2.6.32.15-g1fc4045 @ NexTSense Rom orz

epyon1873 said:
Thx find htc kernel is 2.6.32.15-g1fc4045 @ NexTSense Rom
Click to expand...
Click to collapse
afaik the current nextsense comes with Myshkinbob's cifs module (although not with the latest one) - it's module version id was simply patched to suppress the version mismatch error message you got
here is mine if still interested:
(be sure to type "ln -s . 2.6.32.15-g1fc4045" instead of "ln -s . 2.6.32.15-gf9c0527" when installing)
--
cifs_bravo_2.6.32.15-g1fc4045.zip

Thx~! go to try it.

Greetings,
I tried using your patch on the source for the supersonic (evo) and it went in and compiled perfectly, i was able to do an insmod and loaded the driver fine, but when i go to do a mount the phone crashes.
any ideas?
(i have tried both the arm-eabi-4.4.0 and the arm-2010q1 toolchains)
Thanks!!

adambot said:
I tried using your patch on the source for the supersonic (evo) and it went in and compiled perfectly, i was able to do an insmod and loaded the driver fine, but when i go to do a mount the phone crashes.
any ideas?
(i have tried both the arm-eabi-4.4.0 and the arm-2010q1 toolchains)
Click to expand...
Click to collapse
the patch does not cleanly apply to supersonic-2.6.32.15-g746f4f0, as it is for vanilla 2.6.32.15
please overwrite fs/cifs with the vanilla sources before you apply it
just tried and was able to build the very same .ko published in the first post (except for the buildstamp of course):
pulled the supersonic kernel source from developer.htc.com
overwrote fs/cifs/* with vanilla
pulled & applied the patch from pastebin
pulled .config from my phone
in menuconfig
set the localversion (general setup)
selected cifs + nls_utf8 to be built as module
did _not_ touch the debug options already set
did 'make modules'
stripped the modules with arm-eabi-strip --strip-debug
insmod worked, mount worked, browsing the share worked
if you get crashes, check /proc/last_kmsg after reboot

snq- said:
the patch does not cleanly apply to supersonic-2.6.32.15-g746f4f0, as it is for vanilla 2.6.32.15
please overwrite fs/cifs with the vanilla sources before you apply it
Click to expand...
Click to collapse
What is considered "vanilla sources"?
I used git and pulled the whole android repo but am not finding the vanilla sources there...
do you mean the vanilla linux sources??
[edit]
i tried the cifs files from the vanilla linux source (same version) but the phone still crashes (even after the debug strip)
Should i try to use a different config (rather than the one from the supersonic templates?)
Do you have an evo that you tested this on?
Thanks again!!!
[/edit]

adambot said:
do you mean the vanilla linux sources??
Click to expand...
Click to collapse
sorry if i wasn't clear enough. linux-2.6.32.15.tar.bz2 (kernel.org)
adambot said:
Should i try to use a different config
Click to expand...
Click to collapse
i pulled the config from the device ($adb shell zcat /proc/config.gz > .config)
i do not own an evo, the only reason for me to use evo/incredible sources is that htc haven't released bravo-froyo kernel sources yet

adambot, please let me know if this works for you
--
cifs_supersonic_2.6.32.15-g746f4f0.zip

snq- said:
adambot, please let me know if this works for you
Click to expand...
Click to collapse
WOW!!! That worked PERFECTLY!!!!!
Thanks SO MUCH!!!
(now i just have to figure out why mine wasn't working... I'll try again with your steps and compare the good one to mine with diff)
if you don't mind just to recap:
get linux vanilla kernel source
get supersonic kernel source
replace supersonic fs/cifs with vanilla
edit Makefile with extra EXTRAVERSION info
get .config from running device
make CROSS_COMPILE=CROSS_COMPILE=arm-eabi-4.4.0/bin/arm-eabi- oldconfig (accept defaults)
edit .config and make cifs and nls_utf8 modules
make CROSS_COMPILE=arm-eabi-4.4.0/bin/arm-eabi- modules
arm-eabi-4.4.0/bin/arm-eabi-strip fs/cifs/cifs.ko and fs/nls/nls_utf8.ko

adambot said:
WOW!!! That worked PERFECTLY!!!!! Thanks SO MUCH!!!
Click to expand...
Click to collapse
no problem, glad it worked out
adambot said:
if you don't mind just to recap: ...
Click to expand...
Click to collapse
- i don't see the step where you applied the patch
- i didn't edit the makefile per hand
- i didn't edit .config per hand
- as i don't own an evo, instead of pulling the config from the device i did a 'make supersonic_defconfig' before 'make menuconfig'

snq- said:
no problem, glad it worked out
- i don't see the step where you applied the patch
- i didn't edit the makefile per hand
- i didn't edit .config per hand
- as i don't own an evo, instead of pulling the config from the device i did a 'make supersonic_defconfig' before 'make menuconfig'
Click to expand...
Click to collapse
I got it to work FINALLY!!! I will be posting the step by step (copy/paste) directions in the evo section. Do you mind if i post the patch here as an attachment? also -- how do you want credit -- do snq- or do a different name?
thanks again!!
Adam

adambot said:
Do you mind if i post the patch here as an attachment?
Click to expand...
Click to collapse
feel free to use it for whatever you want
you might however want to post the patch directly applicable to the supersonic source (attached)
thanks for crediting me, using the nick is fine
--
supersonic-2.6.32.15-g746f4f0_cifs.patch

snq- said:
feel free to use it for whatever you want
you might however want to post the patch directly applicable to the supersonic source (attached)
thanks for crediting me, using the nick is fine
Click to expand...
Click to collapse
What did you do differently? (or what is the difference between cifs-supersonic and cifs-vanilla) -- I would look myself, but i'm not the best at coding... (that's what i get for being a sysadmin and not a dev -- but i can script until the cows come home )

Help me
I need nls_utf8.ko for 2.6.34 kernel

I would like cifs module for 2.6.32.15-g6a358a9 kernel, is it posible?
Thanks!

any for 2.6.32.15-ge2fb08e?

running emulator

I am hoping a developer can get back to me on this or someone willing to help.
I downloaded the android source code and successfully compiled (no editing to code was made yet) i compiled as emulator eng (full-eng) but when i try to run the emulator command
$ emulator
i get emulator: ERROR: No initial system image for this configuration!
I put verbose on to see what happening and here is the log
[email protected]:~/WORKING_DIRECTORY$ emulator -verbose
emulator: found Android build root: /home/user/WORKING_DIRECTORY
emulator: found Android build out: /home/user/WORKING_DIRECTORY/out/target/product/generic
emulator: Found target ABI=armeabi-v7a, architecture=arm
emulator: Found target API level: 15
emulator: using core hw config path: /home/user/WORKING_DIRECTORY/out/target/product/generic/hardware-qemu.ini
emulator: found skin-specific hardware.ini: /home/user/WORKING_DIRECTORY/development/tools/emulator/skins/HVGA/hardware.ini
emulator: autoconfig: -skin HVGA
emulator: autoconfig: -skindir /home/user/WORKING_DIRECTORY/development/tools/emulator/skins
emulator: found skin-specific hardware.ini: /home/user/WORKING_DIRECTORY/development/tools/emulator/skins/HVGA/hardware.ini
emulator: keyset loaded from: /home/user/.android/default.keyset
emulator: trying to load skin file '/home/user/WORKING_DIRECTORY/development/tools/emulator/skins/HVGA/layout'
emulator: skin network speed: 'full'
emulator: skin network delay: 'none'
emulator: Found target ABI=armeabi-v7a
emulator: autoconfig: -kernel /home/user/WORKING_DIRECTORY/prebuilts/qemu-kernel/arm/kernel-qemu-armv7
emulator: autoconfig: -ramdisk /home/user/WORKING_DIRECTORY/out/target/product/generic/ramdisk.img
emulator: autoconfig: -sysdir /home/user/WORKING_DIRECTORY/out/target/product/generic
emulator: ERROR: No initial system image for this configuration!
can someone tell me how to fix it, and why im getting this error?

What device are you trying to emulate?

Im trying to emulate a galaxy nexus before i can practice on my g2x, so i simple downloaded the code from git and build the code and trying to run emulator command

Do you have a nexus image? I'm only guessing, but maybe you're missing the ROM/right root directory?

Sorry i'm afraid i still dont understand, these images here are used to recover a phone to stock upon flashing custom rom, and can be used with emulator along source code , the only pre built image was supposed to be the kernel, arn't all other images suppose to come by compiling the code? Do you mind elaborating on what i need to get emulator working with compiled source according to source.android.com i was just supposed to type emulator

Well which ROM are you trying to emulate?
Do you have a ROM you're trying to use?

[Q] Compiling Kernel

Hi All,
I take notes with my Tab2, and sometimes the Default behaviour of the Touchscreen annoys me.
So i decided to recompile the kernel with 3 lines of code added. When done i replaced the zImage in the boot.img of the kkboot stock zip and flashed it trough clockworkmod.
Then i got stuck, my tablet gets stuck inside a boot loop (only the logo comes up, and then reboots after 3 seconds).
The kernel compilation was done by:
- Download Ubuntu, follow the guide on Andriod to setup a build enviorment
- Download Doomlord's toolchain
- Download source from Samsung Open Source
- Adjust code
- Compile using samsungs instructions
How can i resolve this?

http://forum.xda-developers.com/showthread.php?t=1859227 Use Sourcery G++ Lite 2010q1-202 as per Samsung instruction.

ketut.kumajaya said:
http://forum.xda-developers.com/showthread.php?t=1859227 Use Sourcery G++ Lite 2010q1-202 as per Samsung instruction.
Click to expand...
Click to collapse
So, retry compiling with Codesourcery. What parameters do i need to pass to mkbootimg?

Plis man do oc kernel to 1,4 ghz for g tab 7

gieltjev said:
So, retry compiling with Codesourcery. What parameters do i need to pass to mkbootimg?
Click to expand...
Click to collapse
I have my own script base on http://forum.xda-developers.com/showthread.php?t=1241005

ketut.kumajaya said:
I have my own script base on http://forum.xda-developers.com/showthread.php?t=1241005
Click to expand...
Click to collapse
So i downloaded "arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2" and your toolkit.
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
This time the booting takes around 6 seconds, but still resetting.
dawidex444 said:
Plis man do oc kernel to 1,4 ghz for g tab 7
Click to expand...
Click to collapse
If the result is positive i will share my adjustments here so that the real cooks can bake a decent kernel

gieltjev said:
So i downloaded "arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2" and your toolkit.
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
This time the booting takes around 6 seconds, but still resetting.
If the result is positive i will share my adjustments here so that the real cooks can bake a decent kernel
Click to expand...
Click to collapse
So what "adb shell dmesg" output?
EDIT: Incompatible PVR kernel module, disable MODVERSION and add "-blackhawk" string to LOCALVERSION in your kernel config file or you can extract my config file from "/proc/config.gz" by "insmod /system/lib/modules/configs.ko".

ketut.kumajaya said:
So what "adb shell dmesg" output?
EDIT: Incompatible PVR kernel module, disable MODVERSION and add "-blackhawk" string to LOCALVERSION in your kernel config file or you can extract my config file from "/proc/config.gz" by "insmod /system/lib/modules/configs.ko".
Click to expand...
Click to collapse
Wow, how did you find that out?
So i set, CONF_MODVERSION=n, LOCALVERSION='-blackhawk'
Let's recompile
EDIT: Recompiled, added into the CORE kkboot image. Still resetting. while the logo shows i cannot execute "adb shell dmesg". If executed from CWM it adb shell dmesg works.

Code:
$ cp android_espresso10_omap4430_r02_user_blackhawk_defconfig.txt kernel/arch/arm/configs/android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ cd kernel
$ make mrproper
$ make ARCH=arm android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ make -j4 ARCH=arm

ketut.kumajaya said:
Code:
$ cp android_espresso10_omap4430_r02_user_blackhawk_defconfig.txt kernel/arch/arm/configs/android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ cd kernel
$ make mrproper
$ make ARCH=arm android_espresso10_omap4430_r02_user_blackhawk_defconfig
$ make -j4 ARCH=arm
Click to expand...
Click to collapse
Ok, that works! i've got my own kernel running on the device. Now i will continue getting the fix to work.

gieltjev said:
Ok, that works! i've got my own kernel running on the device. Now i will continue getting the fix to work.
Click to expand...
Click to collapse
Congratulations :good:

gieltjev said:
First i extracted the boot.img from "kkboot-0.4.2-core-jb-p51xx.zip", extracted the boot.img and made a new one including my zImage. then using zip replaced boot.img with the new boot.img.
Click to expand...
Click to collapse
What you've done is exactly what I'm trying to do now.
But I'm stuck in unpacking boot.img in kk-boot.
Which unpack/repack tool did you use? Can you plz share them?

aosp kernel for emulator giving error

Hello, when I build the kernel from aosp using the command
BUILD_INITRAMFS=1 BUILD_CONFIG_FRAGMENTS=common-modules/virtual-device/goldfish_defconfig.fragment BUILD_CONFIG=common-modules/virtual-device/build.config.virtual_device.x86_64 build/build.sh
The file goldfish_defconfig.fragment contains only one line
CONFIG_BT_HCIBTUSB=m
After that i try to run the emulator with prebuilt kernel it works. When I try using my built kernel it displays the following
kernel too old to load a ramdisk.
How to solve the problem?
Thank you