Related
Hi,
I am trying to extract the kernel from mmcblk0p20 using unpack-bootimg.pl
from this post: http://forum.xda-developers.com/showpost.php?p=2885020&postcount=1
I can get a valid ramdisk out of it but the kernel is not a gz file as it should be.
Any hint?
Etn40ff said:
Hi,
I am trying to extract the kernel from mmcblk0p20 using unpack-bootimg.pl
from this post: http://forum.xda-developers.com/showpost.php?p=2885020&postcount=1
I can get a valid ramdisk out of it but the kernel is not a gz file as it should be.
Any hint?
Click to expand...
Click to collapse
The kernel is not exactly a "gzipped" file because the first part of it has bootloader code that provides a mechanism to uncompress the remaining part of the kernel (which uses a form of gzip provided by a micro zlib).
More importantly, what are you trying to accomplish? The "kernel" image that comes from split_bootimg.pl (or such) is the actual file you use to re-pack, etc. Unless of course you're trying to decompile the kernel for reverse engineering purposes, but that would be pointless and you wouldn't be asking this question if that were the case.
If you're trying to get the kernel config, use extract-ikconfig from the 'scripts' directory in the Linux source tree. You have to invoke it by cd'ing into the Linux source directory and doing:
Code:
./scripts/extract-ikconfig /path/to/your/kernel-file &> /where/you/want/the/resulting-config
(you can't cd into 'scripts' and have it work).
Enjoy.
As you say unpacking the kernel to get the configuration is pointless: I could get it on htcdev without any effort.
I just had a boring night and I tried to kill it repacking my own flavour of android.
I was not able to make it boot so I started guessing which problem I was having; the kernel seemed a reasonable candidate (I was convinced that I was stripping the header away from it when unpacking)
how could you acquire that kernel? last time I checked there was no source?
You need the kernel source before a kernel can be made. Thats the sucky part.
Sent from my myTouch_4G_Slide using xda premium
Undeadk9 said:
You need the kernel source before a kernel can be made. Thats the sucky part.
Click to expand...
Click to collapse
Eh? No. A kernel exists, just in binary form. HTC has yet to release the source code, but unless you plan to modify parts of it, there's not much point.
nbetcher said:
Eh? No. A kernel exists, just in binary form. HTC has yet to release the source code, but unless you plan to modify parts of it, there's not much point.
Click to expand...
Click to collapse
A kernel source is no problem, I got it from android github.
The issue is the mods htc made and added, and the tools around it they used to compile.
I would like to compile my own, to optimize (did it on linux too).
If anyone can explain me simple how to use the binary kernel, I am happy too for now, if that makes me able to compile CM7
Anyone? Can't be too hard since a lot of folks pulled it of?
I have a lot of technical experience, just need some android specific info
I know nothing bout kernels. They scare me. I'll stick to ROM making.
Sent from my MyTouch 4G Slide using xda premium
OpenMinded said:
A kernel source is no problem, I got it from android github.
The issue is the mods htc made and added, and the tools around it they used to compile.
I would like to compile my own, to optimize (did it on linux too).
If anyone can explain me simple how to use the binary kernel, I am happy too for now, if that makes me able to compile CM7
Click to expand...
Click to collapse
It's not quite that simple. They don't just 'mod' the kernel, they add device support to it. The upstream Linux kernel does not support the latest and greatest Qualcomm-based devices, so HTC uses their own repository based on Codeaurora (http://www.codeaurora.org) which is downstream from Qualcomm. Confused yet?
Point being: Linux will not run properly on our device until we have either the HTC Sensation source, Doubleshot source, or someone sifts through and pieces together all of the various sources needed from Codeaurora.
To use the binary form, just use boot.img from our device's HBOOT image.
nbetcher said:
It's not quite that simple. They don't just 'mod' the kernel, they add device support to it. The upstream Linux kernel does not support the latest and greatest Qualcomm-based devices, so HTC uses their own repository based on Codeaurora (http://www.codeaurora.org) which is downstream from Qualcomm. Confused yet?
Point being: Linux will not run properly on our device until we have either the HTC Sensation source, Doubleshot source, or someone sifts through and pieces together all of the various sources needed from Codeaurora.
To use the binary form, just use boot.img from our device's HBOOT image.
Click to expand...
Click to collapse
Thank you for the explanation.
I have been compiling kernels on linux, I know we need drivers and that HTC patches the kernel. I did not know about codeaurora, thanks .
The HTC Sensation kernel source is on the HTC website:
http://developer.htc.com
I was wondering undead, how do you compile other ROMS? You just strip what is not needed? I thought you know how tot strip just the kernel, since you made a senseless rom.
I will try using the boot.img, thanks.
Does that mean porting a Sense rom would only require swapping the boot.img from another Sense 2.0/3.0 rom?
Thanks for the info
LOL. No its still the sense base and uses the stock boot.img from the stock ROM. It's still HTC at its core. Like I said I know 0 'zero' about kernels.
Sent from my MyTouch 4G Slide using xda premium
Undeadk9 said:
LOL. No its still the sense base and uses the stock boot.img from the stock ROM. It's still HTC at its core. Like I said I know 0 'zero' about kernels.
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
point taken . I think I just made a working zip containing only the stock kernel.
If I have time, I will try to put that kernel in a AOSP rom for the Sensation and see what that does. may take some time...
does any1 know how to mod the device checking of a rom?
i get an error 7, found it is because of the device check.
I modded the update script and binary from the Senation Alpha cm7 and got that error, which seems to point to a different model of phone.
I would like to work around it and see if the kernel works with cm7
AniDroid-Hardened-TF101 Kernel
Short Kernel information:
AniDroid-Hardened Kernel is the first Hardened kernel for Android that uses GRSecurity subsystem to provide different useful Security functionality.
AniDroid-Hardened Kernel now is in early stage of developing but it's almost ready for using and testing on Asus Transformer TF101 and Google (Samsung) Nexus S devices
Provided Features:
Linux Kernel version 2.6.39.4
GRSecurity version 2.2.2 with different security features enabled by default (see GRSecurity Feature List for details)
EXT4, NTFS, CIFS support
init.d support
Compatible with any OTA-based and AOSP ICS Roms
1024 Kb ReadAhead support
Automatic Process Group Scheduling
-fstack-protector buffer overflow detection
GRSecurity Feature List:
Kernel Memory Protection (restrict read/write access to /dev/kmem, /dev/mem, and /dev/port)
Active Exploits Protection (deter exploit bruteforcing, active kernel exploit response)
Role Based Access Control (RBAC)
Filesystem Advanced Protection (including advanced security for applications running in CHROOT environment)
Full Kernel Auditing (event logging for many kernel events)
Executable Protection (deter ptrace-based process snooping)
Network Protection (TCP/UDP blackhole and LAST_ACK DoS prevention)
Managing support via Sysctl Interface
CPU Frequence Scaling Governors:
Ondemand (Default)
Interactive
Conservative
Powersave
Performance
IO Schedulers:
CFQ (Default)
Noop
Deadline (tweaked for flash devices)
Simple IO (SIO)
Links:
Current Kernel Binaries:
AniDroid-Hardened-TF101-Alpha1.zip
Other Kernel Binaries:
Old binaries on SourceForge
Kernel Source:
Will be available on GitHub soon..
Changelogs and issues info:
Alpha 1 known issues:
BCM4329 WiFi kernel module temporarely doesn't work
SU is temporarely cause "Permission denied"
WARNING!!!
AniDroid-Hardened-TF101 Kernel is still need testing!
So, you can flash and use this kernel at your oun risk!
Thanks to msticninja, guevor, eugene373, koush, ezekeel, supercurio, morfic, franciscofranco, sztupy, reddv1, byeonggonlee!!!
Great to see another kernel option. Awesome work, mate!
I'll give it a try.
hi!great to see new kernelz every week!after reading all the features in the nexus 3ad,i wonder if you'll put some of them un future in this tf's build...some of them i use every day on smartphones and are very Usefull..like touchwake,liveOC,BLX , fast charge and others..(fast charge especially)glad to test this kernel now,hoping that wifi works,anyway thanks for the hard work and keep it up in future release!i'll report how it goes...
sert00 said:
hi!great to see new kernelz every week!after reading all the features in the nexus 3ad,i wonder if you'll put some of them un future in this tf's build...some of them i use every day on smartphones and are very Usefull..like touchwake,liveOC,BLX , fast charge and others..(fast charge especially)glad to test this kernel now,hoping that wifi works,anyway thanks for the hard work and keep it up in future release!i'll report how it goes...
Click to expand...
Click to collapse
As far as I know, fast charge from a computer USB port isn't possible on the tf101 because it requires 12v to go into fast charge mode where a normal USB port only provides 5v.
Congrats on getting the kernel compiled with your changes. I'll post some fixes tomorrow that you might want to pull to your git. I have to be honest though, I don't really see the point of grsecurity on android. Do people actually get hacked?
noted but will flash when somebody got the balls to try...
Sent from my Transformer TF101 using xda premium
j3tt3 said:
noted but will flash when somebody got the balls to try...
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Never mind the balls, I don't see the point of flashing a kernel where wifi and SU (both quite critical in my opinion) don't work.
Basically, su won't work with GRSec because of the RBAC model. Another way needs to be found
Sent from my LT26i using XDA
K900 said:
Basically, su won't work with GRSec because of the RBAC model. Another way needs to be found
Sent from my LT26i using XDA
Click to expand...
Click to collapse
SU will work as privileged user can be allowed to run privileged operations useful for such apps as Titanium Backup and so on ..it's not GRSec issue - vanilla asus source have tha same issue for me.. it's either compiler or ramdisk problem..
novic_dev said:
SU will work as privileged user can be allowed to run privileged operations useful for such apps as Titanium Backup and so on ..it's not GRSec issue - vanilla asus source have tha same issue for me.. it's either compiler or ramdisk problem..
Click to expand...
Click to collapse
I meant that you need to either allow switching to root, which defeats the whole purpose of GRSec or use its own access controls, which needs to be done in apps.
Sent from my LT26i using XDA
K900 said:
I meant that you need to either allow switching to root, which defeats the whole purpose of GRSec or use its own access controls, which needs to be done in apps.
Sent from my LT26i using XDA
Click to expand...
Click to collapse
It will be an App
Sent from my Nexus S using xda premium
Does one exist for this device?
Sent from my SGH-T839 using Tapatalk
leolawliet said:
Does one exist for this device?
Sent from my SGH-T839 using Tapatalk
Click to expand...
Click to collapse
Hahahaha....sorry had to laugh for a moment. But seriously no there is no kernel for sk4g that has loop support.
Actually this kernel does have loop support (Bali), but the busybox binary included in the ramdisk isn't compatible necessarily with the script used to boot ubuntu from the linux-on-android installer.
sduvick said:
Actually this kernel does have loop support (Bali), but the busybox binary included in the ramdisk isn't compatible necessarily with the script used to boot ubuntu from the linux-on-android installer.
Click to expand...
Click to collapse
That's a shame, I was hoping I could try out Linux on the sk4g
Sent from my LG-VM701 running Mobster Rom via Tapatalk
1. Motivation/overview
This is a kernel for the 2012 Nexus 7 (grouper/tilapia) which sticks as closely as possible to the stock/released kernel sources, while incorporating the features I want from other popular alternative kernels. I've built it because my Nexus 7 3G (tilapia) has trouble with all of the non-stock kernels I've tried -- something causing USB resets in a tight loop. I rebuilt the stock kernel and started adding my favorite features in order to rule out what was causing the problem, but ended up with a kernel I preferred for day-to-day use.
You might like it, too.
Note that there is very little original content in this kernel: see the credits below and the github repository for the sources of the included features.
2. Features
IO Schedulers
bfq
row
SIO
CPU Governors
smartmax
wheatley
Misc
Build with -Os (optimize for size)
GPU overclock
Experimental: remove baseband_xmm_power wakelock
f2fs driver (see note in second post)
ntfs r/w (see note in second post)
CPU voltage control
Mount slave namespace workaround
CPU overclock (against my better judgement).
3. Instructions
This kernel is intended primarily for use with the stock ROM. The first releases (mr1 and a20) were built with a stock ramdisk, and will generally not work on other ROMs. Later releases use an AnyKernel updater and may work on other ROMs. I am only able/willing to test on stock, however, so non-stock users, use at your own risk (even more than usual).
To install, boot into your custom recovery of choice and install one of the zips below. Or use Flashify. Be sure to make a backup with your recovery first.
4. Warning and disclaimer
I am not responsible for any harm caused to you, your tablet, or the integrity of the space-time continuum by this kernel. In the words of the GNU Public License:
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
5. Downloads
Milestone releases:
mr1: carcosa-kernel-mr1.zip
Alpha releases:
a20: carcosa-kernel-a20.zip
Includes experimental patch removing baseband_xmm_power wakelock.
a22: carcosa-a22-anykernel.zip
Includes changes to governor defaults, ntfs r/w support, and the f2fs driver.
a23: carcosa-a23-anykernel.zip
Includes voltage control (undervolting) interface.
a25: carcosa-kernel-a25.zip carcosa-a25-anykernel.zip
Includes mount slave namespace workaround, CPU overclocking (against my better judgement)
a27: carcosa-a27-anykernel.zip
4.4.3 update
a28: carcosa-a28-anykernel.zip
Remove baseband_xmm_power wakelock again, rather than making it time out.
a29: carcosa-a29-anykernel.zip
Add configurable baseband_xmm_power wakelock timeout
a33: carcosa-a33-lp-anykernel.zip
Lollipop update; adds SIO IO scheduler.
a35: carcosa-a35-lp-anykernel.zip
Lollipop 5.1 update (still works with 5.0.2). Adds hardware acceleration for kernel encryption routines.
6. Source
Sources are on github, which is also your best source for changelogs.
7. Credits
This kernel contains precious little original work -- it builds on the stock kernel release and applies cherry-picked patches from various sources, principally M-Kernel (Metallice) Franco-kernel (Francisco Franco), and Oxydo (Sgt. Meow), but also Faux123, Ezekeel, Maxwen, and many others. My main contributions have been picking the things I wanted, and resolving the occasional hairy merge. I have attempted to maintain the original authorship information in my git logs as much as possible; I apologize for any cases where the attribution of a particular patch has been lost.
Notes
F2FS support
While this kernel (from a22 on) includes the f2fs driver, it does not include any of the ramdisk or init tweaks that you would need to use f2fs. This is because I am not in a position to test f2fs myself. That said, the a22 (and later) kernel installer will not disturb any changes you have already made to your ramdisk or ROM to support f2fs, so if you have already got f2fs working on your device, it should continue to work after installing this kernel. Don't forget to do a nand backup in your recovery before installing, though. Seriously.
NTFS R/W support
This kernel (from a22 on) includes RW support for NTFS. However, in KitKat, NTFS USB drives mounted with StickMount are not writable due to SELinux policy. To write to an NTFS USB drive, you need to (from a root shell) 'setenforce off', then 'setenforce on' when you're done using it. I do not recommend that you put SELinux in permissive mode permanently. It's there for a reason, and this is just a workaround for a policy error in KitKat. The SELinux SetEnforce Toggle app is a convenient way to turn it off and on for this.
Mount slave namespace workaround
Android apps that mount filesystems (e.g. CIFS, Lil'Debi's loopback fs), mount them in a private namespace that is not shared with other apps (as explained by mkasick). There is a rom-based workaround applied in CM-based roms, and probably many others, but not in stock. Instead, I am applying his kernel/ramdisk based workaround. If you are on stock and need this workaround, do not use the anykernel build; use the one with the full disk image.
Configurable baseband_xmm_power wakelock timeout
This is based on work by Sgt. Meow, with some tweaks. It is controlled by the module param /sys/modules/baseband_xmm_power/bb_timeout, which defaults to 10, and represents the time, in 10ths of a second, that the baseband_xmm_power wakelock should be acquired for before timing out. 0 will disable the wakelock completely as in earlier versions of carcosa-kernel. These semantics are not the same as those for the same parameter in Oxydo, so be aware.
-------------------------------------------------------------------------------------------------------
Camilla: You, sir, should unmask.
Stranger: Indeed?
Cassilda: Indeed, it's time. We all have laid aside disguise but you.
Stranger: I wear no mask.
Camilla: (Terrified, aside to Cassilda) No mask? No mask!
– from Act 1, Scene 2 of The King In Yellow
Kernel rocks! Thanks!
bjcrj said:
Kernel rocks! Thanks!
Click to expand...
Click to collapse
You're welcome. Are you using the milestone release or the alpha? And are you on grouper or tilapia? I want to know if the baseband_xmm_power hack is being tested by anyone besides me.
jfmcbrayer said:
You're welcome. Are you using the milestone release or the alpha? And are you on grouper or tilapia? I want to know if the baseband_xmm_power hack is being tested by anyone besides me.
Click to expand...
Click to collapse
I am using the alpha. I run a grouper rom on tilapia and didn't have any wake lock issues.
Hi, I'm using the newest CM Release and after flashing the kernel i got a com.android.phone has stopped error. I cleared the cache and the dalvik before restart.
gremlin89 said:
Hi, I'm using the newest CM Release and after flashing the kernel i got a com.android.phone has stopped error. I cleared the cache and the dalvik before restart.
Click to expand...
Click to collapse
The boot.img in the zips I've provided us built with a stock ramdisk, and CM needs its own ramdisk. Perhaps I could build an AnyKernel zip for non stock users.
bjcrj said:
Kernel rocks! Thanks!
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Nexus 7 using xda premium
Just flashed mr1 on bshiznit’s stock ROM earlier today. So far it's running nice and smooth. Nice work!
Sent from my Nexus 7 using Tapatalk
pjcanales said:
What ROM are you using?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Aospal
jfmcbrayer said:
The boot.img in the zips I've provided us built with a stock ramdisk, and CM needs its own ramdisk. Perhaps I could build an AnyKernel zip for non stock users.
Click to expand...
Click to collapse
Oh that would be really great. Is it easy to build such a rom?
gremlin89 said:
Oh that would be really great. Is it easy to build such a rom?
Click to expand...
Click to collapse
Not a ROM, just an updater zip. In principle, it should be easy. But somehow, I've never got it to work.
Thank you very much for your work! Without your kernel my battery was empty within one or two days due to the annoying wakelocks, now my N7 runs since 7 days and I still have 40%! Awesome!
sengst said:
Thank you very much for your work! Without your kernel my battery was empty within one or two days due to the annoying wakelocks, now my N7 runs since 7 days and I still have 40%! Awesome!
Click to expand...
Click to collapse
I'm glad to hear it. Am I correct in assuming that you have a tilapia device, and are running the alpha version of the kernel?
Just a question
What is the difference between Milestone and Alpha ? btw i am using nexus 7 wi-fi only model
jfmcbrayer said:
I'm glad to hear it. Am I correct in assuming that you have a tilapia device, and are running the alpha version of the kernel?
Click to expand...
Click to collapse
You are right: tilapia aosp and your a20 kernel.
ispukan said:
What is the difference between Milestone and Alpha ? btw i am using nexus 7 wi-fi only model
Click to expand...
Click to collapse
Currently, the difference is that the alpha disables the baseband_xmm_power wakelock, which some people perceive to be a major source of idle power drain on the 3g (tilapia) model.
jfmcbrayer said:
Currently, the difference is that the alpha disables the baseband_xmm_power wakelock, which some people perceive to be a major source of idle power drain on the 3g (tilapia) model.
Click to expand...
Click to collapse
So i can install what ever i want there is now difference for wifi only model ?
ispukan said:
So i can install what ever i want there is now difference for wifi only model ?
Click to expand...
Click to collapse
Right; you can run either on a Wi-Fi only (grouper) device, but the changes are only relevant to tilapia.
Hi, can I use this kernel on PA 4.1 beta on my tilapia? Currently using the Franco r77 kernel and still get massive baseband wakelocks! If this kernel doesn't work on the said ROM, how do I revert to the stock kernel? Using the FKA app and have a backup of stock kernel. Thanks
Sent from my Nexus 7 using XDA Premium HD app
Note: Tested on stock 4.2 kernel only.
CAF may require some specific changes which I may do in future.
Q. What is kexec?
kexec is feature of Linux that allows it to live boot a new kernel over current one. This is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot.
Q. What is kexec hardboot?
Kexec-hardboot does kexec with a full reboot so that all the hardware can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and loads guest kernel from RAM.
Q. What is the use?
kexec hardboot is an essential component of multiboot solutions like multirom. Also it may be used for testing a guest kernel without having to write flash emmc.
Q. More details?
here and here
Defconfig::
Code:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_KEXEC_TAOSHAN=y
CONFIG_ATAGS_PROC=y
CONFIG_CRASH_DUMP=y
Usage:
Code:
kexec --load-hardboot zImage --initrd=ramdisk.img --mem-min=0x85000000 --mem-max=0x87ffffff --command-line="console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3"
kexec -e
or use this script (Modify zImage and initrd.img location: default is /sdcard/kexec/*)
Q. How to determine kexec parameters?
Read this first.
These are highly device specific:
Here's the cat /proc/iomem for taoshan:
Code:
80200000-87ffffff : System RAM
80208000-80ee60d3 : Kernel code
81004000-81306de3 : Kernel data
88100000-88dfffff : System RAM
8ec00000-8effffff : System RAM
...
KEXEC_HB_PAGE_ADDR: 0x88000000
Logic: Address where 1st block of SYSTEM_RAM ends - size of ram_console (we don't have ram_console in stock kernel so 0 here)
Result: 0x87ffffff bits = 0x88000000 bits = ~285 megabytes
MR_KEXEC_MEM_MIN: 0x85000000
Logic: This is the where zImage and initrd.img are loaded in RAM. It has to be in the 285 MB of System RAM.
As you can see first block of SYSTEM RAM spans from 0x80200000-0x87ffffff.
Result: 0x85000000 bits = ~279 megabytes
Links:
Kernel Patch
Kexec Binary
Kernel Source
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices.
My patch is based on the one by @Tasssadar here and by @alvinhochun here.
My special thanks to @alvinhochun for helping me in debugging this hack.
Never expected kexec hardboot for XL Thanks @rachitrawat , With this Multi ROM is not far from being a reality.
I believe CAF won't require any changes as the board sources are same as stock JB. Will test it and will let ya know.
{except for the cmdline ofc}
edit: derp relocate_kernel. Changes+testing required
i have maybe strange idea
if this success and we have multi boot
We will have chance to have KitKat ROM and jb ROM
Or we we will have only two KitKat Roms only or two jb Roms only
i am talking about kernel support both jb and KitKat here with that future
Thanks a lot for your work
Sent from my C2105 using XDA Premium 4 mobile app
Correct me....
Correct me if my idea is a bad one... but with this is there any chance to change kernels on Locked BL? This could be some kind of trick to load a kernel for CM or KK, just tell me =)
david makarove said:
i have maybe strange idea
if this success and we have multi boot
We will have chance to have KitKat ROM and jb ROM
Or we we will have only two KitKat Roms only or two jb Roms only
i am talking about kernel support both jb and KitKat here with that future
Thanks a lot for your work
Sent from my C2105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As of an update by Tasssadar, only host kernel needs to be patched. So if you have a patched kernel, you can run any (patched or unpatched) kernel over it. In a nutshell, this means only the kernel you're running with your primary rom needs to have this patch.
ezzekl said:
Correct me if my idea is a bad one... but with this is there any chance to change kernels on Locked BL? This could be some kind of trick to load a kernel for CM or KK, just tell me =)
Click to expand...
Click to collapse
I'm afraid this requires an unlocked bootloader since stock kernels don't have support for hardbooting kernels. Although I've heard of a workaround by insmoding a module.ko (z1 forums), I'm not convinced of its functionality yet. I hope I'm clear.
rachitrawat said:
As of an update by Tasssadar, only host kernel needs to be patched. So if you have a patched kernel, you can run any (patched or unpatched) kernel over it. In a nutshell, this means only the kernel you're running with your primary rom needs to have this patch.
I'm afraid this requires an unlocked bootloader since stock kernels don't have support for hardbooting kernels. Although I've heard of a workaround by insmoding a module.ko (z1 forums), I'm not convinced of its functionality yet. I hope I'm clear.
Click to expand...
Click to collapse
So, lets not kill the hope of modding LBL's hahaha. Good luck bro! Ty for the answer.
ezzekl said:
Correct me if my idea is a bad one... but with this is there any chance to change kernels on Locked BL? This could be some kind of trick to load a kernel for CM or KK, just tell me =)
Click to expand...
Click to collapse
On Locked Bootloader we need a ramdisk hijack. Here is what dh.harald said abou that: "I try to implement 2nd-init method (Motorola Milestone/Defy/etc) to hijack ramdisk. With this method, we can change stock ramdisk, and we can boot CM with stock kernel... "
And there is a link to that thread: http://forum.xda-developers.com/showthread.php?t=2653896
Is it possible to make CM work on locked bootloader (see the Xperia SP thread...), but I think it will only work with CM10.1 or CM10 'cause it is JellyBean 4.1 or 4.2. If someone willing to work on it..... I really appreciate it and I'll do the test!
Sorry for the offtopic!
dywerd said:
On Locked Bootloader we need a ramdisk hijack. Here is what dh.harald said abou that: "I try to implement 2nd-init method (Motorola Milestone/Defy/etc) to hijack ramdisk. With this method, we can change stock ramdisk, and we can boot CM with stock kernel... "
And there is a link to that thread: http://forum.xda-developers.com/showthread.php?t=2653896
Is it possible to make CM work on locked bootloader (see the Xperia SP thread...), but I think it will only work with CM10.1 or CM10 'cause it is JellyBean 4.1 or 4.2. If someone willing to work on it..... I really appreciate it and I'll do the test!
Sorry for the offtopic!
Click to expand...
Click to collapse
+1 on that, I will do the test too if needed.
Just applied it to my kernel. Seems like i still have a lot of problems with this lol
I'm developing JB kernel too (still learning, though)
Any chances that multirom with kexec hardboot coming anytime?
Sent from my C2104 using XDA Free mobile app
No news? :_(