yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Jagdish84:
Nah, i cant believe thats related to S-OFF, im not having any problems with nand atm, and using AmonRas 2.0.1, dunno what i did to resolve it :\
[Desire Android Development] mad-murdock:
rom is this: http://xdaforums.com/showthread.php?t=829734 (first stable gingerbread with everything working...)

i never had problems like this with n1table and cyanogen, miui and the like.

first encountered this with oxygen/gingerbread

usb-unbricking is a matter of 2 minutes if you are prepared, so i dont complain at all - but for some people this might be a bigger issue.
[Desire Android Development] jaikat:
Mr Amon_RA

will flashing this recovery work through terminal on a s-off device?

If so, is the command the same as it was for my G1?

if not, why not(just curious ;)
[Desire Android Development] mercianary:
do you mean this command?

flash_image recovery /sdcard/recovery.img

Yes, it does work.

also you can

fastboot flash recovery recovery.img
[Desire Android Development] mad-murdock:
@amon_ra - things getting more strange:

i backuped oxygen again, flashed my self-compiled gingerbread rom (early cyanogen port), after testing, restored the oxygen nandroid backup, no usb brick this time....

thats very wierd - i so was prepared to usb unbrick (:
[Desire Android Development] reddev0:
Running AmonRA 2.0.1 and have backed up and restored nandroids for Oxygen many times, from version 0.2 to the current 2.0 RC1. I was worried after reading the last few posts but so far I have not had any issues. Using Oxygen 1.0.4 with Data++ partition table as daily rom. What table are people with problems using?
[Desire Android Development] Amon_RA:
Could it be that the issue is only appearing when you did a toggle usb storage from recovery?
[Desire Android Development] robbiekhan:
No problems here, was on Oxygen 1.0.4 with N1table (as per sig) and now on Oxygen 2 RC1. I always wipe dalvik first then do a all user data wipe before doing a restore.
[Desire Android Development] Jagdish84:
I went from cm 6.1.1 to oxygen rc1, nand before and restored my backup without any probs, I suffered from em usb bricks before, all seems to be just fine now...
[Desire Android Development] mad-murdock:
now that you mention it, yes, i think i used usb toggle to put the oxygen rom on the sdcard for later flashing...

sorry for missinformation - i thought its connected to gingerbread - didnt pay attention to usb stuff...
[Desire Android Development] mad-murdock:
i did some additional tests:

usb-toggle: no ||| nandroid restore: yes ||| not bricked

usb-toggle: yes ||| nandroid restore: no ||| not bricked

usb-toggle: yes ||| nandroid restore: yes ||| not bricked

usb-toggle means switching to usb in recovery and doing some write access to sdcard.
[Desire Android Development] MrAce87:
Bravo C support in the future?
[Desire Android Development] jaikat:
Just flashed thru Terminal Emulator and it worked. Thanks
[Desire Android Development] Amon_RA:
Ugh... I have no idea what could be causing it.

Did you ever flash a rom via clockworkmod , then switched to this recovery and then made a backup?
[Desire Android Development] nikosrs4:
AMON, what's the difference between 2.0.0 and 2.0.1?

op says about 2.0.0.
[Desire Android Development] Amon_RA:
2.0.1 backups the entire sd-ext
[Desire Android Development] mad-murdock:
No, I don't use clockworkmod at all since I switched to your recovery. So no clockworkmod running here for at least a month.

I never again had usb brick, even I do heavy use of backup + restore since testing gingerbread stuff.

But you cannot halluzinate usb brick. It was for real that one time...

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] bemymonkey:
And I haven't used ClockworkMod since I discovered the 1.7x port someone else did of your recovery... So I'm pretty sure Clockwork doesn't have anything to do with it :p
[Desire Android Development] mutokenji:
any chance for creating more then 1 ext using recovery?? :D
[Desire Android Development] Ryanadel:
mmmm something weird happenin,

used unrevoked to flash version 2.0.0,

now i need the 2.0.1 for the data2ext backup,

and when i try to flash it i get an "internal error: couldn't find misc" msg in unrevoked,

anyone got any idea about this situation?
[Desire Android Development] Latty:
I've been getting random SD bricks when nandroid restoring too =(

(happened just now, and has happened 2-3 times in the past week or two)

Now that I recall, I did use USB-MS toggle to copy a ROM over this past time.

I'm S-OFF as well, and have been using these fastboot commands for brick recovery:

fastboot oem enableqxdm 0

fastboot oem eraseconfig
[Desire Android Development] PaY87:
Any chance to get this in this great recovery?

https://github.com/klutsh

Klutsh has the source for his recovery mod there.

It would be so nice to see a Amon_RA version with PSFreedom, this would be the perfect recovery! :)
[Desire Android Development] mad-murdock:
Amon, I never dared to ask this, but since it does not seam we see a new version soon, would it be possible to compile a 201 release with the great cm skin when you are bored?

I tried to modify the .img myself but had no working mkbootimg for x64 at that time and so failed..

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] apristel:
Is there an Amon_RA Recovery for the CDMA desire?
[Desire Android Development] mutokenji:
any chance for creating more than 2 parition using this recovery?

Example

- Partition 1 = fat32

- Partition 2 = ext4

- Partition 3 = ext4..

Since we have data2ext that need 3 partition now.. :D
[Desire Android Development] Amon_RA:
Use adb and parted : http://xdaforums.com/showthread.php?t=534714
[Desire Android Development] dkawa:
Just want to thank Amon_RA for the v2.0.1 version. Yesterday I have installed a fresh ROM in my HTC Desire. The backup went fine (with ext3 backup part)
[Desire Android Development] mad-murdock:
hey amon,

just again i had another usb brick. i play around a lot with gingerbread atm, and did about 10 restores without brick. since i didnt expect it anymore, i have no recovery.log

what about copying the recovery.log always to /sdcard/last_recovery.log - at least until we figured out whats causing the bricks.

again, its not a problem - one fastboot command and one prepared misc image - some minutes, its unbricked (:
[Desire Android Development] Latty:
Ditto. As mentioned earlier in the thread, I've had a few SD/USB bricks recently. It definitely did happen prior to Gingerbread, I just think I've been flash dancing more with nandroid restores since Gingerbread came out.

It's so simple to fastboot to unbrick, but I have to have a computer handy before I can unbrick my phone to a usable state again (esp with A2SD+)
[Desire Android Development] ahwaztaxi:
can someone give me the zip file (not the img)of Amon_RA v2.0.1 recovery for desire ?
[Desire Android Development] Uqbar:
Or, even more simply, can Amon RA update the download link?

The one in the first post still points to v2.0.0!
[Desire Android Development] Amon_RA:
v2.0.1 is a test... it's only meant to test out the ext backup.
[Desire Android Development] hallydamaster:
Using it as permanent recovery. Restored many nandroids with this. Working perfectly! ;-)
[Desire Android Development] iinga:
However, there are numerous scenarios where USB bricks have occurred...so probably not the best idea to release it as a working backup :)
[Desire Android Development] hallydamaster:
That might be true, but I can only say that it has not happened to me!

Has no one encountered this with the 2.0.0 version?

As mad-murdoc I have been messing around with the Gingerbread releases as well, and everything still fine!

I have the early PVT-1 Desire if that makes a difference?

Hallydamaster
[Desire Android Development] FunkyRabbit:
i think i did that to my phone :s.

I can't boot in the recovery anymore, and flashing won't work.

If someone can help me :(

thx

Edit: solved
[Desire Android Development] Nitrius:
So i've been using ClockworkMod until now, how does this recovery compare if i may ask?
[Desire Android Development] mad-murdock:
it got more blingbling, got themes, looks funkier, and got some more features (like partitioning sdcard) - but its mainly the looks and not to use what the crowd uses imho.
[Desire Android Development] mad-murdock:
amon, maybe you missed my idea:

why not make a debug version, which people can flash, which automatically copies recovery.log to /sdcard/last_recovery.log when a restore is done, and maybe even add more debug data to it.

its really hard to trace this bug, since it happens only 1 out of 10 times (from personal experience) - both times, when i figured out, i had a screwed up misc partition, the recovery log was gone already.
[Desire Android Development] Uqbar:
@Amon_RA

I would like to suggest to use the volume buttons as seen on another recovery for the Desire.

Scrolling up and down with the volume buttons (a-la HBOOT) is more precise by far.
[Desire Android Development] thierry_b:
Hello,

I download from a site recovery-RA-desire-v2.0.1.img.

As I'm S-OFF now, i can flash it with fastboot flash recovery.

But I don't find the md5sum that I should have on my file.

This is my md5sum: 528d44d511a27eb30c3105ed54078130 *recovery-RA-desire-v2.0.1.img

Is it dangourous to flash a wrong image file in recovery, or as it's not the hdboot part, it's always possible tl reflash it even with a reboot from fastboot for example (even if recovery is inaccessible due to wrong image file)?

Thanks :-)
[Desire Android Development] Jagdish84:
Ever since i stopped using the USB via the recovery i didnt encounter any USB bricks...
[Desire Android Development] thierry_b:
Hello,

recovery-RA-desire-v2.0.1 works well except that it's just the trackball which is usuable.

I can't use power, or volume -.

Thanks :-)
[Desire Android Development] felenius:
Great stuff.

Guys, i got question/problem. My setup:

S-OFF

HBOOT 0.93.0001

RA-desire-v2.0.0

Oxygen v2.0-RC4 (was at the time)

I wanted to get rid of ext partition in my sd-card, so I did the following in the recovery:

Partition sdcard -> Partition SD -> chose swap-size = 0, Ext2-size = 0, FAT32-size = Remainder.

Everything went kind of OK. I restarted my device, expecting it to boot normaly, since I touched only sdcard. But it's stuck on white screen with green HTC logo. I booted recovery once more, went to Flash zip form sdcard, thinking, I'll flash new ROM. But yeah, "oh surprise", all my ROM zip's gone from sdcard.

So.. Somehow my phones memory was wiped-out next to my sdcards memory? Is that right?

If I'll upload new ROM zip to sdcard and Flash it (I do not have card reader at work to try it now) everything will be OK, my new ROM will bootup normaly? The only thing I lost will be my data on phone and sdcard?
[Desire Android Development] polatkanfatih:
how to install this file?

how to install this img file? it is not zip file to flash from recovery? and what is md5 codes for? can you explain it please......?

thanks....
[Desire Android Development] mi3x:
Wipe only /sdcard/.android_secure :: wipes all apps installed on your sdcard (froyo a2sd).

Does that erase all my sdcard? (including backups from titanium) or is it safe to do this when moving from another rom?

I flashed your recovery, all great, though Id prefer scrolling through the menu with the vol buttons, my trackball only works if I have some sort of fabric on my finger (dunno why, is that normal), it seems not to be working when gently sliding it with my "naked" finger.

Thanks! Awesome job! If you could clarify my question, that d be great!!!
[Desire Android Development] mad-murdock:
changing your positions includes full data loss, same as on pc. So you have a nice newer formatted sdcard now. Gparted is a way to partition without data loss.

Oxygen uses the rc2 partition by default. Deleting it from a running system will make your rom defect. Flashing it new and starting over might work...

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] felenius:
Yeah. After flashing Oxygen 2.0 RC4 it booted up, but I couldn't install any apps from market (is it ROM problem?).

So I recreated ext partition again and headed back to Oxygen 2.0 RC3. Now everything seems to be OK.

Well I got myself a lesson. :)
[Desire Android Development] mi3x:
Ok, the only things that bugs me is that after one flashes a zip, it gets automatically deleted. I don't like that feature at all.

Could that be fixed? Just flashed a theme, got a boot loop and now I had to restore nand, thing which could have been avoided if I still had the other zip I initially flashed on my sd.... But that got deleted after installation.

If that could be done, it seems the best recovery, without that I find myself going back to good old clockwork.
[Desire Android Development] mercianary:
I've never had a zip deleted by this recovery...something else must have deleted it.

The only way recovery can delete a zip is if you format/partition the sdcard, but then you would lose everything.
[Desire Android Development] Amon_RA:
... this recovery doesn't delete a zip after it's flashed.
[Desire Android Development] psygbert:
that's weird. what rom are you using?
[Desire Android Development] mi3x:
Damn, that is weird indeed! I thought that was meant to happen, though I really hated it.

So what gives? It's not like it happened once, it's like about 6 or 7 zips dissapearing after flash. (3-4 themes, some update zips, 1 rom etc.)

Checked them via RootExplorer, checked in recovery, even in usb mode on PC, not there after flashing. No sign of any zip.

So I transfer them there (usually via wifi file explorer), everything is ok, flash them and gone!!

What could be causing this bug (cause it seems a bug if it's not intended).

My setup in signature. Please note I only flashed your recovery yesterday, this never happened to me before with clockworkmod.

I also flashed yesterday the alpharev oxygen table, could that be the cause? If you might know what could be the reason, please share, thx.
[Desire Android Development] psygbert:
there was a bug in certain revision of oxygen 2.0rc4 that deletes files in the rootdir but not directories. you may have downloaded that version. a fixed revision was uploaded yesterday. just redownload it.
[Desire Android Development] mi3x:
Voila! You are completely right! It had a bug indeed. Many thanks, glad I found it out!

As RC5 will be available this evening I wont be bothering with its fix, will wait for the update! Sticking to amonra! Great!
[Desire Android Development] kalua1985:
Can Someone upload the img for me again, I get a 404 error on the link in page 16
[Desire Android Development] mi3x:
Here you go!
[Desire Android Development] kalua1985:
Sorry I meant the 2.0.1 version. The link on page 16 of this topic isn't working anymore.
[Desire Android Development] vivmar:
here u are!

2.0.1

http://hotfile.com/dl/93254723/41761f6/recovery-RA-desire-v2.0.1.img.html
[Desire Android Development] twallden:
I'm sure the answer is in this thread somewhere, but why isnt 2.0.1 on the first post?

Can i use it?
[Desire Android Development] Uqbar:
Because it's beta and considered not ready for release.

Yes, you can, at your own risk (like everything else here). There'd be a link earlier in this forum.

Please use the friendly search button, anyway.
[Desire Android Development] twallden:
And search for what? '.01'? And i did look through the pages, thats how i found it in the first place... Just didnt have time to look through all pages.
[Desire Android Development] Uqbar:
Why '.01'? Try '2.0.1'

But if you don't have time, don't waste it. Wait for the final release: it will show up in post #1.
[Desire Android Development] mr.r9:
Nexus 1 is getting all the attention, they are at version 2.1.1:(

:p
[Desire Android Development] kmetek:
how to install this Amon Ra's Recovery 2.0 ?
[Desire Android Development] najar360:
if you s-on,use unrevoked 3.1 or 3.14

if you s-off,use terminal or fastboot
[Desire Android Development] kmetek:
s-off on used unrevoked 3.3 and it installed me clockworld recovery? :(
[Desire Android Development] najar360:
you must change custom recovery
[Desire Android Development] kmetek:
oh run it, and there is change custom recovery? and load .img?
[Desire Android Development] psygbert:
before connecting your phone, run unrevoked then file -> custom recovery then select the amonra img then connect your phone.
[Desire Android Development] kmetek:
many thanks! that's what i was doing wrong, plugged phone before..hehe.
[Desire Android Development] flyingff82:
I'm having some trouble.

S-ON, so i wanted to install it with unrevoked. But when unrevoked says "running root..." nothing happens and it finishes with the error "firmware too new?".

With the original clockworkmod i didn't get any errors and it worked fine, but clockworkmod itself doesn't work for me...

Any ideas? I just need a working recovery on the phone...
[Desire Android Development] najar360:
have you try using unrevoked 3.1 or 3.14?
[Desire Android Development] flyingff82:
actually i used 3.31, is the first time with unrevoked for me, so i thought the newest version should do it right...

p.s. now i tried it with 3.14 and this doesn't work neither. After rebooting it tells me "failed to flash recovery image".

Now i've tried so many different ways (unrevoked, via terminal, adb...) and it just won't work. -.-
[Desire Android Development] walterdimov:
I have same problem.

My actions:

I bought a phone (PVT4, S-OFF, erase size 4000) 2 weeks ago.

I flashed with Unrevoked 3.31 (Clockwork mod 2.5.0.7)

Phone is rooted but recovery doesn't work - that means - i can enter into CWM recovery menu but i got error Can't find MISC, Can't find cache...

After that I red somewhere on xda forums that somebody put RA 2.0.1 and confirmed that RA recovery is working.

So... i downloaded recovery-RA-desire-v2.0.1.img and flashed with Unrevoked 3.31 and i got error "Firmware is to new?"

Also tried with Unrevoked 3.14 but got different message - "Failed to flash recovery"

That's all :)

What should I do next to make recovery work?

Tnx
[Desire Android Development] Schwarz33:
Same things happened with me.
[Desire Android Development] onyxer:
I have had same problems. I flashed latest offical RUU ROM and than flashed with unrevoked by using amon-ra.v2.0.0 img. Finally i have an working amon-ra recovery
[Desire Android Development] walterdimov:
Hmm... can you put some manual or something "how to do it" because im stilln newbie in that.
[Desire Android Development] flyingff82:
At least i am not the only one with this problem. Couldn't solve it till now.

Please Onyxer, give us some instructions how to get RA on the phone.

As already written i tried even installing it with terminal, but got flash_image error. Pushing the file didn't work because of permission errors.

My rom is the latest original rom, only rooted with unrevoked.
[Desire Android Development] najar360:
last time i try to upgrade recovery using 3.21 and it cause lost my recovery.

then i try using unrevoked 3.1 and i successfull add back recovery.
[Desire Android Development] mad-murdock:
If you cannot get unrevoked working to replace your recovery, you can still go the s-off way, which you will probably go anyways when advancing deeper into all this android stuff

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] Schwarz33:
Successfully flash RA-2.0 recovery with unrevoked 3.31 after uninstall zy.exploit service from the phone memory after getting a root.

Sorry for bad english.
[Desire Android Development] walterdimov:
Still doesn't work... Unrevoked said after reboot: Internal Error: am reported error starting service

I tried to enter into recovery... and I saw old broken ClockWorkMod 2.5.0.7.

Anyway... now bootloader says S-ON... i dont understand... it was S-OFF before flash.

HELP, pleaseee!
[Desire Android Development] walterdimov:
Partially solved.

Unrevoked service was installed on SD card because I had application "A2SD Froyo"

I removed A2SD an Zysploit application and everything went fine. AmonRA 2.0.1 is working.

But now... I need to S-OFF a phone... i want to put custom rom?

Any easy way to to S-OFF?

Tnx
[Desire Android Development] joechung:
Technically, you don't need to be S-OFF to install custom ROMs (unless specifically mentioned by the ROM makers).

But if you want to S-OFF anyway, here's a good guide using AlphaRev. I just did mine yesterday using the CD method. S-OFF'ed in under 10 minutes. AlphaRev 1.8 also offers to install CWM-AlphaRev Recovery 2.5.1.8, but that's optional.

Do note that if your device is PVT4 (erasesize=40000), you might want to forget about flashing the patched HBOOTs listed in http://alpharev.nl/ as they're not supported for these devices, yet.
[Desire Android Development] marcadam:
Nice work

Nice work! Clockwork wasn't clearing my dalvik cache properly, no problems here. It's also nice to have a one click option to wipe all stats. :)
[Desire Android Development] technologylover:
Thanks for this great recovery :D After using clockworkmod I decided to change to AmonRa and I have no problem with the recovery at all. I installed using fastboot and didn't have any problem :)
[Desire Android Development] Borat38:
So I have to S-OFF via AlphaRev first before putting in Amon-RA? Or it doesn't matter which I do first?

Btw, mine's a Desire 2.2 w/ PVT-4, erasesize 40000.

Thanks for any help.
[Desire Android Development] psygbert:
doesn't matter. if you're not s-off, flash it via unrevoked way. if you're s-off, you can do the fastboot way.
[Desire Android Development] Borat38:
Thanks dude! Understanding the process better now.
[Desire Android Development] GuestK00150:
Problem flashing ROM

Hey Amon_RA!

Thanks for your work and your really good recovery!

I was encountering a problem when flashing Amethist 2.3.1 R3 ROM. Would be nice if you could have a look into this:

http://xdaforums.com/showpost.php?p=10454963&postcount=142

THX in advance
[Desire Android Development] Borat38:
Unsuccessful Amon-RA flash

I keep getting this in Terminal:

"flash_image: not found"

This despite repeatedly confirming in Windows that "recovery-RA-desire-v2.0.0.img" is already in the SD Card.

What might've gone wrong?
[Desire Android Development] psygbert:
you have no flash_image - http://xdaforums.com/showthread.php?t=687280

the binary there should work.
[Desire Android Development] Amon_RA:
You are trying to execute the binary "flash_image" and you get the message "flash_image: not found" => it means that you don't have the binary "flash_image" on your phone. => Put the binary flash_image on your phone, chmod it and run it again. :-)
[Desire Android Development] roalex:
Could you possibly add the erase_image binary ? as it is now the one from CM is not working due to a shared library or something.
[Desire Android Development] Nkata:
I have a problem.

Can you help me?

I can't load recovery from bootloader. White screen with green HTC, but from Rom manager and other programms recovery works perfect.
[Desire Android Development] bluelavender:
That means your recovery is not flashed permanently. It's "fake" flashing of recovery, which is usually done via rom manager.

To be able to load from bootloader, you must either flash it via unrevoked or fastboot method
[Desire Android Development] Terepin:
Amon, how about give us new version? ;)
[Desire Android Development] Alex-V:
not new and not tested but with reiserfs

http://www.multiupload.com/1Z92EHH9T6

with kind regards..Alex
[Desire Android Development] Amon_RA:
Alex-V : Which kernel source did you use? I'm looking for an official Desire kernel source that supports both LCD and AMOLED.
[Desire Android Development] Alex-V:
i used coutts latest sense svs kernel...I think it should work also on slcd..or...?

i inly changed : boot.img-kernel

this is how i make it: http://xdaforums.com/showpost.php?p=10508574&postcount=443

and here also the working clockwork version: http://xdaforums.com/showthread.php?t=839640&page=44

with kind regards..Alex