After following the setup for the kitchen, how do I use kitchen?

Click here for another video tutorial from theunlockr.com! Extract the kitchen's .zip file to a folder under your home account. In Cygw in, this folder would depend on what was set for your Cygwin install directory, e.g. C:\cygwin\home\John\kitchen NOTE!! If your user folder contains spaces (e.g. C:\cygwin\home\John Smi th\kitchen), then the kitchen will not function properly. Instead, copy it under C:\cygwin\home\kitchen. To run, open up a command prompt (in Cygwin, click on the Cygwin shortcut on your desktop). Type the command to change to the folder containing the kitchen e.g. if your kitchen is under c:\cygwin\home\John\kitchen, then you woul d type: cd kitchen. e.g. If your kitchen is instead under c:\cygwin\home\kitchen then you wo uld need to go up one directory level. Type: cd ../kitchen e.g. If your kitchen is instead under c:\cygwin\home\John\blah\stuff\and roid then you would type: cd blah/stuff/android) Once you are in the correct folder, start up the kitchen by typing: ./menu NOTE1: If you get a 'permission denied' error, then you must type chmod +x menu and run ./menu again. NOTE2: If you get an error message about the file not being found, then it means you are not in the directory containing the kitchen! Select Option 1 to set up your working folder (the folder where your ROM is going to be created). To import a ROM into this kitchen, follow the instructions in the section below entitled "How do I import a ROM into the kitchen?" Modify whatever you'd like in the kitchen If you want the ROM to be able to run apps that require root permissions , select the "Root" option. You can remove unneeded apps (*.apk) from the /system/app folder of your working folder. If you want to add Market or non-stock apps (*.apk) to your ROM (which c an be uninstalled or updated from your device later) then select the kitchen's m enu option that adds "/data/app functionality". Afterwards you can copy these .a pk files to the new /data/app folder of your working folder. If you put those ex tra apps under /system/app instead then you won't be able to update most of them through the Market. Optional: Read this post for some more information about the fundamental s of creating your ROM with this kitchen. When you are finished modifying your ROM, just choose Build ROM. Your completed ROM can now be copied your SD card, ready for flashing from t he recovery menu! NOTE: It is always recommended to make a Nandroid backup from the recovery m enu before flashing a new ROM!!

How do I import a ROM into the kitchen to use as my base? (NOTE: For the Samsung Galaxy S2, please click here instead) From a shipped ROM: First, find the shipped ROM for your device, usually from htc.com or fro m searching xda-developers (check the Wiki or sticky posts under your device's s ub-forum). This link may help: Various devices Please don't ask me for links, as I don't know everything or own all devices. ;-) The shipped ROM can be found in three different formats. Identify the ty

pe you have downloaded: If the shipped ROM is in a .ZIP format, then simply copy it to the k itchen's original_update folder. OR if the shipped ROM consists of system.img and boot.img files, the n copy those two files to the kitchen's original_update folder. OR if the shipped ROM is in an .EXE format, then do the following: In Windows, run the shipped ROM's .EXE file till it gets to the first dialog. Stop there but don't close the window yet. Go to Start->Run and type: %TEMP% When the folder opens, search for Rom.zip (use the "magnifying g lass" Search button) Copy Rom.zip to your kitchen's original_update folder OR from a cooked/custom ROM: Copy the update.zip (or equivalent ZIP file) to your kitchen's original_ update folder OR from a Nandroid backup (under /sdcard/nandroid) [NOT RECOMMENDED FOR NONSTOCK ROM BACKUPS]: Copy the system.img and boot.img files from the backup folder to your ki tchen's original_update folder NOTE: The Nandroid-backup method of ROM customization is not the best me thod, because the kitchen may not account for various advanced options that were added outside of this kitchen (these options are in the update-script file whic h was in the original ROM but is not in the backup. The kitchen needs to re-crea te this file and 'guess' those options). However, it will support Nandroid backu ps that already have basic features like root, busybox and /data/app functionali ty. Please see Page 2 of FAQ (Other Questions) - in next post! Frequently Asked Questions - Page 2 (If you can't find your answer below, please try Google first before asking.) QUESTION: Whenever I double-click on the 'menu' file in Linux or Mac OS X, the s creen immediately closes or I get an error like "File not found." No, do not click on the file. You were instructed to type "./menu" from the comm and prompt. Follow the instructions as they have been given. Please refrain from asking me this question again and again, or from requesting me to fix it - doub le-clicking is not how shell scripts are meant to be run!!

QUESTION: Whenever I type ./menu to start the kitchen it says "Permission denied ." Your file attributes are somehow missing the 'execute' flag. Type the command ch mod 777 menu (or chmod +x menu) and try ./menu again.

QUESTION: In Cygwin whenever I type ./menu it says the 'clear' command is not fo und. That's because you did not follow the instructions properly for installing Cygwi n. Make sure you did not skip a step in the text file that is included in the Cy

gwin package that you downloaded from the FAQ. There is also a Cygwin pictorial guide in the FAQ that you should not miss.

QUESTION: What versions of the Java JDK are supported with this kitchen? I have successfully built ROMs using Java 5 JDK and also Java 6 JDK.

QUESTION: Does the kitchen support ROMs for Device X?? See post #1. If it is not listed there then I have not done anything for it. Kee p in mind that this is primarily a kitchen for HTC devices. Most of the ROMs for non-HTC devices that are supported in the kitchen are there because they are ea sy to support, as their file structure is not much different from that in HTC RO Ms. However, certain devices use a completely different ROM file structure, so t hey are currently not supported in the kitchen. I am also limited by the fact th at I only own one or two Android devices at a time, which affects the extent of my testing. Finally, please don't expect me to do every Android known device kno wn to man, as I am a busy guy with mouths to feed, like a lot of you. ;-)

QUESTION: I flashed a ROM and when it boots, it gets stuck on the splash screen (boot loop) or goes back to recovery menu. If you are stuck on the splash screen, the first thing to try is to wipe the cac he and dalvik-cache from the recovery menu. A full wipe may also be required, al though I would not recommend it until you try the suggestions below. Debug the issue with "logcat" (you need the Android SDK to use it): Take out the battery so that the phone is turned off. Then, go to the Android SDK, change to its 'tools' folder, and type "adb log cat". It will tell you that it is waiting for a device to be detected. Plug the phone into your computer's USB port, then turn it back on and check the logcat output. When the phone gets back to the same problem, check the logc at output for any error messages (e.g. missing files). This should tell you what the true problem is, which can hopefully be fixed. If you want to direct the logcat output to a file, type instead "adb logcat > c:\logcat.txt". If you want to share the output, paste it to a site like pastebin.com. If it 's not a problem with the kitchen then post it in another thread in the Chef for um, rather than in this thread. Another thing to do is to grab the "recovery.log" file immediately after you fla sh the bad ROM (BEFORE the first reboot!!). This shows a log of the activity dur ing the current recovery menu session (i.e. during the flash). This log may also show errors that were not caught when you were flashing the ROM. In Amon_RA Recovery, you can easily access this file by accessing the menu o ption "Other->Move recovery.log to SD", which moves it to /sdcard/recovery.log. Otherwise, you can usually find it under /tmp/recovery.log or /cache/recover y.log or /cache/recovery/last_log with ADB. Try to copy it to a location where y ou can view it. e.g. Type from your computer: "adb shell", followed by "cat /tmp /recovery.log > /sdcard/recovery.log" Open up recovery.log with a text editor, but don't use Notepad, because it w

ill put everything on one line instead of multiple lines. Check recovery.log for any errors that occurred during the flashing process. Remember, you must grab the recovery log output immediately after flashing and b efore you reboot. If you had rebooted afterwards, then the flashing's log inform ation would have been cleared and you will need to flash again to get the log ou tput.

QUESTION: After I flashed a ROM, it doesn't boot but I get 'File not found' and/ or 'No such file or directory' (usually in reference to /system/bin/sh) error me ssages in logcat. The /system partition was not flashed properly due to an issue on your device. T his usually could mean one of the following: You ported the ROM incorrectly. If you open up the recovery log (see the ins tructions above) you may see the reason, such as the device running out of space or errors copying to the system partition. Sometimes this is because the ROM is too large to fit into the phone's relatively small system partition in the inte rnal flash. In this case, remove unnecessary apps from the system folder until y ou manage to fit the ROM into your device. You ran a script in your updater-script/update-script but it had errors, thu s halting the flashing process and leaving you with an incomplete flash. You added Apps2SD to a device that does not support it. Did you ignore the w arnings in the Apps2SD screen of the kitchen? :P An inspection of your recovery log should help you determine the exact cause.

QUESTION: I get errors in the recovery menu when I flash a ROM. This may mean your update-script/updater-script has errors or there is an issue with how the kitchen created your ROM. Read the rest of the FAQ for potential so lutions, or you may need to inspect the recovery.log to debug the issue (see abo ve).

QUESTION: When I flash my ROM, some of my changes don't appear, e.g. Apps copied to my working folder's /data/app. Check the recovery.log to debug the issue (see above).

QUESTION: Why do I need to convert the ROM's updater-script to an update-script when using the kitchen? First of all, the kitchen supports updater-scripts. BUT, the problem is that the updater-script in different devices (and by different authors) may use various formatting/alignment styles, mount points, partition types and may also employ d ifferent commands for the same functionality, and thus there would be an awful l ot of variations to check for every time a kitchen script is using it. Hence at the beginning, the kitchen will convert the updater-script into a universal form at (e.g. I chose the update-script format) so that all the scripts of the kitche

n will work on the ROM without encountering these issues. When the ROM is built, the kitchen converts it back to an updater-script with the correct syntax, and the partition details are fully restored. If we didn't convert the updater-script then it would take A LOT OF work to over haul the dozens of scripts to accept updater-scripts, which would really NOT mak e a difference in the end anyway, and would likely slow down the kitchen due to extra checks made in the updater-script. So please do not request this again and again, there is no gain in doing it. Believe me, I have spent many months and s tayed up late many, many nights getting this update-script/updater-script compat ibility issue working with the kitchen with all ROMs and numerous HTC and non-HT C devices. When you build the ROM you have the option of converting it back to an updater-s cript, or the kitchen will convert it automatically if it decides it's necessary . The conversion back to the original updater-script is near-perfect, as I have already spent months on the implementation to get it right. If you want to instead convert your updater-script or update-script *before* you build, then use the option found under the Advanced section of the kitchen menu .

QUESTION: What is an update-script or updater-script file? This is a file found under the META-INF/com/google/android folder, and specifies the operations required for flashing your ROM. It performs various file operati ons, such as creating file shortcuts (also known as symlinks or symbolic links), adding permissions to files, running scripts and copying files and folders. Aft er flashing your ROM this file is not executed again. The updateR-script is more advanced than the update-script and supports more dev ices. When you see someone refer to "Edify" format they are talking about the up dateR-script; whereas "Amend" format refers to update-script. The updateR-script also requires an update-binary file included with it. The upd ate-binary contains all the binaries for the commands that the the updater-scrip t uses (e.g. set_perm, symlink, format, mount, etc.). The update-script does not need an update-binary.

QUESTION: I have converted my update-script to an updater-script, but after flas hing I still have the original ROM on the device. That means your updater-script did not have the proper mount points defined for the system (and/or data) partition. Refer to this post for more info. EDIT: You can now add your own mount-point definition file to the kitchen's "tools/edify_d efs/" folder for when it creates the updater-script for your device.

QUESTION: My device only supports ROMs with the updater-script/update-binary fil es but not the update-script If you extract a ROM that contains an updater-script, then the kitchen will ask

you if it should convert it to an update-script. You *must* use an update-script while customizing the ROM, as the kitchen is not capable of modifying updater-s cripts. When you are ready to build the ROM, though, you will need to convert it back to an updater-script if the device requires it. Use the option in the Adva nced menu to convert update-script to updater-script, or else the kitchen will a sk you to convert it while building the ROM.

QUESTION: Can you help me port a ROM? Or can you tell me if Device X's ROM can b e ported to Device Y? No, I am not an expert on porting; however, there is a Porting option in the kit chen. Keep in mind though that it is not the magic solution for all devices and will not work all the time. The recovery log and logcat tool should help you deb ug issues with porting (see instructions above).

QUESTION: How do I get Ubuntu to see my device with ADB? First, download the Android SDK and copy it to a folder like ~/AndroidSDK/ Then, use the following commands: Code: cd ~/AndroidSDK/tools ./adb kill-server sudo ./adb start-server ./adb devices If you want to try Linux commands on your device, you can use the "./adb shell" command, e.g. ./adb shell reboot QUESTION: I get the following error when flashing a ROM: E:Board does not suppor t mtd utils.E:Failure atline 77: write_raw_image PACKAGE:boot.img BOOT: Please see this post for the solution. In some recovery menus the boot.img canno t be flashed straight from the ROM's ZIP, so it needs to be copied first to a te mporary area on your device and then flashed from there.

QUESTION: Why do you only have a few build options (Interactive/Express/Extreme) in the Build menu? Read this. If you wanted an Express option that will sign the ROM, then read thi s.

QUESTION: How do I add or port a kernel to my kitchen's working folder? Follow the instructions here.

QUESTION: I get busybox errors during flashing; e.g. "Can't chown/mod /system/xb

in/busybox (No such file or directory)" or "E:Can't symlink busybox ..." Apparently you need to upgrade your SPL, and it has nothing to do with the kitch en: http://forum.xda-developers.com/show...1&postcount=12 http://androidcommunity.com/forums/276808-post16.html http://forum.xda-developers.com/show...postcount=5638

QUESTION: While flashing my ROM, I get an error about 'assert getprop ("ro.produ ct.device")'. Read about a solution here. You will likely need to modify your build.prop and u pdate-script files in the kitchen and rebuild the ROM.

QUESTION: I created a ROM with root permissions, but whenever I access an app wi th the superuser prompt, it hangs or force-closes. Under Settings/Applications, ensure that USB Debugging is enabled. You probably disabled it after flashing your ROM.

QUESTION: When I flash my ROM in the recovery menu, I get an error like "E:Can't open (bad)". You may need to change your custom recovery menu. For example, see here.

QUESTION: How do I add a theme to my ROM? I don't know, as I just write the scripts and am not a ROM theming/modding exper t. Please ask in the forum but not this thread, as I cannot help you with your q uestion. Sorry.

QUESTION: Can you add APK decompilers and other APK modding tools? Or how about PNG optimizers? See this answer.

QUESTION: Can you give me an explanation of de-odexing? De-odexing will take the *.odex files in your ROM and convert them into classes. dex files, which will then be zipped into their corresponding APK or JAR files. For a technical overview, read this. A short summary of why it is used is in thi s post.

QUESTION: Can you add an option in the kitchen to odex a de-odexed ROM?

No. I don't know how to do it with a kitchen and probably don't have the time at the moment. There is a way to do it, but not from your computer. The odex script must be run on your device - within the Android command shell - after the de-odexed ROM has been flashed (I don't have the script, just Google it). (Here's a thread about it but the link to the script is dead.)

QUESTION: Why do some applications in the data/app folder force-close and others don't? Probably they have native libraries which are not installed after you flash your ROM. Use the Application Verifier plugin to check such apps, and to make the re quired update.zip to flash after you have installed the ROM (see Plugin section in first post).

QUESTION: When we build the ROM, why can't we create a new system.img instead of a ZIP file? Read this post.

QUESTION: What is Apps2SD and what version does the kitchen use? There are multiple 'types' of Apps2SD -- one is the implementation found in Andr oid 2.2+ that gives you the option of moving your apps to the SD card. Normally however, this does not move all of the app components to the SD card, and not al l apps support this feature. The other Apps2SD is sometimes referred to as "Apps2Ext" and requires an extra s tep by the user beforehand to format a new EXT-based partition on your SD card f or the apps (normally an SD card is in FAT32 format). Unlike the 'Froyo Apps2SD' , the Apps2Ext feature moves everything to the SD card, even apps that normally do not support the storage card option. The Apps2Ext version is found in the kit chen as DarkTremor's Apps2SD (by XDA user tkirton) and supports older devices th at have a very limited amount of internal storage.

QUESTION: I am using Ubuntu Linux on a 64-bit Windows PC, and whenever I run 'zi palign' I get an error about "No such file or directory". You need to install the Ubuntu package "ia32-libs".

QUESTION: In the Advanced Menu's boot.img tools, why is there only an option to unpack a boot.img but not to re-pack it? There is an option, you just need to unpack it first! Read this.

QUESTION: Can you include an option to overwrite the ROM's existing Apps2SD with

the one in the kitchen? Answered here.