yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
I just built a shipped ROM, and added rooting/busybox and then finally Apps2SD.

I don't mess around with the kernels, I don't know what a Hydra Kernel is.. I just have a Nexus One. ;-)

Where are you adding the Wireless Tether app when you make your ROM? Under /system/app? you may need to put it under /data/app, which is where apps get installed when you do it manually.
[Android] dawynkoop:
Hydra Kernels are for the Incredible, they allow Overclocking and add Wireless N functionality. I've tested a new rom and it doen't seem to be an issue with the kernels, it's almost like it's an issue with SuperUser, 2 out of the 3 apps I cooked into my rom that require superuser, force close and won't work. If I uninstall them reboot and then reinstall them they work just fine, I'm going to test using the alternate superuser file and see what happens. I've tried the apps in both the system/app folder and data/app folders and get the same thing.
[Android] mycomputerisjunk:
I'm seeing the same.
[Android] dawynkoop:
It looks like you can cook a rom with the Hydra Kernels built in as long as you dont include the wireless tether app, you'll just have to manually install it once your rom boots.
[Android] mycomputerisjunk:
I was able to cook in wireless tether 2.0.2 and it worked fine with Hydra.
[Android] dawynkoop:
Yeah, 2.0.2 always worked fine for me but 2.0.5 isn't working, 2.0.5 is the version that allows Acces Point tethering instead of AdHoc.
[Android] dsixda:
Found the answer -

http://androidforums.com/519235-post77.html
[Android] dawynkoop:
Nice, sounds like apps2sd makes everything a pain
[Android] dsixda:
No doubt!

But it does come in handy. Maybe I should create a script that does this error handling.
[Android] dawynkoop:
Let me know if ya get one written and I can try it out, I have a spare sd card around here i can set up to use with apps2sd or testing.
[Android] dsixda:
Ok you can try it out now :-) 0.76 is up. Thanks.

Basically the error was that if you flash an apps2sd ROM, then flash an apps2sd ROM again (without wiping). It will give an error about DATA:app.

In other words, it's trying to create data/app, but it currently exists as a symbolic link to the SD card. The fix will now delete data/app before copying a new one over.

To reproduce the problem just flash the same apps2sd ROM twice. It shouldn't happen anymore though.
[Android] mycomputerisjunk:
@dsixda

Do you know when we finish cooking the ROM and it signs it... Should we be able to use signature verification? If I enable signature verification in recovery the ROM install fails.
[Android] mycomputerisjunk:
Anyone know if a good writeup exist for customizing a ROM? Any by customizing, I mean changing the icons around, default settings etc..
[Android] dawynkoop:
Just tried it, not getting any errors. Looks like it should be ok now.
[Android] dsixda:
I never knew there was an option called 'signature verification' in recovery. You're supposed to sign a ROM when you zip it up, otherwise you won't be able to flash it.

What do you mean by the install "fails"?
[Android] dsixda:
Thanks bro.. I hope others won't run into that problem again!
[Android] mycomputerisjunk:
In clockwork recovery you can enable signature verification of ROMs. When I do that and try to install it, the error says that the verification failed.
[Android] dawynkoop:
Sounds like we shouldnt. Fortunately I didn't really worry about it since I never use apps2sd. No I'm trying to figure out the issue with the new Wireless Tether apk...this one's throwing me for a loop.
[Android] dsixda:
You should report it to the devs at their site.
[Android] dawynkoop:
I did, just playing the waiting game for a response back. Maybe I'll get lucky and figure it out first and not have to worry about it, lol.
[Android] dsixda:
I have no idea, man. If your ROM was signed in the kitchen, it would be called signedXXXXX.zip. Don't use update.zip.
[Android] homewmt:
Thanks for the great kitchen

Just wanted to say on my mac when I tried to start up the kitchen I got an error message about wget not installed or something, so I just followed this http://www.mactricksandtips.com/2008/07/installing-wget-on-your-mac-for-terminal.html and everything is fine now.
[Android] dsixda:
Excellent, thank you. I will update the FAQ.
[Android] sparksco:
Can't create update.zip

ok so I have all of this set up on Ubuntu, and everything works great until it gets to the signing part, and then says can not create update.zip. I have the latest sun java6, what am I doing wrong?

Edit: I also get a unexpected operator message but not really sure if it's a error or not
[Android] dsixda:
Post the actual output here, not the summary.
[Android] sparksco:
============================================================

HTC Android Kitchen 0.76 - by dsixda (xda-developers.com)

============================================================

1 - Set up working folder from ROM

2 - Add root permissions

3 - Add BusyBox

4 - Disable boot screen sounds

5 - Add wireless tethering

6 - Zipalign all *.apk files to optimize RAM usage

7 - Change wipe status of ROM

8 - Change name of ROM

9 - Show working folder information

0 - ADVANCED OPTIONS

99 - Build ROM from working folder

u - Update/About kitchen

x - Exit

Enter option: 99

Found working folder:

/home/sparksco/WORKING_072710_134550

total 2248

drwxr-xr-x 3 root root 4096 2010-07-27 13:46 META-INF

drwxr-xr-x 5 root root 4096 2010-07-27 13:48 data

drwxr-xr-x 12 root root 4096 2010-07-27 13:48 system

-rw-r--r-- 1 root root 2287616 2010-07-27 13:48 boot.img

[: 9: ./META-INF/com/google/android/update-script: unexpected operator

[: 103: 0: unexpected operator

[: 129: 0: unexpected operator

Making update.zip ...

update.zip created, ready for signing

Signing update.zip as signed_072710_135053.zip ...

[: 105: 0: unexpected operator

Was not able to create signed_072710_135053.zip!

Ensure you have a recent version of the Sun Java JDK

Press Enter to continue
[Android] dsixda:
Looks like a problem in scripts/fix_pre_build. I didn't see this happen to mine.

What is shown when you go to the Working folder and type "find . -name update-script"?
[Android] sparksco:
It says this:

sparksco@sparksco-laptop:~$ cd WORKING_072710_134550

sparksco@sparksco-laptop:~/WORKING_072710_134550$ find . -name update-script

./META-INF/com/google/android/update-script

sparksco@sparksco-laptop:~/WORKING_072710_134550$
[Android] dsixda:
Try this:

Go to your scripts folder, and type - dos2unix fix_pre_build ... and then: dos2unix build_rom

It's a longshot, but see if that fixes the problem. You might have a formatting issue with your files.
[Android] sparksco:
hey thanks for all your help but it says command not found. I really don't know what the problem could be, I followed the video just like on theunlockr.com:

sparksco@sparksco-laptop:~/scripts$ dos2unix fix_pre_build

dos2unix: command not found

Edit: I was just trying to modify a kernel, I'll just extract the kernel and fastboot flash it. I really hope that I can use your kitchen some day.
[Android] dsixda:
Did you download a Starter version of Ubuntu? :D How come dos2unix isn't there, it should be standard on all platforms.

Then install it with this: sudo apt-get install dos2unix

Don't give up so easily. Try the Cygwin method.. much easier!
[Android] sparksco:
oh ok thanks, that sounds like a update install command just like the one I did for eclipse. I'll try it out.

Edit:

sparksco@sparksco-laptop:~$ sudo apt-get install dos2unix

[sudo] password for sparksco:

Reading package lists... Done

Building dependency tree

Reading state information... Done

E: Couldn't find package dos2unix

sparksco@sparksco-laptop:~$

Yeah I must of downloaded the starter Ubuntu, and then upgraded to the 10.4 version. Maybe I should of stayed on the older version
[Android] BesFen:
Hi dsixsa,

App2sd in v 0.75 is not working on legend :(:(, it said, can't mount ext partition.
[Android] dsixda:
I guess that would be a problem with Darktremor's implementation, as you mentioned in his thread.

BTW do you have /data/app functionality enabled? That and apps2sd should not exist together, for obvious reasons (apps2sd uses that as a symbolic link).
[Android] BesFen:
No, i don't enable that.
[Android] dawynkoop:
Do you have all repositories enabled?

In Ubuntu System>Administration>Software Sources> under Other Software make sure both boxes are checked. I've found that this helps with installing things on Ubuntu alot.
[Android] dawynkoop:
Anyone have a guess if this will work with the new 2.2 leak ROM?
[Android] dsixda:
Huh? What are you talking about, you have at least two choices for superuser. I only touched the apps2sd part in 0.76.

Please provide a snapshot of what you see so that I understand exactly what you mean.
[Android] dsixda:
Well.. sorry, nothing I can do about it. You have to ask the developer.
[Android] andrewwai18:
0.76 kitchen on hero gsm

Sorry... been busy but back again... Updated to latest kitchen and built rom as usual. When I flash the zip file in recovery I get the following:

E:Can't chown/mod /system/xbin/a2sd
(No such file or directory)
E:Failure at line 26:
set_perm 0 0 0777 SYSTEM:xbin/a2sd

/data/app functionality not enabled as stated a few posts back.

I checked in the working folder and the contents of the zip and a2sd does exist.

Anyone getting this?
[Android] dsixda:
Google says to update the recovery menu on your Hero if you have chmod issues.
[Android] andrewwai18:
By 'update the recovery menu', do you mean update to a newer version or I need to make some change within recovery? I am already on RA-hero-v1.6.2.
[Android] dsixda:
I don't know, just Google it, I saw something about 'chmod' and 'Hero'. It's not related to the kitchen. I don't have a Hero so I can't do that work for you :-)
[Android] dsixda:
BTW Andrew, is your a2sd a file or folder? In the latter case you need to make sure it has at least one file inside it, even a blank placeholder file if there is nothing else.
[Android] andrewwai18:
I see a2sd is a file. It exists in the working directory and within the built zip. I have not made any changes within your kitchen, just to enable root, busybox, wifi tethering, bash and app2sd.

Edit: Checked in zip:/META-INF/com/google/android/META-INF/update-script. I guess it reaches line 26 which is set_perm 0 0 0777 SYSTEM:xbin/a2sd
[Android] dsixda:
Post the entire update-script here.
[Android] BesFen:
I am waiting for V0.77....:D:D:D

as your direction, I contact the developer of darktremor, I will inform you later
[Android] dsixda:
Wait a sec.. are you trying to say that you are porting an N1 ROM to the Hero?
[Android] andrewwai18:
No, I pulled the rom.zip from the stock hero 2.1 ruu. Was merely pointing out the memory capacity differences.
[Android] dsixda:
If you are flashing a Hero ROM to a Hero, why do you have to worry about storage? ;)

I don't know what your problem could be but I read about the "chmod" issue on Google with people flashing Hero 2.1. I really can't help any further.
[Android] sparksco:
Hey I just wanted to say thanks for all your help yesterday. I figured out what the problem was. I am using a newer version of Ubuntu 10.04 LTS and if works great, just works a little bit different than the older versions. Here's what I did to get everything working correctly in case you want to edit your post about how to set up your kitchen on this version.

Before I didn't change the permissions for the menu file to make it executable. This can be done very easily by going to the properties of the file and selecting the permissions tab. Maybe you already know this but I'm a bit of a noob when it comes to linux. Next I downloaded and intalled the self-extracting jre-6u21-linux-i586.bin file from the java web site and also made it executable. The execute command is the same as the older versions I believe, like ./menu, ./jre-6u21-linux-i586.bin ect. Now under applications I have a system tools option with sun java 6 console. I think the errors were because I was trying to run it as sh menu, because ./menu was not working for me until I changed the permissions.

I'm not using virtualbox anymore, I downloaded the .iso file and burned it onto a cd, and now I can dual boot with a regular size screen instead of a tiny little one.

The only thing I noticed about the kitchen is that it doesn't seem like it is compatible with the RC1 or RC2 for dream. I know they are just release candidates so I'm not expecting a whole lot from the kitchen to be able to modify these type of roms properly. I attempted to add the apps2sd, hoping that this would allow the rom to see and use the ext partition instead of the fat32 partition or whatever froyo uses. Unfortunately when I do this the rom will not boot at all past the g1 screen. Also when I create a work folder, I get the message saying that no update-script was found asking if I would like it to create one. So of course I click on yes and then after it creates it, it says that another update-script was found lol??? Kinda weird, then it ask me if I would like for it to remove the original update-script. I'm a little confused on what I should do here, if I should keep the original update-script or create a new one. Any help would be much appreciated, thanks!

Edit: Wow you come out with a new version like every day!
[Android] dsixda:
Can you edit that reply so that you include paragraphs. I can't read that.. my eyes hurt. Thanks

And why did you quote the entire first post? ;) I will remove that.
[Android] dsixda:
Ask, and you shall receive ;) ....0.77 is now up.

P.S. I don't like making this an everyday occurrence LOL ;) But it seems, everytime I have the latest version, there is always a significant issue that comes up, that I need to fix.
[Android] dsixda:
Well if you read the FAQ then you wouldn't have wasted all that time, and I wouldn't have needed to reply --- It's the first question there (ie. setting permissions for 'menu'). As I said in big bold font in Post #1, please read the FAQ when you have an issue.

Also in the FAQ under Virtual Box, I have mentioned how to make the screen size fit your monitor. ;-)

Not update-script, it's updateR-script. You are using a CyanogenMod ROM which uses an updater-script instead of an update-script. Do a search in this thread for updater-script for more info.

Again guys, I have pointed this out many many times -- just read the FAQ and save yourself lots of time when you have an issue.
[Android] sparksco:
um, ok, hopefully there will be something in there about a easier way to update the java files
[Android] sparksco:
Anyone using the newer versions of Ubuntu

Here's a easy and painless way to install java with the self-extracting file without trying to type in a bunch of commands in terminal that might or might not work:

download the self-extracting file: http://javadl.sun.com/webapps/download/AutoDL?BundleId=40907

Change permissions under file properties and make executable.

Start the installation process. Type:

./jre-6u<version>-linux-i586-rpm.bin

The license agreement is displayed. Review the agreement. Press the spacebar to display the next page. At the end, enter yes to proceed with the installation.

The End!
[Android] dsixda:
No, because people using Ubuntu 10.04+ had various problems installing Java. I had a solution proposed just like yours (downloading Java JRE and JDK from a 3rd party site), but that didn't work for everyone.

Ubuntu 9.x is the easiest way to go.. and this is after months of reading this thread.
[Android] dsixda:
I had the exact same file posted in the FAQ -- as I said, it doesn't work for everyone.
[Android] sparksco:
really, weird, worked great for me ;)
[Android] dsixda:
This kitchen cannot handle updateR-scripts, so that is a major issue. I was working on a converter routine that will convert updateR-script into an update-script, but I don't think all updateR-script routines can be translated into update-script syntax. (I had asked Cyanogen about this, but as expected, he didn't answer back)

I could add that as an experimental feature sometime later this week. It actually works with OTA updates that have the updater-script, but Cyanogen's ROMs add some other crazy stuff in the updater-script that require more effort to parse and translate.
[Android] dsixda:
Worked great for me as well, that's why I had posted those instructions ;) (and then took them down and proposed the trouble-free Ubuntu 9 route)
[Android] sparksco:
I'll just pm you sometime, time to download and check out eclipse and get it all configured
[Android] sparksco:
Understandable, we only do what we can. It seems that CM roms are very unique indeed, and I see a lot of devs struggling to make any types of modifications to his roms. Hopefully he will make them more mod friendly in the future.
[Android] antz88c:
@dsixda, since there is now an option to prevent user from enabling /data/app feature when Apps2SD is enabled, and vice-versa, if i select Enable Apps2SD, can i put my apks inside the a2sd folder? Thanks
[Android] dsixda:
Oh... I'm not sure. Were you using /data/app before to put apps in apps2sd? Then maybe I shouldn't have prevented that. I thought that because /data/app is a symbolic link in apps2sd, it won't allow that.
[Android] dsixda:
BTW I have updated the instructions for installing Cygwin. You no longer need to modify the .bash_profile file IF you had installed Java *before* installing Cygwin!
[Android] TMartin:
This may be another question for Calkulin...His new HTC Evo ROM has both apps2sd and /data/app. He is using the same apps2sd.
[Android] zach.xtr:
If it is helpfull I us a customized a2sd (still similar to tkirton last time I checked) and still have /data/app on both the roms that I produce (links below if you want to disect them) without issue... Basically I do not see this as a problem as the a2sd routine should handle copying any files included in the /data/app folder to the /system/sd (or whatever your mount point is) during the init scripts that are run with then phone boots up... Not sure if this is true for CyanogenMod but it is for all of the HTC framework a2sd I have reviewed...

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

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

Hope this helps and this tools is just wonderful
[Android] dsixda:
Beautiful, thanks for the help! :-)
[Android] dsixda:
New version 0.78 is now out.

I also included a possibly useful script for the plugins option.
[Android] andrewwai18:
Hi dsixda, just an update. Currently reverted back to 0.74 of the kitchen for testing and enabled root, busybox, apps2sd (old version) and wifi tethering, but no bash and I commented out the e2fsck in a2sd script. Installed with recovery without problems and boots ok. Actually even without the mods and with bash enabled I recall 0.74 was successful.

Here is what I have found. For the hero df will show

/system: 174080K total, 172120K used, 1960K available (block size 4096)

This does not leave much! As I am using a stock 2.1 Hero I think that I am hitting a volume limit in /system. I will try to remove some stock apks and see if this will help with newer versions of the kitchen tonight.

Could the copy_dir PACKAGE:system SYSTEM: command fail silently?

Cheers.
[Android] freddyemmer:
First of all Thanx for this amazing kitchen, are you planning to include more phone's or is it going to be HTC only? I'm asking because i trying to create a rom for the vodafone v845 but it's not realy working all that well..
[Android] dsixda:
Probably not because I don't have those phones and HTC phones are already taking up all my time.
[Android] freddyemmer:
oke.. i understand thanx anyway for this great HTC kitchen!
[Android] dsixda:
You're probably better off asking in the Hero development forum, I can't help you much... I'm not much of an expert. Sorry
[Android] firestrife23:
v76 work great until I upgraded to v78 and I get this message during flashing

E:Can't symlink /system/bin/schedtop
E:Failure at line 68:
symlink toolbox SYSTEM:bin/schedtop

Installation aborted.
[Android] dawynkoop:
Getting the same error, reverted back to .76 for now.
[Android] dsixda:
Which ROM are you guys building from?

EDIT: Nevermind, found the problem. Ouch, stupid mistake on my part. I'll fix that ASAP, sorry guys.
[Android] firestrife23:
Building from Stock Eris rom with July patch
[Android] dsixda:
Ok, fix is up (0.79) :-)
[Android] firestrife23:
awesome! working better this time :D I've been toying around your busybox, and here's another quirks I've found.

# busybox ping www.google.com
ping: bad address 'www.google.com'
# ping -c3 www.google.com
PING www.l.google.com (74.125.157.104) 56(84) bytes of data.
64 bytes from gy-in-f104.1e100.net (74.125.157.104): icmp_seq=1 ttl=51 time=188 ms
64 bytes from gy-in-f104.1e100.net (74.125.157.104): icmp_seq=2 ttl=51 time=196 ms
64 bytes from gy-in-f104.1e100.net (74.125.157.104): icmp_seq=3 ttl=51 time=205 ms

--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2010ms
rtt min/avg/max/mdev = 188.415/196.635/205.292/6.896 ms
#

by the way my phone is Verizon's HTC Eris with sense based rom. I tried adding resolv.conf to /system/etc but that doesn't seem to fix it either.

Keep up the great work, love your time saving kitchen!
[Android] dsixda:
Yeah mine doesn't resolve name addresses with busybox ping either. But works with regular ping. If you have a solution let me know. Thanks
[Android] andrewwai18:
No problem... thanks for all your help in the last week. Have learnt a lot from your kitchen already. Keep up the good work.

Edit: Good news! Working with latest version of kitchen. I have to deodex the framework and app folders to reduce their size so it would all fit into the /system partition. Thanks again.
[Android] dsixda:
Good to know! Didn't realize it was such a space saver.
[Android] Kanzie:
I've been having problems with script/fix_update_script: When trying to extract a rom (menu option 1) I get the following errors, and the resultant cooked rom will not flash (complains that it cannot symlink /system/bin/bugreport)

Extracting contents of system.img ...
end of image
Deleting system/bin/bugreport
scripts/fix_update_script: line 16: ./rm: cannot execute binary file
Deleting system/bin/dumpcrash
scripts/fix_update_script: line 22: ./rm: cannot execute binary file

Adding /system/bin symlink entries to update-script ...
./ls: 1: Syntax error: word unexpected (expecting ")")
./ls: 1: Syntax error: word unexpected (expecting ")")
...
Deleting symbolic links under system/bin of working folder ...
./rm: 1: Syntax error: word unexpected (expecting ")")
./rm: 1: Syntax error: word unexpected (expecting ")")
...

Tracing through your scripts, I've noticed that fix_update_script does something like:

1. cd into WORKING_*

2. cd into system/bin

3. (line 16 - corresponding to above error) "rm bugreport"

4. (line 22) "rm dumpcrash"

etc

It seems that (at least on my machine, probably with something to do with my PATH variable), your script tries to execute the ls and rm that is in the system/bin directory instead of the ones in /bin.

When I changed your script by prefixing those commands (lines 16, 22, 28, 37) with "/bin/", the scripts runs smoothly (haven't tried flashing yet). I think it might be a good idea to specifically make the script use the host's ls and rm commands. (May be through a which ls command?)

When I get home and try flashing a rom, I'll let you know whether my changes fix the problem I got.