[Q] How do I make updater-script file? - Android Q&A, Help & Troubleshooting

I really want to create a rom and I'm doing everything right with the Android Kitchen but after I flash my rom I get status 6/7 errors in CWM.
Can someone explain me please how I do updater-script file that don't provide this errors?

Ok but, you need to tell us what errors are you getting...

RoberGalarga said:
Ok but, you need to tell us what errors are you getting...
Click to expand...
Click to collapse
Status 6 and sometimes status 7.

Huh? There aren't any other errors, like "no such file bla,bla,bla"?

There is an updater-script FAQ in Android Software General Section. Post your updater-script there, they will surely help you.
I would have given you a link but I am on mobile now

Related

[Q] assert failed: write_raw_image("tmp/boot.img","boot")

i believe this question is asked before, but the search function is not working at the moment.
I am using a Incredible S with S-OFF, installed with a custom recovery that confirm working with some other rom.
i decided to make one rom my self, i setup the Kitchen enviroment, and extracted the official RUU follow the tutorial, everything goes fine.
until i copied it to my SD card and trying to flash, i will get the following messsage
assert failed: write_raw_image("tmp/boot.img","boot")
can anyone help me? i had tried different setting for and make about 10 rom but all return the same message.
thank you.
chchia said:
i believe this question is asked before, but the search function is not working at the moment.
I am using a Incredible S with S-OFF, installed with a custom recovery that confirm working with some other rom.
i decided to make one rom my self, i setup the Kitchen enviroment, and extracted the official RUU follow the tutorial, everything goes fine.
until i copied it to my SD card and trying to flash, i will get the following messsage
assert failed: write_raw_image("tmp/boot.img","boot")
can anyone help me? i had tried different setting for and make about 10 rom but all return the same message.
thank you.
Click to expand...
Click to collapse
The same problem happened on the myTouch 4G but works with this:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
Let us know if it works...
You can send the "update-script" to me,then let me give a look.
My email addrress:[email protected]
Or just paste it here so that it can help everyone.
dsixda said:
Or just paste it here so that it can help everyone.
Click to expand...
Click to collapse
Well.Take it onder in the web,let me try to download it.
So,I can take a look.
dsixda said:
Or just paste it here so that it can help everyone.
Click to expand...
Click to collapse
Maybe it is this:"write_raw_image tmp/boot.img boot"
zeaxion said:
Maybe it is this:"write_raw_image tmp/boot.img boot"
Click to expand...
Click to collapse
No .... that is wrong syntax. Won't even work in an update-script. For the Incredible S you need an updater-script (not update-script). Commands are followed by parentheses, with each parameter followed by a comma, and then a semi-colon at the very end. Run the kitchen on your ROM to get the proper syntax.
Anyways, nothing can be done at this point unless the original poster provides more detail, like at least posting his updater-script.
I'm no developer but I believe it should be write_raw_image BOOT:boot.img
Correct me if I'm wrong
Sent from my Zio using XDA App
Mattix724 said:
I'm no developer but I believe it should be write_raw_image BOOT:boot.img
Correct me if I'm wrong
Sent from my Zio using XDA App
Click to expand...
Click to collapse
That's correct syntax, but it doesn't work on newer htc devices because of the new filesystem formats. Boot.img has to be copied to /tmp folder before it can be flashed to device. You have to use updater-script to accomplish that.
dsixda said:
The same problem happened on the myTouch 4G but works with this:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
Let us know if it works...
Click to expand...
Click to collapse
That's from ADB? My MT4G is stuck at:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
Any help is greatly appreciated. Stuck on a bootscreen in a bad way
I never had any issues using
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
in my updater-script for Incredible S.
lars.oakland said:
That's from ADB? My MT4G is stuck at:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
Any help is greatly appreciated. Stuck on a bootscreen in a bad way
Click to expand...
Click to collapse
Status 7 usually means you are using the wrong update-binary.
dsixda said:
Status 7 usually means you are using the wrong update-binary.
Click to expand...
Click to collapse
For us that know little can you elaborate and what that means exactly?
Per your previous answer I tried using an updater based on other devs work and I still get the same error on my g2.
I just wanted to add that I do run the error check and it says the update binary fine. No errors.
chchia said:
assert failed: write_raw_image("tmp/boot.img","boot")
Click to expand...
Click to collapse
Should tmp/boot.img be /tmp/boot.img?
Mioze7Ae said:
Should tmp/boot.img be /tmp/boot.img?
Click to expand...
Click to collapse
Good catch!
rsxtypes72 said:
For us that know little can you elaborate and what that means exactly?
Per your previous answer I tried using an updater based on other devs work and I still get the same error on my g2.
I just wanted to add that I do run the error check and it says the update binary fine. No errors.
Click to expand...
Click to collapse
Update-binary is not the update-script.
The update-binary file is supposed to be included with the updater-script and contains all the command implementations that are used in the script... however there are three main types of update-binary and you have to know which one to include. They are mostly differentiated by the number of parameters supported for the 'mount' command for your updater-script.
All I the roms I have made have both the update and updater scripts included. That's why I'm stumped. I am using the leaked gb rom for g2. Oh well. Thank you for everything.
I'm gonna try to do and root the boot.img myself. Decompile and compile.
Sent from my T-Mobile G2 using XDA App
rsxtypes72 said:
All I the roms I have made have both the update and updater scripts included. That's why I'm stumped. I am using the leaked gb rom for g2. Oh well. Thank you for everything.
I'm gonna try to do and root the boot.img myself. Decompile and compile.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
On your G2 you should have only an update-script in the ROM, or else the two other files (updater-script and update-binary), not both at the same time. The updater-script is a more advanced script than the update-script yet very similar.
The new versions of ClockworkMod only support the updater-script + update-binary however.
dsixda said:
The new versions of ClockworkMod only support the updater-script + update-binary however.
Click to expand...
Click to collapse
This is why the roms have both. I have not come across a single htc vision rom that only has an update-binary in it. They all have both
Sent from my T-Mobile G2 using XDA App
Update.
I just wanted to add that I have tried countless times to make a rom. I check that update script has no error and still I get the same error.
The weird thing is if I use a custom rom from one of the devs that does boot and I use the kitchen to go from edify to amend and then try to
convert it back later after I have made changes using the kitchen it wont boot and results in same write error.
Has anyone been able to make a bootable vision rom using the kitchen? If you have can you tell me where I can look or can you give me some answers. Yes I have checked google. No luck. Thanks
Im almost ready to give up.
I did make one rom that booted up and worked fine. Except when i went thru the steps to make the zip I removed the updater-script and update-binary created by the kitchen and replaced them with the udpater-script and update binary from one of the dev roms I use. This is the only way I have gotten a rom to flash and boot.
Just a thought. I know you said the htc vision is supported but would adding an edify_def for it help solve the problem?
Sent from my T-Mobile G2 using XDA App

Does Dsixda's ROM Kitchen work with Galaxy S3?

I've been wanting to try the kitchen out to see if I can try deodexing and zipaligning etc on the stock touchwiz ROM I'm running.
Do you think it would work? (despite it being discontinued)
yes it works still, works on ics & jellybean (i use it myself to deodex and zipalign)
Theshawty said:
I've been wanting to try the kitchen out to see if I can try deodexing and zipaligning etc on the stock touchwiz ROM I'm running.
Do you think it would work? (despite it being discontinued)
Click to expand...
Click to collapse
Yes dxixda kitchen works but you will need to add another file with gs3 parameters in the edify_defs folder with name m0..still the updater-script does not work . It gives me errors in the installing boot.img stage.. . Anyways you can use the kitchen to create your rom and then package your rom manually using updater-script and update-binary from some other working rom.. Then sign it..
If you or anyone finds a solution to that problem do let us know..
:thumbup:
Sent from someone in the Milky Way
zoot1 said:
but you will need to add another file with gs3 parameters in the edify_defs folder with name m0
Click to expand...
Click to collapse
Where do I find such file?
zoot1 said:
Yes dxixda kitchen works but you will need to add another file with gs3 parameters in the edify_defs folder with name m0..still the updater-script does not work . It gives me errors in the installing boot.img stage.. . Anyways you can use the kitchen to create your rom and then package your rom manually using updater-script and update-binary from some other working rom.. Then sign it..
If you or anyone finds a solution to that problem do let us know..
:thumbup:
Sent from someone in the Milky Way
Click to expand...
Click to collapse
I have a file for myself will upload it here once I reach home.. On my way back.. Hopefully you can see what is wrong.. I tried to get help from wanam also but we could not find the problem..
Edit: here you go..put the m0 file in the edify_defs folder..check if you can find any problem with it..
Sent from someone in the Milky Way
zoot1 said:
I have a file for myself will upload it here once I reach home.. On my way back.. Hopefully you can see what is wrong.. I tried to get help from wanam also but we could not find the problem..
Edit: here you go..put the m0 file in the edify_defs folder..check if you can find any problem with it..
Sent from someone in the Milky Way
Click to expand...
Click to collapse
I don't know anything about stuff like that
I'm a complete noob and just wanna try to deodex and stuff
Theshawty said:
I don't know anything about stuff like that
I'm a complete noob and just wanna try to deodex and stuff
Click to expand...
Click to collapse
Deodexing will work just fine..no probs..some times you might get an error with one or two apps..just use the option to deodex a single app and you will be good to go..
:good:
Edit:
Most important change the api level to 16 before deodexing..
just make a copy of your zipped rom, drop it into the working folder, deodex the files you want to and then pull those files out of the working folder and drop them into the original rom zip folder (minus the original odexed files)
no need to change anything, no need to drop new files in or mess with update script
as you will use your existing update script/meta inf folder blah blah blah, it means you can say yes to the mods the kitchen wants to make as you will only be taking the deodexed files from there, nothing else
(does that make sense? - im guessing you will ignore this anyway like my previous post))
Darkside Agent said:
just make a copy of your zipped rom, drop it into the working folder, deodex the files you want to and then pull those files out of the working folder and drop them into the original rom zip folder (minus the original odexed files)
no need to change anything, no need to drop new files in or mess with update script
as you will use your existing update script/meta inf folder blah blah blah, it means you can say yes to the mods the kitchen wants to make as you will only be taking the deodexed files from there, nothing else
Click to expand...
Click to collapse
Thanks, will try this.
Darkside Agent said:
(does that make sense? - im guessing you will ignore this anyway like my previous post))
Click to expand...
Click to collapse
Uh, sorry about that. I totally missed your post!
Did you get it all sorted in the end?
Darkside Agent said:
Did you get it all sorted in the end?
Click to expand...
Click to collapse
Nah, I basically said "f*ck it and deleted the whole thing.
Gonna let someone else deal with zipaligning, deodexing and all that.
Theshawty said:
Nah, I basically said "f*ck it and deleted the whole thing.
Gonna let someone else deal with zipaligning, deodexing and all that.
Click to expand...
Click to collapse
You need Patience my friend..
zoot1 said:
You need Patience my friend..
Click to expand...
Click to collapse
One of many things I lack and will probably always lack.
Sorry for dragging out an old thread but I thought I would have a go with this. I have the kitchen installed, I have put I9300XXDLI5_I9300OXADLI5_I9300XXDLI5_BTU.zip in the original_update and have the m0 file in tools/edify_defs
I then try and extract the ROM but I get an error Error: No system folder found!
How can I not even get started? I must be missing something basic here!
Kangburra said:
Sorry for dragging out an old thread but I thought I would have a go with this. I have the kitchen installed, I have put I9300XXDLI5_I9300OXADLI5_I9300XXDLI5_BTU.zip in the original_update and have the m0 file in tools/edify_defs
I then try and extract the ROM but I get an error Error: No system folder found!
How can I not even get started? I must be missing something basic here!
Click to expand...
Click to collapse
IIRC, the archive file must be a tar archive containing at least a system.img.
Sent from my GT-I9300 using Tapatalk 2
Theshawty said:
IIRC, the archive file must be a tar archive containing at least a system.img.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Can't I start with the ODIN file of the leaks? It must have a system image in it? Where do you start with this? I thought a whole flashable ROM would be ideal.
Kangburra said:
Can't I start with the ODIN file of the leaks? It must have a system image in it? Where do you start with this? I thought a whole flashable ROM would be ideal.
Click to expand...
Click to collapse
Extract the tar file and put the system.ext4.img and boot.img in the update folder.. Then Dxixda kitchen will recognize it..
Sent from the iPoop killer ==>>>
Kangburra said:
Can't I start with the ODIN file of the leaks? It must have a system image in it? Where do you start with this? I thought a whole flashable ROM would be ideal.
Click to expand...
Click to collapse
Oh yeah, I forgot, the system.img must be coverted from yaffs img to an ext4 file. I believe the utility is called ext2fs (or something like it)
Dsixda's tool should provide that program anyhow.
Well I unzipped the ROM and untarred the md5 and then it at least got me started. I am now just working out what I can do and what I need to get. Thanks for your help.
[edit]Well I built the ROM and tried both the update and updater scripts but both fail. Will go and re-read the help. [/edit]
Kangburra said:
Well I unzipped the ROM and unatarred the md5 and then it at least got me started. I am now just working out what I can do and what I need to get. Thanks for your help.
[edit]Well I built the ROM and tried both the update and updater scripts but both fail. Will go and re-read the help. [/edit]
Click to expand...
Click to collapse
Well that is the problem which I am not to work out yet.. As Dxixda kitchen does not support s3
Best way it to use meta-inf folder from other rom..
Sent from the iPoop killer ==>>>

[Q] Help!!! how to add new device in dsixda kitchen

How to add new device in dsxida kitchen?
what do you mean by that ?
we just add new rom as a base in it
in kitchen there is a folder called
original_update
copy the zip file in that folder, open kitchen and select first option of setup working folder
Sent from my GT-S5670 using xda premium
soham jambhekar said:
what do you mean by that ?
we just add new rom as a base in it
in kitchen there is a folder called
original_update
copy the zip file in that folder, open kitchen and select first option of setup working folder
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
You can't just put the zip file in original_update. Kitchen has to be configured for your device, or it will not work. I'd like to know how to do that as well.
klembo1957 said:
You can't just put the zip file in original_update. Kitchen has to be configured for your device, or it will not work. I'd like to know how to do that as well.
Click to expand...
Click to collapse
Nope, there is no such necessity
OK
iamareebjamal said:
Nope, there is no such necessity
Click to expand...
Click to collapse
OK then, if it isn't necessary to configure the kitchen for your device, then how can you make it work with your device? I am just a NOOB, let's make that perfectly clear. However, I followed the directions to the letter, and read up on the kitchen before trying it. I had no success using the kitchen to create a rom that I could successfully flash.
I thought that I would have to do something with the edify defs files first, adding my device before it would work. I just never got that far yet (I only play with this part time, when I have a chance to do so.) If I don't have to add my device, and you have some idea what I may have done wrong, please enlighten me. I obviously need the help. Thanks!
klembo1957 said:
OK then, if it isn't necessary to configure the kitchen for your device, then how can you make it work with your device? I am just a NOOB, let's make that perfectly clear. However, I followed the directions to the letter, and read up on the kitchen before trying it. I had no success using the kitchen to create a rom that I could successfully flash.
I thought that I would have to do something with the edify defs files first, adding my device before it would work. I just never got that far yet (I only play with this part time, when I have a chance to do so.) If I don't have to add my device, and you have some idea what I may have done wrong, please enlighten me. I obviously need the help. Thanks!
Click to expand...
Click to collapse
You put any custom ROM for your device in there, configure it for that file (meaning that show it the file you're working on), replace it's system folder with the stock deodexed system folder.
Now, you're ready. Do your modifications. Add features. Build. Zip
Now, the important part.
Kitchen updater-script doesn't work on our device in some case. Use any custom ROM updater-script (with permission and credit), and voila!
There is a complete guide on it in Development section too.
iamareebjamal said:
Nope, there is no such necessity
Click to expand...
Click to collapse
I have tried the kitchen with my phone before, (LG Spectrum/VS920), and the ROMS generated by it will not work. It has something to do with the "edify defs" file I believe. I read it somewhere before in these forums. If your device isn't supported, it has to be added, or at least that's what I've come to understand. If someone can point me in the right directrion (adding my phone so it is supported by the kitchen), I'd appreciate it greatly.
klembo1957 said:
I have tried the kitchen with my phone before, (LG Spectrum/VS920), and the ROMS generated by it will not work. It has something to do with the "edify defs" file I believe. I read it somewhere before in these forums. If your device isn't supported, it has to be added, or at least that's what I've come to understand. If someone can point me in the right directrion (adding my phone so it is supported by the kitchen), I'd appreciate it greatly.
Click to expand...
Click to collapse
Only thing is that it's updater-script doesn't work
You have to add yours
iamareebjamal said:
Only thing is that it's updater-script doesn't work
You have to add yours
Click to expand...
Click to collapse
That's all? Just add that and it will work? OK, I'll give it a try. Thanks.
klembo1957 said:
That's all? Just add that and it will work? OK, I'll give it a try. Thanks.
Click to expand...
Click to collapse
did it work ?

[Q] Please Guide Me Devs,

I am creating a cutom rom for mu mt6589 device using cygwin, cygwin tool created the udater-script file but when i tried to flash my
custom rom i've got an error in flashing. it is beacause of wrong mout point of updater-script generated by cygwin?
questuin: how to i find mount points and edit lines on updater-script generated by cygwin?
sorry if i've been posted in wrong section.. im so totally noob.
donzkie said:
I am creating a cutom rom for mu mt6589 device using cygwin, cygwin tool created the udater-script file but when i tried to flash my
custom rom i've got an error in flashing. it is beacause of wrong mout point of updater-script generated by cygwin?
questuin: how to i find mount points and edit lines on updater-script generated by cygwin?
sorry if i've been posted in wrong section.. im so totally noob.
Click to expand...
Click to collapse
Wrong mount points in updater-script and invalid update binary. You should have checked first with MTK Droid Root & Tools your mount points and find a suitable binary for your android version.
iZLeeP said:
Wrong mount points in updater-script and invalid update binary. You should have checked first with MTK Droid Root & Tools your mount points and find a suitable binary for your android version.
Click to expand...
Click to collapse
but how sir?
donzkie said:
but how sir?
Click to expand...
Click to collapse
I've already posted the link, go there and read. You'll find everything there.
ok sir i'll find it.
thank you.
iZLeeP said:
I've already posted the link, go there and read. You'll find everything there.
Click to expand...
Click to collapse
excuse me sir but i can't find any tutorial for this.

Please help me!!

TO ALL RESPECTED DEVS I'VEPORTING PARANOID ANDROID 7.2 FOR OTUS AFTER ALL THE THINGS ARE COMPLETE I ALWAYS FIND A ERROR THAT IS ERROR 7 ALSO I TRIED DELETING THE ASSERTS LINES OF UPDATOR SCRIPT PLEASE HELP ME SOMEONE THIS MAYBE DUE TO NOT REPLACING THE VENDOR FILES DURING PORTING BCOZ I COULD'NT FIND THE VENDOR FOLDER IN THERE HELP ME PLOX
ALSO IF ANYONE WANTS TO SEE THE FILE HERE IT IS : https://drive.google.com/open?id=0B3MmVlC0zmu-d0VHVmZ0N1pjZ0E
It's update script problem re check it..
In it Might b SHA velu wrong....
then how to do
Kuck7610 said:
It's update script problem re check it..
In it Might b SAHA velu wrong....
Click to expand...
Click to collapse
how should i continue now and whats saha velu i didnt found any like these can you plox help

Categories

Resources