yashsingh1/xdaforums huggingface dataset:
[Android] Droidzone:
I am on 0.120
[Android] shree.cse:
Have you done this conversion initially? Updater-script to update-script

And at the end while making zip, it will ask you to convert update-script to updater-script, right?

By default it says the option is no, but do the conversion.

If you did this you won't get that error. Try it once and report it back.

Edit: If you got the same error even now, try converting manually before building the zip. Option #22 in advance menu.

Make sure, you can't do anything else other than option#99 which is for making zip. As the kitchen can't do any modifications to updater-script
[Android] Droidzone:
I didnt do the conversion. I create the updater-script on my own. The kitchen didnt have to do anything to the update-script/updater-script. I had both of them in meta-inf. That's the way I've done it all these weeks..

Edit: Anyway, there are no more bugs after the initial process is over..Now I just keep both of them there and it seems to be fine..
[Android] shree.cse:
On your own? How do you create update-script on your own?

I don't know how to do that. Anyway good!

Now your problem solved?
[Android] Droidzone:
By typing it out.. :)

Anyway I let the kitchen work it out at first, creating the toolbox symlinks etc, then manually add all the extra commands I want and edit out what I dont want..Anyway with the latest versions, the kitchen seems pretty good, though I had an error today..minor one again in syntax

Yea, problem doesnt recur..maybe it occurs only first time the rom is added from the RUU..
[Android] IzaacJ:
Hello. Thanks for a wonderful kitchen, just need some info on how to make an app the default one and how to edit it settings so they are set upon first boot?

Want to make GO SMS the default message app, and customize the notifications... Any ideas?

My rom is based on charsingh_onlines unofficial nightly CM7 builds.
[Android] shree.cse:
Hey! Are you working on HD2?
[Android] dsixda:
Hold on.. back up a bit --- The problem here is that you had both an update-script and updater-script in your working folder before you built the ROM. -- Why did you do that? :confused: You should only have one of the two present; otherwise it will lead to unexpected results and your own confusion when you flash a ROM, not knowing which script was used.

However, there is a bug in the kitchen due to your misconfiguration because it didn't check for the presence of both update-script/updater-script together before building the update.zip, thus you put the kitchen into a confused state. Anyways I will fix this.

See reply above... nothing changed. When the kitchen converts a script it renames it to *.orig. Because of your misconfiguration the kitchen thought the updater-script was the temporary one it created during build time (not one that you made), that's why it deleted it, not realizing it was actually the one you had created on your own.

What is the syntax error -- Was it during a conversion? Please attach the original file that you tried to convert, if that is the case. I want to make sure my scripts are as error-free as possible. Thanks
[Android] Droidzone:
Unfortunately this time I was in a hurry to release my Rom and didnt make backups of the working folder/update-zips.

The error was that in the generated file (not the one I typed up. I did that late into the build) which the kitchen made, it repeated a few lines; and a syntax error in the command to write the raw_image (updater-script) which the kitchen made-wherein it omitted the comma between "/tmp/boot.img" and "boot.img.". It became like /tmp/boot.imgboot.img.

I know it is very vague and probably unhelpful, but I didnt make a log/backup of the error, and just corrected it pronto. Will monitor for errors next time.

About the misconfiguration..well..I usually have both scripts in my meta-inf, since that's helpful i case I want the kitchen to work on my script, I can just rename the updater-script before importing it, and vice versa. Anyway, sorry that it is creating problems with the alogorithm..
[Android] dsixda:
You can rename the files to update-script.tmp or something like that, so that it has your unique name that the kitchen won't have an issue with it.

I'll check out that syntax error of yours and try to reproduce it later.

Anyways thanks for the reply
[Android] Droidzone:
Aha..Got it again! :)

Attached..

Original updater-script:

And the kitchen-converted update-script:

That obviously results in:

"package_extract_file() expects 2 args, got 1

Error in /...zip (Status 7) Install aborted"
[Android] dsixda:
Error noted.. thanks very much. That won't be hard for me to fix.
[Android] dsixda:
Ok, Android Kitchen 0.121 is now out. :-)
[Android] Droidzone:
@dsixda, This is just a documentation rather than a bug report:

I see that your new script to check for and delete the temporary zip file that used to be added to the zip file is working..

The following is a case where it was generated and the step at which it was generated:

And then, the kitchen prompted and deleted it correctly:

Great work!
[Android] IzaacJ:
Yes I am :) And it's going good :) Two things left to consider it finished, settings for the apps defined (dont know how thou) and get WiFi working, which stopped working for some reason "/ Could be my weird router thou.
[Android] Droidzone:
Sounds like a bad kernel integration
[Android] eViL D::
Where can I edit the bootclasspath? I always have to do single file with HTC framework. Apps work fine though. Maybe an option to just set the classpath once would be nice in "single" options.
[Android] mike1986.:
dsixda what would you say for adding possibility to extract EXT3/EXT4 data.img? I know it can be done by renaming "data.img" into "system.img" + including with boot.img in original_update folder and building working folder. But anyway it will be nice to have such a feature without theses "hacks" ;) It's very useful for viewing the content of data partition backup with NANDROID.
[Android] dsixda:
Sounds like a good idea. However, does the EXT3/4 data.img Nandroid backup require Explore2FS or similar tool, instead of unyaffs (is it in yaffs2 format after nandroid backup)?
[Android] dsixda:
Haha, I'm not touching that damn deodex routine after wasting a month of last summer on it. ;-)

I don't fully understand what you want to do. You said you cannot deodex a file using the regular 'all files' option, and so you use the single file option. So, all you need to do is specify the extra classfiles. Do you mean that you are using the same extra classfile names for multiple files?

Where is the link to this ROM?
[Android] eViL D::
Yeah, if I use "all files", it will eventually deodex the framework, but it takes forever since it's not using the correct classpath. But, it also cannot do a couple. I am deodexing for vision and glacier.

This is what needs to be included:

core.jar:ext.jar:framework.jar:android.policy.jar:services.jar:com.htc.framework.jar:com.htc.android.pimlib.jar:com.htc.android.easopen.jar:com.scalado.util.ScaladoUtil.jar:javax.obex.jar:com.google.android.maps.jar:com.google.translate.jar:ime.jar:input.jar:am.jar:android.test.runner.jar:bmgr.jar:monkey.jar:pm.jar:svc.jar:framework-tests.jar:com.orange.authentication.simcard.jar

Ok, hold on.

I'm now using version .114 (yes, this is old). It SEEMS to be working fine now. Previous version however would not. I honestly gave up on trying the "all" option on other versions. I'll report back if I get anymore errors.

EDIT 2:

Ok, this version is perfect. You're a star. Thanks!
[Android] mike1986.:
It depends with which CMW the nandroid backup was made. With CMW 2 it should be yaffs 2 but I'm not sure about cmw 3.
[Android] dsixda:
No problem, I guess explore2fs can take care of that case.
[Android] shree.cse:
That's great! Have you got a build working on your mobile?
[Android] mike1986.:
hm I've noticed that your kitchen adds "installbusybox" file + command to execute it on boot in updater-script. What's the difference if I don't have such "installbusybox" but I have set the permissions manually with:

+

+

all busybox symlinks in updater-script.

What's the advantage of adding "installbusybox" file?
[Android] dsixda:
It keeps the updater-script/update-script small and simple. Plus, different versions of busybox may have different numbers of symlinks, so mentioning them directly in the update-script is not good practise, if you don't how many symlinks actually exist with busybox.
[Android] theintelligent:
I have found the solution i.e. I create symlinks manually in the updater-script instead of executing the command stated above :)
[Android] dsixda:
That's a workaround, not a solution
[Android] mike1986.:
Ok so you suggest to remove all busybox symlinks from updater-script, add installbusybox to working folder and leave only this:

Or should I use set_perm(0, 1000, 0755, "/system/xbin/busybox");

instead of set_perm(0, 0, 04755, "/system/xbin/busybox"); ?

And last thing. I found you have much more toolbox symlinks. Yours:

and mine:

I think it's because I symlinked some of them with busybox instead of toolbox?
[Android] dsixda:
I build the update-script toolbox symlinks by grabbing all the existing symbolic links that physically exist in /system/bin of the shipped ROM. So yeah it may have more than you have, BUT, keep in mind that there are scripts that sometimes refer to symlinks in /system/bin rather than /system/xbin. So be careful when you delete symlinks under /system/bin.

I'm not sure about the permissions question you asked above, let me know if u see anything strange.
[Android] mike1986.:
Well in ROM dump I made there are also 51 symlinks but some of them I "moved" to busybox symlink like:

So I think I will remove all busybox symlinks, add all 51 toolbox symlinks and try cooking ROM with installbusybox file. What do you think?

And also message I got from BlaY0 long time ago when I asked something:

So maybe it's good idea to keep toolbox symlinks in bin and busybox symlinks in xbin?
[Android] dsixda:
Yes

10chars
[Android] KBizzle:
Im sure this has been asked a hundred times but i did some searching and wasnt able to find an answer. Its even in the Q&A on the first page but it doesnt really answer the question. I built my first rom just a moment ago using Calkuins rom as my base. I didnt make many changes except for the boot animation and added titanium back up and some minor changes to the init.d scripts but I am getting "E:Can't open (bad)". I am using Amon Ra recovery and the link under the Q&A for that problem has a member stating his issue was because of clockwork recovery. So I am assuming its not my recovery. Any help is appreciated.
[Android] dsixda:
Well you can do a Google search, this comes up often -

The zip file is corrupted? Rename it to update.zip?
[Android] KBizzle:
Thanks. I rebuilt the Rom and tried again. This time it failed with some type of exception. I'll keep trying.
[Android] dsixda:
0.122 is now up! Please read the release notes.
[Android] irondevil:
i have a problem when i add this function "Add /etc/init.d scripts support (busybox run-parts)" to a rom the smarthone at the start up don't mount sd card (i have this problem only when i add that function)
[Android] Diegis0n:
Seems like 0.122 won't find (ZIP) roms under original_update folder ?
[Android] mike1986.:
OK so I removed busybox symlinks from updater-script and added installbusybox file with proper commands in upadater-script. But after ROM flash, xbin folder doesn't content any files except busybox, crasher, su and wireless_modem while it should contain busybox symlinks, right?
[Android] Droidzone:
Read it again. He mentions that subfolders will not be shown
[Android] theintelligent:
It was the same issue that was faced by me :) in the end I have created the symlinks manually in the updater-script.

This is still a mystery that why that command "busybox --install -s /system/xbin" is not executed although the permissions are ok and no errors are seen.
[Android] Diegis0n:
My zip is not located in a subfolder, but straight under original_update.

If i'm confused feel free to rant :)
[Android] dsixda:
You're right, it's not recognizing ZIP files! Sorry guys, I was testing Huawei ROMs and forgot to check whether the existing functionality was still working!! I have re-uploaded 0.122 with the fix.

If you want to make the change with your existing 0.122 (if you have the original version), just do this to the file scripts/choose_rom:

Line 13:

if [ "$zip_cmd" == "" ] || [ "$app_cmd" == "" ]

change to

if [ "$zip_cmd" == "" ] && [ "$app_cmd" == "" ]
[Android] jblazea50:
Dsixda, got a noob question...i have installed unbuntu, java, and your kitchen; i can get into the terminal and get the options by ./menu; but after that, how would i go about taking a custom rom (placed in the update_original folder), removing the kernel for another one, adding other update.zip which includes desire camera as well as oc-uv kernel?

sorry i know it's a noob question as it's my 1st time trying to take a custom rom and taking stuff out from it and putting other features from other roms taht i like
[Android] dsixda:
Hey man,

No problem... I'm kinda new too.. we were all new at one point.

I'm assuming both ROMs are for the Nexus One??? If so, I would replace boot.img with the one from your OC-UV ROM. This would contain the kernel and init.rc and related kernel/ramdisk files. If they were ROMs for different devices, you would need to use the Port ROM method (replace boot.img's boot.img-kernel with the one from your device's boot.img).

Then, copy over the files from /system/lib/modules from your OC-UV ROM as well.

Finally, copy over the camera files -- i have no idea where those files are ;)

EDIT: Oops, I also forgot, make sure the update-script file (found under the META-INF folder) is also from the OC-UV ROM. Or you may need to merge with the existing one.. it all depends on what files are present in each ROM.

Then build and pray!! May take trial and error. I may be wrong and maybe someone can tell you better, but these are the basic steps.
[Android] tararura:
First of all Thanks to dsixda for the great kitchen.

Now some help please......

trying to cook first rom. I am using CM5.0.5.3 and Cygwin. At the end when using option #99 it says :

scripts/build_rom: line75: java: command not found

and also

scripts/build_rom: line108: sw_vers: command not found

Thanks in advance
[Android] dsixda:
I'm sorry, I forgot to mention that you need to install the Java JDK for Windows from the Sun site. Let me know if you have more questions.

Edit: link is http://java.sun.com/javase/downloads/widget/jdk6.jsp
[Android] tararura:
thanks for the quick response.

I installed Java (tm) se development kit 6 update 17 and

Java (tm) se development kit 6 update 19 but same exact problems....
[Android] jblazea50:
thanks, appreciate the help; so basically, if i want one app from another rom, i just need to copy it to the working folder
[Android] dsixda:
I am away from my PC right now, otherwise I would've given you more detail. Basically you have to install the JDK and make sure the java.exe command is executable from any command prompt (cmd.exe). You might need to put it in your path.

I'll look into this further, soon. Look up Google in the meantime.

Eg. http://java.sun.com/j2se/1.4.2/install-windows.html

The above shows you how to set the PATH environment variable.
[Android] tararura:
Thank you

Followed the link and changed the path but still the same.:confused:
[Android] dsixda:
Okay give me a minute to check it out.
[Android] dsixda:
Aha! I figured it out. Start up Cygwin, and edit this file: .bash_profile

Add the following:

PATH=/cygdrive/c/Program\ Files/Java/jdk1.6.0_18/bin:${PATH}
[Android] tararura:
Ok its working.:)

variable name should be 'path' and if there is already a variable with that name, the new path line should be added to it.

thank you ver much dsixda

Senators are doing good ,EH!
[Android] dsixda:
Thanks for mentioning the issue, I have updated the setup guide. I will also ensure the script handles that failure better. ;) I had the day off the last few days, so I have some extra time...

Screw the Senators, I was raised in Edmonton, although this year is not a good year (Fall for Taylor Hall!).
[Android] tararura:
AaHa an Oiler.

You want to jump over to Canucks:)

Thanks for everything. Playing with the kitchen now......
[Android] robin04:
Hi dsixda

I modified the script built_boot_img to avoid the device.cfg and to continue with the script.

Afterwards The Problem Is That I Have Found When it gets to the line of script:

. / $ Mkbootimg_file - boot.img kernel-kernel - boot-ramdisk ramdisk - cmdline "no_console_suspend = 1 console = null"-o newBoot.img - basis $ basis

But Cygwin does not recognize and therefore newBOOT.img was not created

know a way to solve the problem?

maybe some package to be integrated in cygwin?:confused:
[Android] dsixda:
What is the error message, and why are you using ". /" instead of "./"? Cygwin compiles mkbootimg fine for me.

Also, why are you modifying the script and bypassing device.cfg?
[Android] dsixda:
Tararura, I have just updated the kitchen to take care of a couple of Cygwin issues (the java error and also a .bak file issue for Hero ROMs).
[Android] tararura:
3.4 is working ok.

thanks dsixda
[Android] chuti98:
something wrong with busybox

I did port Legend rom to Hero after I Flashed it then it aborted itself and said can't find busybox in the directory
[Android] dsixda:
Was the Legend ROM a cooked ROM by somebody else, or was it a stock ROM that you had used?

If you see errors during the flash it normally means you have a problem in the update-script file (under META_INF).

Also, what options did you use from the main menu?
[Android] sultan-mrm:
Dear dsixda you have to check your links , I think that multiuploader is closed.

Edit: now all of them ok I think the problem from my internet proviedr :)
[Android] dsixda:
What if you try the command manually from a terminal prompt after the ROM has been flashed?

e.g.

su
cd /system/xbin
/system/bin/chmod 755 busybox
busybox --install -s /system/xbin

mike1986 and theintelligent: What devices are you using and are you using updater-script or update-script? Could you post the update(r)-script?
[Android] theintelligent:
I have tried it manually from the terminal after the ROM installation is successful and the symlinks are created successfully via the above command.

I have Desire HD with me and I am using updater-script.
[Android] dsixda:
Can you post the updater-script here within

tags.
[Android] Diegis0n:
Thanks a lot for the fast fix :)
[Android] dsixda:
BTW,

I noticed you didn't have the following lines, does your boot.img flash properly?

run_program("/xbin/busybox/mkdir", "/boot");
mount("MTD, "boot", "/boot");

EDIT:

Ok, stupid thing to try... but for the installbusybox, can you do this instead:

package_extract_file("installbusybox", "/tmp/installbusybox");
run_program("/tmp/installbusybox");

Or

run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin/")

This last example above should work.
[Android] theintelligent:
I will try and report back to you later on.
[Android] mike1986.:
Ok so replace run_program("installbusybox"); with run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin/")? Will try it now and report back.
[Android] dsixda:
Yes, try that.

Or maybe in your original updater-script you need to swap the order of the "set_perm(....busybox)" line with the previous run_program("installbusybox") line.

set_perm(0, 0, 04755, "/system/xbin/busybox");
run_program("installbusybox");

Wish I had a Desire HD with me as well to test.
[Android] mike1986.:
With run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin/")

I got installation aborted. I will try the second method.
[Android] theintelligent:
Just a stupid question, do we need to mount system in rw mode before executing the command?
[Android] dsixda:
I thought this already does it?

mount("ext3", "EMMC", "/dev/block/mmcblk0p25", "/system");
[Android] Droidzone:
System is automatically mounted in rw mode if you issue mount for system in recovery
[Android] IzaacJ:
I got it to work. Cleaned out the kitchen and started from scratch...

Now I'll have to figure out how to customize the default settings for the apps and the system... Anyone with some knowledge about that?
[Android] mike1986.:
I have already tried:

set_perm(0, 0, 04755, "/system/xbin/busybox");
run_program("installbusybox");

and

run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin/")

and

package_extract_file("installbusybox", "/tmp/installbusybox");
run_program("/tmp/installbusybox");

None of them seems to work. Any more ideas how to install busybox correctly apart of setting the symlinks manually in updater-script?
[Android] dsixda:
That is really frustrating ... Thanks a lot for trying though. Something about the Desire HD is preventing it to work unlike other devices. I wonder if it has something to do with the permissions for the busybox binary. You had asked about the set_perm command yesterday. I wonder if using your suggested set_perm (different ownership permissions) before calling installbusybox has an effect?
[Android] dsixda:
Actually, I have just looked at my Nexus One, and my device is also missing the busybox symlinks under xbin! I wonder if it was the updater-script conversion that did it. This installbusybox used to work before.

EDIT: Ok here is my recovery.log attached. This was for a Nexus One ROM with

updater-script

. Looks like none of the scripts in the ROM are being executed. It worked fine with update-script, however.

about to run program [check_data_app] with 1 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1

about to run program [installbusybox] with 1 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1

about to run program [data/dtinstall.launch] with 1 args
run_program: execv failed: Permission denied
run_program: child exited with status 1

about to run program [move_cache_sd] with 1 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1

about to run program [/xbin/busybox/mkdir] with 2 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1

I think I need to do something like this:

package_extract_file("installbusybox", "/tmp/installbusybox");
set_perm(0, 0, 0777, "/tmp/installbusybox");
run_program("/tmp/installbusybox");

Instead of just:

run_program("installbusybox");

I'll report back later......

UPDATE: Yup, that worked! I'll have to add the fix to the kitchen later.
[Android] _fm:
hai,

i keeps getting error,. i am flashing my desire HD, after flash i still have my stock rom,. and sometime i keep getting bootloops,.

i have done this - http://xdaforums.com/showpost.php?p=10963396&postcount=3117

and also have done this - http://xdaforums.com/showpost.php?p=11103858&postcount=3217

well, what have i done wrong? am i not mounting the system correctly when flashing?

this is my mounting updater script :

well, cant i use MTD for desire HD which is EXT3 ?

thanks so much bro,.
[Android] dsixda:
@_fm:

Flash your ROM again, and BEFORE rebooting, dump the recovery.log to your SD card to check for errors during flash.

In Amon_RA Recovery, this feature is found under "Other->Move recovery.log to SD". Then mount your SD card to view the log file with a text editor (but not with Notepad).
[Android] nex7er:
While booting my rom I get stuck at the android loading screen. Attatched is my logcat.txt
[Android] dsixda:
Just say what you see wrong in there, I don't want to spend my time debugging everyone's logcat for them. This is how you learn. I just write scripts, dude.