title: Adb complete failure - start/kill-server doesn't work
body: <p>I'm facing a strange issue with adb in that anything related to adb is failing. Before this is marked as a duplicate, I want to say that I have read a bunch of posts and essentially all of them state that you may need to run <code>adb kill-server</code> followed by <code>adb start-server</code>. I have done this and more. </p>
  
  <p>For <code>adb kill-server</code> I get the following log:</p>
  
  <p><code>cannot connect to daemon at tcp:5037: Connection refused</code></p>
  
  <p>For <code>adb start-server</code> I get:</p>
  
  <pre><code>* daemon not running; starting now at tcp:5037
  ADB server didn't ACK
  Full server startup log: 
  /var/folders/_7/rkfglyr552b_ht0cwd140c300000gn/T//adb.501.log
  Server had pid: 1977
  --- adb starting (pid 1977) ---
  adb I 12-18 11:40:26  1977 142946 main.cpp:57] Android Debug Bridge 
  version 1.0.39
  adb I 12-18 11:40:26  1977 142946 main.cpp:57] Version 27.0.0-4455170
  adb I 12-18 11:40:26  1977 142946 main.cpp:57] Installed as 
  {mypath}/Library/Android/sdk/platform-tools/adb
  adb I 12-18 11:40:26  1977 142946 main.cpp:57] 
  adb I 12-18 11:40:26  1977 142946 adb_auth_host.cpp:416] 
  adb_auth_init...
  adb I 12-18 11:40:26  1977 142946 adb_auth_host.cpp:174] read_key_file 
  '{mypath}/.android/adbkey'...
  adb F 12-18 11:40:26  1977 142958 transport_usb.cpp:37] Check failed: 
  usb_packet_size &lt; 4096ULL (usb_packet_size=5120, 4096ULL=4096) 
  
  * failed to start daemon
  error: cannot connect to daemon
  </code></pre>
  
  <p>The main issue is that I cannot run apps on my devices via Android Studio because adb cannot read my devices (both physical devices and emulators). </p>
  
  <p>When I run <code>adb devices</code> or some other adb command like...<code>adb tcpip 5555</code>, for example, I get the same output that I do for <code>adb start-server</code>. </p>
  
  <p>I have also tried:</p>
  
  <ol>
  <li>Ensuring all paths to my sdk and adb in my local.properties file, bash_profile, etc. are consistent.</li>
  <li>Updating Android Studio.</li>
  <li>Updating all my SDKs/platform-tools/etc via the SDK manager.</li>
  <li>Uninstalling/reinstalling the sdk via the Android SDK manager.</li>
  <li>Manually uninstalling the Android SDK and Android Studio and reinstalling.</li>
  <li>Restarting my devices and my machine.</li>
  </ol>
  
  <p>I have never encountered this issue before and the only thing I did before having this problem was update Android Studio Canary. If anyone has any insight I'd appreciate the input. </p>
  
  <p><strong>Edit:</strong> I am running the current version of Java and have been since October, I have used adb successfully many times since then.</p>