How to modify the kernel.img

General
#1

emuelec 4.3

wget http://whiteboard.ping.se/uploads/Android/unmkbootimg.gz
gzip  -d unmkbootimg.gz
chmod a+x unmkbootimg
./unmkbootimg kernel.img

after unmkbootimg the kernel.img, I will get these files:

initramfs.cpio.gz  zImage

then I edit the ramdisk:

mkdir initramfs
cd initramfs
cpio -idmv < ../initramfs.cpio.gz

## do some change  ###########

find . | cpio --create --format='newc' > ../initramfs.cpio.gz
cd ..

and create the new kernel.img

mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x0 -o kernel.img

Using the modified kernel.img will not boot, and how the content of kernel.img.md5 is generated

round 2:
I use these content Search · ANDROID_BOOTIMG_OPTIONS · GitHub

mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz \
  --base 0x0 --kernel_offset 0x1080000 -o kernel.img

could boot, but will had a kernel-overlay error

60d4a361fa818c30818339460ae96ca
60d4a361fa818c30818339460ae96ca1920×1440 146 KB

#2

Now it can be started, kernel.img.md5 and the problem of this boot error, can anyone answer me?

#3

To be honest, I can’t see any useful info to diagnose the problem. The screenshot only says “Main process exited”, no further info available. I don’t think any one can give you useful suggestions.
I would compile EmuELEC from source code if I were you.

#4

Did you know how the content of kernel.img.md5 is generated

#5

kernel.img.md5 is just the md5 sum of the kernel.img file if I’m not mistaken, and in linux can be generated using in linux:

md5sum FILE.img

how come your modifying the kernel though? The best way would be to change the linux source then re-compile it.