Database Info

Issue using ADB and Windows 7?

I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?

LOL, I just switched back from Ubuntu to Windows 7 just to see how things have progressed. There are so many little Windows 7 quirks that drive me crazy that drove me back to Ubuntu almost instantly. Give Linux a try. A good starting Linux OS would be Linux Mint:
http://www.linuxmint.com/index.php

I had a similar issue when I tried it. Despite the fact that there are 64-bit drivers for Vista/7 available, I don't believe they actually work for ADB currently. I'm pretty sure everyone who has ADB working is using Windows XP 32-bit.

I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.

I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.

ch4dr0x said:
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
Click to expand...
Click to collapse
I faced the same problem a few days ago. I have Windows 7 Ultimate x64 and in a first installations the drivers work fine and the device has been displayed, but BAM when I try to use ADB no way.
After many tries I resolved the issue running the Command Prompt as "Run as administrator" and VOILA worked fine.
I hope this can help you.

ch4dr0x said:
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
Click to expand...
Click to collapse
Try Mint instead of Ubuntu. Mint is Ubuntu based. The big difference with Mint is that it already has all of your codecs installed - great for beginners.

If you installed first the htc sync, you have to remove the current drivers..
and had the drivers from the androidsdk pack! There's is a a lot of program who delete usb installed hardware/drivers.. delete all from htc on this programs!
Hope this solves ur issue!

I use Win7 64bit(rc1) .. i have the amd64 driver installed..
I see the phone from adb (not fastboot) when it's normally connected with USB debugging turned on.
I see the phone from fastboot (not adb) when it's in fastboot mode.

I have no choice but to laugh at myself, just realized I was IN FASTBOOT on my phone and not recovery. Fail me.
Now if I could just edit this apps2hd code /sigh.

ricardomega said:
If you installed first the htc sync, you have to remove the current drivers..
Click to expand...
Click to collapse
and remove htc sync, there are a process than cause problem with adb (i don't remember the name)
I kill this process and adb 100% work fine, or unistall HTC Sync..

GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=

ricardomega said:
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
Click to expand...
Click to collapse
Except that... that wasn't my issue Its ok thanks for the input.

"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.

parrot5 said:
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
Click to expand...
Click to collapse
The same confi, the same result

Everything works fine here with Win 7 Ultimate x64, you just install the driver in the Android SDK.

make sure u have usb debugging checked... cause i have windows 7 rtm ultimate and my adb works fine... i just loaded the needed file into windows/system32 and also put my fastboot.exe in there and added the tools folder to the environment variables and have no problems

What do I load to the system32 folder? I can't install the drivers from the SDK package. Is there a way to overwrite the ones Windows automatically installs and thinks is more up to date?

detonate said:
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
Click to expand...
Click to collapse
Make sure your phone is in recovery mode and NOT fastboot mode.

Finally, I experienced that error you people had been reporting. It MAY have to do with the HTC Sync driver, as suggested, but it really had worked fine with other roms before, so I am not sure. I tried uninstalling and reinstalling the driver, tried to push the ADB driver manually, but that didn't work. And, before I try to uninstall the HTC Sync driver as suggested (I don't even know if I have that installed), I got it working by just plugging in another USB flash drive. Go figure.
So for anyone still having the issue after trying all other solutions, try this bizarre one:
1. Go to device manager and uninstall the HTC disk drive device. (This alone won't work, I tried)
2. With phone still plugged in, plug in a USB disk drive (or maybe just any USB device?) into another USB port.
3. Suddenly Windows 7 detect that unknown ADB driver, as it should. Now you can go ahead to install the correct ADB driver.
As a side note, this computer running Windows 7 Beta/RC have had a lot of problems with USB disk drives in general. The problems disappear after Windows 7 RTM (final).

[GUIDE] adb for your gtab (windows)

hello all,
i had some small trouble setting up adb for my viewsonic gtab, so once i figured it out i thought i'd share.
so far, this is confirmed working only on windows 7 32 and 64 bit. vista should be the same, but i'm not sure, i'll keep you posted. EDIT: we've confirmed these steps for at least vista 32 and xp 32-bit. there shouldn't be any differences between the 32 and 64 bit systems as far as the instructions go.
most of my information comes from nvidia's tegra site, here. that's a pretty technical-minded page though, so i wanted to condense it.
make sure usb debugging is turned on for your tablet (settings -> applications -> development -> usb debugging)
1. open your device manager (right click My Computer -> Manage -> Device Manager)
if you haven't done anything to set up drivers yet, skip to step 4.
2. find your gtab. depending on your previous attempts, this may be under "Android Phone" at the top (Android ADB Interface, make sure it's your tab and not your phone), or under "Universal Serial Bus controllers" on the bottom (called Android somethingorother. should be at the top of the list.)
3. uninstall it. right click, uninstall. check the box that asks you if you want to delete driver software. i didn't need to use usbdeview to uninstall the drivers, but if you're running into issues on this step try it. usbdeview must be run as administrator, thanks droidjunkie.
it looks like most people should just skip right to usbdeview to uninstall any old drivers. like i said, i didn't have any issues using windows' "delete driver software" option, but apparently i was just lucky. rcgabriel recommends usbdeview, and he knows stuff.
4. unplug, and plug your tablet back in. now your device should be under "Other Devices" near the middle (will have a yellow exclamation icon, called NVIDIA harmony). good.
5. hopefully you have the android sdk installed. if you don't, go find a generic guide on setting up adb and then come back. when you have the sdk installed, you need to run "SDK Setup.exe" from where you installed it and use it to download and install the usb drivers (currently r8).
6. open the "usb_driver" folder in your sdk directory. right click "android_winusb.inf" and open it with notepad or your favorite text editor.
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
8. go back into device manager. right click your tablet, select update driver, and click "browse my computer...", then "let me pick...", then "next", then "have disk"
if you're confused on this step, check this post.
9. browse to your android sdk, under the usb_driver folder, and select the "android_winusb.inf" file.
10. of the three choices, the bottom should say "Android Composite ADB Interface". choose it. click next, and allow the driver to install even though you get a big scary red warning.
11. open a command prompt, preferably in the tools directory of your sdk. type the following:
Code:
echo 0x955 > "%USERPROFILE%\.android\adb_usb.ini"
and hit enter. it will just return a new prompt line.
12. test it out.
Code:
adb kill-server
adb devices
you should see your device's serial number. all is well. congrats.
let me know if i should add or clarify anything here. thanks!

Just in case anyone doesn't know what ADB is:
http://developer.android.com/guide/developing/tools/adb.html
Thank you so much! Great info!

this is great! thanks for the concise writeup

I had trouble too. I was unable to get uninstall device to work and put the device under Other devices. I was advised to use usbdeview from pershoot. I used this program to remove the device and was able to get it moved to Other devices in Device Manager.
HTH

Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined by iammuze, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.

THANK YOU!!! after trying many different guides this one worked...other then the fact that I had to right click usbdeview and click "run as administrator" in order to delete the driver it keep installing when i would plug in my tab. I am on windows 7 32 bit, for anyone else having problems getting adb working that is using windows 7.

Thanks
I am finally connected via adb.

rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined by iammuze, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
I had the same experience on Windows 7 that you are having now. Like you, I tried following all the instructions similar to the ones listed above plus advice from other forums and still could not get it to work. I was finally able to get mine working after I discovered Windows still had some drivers from previous failed attempts stored in its system files. These old drivers were interfering with the proper installation of the new usb driver.
To get rid of the old drivers completely, do a file search for the file named android_winusb.inf in your Windows/System32/DriverStore. If your search results show several file folders with the same driver, try to delete each of the those folders completely. After those folders are deleted, you can do a clean install following iammuze's instructions.
NOTE: To delete those folders you will have to change the folder permissions. It won't be easy to do, because Windows doesn't like having its system files messed with. Unfortunately, I can't give you exact instructions on this, because I don't currently have a Vista machine.

rlapela said:
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Click to expand...
Click to collapse
where does your gtab show up under device manager?

Thanks, it worked great! ADB screen shots!
Look at this mess I have crammed onto one page.

[UPDATE: Problem solved: I had two versions of adb in my PATH and the old version (1.0.20) was being executed instead of the new version (1.0.26). Apparently the old adb silently fails and returns no devices when used in conjunction with the current drivers. I worked this out by accident. But if you're looking for ideas, there are lots in the ADB for Dummies thread: http://forum.xda-developers.com/showthread.php?t=502010 ]
Hi All
I've been banging my head against this for hours with no luck. I can't get adb to recognise my gTablet. Here's what I've done:
I'm on WinXP. gTablet is running zTab Clean 3.0
- I've downloaded the latest ADB USB drivers using the Android tools (driver verion 4.0, December 12 2010).
- I've made the modifications to android_winusb.inf noted above.
- USB Debugging is enabled on the gTab
- adb_usb.ini contains a single line containing: 0x955
I've followed various instructions and the driver install ~seems~ to go ok, but adb doesn't work.
Windows Device Manager lists the following devices which are associated with NVIDIA Harmony:
Android Phone > Android Composite ADB Interface
Universal Serial Bus controllers > USB Composite Device
Universal Serial Bus controllers > USB Mass Storage Device
USBDeview lists three devices:
NVIDIA Harmony NVIDIA Tegra 2 USB Device
NVIDIA Harmony USB Mass Storage Device
NVIDIA Harmony Android Composite ADB Interface
The first is listed as connected. The others aren't.
When run adb i get this:
> adb kill-server
> adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
No devices are listed.
I have tried many combinations of uninstalling these devices (with Device Manager and with USBDeview). When I reconnect I get prompted to install drivers. I have tried installing at this point, cancelling and then installing in Device Manager, not cancelling so the Plug and Play window stays open and uninstalling with device manager. None of this has worked. Also the device drivers seem to linger on my machine as they seem to auto-reinstall even after I have uninstalled them (I've also tried the suggestion of searching and deleting the .inf and .dlls from C:\Windows -- that didn't work out either).
I have also been careful to make sure adb is not running when I change the drivers. I have tried rebooting the computer and the gTablet after various installs.
The only way I can get the gTablet to appear in "Other devices" is to plug the device in (the PnP window pops up, I leave it open and ignore it). Then I delete the drivers in USBDeview. Then I unplug and replug the gTablet. Now there is one device in "Other devices": NVIDIA Harmony. Problem is, if I right-click "Update driver..." it won't let me install from the Android .inf, it says "The specified location does not provide information about your hardware." and forces me to install "USB Composite device". Once that's installed, two more NVIDIA Harmony devices appear in "Other devices". The first requires me to install "USB Mass Storage Device" (once again won't accept the .inf). The third does allow me to install "Android Composite ADB Interface". That gets me to the point where the drivers are loaded as listed above. But adb still lists no devices.
When I first started trying to set this up I had old drivers for the original HTC android phone installed. I deleted these with USBDeview.
I think that's all the information I have. Please let me know if you have any suggestions, I'd love to get this working.
Thanks!

A real plus would be screenshots, I'm getting a little confused at the device manager window, especially the part where it's supposed to give you the option "let me pick" > "have disk" > locate the .inf > choose the last of the three choices
I'm not getting any of those windows/options. Also, when I uninstall it, unplug the gTab, and plug it back in, it just re-installs the default Tegra driver. Any help?
Right now my device is showing up under "Disk Drives" as "NVIDIA Tegra 2 USB Device", and then also under "Portable Devices" as "G:\"
EDIT: Fixed! (Sorta)
I found another forum that told me that in Device Manager, select "Add Legacy Hardware" from the "Action" menu. After going through there, I was able to complete the steps you told me to. If anybody's having the same problem I had before, I am using Windows 7 64-bit, so that may be part of the problem? I'm not sure. But it's installed now and in Device Manager it's under the "Android Phone" section as "Android Composite ADB Interface".
However this raises a new problem, it has a yellow triangle with an exclamation mark over the icon, and it comes up with the error "Error code 10: Device cannot start".
Any help?

you edited the .inf file to contain the three lines specified, and selected the modified driver when adding the driver, correct? i'll try to add some screenshots for the dev manager section

after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png

Hi,
FYI, one thing to be careful of: In the thread where there's info about adding the 3 lines to the .inf, there's also a full .inf file.
If you try to use the full .inf file, note that it has references to various DLLs, which may, or may not match the DLLs in the driver install directory, so, if you use that full .inf from the thread, you have to adjust those DLL references to the ones for the DLLs you actually have on your machine.
In my case, I found it easier to just add the 3 lines to the .inf that came when I installed the USB driver files from the Android development website, which then worked.
Just an FYI...
Jim

iammuze said:
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Click to expand...
Click to collapse
THIS IS PIVOTAL... This is where I had the hang up. Make sure that you are looking at iammuze's pic here, especially the 2nd image. by default most of us are used to just pointing to the correct directory where we DO have the modified .ini and it grabbed the wrong one. You HAVE to select 'let me pick'
Thank you iammuze for pointing this out. I think that's where most get lost. It haunted me for weeks as I was just 'skinning' through directions and missed this important step!

Just a quick suggestion - instead of trying to hunt around and fix drivers that are already installed and broken, I highly suggest using USB Deview (http://www.nirsoft.net/utils/usb_devices_view.html) which lets you nuke out the old drivers easily on a Windows Vista/7 machine.
I had old ADB drivers from my Nexus One sitting around, and I was unable to uninstall stuff with Device Manager.
Just run USBDeview **as administrator** if you are on Windows Vista/7 and you can uninstall old drivers for USB devices with a single click (in this case, just nuke any old Harmony drivers or other ADB drivers). Then the next time you plug in your G Tab, you should be able to select the proper drivers as suggested in the first post.

doesn't work
So i have also been trying for days and can't get it working right.
Running Windows Vista, have ADB installed, and can connect to other Android devices. I have setup the android_winusb.inf properly, but when I connect my device it shows up in Device Manager as a Portable Device->Tegra.
I have uninstalled the tablet and every other android device using usbdeview as admin
I have searched and destroyed all other usb.inf files.
i am running VEGAn-1.0.5B
No matter what happens, as soon as I plug in the tablet it immediately installs it as a Tegra Portable.
any help is appreciated!

that's very odd, i haven't seen that device description before. it doesn't sound like a vista issue... do you have another computer with vista on it anywhere that you can plug your gtab into? just to see what it reports to dev manager on a super clean system.

Old drivers were conflicting from previous installation attempts for me as well. All is working well once USBDeview was finally able to uninstall the device, however, it took multiple attempts and reboots for it to actually remove them. All is well now, and my Device is connected to the ADB. Thanks Everyone!

HOW TO: Alcatel Pop Astro (T-Mobile) and USB ADB drivers (MT65xx problem)

So we got one of the free Alcatel Astro Pop phones from TMO for my wife. First thing I wanted to do was get MyPhoneExplorer running on it in USB mode. OMG. What a nightmare. Alcatel doesn't supply USB drivers for this phone and neither does MediaTek directly from their site. I tried damn near every internet suggestion out there (including downloading and installing PDANet, a couple of driver packages, etc.). Nothing worked. Windows XP (yes she's still on that) would just laugh at me with an unknown Android device (MT65xx Android Phone) exclamation point. Always the same message -- problem with a service in the INF.
However, I solved the problem and now it works like a champ so I thought I'd share what I did:
1. Make sure Android debugging is turned on in the phone. (7 taps routine). Set the phone in USB MTP mode (I think it's the one that ultimately worked).
2. Download the generic MTK drivers from MTK HERE:
http://online.mediatek.com/Public%20Documents/MTK_Android_USB_Driver.zip
And no, these won't install directly either. Anyway, unpack the ZIP file on your PC.
FWIW, you can see all the OEM Android driver links here: http://developer.android.com/tools/extras/oem-usb.html
3. Now the trick. I EDITED the INF (android_winusb.inf) file by adding a new line under the [Google.NTx86] section (commented as ;MTK device) to match the device IDs reported by Windows in Device Manager as follows:
Code:
[Google.NTx86]
;MTK device
;This line added to support Alcatel Pop Astro
%CompositeAdbInterface% = USB_Install, USB\VID_1BBB&PID_0167&MI_01
I assume if you have an AMD processor you'd need to make the appropriate changes to the [Google.NTamd64] section.
4. Next I re-ran the Windows Device Manager update driver routine, pointed it to my edited INF folder and voila, everything installed! The Android Phone "MT65xx" turned into Android Composite ADB Interface and the whole mess worked.
Now when I connected MyPhoneExplorer, it found my wife's phone right off and the sync via USB worked like a champ!
Hope this helps others using this phone.
NOTE: Mods, if this is not the right spot for this post, feel free to move it.

Blackview Tab 8 - which ADB, how to remove "Search" widget...

I wasn't sure where to post this, as the only Blackview-related subforum is for one of their phones... Anyway, I recently bought Blackview Tab 8 (a 10" tablet), and I'm quite pleasantly surprised about its quality (even the box is almost wooden-like ) and the fact that they give you basically everything you need in the package (unlike some manufacturers who keep taking away things season by season...). Also, pure Android without any bloatware - there were a couple of games and apps I don't really need, but they can all be easily uninstalled, or at least disabled (the latter didn't reappear so far, I hope it stays that way).
Three questions for now:
- Any idea which ADB drivers should I install to be able to use adb on this device? I already have three on my Windows 7 computer from before, but connecting this device to the computer didn't find a suitable one.
- How can I remove the "silhouette" of Google Search widget/box on the home screen (other than the workarounds such as changing the launcher, or moving icons to a secondary page and leaving the silhouette alone)? It just stays there after disabling Google/Assistant/etc apps, but doesn't do anything and it can't be moved. I had a similar issue in the past (I think it was a Chuwi tablet).
- How can I tell if the device can be connected to an external display via USB-C to HDMI adapter?

Google's ADB & Fastboot drivers basically are both device and Android OS version independent. However how they got implemented by OEM/Carrier is different. Also in most cases it's required to install an additional "Android USB Driver" provided by OEM/Carrier to make ADB and/or Fastboot flawlessly work.
A link to an ADB / Fastboot installer is to be found in my signature.

I think I actually need those "additional drivers". From what I can see your script downloads what I already have (from platform-tools). adb.exe doesn't show any devices, though. The exclamation marks in Device Manager are at "ADB Interface" and 3x "Unisoc Phone".

Neuromancer said:
I think I actually need those "additional drivers". From what I can see your script downloads what I already have (from platform-tools). adb.exe doesn't show any devices, though. The exclamation marks in Device Manager are at "ADB Interface" and 3x "Unisoc Phone".
Click to expand...
Click to collapse
Here you go:
Unisoc / Spreadtrum SPD drivers for Windows (SCI & USB)
Its important to install SPD drivers else Spreadtrum flash tools like Research Download, CM2 SPD etc won't be able to detect the phone. This is a collection of unsigned (.inf) drivers to be installed
forum.hovatek.com

I tried
Spreadtrum SCI Android USB drivers
Spreadtrum Drivers
SCI android usb driver jungo v4
SPD drivers 2018 ver2.0.0.131
but none of them worked.

In the end, I was able to make it work using these drivers:
How-to install SPD Driver R4.20.0201 (Easy Guide)
Step-by-step guidelines to download and install SPD Driver R4.20.0201 on Windows Computer to connect SPD/Unisoc Devices.
gsmusbdriver.com
But truth be told, I'm not sure if that was the only requirement (because there were also remnants from previous manual install from the link jwoegerbauer provided).

Pixel drivers on Windows 11

Hey there people,
I can't find a solution for this one, so here I am!
I want to transfer files from my computer on Windows 11 to my original Pixel, but I can't find a way to install drivers for it:
Automatic driver install does not work
Google USB drivers aren't compatible with it according to the device manager
Google drivers from the full list of Windows drivers don't work either
The phone is detected as 4 Pixels in the device manager, as well as a disk which isn't readable and returns nothing in the disk management service of Windows.
Any tip will be really greatly appreciated!
Thanks in advance to you all

BTW I tried the usual fixes: original cable, other USB port, reboot, changing the USB management setting to PTP/MTP… nothing works.

follow these instructions brother. The fix for me was to put the phone in fastboot mode before trying to install the Google drivers. You do that by issueing the command "adb.exe reboot bootloader",