yashsingh1/xdaforums huggingface dataset:
[Android] RyanLee:
Did you remove these versions from /system/app also? What is your advantage to putting them in /data/app anyways? It's just so they can be uninstalled later. That's the only benefit I'm aware of.
[Android] RyanLee:
Can you post a link to the ROM your trying to use, or at least it's folder structure. The contents of the zip, I mean.
[Android] mike1986.:
Yes, of course I removed the old versions from system/app. The only advantage is the one you mentioned. I placed them now to system/app and we'll see :)

EDIT:

ok, all apks that I moved back to system/app are installed correctly. But all apks from data/app are missing. It seems that I have to move everything to system/app :/
[Android] DxTania:
weirdest thing.

got the kitchen working, tried to set up working folder for an unmodified 2.2 .zip and it seemed to work but then it didn't..every option i tried to execute would leave an error, i forgot to copy them but now even after i redownlaoded the kitchen, i can't even choose option 1.

I just get: chmod: scripts/*: No such file or directory

/Volumes/kitchen/menu: line 6: scripts/init_kitchen: No such file or directory

/Volumes/kitchen/menu: line 7: scripts/check_binaries: No such file or directory

anyone know how to fix this?

help would be much appreciated :]
[Android] RyanLee:
Hey, just trying to rule everything out.

Do you have the check_data_app file in the root of your working folder? I had the problem once where that file wasn't created, even though the folder was.

Edit: I mean the output zip file after you cook.
[Android] Trident1000:
I can not get Busybox run-parts scripts to work on the LG Ally. It hangs up at boot. Any ideas?
[Android] DxTania:
yes i do have all the files, and i'm on a mac with snow leopard, and i just open the file not using ./meny but by clicking on it. it worked the first time so i don't know what's happening now
[Android] dsixda:
Arghh.. Don't do that, you had me worried unnecessarily. Follow the instructions as they're written.
[Android] dsixda:
Search the thread please, it was only mentioned yesterday. Do a logcat as well, as I instructed in the FAQ if you have hanging at boot.

If yesterday's solution works for you then let us know.
[Android] DxTania:
Sorry about that, it's just ./menu doesn't work, although now I pointed it in the right direction....which was /volumes/kitchen/menu

and still the same error

i'm pretty much a nub at most of this stuff :P
[Android] dsixda:
What do you mean it "doesn't work"? What do you see there?
[Android] dsixda:
Actually the problem with the above is that you have the busybox binary likely in two different places.. /system/bin and /system/xbin.

So in the first part above, the /system/bin/busybox does not support run-parts (and thus didn't work), whereas the version in /system/xbin/busybox (ie. the one the kitchen added) does support run-parts.
[Android] DxTania:
same as before

it throws this:

Carter:~ Tania$ /Volumes/kitchen/menu

chmod: scripts/*: No such file or directory

/Volumes/kitchen/menu: line 6: scripts/init_kitchen: No such file or directory

/Volumes/kitchen/menu: line 7: scripts/check_binaries: No such file or directory

and i know for a fact those files are there in the right folder and everything
[Android] mike1986.:
Yes, this file is in my working folder and in the cooked ROM.
[Android] dsixda:
Ok, version 0.98 is now up. This should take care of some of the busybox run-parts issues.
[Android] mike1986.:
@dsixda any idea why even some extra apk from data/app don't want to install?
[Android] dsixda:
Nope sorry.. I already replied to you. everything that I want works fine for me under /data/app..

Check your logcat again.
[Android] mike1986.:
I placed ALL apks in system/app and they were installed correctly. I really wonder where is the problem...

EDIT:

I remember that firstly I added data/app functionality and AFTER I added root. Might that be a cause?
[Android] mike1986.:
ok, no matter in which order I do things data/app functionality doesn't work. Here's the catlog from the first boot after flash.

BTW is it normal that while deodexing apks in framework I got few errors: Error while Disassembling Method Lorg... (I attached the screenshot)

And one more thing. I made a custom ROM based on stock RUU. When I had stock ROM it was rooted with Unrevoked. The strange thing now is that I removed some system apk like google talk, footprints, some ringtones etc., deodexed, zipaligned and I have about 10-15 MB less space available in ROM memory. I was sure that in fact of removing things my space will grow about 5-10 MB... Is this because of deodexing or zipaligning? 10-15 MB is a lot of space I've lost...
[Android] Noonski:
Dear Mr DsiXda.

In my stupidity in searching for answers I could not easily find the answer to my query.

Therefore I am turning to you and the wonderful users in this thread.

Everytime I flash my cooked/compiled/whatever you want to call it new Rom onto my device I get an error at line three and flashing stops (not just me, others flashing my vision of a Rom to).

If I then proceed to flash it again in CWM, it will flash correctly the second try.

I can see from the RomManager log file that it is related with the creation of the Data\App Folder:

-- Installing: SDCARD:/N.S.A.2010-09-24.UPD.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:/N.S.A.2010-09-24.UPD.zip
Opening update package...
I:Update file path: /sdcard/N.S.A.2010-09-24.UPD.zip
Installing update...
I:Trying update-binary.
I:Trying update-script.
I:Parsed META-INF/com/google/android/update-script
calling command show_progress
calling command run_program
calling command copy_dir
Copying files...
minzip: Can't create containing directory for "/data/app/placeholder": File exists
W:Command copy_dir: couldn't extract "PACKAGE:data" to "DATA:"
E:Failure at line 3:
copy_dir PACKAGE:data DATA:
Installation aborted.
Failure at line 3:
install_zip SDCARD:/N.S.A.2010-09-24.UPD.zip

How Many Pieces of Gold will it take to resolve this, and or which additional info is needed? Or maybe even better there already exists an answer, that I could not find
[Android] TMartin:
Can you upload your update-script??
[Android] Noonski:
Yes off course.

It's attached.
[Android] dsixda:
I can't see the picture because it's too small and my eyes aren't good.

Are you sure you deodexed all your framework files? Because the following error means you didn't do something right..

I/dalvikvm( 108): Zip is good, but no classes.dex inside, and no .odex file in the same directory

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

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

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

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

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

W/PackageManager( 108):	at com.android.server.ServerThread.run(SystemServer.java:144)

It says you deleted an odex file instead of deodexing it.
[Android] dsixda:
It looks like data/app didn't get deleted entirely. Can you change the "check_data_app" script so that it does a "rm -rf /data/app" instead of "rm -f /data/app"? Then re-build the ROM and try flashing again?
[Android] TMartin:
Alright Dsixda is on the case.
[Android] dsixda:
I think the error is that he is trying to write a file in /data/app but it already exists (ie. placeholder). This means /data/app had not been deleted previously. I think there was a problem with check_data_app (see my previous reply).
[Android] TMartin:
Ok...Thanks for the insight.
[Android] Noonski:
Will do in an hour needs Smokes now Quickly.

Thanks in Advance..

Forget smokes testing now

I changed the "check_data_app" script in tools but that didn't help, now changing the one directly in the working folder in case you meant that one.
[Android] mike1986.:
I haven't touched anything in framework folder. Nothing was deleted for sure. Here's the bigger screenshot:

Uploaded with ImageShack.us

And I have less ROM space because of deodexing? About 10-15MB. Deodexing is only for modifications or it speeds up the system also?
[Android] dsixda:
So did you deodex all of the files or not? If you had any left over then you are not supposed to flash it. I think I already mentioned that warning in the script.

You said you didn't deodex the framework folder?? What are you trying to do then??

Don't know about your other question. I'm not really the expert, I just write scripts ;)
[Android] Noonski:
I atteched the Check_Data script that get's added into the rom in the end.

It was still a no go :confused:

Is the fi supposed to come after this

(and or what does it stand for, learning as we go along)

Found it fi actually is a real part of the whole if thing in unix and such :D

It's al a bit different, but luckily strangely familiar.
[Android] dsixda:
Or replace the call to check_data_app with: delete DATA:app
[Android] dsixda:
Looks fine to me..

Anyways going to work now.. I'm late :P
[Android] mike1986.:
Yes, I deodexed all files (system and framework) but I didn't delete anything manually. The screenshot is from deodexing process. At the end it is saying that all files were deodexed but I was worrying about those errors while deodexing.
[Android] Noonski:
**** you just forced to look into update scripts with Notepad++ and find out that it's not that scary out there in the woods.

Thanks mate, I'll play around some more myself, just seen some stuff I'd like to experiment with now :(
[Android] dsixda:
If it gives an error while deodexing, it implements a "brute force" method afterwards (ie. testing with every single JAR file in the /system/framework folder as a possible class file to go with the odex file in question), which usually results in it being deodexed successfully. If you don't see any odex files left over then you should be fine.

Anyways I'm very busy at work now, I think I will take a break from this never-ending process. Not a very healthy thing staying up late working on it, waking up late, etc., re-explaining the same thing over and over, telling people to read the FAQ again and again, getting frustrated at people, banning people LOL Wish I could just put something out and walk away from it ;)

I don't know why I NEVER have problems on my Nexus One and with Windows 7 64-bit running Cygwin, but some of you can't even get the kitchen started. Anyways if you guys ever find a problem and manage to fix it then let me know so that I am not left scratching my head for hours. Thanks :D
[Android] dsixda:
Why are you releasing ROMs still, don't you know your life ends there. ;) Or just stay unmarried, unlike me.
[Android] Noonski:
It's Managable, and as far as I'm concerned it's almost finished.

Hey I need to know at least something about this whole new Android Thing I've been hearing bout lately.

Haha, Let's just say I'm working on the whole unmarried thing.
[Android] Android001:
When i load up the kitchen in the terminal (im on ubuntu 10.10) and select the first option to setup the working folder i get an error saying:

Creating working folder WORKING_092810_175507 ...

Copying update-cm-6.0.0-Heroc-signed.zip to WORKING_092810_175507 ...

Extracting ROM ...

[update-cm-6.0.0-Heroc-signed.zip]

End-of-central-directory signature not found. Either this file is not

a zipfile, or it constitutes one disk of a multi-part archive. In the

latter case the central directory and zipfile comment will be found on

the last disk(s) of this archive.

unzip: cannot find zipfile directory in one of update-cm-6.0.0-Heroc-signed.zip or

update-cm-6.0.0-Heroc-signed.zip.zip, and cannot find update-cm-6.0.0-Heroc-signed.zip.ZIP, period.

Error extracting ROM

Hope you can help, this is a really cool tool and would like to actually be able to use it!
[Android] mike1986.:
Thanks for the answer.

I found out that the reason why I had 10-15 MB ROM memory less after cooking custom ROM was deodexing. Maybe it was even more - 20-30 MB. I think it's worth mentioning in the FAQ or instruction. If someone don't need to install themes or other modifications then it's better not to deodex.

I know I have my part in frustrating you with my questions ;) Well... I'm just learning things, like everybody does at the beginning. You decided to create such a grate tool so now you have to take the consequences ;) I understand your pain because I used to be pretty advanced Windows Mobile ROMs developer and I also had to repeat things hundreds times but this is how it works. We think that so many things are so obvious and clear but in fact the aren't.

Anyway thank you for your patient and hard work! :)
[Android] shinobi_uk:
Thanks for the kitchen

Just wanted to thank you for this kitchen, i use it with my Desire, and have found it successful every time :)

Will donate after payday.
[Android] Noonski:
Just did another run.

I made the simple edit to disable the adding of the data\app folder script

by changing the fix_pre_build script

if [ "$grep_cmd" != "1" ]

:p

Seems to be flashing correctly ATM

This might be something related to my specific source.

(And now I'm having another Flashing issue unrelated to kitchen, hopefully I have a full confirm for my situation in an hour)

Yup it's fixed now for me.

Just take a break, eventually you'll find users helping each other in the end.

Or post a Job Vacancy, looking for a group to continue working on this.
[Android] Trident1000:
I had already searched the thread and tried the posted method before even posting..

I also ran a LogCat but it doesn't print anything.

Well, this didn't help it either..

So what now?

It boots if I remove the following from my init.rc:

on property:cm.filesystem.ready=1

No clue if it will actually run scripts or not though..
[Android] dsixda:
Yeah, if you replace the call to check_data_app with just the usual "delete DATA:app" then it may work.

However, if a user has apps2sd enabled on their device, with /data/app actually being a *symbolic link* to the ext partition instead of a folder, then the "delete DATA:app" operation may cause an error during flashing. This was the reason behind adding the check_data_app script, as it fixed that particular issue.
[Android] kendong2:
that is because the script was taken from the g1 and has not been modified until mcr3.2. i discovered that stuff a few days ago in mcr3.1 and was about to inform paul about this, then i looked at 3.2 and saw he cleaned it already.

i would not sign that. there is tons of information out there, you just need to find the right parts. the android documentation is really good, you might be overwhelmed because you are confusing what you don't know about linux with what you don't know about android. you have to learn TWO new worlds, not only one...
[Android] TheAshMan:
Ah, I've only had access to 3.1 so that explains that then...

You're probably right - but I would have though stuff like auto-enabling a2sd in a ROM would be easily available information - like you say I'm probably looking in the wrong places but I struggled to find anything clear on how I'd go about doing it...

I'm happy to learn though and prefer to solve my own problems just wouldn't say no to a few pointers every now and then ;)
[Android] dsixda:
Thanks! I could probably try it myself when I get home, with a spare SD card, but I'll be coming home really late from work.

This is a learning experience for me as well. But I'm glad it's helping others too.
[Android] dsixda:
Anyone had a chance to try out the apps2sd which was modified in this version: ?

http://xdaforums.com/showpost.php?p=5711034&postcount=199
[Android] maliiina:
I have cooked 2.1 rom but apps2sd not working
[Android] dsixda:
Which version did you use? 0.13 or 0.14?
[Android] maliiina:
0.14

interesting that I wanted to manually incorporated but the console showed that in general there is no apps2sd
[Android] dsixda:
What do you mean that you wanted to manually incorporate it? The script copies the a2sd to your system/bin and then writes to the init.rc file - is that what you did?
[Android] an0therus3r:
I can build a ROM but imo it isn't that easy.

The fun off cooking is adding and removing apps/themes and other stuff and therefore some or at least basic Linux knowledge would be necessary or am i wrong?

I’m thinking about underlying relations that some apps or widgets have for example.
[Android] dsixda:
You do need to have some sort of UNIX/Linux command knowledge in order to do regular file management routines (copy, delete, change directory, etc.), but that's all, really. All the Android tools (cooking and development) rely on Linux. All the cooking tools are just scripts, so you just use the command-line to call them.
[Android] dsixda:
Ok I'm putting 0.14 on the first page, so I hope to get some more feedback on the Apps2SD (it should be ok now), but 0.13 will still be there.
[Android] TheAshMan:
I've been really busy past few days, but finally got a chance to cook another ROM from fresh. Basically, a2sd does work!

This time I managed to get everything working using a stock ROM to start with. The main issue I had was that I would end up with a bootloop until I manually created the system/sd/ folder using adb shell.

It's been quite good learning all this, I also got the teknologist kernel working, custom bootscreens and the other common tweaks (it's not hard but for a learner it was still something to be proud of when it worked!)
[Android] dsixda:
Cool, thanks for the feedback! Do you mean that we need the system/sd folder created for the kitchen's apps2sd script to actually work?
[Android] TheAshMan:
I'm pretty sure it's needed. I was stuck with a bootloop til I ran:

adb remount
adb shell mkdir system/sd
adb shell reboot

After I ran that the phone booted up with my test SD card. I then tried with my working SD card too and all the apps from the card loaded up fine.

Until then my logcat results would show a crash due to the ConnectivityThread (I can get the actual error after work). I can have a look later on to see how the other ROMs handle the sd folder creation.
[Android] kendong2:
you need a mount point for the ext partition, so yes, it needs to be created. how you do this is your choice, i'd suggest to add it to the a2sd script.
[Android] maliiina:
under installed ubuntu i have

with setup folder on 0.13 and 0.14
[Android] dsixda:
Yes, like I said in the script - don't worry about it.
[Android] maliiina:
but if I build rom from android 2.1 I have signed file [ 50 mb] and error in flashing
[Android] dsixda:
Then what is the error in flashing? I don't know how well this kitchen will run from AOSP 2.1 branch, it's mainly designed for cooking with a real shipped ROM.
[Android] dsixda:
Thanks a lot. I put a "mkdir system/sd" to the scripts/apps2sd file.
[Android] dsixda:
I don't know man.. I really cannot solve everything, I'm just a scripts guy using methods that are supposed to work.. not an Android expert. Maybe someone else can help you. You shouldn't be removing stuff from init.rc if you don't know what it does.
[Android] Trident1000:
The line that I provided above was something that was added by the kitchen.. do you know what it does?
[Android] dsixda:
Well there is a problem with the zip file you downloaded, so there's really nothing i can do about it. Try re-downloading or try some other rom.
[Android] dsixda:
Why don't you use Google -

http://www.google.ca/search?q=on+pr...&aq=t&client=firefox-a&rlz=1R1GGLL_en___CA376

http://208.100.42.21/showpost.php?p=7230970&postcount=85
[Android] Noonski:
In my Case A2SD was already set up correctly.

I Checked and it's still working. Like I Said this must be pretty specific to my Case only.
[Android] TMartin:
Hey dsixda,

I was wondering if you could help me out with a kernel in a format I'm not used to. It contains a updater-script but looks like when it is converted to update-script, there are a few things left out. Here is a link. Please do this when you have free time, not something to look at when your busy at work or spending time with you family. Just something I'd like to be able to learn. Thanks for any help.
[Android] hateznemigaz:
vodafone 845

hey dsixda!

thank you for your tool! as hungarians say: "köszi!" :)

it was quite hard but finally worked with my device :cool:

there is the result: lightningred845
[Android] Noonski:
So is it really this easy to adjust you rom update not to delete any custom Bootscreens users add?

Remove

delete DATA:local

From Update Script

And add in:

symlink /data/local/android_audio.mp3 SYSTEM:customize/resource/android_audio.mp3

If so, why ain't other cooks making Users life easier this way.

And is there a particular place/order where permissions or symlinks are set in the update script?
[Android] dsixda:
Cool, thanks! Also known as Huawei Joy, correct?
[Android] dsixda:
The updater-script here is using the /tmp (TMP:) partition but unfortunately I've never had luck flashing a ROM using TMP: in an update-script. :(
[Android] TMartin:
I'm not great with updater-script at all yet....if i convert my update-script to updater-script with your kitchen, is there anyway for me to check it before I flash??? I know I can look at it but I won't know what will cause issues, etc?? Thanks for the prompt response dsixda.
[Android] mike1986.:
How can I put new busybox (1.17.2) into the kitchen?

Edit:

Ok, I downloaded some other version, for Linux probably. Now I have correct one with just one file "busybox" which is suppose to be 1.17.2 but the question is: if it's not in the kitchen already it means that it's not stable and no reason to update it? And secondly the 1.17.2 (1042 KB) file is much smaller then 1.17.1 (1824 KB). So what decision should be?
[Android] sparkienl:
update kitchen files/scripts

Nice work dsixda I like it,

I,m a noob in linux, but when I do an update in your kitchen, I get the complete package what I must unzip and put in a old/new folder.

Is it possible to get only the updated files/scripts and put it into the existing kitchen and by a major update to get the whole package.

This will save you a lot of time work because we have to DL and unzip alltogether.

sparkienl:D
[Android] Noonski:
@DsiXda

You can add the following to the shof_rom_info script:

In sense Roms HTC adds WifiRouter for wireless tethering.

Hmm SparkiNL sounds familiar, where have I seen him before?

What's up, how's it feel being an Android Noob (just like me)
[Android] dsixda:
Isn't it easy enough for you to unzip? :D

If you just want the latest files, then that's too problematic for me, and plus sometimes certain script files get removed or renamed, etc. Also if you have an old version like 0.60, then how is the script to determine which files are new at version 0.98, as compared to someone who is at another old version like 0.80?

If you just want the entire file unzipped, well, it's the same reason as above.. certain script files get removed or renamed so you'll have the wrong files remaining. And then you would be trying to overwrite the current script being run (scripts/about and menu), which isn't possible in Cygwin.
[Android] dsixda:
It's stable enough already, isn't it? Do you guys have problems using Titanium Backup with it?

You guys really want me to update every single version of busybox whenever it comes out? I'll be here till I'm 80 years old :D
[Android] mike1986.:
Dude nobody said you have to do it every time new busybox is out. But why not to update it when releasing new kitchen version with other fixes or updates (like the one with wireless tethering suggested by Noonski). You are the developer, I just reported that new version is out.