Ok I have 2 scripts here, both install however both have issues. Any help to better understand what is wrong here would be great.
first is a edify script that imnuts made , however when I boot it i have no 3g at all and after 3 to 5 mins it reboots the phone
http://pastebin.com/qiuyrRHU
This one is mine but when you goto reboot after flashing it, the samsung logo comes up then reboots to samsun logo again then to recovery
http://pastebin.com/euQJNmyP
Now I know I am in the fascinate sections and I figure that there are tons of awesome devs in fascinate area however I am on a mesmerize and trying to make a edify script for Heinz 57.
With yours, try flashing a boot.img after flashing and see if it works.
Also, it's the same script for all phones with the same recovery, so it doesn't matter if you ask this in the Droid forums.
Sent from my SCH-I500 using XDA App
actually after some trial and error found it that the way to mount on our phone does not work with the way they had me mounting it.
I had to mount this way: run_program("/sbin/mount", "-t", "rfs", "-o check=no", "/dev/block/stl9", "/system");
Its all good now, thank you
oh and imnuts pointed out that i was missing some / in the permissions area.
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
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
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)
Hello everyone!
I am trying learning how to create cwm flashable items. I have some questions though.
While i was trying to see how an updater-script was made, i edited some scripts from cwm for themes, wallpapers etc.
I saw that some files have:
run_program("/sbin/unmount", "/dev/block/mmcblk0p2", "/system");
run_program("/sbin/unmount", "/dev/block/mmcblk0p10", "/system");
run_program("/sbin/unmount", "/dev/block/mmcblk0p12", "/system");
What does it stand for? Which is the difference between mmcblk0p2,mmcblk0p10 and mmcblk0p12?
Thanks in advance
Anyone?
Thhey are the mount points for the memory, they are different for each device. If you have some that work for your device that point to the system partition, then just use them. Changing them will mean you will get a bootloop, or the mod wont flash
gregbradley said:
Thhey are the mount points for the memory, they are different for each device. If you have some that work for your device that point to the system partition, then just use them. Changing them will mean you will get a bootloop, or the mod wont flash
Click to expand...
Click to collapse
Thanks mate, but what if i want to create a cwm for another device? How am i supposed to know which one fits?
See my flashable zip tool thread
On general section
Press thanks if I helped