Database Info

[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.

How to update ics?

Hi,
I tried to update to ics but when i put the update on the micorsd and then onto the tf101, it doesnt recognize the update files.
Im new to android devices so I really dont know much about it so I would appreciate help from u guyz =p
Hope to get zome help!

I had the same issue.
Try this:
On the root of your microSD card make a folder caled "ASUS"
Then inside the ASUS Folder, make another folder called "Update"
Then extract the file (firmware update) you downloaded from asus's website into the update folder
so it should be SDcard: ASUS/Update/US_epad-user-9.2.1.11.zip
Note the "US_" portion will be different based on the SKU version of the update you downloaded.
Normally when you download an update from their site, when you extract it, it makes those files for you, however they didn't package the update correctly.
That should make it recognize the update. If it doesn't, try rebooting it with the sd card still plugged into the transformer.

If that does not work try renaming the extracted zip to EP101_UPDATE.zip and putting it on the root of your microsd. When moving the file to your microsd make sure it is not in the tablet, ie use a card reader then insert the card and the update should show up.

[Q] Is there anything I can do???

I've been having problems with ICS and USB mass storage support, or lack of. Is there anything I can place on my micro SD. then copy it to the internal SD and boot from there?
Just grabbing at straws here!
Thansk
TF101 B50 by the way.

honkinn said:
I've been having problems with ICS and USB mass storage support, or lack of. Is there anything I can place on my micro SD. then copy it to the internal SD and boot from there?
Just grabbing at straws here!
Thansk
TF101 B50 by the way.
Click to expand...
Click to collapse
If you're still able to boot into the OS and is able to R/W files than yes, put the files on the micro sd, and using a file manager transfer it to internal sd.

Thanks for the help, but as a neebie, I need a suggestion on WHAT file to place on the internal SD that will I can boot from.
I still get the robot with the red triangle when I try to boot into recovery. I'm assuming that is because there wasn't a bootable file on the internal SD.
Does that make sense?

honkinn said:
Thanks for the help, but as a neebie, I need a suggestion on WHAT file to place on the internal SD that will I can boot from.
I still get the robot with the red triangle when I try to boot into recovery. I'm assuming that is because there wasn't a bootable file on the internal SD.
Does that make sense?
Click to expand...
Click to collapse
Oh I see you're on stock recovery, is the ROM stock also?
Only thing is download the latest firmware from Asus, extract the zip from within, renamed it EP101_SDUPDATE.zip and put it on the micro sd card. Boot into stock recovery and see if it will flash, maybe that will help get USB working again.

Thanks for the suggestion. I did what you told me and still nothing. When I try to boot into recovery, I still get the dead robot with the red triangle, then it boots stock.
IS there a particular folder on the SD or the Micro Sd I need to put the EP101_SDUPDATE.zip file into?
Is there a specific folder on the Intenal SD that the system boots from, that I could replace the update zip with a before ICS version?
Are these dumb questions?
Thanks in advance for taking the time to help me.

Forgot to mentioned, did you extract the zip from within the file you download?

I did extract the zip and placed it on the micro AND the internal SD in the Android folder.
IS there something else I should be doing?
This is driving me nuts.

Try it in the root of the sd card should automatically detect it there

Going on 2 weeks now
Is anyone else stuck in the situation I am? I cannot re-gain Mass Storage, SD support. When I try to boot into recovery, I get the Robot with the red triangle. The only way I can see my internal SD is through the stock file manager that is on the tablet. I don't know if I can move an appropriate file into a certain folder to get this thing to boot up to where I can reflash a ROM.
What is with this POS? I no longer have CWM and root after the OTA update. I e-mailes ASUS and they gave me the " pull the micro card, then do a wipe and re boot" Which did nothing but waste time. as you can probably tell, I am getting tired of dead ends on this Tf101 B50. does anyone have any idea what could have went wrong with the OTA update? Why did I loose the SD? and What can I do to fix/revert back to an earlier state.
self admitted noobie here...Feel free to kick the **** out of me!
Thanks for your help.

With a B50, see if you can get NVFlash working.
Download the NVFLash package
http://forum.xda-developers.com/showpost.php?p=23222380&postcount=414
Get an NVFLash compatible ROM here
http://forum.xda-developers.com/showthread.php?t=1524302&highlight=nvflash+rom

honkinn said:
Is anyone else stuck in the situation I am? I cannot re-gain Mass Storage, SD support. When I try to boot into recovery, I get the Robot with the red triangle. The only way I can see my internal SD is through the stock file manager that is on the tablet. I don't know if I can move an appropriate file into a certain folder to get this thing to boot up to where I can reflash a ROM.
What is with this POS? I no longer have CWM and root after the OTA update. I e-mailes ASUS and they gave me the " pull the micro card, then do a wipe and re boot" Which did nothing but waste time. as you can probably tell, I am getting tired of dead ends on this Tf101 B50. does anyone have any idea what could have went wrong with the OTA update? Why did I loose the SD? and What can I do to fix/revert back to an earlier state.
self admitted noobie here...Feel free to kick the **** out of me!
Thanks for your help.
Click to expand...
Click to collapse
Sounds like your OTA update was fudged so you need to reflash the ROM. I thought people with root and CWM can't do OTA updates?
Does adb or apx mode work? If apx mode works, then you can NVFlash so it shouldn't be a problem.
If ADB works, you can gain root with vipermod so you can install CWM.

I used to have root access. But, My last flash stuck in boot. Had to Nv flash it back to stock. Then the OTA hit, I had no more root or NVflash. So that is where I am. I hope there is something I can do to fix this.
Thanks for the help

OK lets try this method.
The firmware you download, don't rename it.
On the root of your sd card made a folder name ASUS
inside that make a folder name Update
extract the zip file from inside the download firmware and put it in the Update folder.
Just cold boot the TF and see if you get a notification of update avaiable on the status bar.
Outside of that not sure anything can be done except RMA

From custom ROM to offical JB

I have one of the custom ICS roms installed on my TF300T and want to install the offical JB release.
I downloaded the WW version from here: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
What then? I read somewhere you put it on an SD Card then reboot and it should detect it? Does it have to be an SD card? I put in onto the root of the internal memory but nothing happens if I reboot. Do I need to rename it, update.zip or something?
I doubt I should use the recovery to flash it, or is it as simple as that?

[Q] Flashing ROM problem TF201

I tried to flash my Transformer Prime TF201 to update the old NRG Energy ROM and all seemed to go OK flashing the bootloader but when I rebooted again into recovery TWRP to load the new ROM .zip file I couldn't find it even though I know it's on the external SD card. I tried to mount the SD Card but had no success, it just comes up with a stream of error messages. I also have a copy of the .zip file on my laptop. Is this recoverable or have I bricked it?