yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] jmorton10:
I'm curious, why does anybody prefer CWM over amon-ra??

It seems to me they are almost identical. I always used CMW in my Droid Charge etc & was upset when I saw it was not compatible with the Rezound.

At that point however, I installed amon-ra & realized it was almost identical to CWM & has worked perfectly for me for months now (I have done a half dozen restores from it and everyone worked perfectly).
[HTC Rezound] mjh68:
I think one reason some prefer it is just comfort. I used it alot when I first got my OG droid because it made changing roms so simple. Another benefit is being able to name your backups by name not just date and time. All that aside, I have been using Amon Ra exclusively on my Rezound and haven't had any issues. I don't like the ability to not being able to name your backup , but that is the only issue.

All that, I will probably try out the official clockwork touch recovery once Koush releases it to try it out ;)
[HTC Rezound] computerfreek:
You can rename you amon backups! I do it I just do the backup then connect to the SD card or from a file manager and rename the one I had just made. Just do not have space's in the file names.
[HTC Rezound] hgoldner:
+1 to the preceding; renaming is easy.

I'd like to see whether Koush's Rezound CWM has the facility to re-root the phone that Amon Ra does. That was a life saver during the OTA change-over.
[HTC Rezound] jmorton10:
I guess that's a good feature.

I always rename mine on my card after the fact (which is easy enough) but that sounds a little more convenient.
[HTC Rezound] jmz:
I can do that with CWM.

---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------

No it won't but it is as simple as flashing superuser.zip from androidsu.com
[HTC Rezound] RED ZMAN:
Request that he builds that in!
[HTC Rezound] superchilpil:
There's a root zip in Rom manager
[HTC Rezound] jmz:
That's true also
[HTC Rezound] localceleb:
this is a silly aesthetic question just out of curiosity, but what color is this version? I know they've changed colors in the past with each big update. Just wondering...
[HTC Rezound] themusicmonkey:
Just tweeted earlier:

@clockworkmod: Rezound users, you will want to grab the new ROM Manager off the Market (5.8.0.4).
[HTC Rezound] jmorton10:
I have always had the paid version of CWM and I want to try the new touch version, but I have a question:

I have Amon ra installed and it works fantastic. Can I have this still installed/working alongside CWM ?? I know 100% that the ar restores work perfectly and no matter how cool CWM touch is, I'm not going to install it if it disables what I know works 100% now.
[HTC Rezound] TheRedmonian:
Cyan.
[HTC Rezound] hgoldner:
Not sure what you're asking. If you're asking whether you can run ROM Manager on the Rezound, sure you can, but there's no interface with Amon Ra (and, frankly, I cannot see why you would want to do this). If you're asking whether you can run CWM recovery AND Amon Ra (I don't think you are, but just in case), NO, you can't run two recoveries.
[HTC Rezound] JohnShaft69:
hes saying that he wants someone to come forward and say that backups and restores and general operability are sound before he leaps from a completely perfect amonra install. i feel the same. although touch is REALLy intriquing...
[HTC Rezound] dsb9938:
Everything is working fine.

Sent from a deranged mind.
[HTC Rezound] Keanen:
Updated from Amon RA via ROM Manager, when I choose anything from the main menu it just blanks out the menu.
[HTC Rezound] jmorton10:
That is it exactly.

---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------

That is the kind of thing I DONT want to hear.

I think I'll stick with amonra for now.
[HTC Rezound] rfarrah:
That's..... not good. Maybe I'll wait a day or two or three.
[HTC Rezound] Quantumrabbit:
Mine seems to work fine. I've done a backup, not a restore yet. I may do that yet this weekend, but menus seem to work and what not.
[HTC Rezound] jmz:
Everything works just fine for me. Try a reboot and do it again
[HTC Rezound] buckifvr:
Are you using the regular version or the touch version of CWM. Also do you guys know whether CWM will restore a Nandroid that was made with Amon Ra? Or are Nandroids specific to the Recovery that made them?
[HTC Rezound] esheesle:
Am still getting the freezing with backups. Gotta recreate my .hidenandroidprogress file.
[HTC Rezound] jmz:
I tried both. The regular because I was mobile and now the touch.
[HTC Rezound] jmz:
Yeah most likely.
[HTC Rezound] buckifvr:
What does recreating a hiddenandroidprogress file do?
[HTC Rezound] ogre150:
I downloaded the touch cwm .IMG. Can I take the ph98img.zip that has amon ra recovery in it, switch out that recovery.IMG and rename the touch recovery to recovery.IMG put it in and load in bootlader?

Just wondering if that would work.

Then I took an arrow in the knee...
[HTC Rezound] jmorton10:
Restores are the only thing that count really.

Nobody can claim a BU system works until they have done at least one successful restore.

---------- Post added at 10:03 PM ---------- Previous post was at 09:58 PM ----------

Amon Ra will restore a CWM BU, but I don't think it works the other way around although I've never tried it.
[HTC Rezound] con247:
Yes, that will work. You need to use 7zip to open the archive though, don't extract and rezip
[HTC Rezound] Keanen:
I did reboot and reflash through ROM Manager. I will use clean flash to go back to Amon and try again tomorrow.

Thanks for supporting the Rezound, it's a great device!
[HTC Rezound] buckifvr:
I installed CWM Touch, Rebooted, and tried to backup twice and it stalls out and just hangs. I never had a problem with Amon Ra, I think I might go back to that for now.
[HTC Rezound] Taebom:
I pushed recovery through adb and made a backup just fine. About to do a restore.

Edit: Did a restore from a back up i just made and it went well. So far cwm is working perfect for doing back ups and restores, for me that is.
[HTC Rezound] Doddzilla:
I made a back up using touch and it worked fine. Have not tried restore yet.

Edit: was unable to restore back up I had made. No idea why it didn't work.
[HTC Rezound] mjh68:
My biggest question, doesn't look like you can reboot to bootloader like Amon Ra. I like to install all my kernels via fastboot so this issue will force me back to Amon Ra. Fun to play with, but I need a recovery to be functional not fun. No idea, why he didn't code that functionality into it for the rezound when we are S-on..
[HTC Rezound] Taebom:
What error are you getting and how did you install cwm? i did mine through adb and have absolutely no problems making or restoring my backups.

---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------

Koush just got a rezound, maybe he'll add it in the next version. I too like the many features amon has that's why i switched back. I just wanted to try it out and help test out the back up and restores.
[HTC Rezound] bigbigdad:
Quick Boot is free on the android market and it has recovery and bootloader options (although I've only used the recovery).
[HTC Rezound] Taebom:
he was talking about rebooting while in recovery.
[HTC Rezound] zeroxg4:
If you're using fastboot to flash the kernel's boot.img, then you can simply adb reboot bootloader from cwm.
[HTC Rezound] Marine6680:
The touch version costs through the ROM Manager app. If we install it manually it is free. If an update for the touch recovery comes out, and we installed it manually, we will need to do the update manually as well because ROM Manager will not? If we buy the touch recovery though ROM Manager, how is the purchase tracked across full device wipes and different ROMs?

Just curious, I use the regular version, I don't need to use touch for everything. :p

I am having an odd issue with CWM...

After entering recovery, any menu selection I make just blanks out the screen. (the CWM logo is still visible but no text) If I hit the power button it will return me to the main menu. Even selecting reboot does not work, only get the blank screen.

Edit:

Tried reflashing the recovery from ROM Manager and still no go. Next I manually installed the touch version, and it works fine. Maybe I need to install the regular recovery manually and it will work.
[HTC Rezound] lomar24:
it takes you to a market link, so it links to your google account. i can't wait for Koush to dev on this, it's gonna get crazy!
[HTC Rezound] mjh68:
True, just tried it out and it worked fine ! Thanks , wasn't thinking about that :)
[HTC Rezound] jmz:
The power button is not the select button. The home button is. Try doing it that way
[HTC Rezound] jmz:
Or choose reboot and hold down the vol key while rebooting
[HTC Rezound] bigdad1963:
Not sure if we had the same thing, but on mine the enter option is mapped to the home button, volume up and down moves between options and power button is back. When i hit the wrong button (like i was still using my og Droid) it would black out to the logo screen, but just hitting power takes you back to the last screen

Edit: sorry, day late and a dollar short
[HTC Rezound] maniac2k:
Does anyone know the fix for backups freezing? Ive download the latest rom manager and flashed the newest recovery twice.
[HTC Rezound] jmz:
Adb shell

touch /sdcard2/clockworkmod/.hidenandroidprogress

Exit

Do that when booted normally
[HTC Rezound] Doddzilla:
This works for back ups and restores?
[HTC Rezound] maniac2k:
Created file with es file Explorer and the backup completed. Thanks.
[HTC Rezound] Flyhalf205:
Are you using the touch recovery or the standard?
[HTC Rezound] jmz:
It will work on both
[HTC Rezound] dsb9938:
If you go in ROM Manager settings and select fast backups/restores it creates the file for you.

Sent from a deranged mind.
[HTC Rezound] Flyhalf205:
I still see the file names when backing up even with that selected but I don't have any problems backing up :D
[HTC Rezound] maniac2k:
Yes, im using touch. Also, ive tried checking the quick backup options in settings and still got a freeze and xould see filenames as they backed up. Had to create file manually.
[HTC Rezound] jmichaels1982:
couldnt get the touch to work

I couldnt get the touch to work because my hands were too busy cleaning up my pants after working with clockwork recovery touch ...

On a serious note. after applying the adb fix, everything works. I performed a back up. then wiped system,data, boot, cache, dalvik and restored to make sure every thing checks out. and it does

I am so amused, just when i thought my life couldnt get any easier.

dont have any doubts flashing this. it absolutely works ! ( after the adb fix)
[HTC Rezound] tbot:
So I manually installed CWM thru adb and have the premium version of rom manager but it doesn't recognize I have CWM installed...any ideas?
[HTC Rezound] isdnmatt:
I'm getting lockups during Backups. It's shows the file name and then locks up. Anyone have any suggestions?
[HTC Rezound] esheesle:
Create an empty file called .hidenandroidprogress in /mnt/sdcard/ext_sd/clockworkmod/

---------- Post added at 08:39 PM ---------- Previous post was at 08:14 PM ----------

Wonder if there would be a way to get the stock recovery flashable via rom manager as well so whenever an OTA comes around we can flash using that, then restore root and reflash cwm or amon ra. Ideas?
[HTC Rezound] jmz:
You need root to do anything in Rom manager
[HTC Rezound] esheesle:
Yup, well aware. Hence my reroot comment. OTA Rootkeeper can solve the norm OTA lose root problem.
[HTC Rezound] AshtonTS:
Which is better: This or amon ra?
[HTC Rezound] jmorton10:
Although I have the paid version of CWM, I am sticking with Amon Ra for now.

I know the new touch looks cool and all, but the one and only thing I really care about with a BU app is that it restore a BU perfectly 100% of the time and AR does that perfectly for me.

I remember all too well various BU systems in the past where you would think you had made six perfect backups in a row only to have it freeze solid the first time you tried to restore the system. There isn't a worse feeling in the world........

I don't want to be scared sh!tless every time I have to restore my system and with AR I don't think twice about it anymore.
[HTC Rezound] Doddzilla:
Same here, added file with es file explorer and can confirm backups and restores work with touch recovery. Thank you guys.
[HTC Rezound] mkeith813:
I was always a big Clockwork fan but since I've started using AR I have to say I do like it better.
[HTC Rezound] AtLemacks:
AMAZING!

10char
[HTC Rezound] superchaos:
recovery.img?

OK, a fool I am. When I download this file, it is downloaded as recovery-clockwork-touch-5.8.1.4-vigor.img

On the fastboot command, recovery.img cannot be loaded. Do I need to go fastboot flash recovery recovery-clockwork-touch-5.8.1.4-vigor.img to get this to load? It is not downloaded in a zip file. It is downloaded in a .img file. So I am unable to strip the recovery.img file out of it.
[HTC Rezound] NilsP:
Do not strip anything just do the fastboot that you outlined with the full name of the .img file
[HTC Rezound] jmz:
Correct command is

fastboot flash recovery nameofrecoveryfile.img
[HTC Rezound] NilsP:
Wow, did I have a bad day yesterday with the latest RM and the paid version of touch.

Prior to yesterday backups worked fine, restores worked fine, could install ROM's and even flashable zips.

Yesterday my backup restored but the phone would not boot (3 times with 2 different backups). I tried to install the ROM and it could not open the zip file. Tried flashing a flashable kernel and the zip failed etc. etc. etc. Even renistalled CWM touch. Tried everything with no luck.

I can't afford to worry if it will work so I am back on Amon Ra until this is ready for prime time.
[HTC Rezound] jmz:
Must be something corrupt. I haven't seen this happen and I work on so many things and I flash and restore 5-8 times a day
[HTC Rezound] jmz:
Also, with the restore you have to manually restore boot.img through fastboot
[HTC Rezound] NilsP:
I think you missed my point.

It was working fine until yesterday. Every one of the files I tried to flash with CWM had been flashed by CWM before and they then flashed fine afterwords with Amon Ra. The same backups had worked and restored with CWM before but not yesterday. So yes, something was corrupt, it was CWM. My point was that if it works OK for a couple of days then craps out I can't rely on it working.

I am a big fan of CWM and always have been but I can't afford to be paranoid about whether it will work or not the next time I need it. Which by the way is daily.

On the flashing kernels, if you look at my thread on flashable kernels and mt ROM's you will see that the kernels are all flashable in recovery which installs the libs then automatically reboots to bootloader to install the boot.img.
[HTC Rezound] jmorton10:
posts like this are EXACTLY why I'm sticking with Amona Ra for now.

I don't care how cool the touch app looks & I could care less what color it is. The one & only thing I need from my BU system is to know I don't have to be a nervous wreck every time I restore the system hoping it doesn't error out.

I am a long time paid user of CWM & I always loved it, but I have never had one single problem with AR (I click on a restore, go have a cup of coffee & when it's done the system reboots & everything is fine again) & it's what I'm sticking with for now.
[HTC Rezound] m3Jorge:
Let's stay ON TOPIC!

WOW.... this has gotten out of hand...

I usually don't get involved in useless conversations, but I will try and bring this thread back on topic for everyone's sake:

1) Reporting an error is only helpful if a fix is in mind rather than bashing the developer. So stick to the facts and provide evidence of the error so the developers can actually have a chance a reproducing/fixing the error

Developers test their work, but don't have access to a large QA/R&D team so results may vary.

In fact one could say this community is their QA/R&D team!!!

2) Flashing ROMs is an inherently risky activity, EDUCATE yourself for your own SAKE/PROTECTION

3) Kernels and Boot images are NOT flashable/restorable via recovery, this is NOT a recovery issue but a boot loader lock/unlock design feature/flaw. Those who state kernels flash with their ROMs actually mean a HBOOT flashable zip is copied to SDCARD and phone is rebooted to HBOOT for flashing in HBOOT NOT RECOVERY!!!

4) SDCARDS/FLASH memory are a common failure point to flashing community due to all the wiping/writing and mounting/unmounting that is part of the flashing process, so AGAIN not developers fault!!!

If any of my statements above offend you they shouldn't as they are simply factual in nature.

If you feel any of my facts are incorrect feel free to provide FACTUAL information about it!!!
[HTC Rezound] jmz:
Exactly what I was trying to say but a lot better this way. Lol
[HTC Rezound] NilsP:
I agree with everything you said, Read my comments in the thread.

I did say I had a problem but I apologize if I don't have a fix. Third time by the way. The solutions provided did not help and that was all I was saying. It is also a problem others have reported and I only did it so others are aware it can happen. Koushik's actual recommendation is to reinstall recovery and I did and it works with the same sd card and same files.

I never said boot.img's were restorable via recovery and in fact said the flashable zip I use installs the libs then reboots to bootloader to flash the boot.

I think I am slightly educated in flashing ROM's

And I apologize for reporting a problem I had so from now on I won't bother. I was not bashing the developer or the product and I am not the one that flew off the handle.
[HTC Rezound] jmz:
Because I gave you a possible solution and you talked down to me like a noob. That's why it went down the way it did. I have built many recoveries for many devices and this is the first time I heard an issue like yours that couldn't be solved by reformatting sdcard. Or move the file to internal and try flashing that way
[HTC Rezound] NilsP:
I did not talk down to you I told you what I was doing. You just took it wrong.

Yeah, I could have spent hours and pages outlining everything I did and one point I failed to mention was that some of the files were on the internal. All I was trying to do is point out the potential problem no matter the cause.

In the end I flashed Amon Ra to get out of the hole and it worked with the same files. I then reflashed CWM which also fixed it using the same files but now I have to wait and see for how long. Like I said, this was the 3rd time the ROM restore failed (nothing to do with the kernel) and from different sd cards and internal.

I happen to be a long time user of RM and CWM and want it to work.
[HTC Rezound] jmz:
And all my point was that recovery cannot go corrupt except in extreme cases where an outside force screws with /recovery. Recovery itself writes nothing to /recovery.

On a troubleshooting note please pull /tmp/recovery.log if it errors out on you again. That's would be more productive
[HTC Rezound] NilsP:
There was no recovery.log. First thing I looked for after 2 zip file failures. If it does not create a recovery.log nothing I can do. Even looked after I got it to boot.

Also, there were no errors with the restores either. They ran good but would not boot. And it was nothing to do with the kernel since it was the kernel (boot.img) for my ROM that was installed already.
[HTC Rezound] jmz:
You have to manual pull while still in recovery. /tmp/recovery.log. it is always created and started as soon recovery loads. But is gone when exited your recovery

But it just came to me why restores might not be working for you. I am pretty sure that the restore nukes your boot partition before restoring. Just for ****s and giggles next time you restore and it doesn't boot, just flash the appropriate kernel. If this is the case I will get with koush and get that disabled in our build.

Like I said before I'm not home right now else I would look at the source and figure it out on my own
[HTC Rezound] NilsP:
I know that. It was not there to pull in recovery. I didn't expect it to be there after booting but looked anyway.

I suspected the same thing with the restore wiping the boot image which is why I was trying to install a kernel with my zip files which would not open. Even after flashing in fastboot the phone would still not boot. Never got past the htc screen.

I restored then with Amon Ra and installed my kernel using my zip files and all was fine.

I do however agree that that needs to be taken out of restore.
[HTC Rezound] jmz:
Hmm. Ok I should be going home for a bit later and will look at the source and see if I can pull the log. That's really wierd. So it just says file not found when you try to pull? I'm only asking to be clear so when I look at it I have a clear idea of what's going on
[HTC Rezound] NilsP:
OK, I used a file that I know is bad from both CWM and Amon Ra and did get a recovery.log

Here is the log but it does not prove anything since I know the file would cause a bad read (Error 0). Not actually a zip. Just had to rename to get past upload

The only difference is this is after reinstalling CWM recovery
[HTC Rezound] m3Jorge:
Just one clarification "I did say I had a problem but I apologize if I don't have a fix" - What I said is that we should provide information (evidence, logs, etc.) so that the DEVELOPER can reproduce the issue to create a fix...

"I apologize for reporting a problem" - I don't believe that is at all ANYONE's intent but rather to focus on providing something ACTIONABLE... i.e. It doesn't work right I think "X" product works better (not actionable) VS When I attempted a restore I got this error "error XXX" I did this to try and fix it "XXX" where do I go from here (Actionable)...

That being said I'm not trying elude that ANYONE did anything wrong but rather try to bring focus back and provide some contextual guidelines to stay on topic...
[HTC Rezound] jmz:
That is interesting. So it will create it randomly is basically what you ate eluding to correct?
[HTC Rezound] NilsP:
Not sure about randomly. Just didn't create any when it was failing on me. Creates it every time now that I have reinstalled CWM.
[HTC Rezound] dsb9938:
Re-opened.

D
[HTC Rezound] dsb9938:
Some things.

The official version is not my work, I really have no control of it.

My version defaulted to the external SD, the official defaults to the internal. You can change this in rom mgr settings.

Creating the .hide file or checking the fast backup box may or may not work if you do switch which sd card you use without doing it over.

You should check both int and ext SDs and see if you have a clockwork folder on both.

The Rezound seems to be very touchy about corruption, or very prone to it, in my opinion. If you are having issues, wipe the cache partition and see if that helps with reboots and things not working right.

Please don't fight in threads, it makes it hard for people to actually help each other.

D
[HTC Rezound] NilsP:
Yes, if you move backups option to sd card you do end up with two clockwork folders (internal and external) but it does not put the hide file on the sd card. I just copied it from the internal and it worked.
[HTC Rezound] jmz:
I will look at it more over the next week or so. I am only home for a few mins then back to the hospital but I will see if I can talk to koush about removing the nuking boot thing.

While I am there I will be reflashing recovery and backing up and restoring seeing if I can recreate any type of corruption.

Where you going between ICS/GB? or did it not matter?
[HTC Rezound] NilsP:
Does not matter. I just happened to be testing my ics and then restoring when it went haywire on me.