yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
I have already covered this in the FAQ. Please read before posting, thanks.
[Android] TheAshMan:
Cheers again dsixda.

I've not tried it with my Nexus yet because CM seems to do everything I want anyway.

I gave it a go with a Desire ROM yesterday, and it seemed happy to produce a flashable ROM. I only removed all the extra apps and added in some useful ones.

Might have a go with custom kernels, a2sd (when it's stable) and other stuff some time this week too.
[Android] Mikeytjee:
Sorry man i read it al a couple of times but must have missed that part ;)

But now when it wants to install it gives me this:
[Android] dsixda:
Read the error message -- it said it is missing a package.
[Android] hoban_eris:
/data/app sort of works for me. The apps get installed correctly, but when once the system is booted, permissions issues keep you from installing any new packages. /data/data/com.market.vending/cache is the likely candidate, but I haven't been able to pinpoint it just yet.
[Android] Mikeytjee:
dude i did everything you said in the tutorial, download the 2 files and then sudo dpkg -i.. The2 files are in my download folder that;s the strange part cuz you can see i browed to my downloads folder with cd ~/Downloads/ where i downloaded the files :S
[Android] mnjm9b:
i believe he was refering to your error you posted

and if you would actually read it ...

it says:

sun-java6-bin depends on unixodbc; however:

Package unixodbc is not installed.

just a guess...but maybe you need to install unixodbc.
[Android] hoban_eris:
got back to working on it,

"chmod 775 /data/app" plus "chgrp 1000 /data/app" fixed it
[Android] dsixda:
Does this problem only apply to new apps that were manually copied to data/apps after flashing? Anything required for the kitchen or the update-script?
[Android] bonethugs:
error

Hi, I've installed cygwin but when i put the line to the jdk path, cygwin shows an error.

syntax error: the error is unexpected end of line

do you know how can I solve it?

Thanks
[Android] dsixda:
Please provide details as to what you included to your PATH variable. I can't help without seeing it. "syntax error" means that you wrote something in the wrong format, maybe you have an extra character somewhere, so that the path is unreadable.
[Android] bonethugs:
I wrote the line you put in the post to install cygwin.

PATH=/cygdrive/c/Program\ Files/Java/jdk1.6.0_20/bin:${PATH}
[Android] dsixda:
Open a Cygwin command prompt (double-click on the Cygwin shortcut), and type echo $PATH and ensure this path appears.

Also make sure this path is a real path to java.exe.... yours may not be "jdk1.6.0_20".
[Android] bonethugs:
yes, the path appears and it's correct, this means that it's working?
[Android] dsixda:
When do you see this error message? When it's signing the ROM?

I have no idea how you cannot get it to work, it's such a simple step. You have a syntax error somewhere in the file that you edited.

Put the path in a brand new line at the end of the file, otherwise you will need to Google the error message.

If you can't figure it out then cut and paste the .bash_profile into a reply (with

tags around it).

EDIT: By the way, does the following work from a Cygwin prompt?

[CODE]ls /cygdrive/c/Program\ Files/Java/jdk1.6.0_20/bin
[Android] hoban_eris:
Still testing. I'll let you know. Previous tests were done using an update.zip. I'm doing a fresh cook this time and we'll see what happens.
[Android] hoban_eris:
Fresh cook of the rom works fine. It's just my update.zip that was broken.

Thanks!
[Android] ed.dark:
Maximum rom size?

Hi,

Whats the maximum size the update.zip can be? Does a large update.zip use up phone storage or does it sit on a different partition?
[Android] Chevelle1768:
I would be great to replace the Superuser app with this new "Superuser 2.1" in your kitchen.
[Android] cougar694u:
This seems to work on CentOS, altough I haven't tried loading the ROM on my phone yet.

I wanted to also add that if there's a space in 'rom name.zip', the kitchen doesn't handle it. Of course, I just took the spaces out, nbd...
[Android] dsixda:
Would be nice, but I would prefer having an all-in-one superuser.apk without having to check for the build version and whether it was built from source.

Kinda tricky to make the script 100% correct in selecting the appropriate version, unless we make an option menu for the user to select manually (might be confusing for the user - what if they don't know what kind of ROM they have?).
[Android] dsixda:
Good find, yeah I have noticed this before but never got around to fixing it, although it is rather unconventional to have spaces in it from a Linux/Unix point of view.

I have fixed it anyway, I will upload a newer kitchen later. Thanks
[Android] Johbremat:
Props to dsixda for kitchen. Works a treat.

I've attempted to get the kitchen processing a stock ROM with little success. I select option 2 after setting up a working folder, and from the rom.zip file is extracted a system.img and boot.img(.) Option 3 doesn't help afterwards.

After a few combinations, in the end no directory hierarchy is produced and I can't strip unwanted apps.

Is my environment bung, or is it necessary to mount the system.img and copy the hierarchy from there to the working folder to proceed?
[Android] dsixda:
You need to be more detailed and post the output of your commands, otherwise I have no idea what your problem is. ;) Just paste it here, thanks.
[Android] djm25:
i know it was hard for you to go out of your way to make this kitchen for us students(noobs) and i thank you for it its just i wish there was a option to re theme or de theme a rom that has bin decompiled ....can you update the apps 2 sd to the new method i hear its faster then the current method .. on a side note when i say Extract kernel + modules from another ROM and use it on the rom im working on i loose controle of the brightness (both roms are 1.6) i just wanted the super csdi kernal on a stock rom .. i know i sound like an a$$ but please some help or info would be nice thanks for the kitchen non the less
[Android] leonnib4:
Excellent tool!

Nice scripts!

But does it work for Android 2.2 based?

I just get "E:Cant open /sdcard/###.zip (bad)"
[Android] cougar694u:
I get the 'bad' error whenever I try to edit the build.prop file(s) for some reason. Instead of my phone saying "Htcclay's Superbad..." I want it to have my name.
[Android] leonnib4:
so... to make it work, what should I do?

I did not edit build.prop...
[Android] cougar694u:
I dunno, I haven't messed with any 2.2 stuff, only 2.1. I tried to enable the /data/app in the superbad ROM, but I never could get it to work because update.script doesn't exist. Aside from a simple repackage of a ROM, I haven't done any custom stuff, just haven't had time with work carp.
[Android] leonnib4:
Ok so I tried a few things and I cannot get any of my zip files to work.

Always "E:Can't open(Bad)"

I cooked 2.2, signed, copied, flashed-> bad

I cooked 2.1, signed, copied, flashed-> bad

I opened enomther, signed, copied, flashed-> bad

I opened enomther, signed myself, copied, flashed-> bad

what do I do wrong?

PS: Im using clockworkmod recovery
[Android] cougar694u:
What OS/Platform?
[Android] dsixda:
New apps2sd method: I don't know how to do it, sorry.

I don't know what the CSDI kernel is, I'm not a porting expert and I only have a Nexus One, sorry again ;)

P.S. Make sure you also copied the modules (*.ko) when you added the new kernel.
[Android] dsixda:
What are you trying to do? The Android 2.2 update is just a software update, not a full ROM, so it won't work with the kitchen. Unless, you are using Paul's rooted Android 2.2 ROM... which is a full ROM.
[Android] dsixda:
There's been talk about this problem in the XDA forums in other places, just do a search. Seems like you didn't unmount your SD card correctly from your Nexus One before disconnecting the cable.
[Android] djm25:
is it possible to add a gui to this i can due with the comands but for thous that might find it confusing .... and intergrat the apk tool
[Android] dsixda:
Which part is confusing? You just type ./menu and follow the prompts. I made it as user-friendly as possible.

Making a GUI for 3 different platforms (Mac OS X, Linux, Cygwin) is a huge task and may complicate things even more and make the kitchen buggy. I don't think I have the time or incentive to learn and implement such a task. Simple is always better.

For the APK tool, please read the FAQ.

Thanks
[Android] leonnib4:
@cougar694u

GNU/Linux x86

@dsixda

I was just asking about 2.2. Ok I got it ;)

I already searched for bad umount but... I think I did it right. But ok, I'll do a search.

Thanks!
[Android] zach.xtr:
First of all props to dsixda for this wonderful tool! It has been fun to be able to configure ROMs.

At this point I am looking to understand the file tree structure and WHERE each of the important "config" files are located, WHAT they control, and WHEN they are read by the applications. Dr. Google has not been able to provide me with much (e.g. I am searching on: "android /system/customize/MNS/default.xml file use"); so I was hoping someone could point me in the right direction...

As always thanks!
[Android] SImoxTa:
I'm slowly reading the whole topic but in the meanwhile i have a "real noob" question. (after all i'm a noob :P)

With the "Port from another device ROM" command, I took a Nexus One rom (with the RC of Froyo on it) and a HTC Legend (2.1 R2 rooted from Paul's Modaco) and i tried to merge them together (my purpose is to have a final rom for the Legend with 2.2). Once i choose the Legend rom as first step, and then i choose the Nexus one as second, if i understood correctly the final signed *.zip should have the "RADIO.img" and the "BOOT.img" from the Legend and the whole rest from the Nexus right? Do I need to make any other steps before trying to flash it from the recovery on the Legend? (and that in fact is the real noob question :P)
[Android] dsixda:
If you are a noob then why are you porting a ROM, which is under the Advanced section ;-)

Few things to tell you:

- I am not sure if the kitchen supports Legend ROMs - as I already stated in the first post

- the Legend and Nexus One have different screen resolutions so porting is not going to work

- There is no radio.img involved on the cooking process. Only system.img and boot.img are used... You would have noticed that if you paid attention in the first step while porting a ROM or extracting a new ROM. ;) It asks for those two files specifically.

- when you port a ROM, basically you end up with the kernel (which is part of boot.img) and possibly a couple of driver modules from the Legend, but the rest is from the donor device.

Hope this helps!
[Android] SImoxTa:
You made it clear :)

My question about the Radio.img was about the fact that in the final zip it created there was also inside that file and i didn't know where it came from :)

About all the rest i got the point, so in my case i could "easily" port a rom from a hero (that "seems" to be a more supported device than the legend) and then it should be almost "perfect" to be flashed as soon as it finish the process.

Thanks :)
[Android] dsixda:
The Hero is a year old device, you would be downgrading your Legend (and to Android 1.5 possibly!) if you did that. Just read the discussions in the last few pages or search this thread, as I have already mentioned this. Good luck
[Android] cougar694u:
What flavor? I'm asking because I've used the kitchen on Ubuntu and CentOS and it seems to work fine on both, so I was curious if there's a third flavor to add. If CentOS works, I'd assume any RH-based flavor would work fine.

Hero got 2.1 last week or so.
[Android] dsixda:
I know, but the Hero is still an inferior device and the shipped ROM will take into account its shortcomings.
[Android] cougar694u:
What do you mean by inferior? I don't know much about it, only that it has more RAM than my MyTouch. I'm sure they're all inferior to the N1 :p I wish I had one of them.
[Android] dsixda:
CPU, RAM, etc... Look it up in Google.
[Android] cougar694u:
I understand that, it's a matter of perspective. From an N1, most things are, but from the mt3g, the hero's superior. I'd love to have the additional 96mb of RAM and a 3.5mm jack.
[Android] dsixda:
You're missing the point -- the original poster was wanting to know how to port a Legend to Hero, and I said it wasn't worth it because the Hero is a downgrade from the Legend. We're not comparing a G1 or Magic to the Hero here. ;-)
[Android] OMJ:
I followed your suggestion for installing Java JDK, and have it installed, but I keep getting this error.....this is on Ubuntu

update.zip created, ready for signing

Signing update.zip as signed_052610_132204.zip ...
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)

Was not able to create signed_052610_132204.zip!

Ensure you have a recent version of the Sun Java JDK

any suggestions? thanks!

*EDIT* I got it working, looks like I missed installing the sun java binaries
[Android] leonnib4:
Hi all, Hi dsixda,

remember my problem in recovery: Can't open (bad) when flashing my custom zip file?

well I said I was using clockworkmod recovery because I tought I may be an usue... well it seems it was!

I tried the same zip file in Amon_RA's 1.7.0 recovery and it simply worked like a charmed!

Thanks again for your tool and scripts!
[Android] dsixda:
Thanks for the update! I will add that to the FAQ later.
[Android] dsixda:
If you want to run the kitchen in Cygwin, I have uploaded a setup file to the kitchen's download server. All the Cygwin packages that are necessary for the kitchen are zipped up into this file, so installation will be very easy now.

If you are using a netbook + Windows for cooking, I would recommend Cygwin instead of a virtual machine (containing Ubuntu) ... because a virtual machine is verrrryyyy slow on a netbook! ;)

More info here:

http://xdaforums.com/showpost.php?p=5646155&postcount=76
[Android] leonnib4:
new question (sry) :D

I'm trying to include HTC_IME and Swype into my custom ROM, but they always FC except if I install them manually from sdcard. I placed them in /system/app then /data/app, no change.

Does anyone have a clue on this?
[Android] anderson620:
I've been trying to download the cygwin file from grdlock's site but when I follow the directions included and get to:

6) When it shows all the package names, go to the top and select "All <-> Default" until it changes to "All <-> Install" (you must click on the arrows)

instead of (ALL) it says (no packages found).

Is this something you've heard before? Maybe something I'm doing wrong (or just missing)?

I matched up MD5's, and the download's integrity doesn't seem to be the problem.

Thanks in advance.
[Android] dsixda:
Worked fine for me this morning on my work PC, I'm not sure why it doesn't work for you. Did you make sure the cygwin_packages folder path is correct? Which Windows version are you using?
[Android] anderson620:
I'm using Win7 64-bit. I did check the path; I actually removed, re-downloaded (if that's a word), and reinstalled in a different location, but still no luck.

I have all files removed as of now. I'm going to try again and see if I can post my steps so someone smarter than I can dissect them. With any luck you may still be online.
[Android] dsixda:
Oh, the laptop I used to create and run the Cygwin packages is also Windows 7 64 bit.

If you can't figure it out, then as a last resort just install from internet and install only the packages mentioned at the end of the ReadMe file.
[Android] dsixda:
By the way, that folder that is under "cygwin_packages" is called:

http%3a%2f%2fmirror.its.uidaho.edu%2fpub%2fcygwin%2f

Try renaming it, because it has those special characters. Then try running the install again.
[Android] anderson620:
I downloaded and installed on my other computer, which is an XP SP3. I had no problems, but I did notice the "other" folder inside of cygwin_packages, which I think was my problem previously. I've noticed in the past that Win7 seems to be a little more deliberate in searching for files; maybe I just (like you said earlier!) had the path wrong by omission.

Thanks for your help. I can't wait to try this out!
[Android] dsixda:
Hi guys, I just updated the kitchen.. please read the Release Notes for details. Going to bed now..
[Android] leonnib4:
How can you tell your ROM is gonna WIPE system in 0.53?
[Android] dancer_69:
I tried recently to cook a rom for Htc Tattoo with 0.52 version and now with 0.53, but I never get a bootable rom. My last try was just to extract the official rom with option 1 and to root device with option 2. The rom seems to created successfully but when I flashed, device pass the animation screen and shows the HTC logo.But after 20 seconds the logo desappears and device stuck there. I had success only when I just extract and rebuild rom without any change.

I'm using virtualbox ubuntu virtual machine on windows 7 32bit system to run the kitchen.

Does root option works for Htc Tattoo(cause seems that this is the problem)?
[Android] leonnib4:
Or maybe the root is the problem.

You said yourself: unpack then pack works.

Try to put by yourself the /system/xbin/su binary with Superuser.apk from the Superuser thread.
[Android] dsixda:
It's the line "format DATA:" in the update-script.

The Tattoo has been extensively tested with this kitchen, both with Cygwin and with Ubuntu by various users. The problem is not necessarily the root method but it seems to be the boot.img being modified and rebuilt.

If you can't get it to boot, install ADB in Windows and connect your device to it while booting. Read the FAQ on how to use 'logcat'. I am curious to know what the log output is.

Those two files shouldn't have an effect on the ROM booting though.
[Android] dancer_69:
I browsed the folders/files in working folder and there isn't su in xbin folder, it is in bin. I tried to replace it with one from another rooted working rom, but I had the same resaults. Tried to remove it and copy the working's rom su to xbin folder, again same result.

What the root option does? Is just copy su in bin, superuser.apk in app and busybox in xbin, or does some other changes? Because all the times, first I run this option and then I replace the files.
[Android] dsixda:
It also opens up the boot.img and modifies the default.prop file, then rebuilds the boot.img.

You can also try extracting the boot.img and then building it again (Option 15 then 16) without rooting, and you will probably have the same boot result. Something is not working right when the boot.img is being rebuilt. I haven't seen this problem lately on the Tattoo though.
[Android] dancer_69:
I will try thanks.

As for logcat, I cannot run it cause the device doesn't connect at all, so I cannot use adb.
[Android] dsixda:
By the way, do you have libA2DP.so and liba2dp.so under /system/lib? Or do you only have one of those two files?
[Android] dsixda:
What do you mean by "doesn't connect at all"? It should still try to talk to your PC during booting, you should see some log output.
[Android] dancer_69:
I have them both.

EDIT:

Adb doesn't find the device at all. So I cannot run adb shell
[Android] dsixda:
Re: [KITCHEN][MAY 28 '10] HTC Android Basic Kitchen, v0.53 [Linux / Mac / Cygwin]

Can adb see your device while it is in recovery menu?
[Android] dancer_69:
Yes.

-----

I tried options 15 -16 and rebuild rom, but the result is the same.

EDIT:

Sorry, didn't mention that you wrote without root, I'll do it again.

EDIT2:

With no root option and using 15 -16 options the rom boots ok.
[Android] dsixda:
Now that is strange. Did you mean Yes you can access adb through recovery menu? If so, then keep it plugged in while flashing, and then reboot it after you did the logcat command.
[Android] leonnib4:
I thought they might have an effet, e.g. making boot.img invalid somehow...

So thanks for the clearing and disponibility dsixda!
[Android] Sheen160:
Thanks dsixda! I used your kitchen to port over a hero rom to my Eris and it worked flawlessly. I didn't, but your kitchen did :D
[Android] drellisdee:
I'm having trouble with the su on a eris rom. Using the last leak and rebuilding only changing a few apks and adding su and busybox kitchen options I cant get the su to work. When I try to adb su I get cant find exec. Flashing the 2.1 su update.zip fixes the su but I'd like to figure out what to do to get it working in a rom. Usb debugging is on also. Thanks for the nice easy to use kitchen. I've been cooking for win mo for years and am going to switch to android after I get android cooking really figured out.
[Android] dsixda:
Hey, I know you from the ppcgeeks forums.. ;-) I was dsi76.

For your su issue, I wonder if the permissions were not set correctly in the update-script.

Can you add the following to the update-script after this line: symlink /system/xbin/su SYSTEM:bin/su

set_perm 0 0 06755 SYSTEM:xbin/su

I noticed they did that in the 2.1 su update.zip.
[Android] drellisdee:
I'll try that I had my su in system/bin/su does it need to be in system/xbin/su?

my related permissions were

set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
set_perm 0 0 04755 SYSTEM:bin/su
set_perm 0 0 04755 SYSTEM:xbin/busybox

I remember your from ppcgeeks its been a long time that was back in vogue days wasn't it?
[Android] leonnib4:
I have the same issue with the same set_perm and su in bin/
[Android] dsixda:
I'm sorry, ignore my last reply, I was looking at the wrong ROM for my info.

Where did you get the set_perm_recursive line for the xbin folder? My kitchen doesn't add that.

Ok, how about this.... in your update script, can you REMOVE the line "set_perm .... SYSTEM:bin/su" that you mentioned above, and then can you add this directly at where it was:

symlink SYSTEM:xbin/su SYSTEM:bin/su
set_perm 0 0 06755 SYSTEM:xbin/su

I used to cook for the Elf and also for the Touch Diamond, Pro and HD.
[Android] drellisdee:
Thanks I'll try that tonight I just got home from work. Where should I have the su binary? At system/bin/su or system/xbin/su or both?
[Android] leonnib4:
I solved the problem:

su in system/xbin

and

set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin

but dsixda's idea of symlink is also really good to fix the problem we have/had :).

[EDIT] @drellisdee: dsixda symlink solution made you put su in one folder, but made it also executable from both bin and xbin - like a shortcut

btw, dsixda, you should take a look at:

http://xdaforums.com/showpost.php?p=6637524&postcount=11

more really cool things could be included in init.rc with your rom kitchen ;)
[Android] dsixda:
Leave it under the bin folder because the xbin version is a symbolic link created by the update-script during flashing.
[Android] dsixda:
Yeah I know, it's a symbolic link (shortcut) which is sometimes used instead of the actual binary. Did my suggestion work though? I only copied the lines from the update.zip of the new su that was posted.

I know about that but there is no need for that in the kitchen. An advanced user can do that manually.
[Android] erickwill:
Hello Fellows,

I just wondering if is possible to port Windows Mobile drivers from a Brand like Eten or another to create a Android OS for them?

Any idea about how to do that?

REgards,

Erick