This is an attempt to make kernel from my Jaguar rom work on most other custom roms.
1. Nightmare and Impulse governors
2. Overclock to 2304 and 1766 (big/little) is available: settings will hold if set in Kernel Adiutor
3. Voltage control
4. Zenmode Hotplug
5. Intellithermal
6. Seccomp (secure computing)
7. Yama security
8. Several Pax security features
9. Several Grsecurity features
10. Default entropy bumped up to 1024 read and 896 write
Warning. During installation, a script will unpack your existent kernel to replace zImage , install appropriate modules to your system and preserve your ramdisk files. Data partition won't be touched. Keep in mind, there is still a chance that kernel wouldn't work with your rom., because Jaguar has a heavily modified bionic, which also requires kernel changes. That's why I call this an attempt. Forget it: kernel works fine on several roms, as confirmed by users. But do backup everything and be ready to reflash your existing rom. Again, data from your rom won't be touched...
Instructions: Just flash the zip in TWRP
Credit: Anykernel team, as well as those who contributed to regular kernel sources, which is the whole world And special credit to DD3Boch, as I have used a part of his script, which he took from anykernel and modified. And I have modified his script. I have removed that useless backup language. So, there is nothing here related to DD3boh.
__________________________________________________________________________________________________________
December 7. Kernel updated to include December security patches and Westwood tcp algorithm.
Download December release: https://forum.xda-developers.com/devdb/project/dl/?id=27585
November 6. Kernel updated to include November security patches, as well as the latest Code Aurora security patches. Also, you will probably have offline charging working with percentage showing (maybe), but not the animation.
Download Jaguar Kernel November 6: https://forum.xda-developers.com/devdb/project/dl/?id=27209
October 3. Kernel updated to include October security patches plus more. See github for commits.
Download Jaguar Kernel October 3: https://forum.xda-developers.com/devdb/project/dl/?id=26868
September 15. Kernel updated to include September security patches, fixed leds, increase vibration and more
Download Jaguar Kernel September 15: https://www.androidfilehost.com/?fid=817550096634799803
________________________________________________________________________________________
August 14. Want to have cpu voltage control feature on any custom rom? Here is Jaguar Kernel with it. Just flash in TWRP, apply Magisk/Supersu and reboot. Be careful, as undervolting could result in instability and even random reboots.
Download Jaguar Kernel with voltage control Aug 14: https://www.androidfilehost.com/?fid=673368273298978710
__________________________________________________________________________________________
August 13: New release which includes new camera driver, as well as August security patches. No EAS...
Download August 13 release: https://forum.xda-developers.com/devdb/project/dl/?id=26145
____________________________________________________________________________________________________
July 22: New release with vibration max increased:
Download: https://forum.xda-developers.com/devdb/project/dl/?id=25756
________________________________________________________________________________________________________
Download:https://forum.xda-developers.com/devdb/project/dl/?id=25531
XDA:DevDB Information
Jaguar Kernel Universal, Kernel for the Lenovo ZUK Z2 (Plus)
Contributors
optimumpro
Source Code: https://github.com/AOSP-Jaguar/android_kernel_zuk_z2_plus
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2017-07-09
Created 2017-07-09
Last Updated 2017-11-06
Reserved
Reserved...
Mine...
Thank you ! Any bugs ?
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
And how much kinds of the governors ?(poor English, sorry )
xzw2000 said:
Thank you ! Any bugs ?
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
And how much kinds of the governors ?(poor English, sorry )
Click to expand...
Click to collapse
Nougat is pretty stable now. As for governors, hotplug and thermal, read the description. It's all there...
About Thanks not given
@optimumpro You should add even my name between the thanks: you used my Anykernel2 repo located here
This is easily recognizable thanks to my backup modules script, just download your kernel and at the file update-binary into META-INF/com/google/android, line 44 and after... now compare it with this
You will notice that it's exactly the same. I would also presume that you didn't even know that this script is there because you didn't write about it in this thread.
You can also see that you're using my repo from looking at the anykernel.sh script where there are some lines like "add custom tuning to init.rc" or "add spectrum support" that you forgot to remove lol
It's actually even funny that after you said that I know a very little about the development and that I should learn the real programming you use a repo with my edits and without even giving credits.
And that's who usually calls me "fake dev"...
DD3Boh said:
@optimumpro You should add even my name between the thanks: you used my Anykernel2 repo located here
This is easily recognizable thanks to my backup modules script, just download your kernel and at the file update-binary into META-INF/com/google/android, line 44 and after... now compare it with this
You will notice that it's exactly the same. I would also presume that you didn't even know that this script is there because you didn't write about it in this thread.
You can also see that you're using my repo from looking at the anykernel.sh script where there are some lines like "add custom tuning to init.rc" or "add spectrum support" that you forgot to remove lol
It's actually even funny that after you said that I know a very little about the development and that I should learn the real programming you use a repo with my edits and without even giving credits.
And that's who usually calls me "fake dev"...
Click to expand...
Click to collapse
I never called you a fake dev. I only said you didn't have a clue about kernels and roms. And I said nothing about scripts. Your repo?! LOL. And where did you clone it from? Well, there is nothing in the install script that I used that came from you. But anyway, my big thanks.
Now, go away in peace, until they delete you...
.
optimumpro said:
I never called you a fake dev. I only said you didn't have a clue about kernels and roms. And I said nothing about scripts. Your repo?! LOL. And when did you clone it from?
Now, go away in peace, until they delete you...
.
Click to expand...
Click to collapse
1. This script is related to kernels
2. This script has been made by myself editing anykernel and all the history is properly commited is on my github account, it seems that the person that "hasn't clue about kernels and roms" isn't me but another one
DD3Boh said:
1. This script is related to kernels
2. This script has been made by myself editing anykernel and all the history is properly commited is on my github account, it seems that the person that "hasn't clue about kernels and roms" isn't me but another one
Click to expand...
Click to collapse
All right. Now leave. I have no interest in talking to you. Cheers...
optimumpro said:
All right. Now leave. I have no interest in talking to you. Cheers...
Click to expand...
Click to collapse
lol, sometimes you make me even laugh.
DD3Boh said:
lol, sometimes you make me even laugh.
Click to expand...
Click to collapse
I will add your name to credits, just because I am in a good mood... But if you come back to one of my threads with nonsense again, I will remove that.
I also want to thank you for putting this in your DarkMoon install script:
Code:
# Abort on Jaguar
build_type="$(mount /system; grep "^ro.build.flavor" /system/build.prop | cut -d= -f2)";
if [ $build_type == "jaguar_z2_plus-userdebug" ];
then
abort "This ROM isn't supported by the DarkMoon Kernel";
I certainly don't want Jaguar users to use DarkMoon kernel...
optimumpro said:
I will add your name to credits, just because I am in a good mood... But if you come back to one of my threads with nonsense again, I will remove that.
I also want to thank you for putting this in your DarkMoon install script:
I certainly don't want Jaguar users to use DarkMoon kernel...
Click to expand...
Click to collapse
I don't want this too, I added that line because I don't want my kernel to be installed in such ROMs.
And about the credits, you used a script created by me....
DD3Boh said:
I don't want this too, I added that line because I don't want my kernel to be installed in such ROMs.
And about the credits, you used a script created by me....
Click to expand...
Click to collapse
You, my "friend" have created big NOTHING. Here is the script from anykernel:
Code:
# AnyKernel2 Ramdisk Mod Script
# osm0sis @ xda-developers
## AnyKernel setup
# begin properties
properties() {
kernel.string=DirtyV by bsmitty83 @ xda-developers
do.devicecheck=1
do.modules=0
do.cleanup=1
do.cleanuponabort=0
device.name1=maguro
device.name2=toro
device.name3=toroplus
device.name4=
device.name5=
} # end properties
# shell variables
block=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot;
is_slot_device=0;
## AnyKernel methods (DO NOT CHANGE)
# import patching functions/variables - see for reference
. /tmp/anykernel/tools/ak2-core.sh;
## AnyKernel permissions
# set permissions for included ramdisk files
chmod -R 755 $ramdisk
chmod 644 $ramdisk/sbin/media_profiles.xml
## AnyKernel install
dump_boot;
# begin ramdisk changes
# init.rc
backup_file init.rc;
replace_string init.rc "cpuctl cpu,timer_slack" "mount cgroup none /dev/cpuctl cpu" "mount cgroup none /dev/cpuctl cpu,timer_slack";
append_file init.rc "run-parts" init;
# init.tuna.rc
backup_file init.tuna.rc;
insert_line init.tuna.rc "nodiratime barrier=0" after "mount_all /fstab.tuna" "\tmount ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data remount nosuid nodev noatime nodiratime barrier=0";
append_file init.tuna.rc "dvbootscript" init.tuna;
# init.superuser.rc
if [ -f init.superuser.rc ]; then
backup_file init.superuser.rc;
replace_string init.superuser.rc "Superuser su_daemon" "# su daemon" "\n# Superuser su_daemon";
prepend_file init.superuser.rc "SuperSU daemonsu" init.superuser;
else
replace_file init.superuser.rc 750 init.superuser.rc;
insert_line init.rc "init.superuser.rc" after "on post-fs-data" " import /init.superuser.rc";
fi;
# fstab.tuna
backup_file fstab.tuna;
patch_fstab fstab.tuna /system ext4 options "nodiratime,barrier=0" "nodev,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc,discard";
patch_fstab fstab.tuna /cache ext4 options "barrier=0,nomblk_io_submit" "nosuid,nodev,noatime,nodiratime,errors=panic,barrier=0,nomblk_io_submit,data=writeback,noauto_da_alloc";
patch_fstab fstab.tuna /data ext4 options "nomblk_io_submit,data=writeback" "nosuid,nodev,noatime,errors=panic,nomblk_io_submit,data=writeback,noauto_da_alloc";
append_file fstab.tuna "usbdisk" fstab;
# end ramdisk changes
write_boot;
## end install
that anyone is free to use. Just because you put there Z2_131 doesn't make it yours. Nothing here gives you the right to claim it is "yours". I understand this is what you think development is, but it is not. Remember, I never called you a fake developer. I just said you had no clue about developing roms or kernels.
So, leave, because I am going to remove credit that I gave you in the OP. You don't deserve it anyway. So, leave...
Has anyone been able to boot this kernel on a different rom?
optimumpro said:
You, my "friend" have created big NOTHING. Here is the script from anykernel:
that anyone is free to use. Just because you put there Z2_131 doesn't make it yours. Nothing here gives you the right to claim it is "yours". I understand this is what you think development is, but it is not. Remember, I never called you a fake developer. I just said you had no clue about developing roms or kernels.
So, leave, because I am going to remove credit that I gave you in the OP. You don't deserve it anyway. So, leave...
Click to expand...
Click to collapse
After this comment I can say that YOU UNDERSTOOD NOTHING ABOUT WHAT I SAID
What is mine and that I have created and literally developed is the script to backup the modules and the boot.img, I spent time doing it, and it's funny how another developer that said "I know nothing about the development" and that I should "start doing real development" took it and used my source... LOL (and without even knowing that it was there, this part is the funniest one )
DD3Boh said:
After this comment I can say that YOU UNDERSTOOD NOTHING ABOUT WHAT I SAID
What is mine and that I have created and literally developed is the script to backup the modules and the boot.img, I spent time doing it, and it's funny how another developer that said "I know nothing about the development" and that I should "start doing real development" took it and used my source... LOL (and without even knowing that it was there, this part is the funniest one )
Click to expand...
Click to collapse
As I have said before: nothing that is being used here has come from you.
But it is good that we agree on one thing: we don't want Jaguar rom to have anything to do with your kernel. Cheers. And get lost...
optimumpro said:
Has anyone been able to boot this kernel on a different rom?
Click to expand...
Click to collapse
Yes booting in AEX
benplay64 said:
Yes booting in AEX
Click to expand...
Click to collapse
So, it works. Good to know...
optimumpro said:
As I have said before: nothing that is being used here has come from you.
But it is good that we agree on one thing: we don't want Jaguar rom to have anything to do with your kernel. Cheers. And get lost...
Click to expand...
Click to collapse
You known that just because is your thread you can't tell to people to get out from there just because you don't like what they are writing?
This script has been made by ME, you can't say that this isn't the truth because I spent hours on it and fixing it.
It's like if I would say that you didn't fix the encryption but just copied and pasted from other parts completely randomly... But I'm not saying that simply because I don't think this is the truth.
I would suggest you to look better at the code the next time, because this time you missed something
DD3Boh said:
You known that just because is your thread you can't tell to people to get out from there just because you don't like what they are writing?
This script has been made by ME, you can't say that this isn't the truth because I spent hours on it and fixing it.
It's like if I would say that you didn't fix the encryption but just copied and pasted from other parts completely randomly... But I'm not saying that simply because I don't think this is the truth.
I would suggest you to look better at the code the next time, because this time you missed something
Click to expand...
Click to collapse
I am telling you to get out, because you are spamming and trolling here. It is simple. It is not even about your cluelessness.. If you don't leave on your own, you will be deleted like everyone else who came here trolling and spamming...
Related
Disclaimer: For devs only. Updating to it will wipe your device. I am not responsible of any damage of any sort or data loss or anything. Alway do a nandroid backup before updating
Kernel android-msm-2.6.27-hero-community
The purpose of that community project is to have an optimized hero kernel based on HTC kernel sources.
Current release: 1.4 [download]
Features:
- compcache with ramzswap enabled
- /system/etc/init.d init scripts support
- some init script (firstboot, userinit)
- CIFS support
- Ext4 full support
- Removed DEBUG options
- All bluetooth options (don't know if needed ??)
- Droidwall support
- Pptp support (need testing)
- IP Gre tunnel module
- SquashFS 3.4
Links:
Git
Wiki
Issues tracker
Note: devs, as a community project, you patches or configuration corrections are welcomed. Feel free to submit.
Note: if anyone needs it, in the downloads section of the git there is the patch to apply to android-msm-2.6.27 sources so they compile for Hero.
Note: this kernel does not support modaco roms, the reason is that modaco rom is dependant of scripts called from kernel ramdisk, witch is not good. If you use Modaco rom, use teknologist kernel (http://ow.ly/yCxu) witch have similar tweaks
Changelog
Version 1.4 - Nov 3rd 2009
- added ext4 full support
- some init.d scripts (firstboot, userinit)
- squashfs 3.4
Version 1.3 - Nov 3rd 2009 (test build)
Version 1.2 - Nov 3rd 2009
- added ext4dev support (ext4 support in git, update.zip coming soon)
- added pptp support
- removed kernel debuging options
- added ramzswap init.d script
Version 1.1 - Oct 29th 2009
- added support for /data/init.sh script
- added support for /system/etc/init.d/* scripts
Version 1.0.1 - Oct 29th 2009
- fixed wlan.ko
Version 1.0 - Oct 28th 2009
- compcache 0.5.4 patch
- optimized config by Teknologist
Thanks for the hard work and more importantly sharing!..... this will be very useful once Ive got my oven sorted
Lox could you also post the version number of compcache that is integrated ? (and version numbers for future addons) cant wait to test the next release
Edit: Do i need to wipe the data before i update to this kernel? because i cant turn on wifi
whats the diff between AOSF CUPCAKE thread and this? these two projects do diff jobs? which will give us a basic android rom withot sense thing?
dying4004 said:
whats the diff between AOSF CUPCAKE thread and this? these two projects do diff jobs? which will give us a basic android rom withot sense thing?
Click to expand...
Click to collapse
This is the an optimized kernel to run any rom.
Lox_Dev said:
This is the an optimized kernel to run any rom.
Click to expand...
Click to collapse
WHOA!!!
LOX u have got really close in getting those nice roms and fancy stuffs in hero. so this is the base of all roms and fancy things.
CONGRATS BRO
New version 1.1.
Now you can have init scripts in /system/etc/init.d. /data/init.sh supported too.
To run Compache and have a really faster kernel, follow this how to. Busybox is needed (here is an update.zip to install it)
Lox_Dev said:
New version 1.1.
Now you can have init scripts in /system/etc/init.d. /data/init.sh supported too.
To run Compache and have a really faster kernel, follow this how to. Busybox is needed (here is an update.zip to install it)
Click to expand...
Click to collapse
could you also add little adb how-to for adding @ moving 05ramzswap file to init.d ?
i read all the references printed in first post, but there is nowhere a description of what has been optimized.. can someone please inform ;-)
felikz said:
i read all the references printed in first post, but there is nowhere a description of what has been optimized.. can someone please inform ;-)
Click to expand...
Click to collapse
second post maybe?
jaapschaap said:
second post maybe?
Click to expand...
Click to collapse
thats just the CHANGE LOG?
@ Lox_Dev
Thanks
This 05ramzswap script is correct?
#!/system/bin/sh
insmod /system/lib/modules/lzo_decompress.ko
insmod /system/lib/modules/lzo_compress.ko
insmod /system/lib/modules/compcache/xvmalloc.ko
/system/xbin/insmod /system/lib/modules/compcache/ramzswap.ko memlimit_kb=64200 backing_swap=/dev/block/mmcblk0p3
swapon /dev/block/ramzswap0
fi;
For building the rom, is correct added this line in update-script?
show_progress 0.5 0
show_progress 0.2 0
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.2 10
Thank you and sorry my english.
MACH_SAPPHIRE=y
Click to expand...
Click to collapse
Does this option is really necessary ?
thx lox, thread sticky
I managed to use nandroid's restoring method and put new boot.img back without any data wipe. Here is how I did it: Make a nandroid backup first, and copy the latest backup files to your computer, replace original boot.img to the new one(community version). Then edit the value of boot.img in nandroid.md5 to the proper content and match your new boot.img. Finally just restore it in recovery mode.
If the wireless function isn't working after boot, you may also need to push it via adb:
adb push wlan.ko /system/lib/modules/wlan.ko
adb shell sync
(reboot again)
foxfair said:
I managed to use nandroid's restoring method and put new boot.img back without any data wipe. Here is how I did it: Make a nandroid backup first, and copy the latest backup files to your computer, replace original boot.img to the new one(community version). Then edit the value of boot.img in nandroid.md5 to the proper content and match your new boot.img. Finally just restore it in recovery mode.
Click to expand...
Click to collapse
# adb push ./boot.img /sdcard
# adb shell flash_image boot /sdcard/boot.img
I little bit more fast... (but you should make a backup before)
Poischack said:
# adb push ./boot.img /sdcard
# adb shell flash_image boot /sdcard/boot.img
I little bit more fast... (but you should make a backup before)
Click to expand...
Click to collapse
i'm on RUU 2.73.x version, for some reason fastboot and adb push won't work... anyway I just provide an alternative way.
Lox did you try to upgrade to 2.6.29?
foxfair said:
Lox did you try to upgrade to 2.6.29?
Click to expand...
Click to collapse
Clone this git if you want to play:
git://android.git.kernel.org/kernel/msm.git branch android-msm-2.6.29
You WILL need to port over some of the drivers from the Hero kernel HTC released a while back (which was 2.6.27 btw).
Dear all,
Did anyone succeed extracting kernel configuration from I9000XXJP3? Kernel version is 2.6.32.9, the vermagic is "2.6.32.9 mod_unload ARMv7"
extract-ikconfig doesn't work on it.
I succeeded extracting a zImage gzipped payload, but it seems not to contain any configuration in it (see attached).
/proc/config.gz doesn't exist, Samsung open source package (downloaded from Samsung open source site) contains only Android 2.1 Eclair or previous versions.
My target is to build tun.ko and, eventually, ext3/ext4 modules to make them working in Samsung Galaxy S I9000 with rooted I9000XXJP3.
Any idea?
Without froyo source code or a good Samsung Kernel (es. for himem capable) I think is impossible to play good with theses beta roms.
Ciao
Any news? I need tun.ko for jp3 too..
I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!
redsh said:
I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!
Click to expand...
Click to collapse
Did you use the stock linux kernel? Or the common from android.kernel.org?
I'm trying the same thing actually. Isn't there any default config for the processor that might work? I tried with the config from .29 but when loading the module it says wrong format.
try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again
Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.
bilboa1 said:
try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again
Click to expand...
Click to collapse
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..
miki4242 said:
Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.
Click to expand...
Click to collapse
Yes that would be a lot of work. Maybe its better to just wait until they release the kernel from froyo. I read that they release their opensource stuff rather fast. But just for adding a module like ext4 I don't think you need those patches, because imho they didn't touch the fs of the kernel. We just need an adaquate kernel config and adding modules should be possible.
Phlogiston said:
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..
Click to expand...
Click to collapse
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions
Yes i've set the subversion as well but without the patches from samsung its impossible it seems. We need to wait and hope that they release the froyo kernel sources soon....
bilboa1 said:
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions
Click to expand...
Click to collapse
Are you sure they set CONFIG_MODVERSIONS? It's off in the downloadable sources.
Just compare the output of `modinfo -F vermagic <yourmodule>` to `modinfo -F vermagic <modulewhichloads>` or to /proc/version .
did this get solved yet? I google'd for the tun.ko file for my i9000 using jp3 but nothing yet... if you have a proper one for the MoDaCo version here please attach it! ~
I think I saw someone's post with tun.ko for FroYo beta somewhere in these forums, I mean i9000 Android Dev. One of the guys here has found a way to compile kernel for jp* here. I am sure.
I actually found it attached somewhere in the forum and it was 1,5447 mb big I think it was... but it still didn't work for me so I presumed the kernel or something must have been wrong.
Advanced Stock ICS Kernel for Xperia SHere is a kernel based on the Stock ICS kernel with some features which come from DoomLord's GB kernel.
Features
autorooting
CWM recovery (with reboot recovery support)
init.d support (thanks DoomLord)
TUN/TAP driver
Download links
Build 17 (Fastboot)
Build 17 (CWM)
Build 16 (Fastboot)
Build 16 (CWM)
Prerequisites
An unlocked bootloader: Tuto here.
A stock ICS ROM (6.1.A.0.452 to 6.1.A.2.55). Don't expect this kernel to work with CM9/10.
How to flash
For elf files :
Read DoomLord's guide
You just have to replace kernel.elf by the name of the downloaded kernel in the flash command (eg : ics4.elf)
For zip files:
Flash the zip file from the recovery
Changelogs
Build 17 (08/12/12) :
Merge 6.1.A.2.55 kernel sources
Autodetect rom version in default.prop based on build.prop
Updated recovery, adbd and busybox (JB version)
Build 16 (01/11/12) :
Random reboot issue probably fixed (patch from CM10 kernel, thanks Kali)
Rom version increased to 6.1.A.2.50
Updated recovery, adbd and busybox (JB version)
SD card mounted by default in recovery
Vibration at boot removed, only led and backlight now
Build 15 (05/09/12) : Increase ROM version in default.prop from 6.1.A.0.452 to 6.1.A.2.45
Build 14 :
New MMC driver (from codeaurora) : it fixes issue while formatting partitions in CWM
Wifi module built from source (in the ramdisk)
Updated recovery
Disable again hardware clock
Build 13 :
Backup / Restore fixed with dedupe
Backlight enabled in CWM
Better "reboot recovery" handling in adbd / busybox and recovery
Build 12 :
Updated recovery
Hardware clock correctly saved (from CM9 kernel)
Build 11 : Go back to GCC 4.4 (fix artifacts with camera preview)
Build 10 :
Kernel built with GCC 4.6
Several autoroot fixes (Superuser app pushed just once and correctly removed in /data)
Working reboot recovery command (with adb too)
Updated su (3.1.1) and Superuser (3.1.3)
A bunch of new command included in the new busybox (ifconfig, wget, vi, and many more !)
Build 9 :
Kernel built from sources
TUN/TAP driver included (for VPN)
Build 8 : Fix mass storage in CWM
Build 7 : Fix MTP
Build 6 : Key mapping in CWM fixed
Build 5 :
New recovery built from latest CM9 sources
Fixed generation of md5sum with nandroid
Increased font size in CWM
Boot partition backup and restore
New adbd built from CM9 sources (fixed an issue with hardcoded sh path in /system)
Build 4 :
Correct su binary
Don't wait 3 sec if /cache/recovery/boot exists
Build 3 :
Leds and vibrator at startup fixed
Sources
Ramdisk sources
Kernel sources
Credits
DoomLord : many thanks to him for its kernel and all his scripts.
championswimmer and sminki for their help
FreeXperia team for their work on CM
makes it perfectly start does not make any errors
greetings and thanks
yes it boots!
(maybe you can help with my Question here )
Hey, I also have tested several times to include recovery, but withut succes, didn't get any further then a booting kernel without recovery or vibration and LED on to enter recovery but no entering recovery and kernel that doesn't boot.
Please pm me if you want to work together, I saw your kernel is from ICX team? I know nick very well so I'd would be a pleasure to work with you too
sminki said:
yes it boots!
(maybe you can help with my Question here )
Click to expand...
Click to collapse
for this question and any other other question similar to this
head here
http://forum.xda-developers.com/showthread.php?t=1659584
it has menu driven process to extract and repack kernel.elf (ramdisk also can be extracted and packed )
Welcome Champ, good to see you mate.
I will leave the thread here as knowing you, you will have a kernel ready for us in a few hours.:fingers-crossed:
thanks for the test guys... so now i'm diving into including recovery....
good to know i could pull off kernel.elf editing in my first attempt lol
@colossus if not in hours, then definitely within 1 or 2 days
EDIT :
can someone send me the kernel.elf from FXP122 cm9 ??
will save me the time to download the whole ROM
This is sweet, good job!!
john9 said:
This is sweet, good job!!
Click to expand...
Click to collapse
Only a few files to edit now
We'll keep you updated
Sent from my LT26i using XDA
championswimmer said:
btw if anyone wishes to do this before me,
this diffstats should help you
https://github.com/championswimmer/xps-ramdisk/commit/a61969aefca00ce3a6e4e112e97403fb6f0c79e9
it shows how doomlord added recovery to gb kernel..
Click to expand...
Click to collapse
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
fNOOB said:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
Click to expand...
Click to collapse
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
noob.fl said:
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
Click to expand...
Click to collapse
Cheers mate
sminki said:
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Click to expand...
Click to collapse
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
championswimmer said:
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
Click to expand...
Click to collapse
cool, i was only making a bad joke, we all know DooM cares
sminki said:
cool, i was only making a bad joke, we all know DooM cares
Click to expand...
Click to collapse
lol.. ok
and i'll bring you some unicorns soon
championswimmer said:
lol.. ok
and i'll bring you some unicorns soon
Click to expand...
Click to collapse
I can't wait! :victory:
so this kernel has the ro.secure property in default.prop set to 0??
Tnaks mate for your job!
tested right now the test version and the sony logo fades and reboots
can you plug it into a pc and run a logcat from command prompt and give me the output of any comes??
In this post, I would like to explain what kexec-hardboot patch is.
@kernel developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows me to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems. Thank you.
What is kexec?
It is syscall of Linux kernel, which allows you to boot another Linux kernel without restarting the device - "Linux boots itself". The functionality is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot. It is fairly known thing, so more info at wikipedia and man kexec.
Standard kexec call unfortunatelly does not work on Nexus 4. It freezes somewhere, and it is very difficult to find out where - probably some of the drivers are not shut down/re-initialized properly, it is a commong thing among Android devices, which is why kexec-hardboot was made.
What is the difference between normal and hardboot exec?
Kexec-hardboot patch adds a real device restart to that process, so that all the drivers can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and kernel from boot partition immediately jumps to the one which was stored to RAM before reboot.
Unlike grouper's kexec-hardboot patch, this one only requires the host kernel to be patched. This is one of the improvements I made, and I think it is pretty significant.
To sumarize the process:
kexec --load-hardboot.... is called and kernel it loaded into RAM.
kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.
After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.
Kexecd' kernel starts and boots.
For more info, read the original thread.
Patches:
Kernel patch: https://gist.github.com/Tasssadar/7833796, 4.4 AOSP kernel repo
This is the kernel patch. Only the host kernel needs to be patched.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_PROC_DEVICETREE=y
CONFIG_ATAGS_PROC=n # This one is turned on automatically, but it is not needed, so you can disable it.
All these options must be enabled.
Userspace kexec binary: https://github.com/Tasssadar/kexec-tools
I had to change some things in kexec userspace binary because of some kernel bugs, complete description is in that repository. You can get statically built binary at https://github.com/Tasssadar/multirom/blob/master/install_zip/prebuilt-installer/multirom/kexec
Usage:
Once you have the kernel patches and kexec userspace binary in place, just run following command to boot into new kernel:
Code:
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x20000000 --command-line="$(cat /proc/cmdline)" --dtb
kexec -e
Note the command line parameter - cmdline from bootloader is not added automatically, you have to put it there by yourself.
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices, one of them is Asus Transformer TF201 - I used patch from TF201 and modified it a bit (basically just changed few SoC specific constants). People at #ubuntu-arm helped me out with that, thanks.
For hammerhead, I've improved the patch a bit - only the host needs to be patched now and I've added support for DTB.
Merged, thanks again for the awesome work @Tasssadar!
Good deal.My day is getting better.
@show-p1984 would love to see this in bricked kernel too! ?
@neobuddy89 did you see this?
Sent from Nexus 5 on Slimkat
thanks for the hard work.. thats awesome.
AndroidSlave said:
@neobuddy89 did you see this?
Sent from Nexus 5 on Slimkat
Click to expand...
Click to collapse
Yeah, I saw this.
neobuddy89 said:
Yeah, I saw this.
Click to expand...
Click to collapse
I asked that 6 months ago
Sent from my Nexus 5 using Tapatalk
awesome work bro...
much needed..
AndroidSlave said:
I asked that 6 months ago
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I know and I saw that days back..
Enough of OT. :fingers-crossed:
Help with applying the patch
Okay so I have my aosp kernel made. I have my working directory too. Can you just guide me on how do I apply this partch to it?
Is it possible to add that patch from a on the fly flashable zip ?
@Anoopnk since the patch is for the kernel(zImage) its not possible to patch it like that. Or you have to compile the kernel or you need to ask your kernel dev friendly or he can include it in his kernel.
Hello, first I'd like to apologize for dredging up an old thread. Second, I am attempting to build a CM13+kali+kexec compatible kernel, with extra wifi drivers as the base kernel doesnt support my wifi card. Based on that goal, I have a multi-part question for the OP, or anyone else with the know-how to assist me in my quest.
1)Is there a source available for your kernel_kexec_hammerhead_cm13-01-2c39db662.zip listed on the multirom page for nexus 5? I'm attempting to build a new kernel, for kali+CM13+multirom, and your android_kernel_google_msm git only has branches going up to CM12. It would be far easier for me to start with a 'clean' CM13+kexec source then trying to patch myself as per question #2
2) I've attempted to patch a plain old hammerhead_defconfig from CM13 git, however I believe I am doing so wrong. I have managed to compile kexec-tools and aquired the hammerhead 3.4.x patch. Now am I supposed to patch my produced zImage-dtb AFTER build, running the patch from the kexec-tools folder and against the zImage-dtb? Is it something like 'KEXEC.patch -p1 < zimage-dtb'
Any clarification on the use of the kexec-tools patch, or simply a link to github source of a 'clean' CM13 kernel with the kexec patch already applied, would be incredibly helpfull on my journey down the rabbit hole
~EDIT~
Ok so I've managed to figure out the patch and feel like a dumbass. For anyone else looking to get into kernel dev, and wanting to use the kexec patch, heres the basics:
1- run patch within your kernel source directory
2-ensure that the config settings in OP are set (I had to add them to my source by hand as they werent there)
3-when zipping up your kernel, add the sbin and lib/kexec-tools folders from the kexec-tools source build, and be sure your updater-script / updater-binary is set to move these folders into /sbin and /lib respectively.
4-Flash and enjoy Kexec! (check with multirom manager)
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r27. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
2015/04/01
please visit http://forum.xda-developers.com/showpost.php?p=59827552&postcount=8 to see more information:
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108/.157 or any ROM based on it.
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
sharonliu said:
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r25. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108 or any ROM based on it
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
Click to expand...
Click to collapse
cocafe mentioned that the wifi modules has to be original from stock ROM, so i replaced them before flashing the kernel, but wifi does not turn on.
thank you for reporting this problem, it should be resolved next release.
Nice to see another stock based kernel around!
Only .108 or also .157?
Schlengge said:
Nice to see another stock based kernel around!
Only .108 or also .157?
Click to expand...
Click to collapse
from cocafe´s post:
ROM: Stock KitKat 4.4.4 14.4.A.0.108 +
Click to expand...
Click to collapse
so imho for .157 too
sharonliu said:
thank you for reporting this problem, it should be resolved next release.
Click to expand...
Click to collapse
i think this solves the problem: LINK
moonryder said:
i think this solves the problem: LINK
Click to expand...
Click to collapse
Thanks for the information. Just like DooMKernel, my goal is no need to compile wlan module. If I am not luck, I will build the wlan module in this weekend.
Changelog :
wlan is working
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Insturaction:
If you want back to stock kernel, remember reboot to recovery and flash stock wife modules.
sharonliu said:
...flash stock wife modules.
Click to expand...
Click to collapse
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
moonryder said:
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
Click to expand...
Click to collapse
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
sharonliu said:
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
Click to expand...
Click to collapse
ok
btw flashed new build from today and wifi works like a charm.
thx
Thanks for this kernel
The only thing I noticed is that the notification light turns white when the battery is full
Normal it's green
Don't know if it's I bug but I noticed it
It's not a bug. Cocafe made it so the led will notify you of the real eoc. You can change the led color though here I believe "/sys/kernel/qpnp-charger/eoc_led"
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
moonryder said:
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
Click to expand...
Click to collapse
get terminal emulator from the play store and type it in there
or use adb shell
adb shell
su
Click to expand...
Click to collapse
it should work if you type these scripts. In my opinion, DoomKernel is the best custom kernel, bu nice to see another stock based kernel around.
sharonliu said:
...DoomKernel is the best custom kernel....
Click to expand...
Click to collapse
you are so right bro
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
a1b2c3901 said:
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
Click to expand...
Click to collapse
why do you use exFAT format?
Do you have files > 4GB in use?
moonryder said:
why do you use exFAT format?
Do you have files > 4GB in use?
Click to expand...
Click to collapse
Sometimes I will watch movie in the journeys, and that files may be oversize.
a1b2c3901 said:
Sometimes I will watch movie in the journeys, and that files may be oversize.
Click to expand...
Click to collapse
get "MLUSB Mounter" from the play store, you can use the USB hard drive (formatted NTFS, exFAT).