Related
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
thecurran said:
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
Click to expand...
Click to collapse
Did you ever find this out, I'm having the same problem.
Just install the SDK and it should work?
Sent from my HTC Desire HD using Tapatalk
yes the drivers are included in the android SDK from google website
I installed the pdanet software to get it recognized in the fastboot mode.
thecurran said:
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
Click to expand...
Click to collapse
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
I had the same thing - just go to properties, select to update the driver manually,and then select to choose from a list of known devices(this is really important, don't select to choose your own driver file). Second or third from the top should be an Android ADB interface device. Just select that and it should work just fine ;-)
mskip said:
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
Click to expand...
Click to collapse
You sir, are my hero!
Thanks alot
Easiest way is through installing PDAnet, that's what I did.
Sent from my Galaxy Nexus using XDA App
On Windows 7 you go to device manager and select
Updated driver > Browse my computer... > Let me select... > Show all > Have disk
And then browse to the inf file in the android-sdk-windows\extras\google\usb_driver folder.
It's a pain but it works perfectly.
or get a mac
appelflap said:
or get a mac
Click to expand...
Click to collapse
If Google and simply included an install section in the INF file people could have double clicked it and everything would work fine and dandy.
This is not an OS wars case, it's a (minor) 3rd party issue.
Eoinoc said:
If Google and simply included an install section in the INF file people could have double clicked it and everything would work fine and dandy.
This is not an OS wars case, it's a (minor) 3rd party issue.
Click to expand...
Click to collapse
Agree, although developing on a unix based machine (mac or linux) is so much faster.
gambiting said:
I had the same thing - just go to properties, select to update the driver manually,and then select to choose from a list of known devices(this is really important, don't select to choose your own driver file). Second or third from the top should be an Android ADB interface device. Just select that and it should work just fine ;-)
Click to expand...
Click to collapse
Worked perfectly, thank you!
Can somebody help me. I have everything installed but it won't recognize my device
Sent from my Galaxy Nexus using xda premium
I'm new and not allowed to post links
Go to the Samsung Homepage of your Country/Language, go to support -> download center, enter galaxy and use the autocompletion for galaxy nexus, then download the usb driver
was not working for me so I force the use of google usb driver from Android SDK by:
- opening windows device manager
- right click -> update driver on the Other devices : Galaxy(exclamation mark)
- Browse my computer option
- Let me pick from my computer option
- click next on the Show All Devices upper selection
- click Have Disk and browse toward your android-sdk\extras\google\usb_driver
- select Android ADB Interface, Next and finish with the Yes
adb devices command reply correctly
I've done the same and flash succesfully my Gnex in fastboot (once you're in bootloader the driver to update in device manager is Android 1.0).
Adding new lines in the android_winusb.inf file from the extras\google\usb_driver leads exactly to the same result.
As it's not a conventional method there might be some issues
mskip said:
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
Click to expand...
Click to collapse
Just wanted to say thank you as this has resolved my issue. I had installed Android SDK which didnt help.
Edit: I had to install the driver to DeskNotifier application would work with my Galaxy Nexus. After installing, it did connect fine. Strangely though, as soon as I sent a test msg from my phone to the PC, my computer became extremely sluggish. I am now rebooting
USB driver still won't install
Neither the USB driver from Samsung nor Google will work on my Win7 machine with my Galaxy Nexus. I have the device plugged in and in recovery mode. The device shows up as a Galaxy Nexus on the device manager, but is unable to install either one.
Thanks for your help.
http://forum.xda-developers.com/showthread.php?t=1626895, part A. It seems the device should be booted normally to install the adb drivers.
Hello!!
Well, hey guys. I thought I tell you the story, on why I posted this thread.
It started as I was installing Windows 8, on my laptop, and had the same problem, as some others. I just could not install the drivers, for my Droid, so I had a looksee and found that Windows 8 didn't yet have the capability, to download unsigned drivers, unlike Windows 7. So, I found a way of "tricking" Windows, into thinking, that these drivers are legit and it isn't forbidden to use, which is exactly what this tutorial tells Windows, in a way.
So, get going and use the full potential of your Android device!
Tutorial:
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... : devmgmt.msc
Now, the dive manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here/
To prevent confusion: When I say install, it can mean unpack, or instal... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has poped up, choose "Browse my computer" and goto your dsktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\adb reboot-bootloader
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick, from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices.
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your SAMUNG GALAXY NEXUS!"!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Addition: You can only reboot into bootloader, if you are using a motorola, Google or HTC branded Android device! This will NOT work with Samsung models (i.e. Galaxy S II/III) due to the fact, that they use Odin mode. Should the drivers need updating, for some devices, please let me know!
Motorola Razr
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Click to expand...
Click to collapse
Download MotoHelper. Right click the file and run in compatibility mode. It should install the drivers. I used this to run fastboot with my xoom.
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
thejakenixon said:
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
Click to expand...
Click to collapse
Bummer, I just remembered there was a setting to skip os version check in compatibility mode. Did you try that? If that won't work unfortunately I don't know what else to try. Sorry.
Sent from my Xoom using XDA Premium HD app
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
First of all, thanks, for letting me know about the link It's uploading again ^^
Yes, you can do the same for your Motorola. But only with the ADB drivers. Just do the same as with the Samsung. Select your device, form the devman. and right click. Update device drivers -> Browse -> Let me choose from a list... -> Samsnung ADB interface.
They are all provided by Google, inc. so, they are compatible, with every Android device. I've even used my Samsung ADB drivers, for a Sony Ericsson Xperia X8. So I can actually say, for myself, that they work. You then can work, using fastboot... ^^
Have fun fastbooting!
LG familyguy59/Beatsleigher
Well, I'm definitly glad, to see I'm actually helping some people, and they're appreciating it!!
I don't remember mentioning it, but if you Need help, PM me. I'll help you via Team Viewer ^^
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
iconicpaul said:
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
Click to expand...
Click to collapse
Yes, it works on both x86 and x64 bit architectures of Windows 8, works withRC and with pre-release...
Sent from my GT-I9300 using xda app-developers app
confirmed, it works, thank you...very fast and easy
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
To your edit. You have extracted the files. This is also called "installing" because you have extracted NEEDED files. Even when you extract a .zip/.rar/.tar/.tar.gz and so on, because you need files out of them, you are installing, but not to the system, but to yourself
Sorry for bringing up an old post, but this method is not working for me on Windows 8 Consumer Preview. When I'm trying to install the ADB drivers, it says the drivers cannot be installed because it's not digitally signed.
UPDATE: I got it to work by disabling the Digital Signature Enforcement on Windows 8. Steps: Restart Windows > Boot loader Menu > Other Options > Advance Options > *Computer Automatically Restarts* > Press F7 to Disable Digital Signature Enforcement
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
2phonejones said:
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
iconicpaul said:
confirmed, it works, thank you...very fast and easy
Click to expand...
Click to collapse
No worries, dude That's what I posted this thread for.
familyguy59 said:
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
Click to expand...
Click to collapse
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Could someone pls. create a video tutorial, nad post this on Youtube, for me?
My laptop broke a couple of days ago, and my PC is only capable of running 98 - Vista, so, running on XP with 1GB of RAM.
I would appreciate this very much!
If you could do so and send me the link, via PM, I would be glad to pay 5€, via PayPal!
2phonejones said:
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Click to expand...
Click to collapse
Ok, dude! Have fun!
Didn't work for me.
jorgefcbastos said:
Didn't work for me.
Click to expand...
Click to collapse
Did you follow the tutorial COMPLETELY, or did you leave stuff out? If you left something out, it's obviously not going to work
You may have to disable device driver signing, I've had quite a few people notify me about this.
But I'll sign the drivers, ASAP, so you won't have this problem
LG familyguy59/Beatsleigher
Edit: I forgot to mention, you need to tell me what exactly didn't work, otherwise I can't really help you
So after going through this headache of not being able to fastboot either of my Nexus devices (GNex and N7) I have found the solution to my problems and I am sharing it with you guys.
Windows 8 forces drivers to be digitally signed and checks that signature with it's known driver signatures at home. This is a problem if you are trying to install and use something like fastboot/adb which Redmond may not have drivers for.
I was personally trying to install this as I did before on Windows 7: http://forum.xda-developers.com/showthread.php?t=1379875 and in order to install this we need to "Disable driver signature enforcement"
Steps to be taken:
1.) Bring up Charms by mousing over to the right of the screen
2.) Go to Settings
3.) Change PC Settings
4.) General
5.) Scroll down to Advanced Startup > Restart Now
6.) Trouble shoot
7.) Advanced options
8.) Windows startup options
9.) Restart
10.) Choose F7 (I believe) or click on "Disable driver signature enforcement"
11.) Reboot
Install the relevant driver (In my case Universal driver) under Device Management
This allowed me to install the Universal driver for both my Nexus devices. Anyway, hope it helps ya'll.
(Mods if posted before feel free to delete/merge/whatever.)
Or avoid all that by installing drivers from here:
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW#
Then you can install the N7 ones as well.
http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
That way you don't have to deal with a Test Mode watermark and have the latest drivers.
Already posted in the "101" sticky over a week ago.
efrant said:
Already posted in the "101" sticky over a week ago.
Click to expand...
Click to collapse
efrant, if you use the official drivers and not ones that someone patched together, there is no need for that step.
adrynalyne said:
efrant, if you use the official drivers and not ones that someone patched together, there is no need for that step.
Click to expand...
Click to collapse
Yup, if you use the Verizon_Wireless_I515_Galaxy_Nexus_USB_Driver_v1.4.6.0.exe from Samsung's website, I believe it is signed, so it probably would work.
The issue was that some users (myself included), had problems installing the driver using Samsung's .exe package. 1wayjonny's repack worked flawlessly, and doesn't install anything else...
I am able to isntall just fine BUT i cannot get the drivers to work and its ****ing iritating. I just get something like This unit cannot start (error 10), A request for the USB device descriptor failed.
Nburnes said:
So after going through this headache of not being able to fastboot either of my Nexus devices (GNex and N7) I have found the solution to my problems and I am sharing it with you guys.
Windows 8 forces drivers to be digitally signed and checks that signature with it's known driver signatures at home. This is a problem if you are trying to install and use something like fastboot/adb which Redmond may not have drivers for.
I was personally trying to install this as I did before on Windows 7: http://forum.xda-developers.com/showthread.php?t=1379875 and in order to install this we need to "Disable driver signature enforcement"
Steps to be taken:
1.) Bring up Charms by mousing over to the right of the screen
2.) Go to Settings
3.) Change PC Settings
4.) General
5.) Scroll down to Advanced Startup > Restart Now
6.) Trouble shoot
7.) Advanced options
8.) Windows startup options
9.) Restart
10.) Choose F7 (I believe) or click on "Disable driver signature enforcement"
11.) Reboot
Install the relevant driver (In my case Universal driver) under Device Management
This allowed me to install the Universal driver for both my Nexus devices. Anyway, hope it helps ya'll.
(Mods if posted before feel free to delete/merge/whatever.)
Click to expand...
Click to collapse
Thanks,, Solved the problem...
thanks!!!
I tried this method and another method. I still can't get the drivers to work correctly. I installed the drivers and now when i connect my phone it is now coming up on device manager as "Andriod bootloader interface" I have a sony xperia S and after about 5 seconds it reboots. Any thoughts?
when i upgraded to windows 8, all i did was plug my phone in, go into device manager and find my phone and uninstall drivers since it wouldn't let me use fastboot even though it recognized my phone. i then installed pdanet and let it install the drivers and rebooted and it worked great.
t1.8matt said:
when i upgraded to windows 8, all i did was plug my phone in, go into device manager and find my phone and uninstall drivers since it wouldn't let me use fastboot even though it recognized my phone. i then installed pdanet and let it install the drivers and rebooted and it worked great.
Click to expand...
Click to collapse
I looked up pdanet and its a program to tether my phone. Why would that help with fastboot?
it installs the correct drivers needed to use fastboot for your phone. you can just uninstall the app when it's done, i kept it because sometimes i use the cable to tether my phone to my laptop.
---------- Post added at 02:47 PM ---------- Previous post was at 02:47 PM ----------
i'm just telling how i did it, it's up to you how you do it.
t1.8matt said:
when i upgraded to windows 8, all i did was plug my phone in, go into device manager and find my phone and uninstall drivers since it wouldn't let me use fastboot even though it recognized my phone. i then installed pdanet and let it install the drivers and rebooted and it worked great.
Click to expand...
Click to collapse
I did what you said it installed the drivers but when i connect my phone in fastboot its still doing the same thing, rebooting after 5 seconds. On device manager the phone comes up as "boot S1 download" I will try installing the fastboot drivers again and report back
did you uninstall any drivers for your phone first?
I'm having an absolute mare with Windows 8, fastboot drivers won't install (with the Samsung package or the naked drivers - just says 'no drivers found') and now the SDK won't install as it doesn't think I've got the Java SDK on my computer (which I have). This is a ballache!
Windows 7 was so much easier...
EDIT: SDK seems to be done following this:
http://forum.xda-developers.com/showthread.php?t=1758817
I did do it but think I set the path wrong so need to check it later on!
Nburnes said:
So after going through this headache of not being able to fastboot either of my Nexus devices (GNex and N7) I have found the solution to my problems and I am sharing it with you guys.
Windows 8 forces drivers to be digitally signed and checks that signature with it's known driver signatures at home. This is a problem if you are trying to install and use something like fastboot/adb which Redmond may not have drivers for.
I was personally trying to install this as I did before on Windows 7: http://forum.xda-developers.com/showthread.php?t=1379875 and in order to install this we need to "Disable driver signature enforcement"
Steps to be taken:
1.) Bring up Charms by mousing over to the right of the screen
2.) Go to Settings
3.) Change PC Settings
4.) General
5.) Scroll down to Advanced Startup > Restart Now
6.) Trouble shoot
7.) Advanced options
8.) Windows startup options
9.) Restart
10.) Choose F7 (I believe) or click on "Disable driver signature enforcement"
11.) Reboot
Install the relevant driver (In my case Universal driver) under Device Management
This allowed me to install the Universal driver for both my Nexus devices. Anyway, hope it helps ya'll.
(Mods if posted before feel free to delete/merge/whatever.)
Click to expand...
Click to collapse
You seriously saved the day. Awesome! Gave thanks!
anyone found a diag driver for windows 8 x64 got the usb driver instaled but still cant find a diag driver that works.
djcodine said:
anyone found a diag driver for windows 8 x64 got the usb driver instaled but still cant find a diag driver that works.
Click to expand...
Click to collapse
Whats a diag driver?
Sent from my JB'd speedy
CNexus said:
Whats a diag driver?
Sent from my JB'd speedy
Click to expand...
Click to collapse
its a diagnostic driver. The regular usb driver allows for charging and access to memory on your micro usb, but you need another driver to access the phones internal settings once its put into diagnostic mode. Such as programing the phone for service or updating the prl.
Fix
Found a way to get it working on windows 8 x64 you need to Disable Device Driver Signing and install the HTC Diag drivers for windows 7
Code:
Guide:
1. Mouse over the lower-left corner, then select Settings.
2. Select Change PC Settings.
3. Choose General.
4. Scroll to the bottom and select Restart now under the Advanced startup area.
5. Select Troubleshoot.
6. Select Advanced Options.
7. Select Startup Options.
8. Select Restart.
after you install double click on htc usb modem go to modem tab and your port number should be there
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
@Istvan_86,
We should move the discussion for your problem here.
cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.
Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?
Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.
cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.
Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.
What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.
Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html
@clockcycle,
This solution works 100% too. https://www.ubuntu.com/
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!