yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] S4Rs:
I have it working the way i want now, but its really strange. So i can install clockwork recovery 3.0.0.5 from either a PCxxx.zip when I enter Hboot, or if i use flash_image from a terminal, but Rom Manager and fastboot do not work.

Fastboot says remote not allowed.

Rom Manager says it worked fine (this needs to be fixed in the app) and didn't work. However RomManager will install Amon Ra 2.3 no problem.

Terminal Outputs this when I install it which isn't right (however this method seems to work)

export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$su
# flash_image recovery /sdcard/recovery-cm.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
flashing recovery from /sdcard/recovery-cm.img
mtd: successfully wrote block at 0
mtd: successfully wrote block at 20000
mtd: successfully wrote block at 40000
mtd: successfully wrote block at 60000
mtd: successfully wrote block at 80000
mtd: successfully wrote block at a0000
mtd: successfully wrote block at c0000
mtd: successfully wrote block at e0000
mtd: successfully wrote block at 100000
mtd: successfully wrote block at 120000
mtd: successfully wrote block at 140000
mtd: successfully wrote block at 160000
mtd: successfully wrote block at 180000
mtd: successfully wrote block at 1a0000
mtd: successfully wrote block at 1c0000
mtd: successfully wrote block at 1e0000
mtd: successfully wrote block at 200000
mtd: successfully wrote block at 220000
mtd: successfully wrote block at 240000
mtd: successfully wrote block at 260000
mtd: successfully wrote block at 280000
mtd: successfully wrote block at 2a0000
mtd: successfully wrote block at 2c0000
mtd: successfully wrote block at 0
#

My bootloader is definitely in a weird state now as I upgraded hboot, which reverted to S-ON, so then I used unrevoked forever to set it to S-OFF. Now when I boot, Holding v(+) sets the phone in qualcomm diagnostics, while v(-) loads me directly into hboot. From there i can get to fastboot.
[EVO 4G Android Development] kngoworld:
Will I run into any problems running 3.0.0.5 on my CM7 Evo?

I currently run 2.5.0.7
[EVO 4G Android Development] jefbal99:
You will have to ensure that all the zips you flash support edify scripting
[EVO 4G Android Development] CrippleB:
Edit: My bad I copied the whole cwm folder to my new phone. So it also had links to old phone which caused cwm flashing to cease.
[EVO 4G Android Development] ropodope:
Cwm 2.6.0.1 is easily the best version of cwm to use. It's the only version of cwm that supports both scripts. You will need to wipe your cache and dalvik 3 times with cwm to get it all. Amonra 2.3 takes care of it all the first time, every time.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] CrippleB:
Why is that version no longer in rom manager? Only 2.xx5 which incidentally that ver will no longer read my sd card, only folder that shows up is cwm and if I put in zips they dont show either. The only way I can flash is using 3xx5 and it has problems with scripts. I am starting to not like cwm, have had nothing but trouble every since I got my new phone ans rerooted.
[EVO 4G Android Development] jrmatics:
I'm starting not to like it either. The only way I still have 2.6 is cause when I used unrevoked to root, it installs that version and I chose not to update it. Maybe unrevoked bought that version for their program. Just speculating :o
[EVO 4G Android Development] ropodope:
because koush wants to make you get used to just the new script thus fully supporting cm, but the thing is a lot of us who know things about roms dont like cyanogenmod for a lot of reasons and not all developers want to be forced into just one scripting language. As an end user, I certainly have benefitted many times over by using a recovery that will handle both scripting languages.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] CrippleB:
It seems the rom manager program is now headed for the trash on my phone. I can make nandroids with 2.xx.5 and 3.0.0.5 but it will no longer backup my ext3 partition. Says no ext present skipping backup. And 3.0.0.5 wont see my 2x nands. I really loved this app/recovery but lately it seems anything I do with it is flawed. This only happened after I received my new phone so unrevoked/CWM must have changed since I rooted a few months ago. Amon is looking nicer everyday. It pains me to say that because I have been die hard cwm since I started rooting.
[EVO 4G Android Development] ropodope:
It shouldn't pain you at all. it looks good, works great has a ton of options and works the first time, every time.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] aliartos:
had the problem with radio version.moreover could notflashnew radio cause recovery.downgraded to 2.5.1.4 and everything ok.Thnx for your help
[EVO 4G Android Development] generalExpert:
Just updated my CWM from 2.6.0.1 to the newest and was having problems flashing radio... Downgraded again and all is well.
[EVO 4G Android Development] github:
Radio flashing works fine for me no matter which recovery I use. Since you didn't give any details I take it you didn't want any help and just wanted to complain.
[EVO 4G Android Development] github:
fastboot won't work unless you have the 0.76 Engineering HBOOT.
[EVO 4G Android Development] mazook98:
Seriously.????

Look, I'm Definitely not a CWM fan, not at all...in fact, this has nothing to do with recoveries at all.

This has to do with the basic computer model, and how a computer works.

The simplest way to say it is simply:

A Computer will do EXACTLY what you tell it to do.

(That's It: nothing more, nothing less.)

When you tell your 'computer' to 'wipe dalvik cache', it essentially runs a script with an EXACT function. If it wipes it the first time, then it's WIPED. It was SUCCESSFUL. If it worked the first time, then running it again would be silly. YOU WOULD BASICALLY BE ASKING A COMPUTER TO RUN A SPECIFIC INSTRUCTION SET AND EXPECTING A DIFFERENT RESULT.

On that note, if it DOESN'T wipe the first time, then the script FAILED as an instruction set for the 'computer'. IT'D BE POINTLESS, BY THE DEFINITION OF WHAT YOU'RE DOING, TO RUN IT MORE THAN ONCE. It's NOT going to try anything differently the second, third, or BILLIONTH time you tell it to 'wipe dalvik cache'.

Try to remember this anytime you see instructions to wipe anything in recovery more than once. It's just overkill, and it's essentially just wasting your time.

Yes, this drives me crazy.
[EVO 4G Android Development] ropodope:
Tell that to the many who cwm does not wipe properly for but does wipe if done several times if using cwm. Instruction set or not cwm is known for not wiping properly. Amonra rocks.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. Gapps? What are gapps?
[EVO 4G Android Development] ropodope:
Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. Gapps? What are gapps?
[EVO 4G Android Development] mazook98:
Not true about CWM. If it doesn't work the first time, just because you think it worked the 2nd or third, then it's just a placebo effect. Think about what you're saying, and have a look at this perhaps..

http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache

Sent from my 3DeeVo
[EVO 4G Android Development] ropodope:
I really don't care because I know that cwm sucks and have no tolerance for it. Most know that cwm is problematic to reiterate, if they want to keep cwm then they can know that their wipes are taking hold by flashing calkulin's format all or clear temp depending on what they are trying to accomplish. Placebo effect or not, doing that or using amonra 2.3 will get the job done and you don't need to read an article to know that. Thx.

EDIT: in other words cwm is bad software, even the author of your article does not discount that, in fact they crossed out a line in their own article where where they were about to imply differently.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. Gapps? What are gapps?
[EVO 4G Android Development] mazook98:
I'm wholly confused. My statement began by saying that I wasn't talking about ANY recovery at all. I, in fact, think CWM is inferior to Amon Ra's and always have. The point I was trying to make ONLY had to do with how idiotic it is to 'wipe cache' more than once...But you keep bringing up ClockworkMod, and this statement was specifically NOT pertinent to any one recovery...Did you accidentally quote the wrong person?

Sent from my 3DeeVo
[EVO 4G Android Development] CrippleB:
He probably just assumed because this is a CWM recovery thread. I for one did think this convo was about CWM and have also been told by devs to wipe extra w/CWM
[EVO 4G Android Development] ropodope:
right on, you said it. Perhaps this article would do more good for the developers since these smart guys are apparently idiots for telling the users to do this when it comes to cwm.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2.2 for evOG. Gapps? What are gapps?
[EVO 4G Android Development] eraser0:
hey

for the lock screen

i installed it from cwm >> install form zip

it installed succesfully

but how to apply it?

the pictures was not there

please help :)
[EVO 4G Android Development] bhint15:
Can anyone tell me why clockwork doesn't backup my ext3? I tried all 5+ versions and all say no ext found skipping. Trwp does the same thing but Amonra of course does fine. Thanks!

Sent from my Evo with Miui
[EVO 4G Android Development] ropodope:
Because amonra is the shiznit.

ropodope

Deck'd Cream Sandwich v1.3d renobbed + EvoReady 4.1!
[EVO 4G Android Development] Tekn010933:
Very intresting for the time frame it was originally posted.
[EVO 4G Android Development] doejohn:
I don't know why there are so many haters for CWM.

I have been using it since i rooted my evo. Its working fine since then. I have heard very good things about Amon Ra and I think it is a good recovery but I never felt the need to change from CWM.

CWM did have some issue when the version changed from 2.5 to 3+ I guess because it needed edify scripts. I updated to an edify script to wipe everything that's been out and it works all the time. I like CWMs compatibility with Rom Manager. Its easy to make nandroid backups using Rom Manger specially you can name the backup.
[EVO 4G Android Development] ropodope:
if you have to ask why then....oh never mind, why even bother at this point.

ropodope

Deck'd Blues Sandwich v1.3d renobbed + LEE for me!
[EVO 4G Android Development] BorgCymru:
Is this meant to go somewhere called Google GIT ?
[EVO 4G Android Development] fischerben:
can i somehow install ZSJPG modem i would like to try it out, but it says i have to switch to edify scripting?
[EVO 4G Android Development] Zeljko1234:
I don't know what is ZSJPG modem but you can open zip, take file out and push it with adb. Inside zip you could see right path.
[EVO 4G Android Development] DowntownRDB:
+1. That would be fantastic to be able to convert an amend zip to an edify zip.
[EVO 4G Android Development] lowetax:
CWM Recovery

hi koush.

with my evo 0003 i've been using CWM recovery since rooting with unrevoked 3.2.1 in august.

i've never had an issue at all with CWM 2.5.0.1, nor my evo (tada),

and i've done a ton of flashing, modding, nan backups and restores.

i just want to thank you for your time and effort and contribution to this awesome android community.

props!

i too shot and then asked questions later, installing 3.0.0.0

(something i normally never do - install v x.0)

before reading about anything ! (we live and learn)

now i'm back at 2.5.0.1 - although Rom Manager

says Currect Recovery: RA Recovery v1.8.0

(i had used rom manager to get to that - v1.8.0 unmodified version)

and All ClockworkMod Recoveries only lists 3.0.0.1 thru 3.0.0.4

will RM eventually sync up ?

thanks again ...
[EVO 4G Android Development] illogos:
I'm not sure that my explanation would be that helpful because I do not know the nuances of the differences between CWM and Amon-Ra, but here is my anecdotal evidence:

1. CWM backups after wipe cache and wipe dalvik are about 50mb larger than an Amon Ra backup.

2. Amon RA, without a full data wipe/factory reset, takes about 20 seconds to wipe dalvik. CWM performs the same action without any similar delay on 3.0.0.0 and 3.0.0.2.

3. The format and mount options in advance for 3.0.0.0 and 3.0.0.2 appear not to work. I usually use Calkulin's format all zip before a new ROM but CWM has deprecated the scripting language used in that zip. I figured I could just use the format options in the advanced menu to replicate it, however those commands gave errors instead of working. Namely format boot and format system did not work. I also tried to mnt system and that also gave an error.
[EVO 4G Android Development] illogos:
I realize my post was probably less than helpful, but here is some added info:

My dalvik is located in /data/dalvik-cache as far as I can tell. Terminal emulator lists a lot of .dex files in there. It's an alpha stock CM7RC0 build from CM source that I am running. When I do my backup in CWM it takes a good 15-20 seconds to backup dalvik-cache when it reaches the data backup. (3.0.0.4 now) and there still is no delay at all when deleting dalvik-cache in advanced.

If you give me some testing parameters on how to get you solid information I would be happy to help out.
[EVO 4G Android Development] illogos:
Almost done with my testing of 3.0.0.4. Noticed that my backup after advanced - delete dalvik did not have a 20 second pause on dalvik-cache during backup of data img.

Almost back in rom to see if there is a difference in file size between the two backups.
[EVO 4G Android Development] lowetax:
when i do nan backups, i never wipe anything beforehand.

that way, i restore to image i had when backed up.

are you just wiping before backup just to prove your point ?

if you don't wipe anything and back up with both amon ra and CWM,

is the file size the same ?
[EVO 4G Android Development] aduljr:
Well that clears up why things didn't work. Thanks for the update.
[EVO 4G Android Development] illogos:
I was trying to test the claim people were making regarding dalvik-cache not being wiped.

First a positive note: 3.0.0.4 seems to be working perfectly on HW004. I can use the mount/storage options without errors now when formatting system/boot/data/cache. Also, dalvik-cache appears to be getting deleted just fine.

CWM backup without clearing anything was 343MB. After clearing dalvik: 300MB. After both cache and dalvik: 300MB. (cache before wipe was something like 85k after wipe 22k)

Comparing CWM to Amon Ra(Both having done a wipe cache and wipe dalvik cache)

Secure: 36.5MB vs Not Backed Up

boot: 3.25MB vs 3.25MB

cache: 22.64K vs 10.31K

data: 79.32MB vs 79.44MB

Nandoid: 279 vs 219

recovery: 4.5MB vs Not Backed Up

System:151.03MB vs 151.03MB

Wimax: 12MB vs 12MB

Everything seems to be working fine while doing backups and wipes on cache and dalvik cache in version 3.0.0.4.
[EVO 4G Android Development] supdawg:
So when I see a flashable zip floating around that I want to install, I need to know which version it was created in (edify or amend)?

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

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

Is that what I am reading?
[EVO 4G Android Development] Koush:
2.5.0.1 can flash both. (it is an eclair based recovery)

3.0.0.x can only flash edify. (It is a gingerbread recovery)
[EVO 4G Android Development] willy900wonka:
So while an amend to edify (lol) script convert apk, is beyond the scope of recovery; it should be noted that a lot of work is represented in the amend zips. That work should not be lost. I think people see that deprecated does not mean defecated.

This change speaks volumes to the strategy involved in future Android development.
[EVO 4G Android Development] illogos:
Bad news: 3.0.0.4 restore giving an error of

E:can't give path "/sdcard/.android_secure" to format_volume

Error while formatting /sdcard/.android_secure!
[EVO 4G Android Development] tbgreen89:
So I'm on a 0003 evo. Updated hboot 2.10 rooted with unrevoked. I have clockwork 3.0.0.4 installed. I'm trying to install 2.5.0.1 and can't figure out how. I downloaded the file and renamed it PC36IMG.zip and boot into the bootloader nothing happens.. if I flash the zip in recovery it works but once I reboot its back to the 3.0.0.4. Any ideas?
[EVO 4G Android Development] dj_L:
Unfortunately, you are barking up the wrong tree. With *all* of the information reguarding this problem now easily accessible, the picture is quite clear.

This problem goes back to your ROM developers/maintainers. Technically, they never should have distributed ROMs using the old update script method from Cupcake on. Now realistically, they should have been allowed to distribute until Eclair was released. However, *ALL* Eclair and Froyo ROMs should have been distributed having utilized the new bin updater.

To make it plain and simple, just about all of the ROM developers have screwed up in the name of simplicity. Not the first time it has happened, and it won't be the last.

Now, my comments do not mean that I am unappreciative in any way, this is just a minor stumbling block and I don't prefer to sugar coat it. I very much enjoy the plethora of options available to me, and am quite thankful for all of the ROM developers who *give* their time so that we can continue to customize our devices as we see fit.

Give it a couple of days and active developers will have fixed zips ready for distribution.
[EVO 4G Android Development] Persnlmgr:
With that PC36IMG file IN THE ROOT OF YOUR SD CARD, boot into Bootloader, select, then go into, Fastboot and it will automatically find the PC36 file and ask if you want to install it. Hit the power key for yes.

Reboot to your phone/system, let it settle in, then reboot into Recovery. You should be in the "green" version, 2.5.0.1.

It's a bit confusing because ROM Manager will tell you you're still in 3.0.0.*. Ignore this, and don't use ROM Manager until this is all sorted out...
[EVO 4G Android Development] EndlessDissent:
I just flashed 3.0.0.4 and tried to flash the CM7 build for today. Didn't go well.

Wiping was mixed. Mostly, it went fine, but when I tried to wipe dalvik, it gave me an error (didn't think to write it down, sorry), and I tried to wipe it again. As soon as I selected the wipe dalvik option, it said it was done. Usually, when I wipe with Amon, especially with MIUI, which I was wiping, it will take 15-20 seconds for the first dalvik wipe. I chose to wipe dalvik again and got the same instant operation complete message.

I figured "whatever, maybe it wiped," and I went to flash the zips. When I highlighted the Choose zip from SD card option and pressed the power button, it displayed the box with the arrow and android and that was it. When I pressed Power again, the menu reappeared, but no matter which option I picked, it would show the box/arrow/android picture.

Eventually, I pulled the battery and booted back into recovery. This time, it let me flash the zips just fine, but when I rebooted, I got bootloops at the Cyanogen animation.

Long story short, I restored MIUI and reflashed Amon. I hope all the issues in Clockwork get fixed soon, because I'd like to use it.
[EVO 4G Android Development] illogos:
I get a message saying it can't find sd-ext partition when going to wipe dalvik. I think that is normal if you have not setup an ext partition on your sd card. I also noticed there was no 20 second pause like with Amon Ra. However, data sizes on backups indicate that it is indeed wiping dalvik folder correctly.
[EVO 4G Android Development] sicilykill:
I understand your point. I think there was a lot of confusion but it kind of makes sense now. We need to also understand that amend is no longer supported. While the developers (cooks) transition i think the best solution is to stick with 2.5.0.1 which can flash both. Once the transition is completed it would probably be safe to upgrade. just a thought :)
[EVO 4G Android Development] tbgreen89:
Still cant get anything to work! When i got into bootloader it finds the pc36img then doesnt do anything else or ask me to install anything. Im totaly lost now.
[EVO 4G Android Development] illogos:
Just as an fyi this aborts the rest of the restore.

On a related note, 3.0.0.2 was able to do the restore without this error message. However, I was getting FC issues in Market after the restore.
[EVO 4G Android Development] GIGZ1971:
Rom Manager App

@ Koush, is there a way for you to put the old versions (2.5.0.1) of the recovery back in as an option for the Rom Manager App? I think that would help a lot of the people that are having problems right now.
[EVO 4G Android Development] mikeinghilterra:
issues???

Koush,

Thank you for the updated recovery - i started off with CWD and migrated to RA a few months ago and have been waiting for the CWM updates so that i could go revert back to your recovery simply for the fact that i can browse folders and files on my SD card without having to move everything to the root.

i understand that each version of the EVO hardware seems to vary a bit however after flashing the 3.0.0.4 i have noticed a couple of issues and i was hoping you might be able to provide some insight or guidance as to what if anything i can do to alleviate this issues going forward.

I have a V03 EVO with 2.02 HBOOT and S-Off and I am running a dual quad core PC with Win7 and Ubuntu 10.

Mount Dropping - When i go into CWM and mount the SD card via the menu i am finding that in W7 the connection is being dropped or or the mount is lost while transferring data? When i go back to my EVO after the connection has dropped and choose to unmount via the menu CWM recovery just hangs until i pull the battery and restart. Any idea?

Transfer Speeds - Copying the same files via USB my data transfer rates while mounted have dropped from 4-6 mbs (using RA) to 600 - 800 kbs (using CWM 3.0.0.4). I am currently using a Kingston Class 10 - 16 GB sd card. Any ideas?

Zip Files Hanging - While coping the CM 6.1.2 from my PC to my EVO via USB while mounted the zip file transfer is hanging and not completing? i have rebooted my PC and phone and still and experiencing the same issue. I have also been able to replicate the same problem using other zip files (not limited to the 6.1.2 rom)

Screen Tearing? - When leaving CWM via recovery i notice there is quite a bit of screen tearing (not sure if this is the correct term?) is that related to the latest recovery?

I haven't tried replicating these issues in Ubuntu yet but i was hoping you or someone else might have some insight or advice for me.
[EVO 4G Android Development] Koush:
2.5.0.1 should be there
[EVO 4G Android Development] tjeffries4863:
My phone is acting up, started after tried to update to .2 I think. Cannot but to any recovery except the 2.5 that was on there before 3 was out. I am s-on for now. Should I bother messing with CWM or wait until I have time to update my hboot?
[EVO 4G Android Development] illogos:
You need to be S-OFF.
[EVO 4G Android Development] crucial929:
so if i flashed 3.0.0.5 can i flash back to 2.5.01?
[EVO 4G Android Development] GIGZ1971:
@Koush; ok, i found it this time. I think the problem was that I had my phone connected to computer in disk drive mode and rom manager stated that i needed to mount the sd card to use rom manager (when i first looked i seen 3.0.0.1 thru 3.0.0.4). Now that i took the phone out of disk drive mode i see 2.5.0.1/3.0.0.5/3.0.0.4/3.0.03 in that order. is that correct?
[EVO 4G Android Development] illogos:
Yes, it is possible to flash an older version.
[EVO 4G Android Development] GIGZ1971:
I agree!!

+1

This is also one of the reasons I liked ClockWorkMod Recovery over Amon-RA
[EVO 4G Android Development] illogos:
Amon-RA 2.1.1 just came out for EVO. You can browse for zips now too.