Database Info

[32A][ROM][PORT] ZeroXd 5.1 w/ Amon_RA's v1.1.0 Kernel [Sept. 7 2009]

Original Thread
Credits to TwistedUmbrella and Amon_RA for the kernel ofc!
Casper's Shadow - ZeroXd 5.1 w/ Amon_RA's v1.1.0 kernel [rapidshare]
For Ringtones and other "Extra Stuff" download Resources.zip from oringinal thread. Maybe on next update I'll include them already into the original ROM archive...
Note: Just install normally! No need to type anything into the terminal as the original thread states because this port replaces ramdisk and kernel so no need

Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..

I only do the ports This is not my work. I merely repack the files for easier installation and for those that don't have linux

covertless said:
Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..
Click to expand...
Click to collapse
HAHAHA, lol, HAHAHAHAHAHA. Wow, hahahahaha. Ok. Sorry. Ok, seriously... anyway... You might wanna throw the kernel on this
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.1r2.zip
MD5: 0d10525b55ed6c97b7741a70aa113cdb
Execute Terminal and enter the following commands:
rwsystem
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
(and delete system/bin/magic and system/bin/sapphire, as they dont affect a swapped kernel)
I think it'll shut this kid up. Unless he has no idea what partitioning an sd card does, in which case this will still be slow. It's based on some newer source and some improved scripts and optimizing. Can't say its faster, but at least itll even out.

L10nH34Rt said:
I only do the ports This is not my work. I merely repack the files for easier installation and for those that don't have linux
Click to expand...
Click to collapse
Okay my bad, anyway what I meant to say was thank you for the effort in porting over for the 32a.
twistedumbrella said:
HAHAHA, lol, HAHAHAHAHAHA. Wow, hahahahaha. Ok. Sorry. Ok, seriously... anyway... You might wanna throw the kernel on this
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.1r2.zip
MD5: 0d10525b55ed6c97b7741a70aa113cdb
Execute Terminal and enter the following commands:
rwsystem
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
(and delete system/bin/magic and system/bin/sapphire, as they dont affect a swapped kernel)
I think it'll shut this kid up. Unless he has no idea what partitioning an sd card does, in which case this will still be slow. It's based on some newer source and some improved scripts and optimizing. Can't say its faster, but at least itll even out.
Click to expand...
Click to collapse
Anyway twistedumbrella, are you as what your name describes? Your comments are uncalled for and not needed in this community. Please grow up and get a life. I am new here, so would appreciate if you could give positive feedbacks instead of insults.

@covertless: He is right though... On my magic this ROM is *MUCH* faster than the JACxHEROski one
@Twisted: Ok will throw the kernel and include full instructions based on your post here!
Thank you for your work!
p.s. If I delete /system/bin/magic and /system/bin/sapphire will we still be able to run rwsystem and then magic?

*L10nH34Rt: Great could you release the ported version when its done?
P.S. I am not saying he is wrong, anyway I appreciate that there are people like you and him contributing to this community by working hard on the dev of roms. Not sure as to why he had to assume that non programmers like me are "kids".

Sure I will later today when I get to my linux box

covertless said:
Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..
Click to expand...
Click to collapse
Wait, even he says "jac rom"i think he is talkin about older zero releases which are using jac kernel vs new amonra kernel, or is he not? Because there is no hero port who can outperform xero's speed with proper adjustments atm.

Nyanna said:
Wait, even he says "jac rom"i think he is talkin about older zero releases which are using jac kernel vs new amonra kernel, or is he not? Because there is no hero port who can outperform xero's speed with proper adjustments atm.
Click to expand...
Click to collapse
I was referring to L10nH34Rt's port of the JACxHEROski-v1.7r2 w/ Amon_RA's 1.1.0 kernel.
http://forum.xda-developers.com/showthread.php?t=549873

Compiling Cyanogen's kernel - eclair branch - camera not working?

Hi guys,
I'm trying to build a Cyanogen's kernel source (eclair branch) for JAC's xROM.
This ROM has all the bits and pieces necessary for NCommander's camera fix to work, and on my 32B Dream, the camera works just fine with the 32B rom from JAC.
However, I want to use the rom on my 32A Sapphire, so I'm building my own 32A kernel, mashing that with JAC's ramdisk, and hoping to get a working device.
Here's where I'm up to. My build environment is all set up, I've sync'ed Cyanogen's kernel sources from his GIT, and pulled a working kernel config so that I can (theoretically) compile a kernel with the same options etc.
The build works just fine, and spits out a zImage which I can (with mkbootimage) combine with a ramdisk to make a boot.img, which I can flash to my boot partition on teh Sapphire and it works just fine.
Except the camera doesn't work. The screen just goes black and nothing happens.
I found a working 2.1 AOSP kernel ported to 32A, and by coincidence, it happened to be a Cyanogen build - 2.6.29.6-cm42. Using that kernel, and JAC's ramdisk, the device boots, and the camera works. It's this kernel that I extracted the kernel config from to build my own kernel.
I figured same config, same source tree, should result in same (or similar enough) kernel so the camera would work on my build too. But it doesn't.
Does anyone have any advice on how to build Cyanogen's eclair kernel so that Ncommander's camera fix will work?
Desperately seeking advice - this is really annoying me!
reply here, twitter me, or IM me - I'm on gtalk too if you're available for a quick chat there. just let me know and i'll PM you my gtalk address.

So, 94 people have viewed this and no one has any ideas?
Come on folks. There are devs out there using Cyanogen's kernel on Eclair builds, and the camera is working. Surely someone can spare me a minute or two to offer some advice on where my kernel build might be going wrong.
If anyone has downloaded the kernel source from Cyanogen's git hub (the eclair branch, in particular) and successfully used a kernel they've build on an eclair rom with working camera, I'd be really grateful if you could share the process you've followed, just so I can work out where I've gone wrong.
This is, after all, a development forum. Surely someone knows how to do this ...

patience young skywalker

apacheo said:
So, 94 people have viewed this and no one has any ideas?
This is, after all, a development forum. Surely someone knows how to do this ...
Click to expand...
Click to collapse
Well thats been an issue for a long time now, there are peolple who know and they might have even seen this thread. Unfortunately they dont care enough to help, even if this is development. I was one of those 94 views, wish I could help. Nobody is willing to help teach people make their own software.

bubonik said:
Unfortunately they dont care enough to help, even if this is development. I was one of those 94 views, wish I could help. Nobody is willing to help teach people make their own software.
Click to expand...
Click to collapse
You know, it really does seem that way.
I've asked respected devs on twitter, and not ONE OF THEM has bothered to respond.
The only advice I've had was from bcrook88, and to his credit, he didn't have much experience in building eclair kernels. At least he took the time to have a bit of a chat to see if he could help.
That's more than anyone else has offered.
It's really sad.
Even the iPhoney community is more accepting.

apacheo said:
It's really sad.
Even the iPhoney community is more accepting.
Click to expand...
Click to collapse
Yup you'll get better help and support than in a open-source community which is terrible. Asking for things from some devs is like trying to walk on water.
I dont know but maybe this can help you:
http://forum.xda-developers.com/showthread.php?t=566235

dawg, just don't worry about it.

Asswipe44 said:
dawg, just don't worry about it.
Click to expand...
Click to collapse
Easy to say - but I want a working camera, damnit

fetch AOSP from android.git. checkout eclair. fetch vendor/htc/dream-open, vendor/htc/sapphire-open, and hardware/msm7k from ncommander's gitorious. checkout origin/eclair. copy recursive libaudio* from AOSP hardware/msm7k to the new hardware/msm7k directory, replacing what is there. your fetching ncommander's source so you have a reference point for future use.
(assuming your using an x86 host and bash/ksh)
export CCOMPILER=PATH_TO_AOSP_SOURCE/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
fetch 2.6.29.6 'donut' kernel source.
copy your boot.img to the root of the kernel source dir.
scripts/extract-ikconfig boot.img >.config
make ARCH=arm CROSS_COMPILE=$CCOMPILER oldconfig
make clean; make ARCH=arm CROSS_COMPILE=$CCOMPILER
make ARCH=arm CROSS_COMPILE=$CCOMPILER INSTALL_MOD_PATH=./out/modules/ modules_install
(get squashfs-tools package)
cd out/modules
mksquashfs . ../modules.sqf -noappend
cd ../../
fetch this and unpack it:
http://android-dls.com/files/linux/split_bootimg.zip
./split_bootimg.pl boot.img
cp arch/arm/boot/zImage ./
(this util and more are found after you build AOSP, within out/host/linux-x86/bin)
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel zImage --ramdisk boot.img-ramdisk.gz -o boot-new.img
you can flash boot-new.img to boot and push modules.sqf to system/modules
your camera should work now with the hacked in drivers.
-pershoot

pershoot said:
fetch 2.6.29.6 'donut' kernel source.
...
your camera should work now with the hacked in drivers.
Click to expand...
Click to collapse
the donut branch, and not eclair? I've been trying with eclair, with no luck.
i'll try following these instructions and see how i go - i've been doing 90% of this, so i'll see how i go.
thanks so much for explaining it all. even if I have worked out most of this, seeing it black and white at least gives me a reference!

apacheo said:
the donut branch, and not eclair? I've been trying with eclair, with no luck.
i'll try following these instructions and see how i go - i've been doing 90% of this, so i'll see how i go.
thanks so much for explaining it all. even if I have worked out most of this, seeing it black and white at least gives me a reference!
Click to expand...
Click to collapse
ncommander's reverse engineered magic is based off of the donut kernel, 2.6.29.6 revision. they will not work if you use eclair (the msm_camera bits also will not build when using cm-kernel eclair branch, and need to be commented out), and or will not work out of the box with 2.6.32 (as an example).

pershoot said:
ncommander's reverse engineered magic is based off of the donut kernel, 2.6.29.6 revision.
Click to expand...
Click to collapse
well fsck.
i probably should have figured that out
my kernel's finished building now - i'll squishing up the modules etc. fingers crossed!

Alright its booted...
Here goes the Camera test...
OOO YEAH
pershoot, you rock.

Alright its booted...
Here goes the Camera test...
OOO YEAH
pershoot, you rock.

enjoy
-pershoot.

apacheo said:
the donut branch, and not eclair? I've been trying with eclair, with no luck.
i'll try following these instructions and see how i go - i've been doing 90% of this, so i'll see how i go.
thanks so much for explaining it all. even if I have worked out most of this, seeing it black and white at least gives me a reference!
Click to expand...
Click to collapse
haha yes, eclair branch still doesnt have its own camera persay
the camera we have on eclair is "hacked" like people said, from my understanding (please correct me if I am wrong) its source is mainly donut, if not all donut essentially

So after much debugging I figured this out today. And then I find this thread...
Anyways, the diff between donuts's msm_camera.c and the eclair one is quite big: some structure member names have changed, more logging, flash handling, some queuing code has changed. Still, it shouldn't be too hard to update NCommander's drivers, anyone wants to have a go? We might get official drivers soon, but having open source drivers is better.
The trouble with using a donut kernel is that the 3D Gallery doesn't work, still haven't quite figured why. Any ideas?

kapitan_petko said:
The trouble with using a donut kernel is that the 3D Gallery doesn't work, still haven't quite figured why. Any ideas?
Click to expand...
Click to collapse
Apparently the eclair kernel uses a different device for 3D acceleration (/dev/hw3dc). So it's either camera or 3D gallery...

pershoot said:
your camera should work now with the hacked in drivers.
-pershoot
Click to expand...
Click to collapse
Hey pershoot, thanks for taking the time to explain and walk through this. Very nice work, I would have been scratching my head for a very long time.

Hardware GL: SOLUTION

Seems that the file that stands in the way of hardware GL on DREAM for android 2.x is libhgl.so. Now interesting thing is that I've compared the 32A and DREAM versions of libhgl.so (used stock rogers roms since their versions match), and I've found that the libhgl.so for rogers 32A and DREAM are *identical*.... which means that the GL parts of the 7200A and 7201A are compatible -- i.e. work with the same driver.
Now this guy has apparently released leaked 32A/Hero files and has built a 32A ROM with them, including the applicable libhgl.so... which should be compatible with DREAM/32B..... http://forum.xda-developers.com/showthread.php?t=636212
Is there some stupid obvious thing that I'm missing? Because it sure looks to me like we have all the pieces we need.....

here is what we are missing.
A developer (someone that knows what they are doing) to check this before making asumptions of something working right.

whats this guy talking about ^^^^

death1246 said:
here is what we are missing.
A developer (someone that knows what they are doing) to check this before making asumptions of something working right.
Click to expand...
Click to collapse
What are you getting at? Are you implying that I'm not a qualified developer?
I can assure you that I am.
What I am asking is if there is actually anyone who has looked at this at all, and what their findings were. And I want this information BEFORE I waste several hours of my time building AOSP for DREAM with files dumped from HERO. If someone has tried, but there is some simple thing that is missing, like radio/firmware issues that might interfere with this libhgl.so version running on a DREAM with, for example, a stock radio.
Is this related to those weird kernel changes that HTC made to rogers dream? Might we need to install a rogers dream radio? Might we need to install a HERO radio? There are all kind of weird issues that may need to be worked out even given that the hardware IS compatible!

kingklick said:
whats this guy talking about ^^^^
Click to expand...
Click to collapse
Beats me.... but it *feels* like he's trying to insult me...

Very interesting.

Nice observation.
King, since ur pumping out roms like theres no 2moro Have u tried incorporating his libs into ur rom n seeing if it works ?

I'm not a qualified developer, but I am a 32A user and in case this helps:
To use ROMs based on the new Rogers update I need to install the 1.76.2007 SPL and the 6.35 Radio. I also need to use Amon_RA's Hero recovery. The same thing goes for ahmgsk's ROM, though it isn't stable enough for me to use. ahmgsk does have 3D Gallery and HQ YouTube working.

Daneshm90 said:
Nice observation.
King, since ur pumping out roms like theres no 2moro Have u tried incorporating his libs into ur rom n seeing if it works ?
Click to expand...
Click to collapse
He actually is. Not necessarily from THAT ROM, but likely from the same source... hero 2.1 dump. And not necessarily the files needed for GL. That is why h264 playback is working on his roms now....
He is also employing the 10MB ram hack, which breaks GL even when the drivers are definitely right.
Be aware that just putting the files into place and disabling the 10MB ramhack may not be enough. We are definitely talking about two devices with different memory, so it may require a kernel adjustment. It may also require a radio adjustment.

Rede83 said:
I'm not a qualified developer, but I am a 32A user and in case this helps:
To use ROMs based on the new Rogers update I need to install the 1.76.2007 SPL and the 6.35 Radio. I also need to use Amon_RA's Hero recovery. The same thing goes for ahmgsk's ROM, though it isn't stable enough for me to use. ahmgsk does have 3D Gallery and HQ YouTube working.
Click to expand...
Click to collapse
Note that we aren't working off a rogers dump. I just used the rogers files (to judge hardware compatibility between 7200A and 7201A) because I happen to know that everything in those two devices definitely matches up except the CPU/RAM.
But your observation regarding the SPL and RADIO are *definitely* valid... which is why I'm talking about the possibility of needing to mess with the radio. I don't *think* that the SPL itself has any more to do with it than simply being compatible with the chosen radio.
*** further possibility: likely any problems encountered would be due to memory mapping. It may be possible to manually adjust the libhgl.so to the appropriate mappings. Would require some (at least partial) disassembly/hacking.

Not too sure if it helps but sanpei's rom also had 3d accel.
http://forum.xda-developers.com/showthread.php?t=620782

lbcoder said:
I don't *think* that the SPL itself has any more to do with it than simply being compatible with the chosen radio.
Click to expand...
Click to collapse
I asked about that when initially trying a ROM for the 6.35 radio and my understanding, too, is that the SPL is just required for compatibility with the radio.

Daneshm90 said:
Not too sure if it helps but sanpei's rom also had 3d accel.
http://forum.xda-developers.com/showthread.php?t=620782
Click to expand...
Click to collapse
A heads up: ahmgsk's ROM is build on Sanpei's kernel.

Edit: Rhetorical question. No need to be posted.

edited to be nice

death1246 said:
here is what we are missing.
A developer (someone that knows what they are doing) to check this before making asumptions of something working right.
Click to expand...
Click to collapse
kingklick said:
whats this guy talking about ^^^^
Click to expand...
Click to collapse
lbcoder said:
Beats me.... but it *feels* like he's trying to insult me...
Click to expand...
Click to collapse
Nah I think he's asking what Death1246 was talkin about. Because it didn't make a whole lotta sense.
LesserAnimal said:
Never mind that being the entire point of this thread.
Click to expand...
Click to collapse
and Lol at this ^

So would it be possible to pull the libhgl from kings build and push it to an eclair build?

I don't know if it helps or if I'm being Captain Obvious here, but I've tried just today porting ahmgsk's ROM to 32A old radio (using my Cyanogen-based kernel) and neither video nor 3D does work after this. And pretty much the only thing I've changed is kernel image (with ahmgsk's ramdisk) and wlan.ko, obviously (well, I've moved apps from /system/app to /data/app_s to work around the larger system partition with the new 32A radio, but I don't think that has anything to do with 3D not working). So no, the libhgl doesn't cut it by itself, there's obviously something in-kernel preventing 3D from working on the old 32A/32B radios.

Yes, there are a couple kernel changes that need to be made, and after boot on our Kaiser/Vogue we need to:
Code:
chmod a+rx /dev/msm_hw3dc
chmod a+rx /dev/msm_hw3dm
(we do this in our init.rc)
You also will need working copybit.msm7k.so, libGLES_qcom.so, and an egl.cfg that enables libGLES_qcom.so . There are other .so's that may affect it but those are the only ones I've ever had to move around. This gets OpenGLES mostly working.
I'm no kernel dev but our kernel source can be found here, you can thank dzo and vilord for it.

polyrhythmic said:
Yes, there are a couple kernel changes that need to be made, and after boot on our Kaiser/Vogue we need to:
Code:
chmod a+rx /dev/msm_hw3dc
chmod a+rx /dev/msm_hw3dm
(we do this in our init.rc)
You also will need working copybit.msm7k.so, libGLES_qcom.so, and an egl.cfg that enables libGLES_qcom.so . There are other .so's that may affect it but those are the only ones I've ever had to move around. This gets OpenGLES mostly working.
I'm no kernel dev but our kernel source can be found here, you can thank dzo and vilord for it.
Click to expand...
Click to collapse
WOW THIS IS awesome!
Why didn't i think of that?
i might wait to release a rom though, i'm busy.
How bout it king?

[THINK-TANK] EB13 Source a Rebranded DKxx Source? : Cleaned Source Inside : (87.4 mb)

Searching through the EB13 source in /arch/arm/boot/ I came across three files of interest, victory_test_kernel.tar, recovery.bin and zImage, I ran over hear excited since I thought Sammy was throwing us a bone to get some custom kernels running early, but nevertheless in true Samsung fashion the files of interest come from October 1st of all dates, and seem to be before DK28. That's Sammy for you. You'll have to wait until Monday to get anything truly EB13.
-rwxr-xr-x 1 android android 5.5M Oct 1 08:22 victory_test_kernel.tar
Click to expand...
Click to collapse
This got me thinking, maybe Samsung is just had this source for a while now and this is the outcome of all their edits they've made through the leaked stages, this being the final product, anyways, here is a totally cleaned version of the EB13 source that takes half the time to download and is ready to be compiled with a few edits to victory_03_defconfig and build_kernel.sh.
Code:
Edited victory_03_defconfig to add initramfs source and cleaned
various aspects of unneeded files let behind by Samsung.
If your a dev coming from the DI18 source you might find it interesting to know that the default config is no longer ares_003_defconfig, but is victory_03_defconfig.
Click to expand...
Click to collapse

Yo didnt you say that you was working on MIUI and few other roms?How is that coming along?

bubby323 said:
Browsing the EB13 source and took a peak at /arch/arm/boot and found victory_test_kernel.zip. Flash with Odin, should work great on any DK28 rom, using rfs.
I also found recovery.bin which can be flashed to bml8 for the stock Samsung recovery experience you'll find which I assume is 3e. here
Click to expand...
Click to collapse
Do I get to keep root? How is the GPS? More questions that no one can answer this quickly...

u say for RFS?
What does this mean for ext? Is that going to have to be updated or something based on this new releases or no ?

honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc

shabbypenguin said:
honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc
Click to expand...
Click to collapse
Granted, this post was mostly for devs in the first place, just letting everyone know and uploading resources for those who dont want to dig through the source and wait for it to download.

yea i get that bubby, and i thank you for it
plus its good to let end users know there is work being done behind the scenes

shabbypenguin said:
honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc
Click to expand...
Click to collapse
Ok thought so, btw do we still have to wait til monday, to get things really going like roms even with this?
I read elsewhere that the source doesnt help if we dont have the modem and kernal from the ota?

theres work on the kernel right now, may not be done fully but there is work.. the ota will give stuff like modem and the rom itself. dont be surprised to see test builds before thern tho

shabbypenguin said:
theres work on the kernel right now, may not be done fully but there is work.. the ota will give stuff like modem and the rom itself. dont be surprised to see test builds before thern tho
Click to expand...
Click to collapse
Thought so, i will wait til next week, maybe mid week and, probaly be an update for everything and and and update zip for the new modem.

The initramfs seems to be half-developed there is alot of junk added, and stuff *seems* to be alot missing comparing everything to DK28.

it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread

noobnl said:
it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread
Click to expand...
Click to collapse
HMM, meaning the source has old stuff in it??

noobnl said:
it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread
Click to expand...
Click to collapse
That's odd why would they include old stuff in the source. Junk has been left everywhere.

davidrules7778 said:
Thought so, i will wait til next week, maybe mid week and, probaly be an update for everything and and and update zip for the new modem.
Click to expand...
Click to collapse
<delete>..............

davidrules7778 said:
HMM, meaning the source has old stuff in it??
Click to expand...
Click to collapse
Excellent avatar! "Who ARE you....!!?"
Anyway, Seems that without the kernel and modem the source isn't the end al be all. I'm dying to get f'n TV out working on this phone though. I can continue to dream.

bubby323 said:
That's odd why would they include old stuff in the source. Junk has been left everywhere.
Click to expand...
Click to collapse
Sprint figures we need something to do? ;-)
Sent from Bonsai v 5.0.3

ZenInsight said:
Excellent avatar! "Who ARE you....!!?"
Click to expand...
Click to collapse
What are you talking about? Are you being an ass?

So is this an old source or is this thread a mistake its new EB13 source? I am so confused after reading this thread.

ryno502 said:
So is this an old source or is this thread a mistake its new EB13 source? I am so confused after reading this thread.
Click to expand...
Click to collapse
Sammy posted it as new eb13, however it apparently has some very old code in it...hmmmm.

[Kernel]Peas-&-Q's

So this forum was pretty barren so i wanted to spruce it up a bit, maybe give you guys some hope that development was going on? inspire someone to start working on something? if anyone has any questions on how this was made or wants to learn i suggest reading teh kernel script i include in all my sources, i am also always willing to offer assistance to anyone wanting to learn
anyways...
this is a stock kernel, does nothing more than change the name of your kernel version in your about phone im trying to merge in some of the oc stuff from my sgs3 kernel but things arent matching up correctly.. might need someone to test what ive got in a future version, for now just enjoy your first source built kernel
Download
CWM Flashable
source​

reserved for pictures of kittens and pancakes

Very nice

shabbypenguin said:
this is a stock kernel, does nothing more than change the name of your kernel version in your about phone im trying to merge in some of the oc stuff from my sgs3 kernel but things arent matching up correctly.. might need someone to test what ive got in a future version, for now just enjoy your first source built kernel
Click to expand...
Click to collapse
I'm willing to test and if you've included a script that'll build a kernel with source I'll start fiddling tonight to see what I can find/do.

KitsunePaws said:
I'm willing to test and if you've included a script that'll build a kernel with source I'll start fiddling tonight to see what I can find/do.
Click to expand...
Click to collapse
you need to modify the script to fit your install and have the ramdisk in the place it points since have all my kernel source in separate folders. and all the ramdisk files in the ramdisk folder.

OK, excuse my n00bness - but how do you create a flashable ZIP out of the boot.img? I am rolling kernels, but unsure of what to do with the resulting boot.img...
I see others say "just take the latest flashable zip for your device and modify" - but there are no other flashable zips of only the kernel... hum.
Thanks!
Edit - I think I'm getting the hang of it... hold please for a new kernel

arrrghhh said:
OK, excuse my n00bness - but how do you create a flashable ZIP out of the boot.img? I am rolling kernels, but unsure of what to do with the resulting boot.img...
I see others say "just take the latest flashable zip for your device and modify" - but there are no other flashable zips of only the kernel... hum.
Thanks!
Edit - I think I'm getting the hang of it... hold please for a new kernel
Click to expand...
Click to collapse
added cwm zip to the OP for ya to kang ;P