Database Info

[Q] Nexus S Root-Windows requests 'Android 1.0' hardware driver (and other weirdness)

Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.

Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928

webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!

haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!

bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders

The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.

jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.

I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid

I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!

Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!

Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S

Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App

Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"

When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work

matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!

thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App

matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!

I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box

[Q] ADB no devices

Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.

Update driver
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.

ShreddinPB said:
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Click to expand...
Click to collapse
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.

Emul8or said:
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
Click to expand...
Click to collapse
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?

it2steve said:
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Click to expand...
Click to collapse
There is a fix posted for the slowdown issue after resume from sleep, and you ADB to fix it

ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Here's what dev mgr looks like on XP...
Jim

ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.

davinci07 said:
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
Click to expand...
Click to collapse
Found it.. it was under "Universal Serial Bus Controllers" and called "USB storage device" i believe.
I tried updating the driver with the andoid one, but it errored out and wouldnt load it. After that however, 2 new devices popped up.. both the Nvidia harmony drive, and another nvidia tegra one. The harmony drivers failed to load.. so I pointed at the directory in the SDK and bam it works!!
Thanks guys!
But also btw.. before I got this working, I did use ADBWireless to run the adb shell and run that camand mentioned in the main thread that is supposed to stop the slow downs.. and I think its working.

enjoy, can you point me to the post that you needed this for? Also, now that ADB works you can start making your own apps. With either Eclipse and Android SDK (more advance route, but there is alot of good books that could help you alot) or with app invnetor that just got released to the public.

[ADB/FB/APX Driver] Universal Naked Driver 0.72

Universal Naked Driver 0.72
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!

Since ICS is on the way you will get you bootloader upgraded most likely. Then the unlock APK should follow if Asus holds up there end.
This will allows for comminucation with your tablet and phones (execpt moto for now)
Hope Asus hits you up soon with the unlock.
Cheers!

DDMS ok on my evo 3D with your driver, will test my transformer later

Nice work, was waiting for this
Although, could you tell me how did you get into fastboot mode on device? Did you use ICS, or any special bootloader, maybe a modified one?

keyra74 said:
DDMS ok on my evo 3D with your driver, will test my transformer later
Click to expand...
Click to collapse
Thanks for the feedback
fonix232 said:
Nice work, was waiting for this
Although, could you tell me how did you get into fastboot mode on device? Did you use ICS, or any special bootloader, maybe a modified one?
Click to expand...
Click to collapse
On my transformer prime I think the fastboot option only was available after the bootloader came unlocked but I could be wrong. I just do not remember seeing it before.
But after the unlock it I rebooted to the bootloader and then there was three options 1) BootToOS 2) Fastboot 3) Wipedata.
Once you select fastboot it says enabling fastboot protocols. Hope this helps but I do have a prime so it may be different.

1wayjonny said:
On my transformer prime I think the fastboot option only was available after the bootloader came unlocked but I could be wrong. I just do not remember seeing it before.
But after the unlock it I rebooted to the bootloader and then there was three options 1) BootToOS 2) Fastboot 3) Wipedata.
Once you select fastboot it says enabling fastboot protocols. Hope this helps but I do have a prime so it may be different.
Click to expand...
Click to collapse
Hmm, then please remove the Fastboot options from the original Transformer's log, as we have no access to it yet ;D Maybe with a modified u-boot, but that needs some time.

Any fix for Linux? DDMS doesn't find my TF anyomore since I upgraded to ICS

DDMS confirmed working on my ics transformer and windows here (with these drivers)
http://imgur.com/Wnmhd

gnufabio said:
Any fix for Linux? DDMS doesn't find my TF anyomore since I upgraded to ICS
Click to expand...
Click to collapse
Hey try adding these device ID's to your USB config, this should allow ADB, APX and also Fastboot if and when TF101 gets a unlocked bootloader.
USB\VID_0B05&PID_4E1F
USB\VID_0B05&PID_4E1F&MI_01
USB\VID_0B05&PID_4E3F
USB\VID_0B05&PID_4E3F&MI_02
USB\VID_0B05&PID_4DAF
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0955&PID_7820
keyra74 said:
DDMS confirmed working on my ics transformer and windows here (with these drivers)
http://imgur.com/Wnmhd
Click to expand...
Click to collapse
Thanks for the feedback!

complete noob question. adb still confuses me and im tryin to unbrick my prime. its in the recovery bootloop, the thread im following says to do some adb commands. but "adb shell" gives me the message "adb" is not a recongnized as a command or blah blah.. so i figured its cause i don't have the drivers? well anyways.. this thread looks like it has what i need... but where\how do i install the drivers? tia.

shady503403 said:
complete noob question. adb still confuses me and im tryin to unbrick my prime. its in the recovery bootloop, the thread im following says to do some adb commands. but "adb shell" gives me the message "adb" is not a recongnized as a command or blah blah.. so i figured its cause i don't have the drivers? well anyways.. this thread looks like it has what i need... but where\how do i install the drivers? tia.
Click to expand...
Click to collapse
ya... adb not recognised means you don't have the android sdk installed. Also this is the tf101 not the prime. To install drivers hit start and type in drivers. find the one that says unknown or android 1.0 or apx or something right click and hit manually install driver

mrevankyle said:
ya... adb not recognised means you don't have the android sdk installed. Also this is the tf101 not the prime. To install drivers hit start and type in drivers. find the one that says unknown or android 1.0 or apx or something right click and hit manually install driver
Click to expand...
Click to collapse
You also get that message if you have the SDK installed but not in your path and you are trying to run the command outside of the Android\android-sdk\platform-tools\ directory where the adb command resides. I have posted a guide for installing the SDK and then installing these drivers in the Roach's Clockwork Mod Recovery thread. I was trying to help solitude65 who installed a Recovery that only reads internal apparently after he wiped the internal sdcard or didn't realize he needed a ROM on the internal sdcard. Not sure how much of it will apply to the Prime as I have a TF101 and used it to confirm the steps I posted over there.
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
1wayjonny said:
Hey try adding these device ID's to your USB config, this should allow ADB, APX and also Fastboot if and when TF101 gets a unlocked bootloader.
USB\VID_0B05&PID_4E1F
USB\VID_0B05&PID_4E1F&MI_01
USB\VID_0B05&PID_4E3F
USB\VID_0B05&PID_4E3F&MI_02
USB\VID_0B05&PID_4DAF
USB\VID_0B05&PID_4DAF&REV_0000
USB\VID_0955&PID_7820
Thanks for the feedback!
Click to expand...
Click to collapse
Can you tell me specifically what USB config you are referring to and where to find it?

Thank you SO much! I was pulling my hair out, trying to find drivers for my TF101 in recovery mode, and I couldn't.. But these helped me immediately, and did the job!
Thank you!

I am on Windows 8 and couldn't get this installed with an error about missing the hash for the file. It of course is missing, since this isn't a signed driver.
I followed the instructions at http://dhakshinamoorthy.wordpress.com/2012/05/14/installing-an-unsigned-driver-in-windows-8-x64/ and was able to install the driver. If you're using Windows 8, you can do the same to install these unsigned drivers (or any other unsigned drivers for that matter).

Updated version, feedback helpful

1wayjonny said:
Updated version, feedback helpful
Click to expand...
Click to collapse
In order to provide feedback, I would have to have an issue...
the sarcastic joke and hidden props aside, I have a few now phones ill give it a go with sometime in the next week, amazing timing however, just reformatted my "utility" laptop... (CDMA Workshop is such a PITA to resetup after every reformat... so effing annoying! ****ty DRM and updates however are the requirements for a legit copy... sometimes I regret spending that $100)

Hammerfest said:
In order to provide feedback, I would have to have an issue...
the sarcastic joke and hidden props aside, I have a few now phones ill give it a go with sometime in the next week, amazing timing however, just reformatted my "utility" laptop... (CDMA Workshop is such a PITA to resetup after every reformat... so effing annoying! ****ty DRM and updates however are the requirements for a legit copy... sometimes I regret spending that $100)
Click to expand...
Click to collapse
No worries thanks for any help.

I having an issue trying to remove the previous version to the latest one I just sold my tf201 and today i got the nexus7 can someone help on a step by step on what to do in device manager. Now my galaxy nexus isn't recognized when i write adb devices in cmd after trying to push the latest one

perfecto
i tried rooting and playing with my TF101 when i first got it ages ago, but it was all such a pain in the ass. thank you for making this part a bit simpler.

Tried pointing Device Manager to the folder I unzipped Universal drivers to and got this.
Anyone else?

New TF700T not showing in adb?

Hey everyone,
I've read through the All-In-One guide about how to root the TF700T, downloaded the driver pack, put it into developer mode and enabled unknown sources. When I plugged the device into my computer it was immediately recognized and automatically installed the drivers and I can see it through Windows Explorer and browse the file system.
Unfortunately the device doesn't show in adb and I read through this quote in the guide, "if not, install the ADB drivers from Windows Device Manager (if you don't know how to do it then you better stay off from rooting your device)" so I went to the Device Driver and and tried to update the driver with the ADB driver, however, it says it's not compatible.
On the Android device I see the USB mode as Media Device (MTP) and that USB Debugging Connected
In Windows Device manager I see under "Portable Devices" the "ASUS Transformer Pad TF700T" is there and installed without error.
There aren't any device drivers that have a yellow icon indicating they aren't configured correctly.
I had purchased the tablet a few days back and it prompted me for a system update which I did.
I've tried rebooting both my computer and the tablet but it didn't appear to assist.
I'm assuming I'm doing something silly and simple but I cannot for the life of me figure it out.
Does anyone have any suggestions on what I may be doing wrong?
Thanks in advance everyone,
Septurious

Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium

Thanks!
Nebucatnetzer said:
Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious

Glad I could help.
Excuse me that I didn't post the link directly it's a pain on the phone.

I had a similar problem. The TF700 was automatically found, and no ADB drivers were installed. I kept trying to uninstall the driver, but it wouldnt let me. I don't have an option to "delete drivers" on uninstall.
When I tried installing "legacy hardware" to force the drivers, it would come up listed under "Samsung" and not Asus. I think I have my drivers all screwed up from previous phones i've had. I took the driver set, and went to another PC (same os, Win 7 ult x64), and had no problem installing all the drivers and rooting.
Anyone have an idea for me? Not sure if I should start going through my sys32 and manually deleting all driver files associated with my tablet.

Fixed.
I had to do this.
http://www.thewindowsclub.com/how-to-remove-old-unused-device-drivers-in-windows-7
Went through and cleaned up all the old drivers, between the old Samsung Drivers, Motorola Drivers, previous Android ADB drivers. I now plugged in my TF700, and while the ADB shows up as a Samsung device, it shows up on "adb devices", which it didnt before.

Another solution
I tried all listed tips but failed.
ADB driver was installed automaticaly after enabling USB-modem on my TF700.
Now android device chooser showing device

for hours i tried it! no i know why it didnt work!
turn off windows firewall!!! DD maaaaaan

Septurious said:
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious
Click to expand...
Click to collapse
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?

GBDias said:
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?
Click to expand...
Click to collapse
Windows 8?
Try disabling driver signature verification.
Sent from my DROID4 using Tapatalk

Nexus 5 showing up as ACER ADB Interface Windows 8.1

Hi guys, I recently installed windows 8.1 and now my N5 shows up in device manager as ACER ADB Interface and I can't acces MTP , I didn't had this problem with windows 7 , it worked perfectly back than ( i have unlocked and rooted my N5 with windows 7 without any issues ) . What can I do to make it work with windows 8.1 ?

I had the same, you have to go into Device Manager and roll back the driver to the Google one. Proper PITA

I can't do it, the roll back option is grayed out

I have managed to make it work, nevermind .

SilentGTX said:
I have managed to make it work, nevermind .
Click to expand...
Click to collapse
Why not actually post what you did to fix it so it can benefit others in the future? Just a thought...

EddyOS said:
I had the same, you have to go into Device Manager and roll back the driver to the Google one. Proper PITA
Click to expand...
Click to collapse
I rolled the driver back, but it keeps updating to it. I've uninstalled and deleted the driver, yet it keeps reinstalling it. Somehow, my MTP connection started working again. Not sure how though. If I knew which KB update it was, I'd uninstall it from there.

wvcadle said:
I rolled the driver back, but it keeps updating to it. I've uninstalled and deleted the driver, yet it keeps reinstalling it. Somehow, my MTP connection started working again. Not sure how though. If I knew which KB update it was, I'd uninstall it from there.
Click to expand...
Click to collapse
The other option is to manually change the driver in Device Manager from the ACER one to the Google one. I think it's happened as M$ have the ACER driver digitally signed whereas the Google one isn't so it'll always choose the signed driver...

EddyOS said:
The other option is to manually change the driver in Device Manager from the ACER one to the Google one. I think it's happened as M$ have the ACER driver digitally signed whereas the Google one isn't so it'll always choose the signed driver...
Click to expand...
Click to collapse
I'm not sure how to do that, because, of course, if you try to update it, it will say that the Acer one installed is already the best driver. And after uninstalling it, upon plugging it back in, it updates to the Acer driver automatically again.

wvcadle said:
I'm not sure how to do that, because, of course, if you try to update it, it will say that the Acer one installed is already the best driver. And after uninstalling it, upon plugging it back in, it updates to the Acer driver automatically again.
Click to expand...
Click to collapse
You have to manually check and select 'choose from a list' and you'll see the MTP option as well as the Acer one. Select the MTP one and you're good to go

EddyOS said:
You have to manually check and select 'choose from a list' and you'll see the MTP option as well as the Acer one. Select the MTP one and you're good to go
Click to expand...
Click to collapse
Btw... thanks for your help.
I went through those steps, but on my system, the MTP driver wasn't listed as an option.

wvcadle said:
Btw... thanks for your help.
I went through those steps, but on my system, the MTP driver wasn't listed as an option.
Click to expand...
Click to collapse
Hmmm, I've only ever used the Google drivers from the SDK until this stupid ACER one appeared. Managed to get back to it now so it's all good. Perhaps download the Google driver and then point to it?
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip

Yeah , I forgot , sorry about that . I managed to make it work by downloading this drivers " https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip " . After i have extracted the driver i plugged my N5 to the PC, than I went to the Device Manager i right clicked the Acer ADB Interface and I have selected Update Drivers . After that I selected the folder where i have extracted the drivers , than i chose " Let me pick from a list ... " , I selected MTP USB Device and Voila , it works !
PS: You can also try to install the LG Driver " http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 "

EddyOS said:
The other option is to manually change the driver in Device Manager from the ACER one to the Google one. I think it's happened as M$ have the ACER driver digitally signed whereas the Google one isn't so it'll always choose the signed driver...
Click to expand...
Click to collapse
Thanks For your help. It worked.

SilentGTX said:
Yeah , I forgot , sorry about that . I managed to make it work by downloading this drivers " https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip " . After i have extracted the driver i plugged my N5 to the PC, than I went to the Device Manager i right clicked the Acer ADB Interface and I have selected Update Drivers . After that I selected the folder where i have extracted the drivers , than i chose " Let me pick from a list ... " , I selected MTP USB Device and Voila , it works !
PS: You can also try to install the LG Driver " http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 "
Click to expand...
Click to collapse
LG driver helped me to resolve issue while installing LG driver got pop up message for the missing MTP package for windows 8.1, i followed link to download missing package and install after reboot it resolved issue in my Windows 8.1, Thanks for your help.:good:

I can never seem to get adb or fastboot to work I gave up and dual booted my computer with Linux Linux hasn't given me problems with adb or fastboot
Sent from my Nexus 5 using Tapatalk

This worked for me
Hi guys, I had the same problem. My phone was configured as MTP but when i connected to Win 7 it would appears in the Device Manager list as "ADB", this wouldn't allow me to transfer files so what worked for me was:
1- Connect your Mobile to the PC and it appears as ADB Driver (In the device manager screen), rignt click on ADB and select Browse my computer for driver software.
2- Choose let me pick a from list of devices on my computer and choose the option MTP instead of ADB.
3- Did that and problem solve, hope this helps for you !!

Delete this Acer ADB driver when you uninstall it
I have the same issue. Here is what I did and that resolved the issue. Go to "Device Manager" to uninstall the Acer driver. The uninstall window pops up asking you if you want to uninstall it. There is a check box that says "Delete the driver." Make sure you check that off and then go ahead and uninstall it. Once that's done, plug your Nexus 5 back in. The correct MTP driver will now be installed and your computer will recognize the phone normally. Hope this helps.

Experiencing the same on Windows 7...have tried everything suggested
Really hoping someone can help because I've just about had it with this. I'm running Windows 7 Home Premium 64-bit. I have a brand new Nexus 5 16GB. As others have indicated, when I plug my phone into my computer with debugging enabled, it creates an "Android Composite ADB Interface" device listed under "ACER Device" in Device Manager. See attachment.
I have tried every permutation of the 'uninstall driver, manually install Google USB driver' solution, to no avail. The best way I can describe what I'm seeing is that Windows is forcibly categorizing the device as an 'ACER Device' even though the driver files themselves are telling it otherwise.
If debugging is DISABLED, and EITHER MTP or PTP is ENABLED, everything is just fine - the default Windows drivers for those devices kick in, and no 'ACER Device' category is created.
If debugging is ENABLED, and MTP and PTP are DISABLED, when I tell Windows to use the Google USB driver, it says that the device could not be installed.
If debugging is ENABLED, and MTP is ENABLED, the 'ACER Device' issue rears its ugly head even when I tell Windows to use the Google USB driver.
I've already disabled Windows automatically fetching a driver online, so that's not to blame.
If this is the result of a Windows Update, does anyone know the number of the update so I might try uninstalling it? I can't seem to find it despite searching.
Hoping someone out there can help. Thanks!