yashsingh1/xdaforums huggingface dataset:
[Android] :
http://android-dls.com/files/linux/busybox

That sounds good.

Also, it isn't just busybox. There are a couple dozen other files in the /system/xbin folder that I think we need to either add or tell the user to add if there is no busybox file.

For your next release that sounds like a good simple quick approach.

It would be great if we could find the most current version of the /system/xbin folder contents (busybox and all) for Android 1.6 and 2.1 and have your kitchen copy them into the empty folder when needed for the ROM that will be ported. I found the official busybox site (think it's www.busybox.net), but I could not find the version for Android and there is a much more complete and larger version for other Linux distros.

My pleasure. Glad I can help.

A sweet addition to your kitchen would be to add similar functionality that exists in the MAGIC Port tool, but I am not sure it is worth replicating unless you feel the effort is worth it to have it all in one kitchen.

So you could collect boot.img files from different kernel sources (e.g., OE, cyanogen, kingklix, malign, etc.) and for different phones/hardware. You could provide the user with a list based on the phone they are porting to and then basically replicate what MAGIC Port is doing automatically and what I am doing manually and end up replacing the files that I replaced manually in the working folders only you would automate the process. Would be sweet.
[Android] dsixda:
That's strange. I tried to reproduce your error by getting those two "Already found" messages, but I never got those two error messages you got.

Someone else saw this before but never got back to me when I asked about it.

What platform are you using? Ubuntu or some other Linux?

What happens if you use the option "Extract the kernel + ramdisk", followed by "Build boot.img"?
[Android] dsixda:
Doh, sorry.. I forgot you mentioned it earlier ;) However, is that the right version? The one in the kitchen is 1.8 MB! This one is only 642 KB!

Yeah I guess I can just point out the error and offer suggestions (copy busybox, update the update-script), but I'm not going to bother with correcting their xbin folder.

Na, that is way too much work for me, and i don't want to duplicate and hence destroy someone else's hard work and effort in compiling all those images himself. Plus I'm doing this all alone, staying up late while I have a family to take care of, and I'm not being paid for this LOL (a measly 2 donations in 3 months). But I'm learning a lot from this.
[Android] :
That's the file busybox I was pointing to.

There is a 1.8 MB file?

Where is the one in the kitchen?
[Android] dsixda:
It's under the tools folder.
[Android] :
I didn't see that.

I will try that one tomorrow and see if I notice anything different in logcat.
[Android] dsixda:
This is the type of error message my script will now generate while porting (tested with the Beta ROM we discussed yesterday):

----------------------------------------------------------------------

WARNING: The ramdisk's init.rc refers to busybox, but it is not found
in the working folder. If you build this ROM the way it is
right now, it may not get past the boot screen on your device.

I found this:

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

Some tips:

- You may need to copy busybox to the folder referenced above.
You can find the binary under the 'tools' folder.
- Ensure your update-script file also has the following line
or similar:
set_perm 0 0 04755 SYSTEM:xbin/busybox
- You might still be missing some binaries. If you do an 'adb
logcat' during reboot, you will get some indication.

When you are ready to build the boot.img, press Enter to continue ...
[Android] :
That looks good.

I would add under tips that they may also want to copy the contents from a working ROM's /system/xbin folder into their working folder.
[Android] dsixda:
Okay, I'm going to call it a night and try to upload the latest version of the latest kitchen.
[Android] dsixda:
Ok thanks. Done.
[Android] looktall:
i've been trying to port the rom from this thread to use on my 32B magic.

http://xdaforums.com/showthread.php?t=642436

the rom in that thread is for a 32A magic in the form of an RUU.

when i try to install the rom on my phone i get the following error.

E: can't Symlink /system/lib/libA2DP.so
E: failure at line 10: symlink system: lib/libA2DP.so

installation aborted

i extracted the boot.img and system.img from rom1.exe into the kitchen.

i did all of the usual steps i do when porting a rom from 32A to 32B, which has always worked so far. (i'm using version 0.43)

ie.

step 11 (port rom)

step 3 (add root)

step 12 (add task killer tweak)

step 6 (add wireless tether)

step 13 (add /data/app)

step 7 (zip align)

step 99 (build rom)

the only different between this rom and ones that i have successfully ported before is that this rom is cupcake with sense ui.

the others have only been cupcake.

the RUU that i got this from contained two zip files; rom.zip and rom1.zip.

rom.zip contains:

android-info.txt

boot-special.img

hboot_7200A_1.76.0008_091103.nb0

radio.img

rom1.zip contains:

android-info.txt

boot.img

recovery.img

splash1_HTC_magic.nb0

system.img

userdata.img

i have a feeling that i need a different SPL to be able to install this rom.

am i on the right track? or is the cause of the problem something else?

any help would be appreciated.
[Android] seppi68:
Hello good work but just a little question :

Why you not add a ligne with Apk Sign ??

Thx ;-)
[Android] dsixda:
There's been discussion about this before in this thread. It adds complexity to the kitchen if you extract/sign an APK, and it leads to other problems with signing the ROM.. and also it is not necessarily "cooking" the ROM.

Plus I've never tried it, and I'm still a newb, and this kitchen was made to make it easier for newbs to use and understand ;-)

I also don't want to deal with more issues in the kitchen.. I get enough questions already ;)
[Android] colonel_lp:
i have been using the kitchen for a while, great stuff, thanks...

for the first time i tried to extract a stock rom, i followed your steps to run the .exe installer, then copy the rom.zip from the temp directory. extract rom, them put system.img and boot.img in img_files folder...

the problem is that the working /system folder is always empty...

help....
[Android] dsixda:
Are you using Cygwin by any chance? There are two liba2dp.so files in certain Cupcake/Donut Sense ROMs (one with upper case letters - libA2DP.so and the other with all lower case - liba2dp.so). Looks like you extracted the file in Windows and one of them got overwritten by the others. .. Windows is case-insensitive so it sees them as the same file.

So when you flashed the ROM, the update-script was running and it didn't see the one that was removed.

I had a fix for this in 0.38 (in the Release Notes), so that the upper-case one was copied back during flashing. It worked for the Tattoo. However, I guess your ROM requires me to remove that offending Line 10 as well (the ROM that I tested the fix on didn't have that line).

I would like to fix this in the script, but you can also remove that line from the update-script.

Could you please attach the update-script file here?

Thanks for the info!
[Android] dsixda:
I have a similar problem with my work PC, but I blame it on the Cygwin version they use, because it is customized, and I cannot add my own packages to it. Are you using Cygwin? Make sure you have a fresh new, updated version of Cygwin, and that you follow the EXACT instructions in the FAQ for the packages to install.
[Android] colonel_lp:
i am just using windows to get the rom.zip... all of my cooking is done in os x 10.6... (never had any problems there)

if i just try to open the zip file directly in xp or os x, it says the file is corrupted, but 7zip in xp or kitchen in os x will extract the zip......

tried 4 different .exe installers now,,, all same problem...

also noticed that i get the same result when i try to use system.img from any nandroid backup.. ==working system folder empty
[Android] dsixda:
No... that's not a deodexing error that you just posted. Read the warning message - if it cannot deodex it with conventional methods it tries the "brute force" method. You will notice it got de-odexed. I think I have stated this about a dozen times in this thread but I guess I'll have to make it more clear in the script yet again.

I'll check out your other issue later. Thanks for the files.
[Android] Droidzone:
For now ;)

I guess if it starts to be used heavily, such Roms wouldnt work in the kitchen (as they have no update-script counterpart)...

But first things first...First step is to figure out the correct syntax :D
[Android] dsixda:
Oh well.. I plan on retiring soon if they do ;) I hate working on stuff like this, I've already spent months perfecting the conversion script... I'm now sick of it.

But note, in the kitchen if there are commands that don't have an update-script counterpart (e.g. package_extract_file), they don't get converted but get moved to the update-script anyway. But that's alright, they'll still appear when you convert back to updater-script.
[Android] dsixda:
That updater-script issue seems to happen because the person who wrote it put some strange symbol in the ui_print statement... so it confused the script in the kitchen. I could try to fix it later.

EDIT: Nevermind, i just wasted one hour on this stupid updater-script. Whoever wrote it put some strange characters in the 'ui_print' statement which the script interprets as a carriage return, when in fact it's a character similar to the 'copyright' symbol. Why is there a need to have that there. I'm not going to spend more time on this -- I'd leave it up to the user to fix it before or after flashing... It's not hard to figure out.
[Android] old.ghost:
Thanks dsixda, it's working now after I created a working folder.
[Android] rsxtypes72:
The script didn't spell it wrong. I spelled it wrong when I was typing the question. Thanks for the **** response.
[Android] Droidzone:
You shouldnt have to.. :)

You can just write in the OP that these are the list of devices supported, and that 'that's that'.. I cant see any bugs in the Kitchen as of now. It's an excellent tool, but it seems that the amount of time you spend answering queries is more than the time spent on coding.. And at times (like the post just above mine exemplifies), I wonder why you do it! You should probably take some time off from adding more features, and let other people on the thread take the simple genuine queries.
[Android] arif-ali:
+1, I agree here totally

the amount of silly questions that you get here can be ridiculous, I don;t understand why people can't read or search, or even try to diagnose themselves. If people get to this stage, then should at least know how to work a simple rom, and pull it apart. Learning things like this don't come overnight, and needs a lot experimentation on the user part. you only learn by trying yourself.
[Android] dsixda:
Oh good grief! I was not intending to be rude. Here I am trying to help all you new people during my weekend with the family, and you misinterpret me. I am here to help, not to make people look dumb or to start fights. You asked me why your script was failing and I assumed it was because the syntax was wrong, because you had spelled it wrong. :rolleyes: There was no hostility intended. Furtheremore, I'm not allowed to say that I don't know the answer???

Don't give me any more stress, I'm disappointed in some of you guys who refuse to search but instead expect me to spoonfeed all the answers, even if I don't know them. This is a warning - that kind of selfish attitude and language is not accepted on XDA, and especially not in my thread.
[Android] rsxtypes72:
First off I made it clear it was my error. How can the script give a syntax error for that if I had written in my question that everything was fine. it was at the time to flash that the rom that the error came out. Sometime you guy that do know something come across exactly as I mentioned. And no I don't need to be spoonfed. I was asking you a fairly specific question.

By looking at your post I see you updated due to a spelling error too. Is it that hard to believe? Sorry for the rudeness but I'm here to learn not to get crap for a spelling error.

If there is a response for my question then simply let me know which post and I will look. I didn't find anything when I googled it.
[Android] rsxtypes72:
While I do appreciate any help I certainly don't expect anyone to be checking answering questions when they are with their faimly. If you chose to answer then that's choice.
[Android] dsixda:
You mentioned that the line was failing. On first glance it was because of a syntax error. It looked like you went into the updater-script and modified it to accidentally say "write_raw_imgae".

Excuse me?? You don't need to take it personally just because I thought you spelled something wrong in your updater-script. And I asked you if the HTC Vision was a Desire Z, and added that I don't really know the answer. You called me a ****. I am not one of those "you guy that do know something". I started off writing scripts for a kitchen and now people expect me as a "guy that do know something" about every single device, which I really am not.

Uh.. totally different context. I spelled the word 'attitude' wrong, I didn't put a spelling error in my error message. Can't we just agree it was an honest mistake and move on?

Come on man! You are not getting crap for a spelling error. I told you I THOUGHT that the mistake in the flash was because of the spelling error, not because you had accidentaly spelled it wrong in your quote. Stop taking it personally.

Now just move on, I don't want to argue the same thing over and over, I feel like I am arguing with my mother. :-P I don't like this bad energy in my thread.
[Android] dsixda:
If you notice a recurring theme in this thread, if I don't answer someone's question then the question gets bumped again and again by the same damn person.

Now let's MOVE ON.
[Android] dsixda:
The main reason I answer is that there is potential for something wrong in the kitchen. I am not happy if the kitchen does something incorrectly or misleads the user into doing something incorrectly.
[Android] Droidzone:
True.. With the amount of 'intelligence' that these scripts have, it must be a tough time finding out if there are bugs and where they are. With 6 bash scripts in my Rom, that itself is giving me a headache ;) I've been on them for 4 hours already, and still havent solved it yet :p
[Android] freak69ize:
Google is your friend.. use it. :D Google Goooooooood!! lol
[Android] coiledwire:
This needs to be said more: thank you dsixda for providing such a powerful tool and for sticking around to provide support when possible.

I can't say how much your kitchen has helped me save time and effort to complete simple and advanced tasks. Dsixda, please try not to let some of the discussions here burn you out. For every 1 bad vibe here, there's 99 other happy, satisfied users out there going about their business. Your tool is so complete for many of us, we don't frequently think to stop by and share our positive feedback.

Thank you again, dsixda, for the tremendous support and the outstanding tool you provide for us. :)

Sent on the go, from my evo.
[Android] freak69ize:
I couldnt agree more.. I understand people have problems and everyone wants that quick fix to their problems but you aint gonna learn nothing if you dont try to think for yourself.. I dont imagine Einstien asked for answers everytime he got stumped.. back to the drawing board peeps.. and if that doesnt work.. like i said.. Google Good
[Android] wachw:
Same from me as well. Your kitchen has allowed me to do so much, and i've learned so much just from trying stuff out and reading through this thread. Went from being a complete n00b to being fairly proficient with rom modding. So, thanx.
[Android] haggardh:
I got a lot of MD5 error matchups in the checking of Cygwin is that normal?

edit: im just going to use VMware
[Android] ThunderStick:
Thank you in order

OK You have helped more than I can expect thanks for the help.

THANKS AGAIN...
[Android] dsixda:
Ok guys, thanks for the accolades, it's appreciated.. but let's move on, I don't want to create animosity.

@rsxtypes72: If you still have issues, check your device forum and see how they did their updater-script.

You may want to try to replace the problematic line with this instead:

package_extract_file("boot.img", "boot");
[Android] dsixda:
Ok I've fixed the issue with the symbol character in your updater-script. FINALLY.

Try this file out, just unzip it to your 'scripts' folder and try the ROM again if you wish.
[Android] dorf12:
kitchen terminal ubuntu

i am having problems bringing up anything in the terminal except for dragging it over in it but even then it still says no directory or anything so some please help i have read the faqs and went thru alot of the pages on this thread maybe i missed it. right now im updating to the most recent ubuntu. so please help
[Android] freak69ize:
Noooo!!! dont upgrade to the latest Ubuntu.. I did the other night and it wiped everything out.. Java, guest additions.. still havent got guset additions right myself.. only works with karmic kola ( is that right lol )

Ok.. cooked a rom last night. All i did was upload my framework-res apk. to Ultimate online kitchen then replaced it with one from working folder.. installation aborted.. hmmm back to the ole drawing board!! lol
[Android] Jbcarrera:
Flash it then rebuild from the backup
[Android] famonaco:
hi man, have you solved de superuser issue???? means now works properly thx mate ;)
[Android] leith51:
What issue ? I've used this kitchen loads and never had an issue with superuser

Sent from Levo v2.2
[Android] :
Amazing ...
[Android] JGW310:
installed on windows........................ how do i start the kitchen?
[Android] dsixda:
Anyone else who asks how to run the kitchen but refuses to read the simple bolded text above AND below the download link on post #1 (along with the README file that came with the kitchen), will receive an infraction.
[Android] dsixda:
@JGW that was a hint to read the FAQ. ;)

How are you going to expect people to trust using your ROM if you don't follow instructions and ask questions like the above?
[Android] jaykresge:
Hit alt + F4 at the same time.
[Android] johnston9234:
Wait a second....
[Android] NinoFR:
Excuse me by advance for my terrible stupid question ...

Could you, please, indicate me where I can download the Kitchen ?

I cannot find any link in the first 3 posts :(

Thank you by advance.

Best Regards,

Nino
[Android] creezalird:
it is in the first post with some big download picture :D

https://github.com/dsixda/Android-Kitchen/archives/master
[Android] dsixda:
I was afraid the download image would not show up for some users. I have updated Post #1 with the same link but without the image.
[Android] nerdkiller14:
Hey can you help me.

I'm using this on Mac 10.6 with Xcode installed and I can get into the main menu but when I press 1 to select option one I get a flicker and then I am returned to the main screen
[Android] dsixda:
That's because you didn't unzip the kitchen properly. Make sure the scripts and tools folder is there..
[Android] dsixda:
I have uploaded version 0.164 of the kitchen. Please see Release Notes in post #2 for details. Enjoy.
[Android] GazaIan:
Sweet :D How well will this work with ubuntu natty narwhal? Ubuntu itself has been giving me a ****ton of problems, but if it guarunteed works great I'll downgrade. (can't stand the random white screen, or the screen turning white when a window is too big -.- )
[Android] dsixda:
It should work with all versions of Ubuntu but I had the least problems with Karmic Koala, because it supported Java JDK 5. JDK 5 got phased out in later versions of Ubuntu so it required a bit of hacking to get it installed.

However, the later versions of the kitchen worked with JDK 6 so it should be less painful to install Java now, as long as you know the name of the package for it. Would be great if we had a better guide on getting Java (especially jdk 6) to work.
[Android] brad560:
thank you so much for this post! got the weekend off, gonna play around, and read! i would love to have a rom "i made" on my phone :)
[Android] :
Thank you so much! I'm trying out the kitchen with Ubuntu 11.04 and it seems to be working.
[Android] creezalird:
just tried your kitchen recently and for some roms, it went well but for some i always got error status 6 something like that. i assumed it came from the updater-script.
[Android] powduh09:
I've had that problem a bit too... I found that some of the system apk files if added or changed needed to be signed...
[Android] creezalird:
mine is caused by converting the update/updater script, if i just ignore the conversion, the rom will flashed properly
[Android] dsixda:
Its because your recovery image doesn't support updater-script, it's not an issue with the kitchen...

Note that the Build option says updater-script may be used on *newer* versions of custom recovery, so don't convert the update-script otherwise. Just use the default.. which is already No conversion.
[Android] powduh09:
My errors were always status 7 if I needed to sign system apks
[Android] dsixda:
I'm talking about using updater-script instead of update-script, I am not talking about signing or modifying apks. That wouldn't be a kitchen issue anyway.
[Android] xHausx:
I'm surprised you haven't posted this in the OP yet dsixda :D

[YOUTUBE]JmvCpR45LKA[/YOUTUBE]
[Android] puertoblack2003:
that error 7 has something to do with the update-binary.Which was fixed 15 updates ago........:rolleyes:
[Android] Grezvany13:
@dsixda: Thank you for this kitchen! :D

I'm trying to use the scripts to build an online multi device kitchen (the restaurant has a very large menu) for Android based tablets.

My biggest problem is the fact that I'm a PHP Developer and I have no idea where to start in the code (although I seem to understand the basics, since the code looks very simple).

So now some of my questions:

1) Is it possible (and simple) to use multiple base roms without having to "rebuild" the working folder?

2) What files / changes are required to add a new device? Only /tools/edify_defs/* ? Or should I look further?

Please note I have a lot more of questions, but I'll try to figure them out myself since I haven't started "messing around" with the code yet.

And I also didn't walk through the 380+ pages of comments, so it might be possible that my questions are already answered here. If that's the case, I'm sorry ;)
[Android] dsixda:
1) I don't understand your question. If you mean using multiple working folders at the same time in the kitchen, then no it is not possible due to the way the scripts work. It would cause conflicts with the existing (approximately 100) scripts and I'm not keen on changing around 100 scripts to support that either ;-) I want to make the concept as simple as possible to the normal user. If you want to have multiple working folders at the same time under the kitchen's base directory, then I suggest you rename the ones you do not want to use or move them to the OLD_WORKING folder. And then rename/move them back when you want to use them.

2) Yes just change the files under there. If you happen to add some files there, please let me know so that I can update the kitchen as well.
[Android] kaibird:
after install how come cygwin closes immediately???

I could not open it....

I installed everything correctly

I'm using Windows XP

it worked fine before....