yashsingh1/xdaforums huggingface dataset:
[Android] PhantomHacker:
Anyone know how to repack boot.img with the kitchen, I only get the option to unpack.
[Android] dsixda:
You need to unpack it before it shows the option to repack. :P
[Android] dsixda:
Just read the FAQ please.

For device-specific ROMs you'll find them in the device's development forum.
[Android] roxdragon:
First, find the shipped ROM for your device, usually from htc.com or from searching xda-developers (check the Wiki or sticky posts under your device's sub-forum).

My device is: Samsung google nexus s or htc google nexus one

I have not understand where I can find the ROM for Nexus Nexus S and One ...

I can not speak English well ... You can post a link?

I'm Italian: (

Thank you
[Android] PhantomHacker:
I do that and its in the folder were it should br but I still don't get the option.
[Android] dsixda:
I don't know
[Android] dsixda:
You need to say what device ROM you are using. If you leave out important information or screenshots then I can only guess what you are doing. You got me worried that something was broken recently but I just turned on my laptop and tested it.
[Android] jorim.tielemans:
Do you have a Nexus S 4G??
[Android] dsixda:
Guys let's stay on topic. I have mentioned in the FAQ that the ROMs for your device are found in the development forum for your device in xda. Apart from that I cannot help because I don't know and I don't collect devices and ROMs, I only write scripts. In addition, please use Google to search for shipped or stock roms. If you can install and run the kitchen, then I am sure you can figure out where to get ROMs. Thanks!
[Android] roxdragon:
No Google nexus S Normal...

----

@dsixda sorry! i don't find stock rom...
[Android] jorim.tielemans:
Look here: http://goo-inside.me/crespo/stock
[Android] ciko84xp:
Thank to you dear... This was what i wanted to know!

Thank you for the answer!!! ;)
[Android] Truballa4real7:
how would i be able to add a apk to my rom?
[Android] dsixda:
Read the FAQ please
[Android] PhantomHacker:
I'm still having the same problem, with the boot.img (not getting the option to repackage). I'm not sure what I am doing wrong.

ScreenShot

Device: Evo4g

Sorry, and thanks.
[Android] leith51:
I'm guessing that the boot.img your trying to repack is not from the working folder. From your screenshot you have unpacked a boot.img from an outside source so there is no option to repack it.

You can only repack the boot.img from a working folder after unpacking it

Hope that helps
[Android] PhantomHacker:
Doh! Alright, thanks. My mistake.
[Android] leith51:
No worries it happens
[Android] dsixda:
You won't be able to re-pack it without information about the kernel's base address and the command line parameter. These two items are found in the boot.img.

In other words, you'll need a working folder with a boot.img (from which your extracted folder was based off of) in order to know how to rebuild your extracted folder. In addition, your folder needs to be renamed to BOOT-EXTRACTED, which is the name given by the kitchen to extracted folders created by the working folder's boot.img.
[Android] CdTDroiD:
Anyone getting bad zips from the kitchen lately? i never used to but seems to be an updater script issue or something wrong with the zip process...
[Android] dastin1015:
Does it say bad zip when flashing? If so it is a bad copy on your SD card most likely. Check md5sums before and after copying to SD card to see if it is a bad copy or bad kitchen zip.

Sent from my HTC Hero making C.R.E.A.M.
[Android] CdTDroiD:
Yea tried all that ;) Its definitely happening before copying
[Android] dsixda:
You need to be more specific -

What is the error? If you can unzip the file then it is a valid zip file. Also check that you are not out of disk space.
[Android] leith51:
I noticed on your honeysense thread you hit bootloops

I had the same problem mate after getting recovery log and get the logcat I noticed it stopped at installation of busybox, and didn't finish it looks like it doesn't write the boot.img on desire hd

So I went back to kitchen 0.159 and everything fine now
[Android] dewasha:
support of blackstone please
[Android] dsixda:
Can't do anything without NAND ROM support
[Android] dsixda:
We don't know yet the details of his problem, so I wouldn't blame my kitchen right away...

As I have stated here numerous times, I would strongly suggest people to stay away from older buggy versions and not recommend them to others unless you want to run into other issues. Blindly using older versions because "they work" doesn't solve the problem, and is against the true ideals of development, and may also run the risk of introducing issues for users of the ROM (especially if the developer doesn't know what the cause of the problem is).

If you debug and get to the root of the problem then perhaps it is not a kitchen issue after all but an issue with the recovery menu being used or some user error. In one of your older messages you showed a recovery log that used ext4 filesystem instead of the default ext3 for the Desire HD. My advice is to modify the tools/edify_defs/ace file to use ext4.

If you do think it is an issue with the kitchen then I apologize... but please narrow down which version the problem started happening in, and I can try to figure it out from there. Thanks
[Android] leith51:
I did modify the tools/edify_defs/ace file to use ext4. As previous advice you gave that's why it was ext 4. The first time it started was kitchen 0.170 but to be honest I do not think it is the kitchen, what I have found is the original Rom I had downloaded base 2.50 was corrupt as winrar could not extract the files.

The only reason I went back to a kitchen I knew worked perfect for me and had no issues or bugs with was just because I knew it was what I used to build my Rom time and time again with no problems.

I will try the latest kitchen once I find a bug free download of the base but upto now I have failed to get one
[Android] qweasdfzxc:
I'm sorry to bother here but I've opened a new thread in Android general and I fear it will be ignored as all the previous thread like mine I found.

I'm using the kitchen to slim down the Oxygen rom for Desire. I did quite a good job earning 20mb and I'd like to eliminate all the languages beside English (UK). Which files I should delete from the working folder?
[Android] carl1961:
just a heads up

just to let you know you latest kitchen is doing great

I used it to convert dungphp lastest rom test, CLK Rom to Magldr rom

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

could not get new rom to install with any magldr kernel, the clk must be a new one, but your kitchen converted that kernel to magldr ( I guess that what the kitchen used) you would know

anyway after hours of trying, I decided to give the kitchen a chance

thank for you hard work, keeping the kitchen updated
[Android] shark147:
Hi dsixda,

thanks for your greats tools kitchen...

I have a little problem with dump new Official Rom HTC Desire HD v3.06.405.1, in structure folder i don't see folder LIB...

please you can check this?

regards. :)
[Android] dsixda:
If it's missing a folder then it means you used the wrong method of extraction. Just like what the instructions in the kitchen said -- use the other method... eg. Explore2fs instead of ext2explore
[Android] shark147:
Hi dsixda,

Thanks for your answer.

I have try both software "Explore2fs" and "ext2explore" Opened "system.img" but same result, the Folder LIB don't show in structure folder.

it's very strange...

Regards.
[Android] carl1961:
here's a little video, I already have a working folder the boot image is pulling from, the other options do the same but makes you a folder to put your boot file in to fix, I change second boot screens all the time this way, before it was a lot of steps on ubunta,

http://hotfile.com/dl/129163100/570bb11/dsixdas_Android_Kitchen_boot_extracting_and_repacking.wmv.html
[Android] carl1961:
shark147 run your system.img through unyaffs

unzip this unyaffs.zip copy your system.img to folder, double click Command Prompt.bat and press 1 then enter all files in image will extract ( this is windows version of unyaffs)

be careful you don't delete your unyaffs file because they all mix together, often I get a system.img that only unyaffs will unpack ( like from backup file from clockwork recovery) which is basically a dump file

also never use winrar,I quit using it a year ago, always use 7-zip ( Linux and androids friendly) it will open rom.zip when winrar or alzip says it's bad

if that system.img came from a SD Rom ( ment to run and boot from winmobile 6.5) it will not have a lib folder, it uses winmobile6.5 dlls I think

in third picture I highlighted the files to show you the system.img files, they will not be highlighted, also you can edit 1.bat and put other android.img there ( recovery backup files)
[Android] carl1961:
willing to bet 7-zip would have opened that file, you can run a ruu.exe ROM update, go to temp folder and get rom.zip and alzip and winrar will complain, I can't count the time I re download Roms and files because of that ( android must be using a different compression that 7-zip know?
[Android] dsixda:
He is using a Desire HD ROM so I don't believe unyaffs will work here (except if the HD ROM is actually a Nandroid dump) unless I am misunderstanding your reply. The kitchen actually tests the ROM first for unyaffs before it decides it wants to use the newer (ext3/ext4) options.

The other thing to try is to run the kitchen in Linux, which will mount the system.img to a folder and automatically extract the files from there.
[Android] tufeijoe:
Also support Huawei C8600, M860

Please also noted that the KITCHEN is also support Huawei C8600 and M860
[Android] jikantaru:
How can I add splash1.nb0 to ROM using dsixda?
[Android] famonaco:
yep the kitchen delete the lib.img :)
[Android] dsixda:
Lib.img? Wow.. that's something new to me.
[Android] famonaco:
mate i can send you a pm? :D
[Android] nitr00:
Im new to the cooking stuff and also tryed the new Official Rom HTC Desire HD v3.06.405.1

But when I flash the rom it does not boot and just sitting on the white htc screen

EDIT: forgot to mention that im using xubuntu 11.04 in vmware with the latest kitchen
[Android] bambamishere:
linux box setup

I have a pc setup with only linux Mint on it nothing else,could you tell me step by step on how to setup the Android Kitchen on it?

Thanks
[Android] nitr00:
Verry easy, I just did it myself for the first time. Everything u need to know in 3 steps can be found in the first post
[Android] Spyr0s:
I did this on Ubuntu, cd to where your lib.img is

mount -o loop lib.img /mnt

the rest is piece of cake
[Android] shark147:
Hi,

You check in structure Kitchen if in Folder "System" exist Folder "Lib", if not the problem this is....
[Android] pokerhiih:
+1 same here
[Android] nitr00:
So I did this and cp'ed the mnt/lib folder to the system/lib and build the rom, but now I flashed again and im still stuk @ boot ...

Any tips from here ?
[Android] famonaco:
Yep you must check bin and xbin folder
[Android] pokerhiih:
What you meen check??
[Android] famonaco:
Are bad extracted means aren't in correct folder
[Android] pokerhiih:
In xbin i have 21 files....should be 4??

This rom is messing with my brain:mad:
[Android] nitr00:
Well my first kitchen experience is getting a abit frustrating with all these un-documented troubles..

So now bin and xbin are having problems being extracted?

Whats next?
[Android] dsixda:
About what? Just post it here
[Android] dsixda:
Check the FAQ regarding non-booters. Not sure what is meant by checking bin and xbin.
[Android] dsixda:
There is nothing that is an "un-documented" trouble. I wouldn't be hiding info and making things complicated for a new user. HTC introduced a lib.img file recently that I never knew about. Looks like a lot of people are relying on the kitchen to extract such a ROM. I will fix that later this week. For other problems check the FAQ for answers.
[Android] famonaco:
Isn't a kitchen issue , kitchen only delete lib.img :)

Fix it and many users will be happy
[Android] pokerhiih:
Looking like this
[Android] famonaco:
Sorry i can't post the new desire hd rom here .
[Android] dsixda:
??? Okay, why?
[Android] blahbl4hblah:
Just wondering if you could explain to me on how to add certain things to the updater-script in a certain place. For example, if I wanted to put "ui_print("-Checking Model ID");" at the very top. Another example is also putting "ui_print("-Creating Symlink");" where symlinks start.

Thanks
[Android] pokerhiih:
He will have problems with HTC.....
[Android] dsixda:
If you are going to have problems with HTC then why ask here? No illegal or warez discussion here, nor am I going to help anyone for that.
[Android] famonaco:
warez??illegal??? omg nope :P

In the desire hd section we had problems with this release so i can't post here, but if you want ( usefull to fix this kitchen problem) i can send it for pm ;)

see ya
[Android] dsixda:
Problems with release so you can't post here? Haha what? Sorry, I'm not touching it with a 10-foot pole. If you are dealing with something controversial that will cause a cease-and-desist from HTC then it is not allowed on xda. Furthermore if it's for someone's own fame and personal benefit and less for the benefit of the community then I want no part of it, nor do I want to be used for that. :p
[Android] famonaco:
personal fame ???? maybe my english isn't good :p but basically i want to help you to fix your kitchen issue with the new desire hd base ( benefit of the community) btw no problem mate ;)

thx for you work :)

see ya
[Android] TMartin:
The kitchen fix can come when it's safe to post...well when the ok to release the leak comes.

@dsixda - Not sure why the classpath is an issue with this one file...any idea? This is from the HTC Ruby aka TMo Amaze 4G.

Error while loading class Lorg/xbill/DNS/spi/DNSJavaNameServiceDescriptor; from file ims-service.odex
Error while loading ClassPath class Lorg/xbill/DNS/spi/DNSJavaNameServiceDescriptor;
[Android] leith51:
The new htc desire hd base is an official release for the the desire hd base nothing illegal about so I been told

Just for your info
[Android] jikantaru:
Splashscreen how to add one

Why no one answer my question anybody who knows dsixda? How to put custom splashscreen in my ROM.

I tried putting it in the working folder the splash1.nb0 but it doesn't work. lol :P

Please........ :o
[Android] dastin1015:
The splash screen is not something you flash with a ROM. A splash screen is flashed through your bootloader if you are S-OFF. For example with my phone (HTC Hero CDMA) I would make a HERCIMG.zip of the splash screen named to splash1.nb0 and a txt file with my device info named android-info.txt taken from an RUU. With the HERCIMG.zip I place it on the root of my SD card then boot into my bootloader then follow the prompts.

Sent from Dorian's HTC Hero CDMA
[Android] pokerhiih:
I think you have misunderstood us....
[Android] leith51:
Or you could use 1 of the many splash screen flashing tools knocking around xda
[Android] TMartin:
An unreleased official release...that is the issue. I believe the term is intellectual property. This is how HTC found 911sniper.
[Android] leith51:
I see
[Android] nitr00:
Thanks alot for your explanation, I will await the fix you got in mind.

Keep up the good work mate.
[Android] steal25:
is their a script or plug in for the kitchen that will seek out and remove unwanted language packs? I've searched all over to no avail and found nothing, so just wondering?
[Android] dsixda:
Maybe that file needs the Ignore (-I) flag? I am planning on adding Ignore support for the single file deodex option soon.
[Android] dsixda:
I don't know anything about modifying language packs and theming and stuff like that.. sorry
[Android] blahbl4hblah:
dsixda, any chance you can answer my question from the previous page?
[Android] dsixda:
I don't understand the question.
[Android] tonyzz:
Dsixda

Thank you for the kitchen I use it for my captivate works great all in one perfect

Sent from my Samsung Captivate I897
[Android] dsixda:
Great! I haven't made the guide yet but it looks like u figured it out and got it working successfully :)
[Android] builtonRock:
Could somebody help me out? I'm a big noob at all this ROM business, but I finally managed to get the kitchen up and running, and am trying to port the SFM 1.2 ROM from Salsa to Wildfire. I have managed to install from the SD Card, but now it is stuck in a bootloop. When I debugged it with LOGCAT, it tells me 'cannot get intent action - no such field!"

What have I done wrong?
[Android] dsixda:
Not sure about this... sorry. You're better off asking in the chef forum not in the kitchen thread. If you are new to this then you shouldn't be starting out with porting roms. Have you tried to make a regular ROM for your device and gotten to know how everything works? I'm not a porting expert so I cannot really help here -- the kitchen uses very general rules for porting, but to make it work properly requires additional work by someone who needs to know what he's doing. (That's why it's in the Advanced options and it states in the porting menu that it is for advanced users.)
[Android] sharkie405:
@ BuiltonRock, This is an absolute must do. If you're serious about making ROMs, you gotta start from the ground up. ;)
[Android] computerkid23:
when building the rom i get

scripts/build_rom: line 177: zip: command not found

never had the problem til the newer version but i could be doing something wrong lol
[Android] craigbailey1986:
Question dsixda, can this be used for the motorola photon? Or should I just test it out and see if it works. not worried about bricking the phone, but would like a heads up.lol... thanks in advance:D
[Android] jikantaru:
Thanks, for your answers in flashing splashscreens actually I already made flashable zips before i posted here, i wish dsixda would make it to in the kitchen, cause in some option in kitchen there is an option to put radio, maybe dsixda can make also option to put splashscreen. :D
[Android] winpih:
....

I am using Htc Rider(Evo4G+)

My phone is only korea version but similer to Evo3D

I want to make my custom rom so i used Android kitchen v0.178 Tool

but failed....

This is recovery error log

minzip: Extracted file "/system/bin/mpdecision"

minzip: Extracted file "/system/bin/mtpd"

minzip: Extracted file "/system/bin/ndc"

minzip: Extracted file "/system/bin/netcfg"

minzip: Extracted file "/system/bin/netd"

minzip: Extracted file "/system/E:Error in /sdcard/rider_signed_090911_174415.zip

(Status 0)

i am using CWM recovery v5.0.2

Why happen error?

Just, I selected 2 - Add root permissions, 3 - Add BusyBox menu

I attach system.img and boot_singed.img

boot_singed.img:

link-> files.ucloud.com/pf/D877169_6620658_610559

system.img:

link-> files.ucloud.com/pf/D877169_6620658_610551

please.. help me
[Android] dsixda:
I answer this kind of question every week ;) Please read the FAQ part 2.

No this kitchen is for ROMs, not for separate themes or whatever. Please read the FAQ part 2.
[Android] dsixda:
Hi guys, Android Kitchen 0.179 is now up. Please read the Release Notes for details.

By the way, the lib.img file support has been added.
[Android] pokerhiih:
Works....Thx
[Android] dsixda:
As I warned on page 1, if the device is not listed on Page 1 then do not flash anything.

Anyways I will also take a look at your link later. Thank you

UPDATE: Can you rename /tools/edify_defs/shooter to /tools/edify_defs/rider, and then let me know if that works. You are saying it's similar to the Evo 3D ('Shooter'), so I'm assuming it has the same mount points.
[Android] dsixda:
Hi guys, if you are using VirtualBox for Linux and find it runs too slow for you, then try the Wubi installation method. I have updated the instructions in the FAQ.
[Android] famonaco:
Thx mate :)
[Android] shad0wboss:
if something goes wrong while flashing the cooked rom, the device doesn't brick does it? i mean porting a rom from one phone to another (I9001 not listed in compatibility)...just curious before i start flashing a ported rom onto my phone....
[Android] pokerhiih:
Hey ... maybe a noob question ... how to re-pack boot.img???:confused:
[Android] dsixda:
What do you think a 'recovery' menu is for ;-) If you're not sure what a ROM is going to do to your device, then don't proceed to porting. You must first understand how to build a regular ROM and know how it works. Don't use an I9001, it's not even supported on Post #1 - so why use it?

Unpack it first
[Android] shad0wboss:
Well i was hoping it might work with I9001 since Galaxy S/Desire HD are more or less similar to it in hardware wise and rom structure wise...

well i think i'll be able to recover from a bad rom but i want to go forward port a rom...but there isn't enough about it...it doesn't say anything about porting whatsoever...about shifting libs, sensors, drivers from original rom?

can you tell me about this a bit
[Android] jorim.tielemans:
More important, set up a working folder.
[Android] dsixda:
Galaxy S and Desire HD are totally different structurally from each other, one is by Samsung, other is by HTC. One uses zImage, other uses boot.img, etc. Also the I9001 uses the Galaxy S file format, but the kitchen does not have any checks for an I9001, so it's going to assume the common (HTC) Android file structure and will mess up.

Well, I have answered this in the FAQ (part 2). As I said on post #1, this is not a tutorial thread as I only write scripts, so I can't help much. There has been info about your question (sensors, drivers etc.) in this thread, so you can try searching for the answer.. I believe TMartin posted something once about it. I am not a porting expert however.
[Android] dsixda:
Guys, please read the FAQ before asking a question.

I know I have said this many times on Page 1, but it's worth repeating. It saves you (AND ME) a lot of time. :( Thank you.
[Android] dewasha:
thanks for your work
[Android] dsixda:
I am retiring this project.

Thanks to everyone for the feedback and help, I've met a lot of nice people on XDA through this tool, but unfortunately this is not something I can constantly update for the rest of my life. Family commitments, health issues and new responsibilities at work make it impossible to work on this anymore. In the meantime, please refer to Post #1 on how to get newer HTC device (and possibly other device) to work with the kitchen.
[Android] dsixda:
Closing this thread. It's been a blast!
[Android] Farmer Ted:
I got a request to re-open this thread, as there have been some updates to the kitchen since the thread was closed. Have at it!
[Android] dsixda:
No... I was just finishing up whatever I had left to do, I had a pile of requests to fulfill. I am not trying to keep this thread alive. Sorry guys. If you have anything urgent please refer to my Twitter.

Please, do not re-open this thread without referring to me. I am unable to keep up with this thread and I have legitimate reasons. Please refer to Post #1. After the Galaxy S2/Nexus stuff I am not doing any more regular work. Sorry again.. Thank you.
[Android] dsixda:
I'll let someone else find that, personally I am not interested in signing APKs as it's outside the scope of the kitchen and will complicate everything.
[Android] n10zf8:
Re: [KITCHEN][APRIL 17 '10] HTC Android Basic Kitchen, v0.46 [Linux / Mac / Cygwin]

i agree with you about the complication and don't think it wise to screw with those unless you understand it completely but here it is

http://xdaforums.com/showpost.php?p=3175518&postcount=2

cheers

Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk
[Android] oshizzle1991:
dude im like on version .36...will i still be able to upgrade to the newest version or will i have to go through all of them? =/
[Android] dsixda:
Just download the latest
[Android] oshizzle1991:
bamf thanks man
[Android] dsixda:
Hi guys, there was a bug in version 0.46 for porting ROMs. The end of the ROM porting would not build the boot.img in some cases. Sorry about that. This has now been fixed in 0.47... this new version also has a couple other new features. Take a look at the Release Notes in post #2 for more information.