IssueTracker

Forgot to mention running platform-tools 26.0.0. And Android "O" public beta

Not to be "that guy" but is there any update on this? Any additional information needed?

Project: platform/system/core
Branch: master

commit f806a3c303028014eec43894386fbfb117667684
Author: Josh Gao <jmgao@google.com>
Date:   Fri Aug 18 18:25:44 2017

    fastboot: gracefully handle failure to open a USB device on OS X.
   
    High Sierra restricts opening some USB devices (e.g. the touchbar)
    to processes that have specific entitlements. Ignore devices that we
    can't open.
   
    Bug: http://b/64292422
    Test: manual
    Change-Id: I6074b53a365b8d936610bafea60244f8bba1a33f

M       fastboot/usb_osx.cpp

https://android-review.googlesource.com/461857
https://goto.google.com/android-sha1/f806a3c303028014eec43894386fbfb117667684

Since OSX 10.13 is being released the 25th of September (in 5 days as of writing), is it possible to create a new Android Platform Tools release, so the impact can be as low as possible?

Project: platform/system/core
Branch: sdk-release

commit 73f4670f380679ba5e6081968ba7ea992edf51b9
Author: Josh Gao <jmgao@google.com>
Date:   Fri Aug 18 18:25:44 2017

    fastboot: gracefully handle failure to open a USB device on OS X.
   
    High Sierra restricts opening some USB devices (e.g. the touchbar)
    to processes that have specific entitlements. Ignore devices that we
    can't open.
   
    Bug: http://b/64292422
    Test: manual
    Change-Id: I6074b53a365b8d936610bafea60244f8bba1a33f
    (cherry picked from commit f806a3c303028014eec43894386fbfb117667684)

M       fastboot/usb_osx.cpp

https://android-review.googlesource.com/489920
https://goto.google.com/android-sha1/73f4670f380679ba5e6081968ba7ea992edf51b9

Thanks for the reminder, I'm kicking off the process now.

Release process is still churning along, until then I've attached the binary we're planning to release that should work on 10.13.

26.0.1 is live: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

Sweet, thanks a bunch!

I think i still have this issue
MacBookPro13,3 (late 16" touchbar)
macOS 10.13 (17A405)
fastboot version 4022467

bnaya@bmbp ~ $ fastboot --version
fastboot version -4022467
Installed as /Users/bnaya/Library/Android/sdk/platform-tools/fastboot
bnaya@bmbp ~ $ fastboot devices
ERROR: Unable to create a plug-in (e00002be)

Sudo didn't help

More info:
when starting adb i see this message
bnaya@bmbp platform-tools $ adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
adb E 10-28 17:42:35  1657 37964 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)
* daemon started successfully *
LGH815***       device

it not yet fix

Same error message for me. MacOS 10.13, Platform-tools 26.0.2

it seems the version attached in comment#8 actually works on MacOSHighSierra,
(./fastboot version 9dc0875966c0-android ) , but the one (version -4022467) included in 26.0.2 tools release, does not work (it reports the same bug)

I've just flashed fine with the provided version (9dc0875966c0).

jmgao: did we somehow lose this patch when we fixed the Pixel 2 support bug?

Hi, I have a similar issue. I tried to download the latest platform-tools with fastboot version -4022467 but it still tells me:

ERROR: Unable to create a plug-in (e00002be)

How can I fix it?

Thanks for any help.

Not working here too. Am using 26.0.2 platform tools + completely updated High Sierra on MBP 2017.

+1 Stil not working on new MBP running High Sierra, with fully updated platform tools 26.0.2

+1 Still not working new MBP with latest sdk. This is a P1 for us

Platform tools 26.0.2 is not working on High Sierra. I rollback to 26.0.1 and it is working well.

Where can I find 26.0.1?

SOLVED: I have downloaded the fastboot file attached in comment #8 above. Then I have replaced it in the platform-tools folder in sdk and now fastboot works again in High Sierra. I can confirm that the newer version in 26.0.2 does not work as the fixed version in comment #8. NOTE: if the downloaded file has the .dms extension just remove it. It worked for me.

NEW PROBLEM: I think that a similar problem is in the adb because when I issue adb shell I receive the following error:

adb E 11-05 17:05:17   601 15446 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)

Different from the fastboot in platform-tools 26.0.2, adb works despite this error.

Can we get a 26.0.3 revision with the fix? Thanks.

Project: platform/development
Branch: sdk-release

commit 2a75ddf513caf9f971dbecd4474094d5c0f8fcb6
Author: Josh Gao <jmgao@google.com>
Date:   Mon Nov 06 13:29:02 2017

    Update platform-tools version to 27.0.0.
   
    Bug: http://b/64292422
    Test: none
    Change-Id: I1849f0df04af390e8aed716262d2be20efdc3491

M       sdk/plat_tools_source.prop_template

https://android-review.googlesource.com/529912
https://goto.google.com/android-sha1/2a75ddf513caf9f971dbecd4474094d5c0f8fcb6

fastboot version -4022467
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android

I install the latest platform-tools via homebrew
I test on my 2016 MacBook Pro 15' with macOS 10.13.1
fastboot still can't work normally

26.0.1

https://dl.google.com/android/repository/platform-tools_r26.0.1-darwin.zip

What's the solution for someone with a Pixel 2 on High Sierra? 26.0.1 works, however 26.0.2 says it's a fix for Pixel 2, so don't want to break anything using .1

@29: yeah, sorry for the mess. 26.0.1 works on Mac OS 10.13 but doesn't know about the Pixel 2's extra partitions. 26.0.2 knows about the Pixel 2's extra partitions but doesn't work on Mac OS 10.13. We have 27.0.0 going through QA at the moment that will fix both issues. (Linux and Windows are unaffected: 26.0.2 should be fine for them.) we're also addressing the over-complicated process (too many branches!) that led to this mistake in the first place.

not yet fixed... :(
I hate high Sierra.

Sorry, our platform-tools release is still going through QA. In the mean time, I've attached the binary we're planning to release.

fastboot of #33 works!

Can also confirm the fastboot binary in #33 worked.

Does the new release fix also the same problem with adb shell?

How to use #33 fastboot binary because its not recognized terminal.app

I'm blocked by this too :(

How to use #33 fastboot binary because its not recognized by terminal.app? Is this fastboot binary compressed?

After downloading the binary on OSX, you need to run the command:
chmod +x ./fastboot

Then you should be able to execute it:
./fastboot devices

#########-MacBook-Pro:platform-tools #####$ ./fastboot flashing unlock
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
finished. total time: 7.613s

#41: are you using a direct cable from laptop to device, or going via a USB hub? I've seen problems with some hubs before.