Hello, I've tried to build a custom kernel base on the guide from: http://forum.xda-developers.com/showthread.php?t=622916
I'm running Ubuntu 10.04 and the rest is as in the guide. I've setup the environment, everything work, including the kernel build and boot.img.
Like I said, I've got no errors, but the newly created boot.img it's not booting my HTC Tatttoo, the phone starts and those do anything besides displaying the Tatttoo logo.
The build kernel is based on the kernel found at: http://dl4.htc.com/RomCode/Source_and_Binaries/click-656120.tar.gz and was build without any modification to the kernel config. I mean, I've got the config from my HTC, /proc/config.gz.
When into the kernel source zcat config.gz > .config
then make oldconfig and make.
Also wlan.ko was build without any problems too.
Does anyone know how to see whats going on, why its not booting? Or is there a way to disable all the "logos" so I can see the output of the kernel booting, just like on a normal PC?
Hi guys,
Can we use the android NDK tool from this link here to compile an overclocking kernel on Cyanogenmod 10.2.2 for the nook color? Or do we need to modify the existing overclocking kernel at this source here? It looks like android NDK comes with the toolchains needed for compiling a kernel on the nook color? Or do the makefiles need to be changed from the earlier <dalingrin> kernel to work properly on this device? https://github.com/meteorrock/android_kernel_bn_encore
I am on a x64 linux machine and have all of the dependences met to try to compile a kernel for us. I am using this link here for the dependencies.http://ohheyitslou.blogspot.com/2011/09/ohheyitslou-custom-android-kernel-guide.html
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
I am aware of the Android SDK package with its pre-installed toolchains but the nook color is a stubborn tablet device. Most kernel building guides online are for smartphones.
Any help in this area or input would be appreciated. I have noted this question was asked before in 2011, and went unanswered on this issue as noted above asking this question with the options of XDA 2013 beta.
Thanks.
meteorrock:
Good luck on kernel development. I just set up an android build environment which includes kernel building. If you want a smaller system look at this thread. While the information is specific to the touchpad, almost everything applies to any device, including the NC.
http://rootzwiki.com/topic/21362-guide-build-cm9-kernel-wo-building-rom/
Everything is the same up to the uImage stuff. The touchpad needs a ramdisk combined with the kernel image. It's actually simpler for the NC. All you have to do is adb push the uImage you build to /uImage . Reboot and hope it boots.
An even better guide, in my opinion, is this old one from fattire. It is specifically for the Nook, and will teach you to build Cyanoboot as well. If you are building the 3.0+ kernel, you don't use the omap_evta conifg, anymore, use the encore config in arch/arm/config
There is a separate config for CM-10.1...better to use that if building the component for that rom.
All that is needed is to swap the config in the example for the one you use, and makes sure that the command is pointing to your exact ndk. The example is from NDK 5b, which is way way old by now. There is some talk about Code Aurora tools chains, but you do not need them, it compiles with the NDK just fine.
I compiled the kernel from opensource(samsung) in the Ubuntu 12.04 64bits using NDK r9 legacy toolchains. The kernel compiled with success but when init the SGY he crash after boot screen in a black screen with light on. How to solve?
ps: I use the abootimg to unpack and repack the boot.img
edit: Solve I put arm-eabi armv6 and run
Sorry for my bad english.(Google Translate)
Compile kernel from source,but wifi won't work!
I tried to compile the android kernel from source, my device is E330S, OS is Ubuntu 15.04 x64, version of toolchains is 4.7.
I downloaded the source code of 4.4 from opensource.samsung.com firstly, and follew the instructions of compiling. I got the zImage and packed it into boot.img, flashed it into my phone. All things work well except wifi, the button is unable to be checked, and no configuration file was created in /data/misc/wifi. I change the code to 5.0 and flash the kernel, the device won't boot. Finally i tried to use the code of arter from bitbucket.org/arter97/android_kernel_samsung_msm8974.git, but it won't work either.
The KitKat is the only one that works, i have copied all the *.ko into /system/lib/moduels, but the lsmod shows no modules is installed, .
I am a beginner of compiling the android kernel, is there any tips i missed?
anyone knows?
Hello,
First of all, im new to android modding and linux. I tried to build a kernel from stock G935FXXU1BPH6 source based on their readme file. My problem is, I don't have a zImage file after build that I could put into a flashable zip. I only have Image and Image.gz (I guess thats normal for arm64 kernels?) and I don't know how to make them flashable. I found a youtube video where the dude placed the Image file in a directory called "tools" in his flashable zip, I tried it and TWRP said I installed it successfully but when I start up my phone and check kernel version its still the previous one not mine.
Used this toolchain: aarch64-linux-android-4.9/bin/aarch64-linux-android-
I've set up CROSS_COMPILE path, then I set up configuration:
make ARCH=arm64 exynos8890-hero2lte_defconfig
make menuconfig (to tweak it a little bit more, like custom kernel version string so I can see if it worked)
Then I started build:
make ARCH=arm64
Output when build finished:
>>>>> Time used for generated all hashes is 6 sec
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
DTC arch/arm64/boot/dts/exynos8890-smdk8890.dtb
DTC arch/arm64/boot/dts/exynos8890-universal8890.dtb
Anyone knows how could I make it flashable? Thanks.
keezay said:
Hello,
First of all, im new to android modding and linux. I tried to build a kernel from stock G935FXXU1BPH6 source based on their readme file. My problem is, I don't have a zImage file after build that I could put into a flashable zip. I only have Image and Image.gz (I guess thats normal for arm64 kernels?) and I don't know how to make them flashable. I found a youtube video where the dude placed the Image file in a directory called "tools" in his flashable zip, I tried it and TWRP said I installed it successfully but when I start up my phone and check kernel version its still the previous one not mine.
Used this toolchain: aarch64-linux-android-4.9/bin/aarch64-linux-android-
I've set up CROSS_COMPILE path, then I set up configuration:
make ARCH=arm64 exynos8890-hero2lte_defconfig
make menuconfig (to tweak it a little bit more, like custom kernel version string so I can see if it worked)
Then I started build:
make ARCH=arm64
Output when build finished:
>>>>> Time used for generated all hashes is 6 sec
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
DTC arch/arm64/boot/dts/exynos8890-smdk8890.dtb
DTC arch/arm64/boot/dts/exynos8890-universal8890.dtb
Anyone knows how could I make it flashable? Thanks.
Click to expand...
Click to collapse
This particular chipset (64-bit Exynos) uses the uncompressed Image and a separate dtb.img file made from combining all the dtb revisions of your device codename and region into a DTBH format.
You can flash them using my LazyFlasher project.
See: https://github.com/jcadduono/lazyflasher
You will want to use the kernel-flasher branch. The kernel-flasher-samsung branch isn't fully ready and adds additional patch files to remove TIMA/Knox. I've yet to find out everything that needs to be changed from stock state to allow a bootable custom kernel without disabling encryption, unfortunately.
You can simply git clone it, then place your Image and optionally dtb.img in the root folder of the repository, then type "make" to build a TWRP flashable zip. They will be dynamically replaced in the current boot image on the device when the zip is flashed. You can check out the README.md for more info.
If you want to generate your own dtb.img to include in the installer, you can use a script I made from my universal8890 kernel sources on GitHub:
https://github.com/jcadduono/android_kernel_samsung_universal8890/blob/stock-6.0/dtbgen.sh
(correct the toolchain location for your build in the script)
It also requires the scripts/dtbTool folder (from the same git linked above) to be present in your repository. It's not the same as the Qualcomm dtbTool, and the sources are included (and fairly clean!) if you're interested in learning the Exynos dtb.img (DTBH) format.
./dtbgen.sh hero2lte xx
Now, there's still quite a bit that needs to be done to make the device actually boot successfully and be stable with a custom kernel. While the kernel is perfectly stable, the Samsung customized Android OS will absolutely freak out. That's a bit beyond me, and the reason I haven't really worked on any custom kernels for it myself.
Have fun!
jcadduono said:
This particular chipset (64-bit Exynos) uses the uncompressed Image and a separate dtb.img file made from combining all the dtb revisions of your device codename and region into a DTBH format.
You can flash them using my LazyFlasher project.
See: https://github.com/jcadduono/lazyflasher
You will want to use the kernel-flasher branch. The kernel-flasher-samsung branch isn't fully ready and adds additional patch files to remove TIMA/Knox. I've yet to find out everything that needs to be changed from stock state to allow a bootable custom kernel without disabling encryption, unfortunately.
You can simply git clone it, then place your Image and optionally dtb.img in the root folder of the repository, then type "make" to build a TWRP flashable zip. They will be dynamically replaced in the current boot image on the device when the zip is flashed. You can check out the README.md for more info.
If you want to generate your own dtb.img to include in the installer, you can use a script I made from my universal8890 kernel sources on GitHub:
https://github.com/jcadduono/android_kernel_samsung_universal8890/blob/stock-6.0/dtbgen.sh
(correct the toolchain location for your build in the script)
It also requires the scripts/dtbTool folder (from the same git linked above) to be present in your repository. It's not the same as the Qualcomm dtbTool, and the sources are included (and fairly clean!) if you're interested in learning the Exynos dtb.img (DTBH) format.
./dtbgen.sh hero2lte xx
Now, there's still quite a bit that needs to be done to make the device actually boot successfully and be stable with a custom kernel. While the kernel is perfectly stable, the Samsung customized Android OS will absolutely freak out. That's a bit beyond me, and the reason I haven't really worked on any custom kernels for it myself.
Have fun!
Click to expand...
Click to collapse
Thank you very much!
@jcadduono couldn't make the kernel boot after packing it with lazyflasher. I built a completely stock kernel from the mentioned source, pasted the "Image" (not the Image.gz) file in lazyflasher root and then used make command. Tried including "exynos8890-smdk8890.dtb" file as well. Same story. Not sure if I need anything else in the package or I made user mistake. Do you have any ideas how could I debug what makes it stuck on that screen?
Thanks!
EDIT: Solved Problem.
keezay said:
@jcadduono couldn't make the kernel boot after packing it with lazyflasher. I built a completely stock kernel from the mentioned source, pasted the "Image" (not the Image.gz) file in lazyflasher root and then used make command. Tried including "exynos8890-smdk8890.dtb" file as well. Same story. Not sure if I need anything else in the package or I made user mistake. Do you have any ideas how could I debug what makes it stuck on that screen?
Thanks!
EDIT: Solved Problem.
Click to expand...
Click to collapse
Can you help me set up an environment to build a kernel, arm64, for s7? I'm on Ubuntu having a heel of a time..
Galaxy S7 Edge Kernel Flashing Issues
I am currently trying to flash a different kernel into a galaxy s7 edge (SM-G935S).
I have gone as far as building a kernel and extracting a Image file from it, but every time I try flashing a boot.img with a replaced kernel image file, it seems to never work.
A mkbootimg tool that I am currently using requires a dtb file, but I cannot find where to get it from.
I have tried using @jcadduono's git code, but the dtb file created from it doesn't seem to work as well.
Can anyone tell me what I should do to flash a kernel successfully?
kernel panic after flashing
Hi @ll,
with this guide I was able to compile my own kernel and also flashing it to my phone. Unfortunatelly I'm getting kernel panic after rebooting the phone. is there any possibility to get the reason for this? Or do you have any hint, what I may have done wrong?
Thanks for your help.
Kind regards
v0ti