updater script problem

[dan281082]

got this message when i cooked ported rom in kicthen.

make sure u fix these errors

3:mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "???");
5:mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "???");

then on installing i got this error
mount expects 4 args got 3
status 7 error

anybody got any ideas

i was porting a desire s rom to desire using kitchen

 

[dsixda]

got this message when i cooked ported rom in kicthen.

make sure u fix these errors

3:mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "???");
5:mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "???");

then on installing i got this error
mount expects 4 args got 3
status 7 error

anybody got any ideas

i was porting a desire s rom to desire using kitchen

First of all, have you tried creating a regular Desire ROM before porting? Do not start porting unless you know what you are doing, as stated in the kitchen porting menu. Manually change those mount points to the MTD format, as the Desire doesn't use ext4 or ext3. If you have made a Desire ROM you'll know what they are.

The error message about 'mount expects 4 args got 3' refers to the fact your mount command takes 4 parameters (ext4, EMMC, dev/block, etc.) and your update-binary only checks for 3 parameters. You'd have to change the update-binary file to a compatible one, found under the /tools/update_files folder. Just copy the appropriate one and rename to update-binary. Since you are going to be using MTD, use the 'mtd-update-binary'.

Furthermore, you are going to have a hell of a time trying to port a Desire S ROM to an old Desire. The system partition in the Desire is too small, and Desire S ROMs are way bigger than Desire ROMs. Did you read the warning shown in the kitchen after you ported?

 

[dan281082]

thanks for your reply,

yeah i read the warning bt not knowing enuff about it is why i asked on here, only gunna find out by learning in my eyes.
so i would need to slim down the desire s rom to make it fit. my rom i created from the ruu is only small anyway. about 169mb.
i think ur kitchen is very good piece of kit for novices like me to start from.

actually i have a question u may be able to answer

can i replace a system ui apk odexed with a deodexed version?

also u say the desire s is harder which model would port a newer sense to desire easier then ?

 

[nickiberli]

Try it with a newer updater-binary.

 

[Albert Poon]

I am also having similar problem:

NOTE: Ensure you fix the unknown reference(s) at the line number(s) below.
      Compare with the original version of the updater-script, if you have
      one.

367:mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "???");

I figured out that it was fine when the kitchen converted the original updater-script from the ROM to update-script in the WORKING folder, but however, when I build ROM from the working folder, the kitchen converts the update-script back to updater-script using MTD. How can I force it to use EMMC instead?

EDIT: Nevermind... fixed.

 

[tubular_board]

I am also having similar problem:

NOTE: Ensure you fix the unknown reference(s) at the line number(s) below.
      Compare with the original version of the updater-script, if you have
      one.

367:mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "???");

I figured out that it was fine when the kitchen converted the original updater-script from the ROM to update-script in the WORKING folder, but however, when I build ROM from the working folder, the kitchen converts the update-script back to updater-script using MTD. How can I force it to use EMMC instead?

EDIT: Nevermind... fixed.

I'm getting a different issue. it comes up with error 7 or 6 when i try to fix it