yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
What's in the META-INF/com/google/android folder of your ZIP?

The "boot" folder must contain initrd.gz and zImage. If you are starting with a Desire ROM and want to convert it into an HD2 ROM, then choose Option 20 from the Advanced menu to convert the boot.img into a NAND boot folder. Then, replace the zImage with an HD2's zImage, and do everything else necessary (such as the modules and crap). Then build the ROM.

When importing a new ROM for your working folder, it will only convert it to update-script if it finds an updater-script (because, the kitchen can only perform operations on an update-script. UpdateR-scripts are too complicated to modify because there are so many combinations for every command).

Upon building your ROM, if it finds that the update-script contains commands that only work in an updater-script, it will convert it to updater-script automatically. Otherwise, you have the option of keeping the update-script or converting it to updater-script.
[Android] shree.cse:
Thank-you! I did everything same as you said but confused at update script

I feel that I did some thing wrong in that update script, can I replace the update script.org file from the path Meta-inf/com/google/android from a working build zip on my mobile?
[Android] dsixda:
I wouldn't mix up update-script because that will screw up your flash.

What are your errors? You need to be specific.
[Android] shree.cse:
I have two files in META-INF/com/google/android

update-script.orig and update-script

I think, I must have these two instead update-binary and updater-script.
[Android] dsixda:
Why do you have both an update-script.orig and update-script?

If you have an update-script.orig then that means you should have an updateR-script.

You did something wrong by manually copying the update-script or something. If you followed the default instructions in the kitchen then you'd be fine. Sorry, I probably can't help you any further but you have to start again and just follow the instructions on the screen and just hit Enter at the prompts to use the defaults. Don't try to complicate anything, keep it simple. Good luck!
[Android] shree.cse:
This is my issue

After creating the working folder, I am receiving this message

Found an updater-script but not an update-script. The kitchen currently can only modify an update-script.

1= Convert the updater-script (recommended)

2= Let the kitchen create an update-script

3= Do nothing

I am selecting the first option which was stated as recommended

At the end...

Making update.zip....

Update.zip created

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

update-script detected in ROM

To ensure compatibility with newer custom recovery images, .....

Your working folder will remain the same and continue to have the original update-script.

Add update-script to Rom (y/n)? <default: n>: n

Keeping update-script

Signing update.zip as signed_020911_090534.zip ....

Found OUTPUT_ZIP folder

Now I checked the folder META-INF/com/google/android There is only one file update-script

Now can you please tell me, where am I making mistake?
[Android] shree.cse:
I even tried converting update-script to updater-script

While doing this

It shows the message like this

Converting to updater-script, please wait .....

-run_program ....

-show_progress ....

-delete_recursive ....

-symlink (may take a few minutes) ....

-set_perm_recursive ....

-set_perm ....

-package_extract_file ....

-write_raw_image ....

-format and mount ....

After this the screen never displays anything. I waited for 4hrs in the last night and atlast I closed the window

I have these 4files in META-INF/com/google/android

update-binary.orig

updater-script

updater-script.orig

update-script
[Android] shree.cse:
As another choice I did this

Making update.zip....

Update.zip created

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

update-script detected in ROM

To ensure compatibility with newer custom recovery images, .....

Your working folder will remain the same and continue to have the original update-script.

Add update-script to Rom (y/n)? <default: n>: y

Error: Although you have an updater-script, you also have an update script. Remove one of them. proceed (y/n)?

Even now the zip file installation was aborted in my phone
[Android] dsixda:
You shouldn't do any conversion manually unless there is a specific requirement for you to do so. Normally you just need to do the conversions if you're asked during the process of extracting or building a ROM.

Can you post your original updater-script (the one you started with, not the one that was created after conversion)? If you have problems with an update/updater-script conversion, you should post it. Paste it here within

tags or paste it in http://pastebin.com.

EDIT: Actually I know why it was stuck in that "format and mount" section. heheh... It was forever looping because it couldn't find something. Bug in my script :) I'll fix that ASAP.
[Android] shree.cse:
Thanks, what shall I do now! I will Wait for the update.

But, I tried two different custom Roms but had the same issue. I will try using Official stock rom as my base.

I think for Stock roms, Its easy for me to exctract and rebuild wit system.img and boot.img!
[Android] theintelligent:
I am talking about the command

busybox --install -s /system/xbin

This is not executed as when I manually execute this command there are many binary files that are created in system/xbin.
[Android] shree.cse:
Thank you!

You are very fast, I didn't expect an update in this very short time. I will try again and report you back
[Android] dsixda:
Version 0.119 is now out!
[Android] shree.cse:
Every thing run Smoothly, No errors, no loops. Finally, It showed some lines to be edited in updater-script after converting update-script to updater-script at the end. I don't know how to do that.

Tried to flash my zip file using clock work recovery mode, screen shows the message updating from zip

Installing from zip and the screen freezes.

No more process on the screen

I think, I need to seek some more help from you!

Thank you!
[Android] shree.cse:
These are the lines that Kitchen said that might require change depending on the device

format("MTD", "userdata");

mount("MTD", "userdata", "???");

format("MTD", "boot");

format("MTD", "system");

mount("MTD", "system", "/system");

My device is HTC HD2 what should I change in that, Please..!
[Android] shree.cse:
I got it. Testing now! Again failed. Got the error, Installation Aborted
[Android] bharathbala2003:
Hi, I am new to android and i use ubuntu as my main OS.. i followed all the steps and i am able to see the menu in the terminal window but i am unable to select any option other than x (exit option).. which ever i select n press enter it just deletes the character n the cursor keeps blinking on same spot allowing me to re-enter the choice... can you help me out pls
[Android] dsixda:
???= "data". If you had kept the updater-script.orig then this part would have been set to "data" already and not "???".

Did you do a Google search for the error message under Clockwork recovery? What's in your recovery.log?

BTW Please don't post multiple consecutive replies, just edit the first reply and add information there. Otherwise there is unnecessary clutter in my thread. Thx
[Android] dsixda:
Sorry dude I don't know. You said you use Ubuntu as your main OS, so maybe you can figure this out.

Make sure you're not drinking.
[Android] shree.cse:
Sorry for that, I am posting these from my mobile. I feel that Editing and posting takes me more time to do, so I did posted consecutive replies.

Ontopic: I used other builds statements which does worked on my mobile and with same base.

I didn't got any error message, Just the 'installation aborted'. That's it!

Edit: Other builds statements means the 5 statements that I mentioned in the previous post, As I saw they are almost same with some modifications and I thought that may be they were the required changes and I copied them to my updater-script.

And now I edited the build and I again flashed it. Now I got the following error,

Error: Installation aborted

Toggle signature verification failed

Sorry for this question, I don't know how to get the recovery.log file, I searched for that file in cache, sbin and temp. Everything was empty. If you don't mind Can you please tell me?
[Android] dsixda:
What do you mean by "other builds statements"?

Post the recovery.log, search Google, post your original updater-script, etc. as I already advised. You have to be specific. Anyways I am going to work now so I cannot help right now.
[Android] nikitto:
Well, Flecky and me are working on with Desire HD. The kitchen works properly with stock ROM (boot & system.img). But it doesn't work with cooked roms with updater.

Why don't you keep the same updater-script from the cooked ROM ? And after 99, you ask us if we want to edit (& use) that updater-script before cooking the ROM.

Anyway, thanks for the kitchen. It's a great tool.
[Android] dsixda:
What do you mean 'doesn't work'? Please be specific... post the updater-script, post the recovery.log, post the error message, etc. I can't debug anything without information.

Guys, I have probably explained this one hundred times in this thread ;) Re-visit my post from yesterday (go to bottom):

http://xdaforums.com/showpost.php?p=11215706&postcount=3270

Or see answer in FAQ..
[Android] dsixda:
OK, much better.. So you have a problem with the signature verification. Did you wait for the ROM to be signed when you built it?? Otherwise if you interrupted it you are left with an unsigned update.zip. This seems like what you are seeing.

Your recovery menu has an option to turn signature verification off, but looks like you left it on... you are trying to verify the signature of a ROM that is not signed.

Recovery.log may be found in the "Other" Options menu. Look for something like "Copy recovery.log to SD".

Anyways, next time allow the build to complete (sign the ROM) so that you don't confuse yourself or me. It's hard to diagnose an error which is due to user misconfiguration.

BTW, another thing --- Do not use Option 22 to convert your script, as I already told you yesterday. Just follow the prompts when you extract your ROM and also when you build it, and press Enter for the defaults. The kitchen takes care of the conversions for you. So DON'T go into Option 22 at any time unless you are doing it for a specific reason and you know what you are doing.
[Android] shree.cse:
I didn't interrupted anything, Kitchen does all the things and kept the Signed zip file in OUTPUT_ZIP folder, and I copied the same zip file and flashed.

Even I flashed the same build with the signature verification off

I didn't see any options like Other in the Recovery menu. May be HD2 is different, Non-native Android device. I don't know!
[Android] dsixda:
Maybe you should have a chat with the guy which got it working successfully with the kitchen the other day. See previous posts. I don't have an HD2 so I can't do much.
[Android] shree.cse:
May be that will solve all my issues, Thank you!
[Android] Alex-V:
I only want to thank you for don´t give up this kitchen...thanks on the work on it :) :):):):p;)

with kind regards...Alex
[Android] dsixda:
Let me know if there are any issues with the kitchen if you solve your problem, thanks!
[Android] dsixda:
Ok, found the reason for the converter not recognizing the '/data' partition. It's a bug in the script.. sorry. I'll have a fix up soon.
[Android] shree.cse:
This does really sounds good! So, now I can make it

Can you please check the compatibility with HD2, can u tell me any HD2 user you know, who used the Kitchen for cooking.
[Android] dsixda:
Dude.. why dont you just read the posts from yesterday like I told you a few posts up. :rolleyes: :confused: I don't want to spoon feed everything. Remember, learning involves doing the work and investigation on your own as well. Send him a PM, and Good Luck
[Android] dsixda:
And... 0.120 is now out. Some more bug fixes for all that updater-script-update-script mumbo-jumbo crap.
[Android] shree.cse:
Sorry, I forgot that. Thanks for the update. I feel that all these things that u done are at ur finger tips.

Thanks!

Sorry to say, I can't find any other use who does working on HD2 with this kitchen. You just released version that supports HD2 a couple of days back. I can find people working on DesireHD and other native Android devices. I am trying with your latest update. Report u back soon

Edit:

Failed again with the latest update. Now I didn't saw any error messages like ' These line might require a change depending on the device'

May be the reason Kitchen doesn't work with Non-native Android devices.

Thanks for everything!
[Android] Droidzone:
@dsixda,

Started having this error from v0.119. Never had it before.

6:format("MTD", "system");

7:mount("MTD", "system", "/system");
10:mount("MTD", "userdata", "/data");
92:mount("MTD", "boot", "/boot");

Proceed with the change (y/n)?

y = Proceed; updater-script and update-binary will be moved to the ZIP
file; update-script in ZIP file will be removed but will remain in
working folder.
n = Cancel; updater-script and update-binary will be deleted and not
used.

? (default: y): y
adding: META-INF/com/google/android/updater-script (deflated 79%)
adding: META-INF/com/google/android/update-binary (deflated 39%)
zip warning: missing end signature--probably not a zip file (did you
zip warning: remember to use binary mode when you transferred it?)
zip warning: (if you are trying to read a damaged archive try -F)

zip error: Zip file structure invalid (update.zip)

Signing update.zip as signed_021011_113043.zip ...
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.jar.JarFile.<init>(Unknown Source)
at java.util.jar.JarFile.<init>(Unknown Source)
at com.android.signapk.SignApk.main(SignApk.java:320)

Was not able to create signed_021011_113043.zip!

Ensure you have the Sun Java JDK installed on your PC, and have
defined the path to java.exe.

e.g. In /home/Joel/.bash_profile, add to the end:
PATH=/cygdrive/c/Program\ Files/Java/jdk1.6.0_18/bin:${PATH}

Your path may be different.

Press Enter to continue

Apparently it's having issues creating zip files.
[Android] shree.cse:
First update the kitchen! Your very first error with those 4statements will be out

When did you installed java on your system, I mean before or after installing the kitchen. As I saw in FAQ's It will cause some errors if java was installed after Kitchen.

I don't think the Toast 'convert to updater-script from update-script' as an error.

On which device are you working for?

I am working for HD2

I don't have any issues but the signed zip doesn't work for me. Stucked at installing update message in CWM recovery for hours.
[Android] ghkdgns:
Thank You~
[Android] dsixda:
Hi Shree -- send the user "totalcmdext" a PM - he got it to work on HD2.
[Android] mike1986.:
dsixda I was wondering if you can include zipalign.exe from newest SDK in your kitchen? I always replace it manually but anyway it might be worth having it there by default. Also here is newer busybox 1.18.1 that e.g. fixes the problem with ad-free updates.
[Android] dsixda:
OK I will look for the zipalign binaries - I will need the versions for all 3 operating systems. Thanks

Btw are you talking about the app called AdFree?
[Android] mike1986.:
Yes. With previous busybox there was always error while downloading hosts file. Not only me had this problem, all DHD custom ROMS had it. With 1.18.1 this problem was gone. I know the newest version is 1.18.3 but I don't have it yet.
[Android] Droidzone:
Yea..that was it..Never guessed that it could be low disk space..
[Android] shree.cse:
Thanks for spoon feeding me, I saw that post, but I thought that might be on some other device. May the problem I didn't read that properly.

I did a PM to him

Thanks again
[Android] Orphee:
Hello,

I'm using the HTC Android Kitchen to make my own Desire ROM.

I start from the file RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release_159811_signed.exe

I copied from temp folder the rom.zip contained in it.

With the kitchen, I succeed to install root, busybox.

It works, the Desire boot well.

When I try to deodex the ROM, after the flash is complete, I have a bootloop on HTC Logo...

any idea ?

Thank you
[Android] dsixda:
You have signature issues... if you changed an apk or re-signed some files then you'll get that.
[Android] Orphee:
So after the doedex option I don't need to sign all *.apk ?

I did sign all *.apk with the menu, and then a ZipAligning

I should not do this ?

I have java error on RSS.odex and com.htc.rss.odex but it seems to be normal if I look at the script :

elif [ "$odex_file" == "RSS.odex" ]

then

classfile=com.htc.rss.jar

ignore_errors=yes

elif [ "$odex_file" == "com.htc.rss.odex" ]

then

ignore_errors=yes

fi

Thank you

Edit :

In Desire Developpement section, no one still has deodexed the 2.29.405.5... maybe because there is a problem with it ?

I will try to deodex 2.29.405.2 to check (it is already deodexed in Desire developpement section)
[Android] Orphee:
Hum...

I tried again to deodex from beginning...

I have an error on framework.odex :

NOW AT FILE 15 OF 22 IN system/framework: framework.odex

Disassembling framework.odex ...

java -Xmx512m -jar baksmali.jar -d ../framework -x framework.odex

Assembling into classes.dex ...

java -Xmx512m -jar smali.jar -o classes.dex out

out\com\android\internal\telephony\Connection$DisconnectCause.smali[0,0] null

WARNING: Unable to produce classes.dex, not good!

...

Finished system/framework

131 *.odex files remain in system/app

1 *.odex files remain in system/framework

If I try to deodex it as a single file with no dependencies.. it works, but I guess it is not good... ?

Thank you

It's weird ! I tried again with the same framework folder taken from backup, and did not reproduce the error... -_-
[Android] dsixda:
Why are you signing all the files?? If it was necessary then the kitchen would have done that automatically after deodexing, or at least it would've told you. Just follow the instructions on the screen and use the defaults if you get prompted for anything.

Yup, that's normal.

Send me a link to the file so that I can download it (no file-sharing site please, I have proxy at work). I am boarding a plane tonight so I could check it during my flight if I have time.
[Android] Droidzone:
Actually the last part isnt true. I've used the kitchen to deodeox 2.29.405. It had no issues whatsoever.
[Android] Orphee:
here is the link :

http://www.shipped-roms.com/shipped...9.00.32U_5.11.05.27_release_159811_signed.exe
[Android] Orphee:
Did you deoded 2.29.405.5 or 2.29.405.2 ?

Because no one released 2.29.405.5 doedexed... i didn't find any link.
[Android] Droidzone:
@dsixda,

I wish there was a "Build with defaults" and "Choose defaults automatically" option for the kitchen. Because after the first time I port a rom, there usually isnt any need for me to accept anything other the defaults for most of the scenarios, except the "remover updater-script" option. If the kitchen would just check a settings file to see if this option had been chosen, and if so would proceed with defaults, then I could just leave it to build without choosing Enter each time..
[Android] Droidzone:
Really? Check out the rom in my signature!
[Android] dsixda:
No it's better to leave it that way in case there is an issue and the user needs to be notified. I don't want people blindly bypassing options and then reporting issues without knowing what they are doing.

That's extra unnecessary work for me, just to save you two keystrokes... Don't be lazy ;)
[Android] dsixda:
So the ROM in the link you sent me doesn't need to be investigated? The kitchen deodexing tool works fine with this one, without extra steps?
[Android] godfather123189:
thanks

hey bud, thanks for the constant updates on the kitchen :)

i wanted to tell you that you should add the mytouch4g to that list of supported htc phones.. i was able to deodex and build a rom for it with the kitchen with the newest version
[Android] Droidzone:
I didnt do any extra steps at all with the 2.29.405 Desire PB99img to deodex it. The kitchen worked with it just fine..I think it was the 0.110 version.
[Android] Alex-V:
Can confirm this...no problems with deodex 2.29 :)

with kind regards..Alex
[Android] anryl:
just found it :D THNX :cool:
[Android] 5noc:
After quite a few flashes I've find out that my phone keeps rebooting after I flash an image with some apps removed manually. I mean, I've downloaded dsixda's room here http://xdaforums.com/showthread.php?t=927935 the rooted, de-odexed and trackball wake one, embeded some ringtones and notification sounds on it and tried flashing it each time I made a change to the rom to finally see that when I delete some stock apps I dont use (list is down) my phone wont past after the coloured X, it keeps restarting the animation until the end of days...

Any ideas on why can this be happening? This is not the first time I do this and other times has worked nice :confused:

The apps I delete from the app folder are:

CarHomeGoogle.apk
CarHomeLauncher.apk
com.amazon.mp3.apk
EmailGoogle.apk
googlevoice.apk
kickback.apk
soundback.apk
talkback.apk
Twitter.apk

Thanks in advance :)

Editing to clarify: when creating the working folder I choose to remove the install-recovery.sh and the recovery-from-boot.p AND when I create the rom I choose to keep the original update-script. Flashing the rom with Amon_RA's 2.2.1 recovery.
[Android] dsixda:
Please read the FAQ first, as I advised before the download link.

Also, do you know what kickback, soundback, talkback etc. do? If you remove core system apps you will get a device that wont boot.
[Android] 5noc:
I thought I did, those had something to do with haptic feedback and accessibility options. I kept them this time and it worked like a charm, weird as I used to remove those on othe roms :rolleyes:

¡Thanks for the awesomeness!
[Android] Droidzone:
I'm having an odd issue with the kitchen's handling of updater/update scripts.

I had all three in working folder. Update-script which the kitchen made, and updater-scriipt which I made myself.

Now, at the build procedure, see this:

Checking whether update-script requires update for /system/etc/init.d ...
update-script is being modified

Making update.zip ...

update.zip created

NOTE: update-script must be converted to an updater-script before flashing

Error: Although you have an update-script, you also have an
updater-script in the same folder. Remove one of them.
Proceed with the change (y/n)?

y = Proceed; updater-script and update-binary will be moved to the ZIP
file; update-script in ZIP file will be removed but will remain in
working folder.
n = Cancel; updater-script and update-binary will be deleted and not
used.

? (default: y): Y
updating: META-INF/com/google/android/update-binary (deflated 39%)
updating: META-INF/com/google/android/updater-script (deflated 81%)
deleting: META-INF/com/google/android/update-script

Signing update.zip as signed_021111_203119.zip ...

Apparently it is removing update-script and leaving updater-script..

But actually what happened was that it removed update-binary and updater-script and left behind update-script in the zip, and left update-binary and updater-script, removing update-script from working folder.

And there is no reason why it should remove update-script at all. If recovery encounters both updater and update, it will just choose the updater.
[Android] Droidzone:
@dsixda,

Instead of this, what the kitchen used to do previously was just perfect, it would simply rename them to .old. That way, if something went wrong, the only thing one needed to do was to rename them back. Removing them seems to be risky..
[Android] shree.cse:
Which version are you using. I have the same issue with the previous one, with the latest update of v0.120 this problem was solved. Any way I am making for HD2, I am not Succeded in final, no reason that kitchen to be blamed, but something different with updater-script for HD2 as it was a non native Android device.

Update to the latest version and do it again, you problem will be solved.