Database Info

help with error report on g1 after rc30 w root

help!!!. i am going nuts... i have tried everything .. can some help me .. here is what i get when i go to update the rc30 with root.
android systeme recovery utility
using test keys
E: cant open ?cache/recovery/com
mad
Home+back - reboot system now
ALT + L - toggle log test display
ALt + s - apply sdcard:update.zip
Alt + W - wipe data/factory reset
I then hit the ALT + S and get the following
installing from the sdcard...
finding update package...
opening update package....
E: cant open /skcard/update.zip
(bad)
installation aborted.
press home+back to rebot.
i have reformatted and intsalled on my card. hours of trying.. and my phone keeps telling me to update to the OTA 30 which i keep sayling later to..
any info would be great
thanks in advance... i know totall newbie wants to swim with the sharks..

did the terminal emulator and entered the cd /sdcard
ls -l update.zip
it reponds with
update.zip: no such file or directory
do i understand that it is not seeing a file on the sd card.
settings.. bad file... i am going nuts...

chicagopass said:
did the terminal emulator and entered the cd /sdcard
ls -l update.zip
it reponds with
update.zip: no such file or directory
do i understand that it is not seeing a file on the sd card.
settings.. bad file... i am going nuts...
Click to expand...
Click to collapse
what did u name the file when u put it on the storage card

update.zip

try naming the zip file "update"

extracted or in zip format?

leave it in zip format

now comes back ... after cd/sdcard
"not found"

Go here.... http://forum.xda-developers.com/showthread.php?t=443713 Download from where it says "here" Leave it in zip format name it update.zip and place it on ur storage card n try again

clearly it is not seeing the card let alone the file correct.. but when i plug in the usb to the lap top or use the card holder for the micro on the laptop it sees the laptop sees all the files on the card...
by the way if it is at least at the point of trying to find the card in the terminal emmulator am i at root.... i know this might sound like a stupid question but then again.. look at the number of posts i have...
thanks for your help
at this point it is the principal to accomplish this.... hours working on this and going strong..

trying your update file... while doing that i have a question again..
does it matter that this phone is still... rc19
also... i am using my laptop card reader to place files on the card .. i assume that is not an issue..
thank s

Try moving the file to your sdcard with the card in your phone. Meaning, plug your phone into your computer and transfer the file over. Then unplug the phone from the computer and try the update again.

did it and still no luck..
keeps saying... cd/sdcard; not found
i have been at this all day... there must be some easy ansswer to all this pain
it is not seeing the card..
maybe it is the emulator
but when i do the code to see if i have the img going it comes back with a 1

real quick.... r u sure ur sd card is discoverable in ur settings ?

You have the recovery image installed. I said this over at androidcommunity, but I think the problem is with your sdcard...I think a different card may fix your issue.

it looks like it is trying to install from card but cant... when i do the power on and hold the home key and then do alt+l..then alt+s ... i get
a few statements the last is E:cant open / sdcard/update.zip
no such directory
installation aborted..
maybe i should create a file sdcard and place theupdate file in it.?

Stericson said:
You have the recovery image installed. I said this over at androidcommunity, but I think the problem is with your sdcard...I think a different card may fix your issue.
Click to expand...
Click to collapse
yes... try formatting ur sd card with fat32 name the zip update n try again

hmmm....thats a thought...lol try it

chicagopass said:
it looks like it is trying to install from card but cant... when i do the power on and hold the home key and then do alt+l..then alt+s ... i get
a few statements the last is E:cant open / sdcard/update.zip
no such directory
installation aborted..
maybe i should create a file sdcard and place theupdate file in it.?
Click to expand...
Click to collapse
"DO NOT" create a file !!! it has to be a zip by itself no folder

usmc2k said:
"DO NOT" create a file !!! it has to be a zip by itself no folder
Click to expand...
Click to collapse
What he was suggesting was to take the sdcard out and create a dir named sdcard on the phone and stick the update in there...then when he reboots and does the update the phone would pull the file from there...but after thinking about it...the boot.img would erase it upon shutdown..I believe..anyways it wouldn't work that way....

Can no longer root my phone after JH7 update

I have spent the afternoon trying to re-root after applying the JH7 update I downloaded from AT&T. It kick the root out of my phone and I have tried everything to root the thing again... Unleash the Beast, the basic root, one click root... all I get is this when I go into recovery and click install packages:....
E:can't open /sdcard/update.zip (no such file or directory) Installation aborted
Help!!!

Problem solved... Interesting though. no matter how many times I tried to copy update.zip to the root of the internal SD card, it wouldn't copy. I mounted my phone, opened the the explorer, dragged and dropped/copied and pasted, the phone won't allow the file to be copied to the internal SD. I then took and copied the file to my external SD, then used ROOT EXPLORER to copy and paste into the root of the internal SD, then went into recover mode, re-install packages and then the file was found and installed. I'm not sure whether this has to do with AT&T's JH7 update or not. When I did update, my phone was no longer rooted and my ability to re-root in the normal fashion was gone. Is this something AT&T has done to try and prevent people from rooting??? I don't know, but now I know the easiest way... Use Root Explorer!!!

GaryS1004 said:
Problem solved... Interesting though. no matter how many times I tried to copy update.zip to the root of the internal SD card, it wouldn't copy. I mounted my phone, opened the the explorer, dragged and dropped/copied and pasted, the phone won't allow the file to be copied to the internal SD. I then took and copied the file to my external SD, then used ROOT EXPLORER to copy and paste into the root of the internal SD, then went into recover mode, re-install packages and then the file was found and installed. I'm not sure whether this has to do with AT&T's JH7 update or not. When I did update, my phone was no longer rooted and my ability to re-root in the normal fashion was gone. Is this something AT&T has done to try and prevent people from rooting??? I don't know, but now I know the easiest way... Use Root Explorer!!!
Click to expand...
Click to collapse
if what you say is true, then you will be unable to use your ~14GB of internal storage. I would make sure it is not your pc.

[Q] E: Cant mount /sdcard - CWR

Hi guys and gals. I'm a complete newb when it comes to tinkering with Android, I have a little experience with iProducts as I have mucked around with them for a while. Jailbreaking an iProduct is piss easy compared to this!
I have just unlocked & flashed my Xoom with JWTylers One click method here...
http://forum.xda-developers.com/showthread.php?t=1011196
All works well. In the 'about' section it showed the Tiamat kernel to be 1.1.6, or something like that. I also downloaded Rom Manager and flashed CWR through it. What I wanted to achieve was external sdcard functionality, so I tried reflashing with this step to 1.3.1 ...
http://forum.xda-developers.com/showpost.php?p=13036180&postcount=497
Worked a peach.
So, I did everything step by step, and created a new folder called 'sdcard2' in the sdcard directory. After finishing everything I downloaded the 1.3.2 zip and moved it from downloads to sdcard2 folder with Root Explorer? Ran the CWR recovery and when I go to press the flash zip from sdcard I get an error: E: Cant mount /sdcard".
I dont have an sdcard in the slot while I'm doing this, so, I don't know if this is the cause.
Any help to explaining this would be great!

Hey, just flash the new Timat kernal 1.4.0 and download auto mount from the market and your set!

endine said:
Hey, just flash the new Timat kernal 1.4.0 and download auto mount from the market and your set!
Click to expand...
Click to collapse
Hi, thx for your reply. Can I just download the file directly to'my downloads folder on my Xoom, like I did in the second link I pasted in my post, and follow those steps? I also mentioned that I don't have an sdcard inserted. Would this make any difference as to why I'm getting the error message in CWR?

flombs said:
Hi, thx for your reply. Can I just download the file directly to'my downloads folder on my Xoom, like I did in the second link I pasted in my post, and follow those steps? I also mentioned that I don't have an sdcard inserted. Would this make any difference as to why I'm getting the error message in CWR?
Click to expand...
Click to collapse
You need an sd card, that is probably why you got the error.

endine said:
You need an sd card, that is probably why you got the error.
Click to expand...
Click to collapse
Appreciate your help. I'll be getting my sdcard soon, I hope it works.
I also did download an auto mount program from market. What is it exactly suppose to do? It had one option at the top to tick which was to auto mount, and that was it. I suppose it runs in the background doing it's thing?

OK. I got the sdcard working, I flashed to 1.3.2.
I can transfer stuff onto my sdcard2 within my xoom and it will show when i insert the card into my PC. It won't work the other way around though. I can't get the files to show up in root explorer, or with any media player even if its a video file. Why is that? Is there a work around?
All help appreciated.

flombs said:
OK. I got the sdcard working, I flashed to 1.3.2.
I can transfer stuff onto my sdcard2 within my xoom and it will show when i insert the card into my PC. It won't work the other way around though. I can't get the files to show up in root explorer, or with any media player even if its a video file. Why is that? Is there a work around?
All help appreciated.
Click to expand...
Click to collapse
You have to reboot the xoom for them to show up.
Sent from my Xoom

hahaaaa....
That was the simplest advice I could've ever received in my life!
Thanks again.

[Q] "E: Can't open /sdcard/tiamat-xoom-rom-2.2.1.moray.zip (bad)"!!

MZ601 Xoom on 3.1HC wifi + 3G rooted using Universal Xoom Root. Now wish to be able to use USB Host mode. Have followed the instructions in [ROM] Team Tiamat Xoom Rom 2.2.1 - Moray [18/9/11] including performing a factory reset (Wipe data/factory reset) from within recovery, and then selected "Install zip from sdcard" and selected the Tiamat zip file. The system reports that it is opening the file but then immediately aborts with the above message.
Assuming that the download was not successful I then downloaded again, went through the whole procedure again but came up with the same error. Hmmm this is a bit of a mystery.
So, is 2.2.0 a prerequisite of 2.2.1 and should I have tried to flash that first? Or could there be something else that this old fart is missing? I guess it must be the latter judging by all the success stories on here. Can somebody please help?
Irobbie.

irobbie said:
MZ601 Xoom on 3.1HC wifi + 3G rooted using Universal Xoom Root. Now wish to be able to use USB Host mode. Have followed the instructions in [ROM] Team Tiamat Xoom Rom 2.2.1 - Moray [18/9/11] including performing a factory reset (Wipe data/factory reset) from within recovery, and then selected "Install zip from sdcard" and selected the Tiamat zip file. The system reports that it is opening the file but then immediately aborts with the above message.
Assuming that the download was not successful I then downloaded again, went through the whole procedure again but came up with the same error. Hmmm this is a bit of a mystery.
So, is 2.2.0 a prerequisite of 2.2.1 and should I have tried to flash that first? Or could there be something else that this old fart is missing? I guess it must be the latter judging by all the success stories on here. Can somebody please help?
Irobbie.
Click to expand...
Click to collapse
So, just to clarify, you are rooted and attempting ti install the Moray Rom, and your Xoom is giving you an error that it can't access the sdcard to flash the Moray file.
My first question is, what version of CWM recovery are you using and is your Moray file on your external micro sdcard which is inserted in your Xoom?
It sounds like you are trying to flash from the Xoom's internal "sdcard" which doesn't work (unless you have the Rogue recovery installed).

Thanks for your reply.
Regarding the recovery mode version, in recovery mode my Xoom tells me "Clockwork Recovery V3.2.0.0 (solarnz-R4c-100611-1150).
Using "My Files", I have confirmed that the Zip file doesn't exist on the "Internal" storage, but does exist on the external SD card. This is where the Universal Xoom Root zip file sits and where it was installed from. The root zip file installed smoothly, and as far as I know I followed the exact same steps in trying to install the new rom. So I remain confused.
Once again thanks for your reply and any further help will be appreciated.
Irobbie

irobbie said:
Thanks for your reply.
Regarding the recovery mode version, in recovery mode my Xoom tells me "Clockwork Recovery V3.2.0.0 (solarnz-R4c-100611-1150).
Using "My Files", I have confirmed that the Zip file doesn't exist on the "Internal" storage, but does exist on the external SD card. This is where the Universal Xoom Root zip file sits and where it was installed from. The root zip file installed smoothly, and as far as I know I followed the exact same steps in trying to install the new rom. So I remain confused.
Once again thanks for your reply and any further help will be appreciated.
Irobbie
Click to expand...
Click to collapse
Ok, Sounds like you should be set regarding recovery. I'm pretty sure that you should be able to go right to Moray 2.2.1.
First, confirm that your sdcard is good and working properly by inserting it into a phone or a card reader. It could be as simple as a bad card. Also, you could redownload the file, but I think it's most likely your sdcard.

Thanks for getting back to me.
I replaced the SD card with another from my mp3 player and checked it out by loading up a song and playing it. No problems. So then I moved the zip file for the rom (which I had previously re-downloaded) over to the root of the sd card from my PC and proceeded through the steps again. Failed again. The message sequence reads:
--Installing: /sdcard/Tiamat-Xoom-rom-2.2.1-Moray.zip
Finding update package... (So its gone looking)
Opening update package... (And it is found?)
E:Can't open /sdcard/Tiamat-Xoom-Rom-2.2.1.Moray.zip
(bad)
Installation aborted
Hmmm. Just to check that the sd card is still viable, after reboot went back to "files", sdcard, music and selected a song and it played as normal. Also checked that the Tiamat rom zip file is on the card and yep, it is. So tomorrow morning I will download the zip file once again and retry. If you can think of anything else it will be much appreciated.
Irobbie.

If you can check to make sure the downloaded file is the right size that will be great. also make sure that you don't add another.zip file extension on the end, somehow. Some pcs are set up to hide file extensions and that's been a problem a few have encountered.

The mystery deepens! Well, for me at least.
Re: zip file extra extension, have show extensions switched on, and there is no extra extension.
So on to file size, it looks the same to me on each download so I went a bit further. I noticed the link to the file has a MD5sum check noted. So I downloaded an open source file "Sigma Informatics Checksum calculator", pointed it to the rom zip file and ran the check, and then cut and pasted the original number from the thread and got the calculator to do a check. Bingo - exactly the same!
So then copied the file from the Xoom back to the PC, ran the same checks and got different answer!
OK, I deleted the rom zip file from the Xoom, copied another over from the PC, then recopied it back to the PC to a different location, ran the check sum, got the correct answer, so now I knew I had a correct file on the Xoom.
Next, reran the installation of the Rom - failed again with the same results and messages as before.
Then copied the Rom zip file back to the PC to another location, ran the checksum and different answer popped out again. Well, could it be that the zip file is being corrupted during the install and that is why it fails? I've never heard of that sort of thing happening before but I suppose it is possible.
Your continued support is much appreciated.

It seems like I have heard of this happening, but why? What would cause that? Can you use a different method to copy the Rom file to the sd card? Using an adapter, and inserting the card directly into the sd slot of the pc? Download right onto the card?

Thanks for the reply and suggestions again.
To make absolutely sure I eliminated everything possible; I went out and bought a new micro sd card, and card reader with a micro sd card slot. Plugged it altogether into the pc and copied over a copy of the rom zip file.
Then did a checksum check on the file on the sd card and it was fine.
So, holding breath, puff, puff, puff, started the procedure all over again.
SUCCESS! It all went as smooth as silk! Thanks for your help and suggestions. But now I am left with a concern about where the problem really was - was it in the copying of the file onto the card through the Xoom, or was it, in fact, a bad card? I don't want to discard the card because it seems to be o.k. in every other respect so I think a little play around is in order. I think in all probability you are right in questioning the process I was using before, and recommending that the file be copied directly to the sd card.
But in the meantime I'm off to explore the new rom and in particular USB hosting.

Yes! I love success!
Enjoy.

[Q] Rooted, but can't install zip files...

Have CWM v3.1.0.1 installed and can boot just fine but when I install the new CWM, I get "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
This happens with any zip file I'm installing. I get "E:Can't open /sdcard/*.zip (bad)"
I thought maybe I had a bad download so I downloaded and re-downloaded the zip files. Nothing.
I've Rooted using One Click Universal root v4 and during the root process installed CWM 3.1.0.1. No problems. All worked fine.
Was thinking my sdcard might be the problem so I installed on my PC brk's Universal root toolkit v7.1 and tried to use NVflash on Revolver and Prime 2.0.3. Well it just sits there for an hour hung about 30% into it.
Will try brk's Universal root toolkit and attempt recovery install.
Any suggestions/ideas would be greatly appreciated.

Maybe try to format your micro sd card again using the pc.
sdformatter is a good program.

Well I fired up, brk's Universal root toolkit v7.1 and ran the restore recovery and then installed Prime v2.0.1 with success. Installed using NVflash option.
After going through reboots to ensure Prime installed (which looks really good), I decided to try to install the Prime v2.0.3 patch (zip file) using the updated CWM 3.2.0.1.
Well, that didn't work. Got the same error, "E:Can't open /sdcard/*.zip (bad)".
Can't figure this out. Never had this problem before.
Maybe the next course of action is the formatting of the sdcard.
Doesn't the tablet format the card? Or do you recommend using this, sdformatter?

I usually use the PC.
Keep in mind it only work with FAT32 on the micro sd
and you're using the micro sd on the tablet itself correct?

Yes.
Sent from my Transformer TF101 using xda premium

Have exactly same problem, it seem like problem somewhere in CWM 3.1.0.1
In details:
Had rooted 8.5.6.13 with Brk.root.toolkit.v7.1 (that one includes CWM 3.1.0.1),
Put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Loaded in CWM , try to update to 3.2.01 (selected install zip from SDcard) -> got "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Downloaded CWM-ready images from
http://forum.xda-developers.com/showthread.php?t=1334673
and
http://forum.xda-developers.com/showthread.php?t=1341533
Both installed OK (yes, with same CWM 3.1.0.1 !),
Another attempt to update CWM (now on 8.5.6.19)->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Checked root->root disappeared (do not know why), rooted 8.5.6.19 again with Brk.root.toolkit.v7.1,
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Got another 512MB MicroSD, formatted in FAT 32 (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Formatted it in FAT (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Looks like I am stuck on CWM 3.1.0.1 with no chances to update in future, any suggestions would be appreciated.
P.S. MD5 of cwm_recovery-3201_roach-tf101-r1.zip is correct. Transformer of WW version.

Lechaxda-developers said:
Have exactly same problem, it seem like problem somewhere in CWM 3.1.0.1
In details:
Had rooted 8.5.6.13 with Brk.root.toolkit.v7.1 (that one includes CWM 3.1.0.1),
Put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Loaded in CWM , try to update to 3.2.01 (selected install zip from SDcard) -> got "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Downloaded CWM-ready images from
http://forum.xda-developers.com/showthread.php?t=1334673
and
http://forum.xda-developers.com/showthread.php?t=1341533
Both installed OK (yes, with same CWM 3.1.0.1 !),
Another attempt to update CWM (now on 8.5.6.19)->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Checked root->root disappeared (do not know why), rooted 8.5.6.19 again with Brk.root.toolkit.v7.1,
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Got another 512MB MicroSD, formatted in FAT 32 (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Formatted it in FAT (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Looks like I am stuck on CWM 3.1.0.1 with no chances to update in future, any suggestions would be appreciated.
P.S. MD5 of cwm_recovery-3201_roach-tf101-r1.zip is correct. Transformer of WW version.
Click to expand...
Click to collapse
Hi - Here's some things to check:
1) A note from the original post(s) on cwm-3101/3202 in the dev forum:
Code:
Originally Posted by Warboy
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
It does skip internal media unless you put a file called eraseData into the clockworkmod folder on your MicroSD card.
So make sure you've got no file on the MicroSD called eraseData.
2) Have you check the md5sum? Here are the details:
Download
3.2.0.1 roach-tf101-r1
MD5: b28dca7b9dce48627e5e849586f633d1
If you don't know how to do that, then you could download an md5sum verify program for windows if you use it from somewhere, and check the zip file against the md5sum below it, or if you use linux, then just do "$ md5sum 3.2.0.1* and compare it to the md5sum above.
3) I'm not recalling the syntax of cwm errors, but it looks like "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is hopefully where "E" means error, and /sdcard really means /Removable/MicroSD/, which would at least stick you in the right area.
4) Make sure you can unzip this file using 'unzip'/7zip/windows unzip/' or whatever on your PC before you start all this. If you can't unzip it there, then you can't unzip it on the TF. You'll get an error if it won't unzip.
SO: Just make sure you have 1 & 2 & 4 right first and then just for the heck of it rename the long filename to something smaller like cwm3201.zip and put it on a) the microsd and b) /sdcard, and try it again using that name.
Good luck -

Many thanks for your help,
I have stepped again through points above:
1.I did not found any eraseData file neither on MicroSD nor on Internal memory(/,/data,/system) (checked this with RootExplorer), actually I do not completely understood where to search: clockworkmod folder does not exists on those locations.
2.As i wrote, I have checked MD 5, in any case redownloaded file, checked MD5 again: to be precise- MD5 for zip: MD5 (cwm_recovery-3201_roach-tf101-r1.zip) = f71f9b672396be5e494b3d355ed21c9a
MD5 for content (i.e extracted zip): MD5 (cwm_recovery-3201_roach-tf101-r1) = b28dca7b9dce48627e5e849586f633d1
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?

Lechaxda-developers said:
Many thanks for your help,
I have stepped again through points above:
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?
Click to expand...
Click to collapse
Are you choosing "apply update from sdcard" or "install zip from sdcard"?

Are you choosing "apply update from sdcard" or "install zip from sdcard"?
Click to expand...
Click to collapse
install zip from sdcard,
Should i rename cwm_recovery-3201_roach-tf101-r1.zip tj update.zip and try another option?

Lechaxda-developers said:
install zip from sdcard,
Should i rename cwm_recovery-3201_roach-tf101-r1.zip tj update.zip and try another option?
Click to expand...
Click to collapse
No "install zip from sdcard is correct" shouldn't have to rename the zip at all.
CWM only read from micro sdcard not internal sdcard that's why you can't see it there.
Have you tried Gnufabio RecoveryInstaller? It install the newer CWM IIRC.
http://forum.xda-developers.com/showthread.php?t=1346180

I think the idea above this is a good one for a first try at this point.
Also: I reread the original post and see that obviously cwm finds the file, attempts to or succeeds in opening it, and then shouts "bad". I see you tried unzipping from the PC, and all the rest.
I wonder if this could somehow be a permissions error and if somehow there are no meaningful permissions either on the sdcard mount (just run $mount in a terminal emulator or adb to see what they are). I'm guessing that well, it's a zip file, so no matter what else cwm must do, it has to unzip the thing and extract the data to someplace. I'd have to go stare at the github code to figure out where that place is, but the target "could" be mounted r/o. It seems like the target can't be the sdcard or you're never be able to write the zip there in the first place.
If there's a github URL in the solarnz/roach post I'll see what it extracts it to and get back to this.

Lechaxda-developers said:
Many thanks for your help,
I have stepped again through points above:
1.I did not found any eraseData file neither on MicroSD nor on Internal memory(/,/data,/system) (checked this with RootExplorer), actually I do not completely understood where to search: clockworkmod folder does not exists on those locations.
2.As i wrote, I have checked MD 5, in any case redownloaded file, checked MD5 again: to be precise- MD5 for zip: MD5 (cwm_recovery-3201_roach-tf101-r1.zip) = f71f9b672396be5e494b3d355ed21c9a
MD5 for content (i.e extracted zip): MD5 (cwm_recovery-3201_roach-tf101-r1) = b28dca7b9dce48627e5e849586f633d1
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?
Click to expand...
Click to collapse
You have to copy the .zip file to /removeable/micro sd card/ and not to /sd card. For now its not possible to flash something from the internal sd card.
If you allready did this you can try to "toggle signature verification" in Recovery i had to do this when i flashed the su on my sensation xe. you have to do this till it says disabled and then flash the .zip
Hope it helps
Sent from my Revolver powered AsusTransformer using Tapatalk

hachamacha said:
I think the idea above this is a good one for a first try at this point.
Also: I reread the original post and see that obviously cwm finds the file, attempts to or succeeds in opening it, and then shouts "bad". I see you tried unzipping from the PC, and all the rest.
I wonder if this could somehow be a permissions error and if somehow there are no meaningful permissions either on the sdcard mount (just run $mount in a terminal emulator or adb to see what they are). I'm guessing that well, it's a zip file, so no matter what else cwm must do, it has to unzip the thing and extract the data to someplace. I'd have to go stare at the github code to figure out where that place is, but the target "could" be mounted r/o. It seems like the target can't be the sdcard or you're never be able to write the zip there in the first place.
If there's a github URL in the solarnz/roach post I'll see what it extracts it to and get back to this.
Click to expand...
Click to collapse
OK: I grabbed both git's (solarnz and roach) and there is only one spot the error could be coming from originally which is in top-level install.c and is basically just a call to mcOpenZipArchive in Zip.c. If returns an error, then that's apparently the error you got (has E: up front, (bad) in rear, and your stuff in between).
mcOpenZipArchive looks at ~4 criteria to open, and one thing that seems kind of important is that I don't see any changes in this Zip.c file in either git repo so if it fails on solarnz, it "ought" to fail on roach.
What Zip.c checks are these things:
1) Is the file there and openable at all? (based on a few things first on /MicroSD (wheverever you pointed it), or on /sdcard if those other oddball things were setup but you said they weren't.
2) Can it map the memory for this file in shared mem?
3) Did the map return an endpoint(amount of mem) that would hold the entire file?
4) Can it parse the file into mapped mem?
I don't have time to go through more code but if any of those things cause some alarm to go off in your head, then good and there's hope of figuring it out, and if not, well, maybe we can get roach to look it over as if he hasn't got enough going on
The other possible obvious thing might just be that your cwm is corrupt and useless. I've had this happen to me, but have used nvflash to blow another img of it onto the tf. I don't know if you've got that capability or not. Like all errors, it could be a million things, and by the time I finish this paragraph, I hope you've solved it.

Thanks again for advices, solved in 1 minute with
Gnufabio RecoveryInstaller
http://forum.xda-developers.com/show....php?t=1346180
Bad point here I didn’t figured out what was the reason of the problem, I would agree with hachamacha:
The other possible obvious thing might just be that your cwm is corrupt and useless.
Click to expand...
Click to collapse
With only one exception: it was “partly” corrupted (see in my first post, with same CWM I have installed 2 zip- images without any problem), only with conjunction with cwm_recovery-3201_roach-tf101-r1.zip problem appears.
In any case: for guys who having problems "updating CWM with CWM" - just use Gnufabio RecoveryInstaller