yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
Thanks a lot for confirming this for me. I may modify the kitchen so that wlan.ko is also ported when you copy over a new kernel.

EDIT: Done!
[Android] :
Sorry

Im sorry for being a noob at this, but that is what you built it for. Anyway, so i did all of that and what not, but when i put the signed update.zip folder on my hero and flashed it, it says it is bad, any help please?
[Android] oreddy32:
mytouch 1.2

hey just wanted to know if you could port roms for new mytouch with this kitchen? thanks..
[Android] antz88c:
what did you use, nandroid backup or shipped or cooked ROM? I got that 'bad' error when flashing when i used my nandroid backup (system.img and boot.ing) which dsixda stated that it's not recommended.
[Android] robin04:
I have a problem in Windows.

When I ported from another Rom asks me what 'is my device, select it and tells me:

The rom will be built....
Press enter to continue (i press)
cat: device.cfg: No such file or directory
the kitchen could not detected the rom's device type

why?

(the strange thing is that the file exists but does not seem to recognize cigwin!)
[Android] dsixda:
Can you describe step-by-step what you did from the menu, and what file you used as your source ROM?

Are you using your own custom script? Because the grammar in the script above is definitely not mine ;) Also, please make sure you are using the latest version of the kitchen.
[Android] dsixda:
Can you tell me what is special about the new myTouch compared to other HTC Magic 32As?
[Android] robin04:
Hi dsixda

I do not use custom scripts.

I wrote the code that is output on cygwin, is not a script.

I downloaded the latest version but the error is still there.

quote:

What is your own device's model?

1> HTC Hero
2> nexus one
3> HTC Dream
4> HTC Magic
5> HTC tattoo

Select the number: 1

the Rom will be built for the Hero ....

Press ENTER to continue

cat: device.cfg: No such file or directory (this is the error)

then continues to me in the loop code above
[Android] dsixda:
OK thanks a lot for letting me know, I will check it out.

Also please be aware - as I already said in the setup section - your device may not flash a bootable ROM with Cygwin if you use any option that repacks the boot.img, including ROM porting. This applies to Cygwin only.
[Android] dsixda:
Ok, I am unable to reproduce your problem.

Can you make sure that in your Cygwin you have also downloaded Archive / unzip

I have also uploaded a new version of the kitchen, 0.31, which will have better error handling. So if you see this same error again, it will explain it in detail or it will correct the issue on its own.
[Android] Dormantlemon:
Download links do not work. Can you re-up please? Im really looking forward to this.
[Android] dsixda:
Megaupload is down, but Hotfile is working for me, man.
[Android] dsixda:
Sorry guys, there was an error in the Wireless Tethering script after I made all those changes this morning. It has now been fixed into version 0.32.
[Android] oreddy32:
mytouch 1.2

the new mytouch is suppose to be a hybrid 32a so when you flash roms other than the stock the touchscreen & the headphone jack will not work, or something like that.. im a noob so dont know too much more...
[Android] dsixda:
Ah ok. It doesn't hurt to try... But you must use the "Port ROM" method so that the kernel and drivers of the myTouch get copied over (if your ROM is going to be flashed on the myTouch).
[Android] chromersmith:
MyTouch 1.2 LE Fender

Any ideas when we will have support for the 1.2 Mytouch? just boot loops at this point.
[Android] dsixda:
See my reply above.

Other than that, I can't really do much, as I don't have a Magic. We would need to rely on someone who knows what to do exactly.. but try my advice above first.
[Android] jergud:
download : link does not match

download link does not work... is it possible to re-upload somewhere else ? thanks in advance
[Android] jergud:
few minutes later, download link is ok
[Android] dsixda:
Good news, with version 0.33 (today), I can get the kitchen fully working in Cygwin so that it can flash a ROM on the Nexus One and boot without hanging. Installing Cygwin is MUCH faster than installing the virtual machine + Ubuntu in Windows.

Anyone want to try it with their Hero? Cygwin-cooked ROM wasn't working before on the Hero, and I just sold my Hero so I cannot test. :( Ubuntu is fine though.
[Android] nikitto:
If you use new 115 kitchen, you won't need to add those lines.

Follow these steps:

1 - Set up working folder from ROM

(option 2)

2 - Add root permissions

3 - Add BusyBox

0 - ADVANCED OPTIONS

22 - Convert update-script or updater-script

2 = Convert update-script to updater-script

Back to main menu.

99 - Build ROM from working folder

That's all.
[Android] pokerhiih:
tanks...a will try that
[Android] dsixda:
There's fewer steps than that ;)

Actually, this is all you need to do now:

The conversion will automatically add busybox.
[Android] Hiataby:
Same here!

Why is that? Looks like deodex isn't so good after all?

Thx in advance!
[Android] digkong:
what if it is a flashable zip.. file then how do we add the kernel..

great work..!!!;)
[Android] totalcmdext:
Request for NAND rom for WM6.5 device

It will be good idea to include in the kitchen also devices like HTC HD2 (specific kernels) which is possible to run android via NAND rom.

Maybe some adaptation and a tutorial will be enough as it is very close to the rom with the original android devices.
[Android] dsixda:
That boot folder is going to require a lot of modification to the scripts. I would need time and an HD2 to test.. probably not possible right now due to my situation and marital status ;-) I have no idea how it works - not an expert on these things - so i cannot give a tutorial.
[Android] TMartin:
Unzip it.

10char
[Android] vin255764:
good one :D

Anybody know how to fix this?Or point me to the right direction

http://xdaforums.com/showpost.php?p=11055478&postcount=63
[Android] TMartin:
You don't need to install it that way. You can grab the flashable zip from Amon_RA's thread, rename the *.img of the latest recovery to recovery.img and replace the recovery.img inside the zip with the current img then flash it.
[Android] dsixda:
You need to give the correct path, since your flash_image is not there. You'll probably need to download it first, since it's normally not in a ROM. Funny, I was actually thinking of adding it as an option in the kitchen, but it just may be unnecessary work.
[Android] vin255764:
Found link to that script http://cyanogen-files.carneeki.net/flash_image.zip
[Android] dsixda:
Yeah I know about it, you can easily find it with Google. You also have to set its permissions in the update-script (0755) if you include it in a ROM. /system/xbin is a good place to put it.
[Android] vin255764:
Thats why I had permission denial in terminal emulator

If Im using update-script, this should do the trick,right?

set_perm 0 0 0755 SYSTEM:xbin/flash_image
[Android] rs125:
With the latest kitchen v.0.115 I can not flash the .zip file. By v.0.114 it ... why?

I have a HTC Ace ...

Thanks
[Android] dsixda:
You cannot flash it? Why, you hurt your hand? ;) Computer is broken? Please be specific and give details, "cannot flash" doesn't help me understand the problem.
[Android] Flecky:
Hello dsixda.

Thanks for fixing the problem with updater-script, now flashing the rom and it works well.

But I have a problem adding new apks, I fail to appear in the rom installed.

I tested with the official 1.32 rom with a rom cooked taken from this forum.

I get the information from the previous rom I had installed without apks new app folder.

Got any thoughts on this?

Thanks for everything.

Flecky.

PD: Sorry for the translation of google.
[Android] dsixda:
I think so. Why don't you try it out?
[Android] dsixda:
No I don't know. Ask a dev in your device forum.

Or do a logcat while it boots up.
[Android] alvin136666:
dear dsixda

dear dsixda,thanks for your kitchen,i used your newest kitchen to cook my desire hd rom,everything go well in the prosess,when i flash the cooked rom,it flash very fast,say install the room success,then the device start,but it was still the old rom that i was used,i do not know why,the step of my cook is

1 - Set up working folder from ROM

(option 2)

2 - Add root permissions

99 - Build ROM from working folder

Say 'y' to the updater-script option.

please help me,thank you!
[Android] TMartin:
I think it should but I replied with a much easier way, that doesn't even use flash_image
[Android] dsixda:
I have run out of answers, sorry. I don't have the device so I cannot help much anymore.

I am not much of an expert on these things.. perhaps the system partition needs to be mounted a different way before flashing it.

Like I said earlier, ask a dev in your forum. Or do a logcat after flashing. Thx
[Android] alvin136666:
thank you for your help i will try to fix it,thanks
[Android] rs125:
Yes I'm sorry, the recovery with the pack generated by 0.115 no flash ... analyzes the zip and skip the flash, you know why?

I'm currently working with the 0.114 just for this!
[Android] dsixda:
0.114 and 0.115 are the same for flashing recovery. In 0.114 the recovery script was removed to prevent accidental reflashing of the stock recovery. View the release notes.

I could add a prompt to the script, asking the user if they want to remove it.
[Android] dsixda:
Kitchen 0.116 is now out.. Please read the Release Notes in Post #2 for details. Enjoy!
[Android] Alex-V:
Big thanks for new version and the work with this... :) please don´t give up this kitchen (if you have a bit time for this)

Big Thanks...with kind regards...Alex
[Android] lovethyEVO:
Agreed. You have been making great progress over these past few weeks. It is not unappreciated dsixda.
[Android] TMartin:
For dreading the switch to edify for awhile now, you are cranking out these kitchens like a MAD MAN!! Thanks for the hard work and I can't wait to see what you come up with next.
[Android] itje:
Tried latest kitchen with a stock desire hd rom, and added root, busybox, zipaligned and deodexed.

rom builds, converts updatescript

wiping data etc, rom is flashing

then I have same rom as I came from (android revolution)

Anyone have any idea, im sure some have this fixed as most desire hd chefs use this kitchen :-)
[Android] PapaDocta:
@itje

i had the same problem and it's in the updater-script ... try not to convert it to the new format or use one off an the existing rom and modify it to suit your rom
[Android] pokerhiih:
Same here ... if you use "updatescript" kitchen just writing system ... but not boot.If using "updaterscript" it writes nada

Had the same problem now for sametime
[Android] PapaDocta:
from LeeDroid.. regarding the Desire HD updater-script

"

You need to be mounting EMMC as ext3 and pointing to the specific mount point..

Here is how /system is mounted

mount("ext3", "EMMC", "/dev/block/mmcblk0p25", "/system");

If you grab android system info from the market, all mount points are listed "
[Android] emiliano7:
I Have a problem:

when Convert update to updater-script with HTC BUZZ ROM....After the Flash...the buzz Freez to Htc Logo......

I used 0.116

Scusmy for my Bad english....:)
[Android] dsixda:
This post will probably help you guys with Desire HD. Thanks Mike.
[Android] dsixda:
As I've said on the download page, please read the FAQ first for troubleshooting.
[Android] itje:
Sorry for the noobish question then (Yea, me, im a noob...long time since I was that for the first time :-p )

This goes into the updatescript thingy (:o:p)

or is it a task I do on my desire hd?

format("ext3", "EMMC", "/dev/block/mmcblk0p25");
format("ext3", "EMMC", "/dev/block/mmcblk0p26");

then you mount:

mount("ext3", "EMMC", "/dev/block/mmcblk0p25", "/system");
mount("ext3", "EMMC", "/dev/block/mmcblk0p26", "/data");
[Android] dsixda:
Hi,

When you are working on your Desire HD ROM, the kitchen is using an update-script.

When you decide to build it (option 99), it will ask you if you want to convert it to updater-script. Say yes.

After it converts, it will have another prompt asking if you want to proceed. Before you proceed, open up the new updater-script and edit the parts that refer to the formatting and mounting of the 'system' and 'data (or userdata)' partitions --- you must modify those parts manually with a text editor, based on the lines in the post that you quoted below.

EDIT: Just to make it clear again (because people are still doing it wrong) -- You have to REPLACE those format/mount lines, so don't keep the old lines!

Proceed and build... and then flash! Good luck.

------

For other devices having the same problem: follow the advice that PapaDocta gave - if you grab 'Android System Info' from the Market, all mount points are listed (under System tab -> Mount Points).

(NOTE: Referring to the quote below, an 'ext3' partition requires 'EMMC' ; but if your device uses 'yaffs2' then you have to use 'MTD' instead.)
[Android] totalcmdext:
Request for NAND CWM build for HD2

Hi,

Please could you try to deliver and adaptation in order the compile result to be possible flash with CWM (or DAF) which is more close your project but for HD2 device.

The only difference is the boot image that in most of case is default.

I could support you and help you in order to include the HD2 device.
[Android] dsixda:
Please search the thread - I answered it yesterday:

http://xdaforums.com/showpost.php?p=11048524&postcount=3186

If you can make a modified version of the kitchen for HD2, then that would be great for HD2 users. There are already projects like this, e.g. for the Samsung Galaxy S.
[Android] dsixda:
I hope so!

Note that your boot partition didn't require any modification.. I wonder if it does? Only way to tell is to flash and see...

EDIT: You didn't remove the mount for the 'data':
[Android] totalcmdext:
I have seen your reply but i didn't know if we could use your release and modify it for HD2 NAND cooking.
[Android] itje:
Thx I just noticed that one :-)

Ill do a flash and report back :-)
[Android] itje:
Got a fully working rom for my desire hd, thx for help.

Did some research on other roms update script and "figured out" how it works

I will post what I did when I have done this a few times :-)

cheers
[Android] Lucce96:
I can't get this to work!

I have installed JavaJDK and cygwin.

Then i have to extract the kitchen zip i the C -> cygwin -> home, right?

When i click on the cygwin.exe, it just pop up in a millisecond and then close again.

What am i going wrong?
[Android] dsixda:
You mean cygwin.bat?? there is no cygwin.exe.

Open up your cygwin.bat with a text editor to see what commands it uses. Then try executing those commands manually from a DOS prompt (type 'cmd' from Start-->Run).
[Android] nikitto:
Thanks, we're going to wait for your post.
[Android] Lucce96:
Yes, of course!:)

I will test it!
[Android] Lucce96:
No it won't open..

Where exactly am I going to put the Kitchen files??

Or should the cygwin.bat open without those files?
[Android] dsixda:
Ok but how does "it won't open" help me determine your problem - What were the contents of the .bat file? Please be specific and post the output. Sorry, I can't really help further... The kitchen has nothing to do with Cygwin opening.
[Android] dsixda:
Just let me know if you complete a modified kitchen, and link back to my kitchen from your release thread. I can also link yours from the first page.
[Android] dscott23:
As an example, I put the cygwin files in C:\cygwin, and the cygwin packages are in C:\cygwin_packages. I extracted the Kitchen files to C:\cygwin\home\[my name]\Kitchen. So when I want to run the kitchen, I open the Cygwin Bash Shell, and type:

cd Kitchen (the shell initially opens in my Home directory, so I move into the Kitchen directory) and then:

./menu (to open the kitchen)

Hope that helps.
[Android] Lucce96:
I downloaded cygwin from the link in the second post ( i think ). And installed it successfully. It placed a shortcut on the startpage and in the startmenu. I placed the files in C:\cygwin and the packages in some map in my docs.

As I said it just opens for less than a half second and then it close again and no more happends.
[Android] dscott23:
I would suggest opening a command prompt, go to C:\cygwin, and run cygwin.bat manually. Any errors will show in the command window.
[Android] Lucce96:
Finaly got this to work!

I reinstalled it and then i saw that the "hide obsolete files" was selected.

I installed those files to and then it worked!
[Android] dsixda:
Kitchen version 0.117 is now out. Basically a lot of changes made for the updater-script stuff.
[Android] aamikam:
i know most people dont care... but any reason not to update busybox?

again... not really asking u to update it or complaining... just wondering if there is any special reason.
[Android] dsixda:
Don't feel like checking every day for every version of every tool in the kitchen. Busybox works fine as is.
[Android] nikitto:
Thanks man. Let's go to try it.
[Android] dsixda:
Sorry guys, I made a mistake in the updater-script-to-update-script converter routine, so that certain updater-scripts won't convert correctly. I've uploaded a corrected version on the Mediafire mirror link. However, the Grdlock.net server is down right now so I cannot upload the fixed version there.

In the meantime, just download 0.117 from the Mediafire.com mirror link that is on the download page.
[Android] anryl:
could u change the scripts and rename boot.img-kernel to zImage for better kernel inserting :D
[Android] dsixda:
I could, but why not rename your zImage to boot.img-kernel for better kernel inserting? ;)
[Android] dsixda:
Fixed 0.117 is back up on grdlock.net server.
[Android] erawtik:
Unpacking sun-java6-jre (from sun-java6-jre_6.22-1_all.deb) ...

Selecting previously deselected package sun-java6-bin.

Unpacking sun-java6-bin (from sun-java6-bin_6.22-1_i386.deb) ...

sun-dlj-v1-1 license has already been accepted

dpkg: dependency problems prevent configuration of sun-java6-jre:

sun-java6-jre depends on java-common (>= 0.24); however:

Package java-common is not installed.

dpkg: error processing sun-java6-jre (--install):

dependency problems - leaving unconfigured

dpkg: dependency problems prevent configuration of sun-java6-bin:

sun-java6-bin depends on sun-java6-jre (>= 6.22-1); however:

Package sun-java6-jre is not configured yet.

sun-java6-bin depends on unixodbc; however:

Package unixodbc is not installed.

dpkg: error processing sun-java6-bin (--install):

dependency problems - leaving unconfigured

Processing triggers for shared-mime-info ...

Processing triggers for desktop-file-utils ...

Errors were encountered while processing:

sun-java6-jre

sun-java6-bin

This is what i get while tring to install java any help?
[Android] dsixda:
Have you read the error message to see which packages to install as dependencies (e.g. unixodbc)?

Try to follow every step in the FAQ regarding how to install Java. It should work eventually. Try the Java 5 method that I mentioned there.
[Android] dsixda:
Using the name "zImage" may be a good idea, because a lot of kernels use that naming convention. I have already adjusted all the relevant scripts to use 'zImage', for the next update of the kitchen. If anyone has an issue with me renaming boot.img-kernel to zImage, let me know! (BTW I'll also need to update the references to boot.img-kernel in the FAQ!!)
[Android] dsixda:
After reviewing the file format again, this may not be too hard.

When unzipping an HD2 ROM into a new working folder, the kitchen could automatically convert the ROM's 'boot' folder into a boot.img so that all the kitchen operations can work without problem. Then when the ROM is built it can recreate that boot folder from the boot.img.

Probably easier said than done, but I could give it a shot this week! I would need testers though.
[Android] totalcmdext:
I can make any test that you are need.
[Android] dsixda:
Is there an easy way to detect that the ROM is intended for NAND-based devices? The easy way is to check build.prop for "htcleo", in the HD2 case, but I want a generic method for all devices concerned.

I mean it's obvious to tell it's a NAND ROM if it has a 'boot' folder, but if the ROM is instead in the system.img+boot.img format then how would I know?
[Android] theintelligent:
Hi,

One thing left only, run_program(installbusybox) don't work for me.

updater-script attached.

Nothing in the logs either.
[Android] dsixda:
Nothing in the recovery.log (at the line where it runs installbusybox) after you flash the ROM?
[Android] theintelligent:
Yes, just printing Installing busybox, no error.
[Android] dsixda:
Does your ROM have system/xbin/busybox?

Does it have /system/bin/chmod in the ROM or in the updater-script? (EDIT: Nevermind, chmod is in the updater-script)
[Android] theintelligent:
Yes my ROM has system/xbin/busybox

and no there is no chmod in system/bin folder but the updater-script has the below two permissions command.

set_perm_recursive(0, 0, 0755, 0555, "/system/xbin");

set_perm(0, 0, 06755, "/system/xbin/busybox");
[Android] dsixda:
You have a symlink to chmod in your updater-script. So it looks fine. Anyways I have no more ideas to help.
[Android] theintelligent:
If i copy the chmod to system/bin, will this help?
[Android] dsixda:
Where are you going to get chmod binary from??
[Android] theintelligent:
I will install busybox manuall busybox --install -s /system/xbin and then extract the chmod binary from there?
[Android] anryl:
:D okay got .114 moded for kernel only for now gona test .117 koockin froyo cheers
[Android] dsixda:
I don't know, why don't you just try it.
[Android] dsixda:
Ok guys, some more updates... I have 0.118 Kitchen now uploaded.

Support for NAND-based ROMs for Windows Mobile devices has been included. Please read the Release Notes for this and more details. Enjoy..
[Android] shree.cse:
It just looks Amazing! I have HD2, can I use this to build on my own. I saw that it supports HD2 but untested. Anyway, I am going to start working now! Downloading...

Can you please assist me If I stuck at some place making this happen!

Thanks a lot!
[Android] totalcmdext:
I would like to thank you for the new option for NAND cooking!!!!

I have tried and i could confirm that it is working!!!!!

So, i hope in the next versions to fix any bug if existing.....
[Android] dsixda:
Sure, just make sure to read the FAQ first and search when necessary.
[Android] dsixda:
Cool :) I hope other devices are possibly supported with this method. I notice other NAND ROMs use .NBH files instead of .ZIP though.
[Android] totalcmdext:
It will be greatfully if you could adapt you kitchen to cook pure NAND rom (system.img and boot.img)
[Android] dsixda:
Regarding system.img, I have already explained it a few times in this thread:

It would be close to impossible to make one in a kitchen because a system.img does not have an updater-script, and thus all the file permissions, symlinks, scripts etc. would need to already be set in the ROM. I don't know how to set Android file operations within an Android ROM while using Cygwin or Linux. Plus you'd probably need to execute all the commands in the existing updater-script to your ROM while on your *PC* before converting it to a system.img. Forget it ;)
[Android] dsixda:
Oh wait.. what do you mean busybox wasn't installed? You had told me there was no error message... Your boot.img in the updater-script would not have been flashed if busybox was not installed. ??

P.S. Titanium Backup uses its own busybox, usually it's not the one in the ROM.
[Android] shree.cse:
I got a problem. Done with everything, created .zip file and after that I copied to my SD card. Ready to flash, using cwm I tried to install the zip but it says that the file doesn't have update-script and failed to flash.

One more doubt, I modified a Desire based Custom Rom with HD2 kernel, initrd.gz in boot folder and modules. Did I need anything else to do flash my new build on my HD2?

THANK YOU
[Android] shree.cse:
First while importing the Rom the Update script must be converted to Updater script and at the end while creating the zip, we need to convert Updater script to Update script.

Am I correct? Have I done anything wrong? Please correct me...!