Related
New device. Odin works, USB storage works, TCP adb works, charging works. Have the latest drivers, which worked fine on the previous device (new device is a closed box warranty replacement). Device shows up in adb devices as "device", but adb freezes when attempting to push or shell. On super rare occasion, I get a shell prompt, but adb freezes immediately. Oftentimes, it shows up as "offline" instead. Have tested numerous cables, numerous USB ports. Reinstalled drivers, reflashed device in odin, reinstalled adb, redownloaded oneclick. Nothing works. Already went through other threads covering the same topic for numerous other devices. What am I overlooking?
Oneclick does not work anymore, not for Gingerbread. Other than that....try and let Windows find and install the drivers from Windows Update.
Sent from my SPH-D700 using xda premium
Meant the tweaked adb in oneclick. I tried to remove the drivers, and let windows search through update, but still no dice. The phone shows up in device manager, is recognized by odin for download mode, and windows as a storage device. However, adb still won't recognize it other than in an offline state.
Sorry if this is a stupid question but you have USB debugging on right?
Sent from my SPH-D700 using xda premium
Launch ddms.bat from \android-sdk-windows\tools
See if the DDMS application recognizes the device there. If not, then you need to enable USB-debugging and/or try different USB ports (but you said you did the latter already). I found that I must use USB ports directly attached to the motherboard for doing anything with my phone.
@kenny: Yup, USB debugging is enabled.
@nikon120: There's no tool dir, but there is platform-tools. There's no ddms in it.
wingbat said:
@kenny: Yup, USB debugging is enabled.
@nikon120: There's no tool dir, but there is platform-tools. There's no ddms in it.
Click to expand...
Click to collapse
Hmm, then I gather you don't have the SDK installed. I was just on SDK revision 10 and the folder was there. I also just uninstalled revision 10 and my older JDK installation to do a fresh install of the latest JDK and Android SDK. The tools folder is in this latest install too.
If odin works, just odin cwm 5.0.2.7, then flash su.zip which roots you.
Sent from my SPH-D700 using Tapatalk 2
nikon120 said:
Hmm, then I gather you don't have the SDK installed. I was just on SDK revision 10 and the folder was there. I also just uninstalled revision 10 and my older JDK installation to do a fresh install of the latest JDK and Android SDK. The tools folder is in this latest install too.
Click to expand...
Click to collapse
My apologies. "tools" was marked as hidden, and not showing during "dir" in command prompt. I did locate and launch ddms.bat. It shows the device as online, but unresponsive. If I close it, and kill-server, and relaunch, it shows the device as offline.
xboxfanj, I already have CWM flashed, and the device rooted, via Odin. What I'm trying to do is use shell/push.
wingbat said:
My apologies. "tools" was marked as hidden, and not showing during "dir" in command prompt. I did locate and launch ddms.bat. It shows the device as online, but unresponsive. If I close it, and kill-server, and relaunch, it shows the device as offline.
xboxfanj, I already have CWM flashed, and the device rooted, via Odin. What I'm trying to do is use shell/push.
Click to expand...
Click to collapse
Oh I see. Reinstall the drivers from samsungs website.
Sent from my GT-P7510 using Tapatalk 2
Why not use adb from the sdk?
Sent from my SPH-D700 using Tapatalk 2
MДЯCЦSДИT said:
Why not use adb from the sdk?
Click to expand...
Click to collapse
I did, it didn't work.
wingbat said:
I did, it didn't work.
Click to expand...
Click to collapse
That's why I inquired whether or not DDMS was recognizing your phone or not. Your reply was that it showed as offline, and that is a good indication as to why adb isn't working for you.
Outside of the phone not having USB debugging enabled, the only other reason I can think of your cause is device drivers for the phone. You said you've already reinstalled the phone drivers and no difference, so you may want to try on another computer or maybe a virtual machine.
1)Unplug the usb and plug it back again.
2)Go to the Settings -> Applications -> Development of your device and uncheck the USB debugging mode and then check it again back!
3)Restart the adb on your PC. adb kill-server and then adb start-server
4)Restart your device and try again.
Hi All:
I have the 16GB N7 (2013) with USB debugging enabled. I plug into my Windows 7 box via USB 2.0, and it successfully appears in my device manager as 'Google Nexus ADB Interface'. I just downloaded the current Android SDK, however when I run 'ADB devices' in the command prompt, ADB does not recognize any devices.
Any ideas?
Thanks!
Did you try if it would recognize your device in fastboot bootloader?
Go into I believe its called SDK manager and make sure USB or Google drivers update is checked and then click Install as this will install all drivers needed. But prior to that uninstall any drivers in device manager for your nexus 7 . it should pick it up right away after everything installs! Good luck
Sent from my Nexus 7 using xda premium
highwaybandit said:
Go into I believe its called SDK manager and make sure USB or Google drivers update is checked and then click Install as this will install all drivers needed. But prior to that uninstall any drivers in device manager for your nexus 7 . it should pick it up right away after everything installs! Good luck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for the suggestion, highwaybandit. I tried your idea, but still have the same issue with ADB not recognizing the device, despite the device showing up successfully in Windows device manager.
I have the same problem with Ubuntu. I tried "adb reboot bootloader" and nothing. Unlocked fine with fastboot tho.
Sent from my Nexus 7 using Tapatalk 2
Username invalid said:
Did you try if it would recognize your device in fastboot bootloader?
Click to expand...
Click to collapse
Yes, and it does. I was able to 'fastboot oem unlock'. However, can't issue any adb commands.
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
Now that you mentioned it, same issue here, in addition to the ADB issue mentioned above. My N7 doesn't show up as a drive whether I have USB debugging enabled or not.
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
mickrg123, I forgot to mention: I've been getting around this issue by using Google Drive. Not as fast as moving files directly, but still a decent workaround until we get this figured out.
mickrg123 said:
My Nexus 7 will not show up as a drive on my computer. Drivers are installed, shows up in device manager fine, uninstalled and re-installed drivers, usb debugging is on. I cant see it has a drive so I can transfer files. Any help would be appreciated
Click to expand...
Click to collapse
If you have USB debugging enabled, the USB IDs change and for some reason windows can't find the MTP drivers for the device.
If you turn off USB debugging, then the phone shows up as an MTP device (ie it shows up as Nexus 7, not a drive letter)
If you want it to show up as a drive letter, you probably need to root and enable USB mass storage, otherwise it will behave as an MTP device (ie it behaves more like an FTP server than a USB hard drive)
If you have USB debugging disabled and it still won't show up on your computer in MTP mode (ie labeled Nexus 7), then you probably have some problem with MTP on your PC.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
ddb540 said:
Hi All:
I have the 16GB N7 (2013) with USB debugging enabled. I plug into my Windows 7 box via USB 2.0, and it successfully appears in my device manager as 'Google Nexus ADB Interface'. I just downloaded the current Android SDK, however when I run 'ADB devices' in the command prompt, ADB does not recognize any devices.
Any ideas?
Click to expand...
Click to collapse
Generally, if it doesn't show up at all with adb devices, then it is probably driver problem, cable problem, port problem, or USB debugging didn't properly get enabled. Although since you say it shows up in device manger, it would seem to show that USB debugging was enabled, so you might want to look at driver, cable, or USB port issues (try USB 2.0 port if you are currently using USB 3.0). You can get updated drivers here:
http://developer.android.com/sdk/win-usb.html
You can force windows to update driver by right clicking on the adb device entry and going through the tabs until you find the update driver button.
If it shows up but says device offline, then it is probably the RSA security introduced into adb/android since 4.2.2 (in which case you should update your platform-tools to 16.0.1 or greater)
Also when I check box to load camera it will show as drive
sfhub said:
If you have USB debugging enabled, the USB IDs change and for some reason windows can't find the MTP drivers for the device.
If you turn off USB debugging, then the phone shows up as an MTP device (ie it shows up as Nexus 7, not a drive letter)
If you want it to show up as a drive letter, you probably need to root and enable USB mass storage, otherwise it will behave as an MTP device (ie it behaves more like an FTP server than a USB hard drive)
If you have USB debugging disabled and it still won't show up on your computer in MTP mode (ie labeled Nexus 7), then you probably have some problem with MTP on your PC.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
Generally, if it doesn't show up at all with adb devices, then it is probably driver problem, cable problem, port problem, or USB debugging didn't properly get enabled. Although since you say it shows up in device manger, it would seem to show that USB debugging was enabled, so you might want to look at driver, cable, or USB port issues (try USB 2.0 port if you are currently using USB 3.0). You can get updated drivers here:
http://developer.android.com/sdk/win-usb.html
You can force windows to update driver by right clicking on the adb device entry and going through the tabs until you find the update driver button.
If it shows up but says device offline, then it is probably the RSA security introduced into adb/android since 4.2.2 (in which case you should update your platform-tools to 16.0.1 or greater)
Click to expand...
Click to collapse
I don't care if doesn't show as drive but doesn't even show as nexus 7 so I can't root until I can load su onto sd card.
Have tried different cables and ports. I heard beep when it connects and shows in menu to to eject nexus 7
Any other ideas?
mickrg123 said:
Also when I check box to load camera it will show as drive
Click to expand...
Click to collapse
If you have USB debugging enabled, then my experience is Media device (MTP) mode won't be recognized because it can't find appropriate drivers (even though you have the MTP drivers installed) but Camera (PTP) mode will still work. I don't think you really mean it shows up as a "drive" as in mass storage device. I think you mean you see a folder where you can access your files.
If you disable USB debugging, than both MTP and PTP should work.
sfhub said:
If you have USB debugging enabled, then my experience is Media device (MTP) mode won't be recognized because it can't find appropriate drivers (even though you have the MTP drivers installed) but Camera (PTP) mode will still work. I don't think you really mean it shows up as a "drive" as in mass storage device. I think you mean you see a folder where you can access your files.
If you disable USB mass storage, than both MTP and PTP should work.
Click to expand...
Click to collapse
Yes you're correct shows as a device not drive when in camera ptp, but not when mtp checked. Where do you disable mass storage?
mickrg123 said:
Yes you're correct shows as a device not drive when in camera ptp, but not when mtp checked. Where do you disable mass storage?
Click to expand...
Click to collapse
Sorry, I meant disable USB Debugging, not mass storage (I'll correct the post)
I'm sure you know where, but if not, Settings->Developer options->USB debugging
If MTP still doesn't work, then see if you have ever gotten MTP to work on the PC (ie another device in MTP mode). If not, look up how to install/reinstall MTP support for your OS version. Windows added it as part of user driver framework and one of the new versions of media player.
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
mickrg123 said:
I don't care if doesn't show as drive but doesn't even show as nexus 7 so I can't root until I can load su onto sd card.
Have tried different cables and ports. I heard beep when it connects and shows in menu to to eject nexus 7
Any other ideas?
Click to expand...
Click to collapse
If your goal is just to load files onto the sdcard, have you tried "adb push"?
You don't need to have the phone visible as a device/folder on the computer to use adb to place files on the tablet.
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
droider137 said:
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
Click to expand...
Click to collapse
1. Plug in nexus 7, MTP mode
2. Open the device manager
3. Right click the nexus 7 > uninstall drivers > unplug
4. Install drivers > http://developer.android.com/sdk/win-usb.html
5. Plug nexus 7 in, drivers will install, should say adb interface
Open up command prompt > nav to your adb folder > adb devices: device number should pop up. Good to go.
droider137 said:
Im having trouble with mine also. Adb sees it when its in normal mode. When I go to bootloader, it is not seen. When i go to unlock, it just says waiting for device. Any ideas???? Updated SDK installed
Click to expand...
Click to collapse
For me, when I rebooted the phone into bootloader mode, it came up with a new USB device "Android Bootloader Interface". I had to point the driver install at the Google USB drivers I had previously used for the ADB interface so that the Bootloader Interface could be recognized.
sfhub said:
For me, when I rebooted the phone into bootloader mode, it came up with a new USB device "Android Bootloader Interface". I had to point the driver install at the Google USB drivers I had previously used for the ADB interface so that the Bootloader Interface could be recognized.
Click to expand...
Click to collapse
Finally got it!! Had to uninstall and re install the drivers a few times and also remove MTP from device manager. Also had to do the same thing and point it to the drivers in both cases. Thanks. Also thanks to teh roxxorz!
droider137 said:
Finally got it!! Had to uninstall and re install the drivers a few times and also remove MTP from device manager. Also had to do the same thing and point it to the drivers in both cases. Thanks. Also thanks to teh roxxorz!
Click to expand...
Click to collapse
No problem guy; glad you're up an flashing.
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
killfire72 said:
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
Click to expand...
Click to collapse
Use another computer if you can.
I had similar problems until I used this version of adb
http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
ashyx said:
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
Click to expand...
Click to collapse
That version of ADB didn't work for me either. Anyway I was able to get fastboot to work but not ADB so I was able to unlock and root and everything through a strange method using only fastboot.
Second question, if I am switching between AOSP roms, say for example CM to PA, can I dirty flash or do I have to reset?
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
xeron72548 said:
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
Click to expand...
Click to collapse
Not so, I and others have ADB working fine on USB 3.0 ports.
The problem is Windows 8 driver signing enforcement blocking the install of drivers. You need to go to advanced startup options to disable it.
Download these drivers first and extract: http://www.mediafire.com/download/i3lcm7dwl581518/ADB_Fastboot_Drivers_Win81.zip
Follow these instructions to disable driver signing enforcement: http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
Once fully booted go into device manager and you should see a device called 'Android 1.0' with an exclamation mark.
Right click 'Android 1.0' then 'update driver software' then 'Browse my computer for driver software'
Click the 'Browse' button and then browse to the driver folder 'ADB_Fastboot_Drivers_Win81' extracted earlier then click next to install the driver.
You will get a warning about unsigned drivers, just ignore and continue.
The drivers should install and you should see a new entry in device manager called 'Android phone' which means the ADB driver is installed.
ADB should now be working.
Thank you so much for this. Have been wondering for a very long time
Sent from my HTC One_M8 using XDA Free mobile app
It sounds like you've got plenty of technical help already, but I will say that I use ADB perfectly fine on my desktop with Win 8.1 so it's possible. I also use hassoon's toolkit occasionally with no issue.
Before I could get the desktop to recognize the M8 I had to completely uninstall all drivers related to my previous galaxy nexus as well as remove any mention of the device in Window's USBdeview. After a reboot, I just plugged in the M8 and windows automatically installed the necessary M8 drivers. I can then run fastboot and adb from the toolkit.
I ended up uninstalling the MSFT USB 3.0 drivers and use the Intel USB 3.0 drivers instead on my Win8.1 laptop that has only USB 3.0 ports. Works great.
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 !!!
I would like to connect ADB to my Mi 5s, but I don't know where to get USB drivers that are safe for download/install?
I need Windows 10 x64 drivers if possible...
Any pointers?
This tool should contain all needed drivers:
http://en.miui.com/thread-281979-1-1.html
Alternatively, if you use the full Android SDK it also contains the needed drivers (open SDK Manager.exe -> Extras -> Google USB Drivers).
I have the SDK installed and could connect with ADB while the mobile was normally running (and Debugging enabled in MIUI) and also while I was in fastboot.
This on Windows 10 x64.
patoberli said:
This tool should contain all needed drivers:
http://en.miui.com/thread-281979-1-1.html
Click to expand...
Click to collapse
This link seems to be for the Mi5 and not for the Mi5S? Doesn't that matter?
Otherwise I'm using Minimal ADB and Fastboot which is working with Google/Samsung Galaxy Nexus mobile phone. But if I try and connect Mi5S and start ADB Deamon running adb devices doesn't return anything.
Got it working. Thanks.
As far as I understood it, Miflash supports all Qualcomm based Xiaomi devices.
You have enabled ADB Debugging on the 5s? It's disabled by default. You have to enable first the developer options and then you can enable it. Here is the latest version of Miflash: http://api.bbs.miui.com/url/MiFlash but the site is down for me at the moment.
Do you see the Mi5s in Device Manager under USB Devices when it's connected?
I haven't installed Miflash, only the full Android SDK and it was automatically detected.
Here an alternative manual: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=409951&pid=7620087
Please note, you don't actually need EDL, but it nicely outlines possible driver issues and fixes.
[edit]
Damn and I wrote now so much text
[/edit]
USB Drivers
Yes, You may search on Google to get.
Xiaomi USB Drivers
Xiaomi USB Drivers For All Devices Download For Free
USB Drivers
literadesign said:
I would like to connect ADB to my Mi 5s, but I don't know where to get USB drivers that are safe for download/install?
I need Windows 10 x64 drivers if possible...
Any pointers?
Click to expand...
Click to collapse
Have you been wasting your time? it might lest you should get it.
Not better even the way has been downloaded by someone.
patoberli said:
This tool should contain all needed drivers:
http://en.miui.com/thread-281979-1-1.html
Alternatively, if you use the full Android SDK it also contains the needed drivers (open SDK Manager.exe -> Extras -> Google USB Drivers).
I have the SDK installed and could connect with ADB while the mobile was normally running (and Debugging enabled in MIUI) and also while I was in fastboot.
This on Windows 10 x64.
Click to expand...
Click to collapse
It take time to run.