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.
I have the same problem as this Christoph21x in post# 3347 in this thread
[Utility][2.9.9][07/19] Auto-Patcher (4.2.2) but they won't let me post there yet, so I'm asking my question here.
I'm running the stable CM 10.1.2, and when I try to flash the openpdroided CM 10.1.2 file, the recovery flashes it in an instant, and reboots. I don't think its flashing at all. Pdroid manager says that pdroid core wasn't found.
Oh, and where can I find the .exe file for the autopatcher that does this work? ApG Autopatcher. All the links I can find seem to go here: Kobik's Files The autopatcher fails to update from 2.6.0.1 which is given at the link to the latest 2.9.935 and I can't find anywhere to download the .exe. The latest files are on Github, but I don't know how to make an exe file out of it. The autopatcher says it can't fine Git on my computer but I installed it.
I've obtained the original Autopatcher off Github and these are the instructions:
Auto-Patcher
authored by pastime1971 and mateor(od)
A smali patcher that ports mods and themes across roms and devices. Extracts, decompiles/unpacks, patches, recompiles/repack, and outputs a flashable zip.
Requirements for execution
-jdk, cpio, patch
Designed to run on Linux, OSX and Windows (using Cygwin)
The main script expects the patches and patch_tools folders to be compressed. pastime has whipped up a script that gets you ready to use the program:
$./batch.sh
For usage and patch availability, place a rom.zip into this directory and try
$./auto_patcher <ROMNAME>.zip -h
I don't know what this means? Am I to type the bolded parts into Windows command line? I don't have much experience with command line, can someone run me through this?
******* Hi all ********I have developed this little tool containing a few utilities for our Xperia devices
Xperia_kerneltool
Overview
I created this tool to automate the process of kernel compilation for our beloved Xperia devices..In the process i have added a few more utilities like TA partiton backup.
-After completion I added a lot more features like building Cyanogenmod for any device..Kernel tools for a few more devices EFS partition backup..Git tools etc and made a multitool. If you are interested in that multitool then head over to my multitool thread
dark_multitool1.0
Features
-Sony Kernel
Unpack Kernel Source
-Create zImage of various devices(any Xperia)
-Extract kernel.sin from ftf file
-Unpack kernel.sin(to get zImage and ramdisk)
-Make dt.img(For Xperia Z1 and Z ultra)
-Make kernel.elf or boot.img depending on device
-Download toolchains
-Unpack boot.img to get zImage and Ramdisk
-Unpack or Repack ramdisk
-Build zImage for a generic kernel(Experimental)
-Backup TA partition for Sony(By dd Method only)
How to install??
Download the tar.gz file from the link above..Place it in your home directory and run the following command in your terminal
tar -xjvf xperia_kerneltool.tar.gz
How to run it??
cd to the folder xperia_kerneltool and type ./menu in your terminal and execute
This tool is only for any linux based distro(Ubuntu,fedora etc) atm and i dont know if it will work in cygwin
You can install vitualbox and install ubuntu or any other linux based distro to use the tool if you are running windows
Credits
-xda and its wonderful devs for teaching me everything
-Doomlord for his exceptional threads and tutorials on Xperia devices
-Rickwyatt and Rekoil for Ta partition backup tutorial for Xperia
-Google.com
If i have forgotten anyone then please let me know
Donations
Running a 512 mb laptop with a semi crashed hard disk.....So any kinds of donations are welcome if you like the tool
>Just donate to my email ID : [email protected]
>I am from India..so personal payment wont work
>Select buy me goods/services and it should work
>You can donate via tool as well.....
Mods : Please Move the thread if its in the inappropriate section
Updates
-I will keep the thread updated with the latest tool and you can also update the tool through the tool itself
FAQs in the second post
Changelogs in the third post
XDA:DevDB Information
Xperia_kerneltool, a Tool/Utility for the Sony Xperia Acro S
Contributors
Dark Wraith
Version Information
Status: Alpha
Created 2013-12-10
Last Updated 2013-12-10
Reserved
FAQs
>Why is it giving errors while compiling zImage for Xperia devices????
Answer : You need to add the various makefile and defconfig fixes for the toolchain to work properly
Please refer to this excellent thread by Doomlord for various fixes
http://forum.xda-developers.com/showthread.php?t=2447310
>TA partition doesn't work properly
Answer : Please remember to specify the memory block correctly. If you still get an error then please tell me the error so that i can check if the error is from the tool's end
>How to add a toolchain????
Answer : Add it under android_toolchains folder in your home directory
Open the tool and navigate to toolchain_selector script under scripts folder
Add the toolchain name and the correct path as given there in the following format
toolchain_name[the number after the last toolchain name]=
toolchain_path[the number after the last toolchain path] =
>How to clean your kernel work directory?
Answer ; Navigate to the kernel work directory : make clean
I will incorporate this in the next release
>Download toolchains or update tool doesnt work
Answer : make sure you have the git package installed.
Bugs and Suggestions
Please let me know
Reserved
Where is the download link?
juppi said:
Where is the download link?
Click to expand...
Click to collapse
Umm..under download tab..dont download this. Download dark multitool. Its there in my signature
Sent from my Micromax A110 using xda app-developers app
hello everyone
can anyone please patch any cm 11/11.1 xperia arc kernel for 0% battery error..
if you know how to build a kernel please make one patched kernel for me..
i have searched the thread but there is no cm 11 kernel patch.
i know about this thread but can't compile a kernel
http://forum.xda-developers.com/showthread.php?t=1312398
Compile your own version
This are simplified steps. If you dont know how to do, search in the forum.
- First, download the stock kernel source for Xperia (watch out for the correct version), or the sources for your custom ROM you want to use if its not compatible with stock kernel. The developer thread of dev Kalled from Sony (search on developer thread) has some instructions on how to compile the kernel.
This is the direct link to download Sony stock kernel sources:
http://developer.sonymobile.com/downloads/opensource/
- For the ARM compiler, download the CodeSourcery arm eabi compiler version 2010q1.
https://sourcery.mentor.com/sgpp/lit...al/release1294
- Install the compiler on Linux (You can use a virtual machine if you have Windows - use Virtual Box or VMWave Player, both are free for home use).
- Overwrite the bq27520 driver source code with the patched driver from this thread.
- Next, follow the guide on Kalled thread to select phone version and compile the Kernel.
- In the end of compilation, you get a zImage file, that is YOUR Kernel. Congratulations.
- You need a ramdisk. If you are targeting a custom ROM, get a ramdisk compatible with your custom ROM. Also, you can go to DoomLord thread about ramdisk and get a ramdisk suitable for your building. Or generate/use your own ramdisk if you know how. If you use other's ramdisk, give theirs credit.
- With kernel image and ramdisk, generate the file boot.img using mkbootimg tool from Android SDK, or abootimg tool from kubuntu repositories.
- If you choose to use mkbootimg, download a compiled version of mkbootimg, or compile your own version from Android SDK.
- Now you have a boot.img file. Flash it on your phone using fastboot and you are done.
KERNEL I WANT IT TO BE PATCHED
http://www.mediafire.com/download/3o9w31gni49fz4t/11DarkAnzu20140320.img
I HAVE ATTACHED WHAT'S NEEDED(PATCH TO BE REPLACED)..
PLZZ ANYONE HELP..
Hope I'm not too late in posting this message to any devs or learning devs for the T2U. I've patched up my C3 stock kernel and confirmed that it's working as intended so I'm sharing my sources with you as we share the same CPU and firmware.
My original thread (do not flash this, it is built for the C3 and not T2U): https://forum.xda-developers.com/so.../kernel-manjuu-kernel-sony-xperia-c3-t3564190
My kernel source: https://github.com/AngryManjuu/19.4.A.0.182_kernel
For those learning how to compile, here's a few things you need to know:
1. I used this guide from XDA University.
2. That guide is using a very old toolchain, so I used this toolchain which is optimised for our CPU (Cortex-A7) and the latest NDK version, 13b.
3. Be sure to build your kernel using yukon_tianchi_defconfig found in /arch/arm/configs/.
4. You will get build errors, just double-check them by referring to my commits starting on 24 Feb 2017.
5. I'm not sure if dual sim is supported.
6. No I won't build for T2U, but you're welcome to use this thread if you have questions on building.
7. This tool will help you pack your zImage into a boot.img. Please use the original stock boot.img (you can use TWRP to backup and get it from there) to unpack and repack always otherwise your kernel won't boot.
8. There is no flashable zip, the boot.img is the kernel itself so just use fastboot to flash it.
I am interested, in case there is something ready about it could make available ??