Database Info

[solved] fix for adb on osx!

Ok I think im going crazy, I cant find anything about this.
Im trying to access my tab via ADB in OSX. My Evo works just fine, but I just cant find the gtablet. I see in Windows driver's ini has to be modded to include tegra device ID and vendor ID, but I dont see anything for osx and my device is not getting recognized!
Thanks for your help!
Click to expand...
Click to collapse
Ok so after some time, I just found the solution, I dont know why I need it, and some people didnt but anyway, for whoever is having the same problem as I did, this is the solution!
This steps are assuming you have ADB ready and installed!
First, open terminal (/Applications/Utilities/Terminal.app)
Run the command:
Code:
android update adb
Then you will get a adb_usb.ini file in your $HOME/.android directory. Open that file and you will have the following..
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Add in the 4rth line the following (Device vendor code, this case NVIDIA 0x0955):
Code:
0x0955
Save the file and exit.
On terminal window type
Code:
adb kill-server
and then
Code:
adb start-server
Adb devices should now show up your device!, if by any reason you get "device offline" a re-plug fixed it!
thanks!

damn! bumping this thread, really nothing? I just want to know if anyone can ADB with osx??? Its just me? or what?! thanks

Works fine for me.
OSX is the only OS I've used (so far) to connect to my G-Tablet via ADB.
Make sure USB Debugging is on on the 'pad, and it's Plug and Play. No udev stuff like on Linux, no USB driver issues like on Winhose.
I have had troubles in the past connecting through USB hubs. I'm currently using the front connectors on a Mac Pro.
Just another trivia note on the subject:
adb remount
Works for me on ZPad, it does not on TnT Lite.

I have a hackintosh netbook, but I don't really use it in this space. Nor Windows. Sorry about that.

Linuxslate said:
Works fine for me.
OSX is the only OS I've used (so far) to connect to my G-Tablet via ADB.
Make sure USB Debugging is on on the 'pad, and it's Plug and Play. No udev stuff like on Linux, no USB driver issues like on Winhose.
I have had troubles in the past connecting through USB hubs. I'm currently using the front connectors on a Mac Pro.
Just another trivia note on the subject:
adb remount
Works for me on ZPad, it does not on TnT Lite.
Click to expand...
Click to collapse
Thanks for your reply, so...TnT Lite doesnt work for you?..mh that may be. I have not tried Zpad!
Will keep trying!
roebeet said:
I have a hackintosh netbook, but I don't really use it in this space. Nor Windows. Sorry about that.
Click to expand...
Click to collapse
no worries! Thanks for the reply man!

Fix posted on OP!

[Q] ADB error device not found OSX

Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.

Forgive me for asking the obvious, but do you have USB Debugging enabled?

distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.

Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?

distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try

Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.

distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac

kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).

Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.

distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.

Fastboot devices gave me this output:
serial# fastboot

kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.

distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.

kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.

distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe

kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).

Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck

[Q] Updated to JB, and a few issues started happening...

I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.

BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?

Caduceus46 said:
I updated to Jellybean last night, and was in the process of rooting it and installing CWM again. I plug the pad into my computer, and realized that it's not being recognized by my computer. It's not even charging it! However, when I attach the wire to the wall adapter, it's charging. When I plug it into my comptuer, and if the pad's screen is on sleep, it autowakes it though.
I tried using someone else's cable and the same issue still occurs. Is there a way I can install CWM on my pad and root it without using adb commands on my computer? because that could be my only solution now. Unless, there's a way I can get it to recognize on my computer.
P.S. I had root+CWM installed when I was on ICS.
Click to expand...
Click to collapse
It's a problem that some users have, and in my mind it was not resolved.
But If you want to install your recovery, you can do with TWRP recovery and Terminal Emulator app (play store)
You should search if you can make it by the same process for CWM, apparently no, cause you need fastboot.
Try this : [GUIDE] Help for flash more faster when you use Fastboot Line Command maybe you've got a problem with your fastboot. I don't know.
It's an easy installation of fastboot.

Caduceus46 said:
BUMP.
No one else has this issue? I'm 99% sure its my port, but how can i ota fastboot and flash cwm and root?
Click to expand...
Click to collapse
There is an option to allow ADB over network, but I haven't experimented with it. If you were adventurous, you could try it and let the community know what happens?
In the ROM I'm running (Baked Blackbean #5, Android 4.1.1 and based on CyanogenMOD) you can select this option by going to Settings-->Developer Options--->"ADB over network"
I just attempted to do this, and it worked rather flawlessly. Enable ADB over network, and it will give you the IP address of your device (in my case, 172.16.1.22:5555).
Then, follow the steps below. This assumes you have a rooted device. To do the terminal commands on my tablet, I use the "Terminal Emulator" program, free from the Market.
This is really simple.
First make sure you are rooted. Download a terminal emulator from market (there are lots that are free). Make sure that your android is connected to your WiFi and get the WiFi IP address. Open the terminal program and type:
su
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Now go to your computer (assuming that you are using windows) create a shortcut on the desktop for "cmd.exe" (without the quotations).
Right click on the cmd shortcut and choose "Run as Administrator"
Change to your android-sdk-windows\tools folder
Type:
adb connect ***wifi.ip.address***:5555
(example: adb connect 192.168.0.105:5555)
adb should now say that you are connected. Note: if you are too fast to give the connect command it may fail. so try at least 2 times 5 seconds apart before you say this doesn't work.
Click to expand...
Click to collapse
To put the device back to USB, once you get it working (because ADB over network is NOT SECURE):
And you can disable it and return ADB to listening on USB with
setprop service.adb.tcp.port -1
stop adbd
start adbd
Click to expand...
Click to collapse
Got this information from: Here
I do want to note that all I did was verify that ADB is detected over wifi. When I type 'adb devices' on my Windows 7 PC, it detects the IP address of my tablet, which indicates the two devices are communicating correctly. I didn't try pushing/pulling files since I have no need for that, but hopefully this helps you.

I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:

philos64 said:
I will try next week (cause I'm off @t work) this process, just for seen if it works well.
I don't need it, but it's interesting to know this.
The post which speak about this use is in N1 forum => here -> Post #22.
But it's more complete here : How can I connect to Android with ADB over TCP?
Apps which are automate this process :
- adbWireless - no updated since Sept 5 - 2010 - You need root access
- WiFi ADB - You need root access - Updated September 29, 2012
- ADB WiFi - Updated August 27, 2012 - You need root access
Well done @opethfan89 :good:
Click to expand...
Click to collapse
Thanks!!
Sent from my Transformer Pad TF300T using xda app-developers app

@opethfan89, ADB over network will probably not work for me because I don't have root anymore. Appreciate the help :good:
@Philos64, thank you for your post as well. I will try that sometime this week and let you know the results as well.

Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either

Caduceus46 said:
Oh wait, I don't think that method will work. I will need su permission to flash twrp. I don't have root anymore either
Click to expand...
Click to collapse
Perhaps I'm wrong, but you don't need root to be able to flash a custom recovery, since the recovery operates outside of the Android OS (and root only affects app permissions within the OS). You would just need fastboot to be able to flash the recovery. Do you have the proper drivers installed on your computer? Can you try different USB ports? Maybe a USB hub? Try it on a different computer to, just to process of eliminate any kinks between the tablet and the physical connection of the USB cable.
Sent from my Transformer Pad TF300T using xda app-developers app

[App][Root] ADB Tools

ADB Tools
Easily set how your Mobile is connected to ADB.
Supported Modes
ADB over USB
ADB over WiFi
Starting,Stopping and Restarting the ADB Daemon
Planned Features
Start service on Device Boot
Widget to Toggle Mode
ADB Tools 1.1 Test
Supported Modes
ADB over USB
ADB over WiFi
Starting,Stopping and Restarting the ADB Daemon
Start ADB in Wifi/USB Mode on Device Boot
Enable persistent Wifi Mode.
ADB Tools 1.1 Test 2
Changelog:
Wait for SU Persmission. Exit if SU permissions not Granted.
Improved SU Detection and App StartUp
Better info about what each option does.
Improved Boot Startup service.
Lot of Code Cleanup and Bug Fixes
Click to expand...
Click to collapse
NOTE: This app will not work without root permissions
Download
XDA:DevDB Information
ADB Tools,
Contributors
idragon81
Version Information
Status: Alpha
Created 2014-11-27
Last Updated 2014-11-27

Instructions of usage
ADB Over WiFi
1) Select the ADB Wifi Option and Apply
2) Note the IP Address that is given in the WiFi Info Field. (Usually 192.168.x.x)
3) Open CMD/Terminal and type adb connect 192.168.x.x
4) Voila!! Happy Programming
ADB Over USB
1) Select the ADB USB Option and Apply
2) Connect USB
3) And that's it. Happy Programming =)

great idea , and you thread is in portal , i will try it now, meanwhile where are the links?

Yeah, no download links.

yep no download links???

Sam_in_PGH said:
Yeah, no download links.
Click to expand...
Click to collapse
amit.tiger12 said:
yep no download links???
Click to expand...
Click to collapse
Ctrl + F -> type 'Downloads' !
Profit?
Profit!

Sam_in_PGH said:
Yeah, no download links.
Click to expand...
Click to collapse
amit.tiger12 said:
yep no download links???
Click to expand...
Click to collapse
CobraCommander said:
Ctrl + F -> type 'Downloads' !
Profit?
Profit!
Click to expand...
Click to collapse
DevDB is convoluted as hell to me, but obviously this is what I did.....never seen this crizzap before!:good:

CobraCommander said:
Ctrl + F -> type 'Downloads' !
Profit?
Profit!
Click to expand...
Click to collapse
amit.tiger12 said:
yep no download links???
Click to expand...
Click to collapse
Sam_in_PGH said:
Yeah, no download links.
Click to expand...
Click to collapse
ArjunrambZ said:
great idea , and you thread is in portal , i will try it now, meanwhile where are the links?
Click to expand...
Click to collapse
DOWNLOAD LINK​

Winged_Panther said:
DOWNLOAD LINK​
Click to expand...
Click to collapse
Please don't quote me again..
I found the link.
And for those who quoted me, when I replied there was no download section available.
As per that, I stroked my reply.
So don't quote me again.
Thank you.

Debug
How can I use this to run my application from IntelliJ (AndStudio)!

I have installed this. I have given it root access, I have applied Wifi mode, I have then tried to connect to the IP address in Wifi info but I just keep getting the message that it cannot connect. No problems with USB. Can anyone confirm that it works using wifi?

The question that strikes me is .. how is this different to other tools like adb wireless?
What I am looking for ist a tool that fixes my adb to wireless regardless of a reboot or of a wifi toggle and easily lets me set it back to permanent USB. Haven't found that yet. I can boot with adb wireless with an init.d script but there is not a real simple way to turn that off I want to go back to USB. Maybe that's sort of a brain teaser

Doesn't work!
Settings are dead.
Don't even try this crap, guys.
P.S.: Anyone took a look inside? May be it is some root trojan?

useless
Or you can just open terminal emulator and type:
Code:
su
setprop service.adb.tcp.port 5555
restart adbd
And you can disable it and return ADB to listening on USB with
Code:
su
setprop service.adb.tcp.port -1
restart adbd
PC side:
Code:
adb tcpip 5555
adb connect 192.168.x.x

y2k2r2d2 said:
How can I use this to run my application from IntelliJ (AndStudio)!
Click to expand...
Click to collapse
Android Studio keeps starting up its own instance of ADB. To use this with android studio you need to run adb kill-server and the the adb connect command.
MJD said:
I have installed this. I have given it root access, I have applied Wifi mode, I have then tried to connect to the IP address in Wifi info but I just keep getting the message that it cannot connect. No problems with USB. Can anyone confirm that it works using wifi?
Click to expand...
Click to collapse
Could you please provide more info on your PC OS and your handheld device? I'll look into it.
daniello8 said:
The question that strikes me is .. how is this different to other tools like adb wireless?
What I am looking for ist a tool that fixes my adb to wireless regardless of a reboot or of a wifi toggle and easily lets me set it back to permanent USB. Haven't found that yet. I can boot with adb wireless with an init.d script but there is not a real simple way to turn that off I want to go back to USB. Maybe that's sort of a brain teaser
Click to expand...
Click to collapse
Right now it isn't very different, but I got what you are saying, and that's next on my list.

Revertron said:
Doesn't work!
Settings are dead.
Don't even try this crap, guys.
P.S.: Anyone took a look inside? May be it is some root trojan?
Click to expand...
Click to collapse
Could you let me know what is not working?
valexi said:
Or you can just open terminal emulator and type:
Code:
su
setprop service.adb.tcp.port 5555
restart adbd
And you can disable it and return ADB to listening on USB with
Code:
su
setprop service.adb.tcp.port -1
restart adbd
PC side:
Code:
adb tcpip 5555
adb connect 192.168.x.x
Click to expand...
Click to collapse
It does work the way that you have mentioned, however i didn't find it very convenient to type in those commands everytime i had to develop. It works either way so choose whatever you are comfortable with.

idragon81 said:
Could you please provide more info on your PC OS and your handheld device? I'll look into it.
Click to expand...
Click to collapse
I am using:
GT-i9505
Paranoid Android 4.6-BETA5 (4.4.4)
OS X 10.10.1

Hi.. I'm trying to download the app from my S4 but I can't open the viglink link. Could you send me the original link?

MJD said:
I am using:
GT-i9505
Paranoid Android 4.6-BETA5 (4.4.4)
OS X 10.10.1
Click to expand...
Click to collapse
I'll look into it, I don't know how it works on Mac, can you try using root permissions on Mac if something like this is present,
I'll look into it as soon as my exams are over
peppe130 said:
Hi.. I'm trying to download the app from my S4 but I can't open the viglink link. Could you send me the original link?
Click to expand...
Click to collapse
Link for apk http://forum.xda-developers.com/devdb/project/dl/?id=9961&task=get

this is AWESOME....wireless everywhere=) yikes, can't wait to try it now=)

USB debugging not working properly (on Ubuntu)

Hello,
I just got a new U11, hoping to use it to test/debug my Android apps. But I cannot get it connect to ADB reliably. I have tried everything I could, including
enabling developer options + USB debugging
adb kill-server, adb start-server and adb devices
revoking USB debugging authorizations
authorizing & remembering my PC
I've tried countless combinations of the above, but adb keeps showing unauthorized or offline. Very very occasionally adb shows "connected", but Android Studio freezes when I run my app. When I unplug, Android Studio immediately unfreezes. But again, when I plug my phone it becomes unauthorized/offline.
My other Android phone works without any issues. Is it a bug with the stock firmware?
The phone is running stock European firmware, with everything stock (including locked bootloader).

Could anyone please test/confirm this on their Linux laptop/desktop? Any fixes? Thanks a lot!

Strangely, it works on Windows. Maybe Ubuntu kernel update yesterday broke adb :crying:

I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Sent from my XT1575 using Tapatalk

drzoo2 said:
I get my phone tomorrow and will update adb and try to connect. Have you tried starting the adb server as root?
sudo adb start-server
Click to expand...
Click to collapse
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution

spolarbear said:
Yes, I did all adb commands after $ sudo -s
As it works without any problems on Windows, perhaps I should ask on a Linux forum?
For now I would use Windows until I found a solution
Click to expand...
Click to collapse
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.

microcris said:
I have the same problem.
I have Debian in my computer (MSI GS40 6QE) and in my girlfriend's computer (Asus UX32V) . Same update state in both of them.
I'm unable to use adb or fastboot in my computer but it works correctly in my girlfriend's computer.
Click to expand...
Click to collapse
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.

My Xiaomi running LineageOS (basically AOSP) doesn't have any issue. Perhaps HTC Sense heavily modified some USB options?

spolarbear said:
Haha, at least the issue is not unique to my phone (and laptop) :laugh:
I suspect Android SDK is most well tested on Windows, at least everything is already set up for you. But Linux allows you to run most dev tools in your HOME folder, so they don't mess things up.
Hopefully someone comes up with a fix.
Click to expand...
Click to collapse
I have no problem with my M8 and my computer.
Android "is" Linux. By that, at least, tools like adb and fastboot must be very well tested under Linux :angel:.
Try to open you computer file browser and to browse or copy some files from/to your computer/phone. I'm unable to do that also.
I tried to root my phone in the same day I received it and I was getting really worried because I was unable to use fastboot (I by that I was thinking that my device was defective), even the simple "fastboot getvar all". Then I remembered to switch to another computer and voilà, everything was working perfectly.
Maybe HTC has something broken in the USB3.0 stack.

File transfer and fastboot don't work on my Ubuntu either.

spolarbear said:
File transfer and fastboot don't work on my Ubuntu either.
Click to expand...
Click to collapse
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).

microcris said:
I don't know if it related with kernel (in computer side). I already tried version 4.9, 4.10 and 4.11 (the one I'm running right now).
Click to expand...
Click to collapse
I tried 4.10 and 4.4, neither worked

I have same problem with Windows 10 64Bit.

All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?

I have solved my problem. I have install Windows 10 new and now all working.

Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
What Linux distro/version are you running? I've been trying to get this working with Arch and it's driving me nuts!

I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..

Flinny said:
All working fine here.
Sounds like udev. Have you followed the setting up usb access part of
https://source.android.com/source/initializing?
Click to expand...
Click to collapse
Flinny said:
I run various flavours of Debian and Ubuntu across my machines and have ADB working on them all..
Click to expand...
Click to collapse
Got it working by downloading adb straight from Google instead of using the Arch package.