yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] thefredelement:
I don't know what I'm missing here but I only use CM really and any backups after 2.5.0.1 won't restore right. I mean if it's making the zip itself it should be in the right version right?
[EVO 4G Android Development] GIGZ1971:
Thanks

Yeah I just noticed it myself, still like CWM because I bought the Rom Manager App. :D
[EVO 4G Android Development] revel1973:
Went to Rom Manager, flashed 2.5 and it went smooth. Installed Myn's Warm 2.2 Rls 4 and no issues!!!!. My thanks to all of you because just by reading, I was able to figure it out!!!
[EVO 4G Android Development] stargaterules:
So just to understand this problem. Once all of the developers update their zips to edify and you upgrade to new 3.0 receovery, you should be able to flash those zips without a problem. What happens to all of your old nandroid backups that used the old recovery, ie 2.5? Will you have to downgrade the CWM every single time to restore older backups? I hope this makes sense.
[EVO 4G Android Development] chuunarusamurai:
You got it.
[EVO 4G Android Development] stargaterules:
Damn, what a headache. I wish they have older backups convert automatically.
[EVO 4G Android Development] Omegablues:
CWM 3.X

Thanks for the update Koush. For you folks distressed about this, buy ROM Mgr and anytime you want to install Amend .zip versions just flash Amon Ra from ROM Mgr and flash back to CWM 3.X when done. It takes all of a couple of minutes.
[EVO 4G Android Development] theothermillion:
I'm still using 2.5.0.1 and have never had an issue with flashing or restoring anything. What I am getting from all of this is that I will have to upgrade my recovery to flash most future ROM's and mods? If that is the case, will I break anything keeping 2.5.0.1 until I find something to flash that requires the new recovery?
[EVO 4G Android Development] lowetax:
FWIW

[Originally Posted by supdawg]

So when I see a flashable zip floating around that I want to install, I need to know which version it was created in (edify or amend)?

CWM 2.5.0.1 = only can flash Amend scripts (flashable zips)

CWM 3.0.0.x = only can flash Edify scripts (flashable zips)

Is that what I am reading?

[Koush post reply]

2.5.0.1 can flash both. (it is an eclair based recovery)

3.0.0.x can only flash edify. (It is a gingerbread recovery)

http://xdaforums.com/show...3&postcount=30
[EVO 4G Android Development] thefredelement:
So if 2.5.0.1 can flash both what's the problem?
[EVO 4G Android Development] Androidious:
Maybe a big cause to why zips that are flashable are still using the amend command as opposed to the edify command is that tools used to create these zips are floating around that still use the amend command. And these scripts/tools have yet to be updated since it was never really an issue until GB came out.

If this is the case, we need to get cracking at updating these tools/scripts to fix the issue.

Just my 2¢. Who knows if its even close to being correct though. Thanks for clearing this up tho Koush :-)

Sent from my sweet HTC EVO running Myn's Warm TwoPointTwo RLS 4.95 (RLS 5 Beta)
[EVO 4G Android Development] Koush:
Here's a 2.6 version (supports both script versions) and backs up wimax:

http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.6.0.0-supersonic.img

PLEASE TEST THIS FOR ME!

Please note, that once CM7 is released, Clockwork 3.0 WILL BE A REQUIREMENT.
[EVO 4G Android Development] :
I can't flash Myn's latest ROM with CW. I downgraded to 2.5 and tried and it hangs on the white splash screen. I tried to flash using Among Ra and it doesn't work either, same issue. What am I missing?
[EVO 4G Android Development] roscoenr:
You are on the wrong radios
[EVO 4G Android Development] davidnjessicacruz:
Koush,

I just wanted to say thank you for all the work that you do. I've used Rom Manager since I had the Droid 1 when it came out. Keep up the good work. Your freakin awesome! Oh, and btw I've been using your recovery using Lithids compile of CM7 RC0 with no issues. :-)
[EVO 4G Android Development] roscoenr:
so just so im clear after CM7 comes out you will no longer suport the Amend scripting. Just tring to get this strait for my themes. Thank you
[EVO 4G Android Development] firestetz:
First great work have used CW and RA both but mainly RA for wimax keys decided to use new CWM today and found I can't do anything with it. When I select an option the menus disappears and I have to do a batt pull to reboot. So my question is does the hboot have anything to do with this our does it matter which hboot I'm on? By the way I'm hw003 hb.96

Edit: sorry hb.93 just checked to make sure.

Sent from my warmed up ripped up and slain evo beast
[EVO 4G Android Development] Hemidroids:
3.0.0.5 wont let me into recovery.

It goes into the boot loader just fine but when I select recovery it simply goes back to the boot loader and I try to select recovery. Lather rinse repeat.

I downgraded to 3.0.0.3 and it works fine.

HTC EVO

HBOOT 2.02
[EVO 4G Android Development] roscoenr:
here is a way that myn usses for his roms
[EVO 4G Android Development] Ep3n3wp:
How is 2.6 working out?
[EVO 4G Android Development] joshua_:
I'm testing it now on my Evo. If it successfully restores a WiMAX image, I'll call it good and pack up unrevoked 3.31.
[EVO 4G Android Development] joshua_:
Looks good to me. Packin' it up now.
[EVO 4G Android Development] Ep3n3wp:
So everything should work the same as 2.5 but just now includes wimax backup?

As in no problems with flashing anything or should I just stay on 2.5?

Thanks
[EVO 4G Android Development] evohog:
Just flashed 2.6.0.1 as latest recovery.
[EVO 4G Android Development] uh60james:
flashed 2.6.0.1 all seems ok with it so far
[EVO 4G Android Development] Rydah:
Wouldn't it be better if we already started using newer clockwork recovery and had an easy way to update our zips ?
[EVO 4G Android Development] r.storm85:
Ok maybe I missed something here, but if CWM 2.5 will flash both types of zip files, why would i want to update to 3.0 and be able to flash only the new type zips?? I dont see the point....wimax backup isnt that important you can do it manually or just dont flash radios like me.

Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
[EVO 4G Android Development] terryazthompson:
Koush,

I am wondering if you might be able to shed some light on the how different versions of nand erase block sizes (and different partition sizes) effect your recovery. Some technical and also which versions of your recovery have issues with this (if any)?
[EVO 4G Android Development] xdp:
Why is clockwork 3 required for cm7 builds if 2.5/2.6 can flash zips made with edify? Sorry this wasn't something I gathered from the op ...I just thought that rom makers had to use edify for gingerbread builds, but that old or new clockwork would flash them. I've built cm7 from source and flashed it okay from clockwork 2.5...was that just because the cm team hasn't merged the right stuff to break compatibility with that yet?

Also, I noticed that amon RA mentioned support for new evo partition sizes in his new 2.1.1 release...is that something clockwork needed modified for as well?

Thanks for all your work.
[EVO 4G Android Development] davidstjohn1:
Koush im sorry to bother u im confused sorry for being a noobie, I have a stock evo rooted with 3.3 unrevoked. what am i supposed to do just run 3.31 over it? or use the s- off tool first??? i am not sure and dont wanna mess up my evo. please advise me id really appreciate it , or do i just leave it alone? I wanted to add that i did have problems with texts not going out and failed also idk if that has anything to do with root.
[EVO 4G Android Development] lordsargon:
Another person having problems with 3.0.0.5

Koush,

I too am running into problems with 3.0.0.5 not booting into recovery mode. It boots into the boot loader, but never into recovery.

3.0.0.4 works fine.
[EVO 4G Android Development] IceCreaMan:
thanks!, i think i will finally apply the ota and newer unrevoked now since most of the issues have all been sorted out.

glad i waited this time.
[EVO 4G Android Development] Jerryatric:
stuck in bootloader

Ever since any of the 3.0 whatever updates I have been unable to access the recovery. I am stuck in the bootloader. The only way I can access recovery is to install Amaron (spelling?). I would go back to the 2.5 versions but rom manager doesn't even offer those versions as an option. I'm no programmer so I don't know how to fix this.
[EVO 4G Android Development] EndlessDissent:
If you choose the option to install the newest Clockwork, it will install 2.6.0.1, which is the 2.5.x series + wimax backup.
[EVO 4G Android Development] Justin.G11:
Quick note on Amend and it's eventual removal:

As far as I know, there's no reason you _have_ to remove Amend in order to install Gingerbread ROMs, it's just pointless extra code. Both CW and RA both flash CM7 RC0 just fine (as well as the Kanged offshoots). The whole explanation just seems inaccurate to me.

Were I you, I'd leave the Amend support alone until after HTC releases gingerbread ROMS. If you think about it, CM and MIUI are probably the only AOSP and truley independent ROMs out there, the rest are Kanged off that or the stock Sense... which is still 2.2 and thus very possibly compiled using Amend. Once HTC releases Gingerbread, the ROM Devs will be _forced_ to compile using the new method, and then you can safely remove that legacy code.

Until then: what's the rush? Just leave it in there until market forces push them off and avoid the headache of having a wonderful tool getting unnecessary bad press.
[EVO 4G Android Development] jerseymonkey:
Trying to port the existing Market 2.2.7 ZIP that was posted on XDA. As I am new to Android scripting, I documented with what I've tinkered with at the moment, here: http://xdaforums.com/showthread.php?t=898289

If anyone can provide some tips on how to go forward I'd be grateful.
[EVO 4G Android Development] bmwboyee:
yeah, having major problems as well. sucks.
[EVO 4G Android Development] Black SER:
I'm going to wait before installing this.

Sent from my hacked Tapatalk Pro
[EVO 4G Android Development] Jerryatric:
I did try that, but thanks for trying to help. I've flashed the 2.6.0.1 and all of the 3. updates and none have worked. I am using fresh 3.5 and after installing that, I put their radio updates on. I don't remember using recovery since that so could that have caused an issue?

My bootloader screen says HBOOT-0.76.2000 and Radio-2.15.00.11.19

I don't know if that helps. I much appreciate how ROM manager makes it easy to change and backup roms but it is frustrating when it doesn't work!
[EVO 4G Android Development] generalExpert:
Backup compatibility

Does anyone know if the backups made are all compatible regardless of CWM version?

For instance, I did a full backup while in 3.0 but have since reverted to 2.5.0.1. So, I need to know if the backup made before is still compatible with the downgraded version(s).

By the way 2.5.0.1 is working perfectly for me.
[EVO 4G Android Development] leenypost:
someone correct me if I am wrong but 3.0 backs up wimax and 2.5 does not so I would assume if it does work, it will not restore the wimax since 2.5 does not back that up... Or it might not work at all.

You could make a backup using 2.5 right now and then try and restore the one made with 3.0... If that doesnt work just restore the one you are about to make with 2.5
[EVO 4G Android Development] SITH16:
So are the cache wiping problems of clockworkmod solved with this latest version?
[EVO 4G Android Development] Justin.G11:
I would make another backup just to be safe, but here's my understanding:

CWM will make an image of each of the partitions then zip them all up and sign it. During restore it then reverses that process. So in theory it should still work as long as the image names inside the zip remains constant (which I believe it does)... but it will only restore the images its coded to look for (so a wimax image will get skipped as you downgraded to a version that does not backup that partition).

Now there is also a potential issue with the newer partition sizes as the older CWM didn't handle them correctly but if i read your previous posts you are not using the newer partition size so it shouldn't effect you anyway.

Again: it only takes a minute so to be safe I'd go ahead and re-backup. But it should be fine.
[EVO 4G Android Development] Justin.G11:
My understanding is that the cache wiping problems were related to the new partition sizes which is why only some people had that issue and others didn't. According to the notes he corrected this so the cache wiping problem (if you had it) should be solved as well.
[EVO 4G Android Development] SITH16:
I don't think I ever had the problem but I avoided clockworkmod for this reason. Just in case ya know. Now though I feel like it would be great to be able to flash roms on the fly and I would need to have clockworkmod to do this.
[EVO 4G Android Development] Undef:
Why now?

+1

Was there really a burning need to completely remove Amend support? Especially when you *know* how many ROMs depend on it? If they'll break themselves on GingerBread, why insist on breaking them now? ;-)

Sheriffs are needed, sometimes, Koush. But is that the role you really want to take?
[EVO 4G Android Development] Justin.G11:
I'm one of the "lucky guys" who never had this problem so my knowledge of cache wiping is not first-hand, but from all the posts I've read it seems resolved. Unlike some I've always preferred CWM because it integrates so brainlessly with ROM Manager and lets you do fun little extra things like regular backups on a schedule. I know "its not that hard to just copy the zip to the root of your SD" argument, but once you just select a ROM, click the options you want, then let it do the rest it's kind of hard to go back to the manual model unless you're trying to accomplish something specific.
[EVO 4G Android Development] generalExpert:
No sd-ext found?

ok, just successfully flashed to 2.6.0.1 using Rom Manager. I did a back-up and noticed that at one point it gives me a message of:

"No sd-ext found. Skipping backup of sd-ext."

Then moves on to generate md5 sum and finishes just fine.

I've seen this message before in a different version too. Also, the weird lines are back upon reboot...

Is this normal?
[EVO 4G Android Development] dj_L:
IIUC, Koush removed nothing, Google did. For how long to keep supporting legacy apps is the question here, and it seems that Google has answered that question for us. So, the question now becomes, how long should koush have keep two Android source trees up to date?

In defense of the ROM makers still using Amend, Google doesn't seem to stick to normal version numbering, rather using product names to define major releases.

Old stuff goes away at a major release, and Amend probably should have been gone come Froyo as it survived 2 major versions after being deprecated instead of the standard 1 major resease.

Bottom line, if you have legacy apps, or in this case ROMs that use the legacy updater, just use the legacy recovery. Koush even took the time to update the legacy version of his recovery to ease the transition period and still provided the extra features (wimax backup and new partition layout).
[EVO 4G Android Development] Jerryatric:
I just want to apologize for wasting everybody's time... including the dev. It appears I got ripped off when I bought a 32gb memory card for my phone and all the files that would go on it would get corrupted. I put the stock sd card back in and I was able to flash and run any of the recoveries just fine.

Now to get my money back from ebay!
[EVO 4G Android Development] Brandito:
it pays to buy name brand flash memory.

you can get lucky with cheap stuff, but any time something is storing data you don't care to lose, it's best to stick with a reputable brand.
[EVO 4G Android Development] Jerryatric:
It says Kingston.... but I'm thinking I need to stick with a reputable store too. It was from the U.S. but whatever, I'm never buying memory off ebay again.
[EVO 4G Android Development] John Kotches:
You are joking, right?

Cupcake (1.5)

Donut (1.6)

Eclair (2.0/2.1)

Froyo (2.2)

gingerbread (2.3)

honeycomb (3.0)

Each name has an associated version.

Swyped on my PC36100 using tapatalk!
[EVO 4G Android Development] cybertimber2007:
It supports both yes, but it doesn't support gingerbread... if I understood it right.
[EVO 4G Android Development] DiGi760:
I don't understand why everyone is so against the move to edify. Edify appears to something that anyone who has programmed in a C derived language should be able to pick up quickly. I know that not everyone programs, but if someone learned amend, they can learn edify.

Yes, the devs have to get their act together now and start using edify, but that won't be as hard as it sounds. Everyone who isn't cooking their own rom just needs to calm down and let the devs do their thing.
[EVO 4G Android Development] dj_L:
I take it that you've misread my comments. The operative word was _major_. In the list you posted above, Cupcake and Donut are both major version 1. Likewise, Eclair, Froyo, and Gingerbread share the same major of 2. Compatibility should be maintained across the major release.

Define major in the above, however, as Google, or rather many of their represenatives, at least in casual conversation, refer to all above listed as major revisions despite the version scheme. :-)

HTH
[EVO 4G Android Development] Brandito:
what versions of cwm support the 20k partition sizes?

for some reason the latest 3.0.0.5 and the 2.6 won't work, i get sent straight to the bootloader.

3.0.0.3 and amon ra 2.1.1 seem to be all that work from rom manager.
[EVO 4G Android Development] Justin.G11:
Can't comment on the "weird lines" but every version of CWM has given me that skipping "sd-ext message" so I'll go out on a limb and say it's normal.
[EVO 4G Android Development] Justin.G11:
That's incorrect: Koush himself said he removed support for Amend scripting assuming the dev world had done so as well. He basically underestimated how embedded that method was in the community.

To be clear, Amend was in 1.0 ... and nearly immediately depreciated and had Edify added as substitution in 1.5 ... it's life was very VERY short as it's limitations became apparent. But sometimes the motto is "if it ain't broke, don't fix it", especially when still learning a v1.x product.

Google did pick an odd time to finally stop supporting Amend, but depreciation technically occurred awhile ago and during Android's infancy where such depreciation should be expected.
[EVO 4G Android Development] dj_L:
Thanks for the clarification. Taking from comments of other affected devs, I was under the impression that it was removed in the 2.3 branch which the new recovery version was built against, not removal of external/custom code.

I suppose, as opposed to trying to pick through and intrpret hundreds of other comments, proper solution is to get off of my lazy butt and look for myself (which I still haven't done). :-)

Edit: Confirmed. Browsing about git, amend was _removed_ on 2009-07-14...not even a part of donut release branch. No idea when edify showed...git hist is really slow digging that far back, but was not in cupcake release. Still odd how they handle versioning IMO, course development of new version happens behind closed doors too. Just a totally different model from anything else.
[EVO 4G Android Development] IMiLL102911:
So cm7 won't work with amon ra?
[EVO 4G Android Development] mendozinas:
can someone point me where to find available commands for new Edify updater-script?
[EVO 4G Android Development] jerseymonkey:
Here is a list of commands: http://xdaforums.com/showthread.php?p=10276137#post10276137

Example Edify Script:

ui_print("Installing Market 2.2.7");
mount("MTD", "system", "/system");
delete("/system/app/Vending.apk");
package_extract_dir("system", "/system");
ui_print("Installation successful!");
unmount("/system");
[EVO 4G Android Development] generalExpert:
Never used the Nexus before as I'm on the EVO, but what I know is this...

When I upgraded my ClockworkMod from 2.5.x.x to the 3.0.x.x version it went to crap. Judging by the fact that your talking about amend scripting, I'm guessing I don't need to tell you to read about it...

It should be really simple. Just download RomManager and the first item in the menu deals with what version of CWM you have. It will show what is currently installed and what if any upgrades are avail. I know that when I was on 3.0.x.x and tried to flash back to an earlier version using the menu item at the bottom of RomManager, it did not work. It would say it flashed but it really wouldn't. I had to manually flash a PC36IMG.zip in order for it to actually flash it. When you manually get a PC36IMG.zip all you have to do is put it on the root of your file system (in my case, the SD card). When you reboot the phone it will auto check and ask you if you want to update. Once you do that you surely will be on the desired version. I was able to use RomManager to update CWM successfully from 2.5.0.1 to 2.6.0.1.

In my case, nothing would flash at all until I was on one of these versions. I wouldn't trust what RomManager says your version is, I would just manually check...

Hope this helps.
[EVO 4G Android Development] Spiricore:
Thanks a ton for your help! I've run into a few mentions of PC36IMG.zip, but couldn't really nail down the details -- is that something specific I'd need to download, or just grab 2.5.0.1 from Koush's recovery page and renaming it? I checked out my versions with ROM Manager, and everything is up to date.

I'm also having the same issue with ROM Manager; it's fully updated (as of today), but will just give me an error trying to downgrade. I wish I'd posted this before I installed CWM.

I'll do some snooping around regarding the PC36IMG.zip setup, but if you can point me in the right direction, I'd appreciate it. It may save me more time and grief. :P
[EVO 4G Android Development] generalExpert:
Hey, glad I could be of some help... ok I started thinking... im not really sure if your .zip file is going to be named the same... didn't you say you were on the nexus s? Sorry but I'm not sure if that phone has a different name for the .zip files. I know that for the EVO all you would have to do is get the file and rename if necessary. On our EVO's, we would then boot into hboot by holding volume down and power, and everytime that is done the phone auto searches for a PC36IMG.zip. That is why it needs to be named like that.

I bet that is your prob though... you just need to get on a working version of CWM and everything should be fine. I would point you but since I'm on the phone its a little too difficult to do.
[EVO 4G Android Development] Spiricore:
Update.zip is Gingerbread's (or maybe just Nexus S') thing. While it doesn't automatically grab it when booting into recovery, it shows up in CWM and treats it similar to what you seem to be describing with PC36IMG.zip. So, I'm going to rename 2.5.0.1 followed by a couple ROMs to update.zip and see what happens (one at a time, of course). I hope this doesn't end up being a bad idea, but what you're suggesting is the only option I've found and haven't completely exhausted yet. Thanks again for helping me troubleshoot this and giving me a few more options to try.

//update: No luck with 2.0.5.1; same problem with it reverting back to 3x with a restart. I tried it from both the recovery console and ROM Manager. What I need to do is figure out how to remove 3.x back to default, then install 2.x. I ran update.zip (which had CWM 2.5.0.1 in it) twice, then tried to flash a ROM. I received the same error, except with a little extra...

Formatting SYSTEM...
E:Can't format system:
E:Failure at line 2:
format SYSTEM:
Installation aborted.

/facepalm
[EVO 4G Android Development] TomaszK1:
Amen! O:o)