yashsingh1/xdaforums huggingface dataset:
[Android] n10zf8:
Re: [KITCHEN][APRIL 20 '10] HTC Android Basic Kitchen, v0.47 [Linux / Mac / Cygwin]

how would i resolve a symlink error? i dont have the exact error at the moment but it was line 56 and said cant symlink busybox /system/xbin/bb or something like that. with that can you giveme amy ideas or fo you need exact syntax of error. i can get it ez by trying rom again if i need to.

thanks

Sent from my T-Mobile myTouch 3G using the XDA mobile application powered by Tapatalk

EDIT

ok options used 11 & 99

original rom used Fender Stock w/ Root

donor rom Eris_Official_0.8.1T2.zip

Exact error

E:Can't symlink /system/xbin/bb/

[

E:Failure at line 56:

symlink /system/xbin/busybox SYS

Installation aborted

I am not sure exactly what file it is I need to get rid of...only a placeholder is in system/xbin/bb/ and in system/bin as you mentioned above i find nothing that appears to be related

if you could give me a hand with this one i would appreciate it
[Android] dsixda:
Yes, you need to delete the same file in your kitchen, but under /system/bin.

Can you tell me which ROM you used, and what steps in the kitchen you used?

I can revise the kitchen so that it looks for that particular file.
[Android] n10zf8:
Re: [KITCHEN][APRIL 20 '10] HTC Android Basic Kitchen, v0.47 [Linux / Mac / Cygwin]

cool i will give that a shot later this evening will also give you rom details when i get back to my pc

ok options used 11 & 99

original rom used Fender Stock w/ Root

donor rom Eris_Official_0.8.1T2.zip

Exact error

E:Can't symlink /system/xbin/bb/

[

E:Failure at line 56:

symlink /system/xbin/busybox SYS

Installation aborted

I am not sure exactly what file it is I need to get rid of...only a placeholder is in system/xbin/bb/ and in system/bin as you mentioned above i find nothing that appears to be related

if you could give me a hand with this one i would appreciate it

Sent from my top-secret 8 core 36GB RAM 6TB desktop Vista/Ubuntu
[Android] :
You've made some nice progress with your Kitchen.

Keep up the great work.

I'm enjoying the new releases.
[Android] dsixda:
Thank you.. Another release just went up ;-)

Sorry for all the updates, but it seems whenever I think I have it down right, some new ideas or issues arise!
[Android] dsixda:
Can you quote line 56 exactly from your update-script file?

Usually symlink errors are due to the fact that the symbolic link already exists so it doesn't want to create it again.

The only thing you'll need to do is to locate that file that the symlink refers to, and delete it from your working folder, usually under /system/bin.

OR, you may just need to delete the "bb" folder, if you claim there are no binaries in it.

Okay, going to bed now..
[Android] n10zf8:
good morning hope you slept well

line 56 from my update script states "symlink /system/xbin/busybox SYSTEM:xbin/bb/["

i found this interesting and maybe? relevant line 57 states"symlink /system/xbin/busybox SYSTEM:xbin/bb/[["

i have DL the new version 0.48 which sounds like it will take care of this issue...will let you know...i am also going to search a little more to see if i cant find an answer somewhere, if the changes you made in kitchen or following your suggestions don't work.
[Android] dsixda:
Make sure you don't have the files named [ and [[ under system/bin. If this is from a cooked Rom then my script won't take care of it. It only checks for symbolic links in the shipped ROM file (system.img).
[Android] manom18x:
First of all thx for this great tool. I have one problem at the installation, I get a

Failure at line 2:assert getprop (''ro.product.device'') == hero

The rom I am trying to istall is a port from hero to magic.
[Android] dsixda:
Check your build.prop file (under working folder's system folder), and change your ro.product.device to "hero" or else "sapphire" (if already hero).

Let me know what happens.
[Android] manom18x:
First thx for reply.

I changed the ro.product.device to hero from sapphire but I get the same error.
[Android] dsixda:
I have no other ideas, man. Sorry. I'm not much of a porting expert. :-(
[Android] manom18x:
THX anyway. I will keep searching and if I find a solution I will post.

Solution found. When u use ports from hero u must also use the recovery from hero and not the modified recovery for magic.
[Android] dsixda:
You mean you have to flash the Hero's recovery image? I thought they were device-specific? Did you already try it? You could brick your device doing that, I thought.
[Android] cTnko:
Nailed it !!! thx man, dsixda not even wipe helped, but enabling usb debugging finally solved this problem, any chance that we/you could switch usb debugging to ON state when we are adding root? (i mean to edit root script you made and add another line which will switch usb debugging, so root would be working out of the box) ? dunno if i explained it right, i hope you get my point :)
[Android] mr.bang:
DAMN

to run kitchen on mac we need this updated script

i edited the line that make zip (on mac need only "zip -r")

and the line that delete the .zip (on mac need only "rm -r")

@dsixda test it if u can!!
[Android] mr.bang:
everyone have reported following exception when try to sign update.zip?

Building signed_021610_150816.zip ...

Exception in thread "main" java.lang.NoClassDefFoundError: testsign
[Android] cTnko:
"For some reason the tools/testsign.jar file was not automatically copied to your androidsdk/tools/sign folder. Just copy it manually and run the build.again."

do you use the latest version of kitchen ? this problem should be solved
[Android] mr.bang:
yay man i'm not newbie ;) i copy testsign.jar manually!! =)

but i do a trick..

i'm not type the path of my sdk.. simply i make a directory kitchen/tools/sdk/tools/sign

and i put into last subdirectory the testsign.jar..

then i type the sdk path: kitchen/tools/sdk

this exception throw even i type the true path of my sdk..

i mean that this testsign.apk can run only on a few last jre..
[Android] dsixda:
Yeah, I found the culprit..

Line 54 of do_root:

perl -pi -e 's/persist.service.adb.enable=0/persist.service.adb=1/g' default.prop

Should be instead:

perl -pi -e 's/persist.service.adb.enable=0/persist.service.adb.enable=1/g' default.prop

I'll put a new version up soon!
[Android] dsixda:
You mean from the official 2.1 source code? I would assume it'd work but I haven't tried!
[Android] dsixda:
I'm not sure how the Mac would handle it, but if you get it to work, let us know! ;)
[Android] mr.bang:
the verbose exception signing update.zip

mrbang$ java -classpath ./testsign.jar testsign update.zip update_sign.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:675)

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:316)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:280)

at java.lang.ClassLoader.loadClass(ClassLoader.java:251)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374)
[Android] dsixda:
I guess you will need to find the source code for testsign.jar/.java and re-compile it for MAC.
[Android] mr.bang:
i expand testsign.jar

into this jar i found testsign.java

yay the source!!

now i'm going to debug it!
[Android] dsixda:
Good work! I have updated the first post with a link to your original Mac binaries. If you get the testsign working, then we'll need to update that information.

Thanks for the help :)
[Android] idflood:
testsign.jar

First, thanks for the awesome work...

I tried to cook a rom on a mac and didn't had the error with testsign. I used version 0.5 of the kitchen, copied the binaries from mr.bang ( build_rom.zip ), and replaced the build_rom script with the one also provided by mr.bang.

I did a minimal setup ( setup working dir, build hero rom ), and it gave me a zip, without errors. ( didn't tried to flash it yet )

I haven't copied manually the testsign.jar, but it's located here kitchen/tools/testsign.jar
[Android] dsixda:
Cool.. did you try the build_rom from 0.5? I modified the two lines that mr.bang suggested, so that is compatible with Mac as well.
[Android] cTnko:
just out of curiosity, lets say i add Astro (with your sample script for example) can i still update this app via market > downloads?

i am trying to figure out, how can i update google maps to the "latest version for 1.5 android" any ideas? i know that when maps are "included" like all other apps in rom, maps are invisible in market so i cant do anything with it
[Android] idflood:
Yes, i tested with 0.5. I don't have looked much deeper, but I had two error while trying to add root, or add the task killer tweak ( same errors ):

Building ramdisk-boot ...
scripts/build_boot.img: line 46: ./mkbootfs: cannot execute binary file

Building newBoot.img ...
scripts/build_boot.img: line 50: ./mkbootimg: cannot execute binary file
[Android] dsixda:
I am not sure, but even if you can't do it, I'd use an app called aTrackDog to track them for you. I always have TitaniumBackup and WaveSecure in my cooked ROM. With Titanium I can restore my apps automatically without having to go to the Market.. And also, no thief can uninstall WaveSecure when it's in the ROM.. unless they know how to delete a file with root.
[Android] mr.bang:
maybe i found the solution

on my mac 10.5.2 i was unable to sign trought testign.jar

so i found another sign tool: signapk.jar + testkey.pk8 + testkey.x509.pem

open terminal

type:

java -jar signapk.jar testkey.x509.pem testkey.pk8 <update.zip> <update_signed.zip>

yay no more exception

but i need anyone who test this update_signed.zip

anyone?
[Android] dsixda:
If you have a recovery menu, just make a nandroid backup of your current system. Then try to flash your test ROM.

BTW I thought signapk was for signing just *.apk files?
[Android] dsixda:
Are you sure you copied mr.bang's mkboot* binaries to the /tools folder?
[Android] jcarrz1:
This is good stuff right here, and I love the responsive developer!

A few questions:

what flexibility does the script have for porting from another device? Does it modify or replace the kernel? can it implement a2sd or space-saving measures (e.g. framework on /data for low-space devices)?
[Android] dsixda:
The porting option will replace the kernel and the drivers under system/lib/modules. It's very basic and leaves it up to the advanced user to figure out everything else.

Yes, there is apps2sd and data/app support in the options. Just see the screenshot on the first page for an overview of the main menu of the kitchen.
[Android] manom18x:
Magic 32A(with new spl 1.76.xx) use the same recovery with hero:):).
[Android] dsixda:
That's great! But alternatively, couldn't you have also checked the update-script to see if there was any reference to ro.product.device as well?

Eg. I found this answer - http://wiki.cyanogenmod.com/index.php/Talk:Building_from_source
[Android] manom18x:
Thx for the info. I correct the update-script and now is working with magic recovery:D.
[Android] dsixda:
Hi,

The new version of the kitchen has now been uploaded (0.49). It now supports cooking of your Nandroid backups.

Have fun!
[Android] kendong2:
i have a suggestion: what about an option to "adb push" the rom to the sdcard, once it is done? like this (pseudocode):

if [ ! device is in recovery ] ; then
adb shell reboot recovery
sleep 15
fi
adb shell mount /sdcard
adb shell push rom-signed.zip /sdcard

might even evolve to autoflashing it, though i couldn't find code/commands to flash it via cli... nandroid can be controlled via adb easily btw, if you want an option to backup before.
[Android] dsixda:
That would require people to install the Android SDK, I don't want them to do more work to set up the kitchen.
[Android] kendong2:
wouldn't it be sufficient to include the adb binary?
[Android] dsixda:
I could, but I haven't tried to see if any other binaries/DLLs are required.
[Android] alan090:
actually you just need to modify the update script under the com folder

anyhow my biggest problem porting from other devices seems to be the drivers for camera - drivers for accelerometer

i think pushing different lib to the build can fix both problems just does not seem to detect and or use the proper driver that i push from another builds
[Android] stevefxp:
Good morning,

I have a HTC Whitestone (Imagio). Can this kitchen be used to port to other devices? Has anyone thought about adding support for Whitestone?

Thanks,

Steve
[Android] dsixda:
The title of this thread answers your question.

Use Platform Rebuilder Kitchen for HTC WinMo.
[Android] dsixda:
I made a couple of changes to the kitchen, so now version 0.50 is up. If you don't use Cygwin, then you probably don't need this update.
[Android] thedivinehairband:
Busybox Error

Being a bit thick here probably but having issues.

My starting rom was SuperD 1.9.2 with WG kernel

I'm trying to port Villain 5.4.

When I flash the zip created with option 11 I get the error:

E:Can't symlink /system/xbin/bb/zcip

E:Failure at line 62: symlink /system/xbin/busybox SYSTEM:xbin/bb/zcip

My bb folder has nothing in it bar a placeholder file. From what I can gather from this thread I should be able to just delete the bb folder and all things should carry on happily. Not seeing it though.

Sorry for being a bit pants. This is my first rom cook.

P.S.Love the Kitchen btw. :D
[Android] dsixda:
Do you have a system/bin/zcip file in your working folder? If so, just remove it.

Is this the Villain ROM from the Nexus One forum?
[Android] thedivinehairband:
It's the Hero/G2 Villain ROM from http://xdaforums.com/showthread.php?t=654030

There isn't a zcip file in the system/bin folder. Deleting the bb folder under xbin didn't work either.
[Android] dsixda:
Is the zcip file anywhere else in your working folder?

Ok I will take a look later, as I have to go to work now.

Can you in the meantime quote the entire update-script here ? Thanks
[Android] dsixda:
Don't delete the /xbin/bb folder in your working folder, because then it can't create the symbolic link file there.

Also, is there a "busybox" file already somewhere in your working folder?
[Android] thedivinehairband:
The "busybox" file is in the system/xbin folder. It doesn't appear anywhere else.

I did play about with changing the ../busybox text to /system/xbin/busybox in case it was not resolving the location properly but that just gave the same error.
[Android] dsixda:
Try a search-and-replace, so that "../busybox" becomes "busybox"

e.g.

symlink ../busybox SYSTEM:xbin/bb/zcip

is now:

symlink busybox SYSTEM:xbin/bb/zcip

That's the common way of doing it in an update-script.
[Android] dsixda:
This is probably the reason for your error (not the kitchen).. I did a Google search:

http://xdaforums.com/showpost.php?p=4247486&postcount=5638

You need to update an SPL.

I'm not going to spend time on this anymore ;) Please use google first.
[Android] thedivinehairband:
Nope. Same error. :(
[Android] thedivinehairband:
Ah. I did check through a few things mentioning SPL but didn't come across that one. Guess it helps you better know what to look for though. Thanks for your help.
[Android] dsixda:
To be fair, perhaps the cook who provided the G1 ROM should have mentioned on his/her download page that the SPL requires upgrading (or he/she probably already did, but did not make it clear enough?).
[Android] 87Fra87:
I want to know because when I create the folder for the rom the terminal shows me the following messages No META-INF folder found under working folder!?....I have put the directory and files contained in the folder dsixda_Android_Kitchen_0.50 in another folder created by myself called Kitchen........is it right?.........
[Android] dsixda:
You can unzip my kitchen (ie. the 3 folders and the 'menu' script) into any folder name you like.

Regarding your error message, are you using a ROM that was already cooked before? Did you use a .ZIP file for the ROM? Details please.

Or, did you mean you zipped up the WORKING_* folder, and then tried to extract it with Option 1? The error message likely means you are missing the update-script file.
[Android] 87Fra87:
I have downloaded the rom for my liquid from the site: shipped-roms.com/shipped/, i have downloaded the lastest version that is 0.010.00. The format is zip, i have put the zip in the original_update then i have used the terminal for run the Android ROM kitchen........I have pressed 11 Port ROM from another device than i have pressed 1 A ZIP file for a cooked ROM................finally i have the following message:

No META-INF folder found under working folder!

why?
[Android] dsixda:
Did Acer merge with HTC? ;) This is an HTC Android Kitchen, there is no guarantee it will work for other devices.
[Android] 87Fra87:
OK...............There is another kitchen rom for liquid?
[Android] dsixda:
What's a kitchen ROM?
[Android] 87Fra87:
excuse me, I wanted to say there is an Android basic kitchen that worked for liquid?
[Android] dsixda:
I'm not sure.. I only own a Nexus One.

You may want to ask in the forum or go to an Acer site and find out. Use Google ;)
[Android] thedivinehairband:
Re: [KITCHEN][APRIL 25 '10] HTC Android Basic Kitchen, v0.50 [Linux / Mac / Cygwin]

I haven't needed spls before for many roms that say I do as I'm running a 32b magic but there's a first time for everything. :)

I'll have a look into flashing one and see if that makes any difference.

Sent from my Htcclay's SuperFast 3G using the XDA mobile application powered by Tapatalk
[Android] dsixda:
Make sure you flash an SPL meant for your device - you don't want to brick it! I assumed you had a G1, because the threads I quoted here and in the FAQ for this problem were from G1 forums.
[Android] thedivinehairband:
I'm not mad, really, maybe.

OK. Sorry to bother you again but I don't think I'm totally mad. Not really.

Got a ROM that works for my device, KingKlick's DroidEris2G1 1.2. http://xdaforums.com/showthread.php?t=642643, I flash it, it boots. Lovely.

I run it through your Kitchen. Port it in, make no changes. Create the singed zip. That works.

But then!!!

Make changes to the folders ie. Move the apps from the app_s folder under data back into an app folder under system and the framework folder back into system and it all goes wrong. Nothing else is changed but when I flash the ROM I get the following:

E: Can't chown/mod /system/bin (no such file or directory)

E: Failure at line 17: set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin

Now I know that the general consensus is that I don't have the latest SPL but this ROM does work until I start messing around with folders. I could put a new SPL in but because this ROM works without it already I'm loathed to go down that route.

Sorry to be such a pain in the arse. You can just tell me to go flash an SPL. Or use stronger words if you feel. :p
[Android] dsixda:
Did you delete the bin or xbin folder by accident?
[Android] thedivinehairband:
Nope. They're still sitting there happily. Do you want me to upload the Working_folder in a zip and the output zip I get to somewhere? Perhaps that might provide you with some useful info.
[Android] dsixda:
You could, but I probably can't help you much, as I'm not an expert (and definitely not with porting!). The reason he moved the files to the data folder may be because of the RAM limitations of the G1/Magic (as this is an Eris port). For example, the same thing needs to be done when you port the Desire ROM to the Nexus One, because it has less storage RAM.
[Android] thedivinehairband:
Hmmm. RAM limitations. Could be an idea. I'm gonna have another go then. Perhaps there is a limit to the amount I can put in the system folder. I'll try moving stuff about and see where it gets me.

Thanks again.

UPDATE:- You are a genius!!! I bow to your brilliant mind!!! The system folder was too large. Through some searching I've found out the size of the partitions and must now take care with my ROM folder sizes. The zip flashed successfully!! Now I've got other problems but I can work from here. SMD Port Open Failure on my logcat. This one is gonna keep me going for a while!! Thanks again!!!
[Android] dsixda:
Hi, I have put up version 0.51 with a couple of small updates.
[Android] stian230:
hey dsixda.

use your kitchen daily to all sorts of stuff. changes files in the system, framework and creates Custom themes in the original ROMs.

here is something I do with your kitchen:

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

thanks for a brilliant kitchen:)
[Android] agentcdog:
Works great!

Just chiming in to say that I used this tool to make a couple tweaks to the v3(or 4, depending who you ask) leak and it worked great. No issues here.
[Android] hoban_eris:
Thank you!

Thank you so much for your work on this kitchen!

I've been empowered to create the following ROM with help from your kitchen:

http://xdaforums.com/showthread.php?t=674134
[Android] .mak:
dsixda,

When I use your kitchen to decompile, edit and recompile the Verizon Eris v4 Leak, I can't seem to get /data/app to stick. The folder structure is there, but your kitchen always says it's not enabled, and apk's inserted into /data/app don't install when the ROM is installed on my Eris.

Help is appreciated :)

Thanks,

-mak
[Android] dsixda:
Please give details as to what steps you used in the kitchen.
[Android] rodigezstyle:
Hi dsixda, can be that your kitchen do not support the HTC Legend ???

all the Roms i create with only little changes in the apps don´t will boot & Stock on the HTC Animation..?
[Android] dsixda:
Didn't Paul@Modaco say something in the Legend rooting thread that it's not possible to write to the boot.img or something? You'll have to read that thread or ask around in that forum for more info.
[Android] rodigezstyle:
thanks.. but i didn´t touch the boot.img..?
[Android] dsixda:
I guess it has to do with the /system folder? I don't know, I haven't kept up with all the latest stuff. Sorry
[Android] .mak:
I setup the working folder, then gave the ROM root permissions, added wireless tethering, enabled /data/app and packaged it up for a test.

I've built 19 ROMs using your kitchen, all the same build just slightly modified, and I've tried with and without zip aligning apk's, the kitchen always says /data/app is disabled before and after enabling it.

Once the ROM is booted up on my Eris, I quickly find that the apk's that were left in /data/app were not installed upon installation of the ROM each time :o
[Android] dsixda:
hmmm.. I don't know what to say. I had the same problem with certain Modaco ROMs when I added the data/app option. Maybe we need to add something to our devices?? :-(

The data/app functionality in this kitchen was tested successfully on the HTC Hero when it was first added.
[Android] .mak:
That's probably it, there's got to be something missing or out of place. Hopefully I can figure out what that is :)
[Android] Andrizoid:
hoping someone can help, ni can seem to get the menu script to run

ken-kygers-computer:~ slipknotfan4life06$ cd /Users/slipknotfan4life06/dsixda_Android_Kitchen_0.51
ken-kygers-computer:dsixda_Android_Kitchen_0.51 slipknotfan4life06$ ./menu
-bash: ./menu: Permission denied
[Android] dsixda:
chmod 777 menu

./menu
[Android] pympster:
Works great on OSX, thanks!!
[Android] mazjed:
coking legend rom

hi every body

thanks for dsixda for great work

is there any chance to cook a legend rom using this ketchen

and thanks again
[Android] dsixda:
I have already answered this question in the previous page.

As I only have one device (Nexus One), someone else will need to find out.
[Android] Mikeytjee:
Thnx man love it!

Edit: When I try to put it al together it gives me a error when signing. So i tried to install the java but when i install it it gives me a screen with the legal agreements and stuff but i can;t press ok and enter doesnt work :S can you tell me what to do?

Mike