yashsingh1/xdaforums huggingface dataset:
[Android] loveboatcaptain:
hi dsixda,

i have good news

your kitchen is working for the HTC Desire S (aka HTC Saga) very well.

just cooked and flashed the first rom cooked with it.

there are two little errors which have to be fixed in the updater-script.

HCDR.Jacob helped me to find out whats going wrong.

format("ext4", "EMMC", "/dev/block/mmcblk0p25");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
delete("/data/local");
package_extract_file("check_data_app", "/tmp/check_data_app");
set_perm(0, 0, 0777, "/tmp/check_data_app");
run_program("/tmp/check_data_app");
mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/data");
package_extract_dir("data", "/data");

error was that format espacted 2 args not 3. but for desire s i needed 3 args to format system correctly, since the desire s is having ext4 on system and cache.

i also had trubbles with the updater-binary. after replacing it with the one from CM7nightly for ACE everything was flashed correctly without errors in the clockworkmod recovery.

another problem was the boot.img

i had to replace the boot.img comes out of the kitchen with the original one to let the device boot. think there went something wrong.

for that problem with the boot.img please contect me via PM cause i had to rebuild the rom step by step to post you the correct errors.

hope you can fix this and add full support to this device with this informations.
[Android] looktall:
common sense?

you made this for newbies.

i believe the two terms to be mutually exclusive. :p
[Android] dsixda:
New to reading does not mean new to cooking.

I had some other guy who said he was a "biiiig" newb and didn't want to read.

Anyways, no point arguing semantics.. maybe I should remove that Newbie phrase because people get so uptight over it :P

Move on and enjoy...
[Android] alan090:
Re: [KITCHEN][APRIL 9 '10] HTC Android Basic Kitchen, v0.40 [Linux / Mac / Cygwin]

Love using this to port roms

When i add apps to the rom they dont show up though
[Android] dsixda:
Add them to the working folder of the ROM that gets built, not the first ROM in the porting step.
[Android] svprm:
Thanks man for new version.

Working well on Tattoo.
[Android] dsixda:
I have uploaded a minor update (0.41) to the kitchen, which includes a bug fix for porting.
[Android] looktall:
a question about the latest version.

why are magic owners no longer asked about the board type?

does the kitchen make the rom compatible for both types or something?
[Android] dsixda:
Basically it asked you before so that it could determine the base address for your Magic. But now we can automatically figure it out just by reading the boot.img.
[Android] alan090:
i tried adding it the the system folder and the data folder under apps but it didnt show up when i packed and signed the rom :( i just add the apk to the app folder where all the other apk are stored right?
[Android] dsixda:
I'm not sure what you did, but you need to create the working folder (eg. WORKING_*) first. Copy your apk files to the system/app folder of the working folder, or under data/app if it was enabled in the ROM.
[Android] :
For some reason when I do any of the following I am unable to port a few ROMs from 32B G1 Dream to the 32A Magic new radio 6.35:

(1) Use your ROM Kitchen alone to port (I don't think your Kitchen will port to the new radio 6.35 for 32A so this option is out)

(2) Use the MAGIC Port tool here alone http://faruq.yandao.com/magicport/indexBETA.php

(3) Use your ROM Kitchen combined with the MAGIC Port tool (I use your ROM for cooking and the MAGIC Port to generate the new boot.img, wlan.ko, build.prop, etc files which I then copy into the working folder to replace the originals)

I know it is not user error because I am able to port numerous other ROMs using the exact same methods.

I am convinced there is something in these orignal 32B ROMs (perhaps the kernels and/or other files are too customized) that prevent them from a simple port.

ROMs that I can't port include SuperCSDI (donut) and now XxKOLOHExX's new beta ROM (eclair).

It is interesting to note that I am able to repeatedly port XxKOLOHExX's 2.4 stable ROM which also demonstrates my method is ok.

Have you encountered anything similar - that is, ROMs that can't be ported?
[Android] dsixda:
Do you mean that you are getting it stuck at the boot screen?

What happens when you do 'adb logcat' while it reboots?
[Android] :
Yup, only when trying to port some ROMs. My method / approach / steps for porting do not change and work for some but not for others.
[Android] dsixda:
Do certain ROMs contain /system/modules/modules.cramfs? I think this also needs to be copied over when porting. My kitchen doesn't do that right now.

Also, is there anything the new port tool do that my kitchen doesn't? I want to make sure my Port ROM method covers everything so that it does it properly.

Let me know what you get with "adb logcat" while it starts booting.
[Android] :
Not the ones I am working with.

Not that I know of although this MAGIC Port tool allows the user to select which 32A kernel they wish to use. Then it basically creates an update.zip to flash over the original to port it to the 32A device. I used it at times with your kitchen because I can easily apply the best available kernel for the 32A new radio by Sanpei.

E/logwrapper( 50): executing /system/xbin/busybox failed: No such file or directory

I/logwrapper( 41): /system/xbin/busybox terminated by exit(255)

I should have done this to begin with :)

For some reason the /system/xbin folder is empty for this ported ROM I have in your working folder.

This may be a dumb question but are the contents in this folder ROM specific and customized heavily or are they more or less generic? I am going to do a quick test where I copy and paste in files into this folder from the most similar and successfully ported ROM I have.
[Android] dsixda:
That's weird.. if these ROMs are already rooted to begin with, I would assume they already have busybox. Is there a busybox somewhere else in the working folder (also, use Option 14 to unpack the kernel and check BOOT-EXTRACTED too)?
[Android] dsixda:
Hmm.. check this, this guy had the same error as you (I googled) :

http://forum.cyanogenmod.com/index.php?/topic/949-solved-my-experiences-upgrading-from-5041-to-5051/

I think apps2sd plays a part here?
[Android] :
No busybox anywhere to be found.

And when I tried my quick fix I got the following error during first boot:

E/logwrapper( 48): executing /system/xbin/busybox failed: Permission denied

I/logwrapper( 41): /system/xbin/busybox terminated by exit(255)
[Android] dsixda:
If you get a permission denied message, it means the read/write permissions were not set.

Make sure your update-script file has this:

set_perm 0 0 04755 SYSTEM:xbin/busybox

The '7' sets it to read + write + execute (4 + 2 + 1)

BTW, I hope we can figure this out, because other people have reported this issue as well with this kitchen. But it happens with other non-kitchen custom roms as well!
[Android] dsixda:
Ok, I noticed something,

The SuperEclair beta ROM has a system/init.rc file - empty file.

The SuperEclair 2.4 ROM has no init.rc under system.

There is also an init.rc in most ROMs' ramdisk folder of the boot.img. I opened the init.rc for the beta ROM, and I noticed it has a reference to system/xbin/busybox even though it does not exist!

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

I don't know if this is useful info.. but just pointing it out.
[Android] dsixda:
OK I am on vacation, will look at it later.
[Android] dsixda:
Looks like you manually entered the mount points above and didn't change the update-binary ..

That's not an error with the kitchen, because it would have picked out the correct update-binary automatically, based on the number of args in the format command. But the kitchen doesn't currently have Desire S support.
[Android] zookafg3:
Power options

I got my first run at the kitchen today.

I'm using SuperSonic_GB_Sprint_WWE_4.12.651.1 from the leak test, and this thing is fast, there is a few Roms out using it already, but now I have mine with a2sd. :D

My question is: how to add power options to the power menu, like reboot to recovery? :confused: :confused:

I been searching for a while and found lots of threads, but none to the HTC EVO 4G and I don't want a widget or a market app, I would like to add it to the power options.

I installed Ubuntu 10.10 full version on my laptop, so if anyone has a link or any kind of help in how to do it, I thank you in advance.
[Android] Droidzone:
That's kind of out of scope of this thread..

However having worked on the Desire for the similiar task, I can give a few pointers..

Power options are a patch of system files, done after reverse engineering it. For the Desire, the file is android-policy.jar. Disassembling it (apktool/apkmanager-later preferred), can give you smali text files which are disassembled java code, which have to be manually patched to add this. I suggest that for starters, you could get this file from a patched rom, compare all the smali (Use P4Merge/Meld) and see for yourself the actual changes..
[Android] :
I really love this kitchen but I have a few questions about porting roms that I think can be answered here with good answers :D

1. Is porting a MDPI rom to another MDPI device easier?

2. IF then answer to #1 is yes, then is porting a rom from a device with similar specs to the device I'm trying to port the rom to easier?

3. After following the port instructions (option 19) for trying to port a HTC Legend rom to a HTC Hero CDMA,

I JUST KNOW

there is more that has to be done to the new working folder with the ported rom right? Do I have to move the /system/lib files from the original devices working rom? What are all the possible files that would need to be moved in order to get it booting?

4. Also should I swap the kernels out for the ported rom with a working kernel for the HTC Hero? The ported rom's kernel work's on the legend but do I need to swap it with a kernel from the Hero so that it will boot?

5. Does the build.prop affect weather or not the device will boot? If it does I'm guessing I should replace all the similar string's values between my working rom and the rom I want to port's build.prop, correct?

Thanks for answering and many thanks will be given to the one who answers. :D
[Android] zookafg3:
Thank you.

I'll try it later.
[Android] Spz0:
Hey m8. Im having an issue with the kitchen.

Im on a Kyocera M6000.

Im using my stock system.img and boot.img also.

I extracted all and repacked all, without editing anything, and I get stuck in BL (logcat shows: BAD EGL errors) when I flash it through cwm.

I suspected our boot.img.

So,, I used your advanced option to unpack/repack the boot image.

Our boot has a 4096 offset, and it seemingly unpacks fine (not much knowledge on boot images, but most the folders are empty [system, sys, dev, etc...]), but when I repack the boot image, it loses almost 2Mb in size (goes from 4096Kb to 2976KB).

Im sure that is what is causing the boot loop.

Im basically trying to edit just a few things in our stock ROM, and repack it with a good zip so I can flash it via cwm.

I've even tried removing the boot.img from the zip and reflecting changes in the update script so it just flashes /system, still nogo (same EGL errors).

Any clues? Im all out of ideas here. =\

Thanks in advance for ur help, and great job on this app!! :)

**edit: Upon recompiling the boot image, the cmdline reads

mem=[B]213M[/B] console=ttyMSM2,115200n8 androidboot.hardware=qcom

but manually checking the cmdline reads:

mem=[B]215M[/B] console=ttyMSM2,115200n8 androidboot.hardware=qcom

Dont know if thats any help, but I thought it interesting.
[Android] JGW310:
hellppppppppp

when i try and start the kitchen, it tells me i have the wrong version of sed installed, but i dont!!! i am on Mac.... PLEASE HELP!!!
[Android] freak69ize:
I tried to enable usb ports for virtual box last night by using some video on youtube.. now linux doesnt work.. ive tried unchecking the boxes in the pic but to no avail. Any suggestions anyone? thanks

View attachment 577156
[Android] tommytomatoe:
You 100% sure you installed this version of sed? It is important you do so. I have a mac (kind of), so if you got questions let me know. But I would recommend doing lots of reading before diving into this :-)
[Android] dsixda:
Version 0.158 is now up. Please see Release Notes for details.
[Android] sabianadmin:
Seems as though the Kitchen is no longer working with the latest version of Sed installed on Mac OS (4.2.1)
[Android] lovethyEVO:
I thought you were on vacation? Take a break man. Really, you do so much that you deserve it.
[Android] Droidzone:
Same thoughts over here!

That was an unrequested wish. till now, I used a script to rename up update-script and updater back and forth just for this. Thank you. :)

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Android] JGW310:
most definitely installed that version!!!

any suggestions? :|

also, im kinda fed up with all of this, if i cant get this to work, i am going to write my own ROM.... is there a thread that anyone knows of that will give me some pointers?
[Android] tommytomatoe:
Mmm. I don't get you exactly. This kitchen is to aid you in writing your own rom. It is the ultimate goal regardless of whether or not you get this working right? The op has several good links to understand building your own rom. You can also look through the chef central threads. There are lots of goodies to learn from there. :-)
[Android] JGW310:
nevermind what i said, i was just being an idiot :|

any suggestions on how to get the kitchen to work properly?

or i could just go to my windows and try it on there
[Android] klquicksall:
Great tool. I was able to cook my rom from the ruu.exe. it flashed everything is good. The only thing is I had to manually enter the apn settings after I flashed the rom. I searched for this but couldn't find it. Is there a place in the rom where I can enter apn settings before I pack the rom up? I appreciate any advice I receive.
[Android] Droidzone:
Varies from os to os, and I believe from device to device. For the desire, it is /system/etc/apns-conf.xml

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Android] klquicksall:
Thanks this will save a lot of time and effort.
[Android] Droidzone:
The kitchen is fastest and best on linux. It works pretty well on windows too if you install it properly

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Android] klquicksall:
Worked perfectly thanks
[Android] vido.ardes:
First of all, massive thanks for this awesome tool!

Is there anything I can give to you to help with compatibility with the Incredible S? I have been using the kitchen, but I have to manually replace the updater-script everytime as the auto generated one seems to fail, and I have never used the newer updater-script before so I don't know how to modify it (for instance, add /data/app functionality). Any pointers would be a big help!
[Android] Droidzone:
You can help dsixda by including copies of your script, the failing script, and your build.prop

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Android] Hawkysoft:
Could you please at support for the Incredible S as well?

if you need any information you can pm me
[Android] dsixda:
Paste the contents of the "mount" command here, using the Terminal app.

Also include the build.prop.
[Android] dsixda:
Yes people have ported with this kitchen.

I don't know much about porting; everything I know is in the kitchen. You'll have a lot of trouble porting ROMs with different resolutions, of course, unless you want to spend hours converting every single bitmap to new resolution.

Also kifno - please stop posting the same question three times. Someone would have eventually replied, or if they don't know they won't reply. Please refer to Forum Rules in regards to double posts.
[Android] dsixda:
What do you mean? The outcome is still the same as before - it will complain about missing update-script if it's not there.
[Android] Droidzone:
It will? Sorry..guess I misunderstood the release notes. I am away from my pc and didn't get a chance to update..

Swyped with my Starburst based Desire. Please ignore any typos or grammos.
[Android] vido.ardes:
For the Incredible S, here is the paste bin for mount:http://pastebin.com/RXq9K0JL

and I have attached the build.prop. Thanks very much!
[Android] dsixda:
Thanks..

Where's the build.prop though?

EDIT: Nevermind, the device is the 'vivo'.

Ok, can you try this....

Open the following two files and replace the occurrences of 'saga' with 'vivo' and then try to create your ROM:

/scripts/adjust_mnt

/scripts/update_script_should_convert_back
[Android] RolandCruise:
I'm having an error while building the rom during the zipalign process...I'm on ubuntu 64 and I have the ia32-libs package already installed.

Am I missing something?
[Android] dsixda:
You need to be specific, what's the error?
[Android] mskip:
You cant work out whats wrong from that detailed description??

Try using 'The Force' :p

Mark.
[Android] dsixda:
For Incredible S users, if you get assert errors when flashing the boot.img then try this:

package_extract_file("boot.img", "/dev/block/mmcblk0p22");

Let me know what happens ...a number of people had requested support for this device and I haven't had any feedback yet.
[Android] RolandCruise:
This is the error:

Unable to open './system/app/.fr-SVntll/system/app/newHTC_IME.apk' as zip archive
Error: Unable to zipalign, aborting
If you are using 64-bit Linux, ensure you installed package ia32-libs

Cancelling build

Press Enter to continue

It works if I say "No" to "zipalignment".
[Android] vido.ardes:
The change produce a better looking script, I am just nandroiding now so I can try flashing the update
[Android] RolandCruise:
Because of this faq I thought the error could be a known one, that's why I posted quickly and without any care for a detailed description.

Anyway, dsixda could have used "The Force" to know I had a problem without the need of my post... :D :p
[Android] dsixda:
Why do have a system/app folder inside of another system/app folder??
[Android] dsixda:
No, I need as mich details as possible. I can't just assume.
[Android] dsixda:
What change?

Btw, make sure you dump the recovery log right after flashing (before you reboot), in case there are errors that were not displayed during the flash.
[Android] dsixda:
I don't know.. never heard of this device and it's not supported here.

The difference in size in the boot.img shouldn't be a problem. Someone mentioned this before in this thread.. I think the extra bytes are just zeros being padded at the end. As long as the stuff can be extracted and rebuilt successfully it should be fine.

Also, guys.. as I said yesterday to someone else, please don't bump or repost your posts.. I don't want to be obligated to replying to every single post that I don't have an answer for. Refer to Forum Rules regarding reposting.
[Android] RolandCruise:
uhm...yes, I asked this to myself too when I saw this folder inside the .zip package in the output folder...

I don't know where it comes from...it was a hidden folder, that's why I didn't see it inside the working folder before building the rom...

Anyway, this folder was the problem, I deleted it and now zipaligning is working :)

Thanks a alot for your help!

And sorry for the too quick post I wrote yesterday ;)
[Android] dsixda:
Roland - are you modifying an existing zip file or was this a ROM you created yourself from a shipped ROM?
[Android] vido.ardes:
Just an update on the IS front, after I made the changes you suggested the zip flashed but the system just hanged at the boot splash so I don't know if the issue is in the Script or in the ROM, I will try replacing the script with on I know works and see what happens
[Android] RolandCruise:
I made some small modifications to skink's clean desire rom, like changing the kernel to tytung's r8 and symlinking the cache partition to /data/cache to be able to use a smaller cache partition and have more room for applications.

I'd like to learn (if I'll have the time...), so I'm starting from simple and small modifications.

...And your kitchen is great! ;)
[Android] dsixda:
Check the recovery log right after you flash the bad ROM.
[Android] :
Sorry, about that I was just curious. I get in a bit of a rush when i get excited about things :D But yeah I'm porting from a phone with the same resolution as my phone. Just it wont' but but if anyone has successfully ported a rom with this kitchen and is reading this please pm me somethings you did to get it working.
[Android] dsixda:
What do you mean by "it won't"? You need to be specific and give details. I have given a lot of info in the FAQ, eg. the recovery log and logcat.

Also this thread is for sharing information and tips; I would encourage people to post them here, not in private message. If you solve something then please let us know, not just use this thread to fix one's own problems and then leave. Thanks
[Android] klquicksall:
This is one of the best threads on xda. Ive learned so much by using this tool. I can say it works much better for me using ubuntu over a virtual machine. Thanks for your hard work.
[Android] :
:D I the cons of typing to fast , but I meant it won't boot into the phone. It reboots at the splash screen. Okay please quote me and post here if you have successfully ported a rom using dsixda's kitchen. I'm sure it'd be helpful to myself and many others as tips for things to try when porting a rom with this kitchen. I'm going to keep playing around with the ported rom's files and my working rom's files to see what needs to be deleted/added/replaced to get it to boot :D So, of course dsixda, if I figure out some way to get it to boot I'll surely be sharing that info :D

XDA is a place of sharing your work, learning and teaching others :D I plan on doing all three as long as I have an android :D
[Android] dsixda:
I've added a new update for the kitchen, 0.159, to support the Incredible S. Nothing else has changed.
[Android] JGW310:
i keep getting the error where it wont find the java6 stuff!!!! i am running a virtual machine with ubuntu, helppp!!!!
[Android] dsixda:
Again, you need to be specific and give details. Just copy and paste what u did.
[Android] dsixda:
So did it work?? I see your ROM up there..
[Android] JGW310:
nevermind again........... will post if i run into any more problems, i figured this one out!!

could i potentially set up an ubuntu machine and do this on a mac if i do it that way????????????????????????????????????????????????

i have done everything correctly (according to the tutorial) and when i type ./menu, it says NO SUCH FILE OR DIRECTORY!!!!!!!!!! HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android] :
I second that dsixda :D A SCRIPT REPLACEMENT?!?!??! If that was the trick, then WOW!!!! :D Please do tell if it was :D
[Android] JGW310:
could i potentially set up an ubuntu machine and do this on a mac if i do it that way??????????????????????????????????????????????? ?

i have done everything correctly (according to the tutorial) and when i type ./menu, it says NO SUCH FILE OR DIRECTORY!!!!!!!!!! HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android] vido.ardes:
Yes replacing the script with one I wrote manually worked, I was going to try pulling the logs from the auto generated script to see where the problem was, but as you have updated I will try the new one out first

EDIT: The new kitchen works great, no changes required! Thanks very much, now to try the porting tools...
[Android] :
Awesome dude I'll give that a go and then work on the ported rom's drivers and issues :D

If it works i'll report back. Will try this after work
[Android] vido.ardes:
I tried porting CM7 but I just kept getting an obscure error about "- exec '/system/bin/sh' failed: No such file or directory (2) -", haven't worked out what is causing it yet. I tried replacing the kernel with a zImage from the stock Boot.img, still no dice :(