hi guys, im not a developer and im not that noob.
i have galaxy s2 us cellular and i flashed it with the generic JB 4.1.2 rom. ODIN md5 file....everything works great including my network and data
but i wanted to change some stuff in build.prop but keep the rom without root and stock, so i extracted the md5 file with z7 and i took the factoryfs.img and opened with dsixda's Android Kitchen. the kitchen gave me an warning about there is no boot.img, so it will a created a fake boot.img.... looks good so far >>>i guess :silly:
anyway the kitchen processed to the end and i got the working_rom, i edited on build.prop with note++ and i entered 99 and then 2 "lazy"...
i got the rom with out boot.img, i was thinking even if i flash this rom and doesn't boot then i will flash the boot.bin with odin (from the same generic JB 4.1.2 package that i extracted)....
bottom line i tried to flash it with CWM, but it gives me an error status 0. i did ask and they told me to change mount("MTD", "system", "/system"); TO mount("yaffs2", "MTD", "system", "/system"); .... in updateR script i did that
but now it gives me error status 7.... i tried to make the system folder as factoryfs.img by selecting all files and folders inside in add archive with z7 and change the extension to img.. and then zip it to tar with z7.......BUT IT DIDNT WORK ....
i know sound i messed up a lot and i have know idea what im doing with this samsung rom....cuz i have been working on a few roms with htc and i loved it... just i feel it easier .....
thanks guys and i hope someone can help me????!!!!!!
btw im working on windows 7 x32 and i have ubuntu installed on my PC ....
hope this might help you
though it is not for our device its for tab2 but just have a look and it might help you...
Peaceful Droid said:
hope this might help you
though it is not for our device its for tab2 but just have a look and it might help you...
Click to expand...
Click to collapse
i will give it a shot :fingers-crossed: thanks
Related
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
dan281082 said:
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
Click to expand...
Click to collapse
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?
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 ?
Try it with a newer updater-binary.
I am also having similar problem:
Code:
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.
Albert Poon said:
I am also having similar problem:
Code:
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.
Click to expand...
Click to collapse
I'm getting a different issue. it comes up with error 7 or 6 when i try to fix it
hello there! i think this is my first post here but ive been lurking since my evo 4g days. But my question is, is there anyway to remove the full wipe that comes with some roms? sometimes ill flash a kernel that hates my rom or my phone or more likely me. Or some other error happens and i would like to just flash the same rom over top to repair and be on my way. ive been running meanrom gb and it works no problem. but i tried running mikrunny 1.13 and i tried flashing rcmix kernel on it and apparently it wasnt for gingerbread i guess. but since it had full wipe built in i lost all my stuff and had to start fresh. sorry for the drawn out post but just trying to explain what my reasonings are. thanks everyone for being awesome here!
You can always do a advance backup of your data in 4ext recovery, cwm recovery I believe also has that option
(Don't ask me for help as I couldn't care if your phone explodes, eh!
It's a command in the install script. Now where and how to remove, I'm not sure.
jump454 said:
hello there! i think this is my first post here but ive been lurking since my evo 4g days. But my question is, is there anyway to remove the full wipe that comes with some roms? sometimes ill flash a kernel that hates my rom or my phone or more likely me. Or some other error happens and i would like to just flash the same rom over top to repair and be on my way. ive been running meanrom gb and it works no problem. but i tried running mikrunny 1.13 and i tried flashing rcmix kernel on it and apparently it wasnt for gingerbread i guess. but since it had full wipe built in i lost all my stuff and had to start fresh. sorry for the drawn out post but just trying to explain what my reasonings are. thanks everyone for being awesome here!
Click to expand...
Click to collapse
Look at the updater-script in the meta-inf folder you will see something that looks like this at the top of the script
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p24");
Remove any line that references formatting a partition. I wanna say that's all you'd need to do. If that doesn't work PM me a link to the ROM and I'll play with it and get it how you want it.
Editing the updater-script file
This might be more than you are interested in trying, but maybe not if you've been lurking since Evo 4G days.
All Android ROM and kernel installation scripts ultimately perform the installation using a scripting language called Edify, but some of them also have an Aroma script included as a preprocessor. Here's a good description of the relationship between Edify and Aroma explained by the Aroma developer.
To do what you are asking requires editing the /META-INF/com/google/android/updater-script file within the zip file you are going to flash. I use WinZip and UltraEdit on my PC but there are a number of editors and archiving programs that will work. You have to use an editor that will leave the Unix/Linux end-of-line characters and Notepad++ is a free editor that can do that.
Once you have the updater-script file open, look for lines like this:
Code:
ui_print("Formatting DATA Partition...");
unmount("/data");
run_program("/sbin/erase_image", "userdata");
format("ext4", "EMMC", "/dev/block/mmcblk0p24");
and change them to this:
Code:
# ui_print("Formatting DATA Partition...");
# unmount("/data");
# run_program("/sbin/erase_image", "userdata");
# format("ext4", "EMMC", "/dev/block/mmcblk0p24");
The lines above are from the updater-script file in the MikVirgin 1.01 zip file.
That will prevent your data partition from being formatted, although flashallthetime's suggestion to do an advanced backup of the data partition before flashing and advanced restore afterwards is effectively the same as the above script change. However, you may find other things you want to change in updater-script files if you become more familiar with them.
For more help with editing scripts just do a Google search for "edify script". If it's more than you want to tackle, PM ItzCrooK2UxD and ask him to make the changes for you.
ramjet73
thanks guys for the fast reply. i dont wanna do a backup everytime because the backup alone takes up more time then flashing the rom over itself plus then youd have to reflash the backup after the fact. i will try some suggestions and see if they work.
Not a full back up, just an advance data back up which takes no time at all
(Don't ask me for help as I couldn't care if your phone explodes, eh!
advance databackup? ive never heard of that. im gonna see if i can locate it in 4ext right now!
When you go into recovery you'll see backup/restore and you'll see advance restore
Sent from my PG86100 using Tapatalk 2
Okay so uh...I'm trying to make my own custom ROM from a stock Galaxy S3 sgh-i747, using dsixda's Kitchen.
My problem is that I am getting a status 7 error when trying to flash it.
Now I know, since I read the FAQ, that it has something to do with the updater-script. The only info I could gather is that you need to go in and change the format/mount code.
I have this:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/data");
So I suppose my real question is...what am I supposed to change (it to) so I can make it work? (and what else might I need to change?)
Any help greatly appreciated!
Edit: Oh and um...I'm also wondering.... If I put any new apks in the rom (such as note2 camera, etc.), do I have to put specific code in the script for them? (I'm a bit new to all this--everyone starts somewhere I guess)
same issue with me also .. Any one there to help?
Figure out your mount points if this is your error, also depending on your update-binary youay need to change the format of the arguments
As for the question about adding .apks, yes you need to modify updater-script to reflect this, and it depends on what folder they are in for ROM.zip and what partition you want them stored in.
Can't answer any further without more info but Google is your friend
Sent from my Nexus 4 using Tapatalk 2
Thats why i don't use kitchen, you wont LEARN anything.
and then you have this kind of problems, and you cant fix them.
And the last reply it usefull, check your mount points.
may be the updater-binary making the cause, try updater binary of working rom.
TroubleShooter™ said:
may be the updater-binary making the cause, try updater binary of working rom.
Click to expand...
Click to collapse
Try from the stock rom first (if the stock is running the same Android os version)
Hi all guys, finally i've found the way to use this very nice tool on our device!!
I've tested it on my P760 with v20b stock ROM and with some little addon it runs fine
First of all i want to clarify that this guide uses a tool made for the xda comunity by dsixda, so the major credit goes to him.
Dont ask me if it works on other variants, i have the P760 only, so try by yourself and let us know.
What you need:
dsixda's Android Kitchen
dsixda Android Kitchen P760 addon
KDZ file or CWM backup of your stock ROM
...a bit of knowledge on what you are doing
_______
Download and install dsixda Android Kitchen from original thread
Download dsixda_Android_Kitchen_P760_addon and extract the contents somewhere to your pc.
You can see two folder "dsixda_edify_defs" and "brocken_sys_files", copy dsixda_edify_defs content to "\Cygwin\home\YourUserName\Kitchen\tools\edify_defs" folder.
Now we need system and boot from our rom. If you have a CWM backup just copy system.ext4.tar.a and boot.img to "original_update" folder of dsixda kitchen and rename "system.ext4.tar.a" to "system.ext4.tar"
If you want to use KDZ stock ROM please refer to this guide provided by kuma82 on how to extract system.img and boot.img
Now run dsixda Android Kitchen and setup your working folder (detailed info on hawto in the original thread).
When setup completed than copy the "brocken_sys_files" contents located in dsixda_Android_Kitchen_P760_addon.zip to the locations specified in the included readme file. I dont know why but dsixda kitchen doesnt process these files correctly so we have to add them manually. They are taken from V20b but should work on other version too.
Ok,now we are ready to apply our mods and cook!!
I've cooked my own ROM from KDZ file and tested some feature, root, deodex, zipalign, init.d, /data/app, all works fine. I've found only one issue releted to deodexing LG keyboard, just replace it with another one and all should be fine.
NOT tested with CM rom.
I'm NOT responsable of any kind of demage caused by using this method, so use it at your own risk.
@moderators
I dont know if this is the right section where to post this guide, if no than feel free to move it to the right one.
Credits:
dsixda (for Android kitchen)
kuma82 and cmahendra (for KDZ extraction)
___
Thanks for sharing the info, Android kitchen was already working but I had to change the updater-script and update-binary manually.
Lol, I didn't think about changing the CWM backup system .tar.a file to .tar I just used the dd command to extract (my current) system.img to my sdcard
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/system.img
Note: my internal and external or swapped, so change accordingly
Another thing, thanks for giving me credit for my guide
@- shifu - thanks man! you have two pm!
@kuma82 how you change it?
format("MTD", "system");
mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
....
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
Click to expand...
Click to collapse
with:
format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
...
package_extract_file("boot.img", "/dev/block/platform/omap/omap_hsmmc.1/by-name/boot");
Yup, to tell you the truth I haven't tried it yet, been to busy, to actually flash it, but if I'm not mistaken @Kid_Ding used it (android kitchen) to port pac rom to the P769
Sent from my LGMS769 using xda app-developers app
kuma82 said:
Thanks for sharing the info, Android kitchen was already working but I had to change the updater-script and update-binary manually.
Click to expand...
Click to collapse
for me it never worked, even changing updater-script.. but i've tried with stock ROM only, maybe with CM just made the changhes you've mentioned.
Anyway with my addon it works out of the box, no need to modify updater-script
Lol, I didn't think about changing the CWM backup system .tar.a file to .tar I just used the dd command to extract (my current) system.img to my sdcard
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/system.img
Note: my internal and external or swapped, so change accordingly
Click to expand...
Click to collapse
yep, i've tried and it worked
Another thing, thanks for giving me credit for my guide
Click to expand...
Click to collapse
of nothing colleague
Very Useful.
Very useful Thread. Saved lot of time. Thanks
So I was trying to package a rom and let the kitchen create the meta-inf folder along with the updater-script but the problem is that it's not using the specified mount points.
My phone isn't supported in the kitchen so I had to make a file in the edify_defs folder for my phone. I did all the right steps, I renamed the file to that of the ro.produc.device, used the template and made the necessary edits using notepad ++, and checked the file for any incorrect syntax yet after all that, the kitchen isn't using the mount points I put but instead uses the default value "mount("MTD", "system", "/system")".
Any help?
bump
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
iZLeeP said:
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
Click to expand...
Click to collapse
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
black_fire21 said:
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
Click to expand...
Click to collapse
What's your device and android version? Much better if you could post on your device's specific thread.
It's a local phone called starmobile quest, running jellybean. Sadly, there is absolutely no support for the device not even from the manufacturers. There are no developers either. The only thing we have is root and cwm.