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? :_(
Related
AnyKernel zips will only replace the kernel in your boot.img.
To define a boot.img:
Kernel(zImage) + ramdisk(root file system + init scripts) = boot.img
Where AnyKernel came from:
While searching for different kernels for my Motorola Droid I stumbled on a great idea implemented by Koush. Basically it will split the boot.img from recovery while your phone is running then replace the kernel and make a new boot.img and flash it along with the correct modules for the kernel.
I figured I would implement it on the CDMA Hero and it worked out.
This will work on any rooted rom with a custom recovery running Sense UI including the stock rom.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Here are the undervolted and overclocked kernels for Sense ROMS
These kernels are built from the HTC heroc-2.6.29-bc0d2ccf source with toasts overclock patch modified by darchstar/Decad3nce to include undervolt.
The git repo for this is @ http://github.com/zenulator/htc-heroc-2.6.29-bc0d2cff
The GPL license can be read @ http://www.gnu.org/licenses/gpl.html
ZenKernel-HTC-08122010 no perf lock
It has perf lock disabled to allow full overclocking with out the need use setcpu to disable perf lock. The clock speeds will stay at what ever the target rom uses unless you running a rom with no overclock built in. If so it will scale from 19mhz to 768mhz.
Download
ZenKernel-HTC-08122010 perf lock
Same as above but with perf lock enabled. It will run at stock values on any sense Rom until you use setcpu. To overclock it you will need to set setcpu to autodetect and then disable perf lock inside setcpu.
Download
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
StockVoltage Overclocked Kernel:
This kernel is built from the same source as the rest except the voltages were changed to stock values. It will max out at 691 and the governor is set to performance.
Download
Setcpu is free for xda memebers and can be found here:
http://forum.xda-developers.com/showpost.php?p=3638937&postcount=1
Instructions:
Download the update and copy it to the root of your sdcard.
Reboot into recovery.
Nandroid (just in case you want to go back)
Flash the update
Reboot
Check Settings > About phone > Software information > Kernel version
_____________________________________________________________________________
If you wish to modify this with another kernel just extract the update and replace the zImage in the kernel directory with the one you want and replace the corresponding modules. Then rezip and resign and flash. It will work on any 2.1 sense rom regardless of boot.img.
Damn good work zenulator I am downloading it now and will test thoroughly tomorrow and see how it go's.
Thanks for the hard work.
Works great, using it with your beta ROM. Lock screen lag is gone
I got used to it so I barely noticed it... but now it seems a lot faster
I know you just started this and it says for sense. But I gotta ask is there anyway that this will work with froyo? I'm not a fan of overclock roms because of the lag when you push the menu key till when you screen is actually ready to go. And this gives me hope
of having a kernel that doesn't do that
thatguythatdid said:
I know you just started this and it says for sense. But I gotta ask is there anyway that this will work with froyo? I'm not a fan of overclock roms because of the lag when you push the menu key till when you screen is actually ready to go. And this gives me hope
of having a kernel that doesn't do that
Click to expand...
Click to collapse
Yes it will work for froyo if you modify it and put in the correct zImage (kernel). It won't work with the update I posted since it's made for Sense roms and uses HTC's Synaptics driver which isn't compatible with AOSP 2.2 Froyo/Cyanogenmod.
If you want a AOSP kernel with no overclock and no ability to overclock at all then I can do that but not for a couple days. If you ask darch he might be able to do it quicker since he already has everything set up and most likely only two files will need to be changed before a compile.
zenulator said:
Yes it will work for froyo if you modify it and put in the correct zImage (kernel). It won't work with the update I posted since it's made for Sense roms and uses HTC's Synaptics driver which isn't compatible with AOSP 2.2 Froyo/Cyanogenmod.
If you want a AOSP kernel with no overclock and no ability to overclock at all then I can do that but not for a couple days. If you ask darch he might be able to do it quicker since he already has everything set up and most likely only two files will need to be changed before a compile.
Click to expand...
Click to collapse
Thanks for the reply I'm gonna give the new kernel a chance to see how it does
Excuse my ignorance but how is this different from Standard DarchKernel vUV2 691 MHz found here http://forum.xda-developers.com/showthread.php?t=705074 ?
That's what I'm using and it already says
Kernel version
2.6.29-cyanogenmod
[email protected] #6
Thanks for this zen works great
this is undervolted correct? does this really help the battery life?
c00ller said:
Excuse my ignorance but how is this different from Standard DarchKernel vUV2 691 MHz found here http://forum.xda-developers.com/showthread.php?t=705074 ?
That's what I'm using and it already says
Kernel version
2.6.29-cyanogenmod
[email protected] #6
Click to expand...
Click to collapse
Uhh. I'm going to give a brief explanation.
AnyKernel is a tool created by Koushik Dutta found here on github.
The beauty of it is that it can flash/add a kernel to any boot.img regardless of ramdisk. It literally does the unpacking of the boot.img, extracting of the ramdisk, deletion of the original kernel and repacking of the boot.img together with the kernel of your choice.
The difference with this is probably changes in base address/cmd line and possible how it's extracted(haven't looked at it). Very awesome tool nonetheless, and is a lot more efficient that going through the process of coupling the kernel with each specific ramdisk before releasing a boot.img.
That's how it's different from your quoted "kernel".
Decad3nce said:
Uhh. I'm going to give a brief explanation.
AnyKernel is a tool created by Koushik Dutta found here on github.
The beauty of it is that it can flash/add a kernel to any boot.img regardless of ramdisk. It literally does the unpacking of the boot.img, extracting of the ramdisk, deletion of the original kernel and repacking of the boot.img together with the kernel of your choice.
The difference with this is probably changes in base address/cmd line and possible how it's extracted(haven't looked at it). Very awesome tool nonetheless, and is a lot more efficient that going through the process of coupling the kernel with each specific ramdisk before releasing a boot.img.
That's how it's different from your quoted "kernel".
Click to expand...
Click to collapse
I understand the explanation but have to ask what rge different change. I know this will just change the kernal from the boot imiage which is great and it has the HTC synaptic drivers in the kernal but that kernal with the HTC drivers has already been implemented into the latest boot.imgs. its a cool concept and would make it easier to change just the kernal for a one shot stop when a newer kernal comes out but as of right now that's the same kernal most of the sense based roms have already implemented into them at this time. If im wrong I'm sorry.
Now with the HTC Synaptics driver included, the swipe action once the screen is on is no longer lagged. However, I notice that there is still lag from the time the power button is hit to the time the screen comes on as compared to stock where there is almost no lag. Is there some other driver or something that causes this?
Well just an update but it has been very smooth so far, 8 hours as still smooth . Great job. Screen rotation and scroll seem quicker also .
Sent from my HERO200 using XDA App
Papa Smurf151 said:
I understand the explanation but have to ask what rge different change. I know this will just change the kernal from the boot imiage which is great and it has the HTC synaptic drivers in the kernal but that kernal with the HTC drivers has already been implemented into the latest boot.imgs. its a cool concept and would make it easier to change just the kernal for a one shot stop when a newer kernal comes out but as of right now that's the same kernal most of the sense based roms have already implemented into them at this time. If im wrong I'm sorry.
Click to expand...
Click to collapse
This will just make it a lot easier instead of having multiple boot.img for different roms like in the other thread. Plus this will work on other roms not supported in the other thread. I know the kernel brings nothing new but for instance if someone wants to overclock my old ZenHero they can now do that. Or if someone just rooted their phone and installed RA or some other recovery this is all they need to over clock and still keep their stock system.
So when someone makes a new kernel they can use this and have it work on any Rom instead of just a specific Rom.
Sent from my HERO200 using XDA App
zer0vette said:
Now with the HTC Synaptics driver included, the swipe action once the screen is one is no longer lagged. However, I notice that there is still lag from the time the power button is hit to the time the screen comes on as compared to stock where there is almost no lag. Is there some other driver or something that causes this?
Click to expand...
Click to collapse
I've always wondered about this delay with the OC kernels as well.
Sent from my HERO200 using XDA App
zenulator said:
This will just make it a lot easier instead of having multiple boot.img for different roms like in the other thread. Plus this will work on other roms not supported in the other thread. I know the kernel brings nothing new but for instance if someone wants to overclock my old ZenHero they can now do that. Or if someone just rooted their phone and installed RA or some other recovery this is all they need to over clock and still keep their stock system.
So when someone makes a new kernel they can use this and have it work on any Rom instead of just a specific Rom.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Makes sense. I thought about it actually and it will make things easier. I used it earlier today on a boot.img I flashed first that had the ramdisk mod for battery tweak but I think was missing the HTC synaptic driver. Lag is all gone and it worked great.
Papa Smurf151 said:
Makes sense. I thought about it actually and it will make things easier. I used it earlier today on a boot.img I flashed first that had the ramdisk mod for battery tweak but I think was missing the HTC synaptic driver. Lag is all gone and it worked great.
Click to expand...
Click to collapse
It's definitely going to make it easier for me at least since I plan on doing a bunch of new kernels based on toasts and darchstars work. As well as the official HTC kernel with toasts overclock.
Sent from my HERO200 using XDA App
zenulator said:
It's definitely going to make it easier for me at least since I plan on doing a bunch of new kernels based on toasts and darchstars work. As well as the official HTC kernel with toasts overclock.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Now this is what I'm talking about
I was looking for something like this. Darchstar is one helluva dev, but it seems like the only kernels in use these days are Toasts (base) then modded toast kerenels by Darchstar (which are great as well). But I'd like to see a couple of tweaks fixed in the most recent Kernel #6 such as the typo that Uroshiol mentioned that is located in the actual zImage in the DArchstar uv2 kernel 710 with freememkiller
Nice nice work ya'llz and great stuff Zen... makes the addition of new kernels a breeeeze
Wait...so there is an under volted, oc kernel available for nfinite's .6 stock rom that eliminates the menu button wake lag?? i dont like the lag but deal with it. although if there is a way to eliminate the lag, please share!!
Zen, you're definitely an unsung hero (no pun intended I swear) around these parts and I for one definitely appreciate your work. Cheers!
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
Hello,
Based off the bionic kexec with a proper devtree, ramdisk, and kernel (stock) We can probably get kexec on our devices. Also, Don't be suprised if your device freezes and then reboots, it is WIP (Work in Progress). I would test this if my device hasn't bricked. So you can test it. It won't permemetly brick your device.
Well, Enough said here is the dl:
http://beta.androidfilehost.com/?fid=9390135922294522015
Cheers and good luck!!!
Reserved!!!
Safestrap has kexec support. Just no kexec kernel.
Sent from my locked MB865 on Ice Cream Sandwich.
We already have a working kexec for our phone... as DemosZevasa said we don't have a kernal... and really don't need one as we can build most ICS/JB Roms to work with stock.
What can I do if I had kexec kernel?
[I miss symbian^3 community.]
sad_but_cool1 said:
What can I do if I had kexec kernel?
[I miss symbian^3 community.]
Click to expand...
Click to collapse
I'm missing out, Where is kexec?
Is it downloadable?
If I applied this zipped update to add kexec support to kernel,will my phone boots always to the new ramdisk?
Can u share the source for binaries?
I miss symbian^3 community.
tcf38012 said:
I'm missing out, Where is kexec?
Is it downloadable?
Click to expand...
Click to collapse
Look here:
http://forum.xda-developers.com/showthread.php?p=26046059
tcf38012 said:
Hello,
Based off the bionic kexec with a proper devtree, ramdisk, and kernel (stock) We can probably get kexec on our devices. Also, Don't be suprised if your device freezes and then reboots, it is WIP (Work in Progress). I would test this if my device hasn't bricked. So you can test it. It won't permemetly brick your device.
Well, Enough said here is the dl:
http://beta.androidfilehost.com/?fid=9390135922294522015
Cheers and good luck!!!
Click to expand...
Click to collapse
Is this for 2.X kernel or for 3.X kernel? I tried the 3.X kernel kexec, they not work on atrix2( though works well on RAZR), maybe I did something wrong
wanggjghost said:
Is this for 2.X kernel or for 3.X kernel? I tried the 3.X kernel kexec, they not work on atrix2( though works well on RAZR), maybe I did something wrong
Click to expand...
Click to collapse
I'm thinking it is not having kexec support in the kernel
Iv'e got the kernel source 3.0.8 without kexec I just need to add kexec
Once we get a kernel with kexec, we can kexec custom kernels.
Right now I'm mostly working on the fastboot files for ATT US so I can get that out of the way.
Cheers!!!
tcf38012 said:
I'm thinking it is not having kexec support in the kernel
Iv'e got the kernel source 3.0.8 without kexec I just need to add kexec
Once we get a kernel with kexec, we can kexec custom kernels.
Right now I'm mostly working on the fastboot files for ATT US so I can get that out of the way.
Cheers!!!
Click to expand...
Click to collapse
Right now you can only try fully stock kernels with kexec, use the link I provided above, it works, I have done it with a stock compiled kernel. Yes we need to use the one for the RAZR, not the bionic.
This will work with 2.x or 3.x kernels... but since we have ICS, trying to boot a 2.x kernel will get you in trouble.
By the way which 3.0.8 kernel are you using? It is VERY, VERY important to use the moto mb865 source to be able to add the kexec support, for now.
jimbridgman said:
Right now you can only try fully stock kernels with kexec, use the link I provided above, it works, I have done it with a stock compiled kernel. Yes we need to use the one for the RAZR, not the bionic.
This will work with 2.x or 3.x kernels... but since we have ICS, trying to boot a 2.x kernel will get you in trouble.
By the way which 3.0.8 kernel are you using? It is VERY, VERY important to use the moto mb865 source to be able to add the kexec support, for now.
Click to expand...
Click to collapse
I can't find a MB865 kernel source with kexec and 3.x. I don't know about the moto sourceforge they all seem GB (2.6.x)
So i just used a kernel that is OMAP and is ASOP.
tcf38012 said:
I can't find a MB865 kernel source with kexec and 3.x. I don't know about the moto sourceforge they all seem GB (2.6.x)
So i just used a kernel that is OMAP and is ASOP.
Click to expand...
Click to collapse
Yeah that is the issue. Right now, you can only boot stock kernels with kexec on our device, and a few others seem to have this same issue. Yes, moto has not released the source for our phone for ICS yet.
As for finding a kernel with kexec support in it, I would go take a look at hascode's githib, he has the stuff up there, that you might be able to modify, but the kernel I think he has is for cm9 and it is not booting on our device quite yet.
You should look for at least the me865 ICS source and try and throw the kexec parts into it, from hascodes github.
Try the me865 soruce from here:
http://sourceforge.net/projects/me865.motorola/files/ME865/
There might be an ICS version in there, to take a shot at, for now.
And this kid is only 14. Amazing!
Sent from my MB865 using xda app-developers app
smgulsby said:
And this kid is only 14. Amazing!
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
posting something for another phone without any modification would be the opposite of amazing...
Stuff like this should be in the general section.its an ideal,not a development.
Sent from my MB865 using xda premium
rdavisct said:
posting something for another phone without any modification would be the opposite of amazing...
Stuff like this should be in the general section.its an ideal,not a development.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Why do ya think it's WIP, and not Q (Question)? It's because of we just need a kernel that we can combine the drivers and kexec with.
Cheers!!!
tcf38012 said:
Why do ya think it's WIP, and not Q (Question)? It's because of we just need a kernel that we can combine the drivers and kexec with.
Cheers!!!
Click to expand...
Click to collapse
But you also have to use the RIGHT binary version of kexec (the boinic one will not work for our phone). I hope you know that I was part of the team that worked on the OG of kexec with kohlk and mbm and those guys, and the one posted in the razr form that I linked in this thread works for our phone too, I made sure of that, so that there was no need for a razr version and an a2 version...
jimbridgman said:
But you also have to use the binary version of kexec (the boinic one will not work for our phone). I hope you know that I was part of the team that worked on the OG of kexec with kohlk and mbm and those guys, and the one posted in the razr form that I linked in this thread works for our phone too, I made sure of that, so that there was no need for a razr version and an a2 version...
Click to expand...
Click to collapse
I just need my replacment phone back. I'm lost without it. I can't test anything without an Atrix 2 . I should get it Friday .
tcf38012 said:
I just need my replacment phone back. I'm lost without it. I can't test anything without an Atrix 2 . I should get it Friday .
Click to expand...
Click to collapse
Cool!!!
I promise that kexec works. I have tested it with both a true moto a2 kernel and the cm7 kernel that I compiled back in the 2.3.6 days.
I am not 100% on an ICS kernel, though since we don't have source yet, and I am not sure if the aosp kernel will work or not, as I had a lot of trouble getting the cm7 kernel working back in april and may.
jimbridgman said:
Cool!!!
I promise that kexec works. I have tested it with both a true moto a2 kernel and the cm7 kernel that I compiled back in the 2.3.6 days.
I am not 100% on an ICS kernel, though since we don't have source yet, and I am not sure if the aosp kernel will work or not, as I had a lot of trouble getting the cm7 kernel working back in april and may.
Click to expand...
Click to collapse
Oh yeah,
I just never heard about that.
Cheers!!!
Introduction
This is a replacement kernel for CyanogenMod 10 and 10.1 evita builds. The kernel is designed to be as close as possible to the stock CyanogenMod kernel with a few improvements.
Linaro toolchain:
The kernel is compiled with the latest Linaro toolchain based on gcc 4.7 rather than the default Android toolchain. This may provide performance improvements in some situations. I have made a few patches applied to make it compatible with gcc 4.7.
Overclock:
The highest frequency now available under Settings -> Performance with these kernels is,
Code:
CPU: 1782 MHz 1.25 V
L2: 1350 MHz 1.15 V
BUS: 532 MHz
I've also included a modified thermald.conf in the flashable zip.
Refresh rate:
I've reverted the refresh rate to the original value from the sense source code (57 Hz). This works better when "Disable HW overlays" is selected.
Downloading and installing
Download the flashable zip,
cm10.1_vz-oc-linaro.4.zip MD5=7233ccffa17fa16a2dc6292ecf755fb4
mega.co.nz
ubuntuone.com
Older versions:
cm10.1_vz-oc-linaro.3.zip MD5=5e0efdfd0390f3f923090a574d142808
mega.co.nz
ubuntuone.com
cm10.1_vz-oc.2.zip MD5=cf2c4ee8ba09627e598b78dcea225d39
cm10.1_vz-oc-linaro.2.zip MD5=2931cc59515949fa461a89ea17c99328
vz-oc.1.zip MD5=2f1740d67cd1d5c02a7ac5489bafe7a0
vz-oc.2.zip MD5=4e4d444130e8eb71c27cc23fed65fc88
vz-oc-linaro.1.zip MD5=ca674641e05595e64698afda8aa02943
vz-oc-linaro.2.zip MD5=2b01472d00e069c53f934c30b49475d1
cm10.1_vz-oc.1.zip MD5=576db9e99b2289dae7fc5b548a0d61b4
cm10.1_vz-oc-linaro.1.zip MD5=1a5f3b50608e6b44da50829b2c04ec5c
If you have HBOOT earlier than 1.14 or have S-OFF, then you can just flash the zip from recovery. This will flash the kernel as well as all required modules and thermald.conf. Otherwise, HBOOT 1.14 users will need to extract the boot.img, enter bootloader mode and run
Code:
fastboot flash boot boot.img
Then you will also need to flash the zip to get modules and themald.conf.
Compatability
cm10.1_vz-oc-linaro.4 is compatible with CM10.1 UNOFFICIAL build from 16/04/2013 onwards.
cm10.1_vz-oc-linaro.3 is compatible with CM10.1 NIGHTLY build from 01/03/2013 onwards.
cm10.1_vz-oc.2 (and linaro) are compatible with CM10.1 NIGHTLY build from 19/02/2013 only.
cm10.1_vz-oc.1 (and linaro) are compatible with CM10.1 UNOFFICIAL build from 06/02/2013 only.
vz-oc.2 (and linaro) are compatible with CM10 NIGHTLY builds from 26/12/2012 to 13/01/2013.
vz-oc.1 (and linaro) are compatible with CM10 NIGHTLY builds from 28/11/2012 to 25/12/2012.
Future development
I hope to introduce GPU overclocking soon and there will be updated builds as
soon as changes come into the main CyanogenMod repo.
Building the kernel
For those who would like to build the kernel themselves, here are some basic
instructions. First you will need to acquire some tools. You can get the default
toolchain from the CM10 source code at,
Code:
system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/
Otherwise, if you want to use the Linaro toolchain, you can get it at
Linaro toolchain
You will also need a working boot image to get the ramdisk from. You can build
mkbootimg using these instructions
building mkbootimg
Finally, you can get split_bootimg_pl from William Encks site
download split_bootimg_pl
Clone the repo and change to your desired branch
Code:
git clone https://github.com/vanja-zecevic/android_kernel_htc_msm8960.git
git checkout jellybean-oc
Now export an environmental variable pointing to your desired toolchain
Code:
export CCOMPILER=$PATH_TO_TOOLCHAIN/bin/arm-eabi-
Copy the config file, run menuconfig once and start the build replacing -j12
with your desired number of threads
Code:
cp ./config-oc ./.config
make ARCH=arm SUBARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
make ARCH=arm SUBARCH=arm CROSS_COMPILE=$CCOMPILER -j12
Extract a ramdisk from a working boot image and repack with your freshly built
kernel using the following command for cm10,
Code:
./split_bootimg_pl ./boot.img
./mkbootimg --base 0x80400000 --ramdiskaddr 0x81800000 \
--cmdline 'console=ttyHSL0,115200,n8' \
--kernel arch/arm/boot/zImage --ramdisk boot.img-ramdisk.gz \
-o boot_vz-oc.img
cm10.1 will need the following cmdline
Code:
--cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom'
You are ready to flash your new kernel!
Contact
I hope you enjoy using this kernel! Please also visit the github page for this project for alternative download links and for the source code.
GitHub
Cheers,
Vanja
Looks good will give it a shot next time I'm on a CM10 based ROM. Will this only work on CM10 or will it work with other AOSP builds too?
Sent from my HTC One X using Tapatalk 2
1. Could you post flash able zips for the majority of us who can flash these in recovery?
2. Very few users including myself have issues with kernels without stock voltage values. The device will just not boot, any way to have separate versions without different voltages just to rule that issue out when people ask why their device won't boot?
Sent from my One X using Tapatalk 2
superchilpil said:
1. Could you post flash able zips for the majority of us who can flash these in recovery?
2. Very few users including myself have issues with kernels without stock voltage values. The device will just not boot, any way to have separate versions without different voltages just to rule that issue out when people ask why their device won't boot?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
+1 thank you
Straight talked from my HOX!
I like the idea of a stockish CM10 OC kernel, Me myself i underclock. I would give this a go see how it holds up. the increase in clock speed is usually a nice thing to have even if not used. Also a 2.0GHz version would be awesome too.
Nice job!
Sent from my Nexus 7
ChummyDays said:
Fastboot flash boot boot.img
Sent from my One X using Tapatalk
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Re read my post, I know how to use fastboot
Sent from my One X using Tapatalk 2
Thanks for the feedback people!
I'm currently running HBOOT 1.14, so I will need to downgrade to 1.09 before I can make/test flashable kernel zips. I think I will get around to this in the next week.
I will also look into some other requests.
Is anyone running the kernel? Are you happy with it? Any benchmarks?
rohan32 said:
Nice job!
Click to expand...
Click to collapse
Thanks Rohan, I was inspired by your work!
Quick question: Sweep2Wake support?
I know OP stated 'as close to stock as possible,' searched thread for 'sweep' and turned up nuffin, so I'm just curious. Glad to see another kernel option (and prospective CM10 material!).
superchilpil said:
1. Could you post flash able zips for the majority of us who can flash these in recovery?
2. Very few users including myself have issues with kernels without stock voltage values. The device will just not boot, any way to have separate versions without different voltages just to rule that issue out when people ask why their device won't boot?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I don't plan on maintaining them, but if newer versions come out, just rename to boot.img and swap out the file in the zips:
With Linaro toolchain
without Linaro toolchain
Vanja, if you want these gone, let me know.
hands on CM boot screen animation
running stable build cm10, and like the title says, hangs on boot screen animation. Do you have to configure the thermald.conf first?
thanks
taylor.fowler said:
I don't plan on maintaining them, but if newer versions come out, just rename to boot.img and swap out the file in the zips:
Click to expand...
Click to collapse
Thanks Taylor! I've included zips now.
nespid said:
running stable build cm10, and like the title says, hangs on boot screen animation. Do you have to configure the thermald.conf first?
thanks
Click to expand...
Click to collapse
Hi nespid, unfortunately, these kernels currently only support builds from 28/11/2012 onward. I've re-written the "Compatibility" section to make that more clear.
I will put up a build compatible with the "stable" build in a few days if you like.
vanja_z said:
Hi nespid, unfortunately, these kernels currently only support builds from 28/11/2012 onward. I've re-written the "Compatibility" section to make that more clear.
I will put up a build compatible with the "stable" build in a few days if you like.
Click to expand...
Click to collapse
That would be absolutely great!
Thank you!
Sent from my HTC One X+ using xda app-developers app
just wondering ,when and if are you goin make one for cm10.1? because the one for cm10 just flatout smokes :good! really makes your phone move!! :good:
Re: [KERNEL] vz-oc kernel: CM10 overclocking, normal & Linaro builds
Any feedback on battery life with this one? And how does it play with No Frills CPU and such?
Thanks for the hard work!
Sent from my CM10ified Beast (a.k.a. HTC One XL)
I've put up cm10.1 kernels!
ps. cm10.0 stable kernel is coming soon, I haven't forgotten, sorry for the delay
vanja_z said:
I've put up cm10.1 kernels!
ps. cm10.0 stable kernel is coming soon, I haven't forgotten, sorry for the delay
Click to expand...
Click to collapse
That's awesome, I will be testing this soon. I know it was asked before but I'm also very interested to know, any plans on implementing sweep2wake? After using it for even a little bit it spoils you, it really is an awesome feature. Otherwise thank you for your hard work, I'll leave feedback in a couple days after testing!
Thanks much, got the kernel running on CM10.1 with 1.14 hboot no problems. Modified thermald.conf and seems to allow oc to stick thus far.
great work,
dbd
UPDATE: this kernel is working wonderfully with cm10.1. +1 for linaro toolchain.
Hello, I am enjoying my wonderful new rom that was posted here: http://forum.xda-developers.com/showthread.php?t=2430785
I am looking for a kernel that will work with this ROM and allow me to overclock the CPU. I did do some reading already in the forums, but there seems to be no solid answer. Some say the blackhawk works and some say it doesn't. I will be grateful to whomever helps me find this kernel. Thanks!
NEXT Kernel http://forum.xda-developers.com/showthread.php?t=2302663 (only don´t forget to flash the proprietary binary part DIRECTLY after the kernel )
or
Dhollmen Kernel should work too http://forum.xda-developers.com/showthread.php?t=2176563
Android-Andi said:
NEXT Kernel http://forum.xda-developers.com/showthread.php?t=2302663 (only don´t forget to flash the proprietary binary part DIRECTLY after the kernel )
or
Dhollmen Kernel should work too http://forum.xda-developers.com/showthread.php?t=2176563
Click to expand...
Click to collapse
THANKS!!!
nope
Android-Andi said:
NEXT Kernel http://forum.xda-developers.com/showthread.php?t=2302663 (only don´t forget to flash the proprietary binary part DIRECTLY after the kernel )
or
Dhollmen Kernel should work too http://forum.xda-developers.com/showthread.php?t=2176563
Click to expand...
Click to collapse
Dhollmen just hard bricked my GS3. (Slimbean 4.3.1)
just throwing that out there.