Develop Bugs

[GUIDE] dsixda's Android Kitchen - Now with Galaxy S support (Windows/Linux/Mac)

dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
​
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers, and to prevent confusion, please only discuss Samsung Galaxy S in this thread!
Most of all, have patience, take your time and enjoy!!

thanks for info mate exactly wat im looking for
cheers

Thx for this. Working very well.

Very nice guide

Just what i was looking for great
Sent from my GT-I9000 using xda premium

Thanks works very well! *5 stalls *

So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary

Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.

dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?

I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.

dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio

CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?

krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?

Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?

bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.

dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!

I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.

There are problem with kernels. I can't change?

is this supported by the sidekick since it has similiar specs to the samsung vibrant?

xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.

[ROM] AT&T Stock Properly De-Odexed LG1 OTA System...

This is mostly for new devs that want a stock build to work with, or just want to use the latest files & firmware version with their unlocked & rooted device.
All of the stock files are in this rom. The only changes made are busybox, SuperSU (Faster responses than traditional SU in my humble opinion), & I tore a lot of the apks down to java & applied diffpatches from the OTA update to all applicable apk & jar files, De-Odexed 100% & zip aligned. This currently includes the stock rooted kernel & will also work with the kernel by NunHugger (which supports init.d & custom boot images). You can easily change kernels with WinRAR or WinZip by making certain that "no compression" is selected & then drag & drop new boot.img to the root of the zip.
Also in the rom are the newer camera binaries & the other fixes from the AT&T LG1 OTA.
I did change the GoogleQuickSearchBox.apk so that on-device searches are still possible.
Rom include latest SuperSU & a working busybox 1.20.2 build.
Other than that, this is a fully bloated & stock AT&T rom & contains the stock rooted kernel. If you would like init.d support or anything else added, just let me know. I don't believe in init.d, & personally believe in editing xml's or boot init files to accomplish init tasks, but I'll add if desired. I am working on modding the LG1 kernel to have UV/OC function, but other than that, not much else.
This will
I am working on applying the diff patch to the kernel source, so that the kernel will match the LG1 system. However, I am having trouble with occasional bootloops when battery is under 30%. Could be the source, but most likely it is the fact that I haven't played with 100% stock source much, let alone Samsung source.
At any rate, do what you will with this. It is there to do with as you like, or not...
MD5: 1474aaffe7c178f939498da3a87469e3
Link: https://docs.google.com/open?id=0Bxxb003sdLoJZS1kUDJYcnVaXzg
*I will add a second link with updated apk's so that no google play updating is needed.
UPDATE: New version with most of the frequently updated apps located in Data/App to avoid duplicates & allow users to uninstall.
MD5: af4381d027abaec2e96828aa2799037f
Link: https://docs.google.com/open?id=0Bxxb003sdLoJNkFhSFB4M0N5ZUk
***Devs - Anyone familiar with Sammy source & willing to provide any assistance in patching the ALEM Kernel source to ALG1, it would be appreciated!

_just in case....

Am I missin something or where is the link to download - I like having a back up of the latest Stock "just in case' -
Oh - I see this is a fairly recent post - is the "upload" still processing?

Waiting for this as well.
Sent from my SGH-I747M using xda premium

I should lock this is but ill give you the benefit of doubt.

Mr.Highway said:
I should lock this is but ill give you the benefit of doubt.
Click to expand...
Click to collapse
What, a 9 hour upload time is excessive?

RampageRR said:
What, a 9 hour upload time is excessive?
Click to expand...
Click to collapse
Yes

GSLEON3 said:
This is mostly for new devs that want a stock build to work with, or just want to use the latest files & firmware version with their unlocked & rooted device.
All of the stock files are in this rom. The only changes made are busybox, SuperSU (Faster responses than traditional SU in my humble opinion), & I tore a lot of the apks down to java & applied diffpatches from the OTA update to all applicable apk & jar files, De-Odexed 100% & zip aligned.
Also in the rom are the newer camera binaries & the other fixes from the AT&T LG1 OTA.
I did change the GoogleQuickSearchBox.apk so that on-device searches are still possible.
Other than that, this is a fully bloated & stock AT&T rom.
I am working on applying the diff patch to the kernel source, so that the kernel will match the LG1 system. However, I am having trouble with occasional bootloops when battery is under 30%. Could be the source, but most likely it is the fact that I haven't played with 100% stock source much, let alone Samsung source.
At any rate, do what you will with this. It is there to do with as you like, or not...
***Devs - Anyone familiar with Sammy source & willing to provide any assistance in patching the ALEM Kernel source to ALG1, it would be appreciated!
Click to expand...
Click to collapse
Were is the link ??

So
what happened? Waiting...

LOL...Damn T1 line went down, traffic was bad & forgot when I got home. :silly:

1st in after the link lol. Thank you for your contribution look forward to trying it out!
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

So can you flash a different kernel like ktoonez just using cwm?

Yessiree.
Any kernel in the AT&T section I have tried so far has worked fine.
And if anyone wants, I can remove the debugging crap from all of the jars & apks to trim the files down further.

So the modem didnt change? Mine is still the same just curious
Edit: my bad forgot its just ota and just patches on the side note why no just make flashable zip of the removed apk if ever you debloat the rom
Sent from my SAMSUNG-SGH-I747 using xda premium

remove the debugging crap!
GSLEON3 said:
And if anyone wants, I can remove the debugging crap from all of the jars & apks to trim the files down further.
Click to expand...
Click to collapse
Actually - yes, please do and share! We're all after efficiency and optimized stock experience.

Curious as to why you didn't debloat this?

tomween1 said:
Curious as to why you didn't debloat this?
Click to expand...
Click to collapse
It is really meant to be a base for other's that wish to begin learning to cook. That way there is a base rom that is 100% stock for them to add to or deduct from as they choose. However, if you wish, I can do a de-bloated version. I have a new version as well, that still has bloat, but most of the frequently updated apps are in data/app & named so they are properly handled by updates.

Is there any consensus as to what is "Debloated" besides removing the AT&T crude? I usually remove gmail, I don't need two email clients, Flipboard, is gone, awww heck, I'll just do whatever & if ya'all want something back I'm sure I'll hear it.

GSLEON3 said:
It is really meant to be a base for other's that wish to begin learning to cook. That way there is a base rom that is 100% stock for them to add to or deduct from as they choose.
Click to expand...
Click to collapse
Just like the one I released. Only this is based on patches from the newer OTA.
Sent from my SAMSUNG-SGH-I747 using xda premium

GSLEON3 said:
Is there any consensus as to what is "Debloated" besides removing the AT&T crude? I usually remove gmail, I don't need two email clients, Flipboard, is gone, awww heck, I'll just do whatever & if ya'all want something back I'm sure I'll hear it.
Click to expand...
Click to collapse
Well if you do a de-bloated version, anybody that wants the app's you've pulled can pull them from your first one and install what they want. Also thank you

[APP] Offline Kernel Repack Beta!

Hi guys,
As nowadays I rely lesser on an x86 workstation and internet where possible, I need a way to be able to repack kernels with the proper ramdisk so that I can flash on my tablet/phone without worrying about incompatible ramdisk or without losing the ramdisk mods. A short workflow of the app:
You provide app with the original boot.img which has the proper ramdisk, and also the replacement boot.img with the new kernel
Click <Repack!>: Poof! A new boot.img with the proper ramdisk and new kernel is created for you
But of course, the app can even find boot.img in update zips and also replace boot.img in update.zips. What this mean is that you can:
Provide your original kernel update zip, and also your replacement kernel update zip along with the modules
Click <Repack!>: Poof! A new update zip with the boot.img that has proper ramdisk and new kernel along with the modules is created for you
In other words, NO MORE USING UPLOADING YOUR FILES TO AN ONLINE AUTO KERNEL REPACK... OR NEEDING A PC JUST TO REPACK YOUR KERNEL. IT'S REVOLUTIONARY!
Why is it a beta?
I haven't actually fully tested the app. It might break your ROM (which in that scenario, just flash back your original kernel). In other words, this app is FOR EXPERT USERS ONLY!
Try it, and report bugs or issues and I'll fix it.
Download:
v0.1: Dropbox Link
P.s. I need a Holo icon designer for this app!
P.s.s. App Permission INTERNET and ACCESS_NETWORK_STATE is for AdMobs
Screenshot attached

[Q] Building CM10.2.0 For S4 Mini LTE

Hello All,
This may be in the wrong place so if it is, I am sorry, anyway to my question I'm trying to build CM for my S4 Mini LTE Serranoltexx everything was going fine until I got this message after running extract-files.sh
Code:
Extracting /system/lib/egl/libGLESv2S3D_adreno200.so ...
remote object '/system/lib/egl/libGLESv2S3D_adreno200.so' does not exist
Now after adding "libGLESv2S3D_adreno200.so" (if you search Google for it it's the top github link) I managed to get it to build the actual .zip and it does flash properly but it doesn't seem to have the correct graphics drivers (I thought this process wouldn't work and I was right), the guide on the how to build it doesn't help with this problem either so any help would be extremely appreciated
I've attached the logcat for reference (if it's needed) as a .docx file as the .txt file was 1.1mb and because I don't have a pro account on pastebin.

The problem with newer Android versions is that if often require new libraries which are not available in stock rom, so the extract method is actually not very useful unless we have a stock rom of the same version we are building for. To bypass this issue we use libraries from other phones that have the matching Android version. I suggest using the blobs that's on TheMuppets github, as those are up to date.
https://github.com/TheMuppets/proprietary_vendor_samsung

Need help compiling sedikernel (or any kernel)

Hello,
In order to debug the bluetooth problem, I'm trying to compile a kernel for the Captivate Glide. I can't get it to boot properly.
@steadfasterX 's SediROM is the highest-version ROM I know of on which bluetooth works so I've got it installed (version 2.1.2) on the phone.
The steps I've taken so far:
1. I have sedikernel from https://github.com/steadfasterX/kernel_samsung_i927 at commit 088aa4109ad144c583f32da5ffba7bac200f0575
2. I copied /proc/config.gz from a running phone, which contains CONFIG_LOCALVERSION="-sediKERNEL-v1.0", ungzipped it and saved it as .config . Haven't changed anything in it yet.
3. I ran `make CROSS_COMPILE=arm-linux-gnueabihf- zImage` (also tried arm-none-eabi- (both from Debian Jessie) as well as ~/Android/Sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi- from the NDK)
4. I also made a TWRP backup of the boot partition, and used split_bootimg.pl from William Enck to split it into a kernel and initrd
5. I then ran mkbootimg with the initrd extracted in step 4 and the kernel obtained in step 3 in arch/arm/boot/zImage
6. Finally I flashed this new boot.img onto the phone with odin (Heimdall, specifically)
I see the white "SAMSUNG" logo (which is normal when booting) with a yellow-triangle with an exclamation mark in it. No further boot stage happens (no bootanim from sediROM). If I re-pack the original kernel with bootimg and flash that via odin, then after the next boot the yellow triangle changes into a blue one and sediROM boots correctly.
I'm a bit stuck at the moment, not sure what's going wrong there. Probably the kernel panics for some reason. Is there a way to read the kernel boot messages before android starts? Any help would be greatly appreciated.
Thanks!

Successful!
Thanks to a lot of help from @steadfasterX on IRC I finally managed to compile a working kernel
Here's a list of steps I had to follow in addition to https://github.com/steadfasterX/android_device_samsung_i927/blob/sediROM_CM-ICS/README.md :
1. as discussed on IRC, `repo sync` was not finding a branch. Needed to add
Code:
revision="refs/heads/ics-release"
in .repo/manifests/default.xml in the line with
Code:
CyanogenMod/android_vendor_qcom_opensource_v8
2. I removed the spurious comma in device/samsung/i927/cm.dependencies
3. In device/samsung/i927/, I changed vendorsetup.sh to point to vendorsetup.sh.nopatching rather than .patching (none of the patches could be applied)
4. lunch target was therefore the one with -eng, not -userdebug
5. I installed java 6 manually (didn't have sudo)
6. I installed schedtool
7. I adjusted the path to Java and my toolchain in build_sediROM.sh (taken from https://github.com/steadfasterX/android_buildtools )
8. I downgraded GNU make from 4.0 to 3.81
9. I installed linux-headers and created a symlink from /usr/include/asm-generic to /usr/include/asm
10. I changed the toolchain prefixes in device/samsung/i927/BoardConfig.mk to have 4.4.3 rather than 4.7
11. I built with
Code:
BUILDID=samsung/i927 LOKIFY=0 ../android_buildtools/build_sediROM.sh bootimage
12. I used the original ramdisk I had extracted from sediROM's boot image, rather than the one that was built (we discussed this on IRC too)
This got me a working kernel, yay

uukgoblin said:
Thanks to a lot of help from @steadfasterX on IRC I finally managed to compile a working kernel
Here's a list of steps I had to follow in addition to https://github.com/steadfasterX/android_device_samsung_i927/blob/sediROM_CM-ICS/README.md :
1. as discussed on IRC, `repo sync` was not finding a branch. Needed to add
Code:
revision="refs/heads/ics-release"
in .repo/manifests/default.xml in the line with
Code:
CyanogenMod/android_vendor_qcom_opensource_v8
2. I removed the spurious comma in device/samsung/i927/cm.dependencies
3. In device/samsung/i927/, I changed vendorsetup.sh to point to vendorsetup.sh.nopatching rather than .patching (none of the patches could be applied)
4. lunch target was therefore the one with -eng, not -userdebug
5. I installed java 6 manually (didn't have sudo)
6. I installed schedtool
7. I adjusted the path to Java and my toolchain in build_sediROM.sh (taken from https://github.com/steadfasterX/android_buildtools )
8. I downgraded GNU make from 4.0 to 3.81
9. I installed linux-headers and created a symlink from /usr/include/asm-generic to /usr/include/asm
10. I changed the toolchain prefixes in device/samsung/i927/BoardConfig.mk to have 4.4.3 rather than 4.7
11. I built with
Code:
BUILDID=samsung/i927 LOKIFY=0 ../android_buildtools/build_sediROM.sh bootimage
12. I used the original ramdisk I had extracted from sediROM's boot image, rather than the one that was built (we discussed this on IRC too)
This got me a working kernel, yay
Click to expand...
Click to collapse
its really long guide. You have to replace kernel modules, wifi wouldnt work without modules.
Imho best is compile kernel, modules, replace zImage + modules in this
file and flash from recovery. You dont need to compile whole android just the kernel, you dont need java and other special things, this method is much more faster.

bubor said:
its really long guide. You have to replace kernel modules, wifi wouldnt work without modules.
Imho best is compile kernel, modules, replace zImage + modules in this
file and flash from recovery. You dont need to compile whole android just the kernel, you dont need java and other special things, this method is much more faster.
Click to expand...
Click to collapse
You are right for the kernel but we discussed on IRC to build ram disk too then you need all that stuff but most important he wants to build CM too.
However I'm always a fan of making it right so building a ram disk is the correct way of creating a bootimage. But to start its ok replacing kernel and modules first.
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
correct way is rebuild whole android, and reflash everything, wipe data/cache
You dont want to make new ramdisk without replace system. System and ramdisk bound together.
I hope you find something, and fix bluetooth or voip audio.
good luck

bubor said:
correct way is rebuild whole android, and reflash everything, wipe data/cache
You dont want to make new ramdisk without replace system. System and ramdisk bound together.
I hope you find something, and fix bluetooth or voip audio.
good luck
Click to expand...
Click to collapse
Well no and yes. I build kernels including ram disk without building system. This is not necessary as long both are compatible.
But you are right that booting fails when system and ram disk are not compatible so the correct way depends
However @uukgoblin I hope you get the fix you want :fingers-crossed:
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Well no and yes. I build kernels including ram disk without building system. This is not necessary as long both are compatible.
But you are right that booting fails when system and ram disk are not compatible so the correct way depends
However @uukgoblin I hope you get the fix you want :fingers-crossed:
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
would you tell me an example when kernel doesnt compatible with ramdisk but kernel does compatible with system?

bubor said:
would you tell me an example when kernel doesnt compatible with ramdisk but kernel does compatible with system?
Click to expand...
Click to collapse
No no my friend that's not what I said. :cyclops:
I meant if you have CM 9 as system you can build a boot image which includes kernel and a CM9 based ram disk without building cm9 system again. :laugh:
.
Sent from my LG-H815 using XDA Labs