yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] elknipso:
I have s-off but what do I do this in order to be able to flash the whole?
[Desire Android Development] andQlimax:
Op write something on the first post

People always ask the same things

I do not understand why the OP does not write some instructions, faq, disclamer on the first post..come on (this is for all the op that going to open a thread)

I know people should search, but they don't
[Desire Android Development] elknipso:
its ok i have found the information.
[Desire Android Development] iinga:
Unfortunately, just because it is written in the OP there is no guarantee of people reading it either. Even in posts where the instructions are clear, people don't bother reading them...or searching... :(
[Desire Android Development] Flashmaniac:
sorry for the question I know its not on topic so...

I searched a little in here.

How can I dump my current recovery? so that it is an .img file?

Thanks in Advance.
[Desire Android Development] andQlimax:
When u do a nandroid, the folder contain ur recovery.img, that should be flashable via fastboot..Anyway u can download ur recovery searching it on google..What so special in ur particular recovery?
[Desire Android Development] tommeke19:
Hi,

I'm using Amon Ra at the moment as recovery, but I prefer CMW over Amon Ra.

I've try to change it back to CMW but it don't work.

I downloaded the lastest version and renamed it to PB99IMG.zip.

Then I put it on the root of my sd and reboot into fastboot but he will not update..

Please help me!

Thanks, Tom
[Desire Android Development] johno168:
Look around in the "everything is here - desire index" thread and look for "fastboot commander" much easier to use.
[Desire Android Development] tommeke19:
Thanks man! :-) it worked :-)
[Desire Android Development] faceN:
Thanks, works great, and thanks johno168 for the FastBoot Commander tip :)
[Desire Android Development] nitrox1:
Hello,

Is charging enabled in recovery, in the new version? Thought koush had posted a change enabling it?

Desire is the source of all suffering.
[Desire Android Development] AlxMAX:
I would like to solve a problem: flashing a radio image with the help of ClockworkMod. I'm trying to see what is the Edify equivalent command for the Amend command write_radio_image. I have searched through the source files of ClockworkMod and Amon RA recoveries and I have started to ask myself if it was possible at all to flash radio images with ClockworkMod (supposing one had enough space in the /cache partition).
[Desire Android Development] andQlimax:
The problem is not the radio, is the script..with the 3.x recovery u cant use old scripts to flash radio, rom, anything...

The problem is: why who created the zip file, with the radio imagine u want flash, didnt make the script compatiple with 3.x?

Solution: use fastboot to flash the radio if u have s-off or flash a 2.x recovery or amon-ra to use old scripts

Sent from my HTC Desire
[Desire Android Development] faceN:
Just boot into recovery using Rom Manager app and you'll be back to 2.5.0.7 until reboot and able to flash the radio file as usual.
[Desire Android Development] AzureusPT:
I think its not enabled or if it is, the led won't light orange. Last time I connected the phone via ADB in recovery I didn't find the led on nor the battery charging.
[Desire Android Development] AlxMAX:
I know what I have to do in my case. I have a S-OFF HBOOT and I usually use fastboot to flash a new radio image or a new HBOOT (by the way, I have a Linux version of fastboot available).

This is my point: trying to write an Edify script (used by the ClockworkMod 3.x recoveries) to update the radio. I have discovered this so far: when a radio update was running, the Amon RA recovery was not writing the radio itself but it created the environment so that it was the HBOOT which was writing the update into the flash. This might be the reason it was so difficult to write an Edify version of the script.
[Desire Android Development] crasher:
What I do is I keep a 2.5.0.7 cwm update.zip in the root of my sdcard card so that whenever I need it, I can just select the option in cwm 3.1.0.1 to install that update.zip.

Swyped from my Desire
[Desire Android Development] andQlimax:
Old script:

show_progress 0.1 0
write_radio_image PACKAGE:radio.img
show_progress 0.1 10

New script:

show_progress(0.1, 0);
assert(package_extract_file("radio.img", "/tmp/radio.img"),
write_firmware_image("/tmp/radio.img", "radio.img"),
delete("/tmp/radio.img"));
show_progress(0.1, 10);

I NOT TESTED THAT..FLASH A RADIO IN A WRONG WAY CAN BRICK UR DEVICE

Found that with this script convertion tool: http://xdaforums.com/showthread.php?p=10400641#post10400641

Better use fastboot to flash a radio in my opinion ;)
[Desire Android Development] veitograf:
help anyone

i tried to update my phone to 1.0.5 via fakeflash with cwm 3.0.0.5. but when i press yes install insertcoin 1.0.5... it jumps right back to the main screen. it happens so fast i cant realy read but i think i can see two lines with some text.

i even tried cwm 3.1.0.1 but no luck.

lots of people flashed all kinds of versions from this rom so i think its a recovery problem. should i try ra-recovery or does anbody know what the problem is?
[Desire Android Development] AzureusPT:
If you get back to the main menu on the recovery, you can hit submit bug or something like that and it will generate a log file in the SD card. You can check or paste here that log to see what could be the cause.
[Desire Android Development] danward:
3.2.0.0 up'd ;)
[Desire Android Development] elknipso:
Changelog?
[Desire Android Development] k3lcior:
I'm getting error: cannot load recovery-clockwork-3.2.0.0-bravo.img when trying to flash in fastboot (im S-OFF) using following command:

fastboot flash recovery recovery-clockwork-3.2.0.0-bravo.img

Any idea whats wrong? recovery .img is in the same folder as fastboot.

nvm. solved it. :P
[Desire Android Development] AlxMAX:
Well, you're fast! I was about to post the 3.2.0.0 recovery, but you were faster! Anyway, I have a question: what kernel does the recovery use? Is it some special kernel which allows access to more devices/partitions? Is it different from the CyanogenMod system?

What was it? Corrupted file?

There's my dilemma! I haven't tried to use that command, but I can't find it in the ClockworkMod recovery commands either. I have searched through its sources (brute force with grep) and there was no result. There was only write_raw_image. I could find it in the Amon RA recovery sources: in <RA-Recovery-2.2.1-root>/updater/install.c, there is a function call like RegisterFunction("write_firmware_image", WriteFirmwareImageFn);
[Desire Android Development] k3lcior:
No i just didnt "cd C:\fastboot" directory. :p
[Desire Android Development] andQlimax:
I just used google: github "write_firmware_image". Better than grep :D This in the ClockworkMod recovery source:

https://github.com/koush/android_bootable_recovery/blob/eclair/updater/install.c

line 864 " RegisterFunction("write_firmware_image", WriteFirmwareImageFn);"

dilemma solved :p
[Desire Android Development] bakaq:
I updated to 3.2.0.0 from 3.1.0.1 via fastboot with success. My Desire having MTD Hboot-CM7 partition & ROM InsertCoin Nightly_CM7 v35.

My feedback:-

Flashing new ROM, UOT etc & Nand backup works, but unfortunately restore of sd-ext partition doesn't work with 3.2.0.0 (tried 4 times though with various nand backups). Anyone else having similar problem?

Have reverted back to 3.1.0.1 & restoring nand backup made from 3.2.0.0 can be restored using 3.1.0.1....

Thanks.:)
[Desire Android Development] AlxMAX:
Not yet! You have mentioned a file which belongs to ClockworkMod 2.5.0.9 which has almost the same features as the Amon RA recovery (both have support for amend and edify, both implement the write_firmware_image function). My interest is to see if something has been implemented in a 3.x version.
[Desire Android Development] andQlimax:
Maybe this commit explain why you cant find it on a 3.x, is has been removed but replaced by an htc lib:

https://github.com/koush/android_bootable_recovery/commit/e08991e02a7d678f2574e85289a34b2a9a537c82

Why u don't try that command and see if it work or not? :D

I think we are going off topic now..
[Desire Android Development] AlxMAX:
I see! Thank you for clearing the things. It's htc.install_radio and htc.install_hboot now!
[Desire Android Development] teorouge:
Hello! 3.2.0.0 version sort of "reboots" the recovery when making full wipe and it gets to sdext formatting. Read about other sdext issues with 3.2.0.0, so I'm going back to 3.1.x.x.. Thanks anyway for your efforts! ;)
[Desire Android Development] Kirhe:
danward, could you add support of btrfs and reiserfs?
[Desire Android Development] AlxMAX:
Back to my problem: I have done some research and one still needs to activate the support for those commands. The HTC extensions for flashing the radio and the hboot are not compiled by default.

Well, that's not an easy task. One has to enable those file system modules in the kernel (this is the easiest part) and include the utilities (like formatting, checking and tuning) for the reiserfs and btrfs (I've heard there's no file system checker for this one).
[Desire Android Development] Vatrox:
Sorry if it has been asked already, but could somebody point me in the right direction of where to find a changelog (and previous changelogs too, by the way)?

Thanks in advance :)
[Desire Android Development] gutsbn:
I'd like to see this too
[Desire Android Development] karmatt:
There is no official clockworkmod change log
[Desire Android Development] Vatrox:
Any specific reasons for this? And how about fan-made ones? :)
[Desire Android Development] AzureusPT:
Since Koush is pushing directly to GitHub, the only way to get the changes is to diff the commits to see what has changed. I think the main reason there is no official changelog might be that the project has several end-user forks that modify that code, so is kinda pointless since its not the final product.
[Desire Android Development] Kirhe:
OK, i don't care about those utilities. I just need recovery with enabled file system modules in the kernel... Is it possible tо enable it?
[Desire Android Development] expl0de:
What is the point if changing the recovery? does it play a role after flashing rom? I use amon-ra and it dos pretty much everything.
[Desire Android Development] AzureusPT:
If you use the recovery to only flash a ROM, you won't notice any differences between AmonRa or CWM.
[Desire Android Development] 123xdagsm:
Hi all

For me not work "wipe data/factory reset"
[Desire Android Development] AlxMAX:
I have recompiled the Cyanogenmod kernel including those modules (in the kernel, so you don't have to use modprobe), then the recovery. The resulting recovery is about 3.2 MB. I'm not sure of the recovery partition size. I hope it is 5 MB. So help yourself with the attachment! I suggest you test the recovery with fastboot boot recovery.img then, if everything works as expected, flash it with fastboot flash recovery recovery.img.
[Desire Android Development] HFX9:
not work last version for me, when i reboot to default recovery and select apply sdcard:update.zip type my error with signature verification :-(

update.zip is last CWM recovery 3.2.0.0
[Desire Android Development] AzureusPT:
You can disable signature verification or resign the zip file if that is the problem.
[Desire Android Development] Kirhe:
Thank you very much! It works fine for me :)
[Desire Android Development] HFX9:
In default recovery i can't disable signature verification.

In default recovery is only:

1. Reboot system now

2. Apply sdcard:update.zip

3. Wipe data/factory reset

4. Wipe cache partition
[Desire Android Development] Tepes4:
Problem from 2507 to 3200

Hey guys

I've been trying to flash the new recovery 3.2.0.0 using unrevoked but have no luck. I have 2.5.0.7 installed and RCMixS 1.7.2. and I am S-On. It says "Error: failed to get root. Is your firmware too new? ".

Have followed all the instructions (sign verification etc)

Any ideas why and a way to solve this problem?

Thanks in advance

Tepes4
[Desire Android Development] dzumagos:
in order to flash new recovery using unrevoked, you would have to unroot, and then run unrevoked with new recovery chosen

other option is go S-OFF and flash it using fastboot
[Desire Android Development] devil snake:
Would someone PLEASE write the steps of flashing a recovery ? i'm lost ... i Googled it, i searched about 10^ pages in this thread ,,, i can;t find the steps...

i don't think i would flash Recovery from my OLD Recovery Right??? that doesn;t make sense...

so any steps to follow?

i'm S-Off'd...

=============

update: i also went to the the Clockworkmod "wiki" but there was some missing steps.. (maybe the author assumed that the reader should know that... though i never flashed a recovery (only with unrEVOked) but never upgraded... now i'm experiencing problems with the 2.5.0.7 old recovery so i wanna upgrade but no steps to follow)
[Desire Android Development] faceN:
If you are S-off:

1) Download the recovery .img file from the 1st post on your PC/Mac/Linux box,

2) find the "Fastboot Commander" thread and follow the instructions there.

Piece of cake.
[Desire Android Development] tracid:
I have the same problem. Tested it on two devices.
[Desire Android Development] AzureusPT:
There has been some fixes in the source code, so now it should work, but since danward is the one compiling the code in this thread, we have to wait till it compiles it again with the new fixes.
[Desire Android Development] olisun39:
I managed to flash the new recovery but I cannot flash any of the latest radio's ..

It complains of some update method being changed... :-(
[Desire Android Development] Glotzeulor:
Update scripts have changed from 2.x to 3.x

Use an older recovery or flash it with fastboot.
[Desire Android Development] :
Question,

Whenever i format my sd-card using ClockworkMod, i can't find the ext partition in GParted. It only shows the remaining as unallocated.

Now, this is pretty annoying. Whenever i format my sd-card using GParted, i end up with my sdcard being unable to mount. Formatting in ClockworkMod fixes this. But if i want to get rid of my ext partition, i'd have to flash AmonRA since it gives the option to format an ext with 0mb.

Any solutions for this?
[Desire Android Development] iinga:
I find this strange. I only ever use gparted to format my sd card (it gives me a lot more options and control over what is happening) and it mounts perfectly in clockwork mod. I'm not sure why yours won't mount.
[Desire Android Development] :
The weird thing is, USB-Mount works, but when i try to select a zipfile, or manually mount /sdcard, i'm getting an error. Not sure which ext CWM picks, but i had this with ext4 created in GParted. It's been the 2nd or 3rd time.

Will try with ext3, the next time i decide to change roms for a day :rolleyes:
[Desire Android Development] clio16v:
Sorry but where can i download cwm 3.1.0.1 because i cannot find it...
[Desire Android Development] tracid:
http://www.deltaxent.com/rb/recovery-clockwork-3.1.0.1-bravo.img
[Desire Android Development] efx_9:
Hey there.

Even if I disable signature check in cwm 3.2, when I choose to backup or install a new rom from rom manager, it fails because of signature check. It seems that rom manager keeps enabling it... Someone knows why?
[Desire Android Development] iinga:
Rom manager uses its own implementation of cwm. Use rom manager and put up with it or use recovery manually

Sent by Owl Post
[Desire Android Development] efx_9:
I already set "manual flash override" to cwm 3.x. Is this what you meant?
[Desire Android Development] gol_n_dal:
Hmm,

I have searched but didn't find any useful posts, might have just missed them though, so sorry if this has been logged elsewhere, if so please ignore.

Is 3.2.0.0 just not working, or did I fail to do the right thing ? I got it from the first post and installed it fine:

adb reboot recovery

fastboot boot *3.2.0.0*img

It worked fine so:

adb reboot recovery

fastboot flash boot *3.2.0.0*img

It successfully booted then flashed 3.2.0.0. The dammed phone then refused to boot into CyanogenMod 7 properly, it always kept coming back to CWM recovery.

I then tried to flash back an older CWM 2.5.0.7 and 3.0.0.5, they both booted fine but failed to flash the phone.

Interestingly 3.2.0.0 successfully did a Nandroid backup and recovery, still failed to allow the phone to boot into CM7.

Eventually my only option was to recover from an earlier Nandroid backup, which luckily worked.

Colin
[Desire Android Development] iinga:
What you are doing is flashing your boot sector with the recovery. This will screw up your phone regardless of what you flash. Try:

adb reboot bootloader
fastboot flash recovery {name of recovery}.img

Instead of what you are doing above.
[Desire Android Development] iinga:
I'm not sure about the ins-and-outs of how the reboot option of rom manager works with a manual override. What I meant was using the "Reboot to Recovery" option in most power menu reboots, or using an app to do it, and then manually backing up and flashing from there.

I think RM enables signature verification when using the manual override, which isn't a normal CWM feature (CWM by default has sig verifcation off).
[Desire Android Development] efx_9:
Right, reboot to recovery is my only option right now, making RM pretty useless in these conditions.

Thank you anyway.
[Desire Android Development] gol_n_dal:
Thanks,

Oops, my bad,

I clearly can't read my own instructions or type properly at the moment. It's so long since I last did anything with ADB and only use it very infrequently when I do.

It's working with 3.0.0.5 so I might just keep it like that for the moment.

So thanks again "iinga".
[Desire Android Development] AlboGio:
3.2.0.1 source avaiable

As the title :)
[Desire Android Development] mondilv:
3.2.0.0

No one correct backup restore.

Went down to 3.1.0.1
[Desire Android Development] efx_9:
Happened with me too, sd-ext is not restored, had to do it separately.
[Desire Android Development] iinga:
I built 3.2.0.1 in case anyone is interested:

http://www.iinga.net/desire/cwm

On testing, it appears version number in cwm is still 3.2.0.0, will check out the build script I have
[Desire Android Development] Rumball:
Yep, noticed this as well. The restore will not automatically restore the sd-Ext partition. We have to use the advanced restore function afterwards to manually restore just the SD-Ext partition.
[Desire Android Development] danward:
3.2.0.1 Up'd
[Desire Android Development] teorouge:
Thanks, does it fix the "reboot recovery on sd-ext wipe" issue?
[Desire Android Development] shnizlon:
3.2.0.1 - Fixes a bug with 3.2.0.0 (actually a build issue) where ext3 (/data and /cache) wouldn't be formatted properly (they were but CWM was bombing out) :D
[Desire Android Development] teorouge:
Thanks, gonna try ASAP.
[Desire Android Development] suiller:
flashed 3.2.0.1... all seems fine. thank you :cool:
[Desire Android Development] j7k:
flashed 3.2.0.1, but reported as 3.2.0.0 :confused:
[Desire Android Development] davebugyi:
Are you S-OFF?
[Desire Android Development] DenyDarko:
Same here.

Flashed with fastboot.
[Desire Android Development] j7k:
Yes, certainly. I flashed via Flasher 1.7.6 over here, like many times before.
[Desire Android Development] tma24:
same problem also for me. I am s-off and I am flashing via android flasher.
[Desire Android Development] teorouge:
In another thread they mentioned that wrong version report... think it's built-in! :D
[Desire Android Development] krytak:
flashed over 3.2.0.0 with FastbootCommanderV.1.1 (S-OFF), same error here :(
[Desire Android Development] iinga:
Yes, the version number just hasn't been updated in the app, but all changes from recent commits have been included.
[Desire Android Development] Uqbar:
It's still saying it's 3.2.0.0..
[Desire Android Development] teorouge:
Did you even read the post before yours? :mad:
[Desire Android Development] Uqbar:
A few times...
[Desire Android Development] teorouge:
Two options then:

You don't understand English language

You can't understand a thing

Anyway, it doesn't matter as this is the same old, same old. :rolleyes:

EDIT: I saw you can't search (or read) so here it is:

http://idioms.thefreedictionary.com/same+old+same+old

Hope you can get that English, though. And no, you have no excuses because we were discussing about that issue right above your post. But you can go on and be an arrogant head as much as you want while you should just apologize.
[Desire Android Development] Uqbar:
Two answers, then:

A few times

A few times

Anyway, it's nice to have such a polite help to trivial and common mistakes.

When a forum has thousands of readers, common mistakes happen hundreds of times. Like writing a post and hitting SUBMIT too much later.

But, I agree, "this is the same old, same old"

something

.
[Desire Android Development] ivicask:
That's from guy who compiled it..

Anyways don't worry, it is newer version, only its build number shows as 3.2.0.0
[Desire Android Development] aorifan:
just flashed 3.2.0.1 from ra2.0.1 and performed backup once, my phone seems to be really hot after it. dunno if its normal.:confused:
[Desire Android Development] Uqbar:
I guessed something like this ... just an annoyance ...

It can be even left as is until the next release ...
[Desire Android Development] sergmeister:
when i try formatting with cwm i have to go onto computer and use minitool partition wizard to set fat32 partition as primary partition again or i cant mount, i dont have any problems with GParted though..
[Desire Android Development] aorifan:
have you tested the latest version?
[Desire Android Development] bmonster:
Im using the version that installed from the alpharev s off procedure, what benefits are there from upgrading, as the version im using works ok. Thanks
[Desire Android Development] Oijkn:
Maybe bricked ?!

hello I just wanted to test this new recovery, to be updated ^^

I had installed on my phone RA_recovery 2.0.0 which works fine, so I flashed ClockworkMod Recovery - 3.2.0.1 zip file and during restart my system can no longer mount my SD card .... now I'm trying to debrick it :(

Be careful before flashing this file, it's just an advise !

Edit

: I looked better at my problem and it seems to come from the EXT partition that no more recognized...
[Desire Android Development] msiviter:
I've got the same problem, DON'T FLASH THIS UPDATE!!!

Any news on how to fix the sdcard mount problem please post here.

Matt
[Desire Android Development] cyron_at:
..never touch a running system!!!!
[Desire Android Development] Uqbar:
I'm still using the old fashioned fastboot and got absolutely no issue at all ...
[Desire Android Development] cyron_at:
...same here!
[Desire Android Development] tompok82:
3.2.0.1 doesn't work.

Flashed using Fastboot Commander, CWM say it's version 3.2.0.0 instead of 3.2.0.1.

Not to forget that 3.2.0.0 is faulty for not being able to do a complete full wipe.
[Desire Android Development] iinga:
3.2.0.1 does work, the version number displayed just hasn't changed...all commits after 3.2.0.0 ARE included. If you read before posting, you would have seen this has been discussed.

Interestingly though, the Android.mk has been updated to version 4.0.0.0, but there haven't been any major changes since 3.2.0.2 ("minor update" to 3.2.0.1) was committed.
[Desire Android Development] Poodlemastah:
https://github.com/CyanogenMod/andr...mmit/50822991460cbee65757e9de12b29e39238d6386

I'd say ~300 lines of code is a pretty major change.
[Desire Android Development] iinga:
Hence why I said "minor update" :)

The updated versions can be found at http://www.iinga.net/desire/cwm if anyone is interested in trying before danward compiles. 4.0.0.0 still says it is 3.2.0.2 in the recovery, but seeing as there are no new commits, I don't think this matters.
[Desire Android Development] andQlimax:
Did you try doin a "make clean" before build it?

It's strange that the show version is wrong..The latests time i build it, it always change..Even now is long time im not building it, because to many changes for other devices that are breaking something sometimes