I just suggest to update to edify since that is where things are going, sorry for coming off a bit short. I was in a hurry, for that I apologize. If you want help converting I will do what I can.. just remember I was just as shocked as you when I learned there were 2 update.zip format standards..
That's fine but apparently all of our update.zips are the edify format and everything works with your recovery. That is everything but fix1 which was sent out to everyone to fix a few things. But from what we can tell every zip we have is in the edify format and your recovery is working fine with our rom.
The one that I looked at, was just to run a shell script, and it was indeed in the amend format. I recognized it because I opened it up, and there was no updater-binary in there. In the amend format this was how it was done, since the recovery itself handled the parsing of the script file. Nowadays, the recovery only runs a binary to parse the script, included with the update script files (now called updater-script, and that too is in a different format)
Anyway, I am happy to hear you solved the problems and again, I don't want there to be any hard feeling between us, devs should all work together to come up with great stuff
edit: a great example of edify vs amend is a slayher kernel update.zip., He includes updater-script, updater-binary AND update-script to be compatible with all recoveries. If you crack one open you can clearly see the syntax differences in the script.
Yea no I've seen the binary file in every zip I've dealt with but had never heard of the edify or amend formats till u said that however anyway yes it should be devs working together to promote the community I totally agree
Sent from my Droid using DroidForums App
I for one am happy to see your latest post here on sourcery, total 180 and it says a lot, regarding your integrity and class.
You have to understand, though the entire community is not on sourcery, those that are will fiercely leap to attack those that put down or at least come across as putting down the two devs that we have grown to like and respect, due to the way they work and handle supporting their users.
Not to mention providing a very unique experience for us on OGs.
And immediate assistance and problem solving for anyone and everyone that asks, certainly only increases our enjoyment and lessens any worries that one might screw their phone up.
You do much the same I have noticed with those trying to work RZRecovery, and we all appreciate being able to directly deal with the developer rather than one of their underlings, usually lacking in full knowledge to help, knowledge only the developer possesses.
I wish all devs would work together, but it has become all to clear that in the Custom ROM world you have certain devs, not all, with egos the size of the mass of protesters in Egypt. As well as overinflated pride of ownership. Two psychological properties that unfortunately seem to derail most attempts at working in unison. Too many conductors and only one train, so to say.
And from what I have heard, regarding past attempts to work together, things seem to crumble quickly once the infighting begins. And once the train starts going down hill nothing stops its momentum until you have people, who now refuse to talk to or discuss others whom they once worked with on a project together, a project that fell off the tracks
I hope this combining of the minds goes well as it is only to the benefit of all.
And it seems like your recovery may be a really sweet addition to the flashing world. As I have read that thread for quite some time now and am just trying to figure one or two more things out before giving her a whirl as I never used SPRecovery only CWM, though I still choose to do everything myself when in recovery.
I shall cease babbling now.
To all unfortunate non bachelors, get those wallets open, and have a nice valentine's day with your beloved.
And for the lucky few who are single, good luck in the annual running of "find a depressed single woman on valentine's day and make her valentine's night!".