Hi,
did anyone find a USB driver for ADB / Fastboot for the Pixel C?
latest_usb_driver_windows.zip from Google seems to be from 2014, the .inf file within has Nexus One / S / 7 / Q and some, but no Pixel C.
USB VID is 18D1, PID is 5203.
Thanks,
Robert
That 2014 one should work for you.
I used it (Android Composite ADB Interface) with ADB and Fastboot to unlock my bootloader and it worked fine.
Just have to manually select it from the list in the device manager.
Related
Hi guys !
I've got a problem to install Pixel C fastboot driver. i followed this thread : [GUIDE] Unlock Bootloader, Install Custom Recovery, and Root the Pixel C (2/4/2016) but i still doesnt work.
I try to install adb and fastboot driver with Wugfresh's Nexus Root Toolkit, then with the Google Drivers. I also intall the android SDK. But it's still not working! My device works with adb, i can see it, but not with fastboot, im stuck on the pixel c screen "Waiting to fastboot command", and when i try to do something, the program loop (search for devices). I even try to install ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3, but it's not working too.
Of course, EOM is unlocked and USB debbuging is active. I'm on windows 10 64bits. I'm running out of solution.
Thank for your help guys, ans sorry for my english !
If you're running Windows, make sure the drivers for fastboot are installed, for some reason they don't automatically install for me on Windows 10 and I have to manually install them.
Sent from my Nexus 6 using Tapatalk
I had the same issue. I had to disable driver verification in advanced startup.
I had many troubles unlocking and rooting the device, too.
Finally, this worked for me...
(My system is Windows 7 in a Parallels VM, why shouldnt this work on Win 10 too.)
First, I had to edit the driver files (used that from SDK), so Windows recognize it as Pixel C.
Here the link to the guide I found:
http://stackoverflow.com/questions/34775508/where-is-adb-driver-for-the-pixel-c
Now ADB is working.
The next problem was, that the Pixel C wasnt recognized in fastboot mode.
So there was an unknown device with a yellow triangle, in Windows Device Manager.
After awhile of "research" I found out, that I had to assign the driver manually.
What I did was (my Windows is in german, so dont know the exact english labels):
right click on the device
update driver
search for driver on the computer
now you dont point to the driver directory, instead choose "choose from a list of device drivers" (hope this translation is roughly right =) )
from there choose "Android Device" and then "Android Bootloader Interface".
This worked for me.
The last troublemaker was root.
The root guide in the General section worked, except for copying su.img to /data.
In TWRP ADB didnt work, so i had to copy it with the TWRP file manager (if another one has problems with this)...
Now everythings seems to work...
Try just the SkipSoft tool within XDA Pixel C forums. They have a driver section which may help. I had to use PDANet to get ADB to work.
Hi guys, im back again !
Just wanna thank you all for your help, especially WhatZitT00ya who find out how to resolve this (assign the driver manually).
Thanks guys !
::EDIT::
OK Problem Solved. Thanks to PKelly517 for pointing me in the right direction.
So I'm on Windows 10 and had all drivers updated. Device Manager showed Pixel C under portable devices and ADB worked BUT when in Fastboot mode it would not recognize the Pixel C and under Device Manager it showed up as Unknown Device. Trying to install drivers resulted in an error stating "The Third-Party INF Does Not Contain Digital Signature Information."
This is the steps I took to get Fastboot working.
1. Hold Shift and Restart PC.
2. In the following screen: Went to Advance Options > Startup Settings > Restart.
3. Upon restarting, chose the options "Disable Driver Signature Enforcement."
4. Reinstall drivers under Device Manager while in Fastboot mode.
Fastboot mode is recognized after that. Hopefully this could help anybody else having similar issues.
______________________________________________________________________________________________
I'm running on Android 7.0.0 NRD90R and I've searched this entire forum on ADB/Fastboot problems not working on the Pixel C and none of the threads seem to solve my problem. I can see my device in ADB but when I go into Fastboot mode the device is no longer recognized and commands cannot be issued.
I have installed all the updated drivers, the Pixel C comes up under Portable Devices in Device Manager, and when I use the Nexus Root Toolkit 2.1.9 to unlock the bootloader it gives me this:
adb devices
5C08000604 device
fastboot devices
Checking OEM Unlockable Status:
+ Status: Allowed
Checking ADB/FASTBOOT Connectivity
adb devices
5C08000604 device
fastboot devices
+ ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
Retrying.. Checking Fastboot Connectivity
fastboot devices
I've tried using SkipSoft Drivers and that too, doesn't recognize my device in Fastboot mode. Any help would be appreciated. I've spent hours trying to get Fastboot working and I've just about had it with this damn device.
@chob0,
Is your Android SDK up to date?
cam30era said:
@chob0,
Is your Android SDK up to date?
Click to expand...
Click to collapse
Yes, I've installed all the updated drivers including the Android SDK but still not recognized in Fastboot.
chob0 said:
Yes, I've installed all the updated drivers including the Android SDK but still not recognized in Fastboot.
Click to expand...
Click to collapse
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
cam30era said:
@chob0,
Is your Android SDK up to date?
Click to expand...
Click to collapse
pkelly517 said:
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
WOW THANK YOU SO MUCH! I can't believe it was something so simple. I checked device manager before and it had shown up as Pixel C but never while I was in Fastboot mode.
chob0 said:
WOW THANK YOU SO MUCH! I can't believe it was something so simple. I checked device manager before and it had shown up as Pixel C but never while I was in Fastboot mode.
Click to expand...
Click to collapse
Glad I could help.
The fact that it was JUST the Pixel C ONLY in fastboot was the weird part.
I think I spent more time trying to understand how to update the driver than I did discovering the problem. It looks like it was the opposite for you. Enjoy the weekend.
Sent from my Pixel C using Tapatalk
You saved me a lot of stress trying to figure this out. Thanks.
pkelly517 said:
Check device manager while in fastboot. I bet you have a yellow triangle.
In Windows 10 I had to do some pre boot shenanigans to enable unapproved drivers (or something like that). Once that was done, I was able to update the Google driver. It was only the Pixel C in fastboot that gave me the problem. Bullhead and deb gave me no problems.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
So I uninstalled all of the previous Samsung/Koush/Intel Android USB drivers for and downloaded SDK Google USB driver. But I can't get adb to work - when I connect the phone, it says Pixel XL under Portable Devices in Device Manager (Win 7.) I can transfer files, but ADB just won't work.
I used some Intel and Koush Android ADB Device drivers previously, and the Google Nexus ADB device did appear in Device Manager, but adb was still a no go.
Does anyone know how to fix this?
Thanks.
Just to make sure, you did enable adb debugging in developer options, right? When you connect the phone to your computer, are you choosing the transfer files option? What is showing up in device manager?
skaforey said:
Just to make sure, you did enable adb debugging in developer options, right? When you connect the phone to your computer, are you choosing the transfer files option? What is showing up in device manager?
Click to expand...
Click to collapse
I enabled debugging in developers options.
I tried most of the settings - charging, file transfer, ptp.
When I connect the phone, only one thing appears - Pixel XL under Portable Devices.
I can transfer files as mtp and ptp.
I can also update the driver for Pixel XL and force Google Nexus ADB driver (I believe it comes from something like 2013-2014 USB driver package by Koush.) When I do that, Pixel XL disappears and Android ADB device replaces it under Android Devices. But ADB still doesn't work, when I do adb devices - nothing shows up.
I can also update this driver with a current Google USB driver from the latest android SDK. I think it's version 11. When I do this, Android ADB device gets replaced with Pixel XL under Portable Devices. Still no adb.
I have updated Java SDK, I have updated Windows 7. I spent literally 4-5 hours on this, and I can't figure it out.
When you see it as adb under device manager, try removing the driver by right clicking and uninstall. Unplug the device and replug it in. Then make sure it's using the newest SDK driver, that's what worked for me.
Tried a different computer. Adb worked as soon as I installed the 15 seconds adb installer.
There's something wrong with my main computer. I already tried uninstalling and reinstalling the driver - it just doesn't work - every time the device is recognized as mtp usb device.
Any tips would be greatly appreciated!
nabbed said:
Any tips would be greatly appreciated!
Click to expand...
Click to collapse
Erase every adb and fastboot folder you have and download android SDK and reinstall platform tools
nabbed said:
Any tips would be greatly appreciated!
Click to expand...
Click to collapse
You could try using the adb minimal with fastboot at the xda link below. It was updated on 10-22-16 this is what I use.
http://forum.xda-developers.com/showthread.php?t=2317790
Does anyone know where to find official Nokia drivers for this phone so that I can connect to it via ADB? If an official one doesn't exist, are there other options? Thanks!
I have the same problem
When I plug mine Ito the PC, I get an autoplay popup (win 7) for a CD ROM drive. Open the drive and there is a setup.exe that should install the usb driver.
I already have an existing ADB setup on my PC so after doing the driver install the ADB commands work
You will need to set the developer options in setup and set usb debug as well.
HTH
Sooo...I'm a moron. It was the ADB version I was using. I grabbed the latest version of the Android platform tools and everything worked swimmingly.
With Google Android SDK USB drivers (usb_driver_r13-windows.zip from 'Get the Google USB Driver') installed on a Windows PC, the platform-tools adb command can comunicate with the phone when it's in the Android system.
However, after booting into fastboot, the platform-tools fastboot command cannot communicate with the phone.
Does fastboot only work with the USB drivers installed by the miflash utility?
Or does it work with different drivers from Google or Qualcomm? If so, where to download them from?
There are countless sources claiming to be the Qualcomm drivers, but they are not authoritative.
Qualcomm puts all its downloads behind a login, but even after joining the Qualcomm developer network, I still couldn't find the drivers on there.
Gigajules said:
With Google Android SDK USB drivers (usb_driver_r13-windows.zip from 'Get the Google USB Driver') installed on a Windows PC, the platform-tools adb command can comunicate with the phone when it's in the Android system.
However, after booting into fastboot, the platform-tools fastboot command cannot communicate with the phone.
Does fastboot only work with the USB drivers installed by the miflash utility?
Or does it work with different drivers from Google or Qualcomm? If so, where to download them from?
There are countless sources claiming to be the Qualcomm drivers, but they are not authoritative.
Qualcomm puts all its downloads behind a login, but even after joining the Qualcomm developer network, I still couldn't find the drivers on there.
Click to expand...
Click to collapse
I always use the so-called Minimal ADB and Fastboot package (search by Google).
Starting from that it will further download additional drivers (when phone is connected in Android or in Fastboot mode - PC must be on Internet)
But you may have problems (preventing to recognize the phone in Fastboot) with your USB cable or USB port on the PC or even with some previously installed drivers - Windows wrongly recognize and try to use a previously installed driver instead and then it doesn't work in Fastboot
To clean up the previously installed USB drivers from the particular USB ports you may use USB Deview (google for, it's been couple of years ago when I had to use it last time)
Again, countless links to 'Minimal ADB and Fastboot package' downloads from untrustworthy sources such as dropbox, droidfilehost etc,
But anyway it was not necessary. Thank you for the suggestion to clean the device. I think the Google Android SDK USB drivers contains the bootloader driver, it just wasn't installed. The device manager just needed a nudge.
To recreate the issue...
Connect the phone to the PC via USB
In Windows, go to the Device Manager.
When the phone is in Android system, it is shown in the device tree as...
Android Device > Android Composite ADB Interface
...but when the phone is in fastboot, it is shown in the device tree as...
Other devices -> Android
...with an exclamation mark over the Android device to indicate it is not working.
To fix the problem...
In Device Manager, find...
Other devices -> Android
Right click Android, and select Properties.
In the General tab, click Change Settings. At the UAC prompt, log in with an Administrator account.
In the Driver tab, click Update Driver > Browse my computer > Let me pick from a list of available drivers on my computer > Android Device > Android Bootloader Interface > When 'Update Driver Warming' is displayed, click 'Yes'
Shows: Windows has successfully updated your drivers.
Driver properties now shows: Driver provider: Google, Inc
The phone shows in the device tree as:
Android Device > Android Bootloader Interface
Now Android platform tools fastboot commands work.
Gigajules said:
Again, countless links to 'Minimal ADB and Fastboot package' downloads from untrustworthy sources such as dropbox, droidfilehost etc,
But anyway it was not necessary. Thank you for the suggestion to clean the device. I think the Google Android SDK USB drivers contains the bootloader driver, it just wasn't installed. The device manager just needed a nudge.
To recreate the issue...
Connect the phone to the PC via USB
In Windows, go to the Device Manager.
When the phone is in Android system, it is shown in the device tree as...
Android Device > Android Composite ADB Interface
...but when the phone is in fastboot, it is shown in the device tree as...
Other devices -> Android
...with an exclamation mark over the Android device to indicate it is not working.
To fix the problem...
In Device Manager, find...
Other devices -> Android
Right click Android, and select Properties.
In the General tab, click Change Settings. At the UAC prompt, log in with an Administrator account.
In the Driver tab, click Update Driver > Browse my computer > Let me pick from a list of available drivers on my computer > Android Device > Android Bootloader Interface > When 'Update Driver Warming' is displayed, click 'Yes'
Shows: Windows has successfully updated your drivers.
Driver properties now shows: Driver provider: Google, Inc
The phone shows in the device tree as:
Android Device > Android Bootloader Interface
Now Android platform tools fastboot commands work.
Click to expand...
Click to collapse
Ofc that Google's SDK should contain drivers but I suggested Minimal.. since I always use them and it's the minimal/smallest package (as the name says, and self-contained) to download and install
Btw, there is a thread on XDA for Minimal..., that should be trustworthy I think
Anyway, it's important that it works now for you. And problem is usually with some mess on the PC with previous drivers
USB Deview is small, easy to use and powerfully tool for cleaning the old drivers that have been installed who knows when in the past
zgfg said:
Btw, there is a thread on XDA for Minimal..., that should be trustworthy I think
Click to expand...
Click to collapse
Thanks, found it here: https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
The latest version minimal_adb_fastboot_v1.4.3_setup.exe, is 1mb, dated is Feb 2018, hosted on androidfilehost.com.
I guess Google's platform-tools_r33.0.1-windows.zip supercedes it, it's a little bigger at 6mb, but it's portable, so doesn't require any Administrator access to install, and provenance it clear.