ROM Galaxy ACE ACETJ

Pagi-pagi gini bingung juga mau posting apa, tapi saya rasa asaya ingin mempublikasikan ROM yang sudah saya buat, sebenarnya si ingin masih menyempurnakan ROM ini, tapi setelah saya mencoba memakainya, Insyallah tidak ada bugsnya ko.

I hope you have a partition in SD-Card, Terserah si mau dipartisi Ext berapa, yang penting di Partisi agar dapat menjalankan Link To SD dengan baik :) :)

Beberapa fitur yang bekerja pada ROM AceTj (ONLY COMPATIBLE WITH GT-S5830)

Boost Performance
SuperUser (Root)
SMS
Calender syncing is work now
Audio
Sensors
Full 2D/3D/HW acceleration
Camera/Camcorder
WiFi
BLN
Bluetooth
Browser
Live wallpapers
GPS (Use fasterfix to set your region)
Deep sleep
FM radio
Wifi and usb tether (using an app from Play store)
Optimize Wifi, GPS and Touchscreen
Link To SD
Dark Status Bar

Credit:
Dragonnn for his awesome fire Kernel
DXKT4

Link To Download:

HotFile





And all of those who are directly or indirectly contributed to this ROM. Please forgive me if I missed anyone.

My ScreenSoot:

Root, Unroot Galaxy ACE

Hayy All.. Tutorial Rooting And UnRoot Samsung GALAXY ACE GT-S5830 sebenarnya tidaklah sulit akan tetapi disini saya akan mencobamenjelaskan secara keseluruhan bagaimana cara agar kita dapat menemukan suatu permasalahan dalam proses rooting android anda.

Langkah permata yang harus diperhatikan adalah mengetahui system recovery yang ada pada gadget anda.

System Recovery pada android sebenrnya sama fungsinya seperti system recovery pada umumnya, akan tetapi pada android kita dapat melakukan proses ROOTING melalu System Rrecovery ini. dengan memasukan beberapa perubahan set permission pada file system pada OS android anda menggunakan Flashabel Zip.

Flashabel Zip itu sendiri terdiri dari beberapa applikasi yang harus kita instal kedalam system OS android anda yang disebut dengan ROOTING..

Berikut Penjelasan tentang Flashabel Zip yang kita butuhkan untuk melakukan proses ROOTING.

Flashabel Zip yang pertama adalah dengan memperbarui system recovery pada gadget anda. dengan masukan CWM, didalam file cwm sendiri terdapat recovery.img dan terdapat file CWM.apk dimana recovery.img berguna untuk menjalankan system recovery yang baru, yang nantinya kita gunakan untuk proses ROOTING yang lebih kompleks sedangakan file CWM.apk pada proses flashing nntinya file tersebut akan ditaru didalam folder system/app/ nah file ini juga sama fungsinya dengan recovery.img hanya saja CWM.apk itu dapat dijalankan dengan GUI pada smartphone kita. Menggukan beberapa action seperti:

mount("ext4", "EMMC", "/dev/block/stl12", "/system");
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/app/CWMManager.apk");
unmount("/system");
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
       write_raw_image("/tmp/recovery.img", "recoveryonly"),
       delete("/tmp/recovery.img"));

Setelah kita memperbarui system recovery kita barulah kita melakukan proses ROOTING yang pada initinya dengan mamasukan file superuser.apk pada system/app/

package_extract_dir("system", "/system");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 04755, "/system/xbin/ssh");
set_perm(0, 0, 04755, "/system/xbin/sqlite3");
set_perm(0, 0, 04755, "/system/xbin/busybox");

Semua file yang berda pada system/app/ memiliki permission 644.

Dan apabila sahabat semua ingin mengembalikan lagi kedalam keadaan semula maka kita membutuhkan Flashable Zip Unroot, Unroot ini nantinya akan mendelete beberpa file yang kita install pada proses rooting, akan tetapi tidak semau file ROOTING pada gadget memiliki semua file ini.

delete("/system/xbin/sqlite3");
delete("/system/xbin/su-v1");
delete("/system/xbin/su-v2");
delete("/system/xbin/su-v3");
delete("/system/xbin/su");
delete("/system/xbin/sh");
delete("/system/xbin/busybox");
delete("/system/app/Superuser.apk");

Masuk kedalam System Recovery adalah dengan menekan Home+Powerbutton pada Galaxy Ace Anda..

Berikut file-file yang dibutuhkan.

1. Update.zip
2. Root.zip
3. Unroot.zip

[TOOL] System App Pack

Hi all! I have write a tool for Windows with vb.net in order to provide an intuitive tool to create flashable archives from ClockWorkMode recovery containing system applications. You can also sign a .zip and make an update.zip with custom application and edit the updater-script!

REQUIREMENTS

• Windows
• .NET Framework (the latest release is recommended)

DOWNLOAD
SystemAppPack v1.2: here (directlink)
Mirrors: (only v1.0)
Mirror on NathanBookham's site (thanks to NathanBookham)
Mirror mediafire (thanks to matt96g)

HOW TO USE

1. Download the archive .zip and extract all the file in a single folder where you want;
2. Don't delete any files or folder;
3. Open SystemAppPack.exe;
4. Select what you want to do;
5. Copy the .zip in your sdcard;
6. Reboot phone in recovery mode and you can flash your own flashable .zip

FEATURES

• Choice app with checkbox
• Build of flashable archive
• Build of compressed archive that contain the applications
• Build of a folder that contain the applications
• Possibility to import local applications
• Sign .zip already created
• Control the space in /system
• Build of a custom update.zip and edit the upater-script
• Build of flashable archive with custom and own font

SCREENSHOT


CREDITS
DotNetZip team for their library

Sumber: http://forum.xda-developers.com/showthread.php?t=1876685

ADB Shell

This setting is available in android machine in following place Menu → Settings → Applications → Development

This options should be kept enabled only when you are a constant developer or you keep your handset connected to pc all the time. However this must be turned off before connecting to any non trusted machine.
Adb Shell root mode

This is one of the most dangerous setting of all. This setting allows adb shell to connect in root user mode. Effectively giving a root shell to whosoever gets usb connection to phone. Another tricky point about this setting is its activated only at boot time and during whole period of working the variable can’t be changed.

Also we need to keep this in mind that when this feature is enabled that means you don’t even need su binary to gain root access. You just need usb debugging to be enabled. Build.prop inside the ramdisk generally contains this value.

In order to check or modify the ramdisk you need to use following procedure. Location of build.prop : boot.img → ramdisk.cpio.gz → gunzip → un cpio → build.prop

Variable name : ro.secure Value : 0 = root , 1 = shell user If we look at this along with what was discussed in adb shell mode. We have a ready made root user shell which will give me full access to all files, flexibility to push and pull both from just about any level. In not so good hands this simple setting can cause a phone to lose all its important work.

Adb shell over wifi

Another variable which could be set to allow adb shell access. However this time access is over wifi network. Variable : service.adb.tcp.port = <tcp_port_no> To set this variable you can either place it in build.prop or use commandline #setprop service.adb.tcp.port=3355 This will mark port 3355 on phone to be usable to attach using adb. However in this case you need to restart adb service once. Combining this with above two settings and you have handed over your cell phone to one and all, while shouting in top of your voice : - PLEASE OWN ME. Note : this is a hypothetical attack as this is not yet a common habbit.

System permissions

In Android Devices, system partition is the most important partition which holds all the system critical files, as per general policy this partition is marked as RO i.e. readonly. However a general aftr market practice which is observed is to mark system partition as rw. The general use case is that by putting system in rw mode it is easy to work on modification of system data. The most harmful setting is if your ROM maker marks system with 777 i.e. rwx or read write execute permission for all users. When a system is marked with write permission it will allow a user to update / modify content of /system partition. Some of the crucial folders include /system/app or /system/bin. This permission is an open invitation to rootkits, malware, viruses and all simmilar items to start manhandling the device. Example in below scenario if some app gains root access they can modify any file in /system. However another variation is 777 for /system which effectively allows the whole world to modify the

Unpack, Repack boot.img, dan Edit

Unpacking boot.img:

Code:

$ mkdir -p unpack
$ tools/unpackbootimg -i boot.img -o unpack

Extracting boot.img-ramdisk.gz

Code:

$ mkdir -p unpack/boot.img-ramdisk
$ cd unpack/boot.img-ramdisk 
$ gzip -dc ../boot.img-ramdisk.gz | cpio -i
$ cd ../../

Packing a new ramdisk:

Code:

$ tools/mkbootfs unpack/boot.img-ramdisk | gzip > unpack/boot.img-ramdisk.gz

Create a new boot.img:

Code:

$ tools/mkbootimg --kernel unpack/boot.img-zImage --ramdisk unpack/boot.img-ramdisk.gz -o boot.img-repack --base `cat unpack/boot.img-base`

Convert rle to png:

Code:

$ tools/from565 -rle < COOPER.rle > COOPER.raw
$ convert -size 320x480 -depth 8 rgb:COOPER.raw COOPER.png

Convert png to rle:

Code:

$ convert -depth 8 COOPER-new.png rgb:COOPER-new.raw
$ tools/to565 -rle < COOPER-new.raw > COOPER-new.rle

NOTE:
For developers only, don't ask me for support! Solve your problems by yourself!

PASSWORD:
As usual: ketut.kumajaya

ATTACHED FILES

	boot.img-tools.rar - [Click for QR Code] (66.4 KB, 2831 views)
	blackhawk-tools.zip - [Click for QR Code] (282.5 KB, 1277 views)

.
Source: http://forum.xda-developers.com/showthread.php?t=1241005

Membuat ROM Galaxy ACE

For South East Asian users:
GT-S5830_GINGERBREAD.DXKT7.BLACKHAWK.zip (133.59 MB) (recommended)
GT-S5830_GINGERBREAD.DXKT5.BLACKHAWK.rar (133.66 MB) Password: ketut.kumajaya

For European users:
XWKT7.BLACKHAWK: GT-S5830_GINGERBREAD.XWKT7.BLACKHAWK.zip (138.33 MB)
Modem taken from XWKT7: GT-S5830_XWKT3_modem.zip (9.37 MB)

Incomplete locales (discontinued, just for my references):
DXKT5.BLACKHAWK_XWKT7_locales.zip (19.6 MB)
XWKT7.BLACKHAWK_DXKT5_locales.zip (18.34 MB)

Original post at kaskus.us

Features:

• Stock DXKT5/XWKT7, CSC XSE, CWM flashable zip
• Full deodexed
• Filesystem ext4 none journaling for all /system, /data, and /cache
• CF-Root b84 applied, inc. overclock kernel
• Full BLN support, BLN Control free version included
• DT a2sd applied
• Ext4 Manager included to maintain ext4 filesystem
• DXKT4 modem (from DXKT5 firmware) in CWM flashable zip

Instructions:

1. Connect your phone to your computer in USB Mass Storage mode
2. Copy GT-S5830_GINGERBREAD.DXKT5.BLACKHAWK.zip, GT-S5830_CWM-5.0.2.6.zip, and GT-S5830_DXKT4_modem.zip to your phone SD card
3. Reboot your phone to recovery mode
4. Flash GT-S5830_CWM-5.0.2.6.zip
5. Reboot your phone to recovery mode
6. Flash GT-S5830_GINGERBREAD.DXKT5.BLACKHAWK.zip
7. Flash GT-S5830_DXKT4_modem.zip (optional)
8. Format your /sd-ext partition
9. Reboot your phone
10. Select "DT: Auto start" option in Tweak Manager to turn on Darktremor a2sd script on boot
11. Reboot your phone, bootloop will occur several times during DT apps2sd activation for the first time
12. Deselect "DT: Auto start" option in Tweak Manager
13. Done

Note:
DXKT5 CSC: GLB, MM1, SIN, SMA, STH, THL, XEV, XME, XSE, XSO, XTC, XTE, XXV, and XSP
XWKT7 CSC: BGL, D3K, PKO, TRA, TOP, MOT, MSR, BHT, TMT, CMF, CNX, COA, CRG, VIM, TEM, RDS, MKO, BHO, AVF, TEB, MNO, HAT, PMN, VVT, ORO, OMX, MTL, ERO, EGL, TWO, ROM, SMO, TSR, NEE, SIM, and VIP

To apply your CSC, run sec_csc script over "adb shell" or Terminal Emulator or ConnectBot. For example, to apply CNX (Romania) sales code:

Code:

sec_csc CNX

Try to reboot your phone without data wipe first. If your CSC not applied, run again sec_csc with data wipe (Factory Data Reset).

If your CSC code does not exist in /system/csc, sec_csc will not be able to help.

Credits:

• koush, illarain, Grif_07, Lovetz for CWM recovery
• dsixda for Android Kitchen
• neldar for BLN support
• Chainfire for CF-Root
• GLa'DOS for Android Scribble 2.0 boot animation
• tkirton for Darktremor apps2sd
• Go Dev Team for Go Launcher Ex and Go SMS Pro
• Samsung and Qualcomm for Galaxy Ace with stable hardware and software
• Google for Android
• Microsoft for several patents on the Android 

Galaxy Ace Android Kitchen

1. Download the kitchen from here.
2. Copy system.rfs and CF-Root-S5830's boot.img (for ext4 filesystem support) to the kitchen's original_update folder, rename system.rfs to system.img.
3. Open up a terminal window, change to the folder containing the kitchen. Start up the kitchen by typing: ./menu
4. Select Option 1 to set up your working folder.
5. You can use Extract_SGS_CSC_from_cache.rfs plugin to extract csc.rfs file. Select Option 0 and then Option 24.
6. Merge the extracted csc.rfs to your working folder.
7. Clean up your working folder using my clean_system.sh script.
8. Copy format.sh script and mkfs.ext4 binary to your working folder.
9. Modify whatever you'd like in the kitchen.
10. Select Option 99 to Build your ROM, Interactive Mode, zipaligning.
11. Select the option of using an updater-script (Edify) instead of an update-script (Amend).
12. Overwrite updater-script and update-binary has been created under META-INF/com/google/android of your working folder using my updater-script and update-binary. Select to proceed with the change.
13. Continue the cooking process.

WARNING:
Using wrong update-binary or wrong updater-script command could brick your phone.

ATTACHED FILES

blackhawk-kitchen.zip - [Click for QR Code] (453.1 KB, 801 views)

Source: http://forum.xda-developers.com/showthread.php?t=1442889

Fungsi FTF Extractor

If you hang around Android development long enough, you’ll start running into file types you don’t normally deal with. While some are simply used because of user preference, others are used by OEMs as a sort of proprietary file—such as the SBFs used by Motorola. However at the end of the day, users will eventually have to learn how to deal with these files. One such file type is FTF, and it’s typically used on Sony Xperia devices. Now, users can extract FTF files and turn it into flashable zips.

While it is posted in the Xperia Mini, Mini Pro, Active and Ray forums, the method should be usable on pretty much any Sony Xperia device. Written up by XDA Forum Member Knight47, it requires a few applications—namely, FTF Extractor, 7zip, and some additional files to make it all work. Once everything is downloaded, the method is essentially simple.

In short, you unpack the system files and repack them with the proper files to make everything flashable. Namely, the kinds of files you’ll be adding are root files and the META-INF. After that, flash and be happy. This guide is potentially useful for pretty much anyone who has to deal with FTF files on a regular basis.

For the full tutorial, head to the original thread.

Applikasi Membuat Android

If you willing to learn to build custom ROM then you should have following things

• Basic Knowledge about handling Command Promt
• Basic Windows software knowledge
• PC with all tools properly installed
• And a mobile with bootloader unlocked

This tutorial is for "Windows OS (Windows 7 x64 in my case)" And Android 2.3+ OS (2.3.4 GingerBread in my case).
But Dxda Kitchen also supports Ubuntu/Linux and also can support Ice cream sandwich

In this whole post you will learn How To -

• Make custom ROM - Done
• Unpack .ftf packages - Done
• Use Cygwin - Done
• Setup Android Kitchen - Done
• Edit .apk files - Done
• Edit .jar files - Done
• Edit .9.png files - Done
• Rooting System - Done
• Writing scripts
• Making flashable zips - Done
• Porting apk software
• A2SD Techs
• Editing build.prop - Done
• Editing init.d tweaks
• Information of every customizable file
• Making Hosts
• apn configs
• editing boot.img
• converting png to rle or vice versa
• Writing updater-script
• Making Aroma Installer
• How to set default Settings after ROM installations
• more and more things to arrive

Tools Required : (Update them manually and report me dead links please)

Quote: Download the tools as per your need.Link is given in the name itself below.... Flashtool - For Flashing stock ROM if anything goes wrong (Download link in the installation tab of website) apktool Direct Download- for editing apk files and jar files (you can use APK manager but apktool is simpler) Cywign Direct Download- Linus Terminal For Windows ROM Kitchen (ROM Development Tool) Direct Download- For Cooking custom ROM + boot.img related tools - to edit boot.img files (Its inside the ROM Kitchen Files, Please update this Kitchen to latest version its out dated now,for this use inbuilt updater of kitchen) Official Link to kitchen dxda Kitchen - Official Thread and Github source Please refer FAQ on official thread for Kitchen related problems ftf-extractor Direct Download- It will extract system files from the ftf package which you will use to make your ROM fastboot Direct Download- For flashing kernel to your device DoomLords Easy Root Kit v4 Direct Download- To Root Stock/Custom ROM Demo META-INF Folder Direct Download- For Making Flashable zip files DroidExplorer - For advance tools regarding real time phone memory handling through windows. Flashable Zip Demo Direct Download- For those who want to just apply some stuffs through CWM Customized build.prop demo - Download Build.prop

Special Thanks to -

dsixda for his awesome kitchen  Please Hit Thanks button for him
DooMLoRD for providing root files
Please kindly remind me if i have forgotten to write your name in thanks section, i have collected all things from many many sources and with modification.

Source: NeroYoung

Build a CUSTOM ROM Using Android Kitchen

"A person who never made a mistake never tried anything new"-Albert Einstein

This thread will be giving all the newbies basic knowledge on how to build custom ROMS using android Kitchen by dsixda

This is the most basic tutorial!!! Don't ever consider yourself as a developer using this.
Developer is someone who understands what a code is and writes, or enhances the present one.

What is Android Kitchen?

Linux terminal for windows – Basically a Tool created by dsixda (Recognized senior developer) which helps you customize the shipped ROMS, or modify custom ROMs for the features you like

Setting up Cygwin and android kitchen

1. You will need java jdk to run the kitchen – you can download it from here 
2. Download and extract the kitchen from here 
3. Run the setup (.exe) and follow the instructions or the read me text file in the downloaded zip file.
4. local package directory *must* be the path to the cygwin_packages folder that you just extracted
5. when it shows all the package names, go to the top and select "all <-> default" until it changes to "all <-> install" (you must click on the arrows)
6. Now you have Cygwin installed on your computer.
7. Open the shortcut on the desktop and close it. It will include three files in the Cygwin folder.
8. Now it’s time to add kitchen to your folder. Go here and download the kitchen files.
9. Extract the downloaded kitchen files Cygwin folder C:\cygwin\home\(Your user name) and rename it as kitchen 

Ex: Android-Kitchen-0.218 to kitchen.
     10.Now your kitchen is ready for COOKING!!

Starting with the kitchen

     1. Open Cygwin , it should open with your username as the directory
     2. You will have to change the directory to the kitchen
                 Code:
                           cd kitchen
                            ./menu
     3. This will take you to the menu which has list of things that can be performed using the kitchen.          

Code:
===================================================================
 Android Kitchen - by dsixda (xda-developers.com)
===================================================================

Main Menu

1.  Set up working folder from ROM
2.  Add root permissions
3.  Add BusyBox
4.  Disable boot screen sounds
5.  Add wireless tethering
6.  Zipalign all *.apk files to optimize RAM usage
7.  Change wipe status of ROM
8.  Change name of ROM
9.  Check update-script for errors
10.  Show working folder information

To give a head start
I am going to explain how to create a working folder >>You need a ROM (Which is a .ZIP file)

     1. You can use a stock rom (OTA update from HTC or an RUU(extracting ZIP from RUU will be explained below)
     2. Or, you can use custom ROM that you have downloaded.

Quote:
Remember you are using someone else’s hard work, Do not Upload your cooked ROM

• Unless you have changed lot of the features and you might think that will help the original rom    developers a lot(which can never happen!!!
• You take prior permission from the Original ROM developer and give proper credits upon their acceptance to upload

     3. Place the ROM in the original update folder (i.e. C:\cygwin\home\\(Your  username)\kitchen\original_update
     4. Go to the Menu on the kitchen
By opening Cygwin>cd kitchen>./menu
     5. Select option 1 and follow instructions to setup the working folder.
     6. Once the folder is setup you can verify it by going to the kitchen folder.
     7. You can change the system apps, Bootanimations, Default walllpapers and lots.Explore and let us know!!
     8. Always play safe by making a nandroid backup of your current ROM before testing!

Extracting the ROM from an RUU

This is the most simple and easiest way. There are tools which can do that for you. But I prefer this

Run the RUU and as soon as you see the device picture on the screen, Go to %temp% and find the ROM.zip, copy and paste it.You can exit the installer after copying. Done!!


Device Compatiblity:

Alphabetically:
Acer Liquid
Dell Streak 7
HTC Amaze 4G
HTC Aria / Liberty
HTC Desire
HTC Desire HD / Inspire 4G
HTC Desire S
HTC Desire Z / Vision / T-Mobile G2
HTC Dream / G1
HTC Droid Eris
HTC Evo 3D
HTC Evo 4G
HTC Evo 4G LTE
HTC Evo View 4G (untested)
HTC Evo Shift 4G
HTC Flyer (untested)
HTC HD2
- Use NAND ROM method (Please follow this thread for details)
HTC Hero / G2 Touch
HTC Incredible
HTC Incredible 2
HTC Incredible S
HTC Legend
HTC Magic / myTouch 3G
HTC myTouch 3G Slide
HTC myTouch 4G / Glacier
HTC Nexus One
HTC One S
HTC One X
HTC One XL
HTC One V
HTC Rezound
HTC Sensation
HTC Tattoo / Click
HTC Thunderbolt
HTC Wildfire / Buzz
HTC Wildfire S
Huawei Ideos X6
- Please follow this thread for details
Huawei U8100/U8110/U8120/U8150/U8160/U8180/U8650
Huawei U8220 / T-Mobile Pulse
LG Ally
LG GT540 Optimus
LG Nexus 4 (mako)
LG Optimus 2X (P990)
LG Optimus Black
- Please follow this thread for details
LG Optimus G2X (P999)
LG P500
- Please follow this thread for details
LG Shine Plus
LG Vortex
Micromax A60
Motorola Atrix (unconfirmed)
Motorola CLIQ / CLIQ XT
Motorola Droid
Motorola Droid Bionic
- Please follow this thread for details
Motorola Milestone (unconfirmed)
- You may need to remove the boot.img before building
Samsung Galaxy Ace 2 - GT-I8160(L/P)
Samsung Galaxy Mini
Samsung Galaxy Nexus (untested, 'maguro' and 'toro' versions only)
Samsung Galaxy Note
- GT-N7000 - please follow this thread for details
- SGH-I717 - Please follow this thread for details
Samsung Galaxy Note 2
- Supported for:
-- Sprint variants - SPH-L900 - Please follow this guide
-- T-Mobile variants - SGH-T889(V) - Please follow this guide
-- Verizon variants - SCH-I605
(unconfirmed - see this equivalent guide)
-- International variants - GT-N7100/N7105(T)/N7108
(unconfirmed - see this equivalent guide)
-- AT&T/Rogers/Bell/Telus variants - SGH-I317(M)
(unconfirmed - see this equivalent guide)
-- US Cellular variants - SCH-R950
(unconfirmed - see this equivalent guide)
Samsung Galaxy R GT-I9103
Samsung Galaxy S (GT-I9000 and most variants)
- Please follow this thread for details
Samsung Galaxy S Plus (GT-I9001)
- Please follow this thread for details
Samsung Galaxy S2
- Supported for:
-- GT-I9100 and Exynos CPU variants - Please follow this thread for details
-- Qualcomm/LTE variants
(AT&T Skyrocket, Rogers, Telus, T-Mobile, Bell HD LTE SGH-I757M,
Telstra GT-I9210T)
- Please follow this thread for details
Samsung Galaxy S3
- Supported for:
-- T-Mobile/Mobilicity/Wind variants: SGH-T999(V) - Click here for a guide
-- AT&T/Rogers/Bell/Telus variants: SGH-I747(M) - Click here for a guide
-- Verizon variants: SCH-I535, SCH-R530U - Click here for a guide
-- Sprint variants: SPH-L710, SCH-L710 - Click here for a guide
-- International variants: GT-I9300(T) - Click here for a guide
-- International LTE variants: GT-I9305(T) - Click here for a guide
-- Korean variants: SHV-E210K/L/S and SHW-M440S (unconfirmed)
Samsung Galaxy W (GT-I8150)
- Please follow this thread for details
Samsung Nexus S / Nexus S 4G
Sony Ericsson Xperia 2010 devices (X10 / X10 Mini / X10 Mini Pro)
- Can only build ROM without boot.img (please follow this thread for details)
Sony Xperia 2011-12 devices, specifically:
- TX, P, U, Sola
- Active, Arc, Arc S, Mini, Mini Pro, Neo, Neo V, Neo L,
Play, Ray (follow steps below):
- Can only build ROM without boot.img
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
- OR If using Nandroid backups: Rename system.yaffs2.img to system.img
- Use this system.img in kitchen's original_update folder
- WARNING - If using a ROM made from system.sin (not Nandroid), it
is recommended to flash from the temporary (fastboot) Clockwork
Recovery, rather than the regular Clockwork Recovery, otherwise
device may not boot (possibly because custom recovery files in
system folder are not added to ROM? e.g. recovery.tar).
ZTE Blade / Orange San Francisco

P.S: I take no responsibility of anything happening to your device, PC. Think Before proceeding.
Everything worked perfectly for me, I am just sharing what I did! Do not blame me for anything.

You can thank dsixda on his Kitchen Thread

Sumber: xda-developers.org