Database Users

[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

[Q] nexus q not being recognized by windows/adb

hello,
Im trying to dust of my nexus q and boot cm 10 on it, when i try to plug it into windows i get no audible tone and it's also not recognized by adb.
i have downloaded the google usb drivers and read of a modification for them on another website here: http://nexusq.wikidot.com/prerequisites
i am currently downloading the android 4.0 in the sdk.
but can anyone give me a hand. i am currently using a mini usb to usb the chord works with other devices.

sonikot said:
hello,
im trying to dust of my nexus q and boot cm 10 on it, when i try to plug it into windows i get no audible tone and it's also not recognized by adb.
I have downloaded the google usb drivers and read of a modification for them on another website here: http://nexusq.wikidot.com/prerequisites
i am currently downloading the android 4.0 in the sdk.
But can anyone give me a hand. I am currently using a mini usb to usb the chord works with other devices.
Click to expand...
Click to collapse
try the universal naked drivers

sonikot said:
hello,
Im trying to dust of my nexus q and boot cm 10 on it, when i try to plug it into windows i get no audible tone and it's also not recognized by adb.
i have downloaded the google usb drivers and read of a modification for them on another website here: http://nexusq.wikidot.com/prerequisites
i am currently downloading the android 4.0 in the sdk.
but can anyone give me a hand. i am currently using a mini usb to usb the chord works with other devices.
Click to expand...
Click to collapse
If your trying stock, it has to be enabled through the app, which can't talk to the q anymore since the servers were taken down.
I haven't tried yet, but theres a boot.img that supposedly makes it insecure and enables adb.
You might be able to use OMAP flash to get it on there
I'd give you a step by step, but i haven't had the time to try it myself yet.

animal24 said:
If your trying stock, it has to be enabled through the app, which can't talk to the q anymore since the servers were taken down.
I haven't tried yet, but theres a boot.img that supposedly makes it insecure and enables adb.
You might be able to use OMAP flash to get it on there
I'd give you a step by step, but i haven't had the time to try it myself yet.
Click to expand...
Click to collapse
ok, i got it, i basically used fastboot commands first then adb and usb started working some where along the way

yup just push the insecure boot img and adb worked

Bricked Device

I had a rooted 4.3 stock image on my N10. Got the notification about the downloaded update for 4.4
It did the update through TWRP (which was weird to me) and finished, restarts and gets stuck on the boot loading screen.
So I went into recovery, and cleared cache, no luck, then complete factory reset, no luck, then I added "System" to that wipe, not knowing what it was an now there is no OS installed.
I installed the Nexus 10 Toolkit (Unified Toolkit) and install the USB drivers, but my computer is not seeing my device..
Help?

As long as you can get to the bootloader, you can reflash a stock image. Easiest way is with wugfresh nexus root toolkit. It will walk you through the driver installation and the various image downloads.

That did not work.
The computer is not seeing my device. Drivers are installed, not seeing it, it's in the proper Boot mode.

I followed the mode that said I didn't need debugging enabled, still nothing.

bmancell said:
I followed the mode that said I didn't need debugging enabled, still nothing.
Click to expand...
Click to collapse
I would recommend uninstalling the USB drivers you installed with the toolkit and manually installing the Google USB drivers attached to this post. After you have installed the USB drivers I would recommend manually booting into your devices bootloader by simultaneously holding down the power button + volume up button + volume down button. Once you are in bootloader mode I would recommend download this Android 4.4 KitKat Factory Image and flashing it to your device in order to restore things to a working order. Let me know if you still have questions I'll be happy to help you out.

And want explain to me how I copy that file to my device when the computer can't see it?

bmancell said:
And want explain to me how I copy that file to my device when the computer can't see it?
Click to expand...
Click to collapse
Check out my previous post and see if those steps will allow your computer to see your device, and let me know how that goes for you.

Ok, I unziped the folder, got the tablet in bootloader mode, which I already said I tried, nothing.

Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notifcation, nothing in device manager, nothing. Just the sound .

bmancell said:
Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notification, nothing in device manager, nothing. Just the sound .
Click to expand...
Click to collapse
I just want to re-state everything to make sure anyone can understand.
This was a Nexus 10 rooted 4.3 Stock. I got the 4.4 update, it finished without issues, but got the boot loop issue.
I cleared cache, factory reset and eventually the system without luck, which left the tablet without an OS (bootloader or recovery only options).
My systems can not detect the tablet, I have installed, re-installed, tried two different toolkits and no luck.
I can't believe it's an actual brick that can't be fixed? Anyone?

Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.

sojthumper said:
Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.
Click to expand...
Click to collapse
Did you read? I have installed/reinstalled the drivers 3 times.

bmancell said:
Did you read? I have installed/reinstalled the drivers 3 times.
Click to expand...
Click to collapse
I also tried a third computer, and another cable. It will charge from a computer, nothing else.

I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.

You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app

gc84245 said:
You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Don't know what a USB-OTG cable is, and not sure how you'd connect a flash drive, but...
I tried one more computer, this time it was a computer with Windows 7 one it. Detected the tablet right away.
So, why the heck does Windows 8 (8.1 to be exact) not allow my tablet to be seen (im sure with the OS on, and booted in, it will)./

tjupille said:
I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.
Click to expand...
Click to collapse
This must be why my Windows 8 machines don't work, but I dont remember seeing other driver options, only the one, will keep in mind in the future.

Sounds like the problem is solved, but I highly recommend getting a USB-OTG cable anyways. Go to Amazon and search for "USB-OTG". You can connect flash drives and external hard drives to your tablet. I got mine for $2.
Sent from my Nexus 7 using xda app-developers app

[Q] Bricked Updating to CM11

Hey guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?

I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?

Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..

Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.

Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?

mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.

I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app

mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!

Nexus 4 bricked, no OS, no recovery.

Hello
I tried a Nougat rom for the Nexus 4 which was available as a full update package (including system bootloader rom etc) and installed it with the update command from adb instead of from custom rom.
now my phone is bricked and I cant seem to get it fixed.
It either gets stuck in a bootloop, or i can force switch it to bootloader mode. From there I can go to recovery but the stock recovery is useless.
Problem is when i connect this to my windows 10 pc, it shows no sign of being detected. I installed drivers over and over including the universal ADB and fastboot drivers available here on XDA. it doesnt show up under adb devices command and even the Nexus 4 rootkit doesnt detect it as a phone.
I wanna make this phone working again. I'm guessing the way is to go back to stock image and then re-root and re-flash custom recovery and ROM. but even for this, it should be detected by the PC and adb command and rootkit right? Is there something I'm overlooking here?
This is the ROM I tried
https://forum.xda-developers.com/nexus-4/development/fake-nexus-rom-nexus-4-t3230268
The way to install it is also mentioned there and that is exactly what I did.

Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin

nitin.chobhe said:
Did you try this adb installer: https://forum.xda-developers.com/showthread.php?t=2588979
In that thread, I read the people are able to use adb on Windows 10. If that doesn't work, find a Windows 7 PC or boot to ubuntu using bootable pendrive and flash the factory images using fastboot.
Nitin
Click to expand...
Click to collapse
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...

BluTheCool said:
So are you saying this is definitely a problem of Windows 10? I hadnt even considered that...
Click to expand...
Click to collapse
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use adb on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin

nitin.chobhe said:
I read many users complaining about that. You can try that installer; as I mentioned - users have reported that they were able to use abd on Windows 10 after installing adb using that installer. If that doesn't work try the second suggestion (Ubuntu/ Linux)
Nitin
Click to expand...
Click to collapse
i tried the installer but it made no difference. i tried it my win 7 partition as well but it didnt show up in the device manager.. i think usb debugging must have been disabled with my new rom flash. but even then i dont get why it wont show up as anything in devman...
any command i try ends with waiting for device and since i cant find the device in devman I cant even update the driver manually. I guess I could give linux a shot

Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !

BluTheCool said:
Hey I finally figured out the problem. Its unbelievable. The usb port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now its being detected as fastboot. The drivers you provided work like a charm now. Thanks for all the help !
Click to expand...
Click to collapse
Glad that it helped, hope you get it revived soon :fingers-crossed:
Nitin

BluTheCool said:
Hey I finally figured out the problem. It's unbelievable. The USB port of the device was slightly bent in such a way that every cable I tried never really connected with the phone. I twisted it up a little and now it's being detected as fast boot. The drivers you provided work like a charm now. Thanks for all the help!
Click to expand...
Click to collapse
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.

sandy7874 said:
It seems I have the same prob, as my N4 too doesn't get detected. But my ph can charge with USB when I connect to PC.
How you twisted USB port? I mean it has very less room to insert any tool.
Click to expand...
Click to collapse
Tell me one thing - can you boot to fastboot mode?
Nitin

nitin.chobhe said:
Tell me one thing - can you boot to fastboot mode?
Nitin
Click to expand...
Click to collapse
Yes I m able to boot to Fastboot mode.

sandy7874 said:
Yes I m able to boot to Fastboot mode.
Click to expand...
Click to collapse
Ping me on hangouts. My email ID is in my signature.
Nitin