[SOLVED] Creating an update.zip? - Android Q&A, Help & Troubleshooting

UPDATE: Problem fixed, thanks to florpor. The solution was to change the scripting language from Amend to Edify
Hi all,
I was wondering if I could get some quick advice from some more experienced users here on XDA?
Basically, I've been trying to put together a simple update.zip that I can flash that adds a tone to /system/media/audio/notifications. This is because after each time I flash an update for CM9 on my Galaxy S II, it replaces/removes the tone. Now, I could manually re-add them each time, but I'd like to find an alternative solution.
I've spent the past two hours or so searching around on how to put together an update.zip, and came across this tutorial and thought I was going well, until I tried to flash the zip and got an error message telling me that recovery no longer uses update-script files, and instead uses updater-script. So, I went ahead and renamed it, then re-zipped and re-signed the folders, and tried to flash it through CWM, which just returned an installation aborted message, with no details.
Any ideas? It's probably something really obvious that I'm mising, but it's driving me nuts. I've attached the update.zip, in case it helps.
Anyway, thanks for your time,
screamworks.

your updater-script didn't work because apart from changing its name, the scripting language it's coded in has changed from Amend to Edify.
try looking for posts about converting scripts between the two.. I think there's an automated script for this somewhere or you can do it by hand.

Thanks for that! After fixing that up, I got it to work. Thanks a million
screamworks.

Related

[Q] Making updater-script... doesn't make any sense!!

I was tying to make a fancy updater-script for an add-on for my ROM, but I kept getting a Status 6 error when flashing, so I stripped it back to nothing, just the most basic commands, and eventually got it to work. I made a copy, tried editing it to add the fancy stuff back in... broke again.
So I stripped the copy back to the basic commands... and it still breaks .
As far as I can see, the two files I have attached are identical in every single way, but one fails with a Status 6, the other flashes (BattMod works, update doesn't). Both are edited using gedit on Ubuntu, both zips are created in Ubuntu, neither are signed.
Can anyone see why, I am really tearing my hair out here... all I want to do is add some ui_prints and some progress bars .
I haven't looked it them yet, but make sure you are using the correct update-binary. Different ones support different number of parameters in the mount command.
Don't leave junk files in the update like updater-script.old, it's bad practice
My guess would be that since it's named update.zip, it's looking for a signature and it can't find one. Try renaming update.zip to battmod.zip and see if it works, or sign it first with testsign.
l0st.prophet said:
I was tying to make a fancy updater-script for an add-on for my ROM, but I kept getting a Status 6 error when flashing, so I stripped it back to nothing, just the most basic commands, and eventually got it to work. I made a copy, tried editing it to add the fancy stuff back in... broke again.
So I stripped the copy back to the basic commands... and it still breaks .
As far as I can see, the two files I have attached are identical in every single way, but one fails with a Status 6, the other flashes (BattMod works, update doesn't). Both are edited using gedit on Ubuntu, both zips are created in Ubuntu, neither are signed.
Can anyone see why, I am really tearing my hair out here... all I want to do is add some ui_prints and some progress bars .
Click to expand...
Click to collapse
With what are you editing it?
I've found out that editing it with notepad or any program won't work even if i'm using the right commands, so i decided to use amend2edify, you select an update-script (an update-script you can edit it with notepad without any problem) and it converts it into updater-script, updater-binary, but you have the possibility to edit anything in the output that you want and save it, or just copy-paste into the output the commands in your updater-script onto output by overwriting the converted output.
Don't know if i explained myself well.
Good luck
Try This One
Blank-CWM.zip
It's made for the Moto Photon, so you will need to:
1) Replace the update-binary with one from your phone.
2) Copy the file you wish to flash
3) Delete the txt files in it as well as any folders that you do not need to use in the process of flashing
4) Be sure to set the permissions to target the folder or file you are flashing. If you do NOT update this, you will end up in bootloops (Don't say I didn't warn you)
5) Flash away
Cheers!

[Q] how to replace files in a flashable zip

UOT zip aren't working. (it takes miserably long to try to combine all the different options) so i thought i was real clever trying to replace framework-res in a a theme download that does work. of course i got the "bad" error. i looked around, read something about unsigned files, got irritated, and quit searching for the answer.
how can i replace files in a flash-able zip?
i tried to simply open the zip in explorer and paste in a file.
if i can get past all these little small technical details i'll likely start putting together ports and original android themes for the atrix
bump?
anyone gotten UOT cook something usable?

[SOLVED] Creating an update.zip?

UPDATE: Problem fixed, thanks to florpor. The solution was to change the scripting language from Amend to Edify
Hi all,
I was wondering if I could get some quick advice from some more experienced users here on XDA?
Basically, I've been trying to put together a simple update.zip that I can flash that adds a tone to /system/media/audio/notifications. This is because after each time I flash an update for CM9 on my Galaxy S II, it replaces/removes the tone. Now, I could manually re-add them each time, but I'd like to find an alternative solution.
I've spent the past two hours or so searching around on how to put together an update.zip, and came across this tutorial and thought I was going well, until I tried to flash the zip and got an error message telling me that recovery no longer uses update-script files, and instead uses updater-script. So, I went ahead and renamed it, then re-zipped and re-signed the folders, and tried to flash it through CWM, which just returned an installation aborted message, with no details.
Any ideas? It's probably something really obvious that I'm mising, but it's driving me nuts. I've attached the update.zip, in case it helps.
Anyway, thanks for your time,
screamworks.

[Q] - dsixda's Android Kitchen HTC ONE X

Hi all!
Dont know if ill get flamed because this a noob post, but i searched all over, (xda, google) and i cant find a solution to my problem.
Im starting in this cooking deeds but i have problems setting up my kitchen.
I want to cook to an HTC ONE X, i got my dsixda kitchen setted up in a VM, everything works with no problem.
But i have this problem when flashing rom
QUESTION: When flashing my ROM I get the error "mount expects 4 args got 3" or similar.
This refers to the fact your mount command takes 4 parameters (e.g. ext4, EMMC, /dev/block/.., /system) and your update-binary file only checks for 3 parameters. You'll have to change the update-binary file to a compatible one, found under the /tools/update_files folder. Just copy the appropriate file and rename to update-binary. e.g. If you're going to be using MTD partitions, copy 'mtd-update-binary' to /META-INF/com/google/android as "update-binary".
Click to expand...
Click to collapse
i know this is an answered question on dsixda FAQ, but my english is not so good to understand the easy solution to fix it :\
i tryed some several ways to fix this but with no sucess.
i already tryed, copying the update-binary from my ROM.zip to /tools/update_files folder no sucess
i already tryed copying the update-binary from my ROM.zip to /META-INF/com/google/android before script conversion, but with no sucess
i even tryed to make the kitchen my device compatible, renaming the evita (HTC ONE XL) to enderavou (HTC ONE X) in /tools/edify-defs/ in a chance that will have the same "specs" .. but it outputs me another error when flashin :\
sorry for the noob question, i know the solution is in front of my eyes and its easy, but my english is weak and i cant figure this alone with the short explanation on FAQ.
so if anyone can give me a more detailed help, or maybe if anyone has the templates for HTC ONE X to make dsixda kitchen compatible, ill appreciate.
thanks all
I have replaced the updater script from a working rom with the one the kitchen comes up with. Depending on the changes you made in the kitchen that has worked well for me. Looks like your script needs to match the partition setup. Compare the 2 scripts, 1 from working and 1 from kitchen and you should be able to see the difference.
I am far from a dev, and I'm sure someone will chime in with better info. but maybe this will work for you.
onlychevys said:
I have replaced the updater script from a working rom with the one the kitchen comes up with. Depending on the changes you made in the kitchen that has worked well for me. Looks like your script needs to match the partition setup. Compare the 2 scripts, 1 from working and 1 from kitchen and you should be able to see the difference.
I am far from a dev, and I'm sure someone will chime in with better info. but maybe this will work for you.
Click to expand...
Click to collapse
that was my first solution ... no sucess... maybe if i try another updater from another rom ... hum but i dont see any logic .. its supose to work with update from any working rom

Creating Roms...

Hey everyone, Before you tell me there are other threads I can look at for instructions, I understand there are but I'm getting really stressed looking at them. For ages now I've wanted to create my own ROM and now i've finally gotten the chance. For the past 3 days solid I've been trying to look at these guides and instructions and its not that its going over my head, I understand what they're saying. But when I have an error and even if they cover it. I don't have the faintest clue on fixing it, for example:
I've been using Kitchen to build my ROM and configure it... my base is the nightly of Cyanogenmod 26/03/2013
And I can add things and stuff but as soon as I compile it into a ZIP again and try to flash it, I get either status 6... or status 0. I've read up and they say edit Update-script with notepad++ to make sure its in Unix code. Which it already is... When I switch that and just use UpdateR-script with binary... I get status 0. HOW on earth do I fix this xD
What do I have to edit in Notepad++ for this to work? Shall I paste the contents of all the scripts in here?
Please help, I don't want to lose my sanity over this.
Catley.
Bump - Please help ^^
Catley said:
Hey everyone, Before you tell me there are other threads I can look at for instructions, I understand there are but I'm getting really stressed looking at them. For ages now I've wanted to create my own ROM and now i've finally gotten the chance. For the past 3 days solid I've been trying to look at these guides and instructions and its not that its going over my head, I understand what they're saying. But when I have an error and even if they cover it. I don't have the faintest clue on fixing it, for example:
I've been using Kitchen to build my ROM and configure it... my base is the nightly of Cyanogenmod 26/03/2013
And I can add things and stuff but as soon as I compile it into a ZIP again and try to flash it, I get either status 6... or status 0. I've read up and they say edit Update-script with notepad++ to make sure its in Unix code. Which it already is... When I switch that and just use UpdateR-script with binary... I get status 0. HOW on earth do I fix this xD
What do I have to edit in Notepad++ for this to work? Shall I paste the contents of all the scripts in here?
Please help, I don't want to lose my sanity over this.
Catley.
Click to expand...
Click to collapse
The error you get while flashing the ZIP file could be due to an incorrect update-binary. In this case I could solve the problem almost always by replacing the update-binary by the one I extracted from the cache partition (cache.img) of a recent stock firmware.
Thank you, but where would I get that because I've been searching for a while for stock firmware so I could do something like that but I'm also on the side trying to write it from source code on ubuntu, and having a few problems with that too, so I've been more concentrated on that, I might make another thread asking what to do about writing source code because no matter how hard I look, everyone else can do it but me xD

Categories

Resources