yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
A question was asked in this Chef forum about how to use the emulator to test images. You might find the answer there.

I don't know how to use the emulator.. it was one of the things I wanted to do when I was finally free, but at this point I can't help you with that, sorry. I'm just as much a newb as anybody else. But it is a good idea, to be able to make ROMs for the emulator one day.
[Android] theintelligent:
I/logwrapper( 62): /system/xbin/busybox terminated by exit(0)

I am using the new 2.09 as the base ROM for Desire.

Any ideas?
[Android] Jeraimee:
Am I the only one that can't seem to get the apk's in data/app actually make it into the ROM?

I've also noticed (just now) that even after using "Add /data/app functionality" "/data/app enabled" still says NO and - of course - the apps don't make it in.

Anyone have some pointers?
[Android] dsixda:
Search the thread please (mentioned here already).

Someone mentioned it a couple of days ago and then when I asked him further he didn't reply back. Unfortunately some people use this thread to post their problems but never follow up.
[Android] dsixda:
Well, when you enabled /data/app what did it say on the screen? And what does your update-script file say??
[Android] Jeraimee:
When enabling:

I threw one apk in WORKING_*/data/app when I ran this. I've attached my update-script.
[Android] dsixda:
Hmm.. your update-script is missing all references to "DATA:app". I'll take a look at it later, I'm currently working on the apps2sd question someone posted yesterday. Thanks for the info..
[Android] dsixda:
Ok, here's the fix. I also noticed the same issue with the update-script may happen if you select the option to add Custom Boot Animation. So I am including both fixes in the attachment below. Just unzip the two files to the scripts/ folder.
[Android] theintelligent:
Well i was able to move ahead but my desire is in a boot loop. Logcat attached.
[Android] theintelligent:
Sorry here is the attachment
[Android] hexskrew:
@dsi-xda - Just wanted to say thanks again for your kitchen. Rocking awesome software, and thank you for your patience in dealing with all of us :)
[Android] dsixda:
I honestly don't know, it looks like gibberish to me... Again, i'm not an expert on this kind of stuff, I just write the scripts. Also if you do a Google search for your original error you'll find several results pop up.

You also didn't say what options you used in the kitchen. Since you used a new base, then make sure you also wiped your dalvik-cache and possibly your data before flashing.

EDIT: The stuff below looks like you didn't deodex your ROM properly, or you didn't clean up your dalvik-cache before rebooting/flashing. Like I said, you need to say what options you used, I can't make assumptions based on little details.

I/PackageManager( 743): No current settings file!

W/PackageManager( 743): Exception reading jar: /system/framework/com.htc.resources.apk

W/PackageManager( 743): java.io.IOException: /system/framework/com.htc.resources.apk

W/PackageManager( 743):	at dalvik.system.DexFile.isDexOptNeeded(Native Method)

W/PackageManager( 743):	at com.android.server.PackageManagerService.<init>(PackageManagerService.java:908)

W/PackageManager( 743):	at com.android.server.PackageManagerService.main(PackageManagerService.java:686)

W/PackageManager( 743):	at com.android.server.ServerThread.run(SystemServer.java:144)
[Android] theintelligent:
Thanks for the quick reply. Anyways can you please guide how can I use darktremor a2sd to move dalvik-cache on startup?

I tried editing the init.rc file but it didn't work.
[Android] dsixda:
Have you tried my suggestion about a week ago?

The command is "a2sd cachesd" which could possibly be launched inside of a script. See how I did the installbusybox script and how it is launched from the update-script.

Instead of that command you can also set up some symbolic links (/data/dalvik-cache goes to /system/sd/dalvik-cache).

Edit: http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=6175738&postcount=14 Google is your friend ;) I'll add this as an option to the kitchen.
[Android] theintelligent:
Thanks a lot, you are great :)
[Android] BesFen:
Hi....There is an update.... Downloading it now...... :D:D:D

Thank you....
[Android] dsixda:
Update? There hasn't been one for a few days.
[Android] listyb01:
A few days? Dude why ya slackin? lol

Sent from my Nonsensikal Froyo Eris
[Android] dsixda:
Haha, expect a huge change log to make up for it ;)
[Android] BesFen:
Oh..... 1 week i didn't visit your thread. :D
[Android] Yay 4 Juggs:
just did a new build with new kitchen but getting error when launching sms..."sms network failure" not really sure as to why but it's happening now on 2 devices...here is the logcat from one of the devices...

http://pastebin.com/AKyq6YSy
[Android] dsixda:
Sorry, not much of an expert on that. It's all greek to me. The kitchen shouldn't mess around with how you use SMS unless you signed something or played with some important fie.
[Android] Yay 4 Juggs:
im thinking it might be the epst.apk...some are using older apks to try and update pri...then it gets blamed on my rom...not your fault...not mine...
[Android] padlets:
If i edit the file framework and add aother language i get boot loop...

logcat:

http://www.multiupload.com/ECY4KEDFQM
[Android] BesFen:
Downloading 0.86:D:D:D

Thanks
[Android] dsixda:
Wow, you're fast, I just put it up a minute ago!
[Android] dsixda:
If you edit a framework file you have to re-sign a bunch of files. Can't help you with that, but there are guides on XDA that will show you.

EDIT: According to your logcat, it looks like you didn't deodex correctly or didn't deodex at all (which is required before changing an APK/JAR)
[Android] padlets:
the file was already deodex.

i forget to tell the i edit only framework-res.apk file.

can you tell me what files i need tore-sign? i search for guide but didn't find anything useful.

Thaks for the help and for the new version!
[Android] Yay 4 Juggs:
yoink!!!!!
[Android] Yay 4 Juggs:
are you trying to just push an update or a whole rom? if just a rom edit your apk in it's place...then just let the kitchen sign the zip...no need to sign every file if all you're editing is the framework-res
[Android] padlets:
i make whole rom.
[Android] Yay 4 Juggs:
well then just follow the instructions i gave and you'll be golden...especially if you're only changing lang files
[Android] dsixda:
Thanks for helping him out. Let us know if it works!
[Android] Yay 4 Juggs:
hey i learned from you so im more than willing to help someone with the knowledge i got from you
[Android] padlets:
boot loop again, and the custom boot animation not working.
[Android] dsixda:
When you say "not working" what do you mean specifically?

Please show me your update-script file. Just paste it here, enclosed in

tags, or zip it up in an attachment.
[Android] firestrife23:
dsixda, a2sd failed with this kitchen. Basically i get bunches of permission denied when a2sd tried to excute busybox, seem like you've forgotten to set proper permission for busybox
[Android] dsixda:
Based on the info above, it looks fine to me. You just need those three parameters plus a /data/local folder in your kitchen. What's in your data/local?
[Android] firestrife23:
found the problem, seem like ur kitchen forgot to add the following to update-script

set_perm_recursive 0 0 0755 0777 SYSTEM:xbin
set_perm 0 0 04755 SYSTEM:xbin/busybox
[Android] dsixda:
That's already done in 'installbusybox':

cd /system/xbin
/system/bin/chmod 755 busybox

What a2sd are you using? What are you using for a base ROM?
[Android] theintelligent:
I have noticed that there is a init.d folder in /system/etc, but I suppose the scripts in it are not used.

Can you please tell that how can these scripts be used?

I know that we can add the following line in init.rc

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

disabled

oneshot

to have them working?

Is this enough? Can I invoke a2sd via this method?

Please advice.
[Android] firestrife23:
Your A2SD by Dark Tremor

I'm using OTA+July update as base for Eris, from here http://xdaforums.com/showpost.php?p=7230693&postcount=18
[Android] dsixda:
There is something about that in DarkTremor's a2sd thread, just search xda. I can't really help with these things, I'm not an expert... sorry.
[Android] padlets:
bootanimation.zip

this boot aimation run perfect on other rom's

i upload the file framework-res.apk and the language files, can you please make a framework-res.apk with the language files?

http://www.multiupload.com/8ULZL7T9W6

thanks
[Android] BlaY0:
This init.rc basically emulates Linux SysV init. That run-parts tool from busybox runs every single executable script from that directory in sequential order (you can order them by prepending their names with numbers). I would suggest that you put this directory somewhere where you can write to it. I have mine in /data/local so I can add/remove scripts. If you would like to invoke a2sd via this method it is imperative that you start this sysinit service soon enough in the init process (before some other services kick in).
[Android] dsixda:
Haha... Again, I am not an expert and don't make ROMs for people. I just write scripts, man. You expect me to do something I have no clue about? ;)

Regarding the boot animation, maybe you need to set permissions, I don't know.

Maybe someone else has an answer for your questions.
[Android] padlets:
Can you add a script to odex files?
[Android] dsixda:
Why would you want to do that? And how do you odex/un-deodex? I don't want to spend 3 weeks on it like I did with the deodexing. Unzipping the apk/jar, taking out the classes.dex and re-zipping and signing the apk/jar is going to be a disaster. Then you have to convert classes.dex into an odex file. You got a lot of money to pay me? ;) :p
[Android] juansuandi:
anyone get working bootanimation under /data/local ?

its there any symlink to the bootanimaton.zip from system/customize/resources.

im trying to add symlink from http://xdaforums.com/showthread.php?t=735008 to the updater script.

get failure on the symlink

im working on desire official ROM.

edited : this do everythings. i thinks dsixda forget to add symlink into update script.. :D

copy_dir PACKAGE:system SYSTEM:

symlink /data/local/bootanimation.zip SYSTEM:customize/resource/bootanimation.zip

thanks so much for the kitchen.. ;)
[Android] snguyen768:
I dont know why it keep saying "Enter file number" when i try to Set up working folder from ROM...please help
[Android] firestrife23:
I was able to reproduce this, when I ran option "16 - Add Apps2SD" before running option "3 - Add busybox" and this will cause your kitchen to assume busybox is already installed and will not add busybox which explain why there's missing installbusybox script. If I add busybox prior to adding Apps2SD then it'll work fine without errors.
[Android] dsixda:
Which Superuser version did you use? The ChainsDD version requires Busybox (and adds it automatically), so I always used that before adding Apps2SD.

Oh wait nevermind.. it no longer requires busybox... I had removed it. But apps2sd worked on my Nexus One.
[Android] firestrife23:
I'm using newer one.
[Android] dsixda:
Disregard my previous post. I realized the new version of Superuser didn't require busybox. But apps2sd was working for me.

Ohhh wait.. i see what's going on. The a2sd and apps2sd files under /system/bin use busybox (you can open those two files and see)...
[Android] dsixda:
Are you sure? Because there is also /system/media/bootanimation.zip in other devices. The person who told me how to implement /data/local for bootanimation.zip said it was working for him.
[Android] BlaY0:
What Desire official ROM? What are you working on? If you are working on official rom, then I suspect you know more than we do.

Firs of all, there is /system/bin/bootanimation binary which actually does run animation at boot time and you can use it via adb to test animations on running phone. Second, you can do "strings /system/bin/bootanimation" to see where does this binary look for animations and in what order. But you should probably know this...
[Android] dsixda:
For apps2sd + busybox fix, try the attachment.

Let me know if this works!
[Android] dsixda:
Cool, nice tip... I did that command on my Nexus One ROM and got near the end of the output:

/data/local/bootanimation.zip

/system/media/bootanimation.zip
[Android] dsixda:
Huh? It is supposed to say that. What is the name of the ROM you are trying to extract?
[Android] padlets:
I'm trying to install a rom that i made from nandroid, but then i install i get error in line 56:

#
# Generated by dsixda's HTC Android Kitchen
# xda-developers.com
#
show_progress 0.1 0
format SYSTEM:
delete SYSTEM:xbin/busybox
delete_recursive SYSTEM:xbin
copy_dir PACKAGE:system SYSTEM:
symlink dumpstate SYSTEM:bin/bugreport
symlink dumpstate SYSTEM:bin/dumpcrash
symlink toolbox SYSTEM:bin/cat
symlink toolbox SYSTEM:bin/chmod
symlink toolbox SYSTEM:bin/chown
symlink toolbox SYSTEM:bin/cmp
symlink toolbox SYSTEM:bin/date
symlink toolbox SYSTEM:bin/dd
symlink toolbox SYSTEM:bin/df
symlink toolbox SYSTEM:bin/dmesg
symlink toolbox SYSTEM:bin/getevent
symlink toolbox SYSTEM:bin/getprop
symlink toolbox SYSTEM:bin/hd
symlink toolbox SYSTEM:bin/id
symlink toolbox SYSTEM:bin/iftop
symlink toolbox SYSTEM:bin/insmod
symlink toolbox SYSTEM:bin/ioctl
symlink toolbox SYSTEM:bin/ionice
symlink toolbox SYSTEM:bin/kill
symlink toolbox SYSTEM:bin/ln
symlink toolbox SYSTEM:bin/log
symlink toolbox SYSTEM:bin/ls
symlink toolbox SYSTEM:bin/lsmod
symlink toolbox SYSTEM:bin/mkdir
symlink toolbox SYSTEM:bin/mount
symlink toolbox SYSTEM:bin/mv
symlink toolbox SYSTEM:bin/nandread
symlink toolbox SYSTEM:bin/netstat
symlink toolbox SYSTEM:bin/newfs_msdos
symlink toolbox SYSTEM:bin/notify
symlink toolbox SYSTEM:bin/printenv
symlink toolbox SYSTEM:bin/ps
symlink toolbox SYSTEM:bin/reboot
symlink toolbox SYSTEM:bin/renice
symlink toolbox SYSTEM:bin/rm
symlink toolbox SYSTEM:bin/rmdir
symlink toolbox SYSTEM:bin/rmmod
symlink toolbox SYSTEM:bin/schedtop
symlink toolbox SYSTEM:bin/sendevent
symlink toolbox SYSTEM:bin/setconsole
symlink toolbox SYSTEM:bin/setprop
symlink toolbox SYSTEM:bin/sh
symlink toolbox SYSTEM:bin/sleep
symlink toolbox SYSTEM:bin/smd
symlink toolbox SYSTEM:bin/start
symlink toolbox SYSTEM:bin/stop
symlink toolbox SYSTEM:bin/su ----------------> line 56
symlink toolbox SYSTEM:bin/sync
symlink toolbox SYSTEM:bin/top
symlink toolbox SYSTEM:bin/umount
symlink toolbox SYSTEM:bin/vmstat
symlink toolbox SYSTEM:bin/watchprops
symlink toolbox SYSTEM:bin/wipe
set_perm_recursive 0 0 0755 0644 SYSTEM:
set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
set_perm 0 3003 06755 SYSTEM:bin/ip
set_perm 0 3003 02755 SYSTEM:bin/netcfg
set_perm 0 3004 02755 SYSTEM:bin/ping
set_perm 0 2000 06750 SYSTEM:bin/run-as
set_perm_recursive 1002 1002 0755 0440 SYSTEM:etc/bluetooth
set_perm 0 0 0755 SYSTEM:etc/bluetooth
set_perm 1000 1000 0640 SYSTEM:etc/bluetooth/auto_pairing.conf
set_perm 3002 3002 0444 SYSTEM:etc/bluetooth/blacklist.conf
set_perm 1002 1002 0440 SYSTEM:etc/dbus.conf
set_perm 1014 2000 0550 SYSTEM:etc/dhcpcd/dhcpcd-run-hooks
set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh
set_perm 0 0 04755 SYSTEM:bin/bash
symlink /system/bin/bash SYSTEM:bin/sh
set_perm 0 0 06755 SYSTEM:bin/su
symlink /system/bin/su SYSTEM:xbin/su
set_perm 0 0 04755 SYSTEM:etc/ppp/ip-up-vpn
show_progress 0.1 10
show_progress 0.2 0
run_program PACKAGE:installbusybox
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.2 10

in my system/bin i have the file su.
[Android] dsixda:
What does it say about line 56? Please be specific.
[Android] BlaY0:
Then why are you trying to link toolbox to su if su already exsists??? Do not link toolbox to su... toolbox itself doesn't have su in it. So delete that line.
[Android] firestrife23:
seem to be working so far... by the way your script automatically used Direct Apps2SD method, I prefer Busybox Run-Parts Method. I think you should offer options of direct call, busybox or froyo... see here for more info http://xdaforums.com/showpost.php?p=7021331&postcount=4 prior to adding apps2sd.
[Android] dsixda:
Oh, so THAT's why you are having busybox issues and I am not. I already know about that link, but once you add all those other options you're opening another can of worms and making it confusing to the user. Not only that, but it will make things too complex for me to handle, because the busybox run-parts method is used for other services and not just apps2sd.

I'll leave it at that, I'm not spending any more time on it ;) I've wasted a good summer already with no real incentive but ppl asking for more and more LOL Just give me a salary.
[Android] maxrfon:
Can please someone repost/upload mkbootimg and mkbootfs for Mac os?
[Android] dsixda:
It has been posted already, please search the thread...

Otherwise make sure you have installed gcc so that the kitchen can compile it.
[Android] dsixda:
Anyone with any NON-depressing feedback on 0.86? :) A lot of effort was made for this release, yet not a single positive feedback on the requested bug fixes, etc., listed in the change log.
[Android] TMartin:
Working very well rooting, deodex'd, and add busybox to my Evo 2.2 stock Rom. Thanks for the great kitchen.

Sent from my HTC Evo 4G!
[Android] abc001:
I run the kitchen on Windows 7. Everything is ok.

But when I run it on Ubutu, it just cannot create Working folder. Can someone tell me what's wrong?
[Android] firestrife23:
The 2 different business models (free + donations, & paid) both have pros and cons. A model is chosen based on the ethics of the developer. When people pay, you tend to get a lot more flaming: "I paid for this, you must fix it yesterday!!" and so I can totally see why a lot of people develop donationware, it has no reflection on the support/advancement on the project unless this would create jobs for all of the developers and maybe all of them don't even want to do this fulltime and have you as their boss.

Other companies provide lower-grade products and get away with making a fortune so it's tricky...in the end it comes down to choosing a model that gives the developer peace of mind according to their ethics....

;)
[Android] juansuandi:
i mean i make custom rom from official release. and its bootanim is under system/customize/resources.;) so i had to add symlink to the update script to get it work. and thanks for the cool tips.
[Android] theintelligent:
Thanks, well I was able to use this method for apps2sd, but the problem is that busybox gives me errors. E.g. I have several scripts in the init.d folder, but after executing the first two, it gives me error like /system/etc/init.d/02cache : system cannot find the specified path. I have already verified the permissions, they are fine.
[Android] dsixda:
I agree with you, and I don't believe this work should be paid for. I was being sarcastic about the salary thing ;) but it really is stretching the bounds of the time that I have available, although I do enjoy sharing the knowledge.

You didn't offend me, it's the people who ask for stuff that is almost beyond my available resources, e.g. "Can you make a ROM for me", "Can you add this program that can do a million things at once", even though I had already explained how difficult it would be and that I am not keen on spending weeks again on a single feature that likely won't be used by the general user. :)
[Android] BlaY0:
Well, I took a different approach of this method. Instead of directly calling busybox and run-parts I made a shell script called sysinit:

#!/system/bin/sh

PATH=/system/bin:/system/xbin
SYSINIT_DIR=/data/local/init.d

umask 022

[ ! -d "$SYSINIT_DIR" ] && mkdir $SYSINIT_DIR

[ -d "$SYSINIT_DIR" ] && run-parts $SYSINIT_DIR

sync
setprop my.system.ready 1

...put it into /system/xbin and called it in init.rc like this:

service sysinit /system/bin/logwrapper /system/xbin/sysinit
disabled
oneshot

...and start it first thing at boot time.

Then you populate /data/local/init.d directory with your scripts which you can test and edit on-the-fly.

Begin every script with #!/system/bin/sh and define PATH variable. Order of paths is important, because you have two sets of utils doing the same thing but accepting different parameters... first come of toolbox and another of busybox. If you set PATH=/system/bin:/system/xbin then you use let say mkdir from toolbox and if you switch order of those two paths, you use mkdir from busybox. It is important also to comment everything the script is beginning to do or has already done... let say "echo Enabling a2sd..." or "echo Done..."... this is then printed while you are debugging your boot process with adb logcat. If you run those scripts in init.d manually, they are processed exactly as run-parts would do it. If you are not confident enough to run the script at boot time, do not make it executable just yet and rather try it manually like for example "sh /data/local/init.d/30newscript".

Problems most people are describing here are not problems with the kitchen itself but lack of recipes. Well kitchen itself is not everything, you have to have good recipes to make good use of kitchen otherwise there's no point of using it. So what's the point of shiny kitchen if you're a bad cook.
[Android] Yay 4 Juggs:
question re busybox and su...when creating a rom using .86 busybox and su do not get updated for some reason...still 2.1 on su and 1.15 on busybox...am i missing something?
[Android] dsixda:
Keep in mind that if you launch a script from the update-script using the "run_program" command, and it comes before "copy_dir PACKAGE:system SYSTEM:", then this line becomes "#!/sbin/sh" instead, because there is no /system/bin at that point.

Thanks for the tip
[Android] dsixda:
No problems here .. haha, I don't know how you guys get this strange errors.

When you copied the latest kitchen, did you delete all traces of the older version's folders?
[Android] Yay 4 Juggs:
indeed i did...no c&p here
[Android] theintelligent:
I will definitely try this approach tomorrow :)
[Android] theintelligent:
One thing I have noted that the problem occurred with those scripts which are supposed to run after apps2sd script. I have tried changing their sequence and they are working fine now. BTW the apps2sd script was from darktremor that is included in the kitchen.
[Android] BlaY0:
Darktremor is a bloat (my opinion). I made my own a2sd script which had exactly 60 lines. You don't need 6,5 MB of stuff just to move some files and make some symbolic links. Besides "bad" cooks make their ROMs with two or even three busybox binaries which are basically the same but eat 3 times the size they should. And then there is bash (2,5 MB)... you can also find two binaries of bash in some badly brewed ROMs.

The only problem I experienced with my a2sd script was that it kicked in before mmc block devices were available, so i put in one while loop to wait til they were available.
[Android] dsixda:
I agree with you about Apps2sd; in fact I was even thinking the same thing this morning. I wrote a small apps2sd script for my Milestone the other day, it could probably be applied the same way to other devices. I may include that as an option.

By the way, what module did you use for mounting ext3?
[Android] BlaY0:
No module. EXT3 driver is statically compiled im my kernel (HTC Legend 2.03).
[Android] firestrife23:
Hope it's not too much of asking, I'm wondering if you could add feature such as extracting boot.img to dedicated working_boot_xxx folder for instance and allow manual editing? perhap you may have better way of implicating this.
[Android] BlaY0:
Hmm, why would that be part of the kitchen? You can use any of the kitchen's script externally. Besides you can put any boot.img into the current working directory, extract it to BOOT-EXTRACTED and then move this directory elsewhere.

Android powah!
[Android] dsixda:
Already added as part of 0.86 - see the release notes.