yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
Hi Ryan, the file you mentioned gets added when you build the ROM. Also notice that the update-script looks like a mess with all that whitespace -- this gets cleaned up when you build as well.
[Android] RyanLee:
I ended up building and flashing based on the new ROM I mentioned. All went well, but I was stuck at the Android screen for about 10 minutes. I know the update would take some time but I think that was just too much. I wiped CACHE and Dalvik again (after pulling the battery) but still no good.

I don't feel this is kitchen related because the ROM flashed properly.

Oh, with one exception. After the flash, which indicated success, I chose Reboot system now and it boots back into recovery with Deleting:CACHE (possibly Formatting:CACHE) at the bottom (using Amon-Ra 1.80). However, the navigation menu is still accessible, like it's not actually wiping.

I tried a couple of combinations, still without success.

Here's what I'm thinking and this is where I need some input.

Run a nand backup to keep my current config. I've restored this a few times between unsuccessful flashing so I know it's okay.

Flash the ROM I downloaded without using the kitchen so I have an updated, stock ROM.

From there, another backup to pull out the boot.img and system.img.

That's where I'm stuck. How would I transfer these to the kitchen and with the boot.img file being stock, how do I make it "unsecured" or does adding root permissions do that for me?

If I open the two zip files I have now, 3.26 and 3.29, the folder structure is the same as the working folder.

META-INF

system

boot.img

How would I recreate that file structure after pulling the 2 .img files from my backup?

Edit: Also, overwriting root permissions (to ensure the latest ChaidsDD) also wiped the xbin copy of su and failed flashing (set_perm 0 0 04755 SYSTEM:xbin/su - File not found). Copying the bin version flashed but stuck me at the Android screen. Not overwriting and using what came with the ROM (it's rooted) gave me the same error. Just a heads up that I'm still losing /xbin/su as I was before.

Edit #2: Think I figured out the boot.img part. I'll test and get back to you.

Thanks again Daniel.
[Android] dsixda:
Try a logcat to see why it is stuck.

Why don't you use the original stock ROM rather than the Nandroid? Nandroid is not as reliable as having the original, which already contains the update-script (if it's in update.zip formt). If you're trying to create a ROM with a Nandroid then the kitchen has to create an update-script and tries to add the symbolic links and stuff to it.

Root does it

For some reason your update-script has this set_perm xbin/su line, which the kitchen was supposed to remove when you overwrote your root. It was supposed to replace it with the set_perm for SYSTEM:bin/su. The latest version of the kitchen should've handled this.
[Android] dsixda:
Did you manage to resolve this issue? Arggh.. I'm running into this problem too on my N1. Geez

EDIT: Ok nevermind, I have fixed it. Looks like the DarkTremor files had an error when he released the package... one of the files are named wrong.
[Android] RyanLee:
For whatever reason, my update-script doesn't remove the xbin line. I have them both. I also have the latest kitchen version.

Without choosing the overwrite option, my xbin su is not removed.

So here's what I've done since the last post. Thanks for reading all my nonsense, but I did end up trying the ROM I downloaded.

I used the ROM and it was added to my working folder, signed, zipaligned, built - WORKED

Added wireless tether, signed, zipaligned, built - WORKED

Added Astro, MobileDefense and the Sprint_VVM update to /system/app

Removed the following from /system/app

FAIL

The weird thing is, these are the exact files I added/removed from 3.26 with no errors at all.

Now I'm looking at the Android boot screen. It flashes every 30 seconds or so but goes no further.

I don't know if it makes a difference, but I'm running XP Pro with Cygwin.
[Android] dsixda:
Hi guys,

0.96 has been uploaded. More bug fixes as usual.
[Android] robocik:
Hehe, thanks for all your work man :)
[Android] dsixda:
The Darktremor developer has just told me on Twitter that the Apps2sd bug was never reported to him so he didn't notice it. I'm surprised it was never mentioned in his thread for all these days.
[Android] Alex-V:
you are very fast with updates....Thanks for your wonderfull kitchen :)

I buld my Desire roms with your kitchen (see signature) :)

you have a little beer from me :)

with kind regards..Alex
[Android] robocik:
hehe yes that is strange :/

I has reported the dalvik2cache issue in sense roms... sent him my working script and he fixed it now :) so this issue should be gone now hehe

i am gonna try it in the desireHD rom now...

PS. and you are still releasing a new version every day hehe instead of resting ;)

but i know how it is, when you once started, it is hard to stop :)

cheers mate.
[Android] -Mr. X-:
Any way we could get the update script to symlink to busybox instead of tool box if we choose to add busybox?
[Android] Alex-V:
I hope you mean this:

The thread:

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

the solution:

http://xdaforums.com/showpost.php?p=8144292&postcount=114

with kind regards..Alex
[Android] dsixda:
No, I mean the script dtinstall.launch was calling system/bin/dtinstall.sh (which doesn't exist) instead of system/bin/dtinstall.

I have now updated the Release Note description to make it more clear.
[Android] RyanLee:
I've gotten mine to work as I need

Added 3.29 zip to my working folder

Did NOT update root permissions (even with .96, overwriting gave me the xbin error)

Added /data/app

Added/removed the same programs listed in my earlier post

Did NOT sign my APKs <-- I think this it what got me

Zipaligned

Built

Flashed

WIN!

For informational purposes, the only time I touched the update-script was to post it, as is, here for you.

Thanks Daniel.
[Android] dsixda:
Hey OMJ! I was going to message you last week about changing the Evo's Froyo ROM build name in my kitchen, but I guess it works now.

Hmm.. it's hard to tell from first look. Did you try a logcat?

Also you have a set_perm for both /bin/su and xbin/su (instead of symlink to one of them), although that shouldn't be an issue.
[Android] dsixda:
Hehe.. I get in trouble from my wife for spending too much time on it ;) But believe me, I am striving to spend less time ;) However, I am a perfectionist and it irritates me if I release something publicly with bugs that doesn't get fixed immediately.
[Android] dsixda:
There are startup scripts that rely on the standard /system/bin toolset binaries, so it'd be a bit messy to take care of. It's good to have them around. You could try removing the 'symlink toolset' lines in the update-script and see if that works for your use.

The default PATH on your device usually points to /system/bin followed by /system/xbin, so the busybox files would take over if the equivalent binary in system/bin is missing.
[Android] dsixda:
Hey man, could you send me a link to that ROM, I could check it out this weekend to see if there is an issue w/ the kitchen.
[Android] -Mr. X-:
the only reason i ask is because doing s-off testing with team unrevoked. not having busybox symlinked caused the flashing prosses to fail. this was fixed by them so if its not symlinked it can work around that. But i just figured using busy box instead of toolbox would be better.
[Android] dsixda:
BTW, on shipped ROMs I avoided adding the dozens of lines of busybox symlinks to the update-script. You probably noticed that I instead added the "installbusybox" script at the root of the working folder. During first boot, this script executes the "busybox install" command to set the symlinks up automatically without requiring the update-script to do it.

So my method will create the same number of busybox symlinks and probably more (depending on the version of busybox), while at the same time cutting down on the size and complexity of the update-script.

I think some of the more experienced ROM creators do the same thing.
[Android] OMJ:
actually I've never used logcat....

I did some more testing, first I cooked another ROM w/o changing anything from last failure...got the same results, flashed fine, but no boot......then I started w/ fresh 0.96 kitchen, made all my mods w/o adding app2sd, flashed & booted fine. Added app2sd but this time I said no to busybox run-parts, this time it flashed & booted fine. :D
[Android] nfinitefx45:
I just noticed that the "sh" file is getting renamed "sh0" I am wondering why you are doing this?
[Android] dsixda:
When Bash becomes the standard shell, it takes over as 'sh'. The old shell (the original sh) gets backed up as sh0.
[Android] TMartin:
I can confirm an issue with busybox run-parts with the Evo. I don't use app2sd and using the busybox run-parts option caused a non-booter.
[Android] dsixda:
I am using busybox run-parts w/ Apps2SD on the Nexus One and it runs fine. Did you have a /system/etc/init.d folder with files inside? Can you post your init.rc and/or a logcat?
[Android] RyanLee:
Here you go.

[ROM] OTA_Supersonic_3.29.651.5 [ROOTED] [DEODEXED] [SIGNED]

I've had this same issue from since I started using the kitchen. If I choose the overwrite option (Oh, the linked ROM has 2.3.5 ChainsDD) it removes the xbin su file or symlink but does not remove the entry from update-script. Before you made the overwrite option, I was manually removing Superuser.apk and su from both bin and xbin, and replacing with the version in the tools folder.
[Android] RyanLee:
By the way, 2.3.6.1 is out.

[APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05]
[Android] dsixda:
@Ryan - I have a fix for your su issue.. I will have an updated kitchen out soon.

Thanks
[Android] RyanLee:
I'm good bro. I rebuilt my AM ROM with the new Superuser, the new EVO radio and a couple other files. Getting past the reboot issue was my problem, and honestly I think it was the sign apk files is where I got stuck.
[Android] dsixda:
No worries... version 0.97 is now up.
[Android] mike1986.:
It seems that due to some server problems last two pages of this thread are gone :) Actually I think my post was the last one so I will write it once again. I had 5 questions which were already answered by dsixda which I appreciate. And here is my answer for the answer:

1. About root: I decided to give a try to chainsDD, will see.

2. About "placeholder" and data/app - I've placed there new version of Maps.apk, Gmail.apk and install_flash_player.apk so I removed "placeholder" file, is that ok?

3, 4 and 5 about deodexing and sys/app - first I removed Gmail.apk, Gmail.odex, Maps.apk (no Maps.odex in this folder) and install_flash_player.apk, install_flash_player.odex and I placed the new versions (only apk's) in data/app (as I wrote in point above). Then I deodexed all files.

Now I have a following questions:

6. This task killer tweak - is it the same that we can find in spare parts under "Activity/Process manaement" - Normal/Aggressive?

7. What is sysro/sysrw in point nr 14 of your kitchen? Is it recommended for rooted devices?

8. After deodexing any theme can be installed or there are some demandings?

Thanks!
[Android] dsixda:
I have restored your lost post (due to xda server crash) from using Google's cache feature (thank God!)

http://webcache.googleusercontent.c...s=org.mozilla:en-GB:official&client=firefox-a

#1. ChainsDD Superuser app is way more user-friendly and informative, plus it's more recent and there are always new versions coming out (but it's quite stable). The old Superuser app was cryptic and you can easily screw it up; however if you have problems with the ChainsDD version then the old Superuser should work for you.

#2. It is good to have placeholder file because, from my experience, empty folders sometimes do not get extracted if they don't have at least one file in them. So if you are creating a /data/app or apps2sd folder (with no apps to start with), they may not be flashed to your device and thus the feature won't be enabled properly or may cause errors. So the placeholder is just a 'dummy' file to indicate the folder exists. It's an empty file anyway, it's not going to make a big deal if you have it...

#3 and 4. Yes you can update the APK file, BUT if you are updating a file with the same name under /system/app (e.g. Gmail.apk), then make sure it has no .ODEX file of the same name (Gmail.odex). If it has an odex file, then you have to de-odex the entire ROM so that all odex files are cleared. Otherwise, you will get signing issues and a ROM that may not boot if you mix APK files with APK+ODEX files.

Usually system files go under /system/app and Market files go under /data/app. The ones under /data/app can be updated through the Market or uninstalled when you no longer need them. The ones under /system/app sometimes can be updated through Market but if you need to uninstall them then you have to do it manually through the command prompt (a tedious process of unmounting, changing permissions, then deleting) or through Root Explorer.

#5. Depends what you want to do. If you want to add themes or replace system files for hacks such as "trackball wake" or battery indicators, then you need to de-odex. However, de-odexed ROMs take longer to start on the first reboot because it needs to build the Dalvik cache to make up for the missing ODEX files (subsequent boots are fine though).

Hope this helps..
[Android] dsixda:
2. Yes, of course

6. I haven't seen that one. But it's like the MinFree Manager app in the Market, which has the same parameters as in the kitchen option

7. Click on the menu option to see a description.. They are shortcuts to mount your /system folder as read-write or read-only when modifying system files. Instead of having to type a long command you just type those. I use Root Explorer so I don't bother doing these things manually

8. I don't know, I'm not a theme expert. In general, after de-odexing you should be able to change any of the JAR files under /system/framework with a new one. Themes are defined in /system/framework/framework-res.apk, I think.
[Android] marquardt1219:
cant create working folder

when i press 1 hit enter it flashes a quik line 45 file not found error.this happens no matter which option i choose.any ideas on what i did wrong or a solution to my problem??????:(:(
[Android] dsixda:
You'll need to copy and paste the text of the screen output here, including the file names that were showing in the menu. Plus indicate your operating system.
[Android] mike1986.:
@dsixda thank you for all the answers :)
[Android] marquardt1219:
screenies

View attachment 407874

View attachment 407875

View attachment 407876not quite sure what you need so i took some screenshots .im running win7 premium home 64 bit with i5 core .when i press 1 hit enter it flashes (seems to relod)the menu.when i press option 2 enter it reads ./menu: scripts/do_root: no such file or directory .this appears and goes away to fast to capture.im using the cygwin method.
[Android] mike1986.:
Sorry last question maybe not really connected with the topic... if I remove RSS.apk then I will loose functionality of News application and widget?
[Android] RyanLee:
You'll get the option 2 error because it's looking for your working folder, which hasn't been setup since option 1 errors.
[Android] RyanLee:
Newsreader.apk is the file you're asking about. I don't *think* RSS.apk will affect it.
[Android] mike1986.:
I think I made some mistake here. RSS is called News, right? Place where you can put subscription for various RSS channels.

But I was thinking about the second app that you can mix with weather informations. It is also using RSS system or just downloading the date from the internet?
[Android] marquardt1219:
@ ryanlee Any idea why I can't create a working folder?
[Android] mike1986.:
Is there any point in zipaligning apk files that are not in data/app or sys/app? I mean that I'm keeping some apk files (like AppControl, Barcode Scanner, Root Explorer etc.) on my SD card to install them easily after wipe and not to search them every time on Market. Can I zipalignin them also?
[Android] RyanLee:
You must have read my post before I edited it, like 10 seconds later. Newsreader.apk isn't the same as RSS.apk.

I probably shouldn't have answered you either way as I've dumped both of those files long ago.
[Android] RyanLee:
No, sorry. DSI is the man for things like this. I'm trying to help answer issues I've run into myself and yours isn't one of them.
[Android] vaelek:
Big problem with latest update

I was behind a few versions of the kitchen and just updated to the latest. Everything is good, except I noticed my init.d scripts were not getting executed. After looking further I saw the run-parts option. After applying that, I get to the boot image and everything hangs at

I//system/bin/busybox( 59): run-parts: applet not found

I/logwrapper( 59): /system/bin/busybox terminated by exit(1)

Unfortunately this doesn't give me much to go on.. Help!?

I've also noticed that the busybox that is setup does not work. Restoring in TB drops you right back to the boot animation. Once I use TB or Busybox from the market to re-install it it works fine.

Thanks!

ps. I tried searching but search is down :(

This is one of the only remaining issues holding up my next release, any help is greatly appreciated!

Edit:

So I ran /system/xbin/run-parts /etc/init.d from adb shell and it continued booting. I noticed the update-script does not have a symlink line for run-parts this time around. But xbin/run-parts is a symlink to busybox :confused:

Edit:

Solved it. The kitchen puts this into init.rc

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

I had to change it to

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

and it no longer hung on boot
[Android] dsixda:
I have no idea either.
[Android] dsixda:
The busybox symlinks are created by the script "installbusybox" found at the base of your working folder (if you used this kitchen to add busybox). That's why you don't see it in the update-script.

The symlink to busybox is fine. Normally when you run a symlink created by busybox, you would type "busybox <symlink>", e.g. busybox chmod, busybox run-parts, etc.

That's strange, it worked for me. Why is your busybox binary under /system/bin instead of /system/xbin?

Also, did you make sure you had the allow-execute permission set on the init.d scripts, e.g.

set_perm_recursive 0 0 0777 0777 SYSTEM:etc/init.d

OR you could do a "set_perm 0 0 0777" on each file in init.d

That may have been the only thing missing to make the original line work. Or maybe it needed busybox and run-parts in the same folder.
[Android] vaelek:
Not sure what happened there. I did not place it manually, I installed busybox via the kitchen and that's where it put it. The main point of that was that run-parts is not a valid command in busybox, at least for me, so I had to call it directly in the init.rc instead of via busybox as it was setup by the kitchen. I guess it's possible my base rom (the new OTA odexed) had it in already, but I've also heard lots of other people having problems with busybox on the new OTA. I am able to boot, but I still have to repair it via TB or the busybox market app. Without doing so, as soon as I try to restore something I am dumped back to the boot animation, and there really isn't anything helpful in logcat when it happens.

The registered commands I have are

[, [[, arp, ash, awk, basename, bootchartd, bunzip2, bzcat, bzip2,
chgrp, chroot, cksum, cp, cut, date, df, diff, dirname, dmesg,
dos2unix, du, dumpkmap, echo, egrep, env, expr, false, fgconsole,
fgrep, find, flock, free, fuser, grep, gunzip, head, id, ifconfig,
install, ip, ipaddr, iplink, iproute, iprule, iptunnel, kbd_mode, less,
ls, md5sum, modinfo, more, mount, netstat, nohup, nslookup, pidof,
pipe_progress, ps, pscan, pwd, readlink, realpath, reset, rev, route,
sed, setconsole, setkeycodes, setlogcons, showkey, sleep, smemcap,
sort, start-stop-daemon, stat, sum, tail, tar, tee, test, time, top,
touch, tr, traceroute, true, tty, umount, uname, unix2dos, unxz, unzip,
uptime, usleep, vi, wc, wget, which, whoami, xz, xzcat, zcat

I was able to get it working at least. And hey, I know more now than I would have had the error not occurred :cool:

Thanks for the response!
[Android] mike1986.:
Ok, thank you! BTW anyone to say something about my idea of zipaligning all apk's? Few posts before... :)
[Android] mike1986.:
I have a problem. All apk's that I placed to data/app were not installed after flashing ROM :(
[Android] marquardt1219:
Ill try another version.after unistalling and re-installing this one really wish I could use this.
[Android] dsixda:
Actually the script puts busybox under /system/xbin:

echo "Adding /system/xbin/busybox"
cp ../tools/busybox_files/busybox system/xbin/

So you must have used a ROM that had it under /system/bin earlier.

But nonetheless, I'm puzzled why it would not work with run-parts.

Are those commands under /system/bin? The ones under /system/xbin are normally the busybox ones.
[Android] mike1986.:
@dsixda can you give me a hint what to do to have apk files from data/app installed after flashing ROM just like apk's from sys/app?
[Android] dsixda:
There is no hint required, when you choose the kitchen option for "data/app functionality", then all u need to do is copy the APKs to data/app. It is explained there clearly folks.. nothing extra is required.

I think you are thinking too hard and making things complicated for yourself and hence running into these issues. Start with a simple stock ROM as a base and add /data/app functionality to it. Don't do all that zipaligning/signing/etc. stuff if you don't know what it does. ROMs will work fine without it.

If it still doesn't work then let me know and post your update-script.
[Android] tenzomonk:
not sure where "set_perm_recursive 1000 1000 0771 0644 DATA:app" came from... i've always used "set_perm 1000 1000 0771 DATA:app" with data/app enabled.

EDIT: sorry, guess "1000 1000 0771 0644" is the default in the kitchen :)

also, have always had DATA copied after SYSTEM... though i don't think should make a difference.

what apk's are you installing? the fact they don't show up seems like a permission issue... not a "signed/unsigned" apk type thing :)

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

on a side note... how would i go about setting cache2cache on default? anyone know? i "attempted" to copy the cache2sd script, with the following:

#!/system/bin/sh

/system/bin/mkdir /cache/dc

/system/bin/chmod 777 /cache/dc

/system/bin/cp /data/dalvik-cache/* /cache/dc

/system/bin/rm -rf /data/dalvik-cache

/system/bin/ln -s /cache/dc /data/dalvik-cache

echo x > /data/.dalvikcache

and while it creates, etc, just fine... i still have to manually move the cache2cache. (perhaps this is a a2sd 2.7.5.1 question). i can move along if needed :)

thanks in advance!!!
[Android] dsixda:
Hmm I have no idea.. you may want to ask tkirton in his thread, he's usually helpful in that regard. Let us know..
[Android] mike1986.:
Things like Maps.apk, Gmail.apk, Market_enabler.apk... just 6 files in data/app.
[Android] dsixda:
Yeah that sounds familiar, someone mentioned this in this thread once. You will need to search the thread for a possible answer.
[Android] dsixda:
If you do a logcat while it's booting then you should see the reason why they are not being loaded up.
[Android] mike1986.:
Is it recommended to do this log while first startup? I just wiped my device so no problem...
[Android] mike1986.:
Ok, logcat.txt attached
[Android] dsixda:
Looks like you have a permissions issue because you copied Gmail there..

I don't know how to help you further, other than to just put your gmail under /system/app then.
[Android] mike1986.:
Ok I placed Gmail.apk to the system/app and now it's working fine... but the rest is still not there ;) I think I will have to move all system apk (so install_flash_player and Maps as well) to system/app and in data/app leave only some extra apk like Market Enabler etc.

I think it's important information that might be added to the FAQ or something. System apps must be always in system/app