Fixed
Status Update
No update yet.
Comments
il...@google.com
Forgot to mention running platform-tools 26.0.0. And Android "O" public beta
ur...@gmail.com
Not to be "that guy" but is there any update on this? Any additional information needed?
lo...@gmail.com
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
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:
Test: manual
Change-Id: I6074b53a365b8d936610bafea60244f8bba1a33f
M fastboot/usb_osx.cpp
an...@zappos.com
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?
il...@google.com
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
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:
Test: manual
Change-Id: I6074b53a365b8d936610bafea60244f8bba1a33f
(cherry picked from commit f806a3c303028014eec43894386fbfb117667684)
M fastboot/usb_osx.cpp
re...@gmail.com
Thanks for the reminder, I'm kicking off the process now.
ne...@gmail.com
Release process is still churning along, until then I've attached the binary we're planning to release that should work on 10.13.
vi...@gmail.com
Sweet, thanks a bunch!
ma...@gmail.com
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
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
bm...@gmail.com
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
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
an...@backx.org
it not yet fix
il...@google.com
Same error message for me. MacOS 10.13, Platform-tools 26.0.2
mi...@gmail.com
it seems the version attached in
(./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).
(./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).
ev...@willowtreeapps.com
jmgao: did we somehow lose this patch when we fixed the Pixel 2 support bug?
il...@google.com
Yeah, the fastboot we released was from a separate branch.
at...@gmail.com
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.
ERROR: Unable to create a plug-in (e00002be)
How can I fix it?
Thanks for any help.
tt...@appbird.com
Not working here too. Am using 26.0.2 platform tools + completely updated High Sierra on MBP 2017.
tt...@appbird.com
+1 Stil not working on new MBP running High Sierra, with fully updated platform tools 26.0.2
[Deleted User] <[Deleted User]>
+1 Still not working new MBP with latest sdk. This is a P1 for us
ig...@gmail.com
Platform tools 26.0.2 is not working on High Sierra. I rollback to 26.0.1 and it is working well.
mi...@gmail.com
Where can I find 26.0.1?
[Deleted User] <[Deleted User]>
SOLVED: I have downloaded the fastboot file attached in
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.
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.
il...@google.com
Can we get a 26.0.3 revision with the fix? Thanks.
nobody@google.com
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
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:
Test: none
Change-Id: I1849f0df04af390e8aed716262d2be20efdc3491
M sdk/plat_tools_source.prop_template
se...@gmail.com
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
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
il...@google.com
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
de...@gmail.com
Project: platform/development
Branch: master
commit 4592d6f91c24d4cd9f5599c98eebabcb4c3cefcb
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
(cherry picked from commit 2a75ddf513caf9f971dbecd4474094d5c0f8fcb6)
M sdk/plat_tools_source.prop_template
https://android-review.googlesource.com/535055
https://goto.google.com/android-sha1/4592d6f91c24d4cd9f5599c98eebabcb4c3cefcb
Branch: master
commit 4592d6f91c24d4cd9f5599c98eebabcb4c3cefcb
Author: Josh Gao <jmgao@google.com>
Date: Mon Nov 06 13:29:02 2017
Update platform-tools version to 27.0.0.
Bug:
Test: none
Change-Id: I1849f0df04af390e8aed716262d2be20efdc3491
(cherry picked from commit 2a75ddf513caf9f971dbecd4474094d5c0f8fcb6)
M sdk/plat_tools_source.prop_template
il...@google.com
@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.
[Deleted User] <[Deleted User]>
not yet fixed... :(
I hate high Sierra.
I hate high Sierra.
[Deleted User] <[Deleted User]>
Sorry, our platform-tools release is still going through QA. In the mean time, I've attached the binary we're planning to release.
de...@gmail.com
fastboot of #33 works!
ja...@google.com
Can also confirm the fastboot binary in #33 worked.
va...@gmail.com
Does the new release fix also the same problem with adb shell?
ni...@gmail.com
How to use #33 fastboot binary because its not recognized terminal.app
mo...@gmail.com
I'm blocked by this too :(
um...@gmail.com
How to use #33 fastboot binary because its not recognized by terminal.app ? Is this fastboot binary compressed?
ph...@bayfmail.com
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
chmod +x ./fastboot
Then you should be able to execute it:
./fastboot devices
rm...@gmail.com
#########-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
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
finished. total time: 7.613s
ri...@gmail.com
#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.
ag...@gmail.com
Same problem with ADB on high sierra : Unable to create a plug-in (e00002be)
And can't see my tablet.
Both, tablet and usb cable, are working fine on my windows.
And can't see my tablet.
Both, tablet and usb cable, are working fine on my windows.
dt...@gmail.com
Same problem, unable to create a plug-in
[Deleted User] <[Deleted User]>
Fastboot of post #33 worked for me.
mo...@gmail.com
I am connecting directly without a hub.
da...@gmail.com
Not work for me!
iv...@gmail.com
#33 fastboot gives me an error: permission denied
ho...@gmail.com
How do I now it got fix?
[Deleted User] <[Deleted User]>
I tried sdk-platform-tool for version 26.0.2, and it cannot work.
al...@gmail.com
(instead of ./fastboot, drag and drog the fastboot file from the folder to the terminal after chmod +x)
mi...@joyn.de
by the new one*
te...@googlemail.com
Using #32 fastboot binary flash factory image for pixel, ending with
"""
wiping userdata...
/Users/Admin/Library/Android/sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
"""
is this error related to this issue?
"""
wiping userdata...
/Users/Admin/Library/Android/sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
"""
is this error related to this issue?
ro...@gmail.com
Does mke2fs exist in your directory /Users/Admin/Library/Android/sdk/platform-tools/? Not sure which package were you using, the zip file in #28 doesn't have mke2fs. I guess the configuration might be mixing newer fastboot binary with older package that doesn't have mke2fs?
ke...@gmail.com
Yeah, here's the full platform tools zip that has mke2fs alongside fastboot:
ph...@visibacare.com
Yes, i'm using platform tools 26.0.2, and mke2fs doesn't exit. Thanks for #55 full platform tools zip, it works :)
il...@google.com
so...@gmail.com
sdk-repo-darwin-platform-tools-4455170.zip not workin for me.
ad...@gmail.com
Same as #57 for me
ro...@gmail.com
ha...@live.com
tried method #8 provided, and even downgrade platform toos to 26.0.1, no lucky.
mo...@gmail.com
I cannot unarchive the file from #33 - how can I do that on Mac?
ki...@gmail.com
LOL
sh...@gmail.com
#33 works. Just need to replace the fastboot binary in /usr/local/bin.
Getting a similar error in adb
"adb E 12-06 00:49:22 16767 1879237 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)"
Anyway related?
Getting a similar error in adb
"adb E 12-06 00:49:22 16767 1879237 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)"
Anyway related?
mo...@gmail.com
The
il...@google.com
Can someone give a detail instructions or youtube video on how to use this binary in #33 because its not working for a lot of us?
Ive a;lo tried #40 and #63 but in #63. It was no fastboot to replace and still not working even after just putting it in afterward to /usr/local/bin location.
Ive a;lo tried #40 and #63 but in #63. It was no fastboot to replace and still not working even after just putting it in afterward to /usr/local/bin location.
aa...@marinosoftware.com
Install the android sdk as you would normally before High Sierra (e.g. install Android Studio or the android-sdk zip) and make sure the platform-tools package is updated. Then replace the fastboot binary in $ANDROID_HOME/platform-tools/ with the one in #33. Additional instructions to install the SDK are on developer.android.com . `which fastboot` should return a full path to fastboot binary.
am...@gmail.com
Thanks #66, I'll try that now...
I'm used just a adb & fastboot files without installing plateform-tools and that's why I don't have the binary. Plus, I'm using the command ----->
Paste this into Terminal:
touch ~/.bash_profile; open ~/.bash_profile
Paste this into your text editor:
export PATH=${PATH}:/Applications/Android
making it able to use in any folder plus not having to use the command "./" in front.
For others reading, change /Applications/Android to where the files "adb and fastboot" are located.
I'm used just a adb & fastboot files without installing plateform-tools and that's why I don't have the binary. Plus, I'm using the command ----->
Paste this into Terminal:
touch ~/.bash_profile; open ~/.bash_profile
Paste this into your text editor:
export PATH=${PATH}:/Applications/Android
making it able to use in any folder plus not having to use the command "./" in front.
For others reading, change /Applications/Android to where the files "adb and fastboot" are located.
il...@google.com
I've got the latest version, and I'm still facing this error
$ brew cask info android-platform-tools
android-platform-tools: 26.0.2
https://developer.android.com/studio/releases/platform-tools.html
/usr/local/Caskroom/android-platform-tools/26.0.2 (1,831 files, 25.5MB)
$ brew cask info android-platform-tools
android-platform-tools: 26.0.2
/usr/local/Caskroom/android-platform-tools/26.0.2 (1,831 files, 25.5MB)
as...@gmail.com
#68: 27.0.0 is the latest version, downloadable from that link (though the release notes aren't updated yet). if "brew" is giving you an old version, you need to take that up with them...
va...@gmail.com
thanks for clarifying the issue with the release notes.
il...@google.com
below is what i'm suggesting the release notes should say (when it's no longer the weekend and i can get someone to review the change). i'll see about getting "update the platform tools release notes" on the Studio release checklist too, so this doesn't get forgotten in future...
#### 27.0.0 (December 2017)
+ Combines the fastboot fixes from 26.0.1 for macOS 10.13 hosts and from
26.0.2 for Pixel 2 devices.
#### 26.0.2 (October 2017)
+ Add fastboot support for Pixel 2 devices. (But reintroduce the macOS 10.13
fastboot bug fixed in 26.0.1.)
#### 27.0.0 (December 2017)
+ Combines the fastboot fixes from 26.0.1 for macOS 10.13 hosts and from
26.0.2 for Pixel 2 devices.
#### 26.0.2 (October 2017)
+ Add fastboot support for Pixel 2 devices. (But reintroduce the macOS 10.13
fastboot bug fixed in 26.0.1.)
as...@gmail.com
Hi, I'm trying to flash latest Oreo 8.1 on nexus 5x but after ./flash-all.sh return me error e00002be. Debug its enabled on lineage, whats the problem?
jo...@gmail.com
It seems I am having a very similar issue but upgrading to the newest platform-tools or the above provided files did not help.
I have MacOS High Sierra, and after connecting to a device remotely by calling adb connect 192.168.x.x it says "connected to device xxxx:port_number" but after that I cannot see any device connected and "adb devices" returns nothing.
Connecting over USB works just fine.
I have MacOS High Sierra, and after connecting to a device remotely by calling adb connect 192.168.x.x it says "connected to device xxxx:port_number" but after that I cannot see any device connected and "adb devices" returns nothing.
Connecting over USB works just fine.
af...@gmail.com
this bug is for fastboot (which, other than updating the release notes, is fixed.)
https://issuetracker.google.com/70244520 is for adb.
yg...@gmail.com
Am I the only one still having this issue even when using the new platform-tools?
il...@google.com
Remember to use ./fastboot from the download folder, not simply fastboot.
ya...@gmail.com
WOW! I totally forgot the "./" Sorry Mac noob here. It works. Thanks!
[Deleted User] <[Deleted User]>
How should i install this new platform-tools to use it with just the command fastboot in terminal (without using the platform-tools directory)?
al...@gmail.com
It still doesn't work!
lv...@gmail.com
It still doesn't work for me too.
am...@gmail.com
I have the same problem
co...@gmail.com
no devices/emulators found @-@!
vu...@gmail.com
Not working for me either :/
he...@gmail.com
Doesn't work! Please fix it!
ma...@gmail.com
#8
#6/
#80
#6/
#80
ia...@gmail.com
no longer working for me
an...@gmail.com
This issue marked as fixed for SDK Platform tools version 27.0.1.
please provide below info if this issue reproduces again
1. Host operating system version details
2. SDK Platform tools version
3. ./fastboot --version
4. Android device details
please provide below info if this issue reproduces again
1. Host operating system version details
2. SDK Platform tools version
3. ./fastboot --version
4. Android device details
gr...@gmail.com
Still failing for me:
1. OSX version: 10.13.3
2. SDK Platform tools version 27.0.1
3. ./fastboot --version: 0.0.1-4500957
4. Android device: Amazfit Stratos Watch 2, (device enters in fastboot mode but it is not listed using ./fastboot devices)
1. OSX version: 10.13.3
2. SDK Platform tools version 27.0.1
3. ./fastboot --version: 0.0.1-4500957
4. Android device: Amazfit Stratos Watch 2, (device enters in fastboot mode but it is not listed using ./fastboot devices)
ib...@gmail.com
1. OSX version: 10.12.6
2. SKD Platform tools version 27.0.1
3. fastboot versions:
- 27.0.0-4455170
- 9dc0875966c0-android
- 0.0.1-4500957
4. Android device: Amazfit Stratos Watch 2, (device enters in fastboot mode but it is not listed using ./fastboot devices)
2. SKD Platform tools version 27.0.1
3. fastboot versions:
- 27.0.0-4455170
- 9dc0875966c0-android
- 0.0.1-4500957
4. Android device: Amazfit Stratos Watch 2, (device enters in fastboot mode but it is not listed using ./fastboot devices)
so...@gmail.com
OSX version: 10.13.3
SDK Platform tools version 27.0.1
./fastboot --version
fastboot version 0.0.1-4500957
./fastboot devices
- no devices
Android device: ASUS Zenpad Z170C (Android 5.0.1)
SDK Platform tools version 27.0.1
./fastboot --version
fastboot version 0.0.1-4500957
./fastboot devices
- no devices
Android device: ASUS Zenpad Z170C (Android 5.0.1)
gu...@gmail.com
OSX version 10.13.4
platform-tools_r27.0.1-darwin
LG G3 Europe (lg-d855)
fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/toto/Documents/lg/platform-tools/fastboot
Toto:platform-tools toto$ fastboot devices
Toto:platform-tools toto$
(no output)
./adb devices works fine
platform-tools_r27.0.1-darwin
LG G3 Europe (lg-d855)
fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/toto/Documents/lg/platform-tools/fastboot
Toto:platform-tools toto$ fastboot devices
Toto:platform-tools toto$
(no output)
./adb devices works fine
ka...@salesforce.com
Hi Google,
are you going to fix that? Thanks! :)
are you going to fix that? Thanks! :)
il...@google.com
if a device shows up in `adb devices` it won't show up in `fastboot devices` and vice versa. a device can only be in one of the two modes at any given time.
ap...@google.com
Yes, that's right. First we test the device in ADB mode: works.
Then we restart the device in fastboot mode: doesn't work.
Really Google can't solve that issue?! :)
Then we restart the device in fastboot mode: doesn't work.
Really Google can't solve that issue?! :)
ap...@google.com
I'm having the same issue as described above: adb mode success, fastboot failure
OSX 10.13.4 (17E202)
SDK Platform tools version 27.0.1
fastboot version 0.0.1-4500957
OnePlus 3T running Android 8.0.0
OSX 10.13.4 (17E202)
SDK Platform tools version 27.0.1
fastboot version 0.0.1-4500957
OnePlus 3T running Android 8.0.0
ap...@google.com
same thing here.. :(
al...@gmail.com
same thing here.. :(
ap...@google.com
Still this error. This is absolutely ridiculous!
ap...@google.com
I want to know who has been changing and controlling my phone. Thank you, Cristal Gornto.
ap...@google.com
Same thing for me also :(
OSX 10.13.5 (17F77)
SDK platform-tools_r28.0.0-darwin
fastboot version 28.0.0-4797878
Galaxy s6 | Android 7
OSX 10.13.5 (17F77)
SDK platform-tools_r28.0.0-darwin
fastboot version 28.0.0-4797878
Galaxy s6 | Android 7
ap...@google.com
Still Not Working
di...@gmail.com
Is it really that hard to fix this bug for google experts ????
Come on Google do something about it !!!
Come on Google do something about it !!!
je...@gmail.com
still does not work :(
sh-3.2# ./fastboot devices
ERROR: Unable to create a plug-in (e00002be)
sh-3.2# ./fastboot devices
ERROR: Unable to create a plug-in (e00002be)
[Deleted User] <[Deleted User]>
this is still happening it is not fixed
ap...@google.com
I have to use a fast boot execute file from like 4 years ago lol
su...@gmail.com
/sdk/platform-tools/fastboot
fastboot version28.0.0-4797878.it works well
fastboot version
[Deleted User] <[Deleted User]>
fastbooot command is not working on mac High Sierra
ap...@google.com
ap...@google.com
Support onlyforthefutureofthesameplaceinUSBdebuggingonlyto make sure that the product is not the same place as you can imagineandbesuccessfulinyour business with a new one or a long term solution to your problem and the ability to connect with your customers and customers with the best service provider in the world of your business or customer service or service to your company directly from the internet or by phone
ap...@google.com
#2
il...@google.com
K
ap...@google.com
ap...@google.com
ap...@google.com
#55 Worked for me. Thanks
ap...@google.com
Same problem here... fastboot hangs when I give it more than one command:
1. OSX version: 10.14.2
2. SKD Platform tools version: n/a (using fastboot light install)
3. fastboot version:
- 28.0.1-4986621
4. Android device: Nvidia Shield TV
1. OSX version: 10.14.2
2. SKD Platform tools version: n/a (using fastboot light install)
3. fastboot version:
- 28.0.1-4986621
4. Android device: Nvidia Shield TV
ap...@google.com
Similar problem as above here... fastboot gives this error whatever I try (fastboot devices, info, etc):
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
1. OSX version: 10.14.2
2. SKD Platform tools version: n/a (using fastboot light install)
3. fastboot version:
- 28.0.1-4986621
4. android device: anything, does not matter.
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
1. OSX version: 10.14.2
2. SKD Platform tools version: n/a (using fastboot light install)
3. fastboot version:
- 28.0.1-4986621
4. android device: anything, does not matter.
ap...@google.com
tried another mac, only different with the last post is
OSX Version: 10.14.4 Beta (18E194d)
OSX Version: 10.14.4 Beta (18E194d)
ap...@google.com
Same issue. macOS 10.14.4 Build: 18E220a
ap...@google.com
All you motherfuckers are bitches for hacking my phone
ap...@google.com
Same issue on macOS 10.14.4 (18E226)/ADT 28.0.2
Darwin Kernel Version 18.5.0; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64
Every fastboot command returns:
ERROR: Couldn't create a device interface iterator: (e00002bd)
Darwin Kernel Version 18.5.0; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64
Every fastboot command returns:
ERROR: Couldn't create a device interface iterator: (e00002bd)
ap...@google.com
Same issue for me on macOS 10.14.4 (18E226)
Tried multiple versions of fastboot and it has the same issue.
Tried multiple versions of fastboot and it has the same issue.
ap...@google.com
Same problem:
$ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)
macOS: 10.14.4
fastboot: 28.0.2-5303910
$ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)
macOS: 10.14.4
fastboot: 28.0.2-5303910
ap...@google.com
Same issue on 10.14.4 (18E226)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
➜ ~ fastboot --version
fastboot version 28.0.2-5303910
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
➜ ~ fastboot --version
fastboot version 28.0.2-5303910
ap...@google.com
Exactly same issue on 10.14.4 (18E226)
$ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)
$ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)
ap...@google.com
Have any solutions? Same here in macos 10.14.4.
ap...@google.com
macos 10.14.4
fastboot version 28.0.2-5303910
~/Downloads/crosshatch-pq2a.190405.003 ᐅ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
{my_device_id} fastboot
Still seeing the same kernel console output:
`default 22:37:38.850733 -0700 kernel 495549.216174 fastboot@(null): IOUSBUserClientLegacy::start: missing entitlement com.apple.ibridge.control`
I'm guessing not _everyone_ is seeing this, else it'd be a higher sev/pri?
fastboot version 28.0.2-5303910
~/Downloads/crosshatch-pq2a.190405.003 ᐅ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)
ERROR: Couldn't create a device interface iterator: (e00002bd)
{my_device_id} fastboot
Still seeing the same kernel console output:
`default 22:37:38.850733 -0700 kernel 495549.216174 fastboot@(null): IOUSBUserClientLegacy::start: missing entitlement com.apple.ibridge.control`
I'm guessing not _everyone_ is seeing this, else it'd be a higher sev/pri?
ap...@google.com
I am having the same issue with fastboot 28.0.2-5303910 after upgrading to macos 10.14.4 and i also see this in the kernel console
fastboot@(null): IOUSBUserClientLegacy::start: missing entitlement com.apple.ibridge.control
fastboot@(null): IOUSBUserClientLegacy::start: missing entitlement com.apple.ibridge.control
ap...@google.com
This might be a regression because fastboot version 9dc0875966c0-android from android-platform-tools 26.0.1 is working just fine on macOS 10.14.4
bo...@gmail.com
Fixed on any version？
il...@google.com
This isn't fixed ... why it's marked with this status :
Status
Fixed
?
Status
Fixed
?
ap...@google.com
10 QT 5602026
Observing the same error while flashing on MAC Sierra ERROR: Couldn't create a device interface iterator: (e00002bd)
Observing the same error while flashing on MAC Sierra ERROR: Couldn't create a device interface iterator: (e00002bd)
ap...@google.com
android-platform-tools 26.0.1 now does not work on OSX 10.14.5
welp.
welp.
ap...@google.com
Android Debug Bridge version 1.0.41
Version 28.0.3-5475833
Installed as /Users/lengxianfeng/Library/Android/sdk/platform-tools/adb
~/Library/Android/sdk/platform-tools/adb nodaemon server
adb E 06-05 11:10:31 23487 106568 usb_osx.cpp:159] Unable to create an interface plug-in (e00002be)
Terminated: 15
Version 28.0.3-5475833
Installed as /Users/lengxianfeng/Library/Android/sdk/platform-tools/adb
~/Library/Android/sdk/platform-tools/adb nodaemon server
adb E 06-05 11:10:31 23487 106568 usb_osx.cpp:159] Unable to create an interface plug-in (e00002be)
Terminated: 15
al...@gmail.com
Unloked
so...@gmail.com
MOSAAD
em...@gmail.com
OBI
ga...@gmail.com
All fucking shit off china,delete ittt
sh...@gmail.com
Hello easy to you....u get chorme im chorme dev easy so ...no confius again
ar...@gmail.com
Android Debug Bridge version 1.0.41
Version 29.0.4-5871666
Installed as /Users/####/Library/Android/sdk/platform-tools/adb
adb E 10-29 10:24:48 22256 240260 usb_osx.cpp:159] Unable to create an interface plug-in (e00002be)
adb E 10-29 10:24:48 22256 240260 usb_osx.cpp:206] Unable to create a device plug-in (e00002be)
on macOS 10.15
Version 29.0.4-5871666
Installed as /Users/####/Library/Android/sdk/platform-tools/adb
adb E 10-29 10:24:48 22256 240260 usb_osx.cpp:159] Unable to create an interface plug-in (e00002be)
adb E 10-29 10:24:48 22256 240260 usb_osx.cpp:206] Unable to create a device plug-in (e00002be)
on macOS 10.15
bo...@gmail.com
Io
to...@appsfactory.de
If you use 2.4.0-alpha01 and have problems with actionId, switch from "androidx.navigation.safeargs-kotlin" to only "androidx.navigation.safeargs" and adopt to it's changes. The problem with actionId will be fixed in alpha02 soon (see https://issuetracker.google.com/issues/188564435 )
mi...@gmail.com
Thanks for the release!
With the new version, how can I navigate to the destination in another graph? Let's say, I would want to navigate from Title to UserProfile screen in the NavigationAdvancedSample app.
Calling navigate() throws an exception "Navigation action/destination xx cannot be found from the current destination". Is it supported by 2.4.0-alpha01 release?
With the new version, how can I navigate to the destination in another graph? Let's say, I would want to navigate from Title to UserProfile screen in the NavigationAdvancedSample app.
Calling navigate() throws an exception "Navigation action/destination xx cannot be found from the current destination". Is it supported by 2.4.0-alpha01 release?
th...@gmail.com
thank you, the multiple back stacks work well but whenever I switch between fragments with bottom navigation view, my fragments always get attached/detached except the default fragment (the fragment displays when app starts. e.g: HomeFragment). Is this intended? Is there any way to make other fragments persist as well?
il...@gmail.com
I'm also facing a couple of new issues. The first one is related to a transition crash:
java.lang.IndexOutOfBoundsException: Index: 10, Size: 10
at java.util.ArrayList.get(ArrayList.java:437)
at androidx.fragment.app.FragmentTransitionImpl.setNameOverridesReordered(FragmentTransitionImpl.java:182)
at androidx.fragment.app.DefaultSpecialEffectsController.startTransitions(DefaultSpecialEffectsController.java:665)
at androidx.fragment.app.DefaultSpecialEffectsController.executeOperations(DefaultSpecialEffectsController.java:114)
at androidx.fragment.app.SpecialEffectsController.executePendingOperations(SpecialEffectsController.java:294)
at androidx.fragment.app.Fragment$3.run(Fragment.java:2760)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
MaterialContainerTransform is used here.
And the second one is related to a significant performance drop. It seems like the app is almost freezing for a fraction of a second on the bottom navigation stacks swap.
br...@gmail.com
I don't know if this is the best place to report this, but yeah, I am getting occasional crashes in production. Unfortunatelly I am still unable to put my finger on the exact steps to reproduce it, but I hope the stack trace helps, this is the one that is popping more often:
java.lang.IllegalArgumentException:
at androidx.fragment.app.FragmentManager.saveBackStackState (FragmentManager.java:2052)
at androidx.fragment.app.FragmentManager$SaveBackStackState.generateOps (FragmentManager.java:3172)
at androidx.fragment.app.FragmentManager.generateOpsForPendingActions (FragmentManager.java:1953)
at androidx.fragment.app.FragmentManager.execPendingActions (FragmentManager.java:1643)
at androidx.fragment.app.FragmentManager$4.run (FragmentManager.java:480)
at android.os.Handler.handleCallback (Handler.java:883)
at android.os.Handler.dispatchMessage (Handler.java:100)
at android.os.Looper.loop (Looper.java:241)
at android.app.ActivityThread.main (ActivityThread.java:7617)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:941)
I appreciate the work you guys are putting on this, thanks ;)
java.lang.IllegalArgumentException:
at androidx.fragment.app.FragmentManager.saveBackStackState (FragmentManager.java:2052)
at androidx.fragment.app.FragmentManager$SaveBackStackState.generateOps (FragmentManager.java:3172)
at androidx.fragment.app.FragmentManager.generateOpsForPendingActions (FragmentManager.java:1953)
at androidx.fragment.app.FragmentManager.execPendingActions (FragmentManager.java:1643)
at androidx.fragment.app.FragmentManager$4.run (FragmentManager.java:480)
at android.os.Handler.handleCallback (Handler.java:883)
at android.os.Handler.dispatchMessage (Handler.java:100)
at android.os.Looper.loop (Looper.java:241)
at android.app.ActivityThread.main (ActivityThread.java:7617)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:941)
I appreciate the work you guys are putting on this, thanks ;)
il...@google.com
Please always file a new issue instead of commenting on already marked as Fixed bugs.
mi...@iotashome.com
Shouldn't this issue only be closed once the issue is out of alpha and "in production"? Seems like filing new bugs while a new feature is in alpha isn't the best idea.
il...@google.com
Re #150 - no, please always file a new issue. That way each issue can be triaged separately for the appropriate release and deduped against one another.
dh...@bacancy.com
Any recent updates for bottom navigation's multiple back stack maintenance issue like while using system back button the home fragment does not keep that last opened fragment in it. And also the other fragment in the bottomnav other than "home" fragment are still always reloads which actually should persist their state like home option.
lk...@gmail.com
Any new updates for the issue of "The other fragments in the bottomnav other than "home" fragment are still always reloads which actually should persist their state like home option." ?
ph...@gmail.com
The enter animation always rerun when I switch to other tab. Is it possible to disable it?
sa...@google.com
Re #154: Please file a separate issue so we can more appropriately track your issue.
ph...@gmail.com
am...@gmail.com
What if I don't want to use popUpTo() and want to keep my bottomNavBar stack growing?
Is it too crazy to ask for a backstack in each destination? - The destination itself will have its own backstack without the need to save/restore. Soon as the destination is visible/active it will query its internal Backstack and present the proper child screen it host. That will make a lot easier to design Apps like Instagram, which is probably the reason why many of us are here.
Description
- scroll position should be maintained between tabs
- pressing the tab again should reset its' backstack and scroll
- pressing back should go back in the current tab's backstack and then exit the app (it should not switch between tabs)
- each tab should have it's own backstack
(I am not sure which parts of this are already implemented, but the scroll/backstack support isn't there)."