Cannot get ADB over USB to Pixelbook to work (on latest builds)

[Brounzer]

Hi all,

I have a question related to the app development we (our company) performs for Android and ChromeOS devices.

The most recent, much welcomed, update to ChromeOS has introduced ADB over USB for a select few models ( https://www.chromium.org/chromium-os/chrome-os-systems-supporting-adb-debugging-over-usb  ). However, I have yet failed to get this to work by connecting my brand new Pixelbook (as of last week) to a Windows 10 machine, and using the guide provided on https://developer.android.com/topic/arc/#adb-usb
I hope any one of you can point me in the right direction. To my best intention, I have followed the provided guide to the letter, twice.

Using hardware:

• Pixelbook with Stable Build 67, and also attempted Dev Channel with build 69.
  
• Connected USB0 (left side) to my Windows 10 laptop USB-A port, but also attempted connecting it to my laptop's USB-C port (so a USB-C to USB-C cable).
  

My steps:

• Powerwashed the Pixelbook
  
• Set Pixelbook to 'Developer Mode', see image:
  
  

• Enable Android Developer Options by going to Settings in ChromeOS, Manage Android --> 7 taps on Build Number and then opening the 'Android Developer Options' and enable ADB Debugging:
  

- Run the setup commands in crosh/shell as described in the guide (link above), such as dev_enable_udc , and dr_swap commands. As stated by the guide on developer.android: "Use this command each time you disconnect and reconnect a USB cable. To ensure your Chromebook is in UFP mode, you can run ectool usbpd <port number>" . See attached:

• Attached the USB-C cable to the W10 laptop and run ADB devices.
  
• No devices show up in cmd (command: adb devices)
  
• Android Studio also does not list any devices to run on.
  
• Note: only when using the USB-C to USB-c cable: This is what I'm seeing in Device Manager, a 'malfunctioning adb device':
  
   
  
  
• When using the USB-C to USB-A cable: I am not seeing a device in Device Manager and neither is Android Studio presenting it as debug target.

Any help would be greatly appreciated if anyone has already managed to the ADB USB to work!

[Brounzer]

Can anyone from the ChromeOS Team perhaps respond on this message?

A word on whether it is indeed not fully functional, is also helpful.

Or otherwise, if someone in possession of a Pixelbook or ADB-USB supported Chromebook may replicate the issue and confirm my findings, I'd also appreciate it.

[Mike Frysinger]

[ +lhchavez ]

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev

[Pyroxian]

I also cannot get this to work. Followed the same steps as you did, but adb devices shows up nothing, and I don't get the prompt to allow debugging on the device.

[David Schreiber-Ranner]

Can't get it to work either. Also the linked documentation on the Android developer pages seems to have changed, and does no longer contain any reference of how to activate adb for the Pixelbook.

[Jeremy Slavitz]

Anyone get this working yet? Really need to get testing on a chromebook soon!

[Mohammed Abushawish]

Same thing for me, nothing appears on the Android Studio nor "adb devices". 

[Khanh LeViet]

Can you try powering on the Pixelbook while connecting it with host computer via USB cable? I was able to make it work that way.

[Andres Santiago]

So you mean:

1. Power Off Pixelbook

2. Connect Pixelbook to development machine via USB

3. Power On Pixelbook

?

[Khanh LeViet]

Yes.

But before step 1, you still need to do finish the preparation as detailed in https://developer.android.com/topic/arc/development-environment#adb-usb 

I've tested with my Mac Pro development machine and connect to Pixelbook via USB-C - USB-C cable.

I haven't verified it on Windows development machine yet.

[Andres Santiago]

Worked like a charm, thanks Khanh!

[Di Liu]

I am using the same steps, but I am trying to connect Macbook Pro USB-A to a Chromebook on ChromeOS version 75 beta. The steps (1. Power Off Pixelbook, 2. Connect Pixelbook to development machine via USB, 3. Power On Pixelbook) didn't work for me. Can ChromeOS team verify if it's necessary to use a USB-C to USB-C cable?