can't install drivers on win7 or win10 - Fire Q&A, Help & Troubleshooting

i've tried all suggestions to install the drivers and when i connect my fire to my computer, it shows up as portable device > fire. if i try to update drivers, it says that i am already using the best one, the MTP usb device.
i've followed this:
http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
and also tried the drivers from amazon and neither allow me to select the adb driver.

You have turned adb on on the Fire?

Pond-life said:
You have turned adb on on the Fire?
Click to expand...
Click to collapse
thanks for the reply.
yes, i put it in dev mode by tapping the serial numbers and it is adb enabled.

ultraman69 said:
and also tried the drivers from amazon and neither allow me to select the adb driver.
Click to expand...
Click to collapse
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.

i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
thekrakah said:
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
Click to expand...
Click to collapse

ultraman69 said:
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
Click to expand...
Click to collapse
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.

i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
thekrakah said:
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
Click to expand...
Click to collapse

for some reason, on only one out 4 of my win 10 rigs, i had to turn off driver signature enforcement. to do this go to settings, update and security, recovery, advanced startup, restart now. then in the restart menu push, troubleshoot, advanced options, startup settings, then restart. when booted choose "Disable driver signature enforcement" (which is option 7 on current build). now try to install the drivers. after successful just do a normal restart to enable the signature enforcement again

ultraman69 said:
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
Click to expand...
Click to collapse
Can you verify that, "android debug" mode is turned on in the Fire devices developer settings? At least that was the only way I could reproduce the same message output from "adb devices".

I faut with my win 7 laptop for about an hour with one of my fires. Has the yellow icon on unknown device. Ended up "update driver" "browse for file" "let me choose from a list" picked Android/adb composite device. Adb and fast boot now work. I originally had to install Android studio and some extras to get my first fire to link up. Pm if you need help.
Sent from my Nexus 6P using Tapatalk

I recommend RootJunky tool, does everything and gives you instructions what to dohttp://www.rootjunky.com/amazon-fire-5th-gen-supertool/ Also recommend watching all his videos https://www.youtube.com/watch?v=sVv1D_LNLTg&feature=youtu.be

Related

Usb Driver Problems

Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder

ADB Drivers

Hey everyone,
I have been happily using android on nand for quite sometime, and everything has been going well. However, I must have the wrong adb driver installed on my windows 7 computer and can't seem to remove it fully or install the proper one ever. Every time I remove it from device manager, and plug it back in, windows finds it as an HTC composite device, and adb through command line can't find any devices, ever! I would really like to be able to use this feature for things like tethering and what not.
Also, if anyone has any information on how to tether using any OS, windows, mac or linux, I would greatly appreciate it, along with any applications that might be helpful! I have done proxoid in the past and it worked well, pdaNet looks like it might work, but again I don't have a connection to my windows computer!
Thanks in advance for all of the help!
I am using the android SDK usb driver for ADB, you just have to edit a file and add the vendor ID. I can do things like adb logcat, adb shell gives me odd characters in directory listings,I get a ? from adb devices, not sure what that is about.
C:\Documents and Settings\Administrator\.android\adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0e79
0x0bb4
The 0e79 is for my Archos tablet, works fine there. 0bb4 is what showed up in device manager when I plugged in the phone.
I tried to install that driver for my Polaris and it doesn't work.
It shows "Installing Android Phone" while I have my device plugged in. It takes forever and seems that the USB connection hangs the driver install process, but as soon as I disconnect my device, Windows shows me an error message.
Instructions for Vista\Windows 7
For WinVista/Win7
These OS will install Android as a mass storage device. You must uninstall the driver and update to the android driver model.
Instructions:
1) Unplug all removable devices(thumb drive, sdcards, etc) beside the Android phone.
2) Locate "Device Manager", usually under "control panel"
3) Select "Universal Serial Bus Controllers"
4) Select USB Mass Storage Device.
Note: to check if you have the correct device, click on the details tab and select "compatible ids" under properties. There should be three items listed under value.
5) Select uninstall driver
6) Close the window. Now in device manager a new "Android Phone USB device" with a yellow! will appear... If not, Unplug your android device or select Action -> Scan.
Note: view optional steps below if you still have problem with the your windows automatically installing drivers.
7) Click on the "Android Phone USB device"
8) Select "browse my computer to driver software"
9) Under "search this location for driver", Browse for the location that you have unzip the android_usb_windows and select the corresponding folder for your system(AMD64 for 64bit systems or x86 for 32bit systems. Right click -> properties on "My Computer" to check which system you have)
The driver is now installed and is ready to use.r
***Optional.
1. Go to System under Control Pandel.
2. Click on Hardware Tab and Under "Device Installation" select “Never search windows update for drivers”, then OK.
3. Go to Enable debugging on your phone. (Settings->Applications->Development->USB debugging).
4. Run USBDeview and remove all instances of Android Phone
5. Unplug your phone, and plug it in again.
7. Continue on step 7) above.
To turn off search windows update in windows 7, use this link below
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
To turn off automatic driver installation in windows 7, use the link below
http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/
Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.
SuperJMN said:
Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.
Click to expand...
Click to collapse
mine hung as well, what i ended up doing was turnng off the automatic installation. Then uninstalled the adb interface driver that was already installed. Then turning back on automatic installation. Then plugging phone back in and as it was installing automatically, manually installing the adb interface driver at the same time. Eventally the automatic install would error out and the manual install would work. It took like 15 or 20 minutes for it to finish.
when i uninstalled the adb interface, it turned into ''android phone'' in device manager. That was the driver i manually installed while the phone was automatically installing. I know it dont make much sense but it worked for me.
It looks like that will be my fate as well. It also says, that when I do the manual install of the ADB drivers that I already have the most current version installed!!! OH well, keep trying!
Same behavior on my pc with windows 7 32-bits.
When I have lucky the adb driver is connected (working correctly) for a few minutes and then it's disconnected.
i've tried various things to install adb driver, since last night but i've got nothing. i can't install adb driver for my xperia arc.
i installed sdk manager and usb driver. but when i try to install or update driver, i always see this message like "you're using the latest version". So i can't install it.
and also i've tried to uninstall driver and unplugged / plugged my device. then w7 automatically install driver. so i can't install adb driver again.
i want to root my phone, using this way at this link http://forum.xda-developers.com/showthread.php?p=18805560#post18805560
so i must install adb driver, please help me.
thanks everybody
edit: i've windows 7 home premium, 64-bits

[DRIVERS] Nexus 4 Driver for Windows

If you have windows, you will need these drivers to use ADB or Fastboot with your Nexus 4. The long method of getting this is downloading the SDK and running it. I have extracted the drivers and put it into a rar file for easy use.
Follow these steps if you haven't plugged your phone into your computer before.
1. Download the file.
2. Extra the files into a folder.
3. Plug your phone in.
4. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
5. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
If you already installed other drivers and they don't work for you. Download the drivers below and follow these steps:
1. Enable USB Debugging on your phone.
2. Plug your phone into your computer.
3. Go to Device Manager on your computer and locate your device. It will either be under "Android Devices" or "Other Devices" depending whether drivers have been installed or not.
4. Right click on your phone and select "Uninstall."
5. In the box that appears, check the option to "Delete the driver software for this device" then proceed.
6. When that is done, go back to Device Manager and refresh.
7. Locate your phone and right click to select "Update Driver Software."
8. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
9. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
10. Unplug your phone and restart your computer.
11. Plug it back in and everything should work.
Download link:
http://www.mediafire.com/?8xb50uktar8096i
Thanks to efrant for clarifying exactly how to manually select your drivers.
I would suggest everyone download Android SDK.
You have a Nexus device right?
http://developer.android.com/sdk/index.html
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
ijip said:
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
This thread is for Nexus 4 drivers, not the SDK.
Ask your question in the Q&A section.
theexel said:
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
Click to expand...
Click to collapse
Yep, I never needed the whole SDK before. I only download the platform tools too.
Have any other ADB drivers installed? Because then you need to uninstall those:
Go into command prompt and write:
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
Delete all devices including driver software in the "Android Device" section.
Then reinstall the Nexus 4 drivers.
If that still doesn't work, update the driver when connected with usb debugging on and manually add by rightclicking the device, click update driver software, then the "Browse my computer for driver software", then "Let me pick from a list..." then "Show all devices" and then Have disk.
Then you simply point to the driver and select the "Android ADB Interface" (Or something like that) it also has driver for bootloader and composite, bootloader is for fastboot, can't remember what composite is for, but you shouldn't use those.
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
qvert said:
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
Click to expand...
Click to collapse
Go to Device Manager on your PC. If debug mode is enabled, you should see your device listed as an Android phone or something of the sort. If it has a yellow exclamation mark or some sort of symbol next to it, then that means the drivers aren't properly installed. Assuming that is the case, follow FISKER_Q's directions:
Right clicking the device, click update driver software, then the "Browse my computer for driver software." Select the usb_driver folder that you extracted and you should be good to go.
Subbed to refer to later when i have the N4
Sent from my Nexus S
jark99 said:
Subbed to refer to later when i have the N4
Sent from my Nexus S
Click to expand...
Click to collapse
This thread is also in the Misc section of the reference guide in case you can't find it later
I did the same thing and I cant get adb to see my device however fastboot will =/
Shambala001 said:
I did the same thing and I cant get adb to see my device however fastboot will =/
Click to expand...
Click to collapse
Did you enable debugging on your phone yet?
If not, go to Settings > About phone, then tap on "Build Number" 7 times. Go back to settings and you will see developer options. Go in there to enable USB debugging.
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Nitemare3219 said:
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Click to expand...
Click to collapse
Glad you got it figured out. :good:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Try leaving the phone plug in. Go to Device Manager. Find the ADB drivers and uninstall it. While in Device Manager, have it scan for new changes. You should see your phone appear. Right click it and manually install the drivers.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
IAMLordspeed said:
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
Click to expand...
Click to collapse
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Stryder5 said:
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Click to expand...
Click to collapse
I had to put a check in the box next to "Delete the driver software for this device" to get this to work. Otherwise Device Manager will keep detecting the old drivers.

[Q] Kindle Fire HD - USB Compatibility

Hey, I have been trying to root my fathers Kindle Fire HD so he can get the google play store and the google apps(maps, streetview etc) but I seem to have hit a wall!
I have installed the drivers and the Android SDK Tools program etc and got to the point where I open RunMe.bat through command prompt, but nothing happens on the Kindle, and now when I connect it to my computer, instead of popping up in my devices it isn't displayed at all and says "USB Compatibility" and a message about free file transer utilities on the actual device.
Does anyone know how to fix this?
If I have to restore the kindle, how do I back it up? is that all handle by the cloud? Will it keep all his apps/games/books etc?
Many thanks!
Dan Mumford said:
Hey, I have been trying to root my fathers Kindle Fire HD so he can get the google play store and the google apps(maps, streetview etc) but I seem to have hit a wall!
I have installed the drivers and the Android SDK Tools program etc and got to the point where I open RunMe.bat through command prompt, but nothing happens on the Kindle, and now when I connect it to my computer, instead of popping up in my devices it isn't displayed at all and says "USB Compatibility" and a message about free file transer utilities on the actual device.
Does anyone know how to fix this?
If I have to restore the kindle, how do I back it up? is that all handle by the cloud? Will it keep all his apps/games/books etc?
Many thanks!
Click to expand...
Click to collapse
Which driver did you install? Sounds like the adb composite isn't loaded.
First: Ensure adb is enabled under settings.
Second: Read this to see if you installed the driver under adb device or adb composite. It needs to be the composite.
Install your drivers again.
Go to device manager and right click on your KFHD.
Click update driver.
Browse my Computer for driver software.
Let Me pick from a list of device
Show all and hit next
Hit have disk and browse to your directory where your driver is stored at.
After you click ok there will be a few adb choices. Always select adb composite device. Else half the dev adb tools cant detect the KFHD.
After that it will install the appropriate driver(64 or 32 bit)
Whallah you have installed the drivers.
***NOTE****
If you have already plugged in your KFHD and windows has already installed the incorrect driver don't panic. Right click the Kindle and click uninstall. Check delete driver and ok. Then you can proceed to install the right one.

Cannot Get Drivers Installed for Windows 8.1 - Manual Installation or SDK

I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.

Categories

Resources