yashsingh1/xdaforums huggingface dataset:
[Android] TMartin:
Mirror

10char
[Android] Spike_M:
sure i wait for new version . tnx for your hard work and share it with us

this mirror is filter too!!!

if you can , when the new version (0.137) is ready put it in rapidshare or mediafire

tnx dude
[Android] TMartin:
Will going through a circumventor work?? Go here then copy my link into on the url boxes.
[Android] Spike_M:
no it doesnt work !
[Android] dsixda:
Try now:

http://android.grdlock.net//index.p...irectory=ROM Kitchens/dsixda Android Kitchen&
[Android] dsixda:
Ok, fixed in version 0.137, just upload now!

If anyone can provide mirror, that will be great.. I have to go out.

EDIT: Mirror - http://android.grdlock.net//index.p...directory=ROM Kitchens/dsixda Android Kitchen
[Android] Alex-V:
Wow...many updates in last weeks...thanks for this :) :p :p :p:) :) ;)

with kind regards...Alex
[Android] jaykresge:
I'm no programmer, but maybe it's time to learn. I've tried various combinations but I just cannot get this Kitchen to make a ROM with /data/app functionality, and have the apps placed in that folder actually install properly. I don't see anyone else reporting this issue, so I'm certain this is user error on my part. I also cannot find the recovery log, though I've used a root explorer (not the paid app, but a knockoff) and there is nothing in /cache/recovery/.

When using edify scripts, absolutely no apps in /data/app are visibly installed on the phone (app drawer, or manage applications) but the space is taken up as if they were installed. When using amend scripts (the older one), I placed 5 apps in /data/app, and three installed properly. They showed up in the app drawer and in manage applications, but the other two did not. However, the space on the device was used up to indicate that the other two had installed.

Any ideas on what I'm doing wrong? Any more information that I could provide?
[Android] maxq1:
@dsixda

nice work on this kitchen, man! may i know what version of dt a2sd is included in the latest kitchen? i'm asking coz the latest dt a2sd, if i'm not mistaken it's beta4, has a couple of more functionality than previous versions. TIA...
[Android] dsixda:
In post #2 I mentioned that I reverted back to the earlier, stable version of apps2sd due to booting issues in the new version. The developer has also said he is going to rewrite it as it has some issues now. What more functionality is required, other than putting your apps 2 SD? ;) :)
[Android] dsixda:
I don't have a solution but you should've checked the recovery.log before your first reboot, because otherwise it gets cleared. It only stores info of the current recovery session, so u should check it right after u flash. You probably have to use ADB to access it while in recovery. OR, if u have Amon_RA recovery you can simply copy it to SD card.

You may also want to try out the data/app verification plugin on post #1.
[Android] Spike_M:
tnx dsixda

great job

i test kitchen for cooking dhd roms today ...
[Android] maxq1:
well, there's /data to ext & lowmem presets which users may play around with to improve device performance. hope you could also include the latest version along with the previous on your next kitchen version. imho, the 'bootloop' thingy may be avoided by NOT enabling a2sd by default (or upon rom install) during cooking (btw, is this possible w/ the latest kitchen?). instead, users can able it after a successful install & reboot. just a suggestion though...
[Android] dsixda:
Nah, I think that's just extra work which makes things more complicated for the user. I'd rather keep things simple for everyone. If someone wants the latest but buggy version then they can go to that thread and download it. Data 2 Ext is interesting though... are you sure it's in that version (no mention of it in release notes)?? Low memory killer won't be compatible with the settings in Gingerbread. I'll wait for a stable version.
[Android] dcharleyultra:
DT gives a straight forward procedure for adding a2sd to a ROM. You can use it if you want a version other than what's in the kitchen.

Swyped from my Evo 4G using Tapatalk
[Android] G1ForFun:
Anyone try to set this up within the last two weeks? Did you manage to get java installed? Nothing in this thread works on my end...

I can rape windows but this stuff has me scratching my head...
[Android] jaykresge:
Yea. If you mean the guide from theunlockr, it's a bit outdated.

First, Download the latest Ubuntu (same VM software) - http://www.ubuntu.com/desktop/get-ubuntu/download

Make sure you get the 32-bit version, even if you're on a 64-bit CPU/OS.

As for getting Java setup, that was a pain in the but for me. Use Google. I'd do it for you now if I weren't on a time crunch. If you still don't have it working tomorrow, I'll try to find the java fix for you.
[Android] G1ForFun:
Appreciate the reply...I am going to keep trying but man I can't believe how difficult it is to do something so simple (Install Java!).

edit: HAh I finally got it...I ended up downloading the older Ubuntu because I had no luck with the newer version...the older version worked fine.
[Android] Spike_M:
hi again dsixda

i cooked a rom for dhd and try to flash it but i got this error:

format () expects 2 args. got 3

e:error in /sdcard/signed_xxx.zip

(status 7)

installation aborted.

i try cooking with another option like add task killer or dont add task kiler but i got a same error when try to install it
[Android] dsixda:
Just search the thread, this was asked twice on February 20th.

Can you post your updater-script please?
[Android] Spike_M:
yeah sure ...

I apologize if I disturb you
[Android] mike1986.:
This "3" arguments are referring to formatting commands like

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

ext3 ---> first argument

EMMC ---> second argument

/dev/block/mmcblk0p25 ---> third argument

You need to use newer update-binary. Take mine. File attached.
[Android] dsixda:
I had once told someone with the same Desire HD problem to try your ROM's update-binary but he said it didn't work, so we'll have to see.

The update-binary supplied by the kitchen is a universal one for all devices, but Mike's will only work for the Desire HD. Looks like I may need to download the Android source and build a new update-binary if the suggested method above works.

BTW make sure u copy the new update-binary to the tools/update_files folder of the kitchen so that it doesn't get overwritten by the kitchen's own version.
[Android] mike1986.:
This update-binary was taken from CM7 RC1 for Desire HD. I didn't test it with any other device apart of Inspire 4G which is US version of Desire HD.
[Android] mike1986.:
dsixda can you shortly explain to me how show_progress arguments works? I noticed that when I add to many ui_print then I got error in recovery. I'm sure it's connected somehow.

Thanks
[Android] dsixda:
I knew someone would ask this week ;) That's the only thing I never bothered to work on. It's like a status bar percentage setting. There is more documentation on xda when you search for update-script syntax. It shouldn't be connected to ui_print.
[Android] dsixda:
@Spike_M:

Can you try this updater-binary (put it under tools/update_files) for your Desire HD?

I re-compiled this generic version just now from the Android source.
[Android] maxq1:
under beta4, command is 'datasd'. its function according to the help file: Moves /data/data to the SD card. using it myself. anyway, thanks for considering though. i have an idea too, will put it to test later on & report back. thanks again, man...
[Android] _fm:
hai,

your new update-binary doesnt work,. the best for desire hd is the one that has 244.244 size,.

it could read command with 4 arguments and could use asserts,.

BR
[Android] dsixda:
Could you upload it, and does it work for any Android device (generic version)?

I was trying to build one from the Gingerbread stream (the one I attached is from Froyo), but Gingerbread requires 64-bit Ubuntu and Java JDK 6, both of which I need to install.

Here's how to build it:

repo init -u git://android.git.kernel.org/platform/manifest.git -b gingerbread
repo sync
source build/envsetup.sh
lunch 1
make out/target/product/generic/system/bin/updater

When complete, rename 'updater' (from the final command) to 'update-binary'

If anyone could do this and save me lots of time, that would be great!!!!
[Android] _fm:
dsixda,

as far as i try, there are 3 kind of update-binary

1. it could use only a few argument, especially EXT3, it could be like this :

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

but, we couldn't use any [B]format, MTD and assert[/B] command

2. it could use a few argument, especially MTD, so it could be like this :

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

assert(package_extract_file........

[B]we could use asserts, but we can use ext3 or emmc[/B]

3. commonly used with the DHD, and the one that support CWM v3.0.0.x, it support more commands

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

we can use asserts and we can use EXT3 and eMMC here, so that the issue that coming with error 3 argument, got 4 is gone,

because the format command support until 3 arguments (while the other just support 2)

and because the mount command support 4 arguments (while the other just support 3)

Hope it helps
[Android] dsixda:
Excellent, thanks... So I have one question -- Does the third version (the one that supports the most arguments) also support the format commands with just 2 arguments (e.g. MTD)?
[Android] _fm:
no dsixda, the third version support only :

- 4 arguments for mount

- 3 arguments for format

the importance of this third version is the compatibility to use with CWM 3.0.0.x, because afaik, cwm v3.0.0.x doesnt support any other command except this,.

thats what i know from trial and error with my DHD,.

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

and about the mounting problem with DHD with your kitchen, its all work with DHD,

the update binary that came with your kitchen is the first version, so for those who cook for DHD, should use this line :

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

otherwise, it wont work,. will came an arguments error in recovery,.

and if the update binary in your kitchen is the second version, we should use the line for the second version that i have wrote above,.

so its pretty simple about mounting for DHD, it depends on the update-binary, and we just need to change the right command,.

BR
[Android] _fm:
dsixda,

well, i am having a problem since last night with your kitchen,

everything is running well before last night, but now the kitchen gave error when the kitchen doing a progress that related to boot.img,

example :

- show working folder information

- unpack and repack boot.img (in advanced menu)

- root permission

- etc

the error is it stuck when tyring to extract the boot.img,

then the kitchen said :

Error : kernel offset not found in boot.img!

well, it happened to stock boot.img and also happend with all custom boot.img

do you have any idea what have i done wrong? i dont think i did something bad with the kitchen at all,. :confused:

as far as i remember, it happened after i change to v137, then i revert back to v135, v130, v126, etc to check maybe the v137 is the troublemaker, but its all the same, boot.img extract still error,. :(

thankyou for the time,.

BR
[Android] dsixda:
I'll provide all 3 versions of update-binary; my script will check the updater-script for the version that suits it.
[Android] dsixda:
Are you using a Mac? Version 0.128 and higher had a fix for this issue for Mac OS X.
[Android] _fm:
nice to hear that,. :)

nope i am using xp with cygwin,. any idea? i didnt do something bad with the kitchen,. :confused:

hehe, anyway, thanks alot for the kitchen,. :)
[Android] dsixda:
No problem.. thanks for your help!!! XP with cygwin should be fine, I use it too.

What device ROM is this?

If you want a quick fix (I have to go to bed very soon, it's past 1am), go to scripts/check_kernel_offset and hard-code hex_offset to 2048 or 4096, depending on your boot.img type.

e.g.

hex_offset=2048

EDIT:

Let me know what you get with this command:

od -x -A x boot.img | grep 000800

Please paste the EXACT output (including spaces and tabs)
[Android] dsixda:
OK I've posted kitchen 0.138 to GitHub. I'm going to bed now.. it's getting late and all this work is making me crazy. ;-)
[Android] _fm:
the command you gave doesnt work,.

DHD use 4096, but it could also use 2048 (i havent try injecting the zImage that extracted with 2048),. :D

it's all working well now, the problem came from my computer,.

thanks again dsixda, :D

BR
[Android] dsixda:
Dv

Hmm, if the command didn't work then you should've gotten an error message when you started the kitchen, which would say that 'od' wasn't found (assuming that u were missing it).
[Android] TMartin:
Is something going on with github?? Keeps throwing an error when I try to download the latest v0.138.

/tmp/XOemdKjt.zip.part could not be saved, because the source file could not be read.

Try again later, or contact the server administrator.
[Android] dsixda:
Downloading fine for me as I type (from Dolphin browser)..
[Android] TMartin:
I'll try a few other browsers. Thanks dsixda

EDIT: Mirror for v0.138
[Android] Spike_M:
hey

tnx dsixda for update kitchen

i cook a simple rom based on orang 1.84.61.2 for dhd with 0.138 version and it seems to work just fine...

tnx for your hard work dsixda

i test it with other option an compile kernel ... and i announce to you the result

tnx martin for mirror
[Android] dsixda:
That's great news for the HD! Thank you for reporting.
[Android] maxq1:
i'm stumped here. building a rom from cm7 build 5 for htc legend . hope someone could help...

added /data/app functionality. from previous kitchen version, i'm getting this:

format () expects 2 args got 3

problem line w/ updater-script, i think is:

format("yaffs2", "MTD", "system");

on latest kitchen:

mount () expects 4 args got 3

problem line w/ updater-script, i think is:

mount("MTD", "userdata", "/data");

though i also have another line:

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

attached are the updater-scripts & binaries i generated from the kitchen.
[Android] dsixda:
I think I see what the problem is. When you added /data/app it probably caused the mount("MTD", "userdata", "/data").

You have to change it to: mount("yaffs2", "MTD", "userdata", /data")

.. so that it is the same as the others.

Can you please upload your update-script.
[Android] maxq1:
^ got it! can't try it for now as i'm at work. will report later though along w/ my update-script. thanks again, man!
[Android] dsixda:
Also, you might need to copy: tools/update_files/ext3-update-binary to your META-INF/com/google/android/update-binary.

EDIT: Actually, it should be emmc-update-binary.... aaaarggghhhh this is so confusing!
[Android] dsixda:
No need to upload the update-script, thanks. I was able to reproduce the issue with a Cyanogen ROM. I also fixed the wrong update-binary that was produced in your working folder.

Kitchen 0.139 has been uploaded with these fixes.
[Android] mike1986.:
dsixda I have some strange problem. I can't force some script to run. What can be wrong? Executing the script manually works so no problems with script itself.

Here's code from updater-script:

Thanks!

EDIT:

ah fixed :D
[Android] cruizz:
somebody,would you tell me 'bout creating update.zip using dsixda kitchen for sony ericsson...because when i tried it always be fail to flash it...(forgive me for my bad english)...i'am a newbie... :)

best regards...
[Android] dsixda:
You'll have to be more specific than that, what do you mean by, "fail to flash"? Give the error message.
[Android] TMartin:
Mirror for v0.139
[Android] cruizz:
ok... after finish creating the update.zip using the kitchen, then im flashing it using zdzihu xrecovery mini-alpha...here goes the error :

# finding update package...

# opening update package...

# installing update...

# formating SYSTEM:...

# copying files...

# E:failure at line 8:

copy_dir PACKAGE:data Data:

# installation aborted.

could you explain it..forgive me if my words makes you confused...thanks in advance :)

sent from my Xperia X8
[Android] maxq1:
man, you're fast! dl & will test asap. thanks again!
[Android] Spike_M:
hey

dsixda , i test 138 and 139 version and i have a good news and bad one

first bad : :D

if you cooking a dhd rom with advanced options like app2sd after install it and reboot your device just see htc logo and then reboot and reboot ... (stuck in htc logo)

and good news :

i test your kitchen many time and i figure out device stuck in htc logo because of any options that add a data folder in root folder of rom ( like app2sd , install bash , install data/app ...)
[Android] dsixda:
Both are bad news.

1) did u use shipped ROM or custom ROM to make yours?

2) why are you using app2sd on a device with enough internal storage?

3) please be specific and provide updater-script and logs of why it fails, otherwise I don't know. Make sure it is not user error. Please understand that I dont own this device

4) I am getting frustrated with this kitchen. Not sure if it is worth the time anymore - No matter how much time I invest there are always failures.
[Android] Spike_M:
i use shipped rom

yeah 1gb its enough for install apps but its not just app2sd , its including data/app or custom bootanimation ...

i just want to help you to make a prefect kitchen for cooking

no , be sure it worth to complet your kitchen an i help you if you want

i attach updater-script of rom that stuck in logo
[Android] ciolnadu:
don't give up @dsixda

this kitchen is working great with LG P500 Optimus One :D
[Android] dsixda:
Do you really have a folder called "data" in your working folder?

Ok, post your entire update-script then..
[Android] NinjaWolf:
Porting issues

ok, ive tried dozens of times with diff. outcomes, first i tried porting from another device(thunderbolt to evo) off of a ruu rom.zip. the farthest i get is the "Evo 4g(htc bootscreen)" then goes black for 3 sec. then goes into recovery. so am i missing something. ive done the basics(changed init.device.rc to init.supersonic.rc and changed kernal, applied supersonic hardware files and changed build.prop). plze help
[Android] dsixda:
Hehe, you have it easy, you have an update-script, most likely. ;) I was going to stop the project back in November because the updater-script stuff was a huge undertaking. But a lot of people were pressuring me for it. I didn't reallize I'd be working on it every day since my vacation ended in mid-January. I think it's close to being perfect but just those newer devices are throwing me off... although I'm slowly getting those issues fixed!

Please keep in mind, the kitchen is a tool to help you learn and to make your ROMs, and I strongly emphasize the word "LEARN". When you see issues in your updater-script or update-script, please apply common sense and figure out what is the issue on your own. I don't like asking for these things all the time in my replies, I don't mind it once in a while, but if it's too much then it takes away my own spare time while it saves other people their time. If you find a problem, try to debug it on your own -- there is LOTS of information in the FAQ -- and if you fix it then please let me know. Some of these problems are simple. I do this in my spare time and for free, but it's tough when you have other obligations in life, like family, work, other hobbies and sleep ;)

I was never an Android expert, and I still don't call myself an expert. I write scripts to expediate the process of making ROMs. I want you guys to benefit, but it doesn't mean to have you guys sitting and making automatic ROMs and publishing them on XDA and becoming famous and rich etc., and then relying on me to fix them when something goes wrong. Take this as an opportunity to learn Android, Linux, programming, operating system architecture, etc. I'm not telling you to be Cyanogen or some hot-shot developer, but if you made it all this way to downloading a kitchen and making a ROM, then take the intiative.

Also, if you have a legitimate problem, then do let me know or send me a Tweet. I get annoyed when I can't make someone happy, and I also get annoyed that a lot of those developers like Cyanogen, Koush, Paul O'Brien, etc. rarely ever respond (+ NEVER to me), and that was a reason for starting this kitchen. It's here to help you guys who have trouble getting help elsewhere.

Anyways, hope you all understand. Enough of my rant :-)
[Android] dsixda:
Thanks, will look at it later.
[Android] TMartin:
We appreciate all the hard work dsixda. I know I have learned an unbelievable amount about Android because of you and this great kitchen. I know Cyanogen and Koush don't respond but Calkulin helps and if you ever need any other answers, I can get you touch with Behnaam. He is an Android Dev godfather. Thanks again for all the great work.

Posted from my HTC Evo 4G on Tapatalk Pro!
[Android] svprm:
@dsixda

Now only saw your post on mini pro forum.

Thank for updated version of kitchen to work without boot image.

It will helpful for Xperia x10 user.
[Android] dsixda:
This updater-script actually looks fine to me. You'll need to check your recovery.log right after you flash it (before first boot). If you see no errors then you need to check your logcat.
[Android] dsixda:
Read the FAQ, logcat, recovery.log, etc...

That porting tool is only experimental, as I'm not an expert on that. It should, in general, boot up though... however, in your case you are using two different filesystems (Thunderbolt=ext3, Evo=yaffs), so the drivers and ramdisks etc. may be totally incompatible between the two devices. But I might also just be talking BS.
[Android] dsixda:
I appreciate the help from guys on this thread like you :-)

Yeah.. most of the guys I know from Windows Mobile days, especially from PPCGeeks.com (Calkulin and a couple others) are really helpful and will respond. The WinMo community in general are full of nice and helpful guys. There is always help to go around when it comes to cooking. Android guys are grumpy Linux geeks :D Just joking, don't mean to stereotype ;-)
[Android] dsixda:
Looking forward to feedback from the X10 series!
[Android] NinjaWolf:
RE:porting

Well, it seems caulkilin(i think thats his name, i cant remember) go it ported to evo, but with bugs. And i do love his roms, i dont like themes, also i want to learn. so im going to message him and ask for tips.
[Android] muralto:
Hi dsixda,

I'm the latest donor you mentioned in the first post of this thread (you must ignore this info) and I'm experiencing a few troubles with your latest builds.

I'm (almost) a

Huawei U8150

's chef and from build 138 the kitchen doesn't work anymore... when I install the cooked ROM, two recovery (on two aviable for my terminal) report an "error 0".

With build 137 everything works smoothless!

That's all, thank you for your work :)
[Android] Droidzone:
Converting deodexed apks to Odexed apks

This is not a Kitchen related query, but I was hoping that other Rom devs could shed some light on a problem.

I'm building a Non-deodexed Stock Sense Rom for HTC Desire. I'm trying to replace the non-deodexed system apks in /system/app with their newer updates from the Market.

Eg: Vending.apk

I've tried the following:

Remove the Vending.apk and Vending.odex from /system/app and replace them with the latest deodexed Vending.apk from Market.

Remove the Vending.apk and Vending.odex from /system/app. Then, removing classes.dex from Vending.apk (Zip-Unzip), and then using the .dex file from /data/dalvik-cache and renaming it as Vending.odex and putting both the files in /system/app folder

Keeping the orginal system/app files, and adding the new deodexed apks to /data/app

In cases 1 & 2-System fails to boot. Logcat: busybox terminated with error code 255

Case 3: System boots fine but the update doesnt seem to be installed.

If anyone in a similiar predicament knows a solution, I'd love to hear it..

Edit: I found a script for this