yashsingh1/xdaforums huggingface dataset:
[Android] dsixda:
No, because I said you need a custom recovery menu, it means you dont need to install one.

;-)

I think I answered this question 2 days ago about the same issue to someone else, about the format command taking the wrong number of arguments. Go back and check that reply of mine. Maybe the update-binary in the kitchen is out of date. Did you try the one that was in the original ROM?

init.d scripts will get executed all the time unless you set a flag to make them only run once. You don't want to keep installing busybox over and over.

I think you are getting a little too obsessive-compulsive -- Just stick to making the ROM work. ;-) Who uses chownto? My Nexus One doesn't have a /system/xbin/chownto or /system/bin/chownto in the stock ROM either. There are reasons that dumpstate is there in yours and not dumpcrash, I just have to look at the scripts, too tired right now. You can take a look.

I answered this system.img question three times in the last week and also have the answer in the FAQ. I have also answered it twice in PM's in the last 10 days or so. I also have said on the first post to read the FAQ before asking questions in this thread.

Come on guys, save yourself and also myself some time. I dont want to clutter up the thread with duplicate questions/answers all over the place. So just read the FAQ.. thank you.

I had made a change last month to make the kitchen work with boot.img files in Huawei and newer ROMs like on the Desire HD. I just tried your 'full' and 'flashover' ROMs and they extract fine on my system. The other guy who asked this question did not answer my question about the platform he was using nor the device he used, but I believe it was a Nexus S (based on his post history), and my kitchen has no problem extracting kernel from that device's boot.img either.

What OS are you using? Can you do this: type od --help and let me know if you see "-x" as an option. Thanks

True, but not necessarily... In Cyanogen mods they use the format("yaffs", etc..) method as well. I guess the format("MTD", "boot") is a workaround, but I believe the update-binary may be out-dated so that it doesn't support the "yaffs" parameter.

BTW, Nixeus -- the answer at the top was sarcasm.. yes, u need a custom recovery image, why was it not clear enough on the first post?
[Android] IzaacJ:
Well, I've already tried that. And as I've stated in my previous posts, that script work perfectly with every other ROM, not just this one.

Every ROM I've built and flashed has had format("yaffs2", "MTD", "boot"); and none of them has returned an error before.

My base ROM (which is fully functional, running it now) updater-script also has format("yaffs2", "MTD", "boot"); in it.

EDIT: It stops working after the kitchen has converted it, even if it's exactly the same :O
[Android] Droidzone:
Well, then, as dsixda suggested, take the update-binary from the working rom and pair it with the script
[Android] dsixda:
If droidzone's MTD suggestion doesn't work in your ROM, then I have no idea either. If you use his idea then you also have to do the same to the other mount points in the updater-script ... did u do that? ie. Remove the yaffs2 parameter.
[Android] IzaacJ:
I have tried with the update-binary. But I have not edited every format command, as it always stops when formating the boot. I know this as I have a lot of ui_prints in case of any problems.

The weird thing is that the exact same script is working in an other ROM, only difference is that there are ui_print commands in it. But as neither the original script or the updater->update->updater converted script is working when the build has been opened in the kitchen my only idea is that there is something among the files that gets messed up while building... Could that be right?

You're free to check both my base and my modified ROM, if you want then I'll upload them both

EDIT ! The error can't be in the script ! I took the script from the built ROM and put it in a copy of my base ROM and it installed just fine ! And the only thing I've done in my own this far is replacing ADW with GO Launcher, adding GO SMS and added another bootanimation.zip.
[Android] dsixda:
@sk806:

Can you try the following from your WORKING_* folder, and tell me what you get? Just cut and paste the exact output, I want to see where all the space characters are as well. Thanks

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

Anyone else having the same "kernel offset" problem, please try this as well.
[Android] mike1986.:
After some tests it came out that installbusybox method caused that phone wont boot if previously usb debugging was turned off. It's strange and I wonder if you have some peace of advice for that?

Ok, forgive me my being obsessive ;) I will try to calm down.
[Android] 1975jamie:
i have just installed kitchen .127. when i go to zipalign the apks it tells me

Zipaligning ./system/app/Swype.apk ...

scripts/do_zipalign: line 62: ../tools/zipalign_files/zipalign: No such file or directory

Error: Unable to zipalign

please help
[Android] dsixda:
USB debugging is already set by the kitchen to the boot.img when you root the ROM. Default.prop --> ro.debuggable=1

Did you change it?
[Android] dsixda:
Link to ROM?
[Android] 1975jamie:
on my other computer that has kitchen 112 it works fine with the same rom. this is a new computer that i installed kitchen on. the only difference is 127

edit it also does it on every rom i start a new working folder with.
[Android] dsixda:
I havent touched the zipalign script in months. I used it a couple of days ago with no problem in cygwin.
[Android] 1975jamie:
maybe i should just uninstall and start over
[Android] dsixda:
I think all of you guys with issues shouldn't even be touching the kitchen on a Saturday ;-) I have not seen anything yet that I have to fix.
[Android] IzaacJ:
Please. I really need some help. Been stuck with this too long. Tried about everything...

My tries has made one thing clear,no problem with the script. The problem is how the rom is being built. But I can open another ROM (have tried with HyperDroid) and rebuild it w/o modifications and flash it, but opening the CM7, rebuild it w/o modification and flash I get errors... Even if I use the original script or any other script that works. I'd be really pleased if anyone would help me with this throughly.
[Android] mike1986.:
No, it's also ON be default in my default.prop but the thing it that some people are not wiping data partition before flashing new ROM version and then if they turned usb debugging OFF it will remain OFF because this setting is saved on data partition. I will try moving installbusybox to init.d script and also with command to remove it after first boot (in script with higher number).
[Android] 1975jamie:
fixed

just wanted to let you know i fixed the problem. the new computer is running 64 bit windows 7.

i guess unbuntu does not like that. i had to install ia32-libs. all works now. every apk zipaligns now.

thank you
[Android] nickiberli:
Hey guys

I hope this question has not been asked before..

I converted the updater-script from the 1.84.xx Version for the DHD to an update-script.

But if i flash the rom now, (with the updater-script it worked..) i get the following error:

E:Board does not support mtd utils.E:Failure at line 237:

write_raw_image PACKAGE:boot.img BOOT:

Installation aborted.

I repacked the boot.img and added another kernel, but i stillt get the same error.

These are my last lines of the update-script:

Line 137: format BOOT:

write_raw_image PACKAGE:boot.img BOOT:

show_progress 0.100000 0

Any ideas how i can fix this error?

best regards

nickiberli
[Android] dsixda:
The FAQ, man, the FAQ...
[Android] dsixda:
I'll post this in the FAQ, I think someone mentioned something like this a while back but couldn't solve it. Thanks.
[Android] dsixda:
Try the HD2 dev forum or start a thread in this Chef forum. I don't think most people here are familiar with a NAND ROM. If it's not a kitchen problem then it should be asked in a separate thread.
[Android] matt_b:
i read the faq. my bad.
[Android] dsixda:
If you still have the same ROM as before, then there is already an answer for that in the ......... wait for it........ the FAQ.
[Android] matt_b:
guessing you were referring to this post?

i suppose i'm not sure what lines exactly i need to edit in the updater script. i don't see anything similar to whats in the post. i'll keep looking though.
[Android] mbobino:
I'm also having the kernel offset not found issue. Here's the output of your command.

Michael-Bobinos-MacBook-Pro:WORKING_021911_232134 michaelbobino$ od -x -A x boot.img | grep 000800
0000800 0000 e1a0 0000 e1a0 0000 e1a0 0000 e1a0
0008000 8006 c31b cf03 349d 39e8 dcca 6b66 cf03
[Android] dsixda:
Thank you very much... so it was in fact a Mac OS X issue. The output was returning extra spaces between numbers, rather than one space.

I hope the new version 0.128 will work for you.
[Android] dsixda:
You'll need to convert it to an updater-script first. Then just follow that post, but first confirm your mount points are the same as in that post. I assume you have a device similar to the Desire HD.
[Android] Nixeus:
@Dsixda :

I'm sorry for my last noob question....

I have read the FAQ and finded the answer , i'm sorry.

For the moment, i don't find a way on my tab ( Gpad Gforce) in order to flash a rom with zip file :(
[Android] IzaacJ:
Well, it has to be a kitchen problem as my base rom is working fine. BUT if I open it in the kitchen and does nothing other then rebuilding it it doesn't work. You try it yourself. Download this and just make an workingfolder of it, and then rebuild it. It will not work.

There is no problem with the rom as it is working perfectly when I flash it w/o going through the kitchen.

Only way to get it to flash is if I put it in a zip by hand. Not letting the kitchen do it. Isn't that a sign that the kitchen fails with the building?
[Android] Bytecode:
Wow really cool kitchen
[Android] dsixda:
I only have a Nexus One, I can't try it --

I am confused as to what the problem is, you said earlier it was not the updater-script's fault so I assumed it was a user error. What do you mean it "does not work"? That doesn't help me, you will need to mention the logcat and recovery.log. There is help already in the FAQ about what to do if your ROM does not boot.

If you are making a NAND ROM then make sure you end up with a boot folder and not a boot.img.
[Android] dsixda:
This is a kitchen thread, please Google your answer for a custom recovery for your device. I can't do this for you. Sorry, I don't own all these devices and don't know all the answers... I just write scripts. Good luck!
[Android] matt_b:
yes, i have the inspire 4g.

my mount points in android system info for data and system are the same as in the scripts you listed. i'm making this change prior to the final step of cooking the rom, where it says to make any changes to the updater-script.

do i need to put them in any particular place of the script? i tried putting the 4 lines after line 2 which is "delete_recursive("/system");", but when trying to flash i get 'error in sdcard/' then the file name followed by 'status 6'.

i'm really trying to figure out where i'm going wrong. thanks for the help you've given me thus far.
[Android] dsixda:
Do you need to do a recursive delete of /system? Why don't you just do a format of system. Format it and then mount.
[Android] IzaacJ:
My base ROM has a boot folder, a system folder and the meta folder.

If I by hand edit the updater-script, apply all my mods and adds the apps I want in it W/O extracting it with the kitchen it flashes okey.

BUT if I make a working folder of it, by that I mean extracting everything with the kitchen, and then do absolutely nothing, by that I mean no apps added, no edited update/updater script, no editing build.prop, just extracting it with the kitchen and then rebuilds it, it won't FLASH. No boot problem, flash problems.

The scripts I have edited does all work if I put them in the original zip, the apps are added correctly if I put them in the original zip, the other mods work perfectly if I put/apply them to the original zip, BY HAND, not even getting the zip near the kitchen. BUT if I do like this (using cygwin):

1. run "./menu"
2. select "1 - Setup working folder from ROM"
3. select my base ROM (charnsingh_online's unofficial CM7 Leo nightly)
3. converting the updater-script to update-script (as recommended in the extraction progress)
4. selects recommended option for the two queries about the recovery reference and the script
5. select to build the ROM
6. convert the update-script to updater-script (as CWM only handles updater-script)
7. put the newly created zip in the root of my mSD
8. boots CWM Recovery and selects to flash zip from card (as always)
9. selects my newly created zip
10. verifies that I want to install this zip
11. it errors out abut format getting 3 args instead of the required 2

As soon as the kitchen has touched any of the files it won't work to flash it.

I can't even take the working folder and build it by hand, and by that I mean, taking the correct folders and put them in a zip. But as stated before, if I extract them with winrar and repacks them with winrar it work fine.

Do you get what my point is? And I'm not a noob when it comes to all of this as I used to convert sd-ROMs and DFT ROMs to CWM ROMS, so I know how the zip is supposed to be constructed.
[Android] nickiberli:
Now i have another question and at this thime i read the FAQs, the latest posts and searched... ;)

I get this error if i flash the rom:

I know that the error comes with one of these lines:

ui_print("Formatting partitions...");
format("ext3", "EMMC", "/dev/block/mmcblk0p25");
format("ext3", "EMMC", "/dev/block/mmcblk0p27");
format("ext3", "EMMC", "/dev/block/mmcblk0p22");
#format("ext3", "EMMC", "/dev/block/mmcblk0p26");

show_progress(0.500000, 0);

ui_print("Mounting partitions...");
mount("ext3", "EMMC", "/dev/block/mmcblk0p25", "/system");
mount("ext3", "EMMC", "/dev/block/mmcblk0p26", "/data");

I took these lines from mike, but it still doesn't work..

This is my updater-script: http://pastebin.com/40gykpA8

This is mikes updater-script: http://pastebin.com/RU8VS0se

I have no idea why i get this error.

If i flash Android Revolution HD i don't get the error...

Hope you guys can help me :)
[Android] dsixda:
Try his update-binary (if you have a Desire HD) and try again.

Otherwise, put a "ui_print" before each format line and see where it fails.
[Android] dsixda:
I know what your point is, but you are posting the same problem over and over.

Did you try an update-binary from another working ROM like I told you a few replies ago?

Have u searched Google for the error? Have you tried getting help from an HD2 dev? There were a few who already posted here, just search the thread from the last 2 weeks...

I can't help any more because I only have a Nexus One. I write scripts, I'm not an Android expert or claim to know everything about Android or what every single updater-script error means. There are people around this site - especially for your device - who know more than I do, please don't expect me to know everything. Hope you understand.
[Android] IzaacJ:
Yes I've tried it. And yes I've googled it. The reason I'm posting here is that the script or something else seems to be corrupt when your kitchen has been working on the files. Thats when things go bad. That tells me that the problem has to be in the kitchen. You might find something if you look through the zip supplied by charnsingh_online. OR there is a problem with your kitchen and CyanogenMod 7 roms. I don't know.
[Android] nickiberli:
I took his binary but i still get the same error.

i tried it with putting an ui_print before each format line, but it seems that none of these lines is working.. :(

Any ideas?
[Android] dsixda:
Ok I will take a look at your previous upload. Actually why don't you post the original updater-script and also the one you created with the kitchen. Then I can see where things changed. Thx
[Android] dsixda:
I don't know man, just ask Mike and/or Google it. I'm out of random useless answers. LOL.

Btw do a dump of the recovery.log immediately after you flash, as I said in the FAQ.
[Android] nickiberli:
Ok, this is the "flashing part" of the recovery.log:

-- Installing: /sdcard/signed_022011_124332.zip
Finding update package...
I:Update location: /sdcard/signed_022011_124332.zip
Opening update package...
Installing update...
mke2fs: can't format mounted filesystem
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25mke2fs: can't format mounted filesystem
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p27mount: failed to mount /dev/block/mmcblk0p25 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk0p26 at /data: Device or resource busy
script aborted: format() expects 3 args, got 2

Welcome to AndromedaMOD

Formatting and mounting partitions...
1
2
3
Cleaning up...
Formatting System...
format() expects 3 args, got 2
E:Error in /sdcard/signed_022011_124332.zip
(Status 7)
Installation aborted.
[Android] dsixda:
After the file is finished uploading from my computer, it takes additional time for multiuploader.com to finish uploading to the other sites.
[Android] chuti98:
I used legend stock rom and Hero3G stock rom. I did wipe and flash
[Android] dsixda:
Ok, so what options did you use from the main menu of the kitchen?

Also, it will be helpful if you can provide me the following info:

- where did you get the stock ROMs from? (link)

- what was the exact message you saw on the screen? Please copy it word-for-word.

Thanks
[Android] chuti98:
I used port option and follow the step first put system.img and boot.img from Hero3g and then do follow from kitchen by put system.img and boot.img from legend. and also did option root, add task killer, app to sd (can u do fat32 + ext4 as well), add wireless tethering and add /data/app. After that I did build rom from working folder

I got stock Hero3G rom From ftp://xda:xda@ftp.xda-developers.co...3G_UK_2.73.771.73_release_signed_NoDriver.exe

and Legend rom from http://xdaforums.com/showthread.php?t=649565

and the message that I got from flash is:

E:Can't chown/mod /system/xbin/busybox (No such file or directory)

E:Failure at line 74:set_perm 0 0 04755 SYSTEM:xbin/busybox

Installation aborted
[Android] dsixda:
Ok thanks,

Is there a /system/xbin/busybox in your working folder?
[Android] chuti98:
yes, the busybox is in that

I used port option and follow the step first put system.img and boot.img from Hero3g and then do follow from kitchen by put system.img and boot.img from legend. and also did option root, add task killer, app to sd (can u do fat32 + ext4 as well), add wireless tethering and add /data/app. After that I did build rom from working folder
[Android] dsixda:
There is a thread about this error, not sure if they fixed it:

http://xdaforums.com/showthread.php?t=556802

I wonder if Apps2SD is causing this problem. I'll keep looking...

EDIT: I think it may be with the ROM you downloaded was corrupt? Here's another thread (not related to my kitchen) where people were complaining about the same error when flashing a custom ROM:

http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/

thanks
[Android] dsixda:
No bro, that looks fine. I am flashing ROMs all the time with that line.

Check my previous reply, i've added more info.
[Android] dsixda:
In the root option of the menu: if you say "No" to the busybox question, then you won't get that busybox error during flashing, because it won't modify update-script with those lines.

But that doesn't solve the problem of why we get that error message. Using a Google search, it looks like a lot of people are getting it when flashing any custom ROM (not from my kitchen). I haven't seen a solution yet but it seems that people get it when they use apps2sd.
[Android] chuti98:
I think that I have to format my card and delete all partition cause now is fat32+ ext4 it may not match my custom rom..
[Android] dsixda:
Yeah, give it a shot and let me know what happens. Thanks a lot for taking the time to do this. This info will help other people as well who have been having the same problem.
[Android] chuti98:
it still show the same exactly error.
[Android] dsixda:
But you selected Apps2SD when creating the ROM. You need to either re-create the ROM without apps2SD, OR, create the correct partition type on your SD card before flashing.
[Android] dsixda:
Support for the Desire and Legend coming hopefully tonight.. or after recovery image for those devices is released ;)
[Android] chuti98:
I wiil create one custom rom without app2sd and see what's going on. My card now is ext3, so I don't think its about my card partiton
[Android] dsixda:
Yeah I wonder what the problem could be, then. It occurs on other ROMs too that aren't created with this kitchen.
[Android] chuti98:
or you think I should manual delete two line that I had refer to about busybox coz it don't have in other custom rom.
[Android] dsixda:
Those lines only get added if you selected the busybox option. You said there was a busybox under system/xbin.
[Android] chuti98:
That why I'm so wondering why there are still error

so you think I should try on custom rom without root to see what will happen
[Android] TarLink:
Hello respected! I such question how me to make so, what in my insertion would have a frequency on demand interactive / 729 mHz ?! I for myself collect assemblage, for LG p500, but I can not understand with this question in any way. Like has found something in type files init.qcom.post_boot.sh in Boot.img and in a folder/etc. Excuse if this question already rose, I simply don't know language, I from Russia and write by means of the translator. Thankful in advance, Alexey!
[Android] dsixda:
Like the recovery.log says, why are you mounting/formatting the /system partition again after it has already been mounted/formatted?

Your updater-script:

ui_print("Formatting partitions...");
format("ext3", "EMMC", "/dev/block/mmcblk0p25");

...

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

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

I thought I made it clear in the FAQ. You have to MODIFY the existing lines, NOT ADD to them. :-) Guys, come on.
[Android] dsixda:
Both of you guys have been asking me about the same problem today.

1) Nicki followed the instructions in the FAQ wrong about his updater-script. Not a kitchen issue.

2) Izaac - I converted Charan's updater-script to update-script and back to updater-script, and there is no difference between what he had and what the kitchen created. You did not provide a recovery.log immediately after a flash, as I have told you to, so there is no way I can help you otherwise. I'm not going to download any more ROMs. Have to spend time with my family.

Anyways if you follow the troubleshooting that was laid out in the FAQ in the beginning then the issues would be easier to resolve. Otherwise you will just be wasting your time and a lot of my time as well. No problem though, hope you learned something. Good luck with the ROM.
[Android] TheRedDroid:
Thanks alot bro!!
[Android] dsixda:
I've uploaded 0.129, just a minor change to reduce the chance of server issues when you download updates through the kitchen. It also makes my work easier by using GitHub to upload ;)
[Android] aZuZu:
since there is no way to conntact you,,,

i work on xperia kitchen .. in rom build .6 unyaffs then mkyaffs gives non-valid img at least in mkyaffs/unyaffs that i could get over internet.. could you confirm that? thanks!
[Android] dsixda:
There are ways to contact me ;) see below. Also give me links, I am not gonna search for ppl's ROMs. Thx
[Android] aZuZu:
img file will be avail here for around 2h-3h ... http://azuzu.spice.net.au/other/

thanks for help!
[Android] dsixda:
Oh... Wait a second... this is not a dsixda Android Kitchen issue is it? You're asking about another kitchen, which is off-topic for this thread. Your provided system.img does 'unyaffs' fine. I never used mkyaffs. If you have any other questions, let me know.. send me a Tweet.
[Android] aZuZu:
Yes! off-topic

here is my msn: x_azuzu_x@hotmail.com
[Android] dsixda:
Kitchen 0.130 is now out.. enjoy.