Database Info

[Q] Transformer NOT connecting to PC or Mac

My TF used to be able to connect to my PC and my Mac so I could do file copies and transfers. A few days ago I was running low on space and deleted some old music and movies and stuff that was in the ASUS folder. Now I can connect to any PC or mac. I thought maybe I deleted something so I decided to update the rom with the official file from asus but I copied the file to the root of sdcard and the root of external sdcard and booted into recovery but get an exclamation mark on the andoid guy.
1. Why wont this damn thing connect to my computers NOW when it did before? Did I delete something on the TF that would allow this? I downloaded all the usb drivers and sync SW from asus for the PC and Mac but no go.
2. How the hell to I restore the rom from the update file?
I am not rooted and run completely on stock.

Really? No one knows if there are files on the TF that controls computer connecting?

How are tou trying to connect to your pc? Regularly, as if you were going to sync? If your tf is not booting, you can't connect in this mode.
Sent from my mopho

AustinMartin said:
How are tou trying to connect to your pc? Regularly, as if you were going to sync? If your tf is not booting, you can't connect in this mode.
Sent from my mopho
Click to expand...
Click to collapse
I would normally just connect the tablet to my computers via the usb cable. On my mac I would run the android file utility and it would mount. On the PC I would run the asus synch sw. But now none of these work. I connect to the pc and if the tf is in sleep mode it would wake but I get no prompt on the tab to run pc synch and if i run the sw on the pc it says no device detected. on the mac I run the android file utility and it says no device connected. The cable does not look busted and it still charges the tab. I dont know what was in the asus folder on the tablet when I deleted it but I am thinking there must have been something there that would run.
I am trying to update the tf with the firmware file I d/led from asus's website but I dont know where to put the file. I put it in the root of sdcard and in the root of external sdcard and booted into recovery but just get the android guy with excalamtion.
If I let it boot up normally it works fine, just wont mount.

I don't think you'll be able to update if you went in and randomly deleted a directory. Especially if it was labelled ASUS.
I think that the update procedure does a crc check of all the files it's going to update, and if they don't match what it is expecting, it fails.
You might have deleted something needed for asus syncing.
In order to manually update, you need to put the update on a microsd, anyways, so you can just copy the files from a pc that has a microsd/sd slot.
---------- Post added at 03:43 PM ---------- Previous post was at 03:23 PM ----------
You also need to be very clear in your questions what you're referring to
SDCARD - is the internal memory of the transformer. You definately shouldn't delete an /ASUS folder from there.
microSD - is the microSD card you can put into the tablet. This is where you need to put an update file to manually update your transformer.
external SD card - is the full size sdcard in the keyboard. This can't be used for recovery, as the recovery software doesn't see this card.

AustinMartin said:
I don't think you'll be able to update if you went in and randomly deleted a directory. Especially if it was labelled ASUS.
I think that the update procedure does a crc check of all the files it's going to update, and if they don't match what it is expecting, it fails.
You might have deleted something needed for asus syncing.
In order to manually update, you need to put the update on a microsd, anyways, so you can just copy the files from a pc that has a microsd/sd slot.
---------- Post added at 03:43 PM ---------- Previous post was at 03:23 PM ----------
You also need to be very clear in your questions what you're referring to
SDCARD - is the internal memory of the transformer. You definately shouldn't delete an /ASUS folder from there.
microSD - is the microSD card you can put into the tablet. This is where you need to put an update file to manually update your transformer.
external SD card - is the full size sdcard in the keyboard. This can't be used for recovery, as the recovery software doesn't see this card.
Click to expand...
Click to collapse
I put the zip file in the root of external sd and still get the exclamation when I attempt to update. At this point I may restore. Quick question though, does performing a restore from setting bring back the tf to original state?

Actually, I have exactly the same problem. I didn't do anything e.g. I certainly did NOT delete any files of folders labeled asus on my device. And it just stopped working for me. My cable is totally ok so it does charge my Transofmer. Trying to wipe it now to see if it does any help.

Wipe did nothing at all. Still the same. Actually, when I boot into Windows and try to connect my pad to it, it says that there is an unknown device detected, but when I try to install asus drivers, nothing happens, it just doesn't work.

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

Transformer refuses to update. [SOLVED]

This is annoying as I updated the other one in the shop OTA and then after buying one it says no update available for mine. So I dowload the WW SKU from Asus and follow the SOP instructions. Unzip ro root of SD card (another .zip file) and insert. Result..... nothing no update notified. What am I doing wrong?
Build HRI66.WW_epad-8.2.3.9-20110423
Android 3.0.1
Kernal [email protected] #1

Rumors tell that Asus put the update to a halt after many customers complained about a lot off issues in the ICS release (like random reboots etcetera).

Are you trying to updater straight to ICS? Try updating to 8.6.5.21 first

baseballfanz said:
Are you trying to updater straight to ICS? Try updating to 8.6.5.21 first
Click to expand...
Click to collapse
Yes I didn't realise there was another update between them. I will try that then.
OK Dloaded 8.6.5.21 and unzipped. Placed WW_epad-user-8.6.5.21.zip on root of SD card then plugged into Transformer. Result. Nothing. What am I doing wrong here?

I have now tried putting the .zip on the external SDMC and rebooting, rebooting with Vol- and then pressing up. And also tried the same with the .zip on the internal SD of the Transformer. None of which resulted in the update being applied (neither the WW_epad-user-9.2.1.11.zip nor the WW_epad-user-8.6.5.21.zip).
Looks like I have bought one that cannot be updated in the manufacturers recommended way.

Try it this way,
make a copy of the ROM file you download and rename it to EP101_SDUPDATE.zip
put it on the root of external micro sd card
Boot into recovery and see if it will take.

Followed the instruction precisely and still no update performed :-(

Progress.
OK here is what I have done.
Placed full download without extracting it
Placed Download as extracted IE: The Folder = Asus/Update/WW_epad-user-8.6.5.21.zip
Placed Download extracted as: The folder Update/WW_epad-user-8.6.5.21.zip
onto SD card
One of these seems to have been recognised where WW_epad-user-8.6.5.21.zip was not.
It is just re-booting then I will try for ICS.
Looks like a total success. Just extracted ICS to SD nd plugged it in, Bob's your Aunties husband. It is updating as I type.
So in conclusion the .21 WW...zip seems to need to be in either the Asus/update folder or the Update folder on the root of the external SD card. Not sure which.

Yippppeeeeeee the update worked!!!!
Thanks for this I am so happy I found this thread as I could not do OTA as that has stopped at the moment and when I tried the firmware update via Micro SD card it just would not work!
Then I read your post and tried the different ways of putting the update on the microSD card
The one that worked for me was to put the update on the microSD card in the following folders Asus/Update/
My firmware was HRI66.WW_epad-8.2.3.9-20110423 (Android 3.0.1)
It is now on firmware IML74K.WW_epad-9.2.1.11-20120221 (Android 4.0.3)
Excellent!!!!! Why don't Asus advise you of this folder structure!!!
So I went from (Android 3.0.1) to (Android 4.0.3)

[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

[Completed] Help Convert TNTpipo.img into and ext sd installable file/zip

Hello, i need a bit of help, ive got my original .img file from TNT.
i had windows when i installed it first time, i have Linux mint 17 now .
i tried with neighbors win 7 machine but i can tget the tablet recoged by any means, i think the usb port is buggered up
nothing works.
any way i can install from external sd card, is there any way to mod the img to install from sd card similar to the Decontaminatv3.1.zip
iv installed tnt software and can mount the system folder have a copy of it converted to ext4(was a real pain)
decontam just gets renamed to install.zip and goes right in, just wish there was a linux based converter that didnt require an enlarged brain to operate
put img file in folder
start app
press button to convert .img to install.zip
copy install.zip into sd card
done and happy!!
any body have any ideas?

IMG is a completely different Packing of Source files. Those typically can not be converted into Zip files as their signature is integrated.
Please post Device details so we can help further.