• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

dsixda

Inactive Recognized Developer
Nov 1, 2007
9,588
5,306
Ottawa
dsixda's Android Kitchen - Now for Samsung Galaxy SII GT-I9100

Compatible with Windows (Cygwin) / Linux / Mac OS X

The following is a guide to assist you with creating your own Samsung Galaxy S2 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.

For the benefit of other readers and to prevent confusion, please stay on topic and only discuss Samsung Galaxy S2 in this thread!

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. The kitchen has been designed almost exclusively for HTC devices, although many people have had success using it with other manufacturers' ROMs. Recently I bought a Samsung Galaxy S2, and of course, I wanted to take control and create my own custom ROMs. However, ROMs for this device are totally different from those that I had worked on before, and so I decided to take on the project of supporting this device in the Android Kitchen. So, as of version 0.175, you can now create your own ROMs with the kitchen.

First, I'd like to thank pulser_g2 of Villain ROM for voluntarily helping me during his vacation to get started on this SGS2 project. Secondly, a big thanks to Noonski for testing and providing feedback.



PROCEDURE


IMPORTANT: For this guide to work, you need one of the original Exynos-based Galaxy S2 variants, including the Galaxy Note GT-N7000. Unfortunately this means there is no support for the I9100G, since it uses a different chipset. For the Qualcomm-based AT&T Skyrocket, T-Mobile SGH-T989, Telus Galaxy S2 X (SGH-T989D) and other variants, please follow this thread instead.

  1. First, you need a rooted Samsung Galaxy S2 with a ClockworkMod custom recovery.
  2. 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: To verify your variant of the Galaxy S2 works in the kitchen, read this post.
  3. Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S2, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
    • Stock firmware:
      • factoryfs.img, cache.img, zImage, hidden.img (if it exists), and modem.bin (optional)
      • TAR file containing factoryfs.img, cache.img, zImage (and optional modem.bin)
      • TAR.MD5 file - Same as above but must be renamed *without* the MD5 part in the file name
      • ZIP file containing factoryfs.img, cache.img, zImage (and optional modem.bin)
    • Custom ROM:
      • ZIP file created by the kitchen from the stock firmware (other ROMs such as CyanogenMod may use a different file structure that is incompatible with the kitchen!)
    • Nandroid backup from ClockworkMod recovery
      • system.img and boot.img
      • system.ext4.tar and boot.img
  4. 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):
    1. Start the kitchen with: ./menu
    2. Create a working folder (by choosing your base ROM)
      • If you used a stock factoryfs.img but then didn't include the cache.img, then you have the option to add a cache.img later using the Extract CSC script in the Advanced menu's 'Plugins' section.
    3. Optional: Add a rooted kernel (zImage) to the base of your working folder
      • If your working folder currently has the stock kernel (zImage), you should replace it with the CF-Root kernel (or any other custom rooted kernel) which must match the stock ROM's Android OS version. Just replace the stock zImage with this zImage any time before you build the ROM. Otherwise, if you keep the stock kernel you will lose access to ClockWorkMod recovery!
      • OR, you can create a ROM without a zImage and thus keep the existing kernel on your device, although you must ensure the kernel is compatible with the ROM!
    4. 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.
    5. Root your ROM (Not required if you are using the CF-ROOT zImage)
    6. Add Busybox (Not required if you are using the CF-ROOT zImage)
    7. Disable boot sounds (if you find the Samsung starting sound a bit annoying)
    8. In the Advanced options menu: De-odex your ROM
      • If you have trouble deodexing the leaked 4.0.3 ROMs, read this post for help.
    9. Build ROM
      • The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
  5. 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.


Direct your questions to this thread, please do not PM me for tech support. Most of all, have patience, take your time and enjoy!!



USEFUL LINKS

 
Last edited:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
Reserved For something Fun.....
attachment.php

All the hiccups I had where because I was to anxious to read.
For Real Newbs setting up Sygwin on Windows is harder then baking the rom, I enjoyed myself thanks for that and thanks for your hours of work on this project since the beginning it already gave me great hours with my desire.
Enough with the ass kissing :)
 

Attachments

  • Brow.jpg
    Brow.jpg
    17.5 KB · Views: 68,150
Last edited:

D.O.C

Inactive Recognized Developer / Retired Senior Mod
Jun 24, 2006
3,141
4,002
42
Thankyou!...many thanks bro...nice job!
 
  • Like
Reactions: dsixda

clavicle

Senior Member
Sep 16, 2009
469
99
Simla
Wonderful news, I always wanted to learn some cooking and you have made my life simpler by showing me the way. thanks a lot man ;)
 
  • Like
Reactions: dsixda

dsixda

Inactive Recognized Developer
Nov 1, 2007
9,588
5,306
Ottawa
I've now uploaded version 0.177 of the kitchen, which takes care of a few issues that came up while adding the SGS2 updates to the kitchen. Please visit the main kitchen thread to download the latest version. Release Notes are found in Post #2 of that thread.

Enjoy
 
  • Like
Reactions: stian230

stian230

Senior Member
Oct 29, 2009
1,425
1,836
Nesttun
I used xxkh3 stock firmware removed all bloat ware removed all crap I didn't Ned as ringtones and wallpapers. Added my own ringtones/wallpapers/transition effect and jkay themes . Removed ugly yellow triangle in boot logo added my personal logo and made a ugly dock for the launcher..
I used about one hour .
tB2ANEI
1rfunsL
TA8rRlP


I've been using this kitchen since I got my N1 and it's the best ROM kitchen no discussion..

thanks Dsixda.
 
Last edited:
  • Like
Reactions: dsixda

dsixda

Inactive Recognized Developer
Nov 1, 2007
9,588
5,306
Ottawa
By the way, to verify your Samsung Galaxy S2 variant works with the kitchen, open your device's /system/build.prop file and check the ro.product.device value. If the value doesn't exist under the kitchen's tools/samsung_files/sgs2_variants/ folder then just create a file there with same name.
 

sendhiloo7

Senior Member
Sep 28, 2008
1,294
387
Chennai
OnePlus 9 Pro
By the way, to verify your Samsung Galaxy S2 variant works with the kitchen, open your device's /system/build.prop file and check the ro.product.device value. If the value doesn't exist under the kitchen's tools/samsung_files/sgs2_variants/ folder then just create a file there with same name.

Hi dsixda,

Thanks to see here. i was used your ROM for HTC ELFin..

I am very happy :)..

Now i have created a ROM for SG II, Where i will remove/add application in this kitchen.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 111
    dsixda's Android Kitchen - Now for Samsung Galaxy SII GT-I9100

    Compatible with Windows (Cygwin) / Linux / Mac OS X

    The following is a guide to assist you with creating your own Samsung Galaxy S2 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.

    For the benefit of other readers and to prevent confusion, please stay on topic and only discuss Samsung Galaxy S2 in this thread!

    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. The kitchen has been designed almost exclusively for HTC devices, although many people have had success using it with other manufacturers' ROMs. Recently I bought a Samsung Galaxy S2, and of course, I wanted to take control and create my own custom ROMs. However, ROMs for this device are totally different from those that I had worked on before, and so I decided to take on the project of supporting this device in the Android Kitchen. So, as of version 0.175, you can now create your own ROMs with the kitchen.

    First, I'd like to thank pulser_g2 of Villain ROM for voluntarily helping me during his vacation to get started on this SGS2 project. Secondly, a big thanks to Noonski for testing and providing feedback.



    PROCEDURE


    IMPORTANT: For this guide to work, you need one of the original Exynos-based Galaxy S2 variants, including the Galaxy Note GT-N7000. Unfortunately this means there is no support for the I9100G, since it uses a different chipset. For the Qualcomm-based AT&T Skyrocket, T-Mobile SGH-T989, Telus Galaxy S2 X (SGH-T989D) and other variants, please follow this thread instead.

    1. First, you need a rooted Samsung Galaxy S2 with a ClockworkMod custom recovery.
    2. 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: To verify your variant of the Galaxy S2 works in the kitchen, read this post.
    3. Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S2, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
      • Stock firmware:
        • factoryfs.img, cache.img, zImage, hidden.img (if it exists), and modem.bin (optional)
        • TAR file containing factoryfs.img, cache.img, zImage (and optional modem.bin)
        • TAR.MD5 file - Same as above but must be renamed *without* the MD5 part in the file name
        • ZIP file containing factoryfs.img, cache.img, zImage (and optional modem.bin)
      • Custom ROM:
        • ZIP file created by the kitchen from the stock firmware (other ROMs such as CyanogenMod may use a different file structure that is incompatible with the kitchen!)
      • Nandroid backup from ClockworkMod recovery
        • system.img and boot.img
        • system.ext4.tar and boot.img
    4. 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):
      1. Start the kitchen with: ./menu
      2. Create a working folder (by choosing your base ROM)
        • If you used a stock factoryfs.img but then didn't include the cache.img, then you have the option to add a cache.img later using the Extract CSC script in the Advanced menu's 'Plugins' section.
      3. Optional: Add a rooted kernel (zImage) to the base of your working folder
        • If your working folder currently has the stock kernel (zImage), you should replace it with the CF-Root kernel (or any other custom rooted kernel) which must match the stock ROM's Android OS version. Just replace the stock zImage with this zImage any time before you build the ROM. Otherwise, if you keep the stock kernel you will lose access to ClockWorkMod recovery!
        • OR, you can create a ROM without a zImage and thus keep the existing kernel on your device, although you must ensure the kernel is compatible with the ROM!
      4. 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.
      5. Root your ROM (Not required if you are using the CF-ROOT zImage)
      6. Add Busybox (Not required if you are using the CF-ROOT zImage)
      7. Disable boot sounds (if you find the Samsung starting sound a bit annoying)
      8. In the Advanced options menu: De-odex your ROM
        • If you have trouble deodexing the leaked 4.0.3 ROMs, read this post for help.
      9. Build ROM
        • The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
    5. 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.


    Direct your questions to this thread, please do not PM me for tech support. Most of all, have patience, take your time and enjoy!!



    USEFUL LINKS

    8
    6
    Preserved...
    6
    As of version 0.215, I've added support for the recent Jelly Bean leak ROM. It fixes the /preload symlink issue everyone was having.
    5
    I have successfully managed to deodex Samsung ICS firmware. Choose API 15 it will deodex the system except Exchange.apk, Email.apk & MobileTracker.apk now tto deodex them we need to put the attached java.awt.jar into the framework folder but don't put it before or you will have issues deodexing other framework files. Use it when those three files are left behind.