Hello guys,
i have compiled a kernel for the oneplus one. But i am not sure if it will work so i want to know if these steps are right.
At first i forked francos kernel source + ramdisk.
After that i went into kernel source directory and typed this into the termnial.
Check my make.sh script https://github.com/DerRomtester/one_plus_one/blob/cm-11.0/make.sh
After that i went into the ramdisk source and extracted francos boot.img and deleted a file like this boot.img - zImage
Than i went into the kernel directory and started the build.sh file to get an boot.img file.
Everything went fine.
I had no errors. Are these steps correct.
My kernel source: https://github.com/DerRomtester/one_plus_one
Ramdisk source: https://github.com/DerRomtester/ramdisk_one_plus_one
I hope some devs can help me.
Related
Nov 12th 2010
Was bored again, patched the htc source to 2.6.32.25, has been tested and reported working by Apache14
extract this tar.gz to ~/ if you extract here the script i wrote for anykernel to pack the zimage and modules will pack and sign the zip and place it in the OUT folder after you make your kernel.
Hope you guys can have fun with it
Thanks to koush for anykernel, and Bumble-Bee (Apache14 on XDA) for testing.
Get it HERE
I worked with Bumble-Bee on IRC (Apache14 on XDA) last night and today to get the source working and compiling properly.
There were some issues with the config.gz from the ace causing make errors. The config was a cluster-****, it was trying to build with multiple touch panel configs, camera configs for hardware that wasn't even included in the DHD. So we fixed it and Bumble-Bee has flashed kernels i have compiled from this and they work 100%. So here is the source all packed and ready to go for new kernel compilers or old dogs who don't wish to mess around with the erroneous config.
extract this tar.gz to ~/ if you extract here the script i wrote for anykernel to pack the zimage and modules will pack and sign the zip and place it in the OUT folder after you make your kernel.
Thanks to koush for anykernel, and Bumble-Bee (Apache14 on XDA) for testing
Right now users who are ENG flashed will have to 'fastboot flash zimage /path/to/zImage' and push modules accordingly until Koush makes a custom recovery.
Get -Mr. X- pre setup source HERE
Click to expand...
Click to collapse
Sounds like you have done some good work Mr.X, I thank you and look forward to trying it out for myself.
Thanks Mr X & Bumble-Bee, you have save us alot of time ;-)
thanks again
Bump for new source in first post
I have been trying out the various TW roms that run on MTD and have noticed some problems with the init.rc files that are being used, so I decided to create something that could be used as a base by others. I'm not sure who created the first TW rom on MTD, but they all seem to have mostly the same init.rc file, so I started from the one in tortel's EI22-Stock-ish MTD.
Things I changed:
Various changes and additions from the CM7 version
Removed plus tweaks (all of this can be taken care of elsewhere)
Added init.d support
Added support for /etc/init.local.rc
For init.d support to work, your rom must have the file /system/bin/sysinit, containing something like so:
Code:
#!/system/bin/sh
export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper /system/xbin/run-parts /system/etc/init.d
Every rom I've seen so far has, so it shouldn't be a problem.
How to use:
If you're not familiar with the format of the boot.img file that is flashed to the boot partition, check my other thread here. Basically is contains the zImage, and two ramdisks: boot and recovery. The zImage contains the kernel and a ramdisk: initramfs. The init.rc is located in the boot ramdisk, so I will distribute a copy of that. You can put this into your rom or kernel by deconstructing your boot.img with extract_boot.sh, replacing the boot.cpio.gz with this, then rebuilding the boot.img with mkshbootimg.py
Download:
boot.cpio.gz - 1.2 MB
Thank you. What I need is what changes the the kernel are needed to make a kernel work with MTD. I tried comparing my source tree with Tortell's but he had so many tweaks that it was hard to know what was really needed to make it work.
I thank you greatly for this good sir, and for all of your help !
As you may know farmatito's powersaving kernel is really saving power:
http://forum.xda-developers.com/showthread.php?t=1010932
However, his patches are hard to apply, so I setup a github repo with all patches applied:
github.com/bood/htc-magic-kernel
(not having enouth posts to post a outage url link yet...)
I also ported the vocpcm module so you can run rVoix on it
I only tested on my HTC TIM (32A) phone with old radios
Also, my original camera app does not work with this new kernel (I flashed the new kernel only, apps are untouched), appreciate that if anyone know how to flash it.
Instruction to flash the compiled kernel (32A only)
1. Do a backup
2. enter fastboot
3. unpack the attached 7z file
4. fastboot flash zimage bood-2.6.35.14-autogroup-vocpcm-kernel
5. reboot to recovery
6. adb shell mount -a
7. adb push wlan.ko-bood-2.6.35.14-autogroup-vocpcm /system/lib/modules
8. reboot normally
Update Logs:
2012/02/03
Updated a compiled kernel (autogroup version for 32A) with wlan.ko
2012/02/02
1. Applied all patches except BFS patches since I don't use it
2. Ported vocpcm module
Hello, thanks for that! Would gladly try the compiled version if possible, since I'm using Linux. Thanks in advance.
Actually it is compiled in Linux.
Anyway I've uploaded a compiled version, give it a try!
Sorry didn't made a flashable zip, since the ramdisk could be different.
saibot64 said:
Hello, thanks for that! Would gladly try the compiled version if possible, since I'm using Linux. Thanks in advance.
Click to expand...
Click to collapse
HEh, what I meant was 'I don't use Linux' Thanks for that, will try it !
https://github.com/StarKissed/starkissed-kernel-ekgc100
This repository will include the kernel source from the "Update 1" version of the kernel.
The compile instructions included with the source do not cover making any modifications to the kernel and the previous thread seems to mirror those instructions, so this one will be dedicated to creating custom kernels.
The buildKernel.sh script is fairly straight forward to demonstrate the process, but the config files have a few eccentricities when building the wifi. When loading the config during the build, there are prompts for the bcmdhd parameters that are not referenced anywhere, as the system image does not include any bcmdhd firmware files.
The repository includes a generic ramdisk, as none is provided. Odin flashes the boot.img as a compiled file, so the ramdisk cannot be merged during install like most phones do to maintain the current version. A key note to this is that modules are built into the boot.img ramdisk, which is confusing not coming from any device that does not require Odin.
Edit: The last comment on ramdisk flashing during the install may soon be resolved. There are compatible tools to pack a ramdisk made for the recovery platforms, allowing those items to be included in a zip with the kernel. All that is needed is a custom recovery and that is in the works.
Can anyone tell me is the link below belongs to the kernel source code of cm11s?
I have successfully compiled the kernel source with cyanogenmod_bacon_deconfig but it sucks at the oneplus screen boot screen when start up. Someone please help.
https://github.com/CyanogenMod/android_kernel_oneplus_msm8974/tree/stable/cm-11.0
@ak
you can use this:
https://github.com/CyanogenMod/android_kernel_oneplus_msm8974/tree/shipping/cm-11.0
ak said:
you can use this:
https://github.com/CyanogenMod/android_kernel_oneplus_msm8974/tree/shipping/cm-11.0
Click to expand...
Click to collapse
Still cannot boot with the shipping/cm-11.0 branch.
How should I pack the zImage?
I have the ramdisk which is unpacked from the official 30o kernel.
Which files inside the boot directory should I include?