[Q] Can't connect to PC with my A500 - Acer Iconia A500

Finally i got myself a acer iconia a500 yesterday.
Rooting, flashing a CWM-Recovery and flashing the latest Taboonay rom was no problem so far.
But somehow I can't manage to connect my Tablet to my PC. I have been searching and trying for hours - without any solution.
I installed the official Acer driver, tried different usb ports & different cables.
I am running Windows 7 32 bit.
The tablet is recognized, but windows is failing finding the right drivers for MTP-USB device. Even pointing to the installed acer drivers doesn't help.
The device is shown as "Acer Tablet" in "Devices & Printer" but with an exclamation mark, leading me to the mentioned driver
Actually I am running out of ideas now
any idea or help is appreciated

ditto
-bump-
Same issues here :S
Ever since Taboonay I haven't been able to get anything to work. not even the stock Rom. :S

Actually i solved this problem in the meantime, by connecting with another Computer. Same OS - worked right away.
Guess, I had some kind of driver issues...

Related

[Q] Problem...Recovery with no ROM to flash or USB recognition

Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!
Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program
Thanks for the info!
I am away until tomorrow evening. I will try it then.
Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!
it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver
Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.

HELP! ADB -USB Not Recognized

Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
vipergrm said:
Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
jgaf said:
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
Click to expand...
Click to collapse
Thanks but that still didn't work for me. What exact driver did you use? Thanks!
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
jgaf said:
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
Click to expand...
Click to collapse
Thanks again. I will give this another go later and see what happens...
Any luck?
jgaf said:
Any luck?
Click to expand...
Click to collapse
I haven't had the opportunity to try it again just yet. I plan to do this tomorrow night on my nightshift in work. I'll let you know then. Thanks for asking
Tried tonight again and still no luck. I know the driver installed on this machine definitely works because its the same one that worked last week when I tried it. Oddly, the ADB driver picks up ok when I'm in the OS with debugging on but I don't think i would be able to flash whilst logged on to the OS. This is concerning because the CM10 ROM 4.2.2 which I have installed a the moment is firing up random reboots. I know it's still in experimental stage and I'm not complaining but it would be nice to change my ROM when needed. Below is a couple of screenshots of the problem I am having.
I had a similar problem my adb worked flawlessly when the OS was running, but it wouldn't get recognized when in recovery (fastboot worked too). So, what I wrote earlier solve my problem. Sucks it didn't work for you. Anyways do you have a recovery installed? If you do why can't you use that one? Also, I'm pretty sure you can install recovery when the OS is running, even from android terminal emulator in the pad.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Thanks again. I did do a backup thankfully and currently it is restoring. I will try to see after restoring the backup if it works. Another method I have found to repair the bootloader is the NVFLASH method, although this does scare me a little! I would be very interested in trying those drivers you have as mine are older but so far I have been unable to find anything newer, despite extensive searching. :crying:
Thanks for your help thus far! :good:
Looks like I'm finally getting somewhere. I decided that I would try connecting directly to the TF300 instead of through the keyboard dock and oddly this worked. The driver is now loading correctly and I am able to flash again! Now to choose a JB ROM... :good:

[Q] Windows doesn't recognize my A500 through usb

Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks
SolomonAiel said:
Ok so I think I've searched well enough to conclude no one has my particular problem. When I plug in my A500 into my computer that has windows 7 windows recognizes that something was plugged in but not what it is. It says USB device not recognized, unknown device, and so on. I've tried installing the drivers from the acer website, I've tried installing the drivers from the link in the ics rooting thread, I've tried using the google android drivers and none have worked. I've even tried reinstalling windows but that had nothing to do with this it was a different thing that made me do it. Nothing has worked and I've become a bit frustrated with the tablet. Any suggestions on what to do?
Thanks
Click to expand...
Click to collapse
What state are you connecting it in (recovery, fastboot, normal boot)?
Moborobo test program
Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.
SolomonAiel said:
Sorry forgot to say, it's stock rom not rooted and is being connected in normal boot.
Click to expand...
Click to collapse
tick the usb debugging
and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.
SolomonAiel said:
and that is on. Forgot to mention that as well. I forget about details quite often when i'm explaining something.
Click to expand...
Click to collapse
Moborobo, download the program and try it. Ami has worked with me many android devices
---------- Post added at 06:30 PM ---------- Previous post was at 06:26 PM ----------
Moborobo, download the program and try it. to me has run many android devices. sorry for my English
Your computer isn't detecting it at all, or is there an error while trying to identify it? Make sure you have the proper drivers for your device on your computer.
It's an error identifying it. I do have the correct drivers the a500 drivers from either the rooting guide or the Acer website neither has worked.
Moborobo does not work with the a500. I tried it and it still says to connect my device. which it is but it's just unrecognized.
If you have installed the driver correctly, AND you had administrator rights when you installed, should be no reason why you can't get the PC to recognize the device.
First, I would advise using a good USB cable. It's been known in the past, that some folks try to use a printer cable, and sometimes it doesn't work. If changing cables doesn't work, then do the following
1. In Device Manager, try loading the drivers manually. You should be able to have it search the windows system for the drivers. If it doesn't find it, then windows is being stupid. Try installing it manually (ignore the warning it may not be compatible,.....)
2. If that doesn't work, then you can use the Google USB drivers
http://www.redmondpie.com/android-u...r-samsung-htc-asus-sony-lg-and-other-devices/
Generally, we install the Android SDK first;
http://developer.android.com/sdk/index.html
And again, have Device manager look to that directory and manually select.
Either way, this should get you up and running.
And one more thing, turn on USB Debugging in your tablet's system properties.
MD
I've tried that. Didn't seem to work as windows would still not recognize the a500. And the usb debugging has been on since the beginning.
Okay i've gotten windows to the point of being able to install the drivers from the device manager but there is no clear option to choose. Here are the choices:
acer android communications port
acer android modem
acer hs-usb android diag
acer hs-usb diagnostics
acer composite adb interface
acer fastboot interface
acer picasso usb boot-recovery driver (google driver)
android bootloader interface (google driver)
So any suggestions cause I've tried installing the adb interface, fastboot interface and the android bootloader interface and haven't gotten any good results.
Thanks
Did you try a second PC? Sometimes a machine can get wonky if you've been using for years. Using a second machine or reinstalling Windows freshly would greatly increase the chances of detection.
Yep tried about 3 machines.
SolomonAiel said:
Yep tried about 3 machines.
Click to expand...
Click to collapse
I'm having the same issue with a bricked A500 I bought on ebay
Windows just recognizes it as an MTP USB device and fails to install the drivers
I have another A500 that comes up fine as an A500 on the same PC.
Try disabling the USB debugging in developer options I have the same issue with my Win 7 x64 system

KitKat on Nexus 7 Failes

My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
In my win8 64bit the nexus 7(2012) does show up as a portable device, but MTP works and there's no issue with sending or pulling files. currently it's running stock kitkat 4.4 (KRT16S).
like you I suspect it's a driver issue with windows. If you could locate the device on device manager (try View\Devices by connection and look under PCI Express Root Complex and comb for USB Host Controller\USB Root Hub\Generic USB Hub), delete the entry for Nexus7 and scan for hardware changes again. This forces the system to look for correct driver(s) for your nexus.
Some guides on updating drivers are in fact concerned with the ADB interface, which is needed for USB debugging. In your case, if it's just accessing the internal storage of your Nexus you want to solve, those info may not be relevant.
krrasmuss said:
My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
Click to expand...
Click to collapse
Installing fresh SDK won't hurt.
holynoob said:
Installing fresh SDK won't hurt.
Click to expand...
Click to collapse
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Update
peterk-1 said:
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Click to expand...
Click to collapse
Basically I would like to have ¤.¤ installed on my Tablet. Right now I have 4.2.2 SmoothROM installed, and whilst this works for me, I'd like to get the update.
In the past, I used the Toolkit to root and install stuffies... Until the last update to SmoothROM wheres I used GooManager thingy...
When I started this I got the Tablets to connect using PTP whilest in Android, but not in Fastboot mode. So I downloaded the 4.4.kitkat Offisial ROM and tried to install that in recovery, after a full wipe, BUT that ended in me having to install SmoothROM again. And now the Tablet wont connect at all... I have deleted all drives, and reinstalled them... I've tried 3 diffrent Wondows USB driver, but no luck there... I've tried like 5 diffrent USB data cables, in all 4 of my USB ports, on 2 diffrent machines, both win 7 and win 8... AND still no luck... now all the machine says that it cannot identfy the device...
Tomorrow, I will end up installing linux, and try there... At the moment I loathe all things called windows drivers...!!!!
EDIT:
Great news... I found a cable, I havent used in a long time. THis is the original cable that came with the Nexus, and I havent used it in a long time because it had some bad connections. Felt like the plug was loose, but now it made the whole thing work without any problems at all...
So I found the cable, used USBDeView to delete all drivers assossiated with the nexus. plugged it in while in fastboot, and BANG installed. rebooted it, and BANG installed.

[Q] LG G2 802 stuck in TWRP - drives not installing

Hi,
I wiped my current rom in TWRP and something went wrong with the rom I was trying to install so I have a phone without an OS now (LG G2 802). Now I am stuck in TWRP. The backup for the phone is on my laptop but I cant seem to get my laptop to recognise the phone any more.
When I connect my phone to the laptop via USB it shows up in the device manager but with an exclamation mark. I've tried pointing to the LG folder under program files for the drives but for some reason they dont work and the device is still showing up with the yellow exclamation mark in the device manager. These drivers were working before this happened (I've connected the same phone to my laptop quite a few time before, including using ADB to root it earlier) so I don't know why this is happening.
Any help would be appreciated, I am completely lost right now.
Thanks...
You can use an otg cable with a thumb drive too.. The driver for this is under Google, see if you can find it. There was a guide somewhere but I've lost the location :/
*edit* FOUND IT
http://forum.xda-developers.com/showthread.php?t=2557248
Sent from my LG-D802 using xda app-developers app
Got around it...phew!!
As it turned out I had a few issue, for anyone else in the same boat here is what I did to get my phone back up.
First, I cant thank Koush enough for his amazing work, after installing his universal adb drivers the laptop started recognizing the phone immediately (as to why it didnt with the official drivers, I have no idea).
The drives can be found here: http://koush.com/post/universal-adb-driver
Once the phone was recognized by the laptop I knew I had some hope, I tried to adb sideload a few roms but kept getting error messages. I looked up TWRP for the latest version 2.7 and updated to that from 2.6.3.2 and the Roms started working immediately. Now I am happily running the PAC KK rom (which by the way looks fantastic).
Hope this helps anyone else who is in the same boat.
Regards,
Tariq

Categories

Resources