yashsingh1/xdaforums huggingface dataset:
[Android] robocik:
Yes, i am looking for such script too... i let you know if i find one.

i am gonna check out your port rom functionality, you copy the modules and kernel, but if i remember correct you dont copy the init.device.rc eg. init.hero.rc or init.sappire.rc, and you need it to get the wifi and sensors to work.
[Android] dsixda:
Oh! Good point. I have seen those files but never considered them.

What is the best way to do it? Shall I copy over all init*.rc files (except init.rc)?

Both the "Port ROM" and "Extract kernel/modules from another ROM" options would need to be updated.
[Android] robocik:
you need the init.device.rc for sure... but when you are porting a rom, it depends on from which device to which device you are porting, somtimes you are gonna need to edit them manually anyway, eg. to make wifi working...

new devices are using tiwlan_drv.ko and older are using wlan.ko... so need to change that in init.rc...
[Android] dsixda:
Ok, that shouldn't be too hard. Currently I just fix the kernel and move the modules, but I know there are lots more (what about build.prop?). You'll need to give me a rough algorithm so that it applies to all ROMs in general ... Of course it won't be perfect because some devices may require specific things, but it should be enough so that most of the work is already done for the user.

I'll take a break today though :-)

Thanks!
[Android] robocik:
Ok, let me know if you need something ;)

have a nice break :)
[Android] dsixda:
Sorry guys, I noticed one more issue in the kitchen tonight, so I had to fix it. It only involves the task killer tweak, nothing else.

Hope to take a break .... starting now! ;)
[Android] alan090:
Lately your updates are mutilating my update scripts.... I have to manually restore them after every unpack /port

Please fix this - I am using CM 5.0.8 - CM-6 (ds) - and Stock Acer Liquid Roms - Worked fine like 5 -10 versions ago

also please change the default to y for zipalign - i prefer just pressing enter as before...
[Android] dsixda:
This kitchen is for HTC devices, as already stated, so I'm not going to change it for an Acer ROM and then break HTC functionality. You can go into the scripts and change it on your own though.

Pressing "y" is an issue? Ok that can be changed.
[Android] nerdo:
@dsixda

Please allow me to buy you a nice cup of cappuccino with something sweet :D

Perfect kitchen.... am not a programmer but I know some basics.. rusty

though.... this kitchen is definitely the right place to start

A2SD in kitchen v0.68 (haven't tried latest yet)

I can confirm that A2SD functionality is working fine on my Desire ROMs now

Will try e2fsck and Darktremor files as I believe it moves Dalvik cache too to sd

ROM size(s)

Any tips guys on increasing internal and system memory? what can be cut loose?

Kernels

Have been trying to use the kitchen to import other rom(s) kernel(s) but with

no luck.... won't even boot... anyone managed or is it better done the dirty way!

dsixda again Shukran man ;)
[Android] tazzpatriot:
question

do any of the kitchen versions allow to just make a no wipe update? or do i have to wipe every rom? sorry for the stupid question
[Android] dsixda:
Check the screenshot on the first page for the answer and more.
[Android] TMartin:
Hey Dsixda,

I've been building with your kitchen for awhile now but I have a quick question. I did a nandroid backup on my HTC Evo of a ROM I made in your kitchen then later updated my kernel via an update.zip. I then dumped my backup with your kitchen, added data\app support, and moved a few things to data\app. For some reason the working folder didn't have su in the system\bin and few of my apks in data\app didn't build in. I also added the su to system\bin but still didn't have root.

I'm a noob when it comes to Android but I'm trying to learn. I have compared the update scripts from my stock rooted rom and the one from the kernel update.zip, I'm just not sure if I should every line from the one to the other.

EDIT: Also if I take the new rooted/deodex'd update.zip by Calkulin and dump it with the kitchen then try to add wireless tethering, it tells me the ROM isn't rooted. But when I show the working folder information, it says it is rooted and also isn't rooted with an unsecured boot.img. Should I allow the kitchen to re-root??
[Android] nerdo:
Speruser 2.2.2

BTW I added latest release of Superuser 2.2.2 found here to the kitchen and is

working fine
[Android] nickiberli:
Hi

Can you tell me how did you add the superuser 2.2.2 to the kitchen?

Maybe dsixda can add this to the next version?
[Android] dsixda:
Those shouldn't be happening. Can you give me links please to those ROMs/backups? Thanks
[Android] dsixda:
No, sorry, I have explained this a few times in this thread -- it's not easy to decide which version of the special Superuser app to use, because he has different ones for different kinds of ROMs. (Unless he has changed it to an all-in-one su?)
[Android] dsixda:
Anyone else having problems with enabling the custom boot animation feature? Someone mentioned it gave errors with flashing. I think I know of the error in the kitchen scripts..
[Android] TMartin:
Yes..ill post tonight.

EDIT: Any way to add data\data support??

Sent from my HTC Evo 4G!
[Android] dsixda:
I'll look into that later.
[Android] TMartin:
Here is the link to the Deodex'd/Rooted Stock ROM that tells me it's rooted but not (unsecured boot.img)

And here is the link to the nandroid backup that isn't dumping right.

Thanks!!!
[Android] fr4nk1yn:
Great Work! I'm spending too much time playing with this much like I did in the WinMo days.

Just so this isn't a useless post. To change the default wallpaper "default_wallpaper.jpg" in /system/framework/framework_res.apk should be changed.

There's two locations: /res/drawable & /res/drawable-hdpi

After changing and signing though It doesn't boot )':
[Android] dsixda:
You will likely need to sign every file so that they all use the same signature. The option is in the kitchen.
[Android] dsixda:
Thanks, I'll get to it eventually.. if not tonight then tomorrow..
[Android] dsixda:
Now I remember... someone else asked this question over a week ago on my Twitter, regarding the Evo ROMs. They're not fully rooted because the boot.img doesn't have the appropriate flags set, even though they have /system/bin/su and /system/app/Superuser.apk present.

The kitchen is reading it fine. You can tell it to re-root, in which case it will set boot.img properly.
[Android] capychimp:
this is not really a question or anything, but damn your kitchen has gotten nice :)

thank you for your great work :)
[Android] dsixda:
There is a problem with the /data/app as well as the /data/local (custom boot animation) scripts. I have put in a fix which may be coming shortly.

Your "su" binary is found under the /system/xbin folder. If you read the output while it was extracting to Working folder you would have seen it: :P

Found OLD_WORKING
Moving old working folders to OLD_WORKING ...

Found original_update/system.img
Found original_update/boot.img

Creating working folder WORKING_072110_001207 ...
Copying boot.img and system.img ...

Adding an update-script ...

Compiling unyaffs ...
unyaffs successfully compiled

Extracting contents of system.img ...
end of image

Deleting symbolic links under system/bin of working folder ...

Deleting system/bin/bugreport

Found ./system/xbin/su

Updating update-script with su entry

Deleting symbolic links under system/xbin of working folder ...
Found ./system/xbin/su

Found /system/xbin

/system/xbin/busybox already present

Updating update-script with BusyBox entries

Listing of WORKING_072110_001207:

total 2564
drwxr-xr-x+ 1 Danial None 0 2010-07-21 00:12 META-INF
-rwxr-xr-x 1 Danial None 2621440 2010-07-21 00:12 boot.img
drwxr-xr-x+ 1 Danial None 4096 2010-07-21 00:12 system

Done setting up kitchen!

The "show info" option also shows it was rooted when it was extracted to Working folder:

Working folder information
-------------------------------------

Android OS version : 2.1-update1
Build Number : ERE27
Rooted (unsecured boot.img) : YES
Rooted (Superuser.apk + su) : YES
BusyBox installed : YES
Apps2SD enabled : NO
Wireless tethering installed : NO*
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO

* - Did not find wireless_tether* or android.tether*
[Android] dsixda:
Ok, new version is now up.

I have added a new feature (Release Notes) based on user requests...

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

About the Kitchen

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

For help and discussion : http://bit.ly/aLKQaR
Follow dsixda on Twitter: http://www.twitter.com/dsixda
For Paypal donations : http://bit.ly/blHTKy

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

Check online for updates (y/n)? (default: y):

Searching for updates ...
An update was found (0.71).

[B]Latest Release Notes:

Version 0.71 (July 21, 2010):
- Updated the About page, so that if a new version is found, the Release Notes for the last version is shown.
- Fixed problem in update-script for custom boot animation feature (was specify ing an invalid folder)
- Fixed update-script conflict that occurs if user installs both /data/app and custom boot animation features
- Changes to kitchen's tools/apps folder: Removed Astro (no longer works :P), updated Titanium Backup
- Made some additional but very minor changes

[/B]Download (y/n)? (default: y):

This will only show you the LAST release note, so if you have version 0.69, it won't show you the release notes for 0.70 and 0.71; it will only show you 0.71's.

EDIT: This feature will only work if you have 0.71 or higher.. it won't show this info if you have something lower like 0.69... the above example was just a test, even though it says 0.69.
[Android] capychimp:
is it possible to make a feature of when deodexing, you can pause the deodex, so when it's done baksmling, one can edit the outcome and then continue and smali it up?
[Android] dsixda:
Well if there are failures you will see the number at the very end and you can go back to it. You can run each individual ODEX by itself too (there is an option in the menu)..

You're proposing that the script should stop when it encounters an error.. that may be a good idea, i.e. the user fixes it or removes the problem file and then restarts the deodexing.
[Android] dsixda:
P.S. Do not make a suggestion for changing something to the kitchen RIGHT AFTER I uploaded a new version ;) :P. After spending an entire night and uploading everything and documenting the release notes, and getting ready for bed, that's not what I want to read right afterward. LOL. ...You could tell me that a few hours earlier. ;) Hehe.
[Android] capychimp:
lol sorry just got to a problem now, where i would be a nice feature ;) but it's not in a hurry, just something to keep in mind, next time i will wait and write it later ;) but anyways looking at your script i might have found a manual way to do it :)

but anyways awesome job, still using .70 and it works really nice for me

deodexing mytouch slide goes well, but do have a fc on my uploads google apps, otherwise everything works, will make a logcat later on it
[Android] dsixda:
Well I think people would prefer having the script continue running after an odex file fails to deodex. There are a lot of files involved and most people would let it run unattended. If we make the script stop after one file fails, then you have to run the whole thing again. I would rather let it run in its entirety and then check the results at the very end.

The file that is in error does not get changed, so you will still have the original odex to try out again.
[Android] TMartin:
Awesome...Thanks dsixda

Yes...I knew that but when I dumped the Rooted/Deodex'd ROM I swear I saw su bin and xbin.
[Android] capychimp:
ok sounds clever ;)

i was thinking what about support for binary update script, right now the kitchen only checks for updatescript
[Android] dsixda:
If the ROM was made with a kitchen version earlier than 0.59 and system/xbin already existed, then the kitchen would have still put a new one under system/bin. That was an old bug in the scripts.
[Android] dsixda:
I can't support that because it will require too much effort and I already don't have much free time as it is. I dont even know how to create or read those. It will require a huge modification to existing scripts.
[Android] TMartin:
You must use your little free time very wisely because you bust these kitchen updates out extremely frequently.
[Android] dsixda:
11pm to 3am is not really free time, and I'm not going to continue doing that ;-)
[Android] TMartin:
Well you're an animal!!! Thanks for all you do sir.
[Android] dsixda:
All we really need is an updater-script--to--update-script converter. The kitchen can handle the update-script.

However, there are two types of updater-script, I believe. One that is standalone, and another one that involves it to be compiled into an update-binary.
[Android] dsixda:
That's just how I am, I won't go to sleep knowing something is not working right. ;)
[Android] dsixda:
BTW, in the Advanced Menu, where it says "Add /data/app functionality", please ignore the part that says "(stock ROM only)"... This no longer applies --- You can add it to any ROM.

I have uploaded a version of 0.71 without that label. But otherwise I didn't change anything else.
[Android] TMartin:
Alright....data\app is still only partially working for me. Some apks are being built in and others aren't. If I completely start fresh, can you assist me with my update script to add a kernel from an update.zip??
[Android] dsixda:
I don't know about what else should be done for the /data/app.

This is the main part in the update-script, maybe it needs to be another value:

set_perm 1000 1000 0771 DATA:app

If you want to add a kernel, just search the thread, I have mentioned it many times on how to do it. If you mean boot.img, then, easy.. just copy it over to your new working folder. If you want the *kernel*, use the boot.img unpacking method (Option 15), copy the boot.img-kernel file.... Then create a new working folder and put it into the new ROM (unpack, add new kernel, re-pack)...
[Android] TMartin:
It may just be an issue with the Evo. I'll get with Jugs and Calkulin and see if they have any issues. I'm still lurking around in WinMo so it seems i need to learn a lot more about Android. Thanks for all the help dsixsa

Sent from my HTC Evo 4G!
[Android] alan090:
when did CM 5 and 6 for (ds) = an acer liquid

I use it for liquid roms fine without complaints - my complaint is that your kitchen destroys every single CM update script there is and I have to manually restore it - no need to get all offensive towards the fact that it works with the acer roms fine ;)

CM is htc dream and sapphire
[Android] dsixda:
I was not offensive, I get complaints every day, you think I'm not used to it? ;) All I said is I don't support non-HTC devices. But I don't understand your cryptic language. DS is what? Liquid = Acer Liquid? CM for Acer? Oh wait, you mean HTC Dream and Magic? hehe.. I don't know these things, man -- I just have a Nexus One with my own personal ROM.

Please be more specific when you mean "mutilate" and "destroy".. :-D Also I have already stated, I do not support update-binary and updater-script.

EDIT: Actually I could just leave those two files in the ROM and/or ask the user if they want to keep them.
[Android] TMartin:
Here is what Calkulin's update script has for /data/app & /data/data:

set_perm_recursive 1000 1000 0771 0644 DATA:app
set_perm 1000 1000 0771 DATA:data

I'm going to try to change my update script to that and see if all the apks get built in.
[Android] dawynkoop:
data/app was not working for my roms on the Incredible, read through this thread and edited the file add_data_app_to_update_script in the scripts folder I replaced "nset_perm 1000 1000 0771 DATA:app" with "nset_perm_recursive 1000 1000 0771 0644 DATA:app" and after testing the rom, apps in the data/app folder installed successfully. The kitchen no longer shows data/app as being active when you check the rom info, but it does work in the actual rom.
[Android] dsixda:
Thanks guys for the help, that's very very appreciated :-)

I'll put that fix in during my lunch break, and also do a quick fix for the updater-script/update-binary issue.. I will leave those files in the ROM.

I'm currently working on a conversion routine to convert updater-script to an update-script. I got it successfully working on a shipped OTA ROM but am having trouble with a Cyanogen ROM, so it will take a bit of work.
[Android] marlopainter:
I found a German forum that talked about Windows adding hidden characters at line breaks. This is messing with the bash_profile inside the Linux environment.

http://www.pocketpc.ch/android-entwicklung/93588-hilfe-wie-kann-man-roms-kochen.html

Google translate did an alright job... I gathered we need a pure text editor.

I could be wrong though, lol.
[Android] dsixda:
Type: dos2unix .bash_profile

This will convert it to unix format... let me know if it works.
[Android] marlopainter:
Yes!!

I did that command from the default point Cygwin opens up.

I restarted Cygwin and those errors are gone!!

EDIT - I have yet to make a flashable ROM with this thing. I'm hoping this error

is the reason.
[Android] dsixda:
0.72 is now up, guys.
[Android] Yay 4 Juggs:
something is wrong with signing of rom...apks...etc...i modify apk's then tell the kitchen to sign them...says it does but when i flash the rom they force close...and com.htc.resources.apk never gets signed it seems apk's that require root force close as well...system apps as well that werent modified...settings...camera...dss...
[Android] marlopainter:
I loaded Dwangs 1.17 into the kitchen, removed some system apps, added some data apps, did the zip align and sign, made the rom, and flashed...

Made it thru sign up with Google account, but at the home screen....

force reboots continuously...
[Android] nickiberli:
I tried to deodex my ROM with the new kitchen (0.72). But I still have this f*****g boot-loop :(

Here is the logcat:

http://pastebin.com/V8ZAPpJH

I hope you can help me..
[Android] dsixda:
Why did you sign?
[Android] Yay 4 Juggs:
if you didnt modify the the files contained in the apk there's no reason to sign...dwangs rom is already signed...
[Android] dsixda:
Isn't this the same Maps.apk issue you have been mentioning here, which we had discussed already?

#
E/AndroidRuntime( 84): dalvik.system.StaleDexCacheError: /system/app/Maps.apk
#

#
E/AndroidRuntime( 84): at dalvik.system.DexFile.isDexOptNeeded(Native Method)
#

#
E/AndroidRuntime( 84): at com.android.server.PackageManagerService.performDexOptLI(PackageManagerService.java:2175)
#

#
E/AndroidRuntime( 84): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2553)
#

#
E/AndroidRuntime( 84): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2109)
#

#
E/AndroidRuntime( 84): at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2005)
#

#
E/AndroidRuntime( 84): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:595)
#

#
E/AndroidRuntime( 84): at com.android.server.PackageManagerService.main(PackageManagerService.java:335)
#

#
E/AndroidRuntime( 84): at com.android.server.ServerThread.run(SystemServer.java:135)
[Android] nickiberli:
I don't know, you're the specialist :)

What can I do?
[Android] marlopainter:
RE: app signing

Sorry for the nub-dumb... My posts are low because I do search my butt off for things, but some things are learned by mistake.. :P

Thanks for the info on that, I will keep it in mind on my next attempt.
[Android] Yay 4 Juggs:
still getting force close after force close...even with apps installed from data...was not getting this before...i have a flashable rom out there...something def went wrong
[Android] dsixda:
This is actually the third time you asked the same question:

http://xdaforums.com/showpost.php?p=7202778&postcount=1112

Come on dude, just search for Maps.apk in this thread.
[Android] dawynkoop:
I have an APK for the updated maps app if that would help. It's the apk for the version you install when you perform the update of the stock Google Maps.
[Android] nickiberli:
Can you upload this file? Maybe it helps.. :)
[Android] TMartin:
Hey dsixda,

Looks like the /data/app is working. The only apk I'm having issue is my ebay apk. If I throw it in /system/app it will work.

One other question....I changed my htcclockwidget a little, threw it in /system/app, then sign all apks and it works fine. Next I grab a multitouch keyboard and throw it in /system/app and resign all apks since I changed the keyboard apk and now my clock doesn't show. Any ideas why signing it twice might cause that??

All in all this kitchen has been producing all bootable Evo 4G ROMs for me. I have either a) started with a completely stock ROM, rooted it, then deodex'd it. b) started with a rooted stock ROM and just deodexed it. c) Grabbed my own nandroid backup. I really can't wait to see how far you take this great project!! Thanks dsixda
[Android] fr4nk1yn:
I'm starting over from a RUU base. Been having major problems last few cooks.

Trying to isolate but one thing that stands out the last 3 updates(?).

The working folders owner is root which makes modifying the files a bit difficult.

Is that by design?
[Android] dawynkoop:
I'm not at my comp right now, I'll post it later tonight when I get a chance.
[Android] antz88c:
i'm geting this when i make update.zip

sed: 1: "update-script": invalid command code u
[Android] juansuandi:
is it with update superuser file or an old super user? that with 0.55?

thanks
[Android] fr4nk1yn:
Something is "wrong" with the permissions. If your running Linux login as root, *gasp, or typing chmod +x menu will allow you run menu.
[Android] alan090:
yea if you leave them alone that would fix everything

I will try and be more specific in the future ;) sorry
[Android] BlaY0:
Hi dsixda,

I found a potential problem that might occur when building from ruu or nandroid yaffs2 (system) images. If toolbox/busybox is originally linked statically it might cause problems when building system update zip (size of it), as static links are not restored.

To prevent that, you could implement a logic that would check the size of toolbox/busybox itself and then find all binaries that have that exact same size and delete them except those two.

Regards,
[Android] Yay 4 Juggs:
i started from scratch with the latest build with no modifications to any app apk's and only modified the framework...only told to the kitchen to sign the framework apk...built rom..flashed...fc'd just about every time i tried to open an app...
[Android] dawynkoop:
Here is the updated Google Maps apk.
[Android] TMartin:
I think you should have signed all the apks so they all have the same sig. Just a thought.
[Android] Yay 4 Juggs:
i went back and did that...same result...fc's all over
[Android] dsixda:
Just woke up.. damn I am late for work ;)

To some of you -- as I already said next to the download link -- before asking questions please read the FAQ. You will do yourself and me a big favour by looking for your problem and saving us some time.. Also if you have a problem please be specific so that I know what you are talking about and so that I don't worry unnecessarily .. thanks

I don't like spoonfeeding because it wastes time having to do someone else's work for them. Google is also your friend.

LOL. I sound like myself in my old ROM thread ;)
[Android] dawynkoop:
Has anyone else noticed an issue with the Facebook for HTC sense being unable to connect?
[Android] dsixda:
Google: sed "invalid command code" ...First result will have your answer.

I need to have "-e" as part of the sed command whenever "-i" is used.
[Android] dsixda:
You have to remember the long discussion we had last week about Google apps and shared IDs + signing