Yesterday I donwloaded CF_FIRE kernel (http://forum.xda-developers.com/showthread.php?t=2263720) for my WFS 2012. After compilation with default config using arm-eabi-4.4.3 and packing into boot.img using abootimg tool kernel doesn't boot. Inmediately after booting it from fastboot phone restarts. Phone is S-OFF. Image unpacking and re-packing works well, I made some modifications to ramdisk, also precompiled kernels are working. WTF?
SOLVED
Problem solved, i made mistake in kernel base address in config file.
Related
Hello all. I was wondering whether it'd be possible to put a 2.6.27 kernel into a 2.1 rom so that it can be made faster for the time being.
For now, i can boot up the image using
fastboot boot zImage
but i want it to be the default kernel it boots not the .29 one. Whenever i try to flash the 2.6.27 kernel from recovery mode, the phone will refuse to start up. Is there any way around this?
Yes I have the 2.6.27 working on the 2.1 ROM. (With Brain **** Scheduler Patches)
How?
10char
Compile your 2.6.27 kernel, create the required libs. unpack boot.img mv zImage as your new kernel repack it and boot.
This post has helped me a lot!
http://forum.xda-developers.com/showthread.php?t=551711
what do you mean by create the required libs? I already have a zImage file.
And the wlan.ko (loadable module)?
Did you compile this with most of it static in the kernel?
i have that as a seperate file which i'll push to the system after i flash the kernel
Well then go ahead
hello everyone
can anyone please patch any cm 11/11.1 xperia arc kernel for 0% battery error..
if you know how to build a kernel please make one patched kernel for me..
i have searched the thread but there is no cm 11 kernel patch.
i know about this thread but can't compile a kernel
http://forum.xda-developers.com/showthread.php?t=1312398
Compile your own version
This are simplified steps. If you dont know how to do, search in the forum.
- First, download the stock kernel source for Xperia (watch out for the correct version), or the sources for your custom ROM you want to use if its not compatible with stock kernel. The developer thread of dev Kalled from Sony (search on developer thread) has some instructions on how to compile the kernel.
This is the direct link to download Sony stock kernel sources:
http://developer.sonymobile.com/downloads/opensource/
- For the ARM compiler, download the CodeSourcery arm eabi compiler version 2010q1.
https://sourcery.mentor.com/sgpp/lit...al/release1294
- Install the compiler on Linux (You can use a virtual machine if you have Windows - use Virtual Box or VMWave Player, both are free for home use).
- Overwrite the bq27520 driver source code with the patched driver from this thread.
- Next, follow the guide on Kalled thread to select phone version and compile the Kernel.
- In the end of compilation, you get a zImage file, that is YOUR Kernel. Congratulations.
- You need a ramdisk. If you are targeting a custom ROM, get a ramdisk compatible with your custom ROM. Also, you can go to DoomLord thread about ramdisk and get a ramdisk suitable for your building. Or generate/use your own ramdisk if you know how. If you use other's ramdisk, give theirs credit.
- With kernel image and ramdisk, generate the file boot.img using mkbootimg tool from Android SDK, or abootimg tool from kubuntu repositories.
- If you choose to use mkbootimg, download a compiled version of mkbootimg, or compile your own version from Android SDK.
- Now you have a boot.img file. Flash it on your phone using fastboot and you are done.
KERNEL I WANT IT TO BE PATCHED
http://www.mediafire.com/download/3o9w31gni49fz4t/11DarkAnzu20140320.img
I HAVE ATTACHED WHAT'S NEEDED(PATCH TO BE REPLACED)..
PLZZ ANYONE HELP..
Hello friends,
I wanted to start kernel developing for the N910F. So i wanted to start compiling the original samsung sources.
Please excuse me, I'm pretty new to android/linux development.
I managed to get the kernel compiling, which gives me an output folder with some GB of stuff and as i could point out a zImage-file, which is hopefully the compiled kernel
To get my kernel working, extracted a stock boot.img with umkbootimg, which gave me a warning, that i can't repack the boot.img without using a modified mkbootimg executable.
A mkbootimg is included in the sammy-source so i used this to pack my zImage together with the extracted initfs.gz, resulting in a boot.img.
Which I flashed ofc, but the reason why i opened this thread is the result of this
The kernel is obviously not booting, it shows for maybe 0.5s the sammy logo and directly starts into download mode.
I guess it has something todo, how i pack my kernel. because i didnt even manage to unpack the stock kernel and repack it and get it booting.
So where is my mistake? Do i miss something?
greez d4rk
Deleted - I notice I replied to an old thread
Hello xda,
I am new into kernel development.Recently I downloaded the kernel sources for my phone Zenfone 2 Laser -ZE550KL
After that I compiled the stock kernel, since It is based on arm64 I got a file named Image instead of zImage.
After searching I found a way to convert that to a boot.img (using the ramdisk from stock kernel).I could get the kernel to boot on the device using
Code:
fastboot boot boot.img
The device booted successfully with the kernel, I could see change in the name of Kernel in About Phone.
But the problem is Wifi/Bluetooth and Soft keys do not work.Wifi turns on But cannot see any AP.
BT works(A BT enabled watch vibrated )but no device can be seen in bletooth settings.
Please help me with this kernel.
here is the link to my source=>
https://github.com/abhishekr700/ZE550KL_KERNEL
I am using ze550kl_defconfig present in /kernel/arch/arm64/configs to make .config file for building kernel.
Thanks.
You have a thread for this topic already in the correct section (Q&A):
http://forum.xda-developers.com/android/help/help-wifi-bluetooth-compiling-kernel-t3368463
Please only create one thread per topic, thread closed.
Hey guys,
I just compiled the Oneplus 5T Stock Kernel for android Oreo with the msmcortex_defconfig.
The kernel seems to boot fine but wifi seems to be disabled?
Can the device blob trees be a reason for this?
I basically compiled this:
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8998/tree/oneplus/QC8998_O_8.0
And with abootimg I made a boot img with my compiled (stock) kernel and the stock ramdisk.
The only notable difference is that with the stock kernel (from OTA) there are 20 device tree blobs while in my compiled kernel there are only 7.
Any reason for that difference, and might this be the cause of the problem?
Greetings,
Down...