yashsingh1/xdaforums huggingface dataset:
[Android] koider:
ifconfig -a

First of all, let me say thanks for a great tool! It's very easy to use and I love being able to specify exactly what I want in my ROM. It's also a good learning tool - because it's a collection of shell scripts it's not hard to find out what the kitchen is doing.

Now my questions ;) I've cooked a ROM using v0.87, and have included busybox. When I do "ifconfig -a" on the device it doesn't work - should it? I'd expect it to list all of the network interfaces. Querying the interfaces individually, e.g. "ifconfig rmnet0", does work. Here's what happens:

adb shell
sh-3.2# ifconfig -a
-a: No such device
sh-3.2# ls -l `which ifconfig`
lrwxrwxrwx root root 2010-08-26 23:58 ifconfig -> toolbox
sh-3.2# ifconfig
sh-3.2# ifconfig eth0
eth0: No such device
sh-3.2# ifconfig rmnet0
rmnet0: ip 178.123.456.123 mask 255.255.255.248 flags [up broadcast running multicast]
sh-3.2#

I'd also like to have a go at building busybox myself, can you share the .config file and/or any tips on how to build it (e.g. which toolchain to use)?

Thanks :)

EDIT: Adding "busybox" to the start of the command, i.e. "busybox ifconfig -a", works so it seems that the problem is something to do with command-line parsing. I am using bash in my ROM, could that have something to do with it?

EDIT 2: Doh! The ifconfig that I've been using wasn't the one from the kitchen-supplied busybox, it was the one from the stock ROM I started with (RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe). If I use /system/xbin/ifconfig everything works fine. Can I change the default PATH to have /system/xbin before /system/bin, or remove /system/bin/ifconfig, without breaking anything?
[Android] BlaY0:
If you mean changing PATH in init.rc I wouldn't suggest it (I've done this once and revert back to default in several hours) but you can change it in any of your scripts or in current shell.

Android powah!
[Android] koider:
Yes that's what I meant. Thanks for the advice :)
[Android] mr.bang:
after a complete deodexing i reported this adb install exception:

INSTALL_FAILED_DEXOPT

see this: android java doc

is this exception a kitchen's bug or not?

M
[Android] dsixda:
What do you mean by "adb install exception", and which file was it?
[Android] mr.bang:
after building rom (complete deodexed) i've flashed it on my hero.

so i when i want to install application via adb i get exception

INSTALL_FAILED_DEXOPT

M
[Android] dsixda:
What application? And why do you want to install it when you've already flashed it?

You may also want to report deodexing issues here: http://code.google.com/p/smali/
[Android] mr.bang:
after flashed deodexed rom i can install all apps i want. but when i reboot 2nd time i can't install all apps..
[Android] wikywwj:
"HTC USB MODEM" will be not found when set to mobile broadband connect,if use the update-script that generated by kitchen.It works normally if use updater-script.
[Android] dsixda:
You need to be more specific, otherwise I have no idea how to help.

Please post your updater-script and update-script.
[Android] wikywwj:
HTC Droid incredible froyo rom.

here's updater-script,I'm sorry i have deleted the original update-script.

i think maybe something wrong in the part "Creating links and setting permissions" which make the difference between update-script and updater-script.

and here's my question related:ht tp://xdaforums.com/showthread.php?t=767504
[Android] dsixda:
I know what the problem is, it's the way the script handles these copy operations to the /tmp folder. Can u send me a link to the actual ROM? Thanks..
[Android] wikywwj:
here it is:

rmk40's :h ttp://xdaforums.com/showthread.php?t=765447

wakeboard143's:h ttp://xdaforums.com/showthread.php?t=766223

they both use update-script,and both same problem exists.
[Android] dsixda:
You mean they both have the updateR-script in them when you download?
[Android] wikywwj:
just update-script

attachment above comes from another rom:

h ttp://xdaforums.com/showthread.php?t=764787

i make some change.
[Android] dsixda:
Ok, well now I am confused and I don't understand what you are trying to do. ha ha

You said you had a problem with the update-script in your ROM, so then you replaced it with an updateR-script. So do you mean the original base ROM had an updater-script?? If yes, then give me the ROM with the updateR-script

EDIT: Nevermind, unzip the files in the attachment to your /scripts folder. This should fix things for you.
[Android] dsixda:
By the way, I think there is an error in the file you attached in that post:

ui_print("Installing apps ...");
package_extract_dir("move", "/tmp");
package_extract_dir("data", "/tmp");
set_perm_recursive(1000, 1000, 0771, 0644, "[B]/temp/app[/B]");
set_perm(0, 0, 0777, "/tmp/move.sh");
run_program("/tmp/move.sh");

/temp/app should probably be /tmp/app?
[Android] dsixda:
Okay, version 0.88 is now out!
[Android] wikywwj:
no,no,no...what all i 'said is about the update-script generated by kitchen will cause "HTC USB MODEM" diappear.

ignore that data/app part,that shouldn't be related.
[Android] dsixda:
My kitchen can do magic? :D

(I know that, I just noticed that while looking at the script... Besides, you're not answering my questions.)
[Android] -Mr. X-:
thanks for the update, When you update the kitchen and the tools/apps included respectivly. whats the best prosses of updating a rom i have already cooked with the kitchen? or is there no way, should i just start fresh. the reason i ask is because when i try to add the new a2sd or the new su + superuser, it says they already exist, so i asume it has not replaced/updated.
[Android] dsixda:
I guess you should start fresh if you want to add the new apps2sd/su. Or just go to the apps2sd/su threads and download + flash the new version.
[Android] wikywwj:
well,i didn't describe clearly.

I cook a few froyo roms with your kitchen,all those roms have that issue.just 2.2,never happen when cooking 2.1 roms.

so i downloaded and tried rmk40 and wakeboard's roms to test,same problem in their rom,both of them use normal update-script to install the rom.(maybe they use your kitchen,maybe not).

then i try to download and install Skyraider's froyo rom which doesn't have that issue,it use a updateR-script.

so,i make some changes to the updateR-script copy from Skyraider's rom(the script i uploaded above),put that into my rom and install,then issue gone.

end of all,i figure it out.maybe when the kitchen is generating scripts, something missed in part of "symlink" or "set_perm".
[Android] dsixda:
I understand what you mean, the latest version of the kitchen (0.88) should have a fix for those problems. Before, when I tried converting that updater-script to an update-script, it didn't convert properly... but now it does.
[Android] listyb01:
And I am now cooking, thanks!!

Sent from my nonsensikal froyo
[Android] wikywwj:
Really appreciate your work!

Edit:you've fixed converting between two kind of scripts, how about generating script? i mean start with no scripts at all,also fixed?
[Android] dsixda:
Fixed what? It has always generated an update-script automatically if none are found.
[Android] wikywwj:
lol.....i've told you exactly that generated update-script will cause "HTC USB MODEM" missing.

see above,there's a link i post,someone else has that issue too.

PS:install roms with kitchen generated update-script,it will display "deleting files",maybe it deleted something which related to "HTC USB MODEM"
[Android] dsixda:
What do you mean the modem is missing and why do you keep enclosing it in quotes? Does an error pop up on the screen with this name? I don't understand your English.

Those are symbolic links being deleted... Post an update script that doesn't work, I don't want to hunt around and waste time looking at different links.
[Android] HeyItsLou:
Admitidley this is the first time I've used any type of Rom kitchen so I may very well be doing something wrong. I'm on a mac have the Rom kitchen set up exactly the way the instructions have listed. I've imported my Rom into the latest kitchen .88. I add superuser, busybox, zipalign, deodex,/data/app then I put the Rom together sign it and try to flash. I'm then greeted with a long list of "deleting files" installation aborted E: error on various lines sometimes 2,36,40. I've seen some posts saying this is due to the updater script what am I doing wrong???

Thanks in advance for the help.
[Android] wikywwj:
:(....i've told you the situation of that issue at my first reply here:

"HTC USB MODEM" means the device in PC when you set usb connect method to Mobile Broadband Connect.

Sorry for my poor english to get you understood.
[Android] dsixda:
Dude.. I keep telling you to post your update-script.
[Android] dsixda:
Please be specific and mention exact error messages and quote the update-script file. You know that I can't help with vague descriptions and line numbers. Thanks.
[Android] wikywwj:
i know..i've deleted mine,i use updater-script instead.

you can check similar update-scripts in these two roms,as i told,their roms have same problem:

rmk40's :h ttp://xdaforums.com/showthread.php?t=765447

wakeboard143's:h ttp://xdaforums.com/showthread.php?t=766223

EDIT:I recreate a rom with kitchen,check it out.
[Android] dsixda:
I don't have the time right now to open up ROMs, as it's 2am here and i have work next day. These guys may have screwed up themselves, I'm not going to debug their ROMs if it is not a kitchen issue.

So was this update-script of yours generated from a shipped ROM?? If you generated it from an existing cooked ROM, then that's not the right way to do it. There are a lot of differences between this one and the updater-script you posted before. The most important is the run_program stuff.
[Android] wikywwj:
yes,it's from a shipped rom.

the updater-script i post before is almost the same except the part of "data/app".
[Android] dsixda:
Huh? It's not even close to being the same, I just told you that.

Run the 'updater-script to update-script' converter function and then compare with your existing update-script. Many differences.
[Android] RyanLee:
If I want to drop the latest wimax.img into my ROM, do I put it in the same place as the boot.img and radio.img files? I don't use 4G but hey, if I'm gonna do it...

Also, would it be possible in the Add root permissions and Add BusyBox items to overwrite the current files or give the choice to? If your working folder is already rooted with an older version, then it's all manual. Not a hassle, so if you don't wanna address that it's cool.

As a side note that question, does su in the xbin folder need to match what's in bin, or is that a symlink? I notice when I add root permission the xbin version isn't updated.

Thanks a ton for your efforts.
[Android] dorkboy69:
can't extract cellcom rom

I am trying to extract my Cellcom rom in the kitchen and it keeps giving me there is no Meta-INF folder- should I make one. I hit yes and then it says setup failed. How can I get my rom to work in the kitchen?

Tried to extract in windows and it is an update file and just wants to run the update.

How can I get the rom that is not an update file?

this is copied from the kitchen and it does the same thing whether I hit yes or no.

No META-INF folder found under working folder!

Did not find an update-script. Shall I create one (y/n)? (default: y):

Adding an update-script ...

scripts/fix_update_script: line 16: cd: system: No such file or directory

Looking for symbolic links under /system/bin ...

find: `bin': No such file or directory

None found

grep: ../META-INF/com/google/android/update-script: No such file or directory

Adding a default set of symlinks to update-script ...

cp: cannot stat `../../tools/update_files/default_symlinks': No such file or directory

sed: can't read ../META-INF/com/google/android/update-script: No such file or directory

rm: cannot remove `default_symlinks': No such file or directory

Can't open META-INF/com/google/android/update-script: No such file or directory.

Can't open META-INF/com/google/android/update-script: No such file or directory.

Can't open META-INF/com/google/android/update-script: No such file or directory.

Can't open META-INF/com/google/android/update-script: No such file or directory.

Can't open META-INF/com/google/android/update-script: No such file or directory.

Can't open META-INF/com/google/android/update-script: No such file or directory.

Can't open META-INF/com/google/android/update-script: No such file or directory.

scripts/fix_update_script: line 102: scripts/fix_update_script_blanks: No such file or directory

Contents of META-INF/com/google/android:

total 4

-rw-r--r-- 1 curt curt 1067 2010-08-31 22:19 update-script

Listing of WORKING_083110_221834:

total 8

drwxr-xr-x 2 curt curt 4096 2010-07-01 11:52 ADR6250_2-1_MR_Cellcom

drwxr-xr-x 3 curt curt 4096 2010-08-31 22:18 META-INF

Error: Setup failed

Press Enter to continue
[Android] HeyItsLou:
get this message when I try and convert updateer script to update script to flash properly......sed: -e: No such file or directory....any thoughts
[Android] HeyItsLou:
I can't get this friggin Rom to flash I checked the Meta-INF folder for my update-script and this is what I found....View attachment 392688
[Android] dsixda:
I have no idea what wimax.img is or what it does. If it's a renamed radio.img then rename it back to radio.img.

You could just remove the existing superuser.apk + su and busybox. From your working folder.

If there is one already in the xbin folder then it gets moved to the bin folder so that it's consistent with the case when there is no su present (it gets created in bin folder). What do you mean it's not updated?
[Android] dsixda:
Once again, you have to be more specific and give me links. You can't assume that I know what a cellcom ROM is.

I'll say it again: READ THE FAQ please.

Are you even using a proper ROM or do you know what you're doing? It doesn't even have a system folder!
[Android] dsixda:
I haven't seen any problem like this, but please be specific and post the exact output you see on your screen and at what point. Also I need to know if you're using Mac, Cygwin, Ubuntu, etc....??
[Android] HeyItsLou:
everything in the kitchen works great when I go to build the Rom from the working folder then flash something is happening with the update-script and it's not flashing the rom I think it has to do with converting it from the updater-script.

EDIT: Mac - I posted a screen shot above of what's in my Meta-INF folder
[Android] dsixda:
You haven't answered my question.. are you using Cygwin, Mac, or Ubuntu?

Judging from the screenshot you are either using a Mac theme on your Windows box or using Mac OS X. In the latter case, make sure you read the FAQ on how to install sed for the kitchen on Macs.
[Android] HeyItsLou:
installed sed-4.2.1-0 I'm using the Java that is pre-installed in OSX should I be using something different?
[Android] dsixda:
Hmm, I thought this version was the GNU version of sed, not the crippled FreeBSD version that ships wih Mac OS by default. Did you actually install it or just download it? I haven't tried it myself since I don't have a Mac.

1) Does the sed-4.2.1-0 support the "-e" option when you type "sed --help"?

2) What does it show when you type "sed --version"

There is another version of GNU sed if you install it with the "Fink" tool. You may want to try this if the above doesn't give the expected output --

From Google:

If the the 'build ROM' routine is successful in creating a signed_xxxx.zip file (ie. without errors) then your version of Java is fine. Why are you asking?
[Android] dsixda:
I am currently uploading a new version of the kitchen (0.89) to address some of the issues encountered in the past few hours. Please read the Release Notes in post #2 for more info.
[Android] heliotropeUCSD:
With the new version, the sed-check fails at onset but the rom is successfully built. Is there something funny or is that okay? I'm running OSX with the Rudix download of sed.
[Android] dsixda:
1) What is shown when you type "sed --version"?

2) If you type "sed --help" does it have help for the "-e" parameter?

3) Did you run any of the scripts in the kitchen that involve "sed -e"?
[Android] Noonski:
Still angry at you for getting a N1 instead of a Desire.

But I must forgive you since your doing a tremendous job here.

Yes I'm back and just needed to say hello to the brother from Canada.

Rock And Roll.

PS: No i'm not going to install a Linux VM just to play around with your Kitchen, I'll do it the lazy, unsigned and dirtee way.
[Android] heliotropeUCSD:
sed version info

In terminal, sed --version returns illegal option.

In terminal, man sed returns

-e command

Append the editing commands specified by the command argument to

the list of commands.

In terminal, /usr/local/bin/sed --version returns GNU version 4.2.1.

So, it looks like I have the "right" version in /usr/local/bin, but that the "wrong" option does have -e as a command.

I'm new to this, so I don't know if I used a -e command. Do I just need to copy or symlink sed to the .dmg where Kitchen is stored?
[Android] TMartin:
dsixda,

v0.89 is amazing!!!! The script converter is so much better. Thanks for the great revision.
[Android] dsixda:
Or just use Cygwin on a PC .... 5 minutes to install ;)

Welcome back!
[Android] dsixda:
Thanks for looking into this. So that means that 'sed' is still pointing to the old (default) version of sed, and you need to set your PATH variable to point to the new one. Arghh.. I thought it would do that automatically.

Preferably we need the GNU version of sed (the new downloaded one), because it's the same version used in Linux/Cygwin and is compatible with the various options that are required for it to work with the kitchen. The default FreeBSD version on Macs is crippled and requires many workarounds to the kitchen which I just don't have time to test and implement... it would be nightmare. Although it does support "sed -e", it doesn't handle certain characters used in search & replace the same way as the GNU version.

A good test for your GNU version would be to run the option to convert your update-script to an updater-script and then back to update-script. If it can do that successfully without errors, then we know that "sed -e" is working. We would also need to take a look at the newly converted file to ensure everything else was done right.

I don't use Macs, so I don't know exactly how a .dmg is used. Maybe one of the other Mac users can help.
[Android] dsixda:
Good to know, just don't open up the converter scripts because they are a mess. ;) I had to do a lot of patching here and there to get all of my different updater-scripts converted properly in my tests.
[Android] heliotropeUCSD:
sed

Argh is right. However, if I get no errors, I'm probably okay for the moment? I don't really know enough to solve this, but I'll see what i can do. I'd like to use the update script, but I have no prepped files to do that with.
[Android] dsixda:
I use the "sed -e" / "sed -i -e" command in a lot of places... e.g. you could try just adding the "/data/app" functionality from the Advanced Options menu and try to flash the ROM afterwards. If it flashes without errors then you are ok.

(The /data/app functionality won't change how your current ROM behaves.. you can leave the folder empty if you want. The update-script gets modified though.)

Thanks a lot.
[Android] heliotropeUCSD:
Yeah, sed -e barfs with an LONG list of no such file or directory. Can I add the /usr/local/bin path somewhere within the kitchen?
[Android] dsixda:
Yeah that sounds like a good idea. Why don't you try to add it to your .bash_profile file? NOTE: If you don't have the file, create it in your home directory (i.e. the folder you started at when starting a terminal session)

e.g. Add this to the *end* of ~/.bash_profile, at the front of the $PATH variable, as shown below:

export PATH=/usr/local/bin:$PATH

Then, either restart your terminal session or type "source .bash_profile" to load up the new path.
[Android] heliotropeUCSD:
Gooooood call. Loads without error, runs the update script biznass, good call. What a lovely set of scripts, thank you. Now that it works I just need to learn how to use it.
[Android] RyanLee:
It's the 4G radio update for the EVO. Disregard.

That's what I'm doing. Again, no big deal.

I removed Superuser.apk and su from the bin folder. I then applied root permissions (working folder showed NO after removal, as expected). I checked the bin folder and the su file had the current date while the xbin su file was dated back several weeks. I just figured that one didn't need updating. I copied the version now in bin over anyways and it works fine.

Thanks for the input.
[Android] dsixda:
Awesome!

If you want to learn, just begin with the options on the first screen. As you get more familiar with creating your own custom ROMs you can move on to the Advanced options menu. Most of the stuff have commentary in the screens to help you learn.
[Android] dsixda:
Thanks for your feedback yesterday, you may have noticed that I added an "overwrite" option for the superuser files.
[Android] heliotropeUCSD:
Mac and ATK

It's worth noting that OSX tends to load files and folders with .DS_Store files, and you can recursively delete them with the following command.

find . -name '*.DS_Store' -type f -delete

Anyway, I changed a few icons and things in framework res, removed a few apps from /system/app, rezipped it, zipaligned, resigned, and flashed. Promptly got the looping white screen of death. Any suggestions?
[Android] dsixda:
At what point do you delete those DS_Store files? Ok.. that was a stupid question... I guess it's before you build the ROM.

Regarding your problem, do a logcat, as outlined in the FAQ. If your ROM was not deodexed and you changed the framework file, then you will have a problem.

Also, you can search the thread, as several people have had the same issue after modifying framework.res.
[Android] RyanLee:
Right on. Just now, I sent you money. Thanks for all your hard work.
[Android] HeyItsLou:
Ok up and running 100% finally!!! Ditched using OSX installed virtualbox using Cygwin and XP. The only thing I ran into is when I tried to deodex the framework it went through fine but when it got to the apk's it failed and said I'm missing baksmali I installed everything per this thread not sure why that happened.
[Android] dsixda:
All that deodexing stuff should work fine, I spent all of July on it ;-)

Can you paste your screen output here?
[Android] HeyItsLou:
Your hard work is much appreciated let me tell you I'm having a blast doing this I just put my first Sense Rom up for the incredible here on XDA with the help of this bad boy! Things are ok now I tried to recreate the issue again by putting another fresh untouched rom in and deodex and things are moving right along. Your support is awesome it must be frustrating working with so many people with "noob" questions you're doing a great thing so thanks again.

EDIT: Actually it failed about 22 apps in
[Android] dsixda:
At what point did it start failing? Can you show where it last passed?
[Android] mapleshadow:
Hi dsixda:

After i checked your ROM package, i got a question, hope u can help me to deal with it.

I found all the odex file with name apk and jar are gone within your ROM, i know they've been modified and i know how to do it as well, my question is i did a test , i deleted the framwork.odex in orignal ROM without touch others, replaced oringnal jar with modified one, but i cant boot the system, if i keep the framework.odex, then it can boot without problems, but i didnt see odex file in your ROM, so why it can still boot? so right now my thought is once u edit the odex file, then u need to edit all files in order to boot the system? is this what the proble is ?

Thx!
[Android] mapleshadow:
Why do I use the kitchen, and all the apk file deodexed jar, remove Samsung rom and within the app framework, import deodexed and the jar after the apk file, brush into the system can not boot?

PS: ultraISO Samsung rfs files can be opened.

apk has signed

My English is not very good, very sorry, but thank you for your contribution, thank you for your answer ~ ~
[Android] dsixda:
Yes, because framework files affect many other files.