yashsingh1/xdaforums huggingface dataset:
[Android] mike1986.:
So it's not usefull file in the kitchen?

BTW this is updater-script:

ui_print("AnyKernel Updater by Koush.");

ui_print("Extracting System Files...");

set_progress(1.000000);

mount("MTD", "system", "/system");

package_extract_dir("system", "/system");

unmount("/system");

ui_print("Extracting Kernel files...");

package_extract_dir("kernel", "/tmp");

ui_print("Installing kernel...");

set_perm(0, 0, 0777, "/tmp/dump_image");

set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");

set_perm(0, 0, 0777, "/tmp/mkbootimg");

set_perm(0, 0, 0777, "/tmp/unpackbootimg");

run_program("/tmp/dump_image", "boot", "/tmp/boot.img");

run_program("/tmp/unpackbootimg", "/tmp/boot.img", "/tmp/");

run_program("/tmp/mkbootimg.sh");

write_raw_image("/tmp/newboot.img", "boot");

ui_print("Done!");

Where should I add it in the original update-script? Should I add more then those lines? :

set_perm(0, 0, 0777, "/tmp/dump_image");

set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");

set_perm(0, 0, 0777, "/tmp/mkbootimg");

set_perm(0, 0, 0777, "/tmp/unpackbootimg");

run_program("/tmp/dump_image", "boot", "/tmp/boot.img");

run_program("/tmp/unpackbootimg", "/tmp/boot.img", "/tmp/");

run_program("/tmp/mkbootimg.sh");

write_raw_image("/tmp/newboot.img", "boot");
[Android] BlaY0:
Why for the sake of Android god would you do that??? If you don't know what those lines mean leave ROM building to someone else.

When you are building ROM, you don't need to separate kernel and initrd images, just put them together into boot.img flashable image and put it into your ROM. If you don't know what am I talking about GOTO 1st paragraph.
[Android] mike1986.:
Well I suppose you were born as Android Guru and now it's all easy for you. I believe forum is a perfect place for asking questions. If it's forbidden to ask questions here then please mention this in the topic or wherever. If not then please don't answer my questions if you are going to be "oh I know everything" guy. Some people here are learning. The point of the kitchen is mentioned in the first post and it says "Those who are brand new to "cooking" and want an easy place to start". So what's your problem?

Info from this thread:

so heres what's in "first case above"

and finally I was asking about:

So the kernel implementing tutorial by dsixda says that I should add those lines but you said something different.
[Android] BlaY0:
No my friend, you said that you knew what to do with kernel folder but obviously you didn't. Second thing is that you don't know that there is a difference between update-script and updater-script/update-binary pair. If you open them, you should notice a big difference in syntax and you can't mix those two contents. Third... your concept of learning is very wrong. You think you would ask a Q here an a Q there and all of a sudden become a chef. Well you're wrong... such approach would cost you a lot of questions and would nee you to memorize too much. That's not learning my friend, it is called memorizing things. Sorry if this post sounds discouraging. Well in fact it is. I want to discourage you in this "chef" business because with such approach the scene will end with bunch of mediocre cooks and no chef.

Despite all of the avove I will give you an advice for free. First check Cyan's advice thread in this subforum and second open any update U get and read the contents of every script inthere trying to understand what they actually do and try to invoke some commands from those scripts manually just to see what would be the output. Actually things are not that simple as this kitchen is trying you to think.

And for the last... you don't need to implement the kernel update routine just to be able to use custom kernel in your ROM, you just need a kernel image from that update and integrate it into boot.img (replacing the previous one).
[Android] mike1986.:
I don't want to be a chief. I just want to make good rom for myself. I used to be a professional chief in Windows Mobile section (you can see my signature) and I don't want to play with Android as much I used to play with WM because I don't have that much time now. I was confused with this kernel because the author mentioned about a lot of extra stuff with the kernel

so I though that I need to do something more then just compile new boot.img and copy files from system\lib\modules to working folder.

Android cooking environment is totally different that the one for WM so that's why I'm lost sometime in informations and I have also some old "habits" from WM that are not helping me here in Android cooking.
[Android] BlaY0:
Now you're talking m8 ;)

Haven't seen your signature, I guess it can only be seen through web forum.

I can tell you this much that kernel update you have is basically on-the-fly native boot.img creator. It is run on your phone (while doing the "update") copying your current boot partition into file on recovery's ramdisk, disasembling it into kernel image and initramfs image, grabbing new kernel image, asembling it with current initramfs image into new boot.img image and flashing it back over. You don't need all that mumbo-jumbo when doing the whole ROM. You just need to extract (disasemble) boot.img you have in the kitchen, grab a kernel image from that kerlnel update (it's zImage file in kernel dir) and put it in place of current kernel image in BOOT_EXTRACTED dir of your kitchen (don't remember the exact filename but you should figure it out I guess) and make new boot.img from your current initramfs image and new kernel image. You probably wonder what the hell is this initramfs image... well it is basic (initial) system that is extracted into device's RAM upon kernel loading and is mounted afterwards as a so called root file system...

Enough for today. I think one should really know some Unix/Linux principles before trying to make 1st Android ROM. Maybe I will write a guide covering all this basics in this subforum some day ;)
[Android] endroidphone:
i'm having an error as:

Error: /system folder is empty!

Unfortunately unyaffs cannot open this system.img. The file format used in the .img file may not be supported.

can anyone help pls? i'm using the desire rom, which is put in the original_update folder. i'm wondering if this error is caused since the rom is not supported by the kitchen. any help will be appreciated. thx.
[Android] BlaY0:
What was the exact filename of the ROM you were talking about? You can issue "file <my_file>" command to find out of what type is that file exactly...
[Android] dsixda:
This question has been asked three or four times already this month. Are you sure it is a Desire ROM or a Desire HD/Ace ROM?

EDIT: I was just going to add the answer to the FAQ when I realized it was already there. So, again, make sure you read the FAQ for any questions.
[Android] P30TiP:
Hello,

First I have to say: thank you alot for this kitchen!

Secondly, I have a problem, here is what I did step by step (device = Nexus One):

1- I setup the kitchen

2- Used Cyanogen latest nightly as base

3- Copied the Arabic framework.jar, libandroid_runtime.so & libwebcore.so to my woking folder (got these files from cyanogen4arab.com)

4- Unpacked boot.img and then Replaced the zImage file from "kernel" folder with the boot.kernel-image (intersectRaven latest BFS kernel)

5- Added gapps HDPI apks

6- added data/app function and copied some apks to it

7- Re-added root permissions with ChainsDD (don't mock me on this one! :D)

8- Changed name of the ROM

9- Added apps2sd

10- Added etc/init.d scripts support (busybox run-parts)

11- Signed and then zipaligned all apks

At last I copied signed .zip file made with this kitchen to my n1 and when I want to flash in recovery it shows this:

E:Can't mount TMP:

E:Failure at line 1:

copy_dir PACKAGE:backuptool.sh.dir TMP:

Installation aborted.

Thanks in advance!
[Android] BlaY0:
Well, error said it all. Your gizmo obviously doesn't have a tmp partition, so you can't mount it. Obviously you don't know your gizmo enough if you are trying to do something it does not support. Investigate your update(r)-script.

I hope your next question won't be "What's tmp partition and what's it for." because we could easily end up in 3rd grade of elementary school...
[Android] TMartin:
I honestly had Zero Unix/Linux principles before I release my first Android ROM and I've seemed to be alright lol. I'm alright mainly because of people like yourself, behnaam, dsixda, netarchy and Calkulin.
[Android] P30TiP:
I'm completly new to cooking and I know only a little bit of it (very basic). I appreciate your anwser, but I will appreciate it alot more if you guide me through... I'm making this ROM for myself and I would be very happy to see it working. By the way I searched in the topic and it returned with converting update-script to updater-script. I did that and it still doesn't work...

Thanks
[Android] dsixda:
Nexus One doesn't seem to have a TMP partition, this is what I said in the past (you probably read these):

From 2 days ago:

http://xdaforums.com/showpost.php?p=8577346&postcount=2335

From 2 weeks ago:

http://xdaforums.com/showpost.php?p=8371392&postcount=2204

http://xdaforums.com/showpost.php?p=8360682&postcount=2189

Unfortunately i have no idea what to do, I have tried converting the updater-script in a Cyanogen ROM myself and had instability when using a workaround for TMP (I tried copying to a different folder rather than TMP).
[Android] P30TiP:
So there is no solution? :(
[Android] BlaY0:
There are plenty. But first we have to know what's inside backuptool.sh.dir directory otherwise we won't know how to handle it...
[Android] dsixda:
The backup script just backs up and restores the google apps. I got it running by changing it to a new folder rather than TMP, but the ROM itself was not stable (I forgot what the actual problems were but I think once it did not boot successfully after I reset it later). So perhaps the TMP workaround was not the problem for me.

I could try to put that workaround into the conversion script anyway or you can manually edit your update-script to fix it.
[Android] TMartin:
Hey Guys,

I've seen people deodex the Ace apps/framework so I decided I wanted to try deodexing the Lexikon 1.31.605.1 apps/framework but I'm having some errors thrown. It seems it only deodex's the jar files and can't do any apk's.

Here's what it's giving me:

Trying dependency with ext.jar ...
Disassembling services.odex ...
java -Xmx512m -jar baksmali.jar -d ../framework -c :com.htc.framework.jar -x ser
vices.odex

Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ClassPath$ClassNotFoundException: Could not find int
erface Lcom/orange/authentication/simcard/AkaAuthenticationResult;
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.loadAllImplementedInte
rfaces(ClassPath.java:819)
at org.jf.dexlib.Code.Analysis.ClassPath$ClassDef.<init>(ClassPath.java:
675)
at org.jf.dexlib.Code.Analysis.ClassPath.loadClassDef(ClassPath.java:280
)
at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:16
3)
at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(Cla
ssPath.java:110)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:96)
at org.jf.baksmali.main.main(main.java:278)
Error while loading class Lcom/android/internal/telephony/gsm/HtcSimCardAuthenti
cationManager$AkaAuthenticationResultWrapper; from file .\framework.zip
Error while loading ClassPath class Lcom/android/internal/telephony/gsm/HtcSimCa
rdAuthenticationManager$AkaAuthenticationResultWrapper;

WARNING: Cannot deodex services.odex

Any help?? New baksmali or smali I might need??

EDIT: Well it seems to only be an issue with two jar's in framework. It just deodex the apps there are no errors. If I remember correctly, if threw errors for everything in framework but everything but two jar's got deodex'd.
[Android] P30TiP:
Okay thanks, I switched to another ROM as base... I should forget CM then :(

Just one more thing: How can I have 2 launchers? Like the Launcher2.apk and LauncherPro.apk? I copied launcherpro.apk beside the launcher2.apk and when I flashed my ROM, it didn't ask for wich launcher to use...
[Android] BlaY0:
The easiest way would be to install Home Switcher which allows you to set default home launcher.
[Android] deprecate:
You will have to create it first :)

Sent from my Nexus One
[Android] ToastPwnz:
Ah alright. I feel kinda dumb now. >.<

Any specific directory it needs to be in?
[Android] Jlluna87:
permission denied

so i'm tryin to start cooking but when i bring up terminal and type in ./menu i get permission denied. if any1 can take me through some steps to help me get started plz pm me. if you need more info on what i'm dealing with PM will work as well. thank you
[Android] dsixda:
When you downloaded the kitchen, I said twice: WARNING: READ THE FAQ. Is that so hard? :rolleyes:

Or, you can search the thread:

http://xdaforums.com/showpost.php?p=7779521&postcount=1774

http://xdaforums.com/showpost.php?p=7313737&postcount=1380

http://xdaforums.com/showpost.php?p=7565896&postcount=1634

http://xdaforums.com/showpost.php?p=7307361&postcount=1368

http://xdaforums.com/showpost.php?p=7235343&postcount=1235

http://xdaforums.com/showpost.php?p=6419740&postcount=635

Next person who asks will get banned ;) :D
[Android] jjfreak5:
Okay now I may have just missed this somewhere. I tried searching this thread, I have tried searching google and everything. I know you can get Cyanogen to run on an emulator, but is there any way to get a rom that I cooked to run on the AVD or not? I am guessing it probably isn't otherwise there would be instructions on it I would assume.

Because I am cooking one for an Incredible, but I currently do not have an Incredible (hope to be getting one very soon as new every two is up real soon). I just wanted to try and test it, but guessing it won't be possible until I get my new phone.

Thanks for any help, and to the OP for making such a great tool!!
[Android] Jlluna87:
D'oh

lol, sorry. i guess i skimmed past that part. thank you. i figured it out and meant to come back and delete my post before someone noticed. but thank you for quick reply.
[Android] P30TiP:
Thanks very much for the replies. Just one last question: I used Paul's rooted/deodexed/busybox FRG83 as base and I miss one thing: 720p. Is there anyway to add that? does copying the files from 720p .zip (in 720p topic) work? or it's only for CM?
[Android] Jimmothy:
Hi, I'm trying to cook for the Desire using rom.zip from 2.10.405.2 sad my base, no matter how simple the tweaks I add my signed zip will not flash. I get verification failed in click work mod. Anyone had any luck making desire roms?

Using ubuntu 10.04 java 1.6.
[Android] BlaY0:
Try disabling verification in ClockworkMod (advanced menu if I recall).
[Android] NilsP:
Fantastic kitchen, been using it for a few versions now with no problems and love it.

I think there was mention of this when I read through the entire post but 1 great addition would be a working folder chooser for when you are working on 2 or more version. Right now I just rename the front of the file name.

Thanks
[Android] Jimmothy:
When I do that it flashes it and it never boots up.
[Android] kendong2:
make that "mkdir -p" and it won't complain if the dir is already there ;)
[Android] grassiekuik:
Did someone even manage to get it running with a non shipped rom? I can't seem to be getting it right.

Is there a way to test roms on some kind of emulator instead of flashing over and over and over again?
[Android] dsixda:
Actually, the script checks to see if that dir is already there first before it attempts to create it :)

ie.

if [ -d system/sd ]
[Android] kendong2:
good aswell ;) sorry, didn't actually look at the script before correcting you :rolleyes:

sadly there is no way to run a hero rom on an emulator afaik... the emulator is more of a g1 i think. might work with a g1 kernel, but since you will probably get a lot of FCs (if it boots up at all) it won't do the job for testing...
[Android] grassiekuik:
Grr :( So how will I ever learn this?
[Android] kendong2:
that's easy ;) by

edit: and what do you mean by non-shipped rom? if you are trying to use it with mcr (for example) that might cause some trouble as it differs from what the kitchen expects. and although you did not say "didn't work", "can't seem to be getting it right" is not better for an error message ;)
[Android] maliiina:
ealier i cooked 2.1 build

error
[Android] grassiekuik:
No you're right about my explicit message i got during flashing. Well i somehow got a rom "working" I was playing a bit with the sensehero rom from stickman. I was planning to get all of sense out of it. So I googled on what i could remove from all the apk's I finally had it booting only it didn't start a launcher at all. When i pressed and hold the home button i could see the recent started apps dialog box. And i could even shut down my phone the normal way. But that was about it.
[Android] dsixda:
What did you remove? Just remove Rosie and all the HTC Widgets... That's what I did. But you probably can't get all the default Android stuff like Calendar without actually compiling the source.
[Android] grassiekuik:
This is pretty much I removed. Maybe a bit more HTC stuff only not the odex files coz they weren't there

rm /system/app/Rosie.apk
rm /system/app/Rosie.odex
rm /system/app/htcbookmarkwidget.apk
rm /system/app/htcbookmarkwidget.odex
rm /system/app/htccalendarwidgets.apk
rm /system/app/htccalendarwidgets.odex
rm /system/app/htccontactwidgets.apk
rm /system/app/htccontactwidgets.odex
rm /system/app/htcmailwidgets.apk
rm /system/app/htcmailwidgets.odex
rm /system/app/htcmsgwidgets.apk
rm /system/app/htcmsgwidgets.odex
rm /system/app/htcsearchwidgets.apk
rm /system/app/htcsearchwidgets.odex
rm /system/app/htcsettingwidgets.apk
rm /system/app/htcsettingwidgets.odex
[Android] dsixda:
Yeah I removed those APKs too. Running great for me. I used the shipped ROM posted on the first page.
[Android] grassiekuik:
From the stock rom or from stickmans sensehero rom?
[Android] dsixda:
Make sure you didn't overwrite the existing update-script. Instead you have to merge them into one.
[Android] dsixda:
Shipped ROM...

This kitchen was not made to cook someone else's custom ROM.. it was made for you to make your own custom ROM from a shipped ROM. ;) (although you could, but it requires more manual work)
[Android] grassiekuik:
Lol I know but it's worth a try. You did an excellent job building this kitchen for n00bs like me. I'll try some more with a shipped rom. It sucks that it isn't possible to emulate them
[Android] dsixda:
What do you want in your ROM that is in the other ROMs? For me, performance-wise, I feel the task killer tweak is all I need (plus removing all the Sense UI stuff).
[Android] grassiekuik:
I don't know really. It's just i want to learn some more about how it works and what i can do with it all. And what I can change. maybe do some graphic tweaks later on. It's much more work than creating a skin for winmo
[Android] dsixda:
I agree with you, WinMo is much more straightforward, but I'm happy with what I have now for my Hero - it does the job for me right now ;)
[Android] grassiekuik:
What are you running atm? Just a plain bald stockrom?
[Android] TheAshMan:
Just want to say you've done some great work producing this kitchen.

I've been working daily on my custom ROM and finally have something that I'm pleased with almost does everything I want it to!

I still can't get the system/etc/init.d support working, I've added:

"start sysinit" after "start a2sd" in my init.rc file

And at the bottom after the 3 lines of ramzswap I have:

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot

Any scripts I have under system/etc/init.d aren't run. I've added some echo's to see if it runs using logcat - but I get no output from any script.

Secondly, do you know the location for the default location of wallpapers? I want to replace the default ones with the Desire ones.

Once again, great work so far. You making this kitchen has made me finally start learning how to produce ROMs. I've donated to show you some appreciation.

Keep up the good work!
[Android] Jimmothy:
Also, thinking about it, I had the same problem trying to cook on gentoo linux.
[Android] dsixda:
Read the FAQ to investigate booting issues.
[Android] deprecate:
~/.bash_profile
[Android] NICEGYPT:
after updating my ubuntu to 10.10 i can't run the menu anymore , everything is ok java running 100% i don't know where is the issue
[Android] dsixda:
You need to be more specific, what do you mean you can't run menu? Be clear about error messages etc.
[Android] NICEGYPT:
open as a text editor, i can't get it to run on terminal
[Android] myn:
Just an FYI,

The current kitchen's busybox version has output coloring enabled. What this means is if you are using a windows command shell and you adb shell and issue commands you will see an output like this:

Any chance you can add one that doesn't have coloring enabled?

Great work BTW. Your tools take all the tedious effort out of rom development :)

drwxrwx--- 1 1000 2001 2048 Nov 27 02:32 ←[1;34mcache←[0m

drwxrwx--x 1 1000 1000 2048 Nov 27 02:32 ←[1;34mdata←[0m

-rw-r--r-- 1 0 0 118 Jan 1 1970 ←[0;0mdefault.prop←[0m

drwxr-xr-x 11 0 0 1340 Nov 27 02:32 ←[1;34mdev←[0m

lrwxrwxrwx 1 0 0 11 Nov 27 02:32 ←[1;36metc←[0m -> ←[1;34

m/system/etc←[0m
[Android] dsixda:
What are you trying to do?? You have to run it from the command prompt, not run it like a shortcut with your mouse. Please read the FAQ.
[Android] dsixda:
The FAQ has something on this, but otherwise I don't know how to enable it in busybox.
[Android] fonix232:
Hm.

In the last version (0.101) I've got some little problems :S

When I try to add busybox, apps2SD, or anything what uses an external shell script, the scripts won't get added to the update-script - what is kinda annoying, as I have to add them manually.

Then, the generated update-script is kinda weird. First, it runs the data/app checker script (the only .sh script what gets added) then copies the contents, and after this, it formats the whole data drive :O

Could you please fix these?

Also great work on the kitchen, I like it very much :D
[Android] pendo:
lol....this thread cracks me up sometimes. Good stuff.

I haven't checked in here for a little while, but a few pages back there were some having problems with sed....I know for me running snow leopard, BSD sed was in /usr/bin....which was located before /usr/local/bin in my path. So you might be running into an issue where even though you have GNUsed in your path, it's not getting called first.
[Android] dsixda:
Thanks for the tip, yeah it is mentioned in the FAQ that you must put the new sed's folder before the current PATH value. I think people are not following the instructions properly. It's hard to diagnose people's sed issues when they say they have read the FAQ, thus I assume they had followed all the instructions correctly.
[Android] dsixda:
I can't fix it because you are not providing details about the ROM, and it works fine for me. Could you be more specific about the ROM you are using..... shipped, custom ROM, nandroid backup... ? If it came with an update-script when you downloaded it then please post it here. Or post the exact link to the ROM. Thank you
[Android] pendo:
Yeah, and you see that command all over the place if you google, but it's easy if you're not paying attention(I know I didn't catch it at first), you have it correct in that link...to PRE path it's

PATH=/your/folder:$PATH

and if you want it added to the end of your path its

PATH=$PATH:/your/folder
[Android] endroidphone:
thx for the answers. i used the Disire HD/Ace Rom as mentioned. yep, i read the portion and found the answer but i just doubted if it's the same error. thx for pointin' out that anyway. i'm just curious wut other software others use for the Desire HD rom cookin'. any idea?