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.
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)
Hi all, my first post here, I hope its not in the wrong section
I know this will probably be a very noob question, but I have been trying to create a .zip file with my stock rom I downloaded from a site, (I have a HTM-H9500 [MTK 6582]), I was creating the zip in android kitchen, but whatever i do i always get Error: status 0 in CWM, I read that this would probably because of update-binary or updater-script, I have tried creating update-script (without the r) and CWM directly says that its very old and that i should create updateR-script, however when i do all the process again with updater-script I get this annoying status 0 error.
What can i do? I searched this topic in the net and all the sugestions people had said havent worked for me.
Thanks in advance and sorry for my bad english.
Replace the update-binary file from an existing custom ROM of your device with the ROM you made using kitchen that should do the job.
Also while adding the file to zip make sure you set the compression to store
Hit thanks if I helped.
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Replace the update-binary file from an existing custom ROM of your device with the ROM you made using kitchen that should do the job.
Also while adding the file to zip make sure you set the compression to store
Hit thanks if I helped.
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Hi! Thanks for the quick answer, the thing is because my phone is not very popular i havent found any other custom rom other than the stock specifically for my phone (thats why i was trying to port from another device that is very similar, but first i tried to do this process with my stock rom) so i dont have any other update-binary file other than this one.
About the other thing, how can i change the compression rate in android kitchen ?
Again, thanks a lot and sorry for my english
AlpinoSoyYo said:
Hi! Thanks for the quick answer, the thing is because my phone is not very popular i havent found any other custom rom other than the stock specifically for my phone (thats why i was trying to port from another device that is very similar, but first i tried to do this process with my stock rom) so i dont have any other update-binary file other than this one.
About the other thing, how can i change the compression rate in android kitchen ?
Again, thanks a lot and sorry for my english
Click to expand...
Click to collapse
Go to play store and download zipme app.
Create any flashable app using zip me and then copy it to PC. Open the META-INF Folder then com->android ->Google then open it and you'll see a update-binary file. That is your stock binary
Open the final zip after creating the ROM. If om Windows open the zip (ROM) created and open the zip created using zipme.
Copy the update-binary from zipme ZIP to kitchen created zip and when you'll do this you will see a menu that will ask that are you sure about adding this file, search around a bit and you'll see the compression option
Tech N You said:
Go to play store and download zipme app.
Create any flashable app using zip me and then copy it to PC. Open the META-INF Folder then com->android ->Google then open it and you'll see a update-binary file. That is your stock binary
Open the final zip after creating the ROM. If om Windows open the zip (ROM) created and open the zip created using zipme.
Copy the update-binary from zipme ZIP to kitchen created zip and when you'll do this you will see a menu that will ask that are you sure about adding this file, search around a bit and you'll see the compression option
Click to expand...
Click to collapse
Seriously, thanks lot, means a lot to me, im not used to get much help in forums haha, what you said worked flawlessly, now i get status 7 error, but this means where going somewhere, il keep digging to fix this.
Thanks again
AlpinoSoyYo said:
Seriously, thanks lot, means a lot to me, im not used to get much help in forums haha, what you said worked flawlessly, now i get status 7 error, but this means where going somewhere, il keep digging to fix this.
Thanks again
Click to expand...
Click to collapse
Glad to help friend
Status 7 is error with your mount points.
In your updater-script when you'll open it (open using NOTEPAD++ ONLY, don't use notepad or wordpad) you will see two lines as
Format ("MTD", "SYSTEM"); and other would be mount.
Check these two lines and replace them with your device mount paths
You'll be having no problem.!
Tech N You said:
Glad to help friend
Status 7 is error with your mount points.
In your updater-script when you'll open it (open using NOTEPAD++ ONLY, don't use notepad or wordpad) you will see two lines as
Format ("MTD", "SYSTEM"); and other would be mount.
Check these two lines and replace them with your device mount paths
You'll be having no problem.!
Click to expand...
Click to collapse
Thanks !
In my updater-script I have this two lines
format("MTD", "system");
mount("MTD", "system", "/system");
I know i should know this by now but what are you refering to with 'your device mount paths'?
Thanks a lot, trying to learn here
AlpinoSoyYo said:
Thanks !
In my updater-script I have this two lines
format("MTD", "system");
mount("MTD", "system", "/system");
I know i should know this by now but what are you refering to with 'your device mount paths'?
Thanks a lot, trying to learn here
Click to expand...
Click to collapse
Do you have a recovery.img for your device?
Extract it using kernel kitchen and then after extracting it you' ll get a folder named ramdisk.
Open it go to etc and then recovery.fstab.
Open it with notepad++ and see the mount paths for your device just copy and replace it.
Mount path is the line that tell CWM where to install the particular files. If you face any problems then attach your recovery.img and updater-script and I'll have look at it
Tech N You said:
Do you have a recovery.img for your device?
Extract it using kernel kitchen and then after extracting it you' ll get a folder named ramdisk.
Open it go to etc and then recovery.fstab.
Open it with notepad++ and see the mount paths for your device just copy and replace it.
Mount path is the line that tell CWM where to install the particular files. If you face any problems then attach your recovery.img and updater-script and I'll have look at it
Click to expand...
Click to collapse
Well i didnt had kernel kitchen so after downloading it and runing it i only found those 5 options:
1 work with boot.img files
2 work with kernel.sin and ftf files
3 work wih kernel.elf files
4 work with init ramdisk
5 editing bootsplash image
But nothing to extract recovery.img, i suposed that i should just change recovery.img name to boot.img and do the process but i get an empty folder in the output folder, what should I do?
Thanks thanks thanks again
Google this tool "std unpack" open to first link and download that tool.
Drag your recovery.img to STD unpack and you'll get your files.
Alternatively you can also use kitchen to unpack the recovery.img
Just go to advanced options then go to boot unpacking tools and follow steps as suggested
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Google this tool "std unpack" open to first link and download that tool.
Drag your recovery.img to STD unpack and you'll get your files.
Alternatively you can also use kitchen to unpack the recovery.img
Just go to advanced options then go to boot unpacking tools and follow steps as suggested
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Seriously, sorry to be this stupid, but i cant find anything googling "std unpack" "std unpack tool" or "std unpack download" just a bunch of c++ questions..
Thanks again..
EDIT: nevermind i did it with kitchen like you said in advanced options, this is what I have in recovery.fstab
# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
How should i change the lines: format("MTD", "system"); and mount("MTD", "system", "/system"); according to that?
Again, thanks for the extensive help
AlpinoSoyYo said:
Seriously, sorry to be this stupid, but i cant find anything googling "std unpack" "std unpack tool" or "std unpack download" just a bunch of c++ questions..
Thanks again..
EDIT: nevermind i did it with kitchen like you said in advanced options, this is what I have in recovery.fstab
# mount point fstype device [device2]
/misc emmc /dev/misc
/data ext4 /dev/block/mmcblk0p7
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
How should i change the lines: format("MTD", "system"); and mount("MTD", "system", "/system"); according to that?
Again, thanks for the extensive help
Click to expand...
Click to collapse
Ready to help always
Use this command for format.
format("ext4", "EMMC", "/dev/block/mmcblk0p5", "system") ;
For mount statement just replace format with mount and keep rest same.
Tech N You said:
Ready to help always
Use this command for format.
format("ext4", "EMMC", "/dev/block/mmcblk0p5", "system") ;
For mount statement just replace format with mount and keep rest same.
Click to expand...
Click to collapse
Thanks again man...
Im still getting status 7 error but now it says format() expects 3 args, got 4
AlpinoSoyYo said:
Thanks again man...
Im still getting status 7 error but now it says format() expects 3 args, got 4
Click to expand...
Click to collapse
Update-binary error only. Try to get a update-binary for your mobile model this is only the problem rest everything is ok.
Also keep a nandroid backup ready if anything goes wrong just explore your device. If it is a Mediatek6557 (just a example) device then search for the any handset running the board of mtk 6557 and download it's custom ROM and replace update-binary and it will work. Download CPU-Z for your phone from play store to get detailed information of your device and board.
Tech N You said:
Update-binary error only. Try to get a update-binary for your mobile model this is only the problem rest everything is ok.
Also keep a nandroid backup ready if anything goes wrong just explore your device. If it is a Mediatek6557 (just a example) device then search for the any handset running the board of mtk 6557 and download it's custom ROM and replace update-binary and it will work. Download CPU-Z for your phone from play store to get detailed information of your device and board.
Click to expand...
Click to collapse
Well thanks, i'll kep searching, one last thing, why would my update-binary wont work? i mean, im using stock rom and trying to flash stock rom again, why would i need a different one?
AlpinoSoyYo said:
Well thanks, i'll kep searching, one last thing, why would my update-binary wont work? i mean, im using stock rom and trying to flash stock rom again, why would i need a different one?
Click to expand...
Click to collapse
You using stock ROM but according to device it doesn't know stock or custom for it everything we flash is just a external source which is implemented in it.
Tech N You said:
You using stock ROM but according to device it doesn't know stock or custom for it everything we flash is just a external source which is implemented in it.
Click to expand...
Click to collapse
Well like you said i kept searching and found an update binary that did the trick and everything flashed just fine, however, even though i didnt get a bootloop, when i turn on the phone it shows the brand logo as always and then its just a black screen.
Any ideas? Thanks !!
Check the permissions in updater-script to and hope you can boot into recovery, restore the phone to old state and then using kitchen convert your updater-script (edify) to update-script (amend) and check for errors. Ignore error with the format and mount command
Sent from my C5302 using XDA Free mobile app
Tech N You said:
Check the permissions in updater-script to and hope you can boot into recovery, restore the phone to old state and then using kitchen convert your updater-script (edify) to update-script (amend) and check for errors. Ignore error with the format and mount command
Sent from my C5302 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again, what should i look for in permissions in updater-script?
and update-script (without r) gives me problems when i try to flash in cwm
Update-script is old format and isn't used much more. New devices use updater-script for flashing
Sent from my C5302 using XDA Free mobile app