yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] keyra74:
yup just flashed 4.0.0.0 and it says 3.2.0.2, gonna see what changed
[Desire Android Development] iinga:
Yeah, I always clean out my out folder when I compile things. I have it auto compiling in a script on boot. If there's a new version, it will compile it, along with other things I use from CM.

3.2.0.1 also had the same bug (showed as 3.2.0.0 in recovery - using the one I compiled and also danward's in the OP). 3.2.0.2 showed up correctly though. Which makes me wonder where CWM pulls its version number from to display in the recovery. I always though it was from the Android.mk file
[Desire Android Development] AlxMAX:
I have noticed the recovery used a kernel with the userspace CPU frequency governor. If you recompiled a kernel with ondemand as default then the recovery, you might solve the problem.
[Desire Android Development] nespresso33:
With 4.0 recovery, I get "can't mount sdcard" !
[Desire Android Development] teorouge:
Actually 3.2.0.1 (which shows up as 3.2.0.0) suffers the same sdext issue as (true) 3.2.0.0, tried this morning and had to reflash 3.1.0.1 to make a full wipe. I didn't try 4.0.0.0 yet, will do that soon.
[Desire Android Development] iinga:
I don't know that 4.0.0.0 can restore sd-ext. I will try and do some tests.
[Desire Android Development] iinga:
Yes, I'm also getting this. Will remove 4.0. It seems 3.1.0.1 is the last "working" version for desire
[Desire Android Development] Jinson7:
I have done a key test using this recovery and when I press my volume up button it displays 114 then 102 (which is the home key)

Can I correct this in the recovery? I tried the app button remapper but it didn't pick up the defect. Really annoying me especially when I am in call and want to turn the volume up :(
[Desire Android Development] SergioA:
Is there any link to the 3.1.0.1 still available?

Thanks!
[Desire Android Development] Bjork62:
Link for 3.1.0.1:

http://www.mediafire.com/?gjmaot7infkrork

Just tested, it's ok
[Desire Android Development] msiviter:
Downgrading, flashing 3.1.0.1 doesn't restore the ability to mount sdcard.

Phone still bricked!!!
[Desire Android Development] iinga:
Then unbrick it?!
[Desire Android Development] Oijkn:
Hi I have unbrick it with the tuto in xda but the sd card still bad, then I reinstalled a new rom and all come back good :)

pm me if you need help ;)
[Desire Android Development] nespresso33:
Not logic your phone get bricked...

I can't mount sdcard in recovery but it is working in the rom.

I will downgrade now.

EDIT: Downgrade to 3.1.0.1 done, and it is working good
[Desire Android Development] msiviter:
unable mount sdcard - solved

With phone in Hboot Fastboot mode

At the commant prompt on my Win 7 32 bit PC:

C:\adb\tools\fastboot devices

SH11APL03395 fastboot

C:\adb\tools\fastboot oem boot

Blah blah blah

INFOCID is ORANG001

Blah Blah Blah

C:\adb\tools\fastboot oem enableqxdm 0

...OKAY [ 0.164s]

finished. total time: 0.165s

Alpharev bravo Hboot

CWM v3.1.0.1

All recoveries and Hboots can now mount the sdcard, I dont know why the 'enableqxdm' command worked this time, I'm by no means an expert! All I know is that my phone is useable again- hurrah!

Thanks for all your efforts guys

Matt
[Desire Android Development] iinga:
I have made a slight change to the source (trial and error) that when I just restored nandroid, it successfully restored the sd-ext. However, I have had to disable .android_secure restore.

I need further testers. http://www.iinga.net/desire/cwm/test/4.0.0.2-sdextfix.img (4.0.0.2). (The 4.0.0.2 in my cwm dir is an unedited version compiled directly from koutts' source)

Does nandroid restore work normally for someone that has a .android_secure backup?

if (restore_data && 0 != (ret = nandroid_restore_partition_extended(backup_path, "/sdcard/.android_secure", 0)))
return ret;

For those who are better than me (and trust me, I have no idea what I'm doing), when the restore process reaches this code, it bombs out on my phone. I am unsure about others. I do not have an image for .android_secure so I am guessing that something about the code is returning incorrectly.

As can be seen in the screenshot, 4.0.0.2 has successfully restored my nandroid.
[Desire Android Development] shakland:
I'm gonna flash it and test it right now ;)
[Desire Android Development] expza:
Anyone got an MD5 for recovery-clockwork-3.1.0.1-bravo.img ?

Can't find it in the thread.

Thanks :)
[Desire Android Development] deathbringer:
flashed CWM 4.0.0.2 using good 'ol fastboot.

1) SD Card mounts fine.

2) version number displays correctly.

any problems i should look out for or test?

cheers.
[Desire Android Development] Scofield.:
need the option to partition the sdcard from the recovery!!
[Desire Android Development] deathbringer:
it's there under "advanced" tab
[Desire Android Development] iinga:
.android_secure restore when .android_secure is empty (possibly)/sd-ext is used. Causes restore to bomb out and sd-ext is not restored. If you need sd-ext restore, I suggest using my test version (.android_secure has been removed).

I am investigating the problem with another dev, and we'll see what happens. Problem is, I know very little about what I'm doing, and so am working through what I think the problem is by trial and error.
[Desire Android Development] sergmeister:
here's the checksums:

CRC-32: 59a91140

MD4: 9ab489c2c2ca6f64151efc97486c3e72

MD5: 800ecf2b328d8d4cb29883f52fd5916b

SHA-1: baa30a015cf7062001d6504fd7eb04cd67fa9e8a

I attatched the md5 file in a zip (since .md5 isn't allowed)
[Desire Android Development] Scofield.:
So i can create an ext Partition with the CWM Recovery on my sd card?
[Desire Android Development] krytak:
800ECF2B328D8D4CB29883F52FD5916B recovery-clockwork-3.1.0.1-bravo.img
[Desire Android Development] deathbringer:
i can confirm the problem too. "android secure" cannot be restored or wiped!! however, i have not tried your fix as you will have to remove .android_secure and that might mess with my apps installed on the SD card

yup.
[Desire Android Development] Silvercn:
Hi Ppls,

i got a Problem with cwm, i installed the last version from here but it shows me as versionnumber 3.2.0.0.0 not 1 at the end. Its normaly? And my biggest Problem is, the version before was 2.5 or 2.3 if im right (updated a long time not) but now when i try to restore it doesnt work, all my apps not there, looks like i did a fresh install, just two or three apps will be restored, i tried two restore Points.... :( (Im using Ginger Villian 2.5) so maybe someone can give me a link o an old cwm and ill try with an older version, maybe that will work. thanks for reading
[Desire Android Development] mikbe:
If you had read a few previous pages you would have noticed that this has happened to everyone who has tried 3.2.0.0 and 3.2.0.1. Downgrade to 3.1.0.1 and restore works.
[Desire Android Development] Silvercn:
Okay thanks, someone got a link to 3.1.0.1 the previous link doesnt work. Ok works now, was inet error.
[Desire Android Development] AlxMAX:
I have compiled the 4.0.0.4 version of the ClockworkMod recovery. With it, I was able to perform a backup (/boot, /system, /data, /cache), then to restore them (after an HBOOT upgrade). Everything seems to be working well. The difference from the standard one is that I have also recompiled the kernel and I have set the ondemand CPU frequency governor.
[Desire Android Development] roalex:
My point is that this recovery are not released for the public simply cause they aren't done, thats why koush didn't put them out, he's working on them still.

I think using Kali's r3 is the best a regular user can do and i hardly see why they should be tempted into a lot of hassle.

There are pretty good devs around here if there is a demand for a specific recovery feature im sure someone will build one and test it :)

this is the changelog of the recovery source, you can see stuff like:

But i think that prove not to do the job actually :) as in the user still win!
[Desire Android Development] tompok82:
For some reason, I can no longer flash radio after updating CWM to 3.0.2.4.

Anyone else can test this on their S-Off Desire?
[Desire Android Development] Nyto75:
when you are s-off, you have to change the radio via adb (fastboot) :

"fastboot flash radio radio.img" i think it's that ^^ you can also use android flasher which is useful ! :)
[Desire Android Development] snapilica2003:
So you're saying that 2.5.0.7 is the last recovery we can safely use on our devices?

This version difference has been bugging me recently as I have Kali's r3 installed but ROM Manager uses 2.5.0.7 (I haven't been able to find an update.zip for 3.0.0.5-r3). And flashing is done either via 2.5.0.7 from ROM Manager, either via 3.0.0.5 if I manually enter recovery. I have a feeling using two versions is not a very good ideea.

Anybody have a update.zip for Kali's r3?
[Desire Android Development] roalex:
http://xdaforums.com/showthread.php?t=917570

on the second post you can find the latest safe recovery, Kali is the CM's Bravo maintainer, you can trust him :)

(think he also has a small guide for you, in any case flashing recoverys trough recovery isnt't smart at all)

ALSO !

RM will see your recovery as 2.5.0.7 since its the latest he knows.
[Desire Android Development] robbiekhan:
Hmm since the CWM builds have been updated I don't quite know what recovery is thebest now for features and compatibility. I use AmonRA and would like to have partitionining support for SD-EXT should I wish to go back to Sense ROMs and so on.

I take it this new CWM has more features than AmonRA?
[Desire Android Development] snapilica2003:
Actually no, RM shows 2.5.0.7 as it's the version in the update.zip that's located on the SDcard. RM does not boot into the installed recovery it boots into the update.zip from your sdcard.

You can check this very easily by checking the version when you use installed recovery (holding VOLDOWN + POWER) with the version when you select "Boot into recovery" from ROM Manager.

That means you actually have two versions you can use depending on what route you choose which is not a good idea in my opinion (as using the built in update CM7 uses means using the RM route)
[Desire Android Development] Golomidov:
Actually, it seems that you are right. But this means that Koush must have a reason not to include 3.x recoveries into RM. Hm...
[Desire Android Development] tompok82:
That's weird because when I'm on 3.0.0.5 (S-Off too), I can safely flash my radio.

I'm going to try and flash back to 3.0.0.5. If radio flashing works, then it's proven that 3.0.2.4 has some bugs that prevents users from updating their radio.

Will update later.
[Desire Android Development] snapilica2003:
My point exactly. And I've already USB Bricked my phone one by mixing CWM2 with CWM3 once and I don't want to do it again. My plan is to stick to Kali's release of CWM but i need to find a way to make ROM Manager use that version also (meaning finding an update.zip with 3.0.0.5-r3 and replacing it with what ROM Manager has).
[Desire Android Development] tompok82:
This is mighty strange.

I'm back on 3.0.0.5 but flashing Radio still fails.

But I do know that I can safely flash Radio before.

Not once have I flashed Radio using Fastboot Commander, all through CWM.

But now, no more. :(
[Desire Android Development] roalex:
I can assure you i don't have 2 recoverys, on sdcard i only have the backup folder(the GUI still show me as having 2.5.0.7) on the other hand id never use the gui for recovery operations, just reboot in recovery :)
[Desire Android Development] roalex:
it has a safety check, as its not safe :)
[Desire Android Development] Golomidov:
Didn't you change your partition table? Flashed CM hboot for example? Some hboots have too small cache to flash radio from recovery, you should flash via fastboot.

2roalex: I believe nodoby has 2 recoveries, but RM update.zip runs after reboot and start itw own binary which is 2.5.0.7 despite I have 3.0.0.5-r3 flashed
[Desire Android Development] snapilica2003:
-nevermind, Golomidov was faster-
[Desire Android Development] lazarost:
Thx for the new build.

Things are working as expected although I don't use a2sdext, so as to notice if it backups/restores sdext partition properly.

Looking forward to a new build that hides the format recovery/format misc, these options are just a disaster waiting to happen.
[Desire Android Development] schlex2010:
Can I flash the recovery-clockwork-3.0.2.4-bravo.zip per Recovery Mode?
[Desire Android Development] ssauger:
As described before, if you got a other hboot like CM7 the cache partion is to small to flash the recovery. So u need to go to Bootloader (power off phone, hold back button and power button), then your in bootloader. connect usb cable, type "fastboot devices" in a console to be sure the device has been recognized by the PC,

"fastboot flash recovery recovery-clockwork-3.0.2.4-bravo.img"

Hope this helps.
[Desire Android Development] enuazeal:
what if device is not recognized?
[Desire Android Development] dallholio:
You need to install HTC Sync to install the drivers. Close HTC Sync before connecting to fastboot
[Desire Android Development] iinga:
sd-ext restore still doesn't work on it...But I think chainfire fixed it for sgs2, so I may speak to him about it.
[Desire Android Development] AlxMAX:
I don't have a /sd-ext partition anymore. I have deleted it because of very slow speed when transferring files via mass storage.

On another thread, zyonee and j_r0dd are discussing about a modified menu. Could those modifications be integrated in the main branch?
[Desire Android Development] iinga:
Well does .android_secure restore work for you? I would hazard a guess that it is no because it bombs out regardless of what I do, which means that apps moved to the SD card will not be restored. It also can't be wiped.

And the modified menu moves wipe dalvik-cache to the main menu. Wiping dalvik-cache is something that needs to happen VERY rarely. It is a common misconception that dalvik and cache need wiping on rom upgrade. You can see this former gerrit change http://review.cyanogenmod.com/#change,4933 when something similar was attempted to be merged (this proposed that during rom flash, it wiped cache + dalvik) and the reason it was rejected because it is not needed, as the caches are invalidated by a new flash.
[Desire Android Development] Nuntius:
Hi,

Is version 3.2.0.1 compatible with latest ROM Manager?
[Desire Android Development] mikbe:
3.2.0.1 is not compatible with your sd-ext.
[Desire Android Development] iinga:
The latest version (4.0.0.5) may work with sd-ext and android_secure. I am currently testing.
[Desire Android Development] kahila:
Hi!

When I try to do a full wipe it always fails, atleast I think so. After wipe there should be a text "Full wipe completed succesfully", but nothing like the recovery just goes back to menus. There comes a text just before failure, but it goes so fast that you cant see it. Any solutions?

EDIT: When I boot the phone after full wipe, the phone is in clean state. The previous rom is clean and EVERYTHING ELSE BUT ROM ITSELF HASNT BEEN WIPED... ???
[Desire Android Development] iinga:
Yeah it bombs out after android_secure. Try 4.0.0.5 (http://www.iinga.net/desire/cwm) and let us know how you find it.
[Desire Android Development] kahila:
Well yeah that helped, thanks. It still gives the same failure info which was given with 3.0.0.2, but it wipes the phone though. The message says: "No app2sd partition found, Skipping format of /sd-ext"

I have 16gb sdcard which have partion of 1 gb in EXT3 made with gparted.

EDIT: No actually nothing changed, it still doesnt wipe anything else but my info, the rom stays.
[Desire Android Development] iinga:
Oh that's because its a data wipe and not a system wipe. System gets formatted when you flash a new rom. I misunderstood what you said originally, but this is "normal" as there is no point in wiping system, when all roms will "wipe" it on install.
[Desire Android Development] kahila:
Still problems, when installing InsertCoin stable (I have the correct Hboot) the phone boots to home screen, but when trying to open "settings" it says "the application hasnt been installed to this version." Cool Kingdoms gives bootloop. Can the EXT partion be corrupted?
[Desire Android Development] iinga:
Mmm I thought that Koush had fixed the sd-ext issue. I'll have a look at the commits. Try 3.1.0.1, there's links up above, and I'll mirror it on my cwm repo (http://www.iinga.net/desire/cwm)

EDIT: 4.0.0.5 works fine for me. It correctly wipes everything, restores everything and can flash to sd-ext as well.
[Desire Android Development] kahila:
Still no use. Trying to repartion my sdcard.
[Desire Android Development] Nuntius:
??? What do you mean by that?

Recovery installed is 3.2.0.1 . ROM Manager says it is 2.5.0.7.

Can anyone tell me why?
[Desire Android Development] iinga:
Because rom manager uses fake flash to flash a recovery from the sd card, and not the recovery on the recovery partition, unless of course you change it in settings to have manual override
[Desire Android Development] Soul-Seer:
hey just installed this new recovery and now it cant mount system.... it fails when trying to do a backup. I was able to mount system before the update though... any reason or fix for this?
[Desire Android Development] iinga:
What version are you using?
[Desire Android Development] Soul-Seer:
I first upgraded to 3.2.0.1, partitioned my sd card for ext3 through the advanced menu and then couldn't make a backup. when that messed things up i tried downgrading to everything one step lower at time all the way to 2.5.0.7. Nothing worked so i read through the thread a bit more and found links to 4.0.0.5. that didnt work either...

After that i tried one of the amon-ra recoveries and that one gives an error then freezes when trying to do a backup now....

I was originally on 2.5.0.7 and was able to mount system no problem until I updated.
[Desire Android Development] angusc:
I'm addicted to flashing ROM's....you people seem addicted to flashing Recoveries....!! :-)
[Desire Android Development] AlxMAX:
Has anyone checked what adb devices showed when the phone was in the recovery mode? In my case, it showed something different (0123456789ABCDEF recovery) than in the case the phone was booted normally (<serial number> <mode>).
[Desire Android Development] expza:
I had a problem with the following versions of CWM:

3.1.0.1

3.2.0.2

4.0.0.0

4.0.0.1

4.0.0.5

The ext partition was literately 'invisible' to every partitioning program out there, including gparted. Mount USB, gparted, can't see existing ext partition.

Have fixed by fastbooting 2.5.0.7, can now see the ext3 partition in gparted.

Also had a massive problem with 4.0.0.5 - clockworkmod/backup/<date> didn't contain the normal system.img, boot.img ect... it contained multiple files 4 - 5 GB big (impossible, as SD card is only 4GB big) with incoherent file names. Couldn't delete them. Had to completely format (and thus reload my ROM) to fix it.

Backup was made with 4.0.0.5.
[Desire Android Development] erklat:
I flashed the latest via fastboot, but the recovery still says it is version 3.2.0.0. Anyone else noticed this?

Lazy me :ashamed:

I'm up and running for 19hrs straight now, so I slipped. My bad :p
[Desire Android Development] StuMcBill:
Ok, so I have updated to the clockworkmod on the first page, nandroided my CyanogenMod before trying a sense 2.1 + 3.0 hybrid.

I tried to restore my nandroid backup, however it keeps telling me that my md5 is wrong, even though they are not?

Could I go back to a friend about older version to restore this backup (including sd-ext)?

Thanks

Stewart

Sent from my Amiga 500 using Workbench
[Desire Android Development] iinga:
You can try 3.1.0.1 (http://www.iinga.net/desire/cwm) and that is the last known working version...The latest (4.0.0.5) has some bugs with ext restore, although it will back it up.
[Desire Android Development] StuMcBill:
Perfect i will give it a go tomorrow!

Sent from my Amiga 500 using Workbench
[Desire Android Development] milogen:
Thank you for the sharing.
[Desire Android Development] Exiled_SouL:
Those who are facing problem did any of you guys tried Amonra-2.0.1

2 weeks ago i was on cwm recovery and facing those problem like recovery,flash,sd-ext error and usb bricked twice.

now i am using Ra and still didn't face any problem.
[Desire Android Development] rk-ger:
Which is the latest version that I can use for my Desire Z (Desire G2)? Thread says 3.2.0.1. Rom Manager (V. 4.3.2.3, free) says 3.0.2.4. Now I have 3.0.0.5 and everything works fine (I hope), but I want to do a ROM upgrade so I think I have to upgrade to the latest (working) version, right?
[Desire Android Development] iinga:
You might want to look in desire z threads then...
[Desire Android Development] Uqbar:
Puzzled

Which recovery is the one considered to be stable and working?

This thread title says it'd be "v3.2.0.1" but, accordingly to the posts earlier it doesn't seem so.

I've seen also a number of v4.0.0.* out there as well as a number of complains.

Finally the "Everything Desire" thread is adding a little more confusion.

I'm running v3.2.0.1 but I'm just using the "wipe" and the "flash from zip" items.

And for these two there seems to be no issues for me.
[Desire Android Development] iinga:
3.1.0.1 works, and I think the 4.0.0.5 (http://www.iinga.net/desire/cwm) should be working completely, using various edits.
[Desire Android Development] Uqbar:
Which edits?

Do you mean that the recovery image is not usable as is?
[Desire Android Development] iinga:
A few commits done by zyonee (he builds a desire recovery but there are a lot of changes from CWM - which in turn came from other people roalex etc) which add ext4 support and also enables ext to be properly mounted. This enables 4.0.0.5 to be useable by sd-ext users.

I'll upload source to github, but am currently setting up my win7 to work with github and be able to compile, so bear with me
[Desire Android Development] AlxMAX:
Wouldn't it be better if the two branches/repositories were merged?
[Desire Android Development] Hypercaine:
Won't install a new radio. Just says installation aborted. No matter what I try. The version i use is 3.1.0.1.

Any solution?
[Desire Android Development] ssauger:
Are you on any hboot with a small cache like CM7 hboot? Then you cant flash radio in recovery, you have to do this in fastboot mode. Extract the *.img file from the archiv. You must have installed adb drivers, then boot into fastboot and connect usb to your phone. I preffer to place the img file in android/tools. Open command promt, navigate to android/tools and do

fastboot flash recovery *.img
[Desire Android Development] angusc:
I can't download 4.0.0.5 from this link......it only opens the coding....? I only have Dolphin installed on my Desire. Is there another way to dl?

EDIT:OK I got it using the home PC and Chrome.

Sent with Desire.
[Desire Android Development] k3lcior:
http://xdaforums.com/showthread.php?t=1112658

Use the latest one, Desire_recovery-clockwork-4.0.0.5.z110623-j_r0dd_mod.zip

AFAIK everything is working fine.