IssueTracker

Thank you for this feedback. The team may reach out for more information on triaging or reproducing this issue.

pallavi@ - Have we done any testing on Win7? Looks like this issue should be easily reproducible.

a.sworowska: could you click the "view problem details" button and send us what that shows?

zyy: is there any other useful information about a crash on Windows that's easily available?

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    adb.exe
  Application Version:    0.0.0.0
  Application Timestamp:    34f534d5
  Fault Module Name:    adb.exe
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    34f534d5
  Exception Code:    40000015
  Exception Offset:    00016717
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    7763
  Additional Information 2:    7763cd91f17ba1394e15130ad28436a8
  Additional Information 3:    622c
  Additional Information 4:    622c3aed538ac58f09882fe423edc57a


Also there's a console output: (for adb devices)
List of devices attached
* daemon not running. starting it now at tcp:5037 *
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

We have the same problem at my workplace (computers running with the same configuration).
Changing the port (5037) didn't solve.
We were thinking about a conflict with the company's proxy but we gave up to find a solution as soon as we downgrade to 25.0.3 and understood that the update was responsible of the crash.

>zyy: is there any other useful information about a crash on Windows that's easily available?

One can generate a minidump file on crash, here's instructions (WER part): https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/

Other option would be to integrate Breakpad (https://chromium.googlesource.com/breakpad/breakpad/); it will take much longer but would allow for automatic / user-initiated crash information submission

I did the WER method and generate a dmp file (2 in fact because of the DumpCount set to 2... Should I set it higher ?)
But it is a 40MB file which I can't upload. Any suggestion ?

Thank you so much! You can either archive the dump with 7zip or plain Zip - .dmp files pack really well. Or you could upload it to some file share, e.g. Google Drive, and give a link here. Anything would work

the stack overflow match for "Exception Code:    40000015" says it's what happens when you call abort(3).

that combined with the error message points to this:

    if (adb_socketpair(s)) {
        fatal_errno("cannot open transport registration socketpair");

unfortunately adb_socketpair only writes its failures to the debug log.

i don't think we need a dmp file, but can someone run adb with the ADB_TRACE environment variable set to "all" so we can see the underlying error? we're looking for an error that starts "adb_socketpair:". (and our QA folks did test on Windows 7 but didn't hit this.)

(i'm being deliberately vague about how to set an environment variable on Windows because i assume everyone reading this knows better than i do!)

Output for adb devices (with ADB_TRACE set to "all")

adb I 03-23 09:00:57  3852  6096 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-23 09:00:57  3852  6096 adb_trace.cpp:178] Revision 5943271ace17-android
adb I 03-23 09:00:57  3852  6096 adb_trace.cpp:178]
List of devices attached
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:271] adb_query: host:devices
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:124] _adb_connect: host:version
adb I 03-23 09:00:57  3852  6096 sysdeps_win32.cpp:750] port 5037 type tcp => fd 2048
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:75] readx: fd=2048 wanted=4
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:157] _adb_connect: return fd 2048
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:165] adb_connect: service host:devices
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:75] readx: fd=2048 wanted=4
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:75] readx: fd=2048 wanted=4
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303234 0024
adb I 03-23 09:00:57  3852  6096 sysdeps_win32.cpp:475] adb_close: 2048(lo-client:5037)
adb server version (36) doesn't match this client (39); killing...
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:124] _adb_connect: host:kill
adb I 03-23 09:00:57  3852  6096 sysdeps_win32.cpp:750] port 5037 type tcp => fd 2048
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:101] writex: fd=2048 len=13 30303039686f73743a6b696c6c 0009host:kill
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:75] readx: fd=2048 wanted=4
adb I 03-23 09:00:57  3852  6096 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb I 03-23 09:00:57  3852  6096 adb_client.cpp:157] _adb_connect: return fd 2048
adb I 03-23 09:00:57  3852  6096 sysdeps_win32.cpp:475] adb_close: 2048(lo-client:5037)
adb I 03-23 09:00:59  7704  6108 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-23 09:00:59  7704  6108 adb_trace.cpp:178] Revision 5943271ace17-android
adb I 03-23 09:00:59  7704  6108 adb_trace.cpp:178]
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:827] port 0 type tcp => fd 2048
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:1060] adb_socketpair: bound on port 57887
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:750] port 57887 type tcp => fd 2049
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:945] adb_socket_accept on fd 2048 returns fd 2050
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:1087] adb_socketpair: client and peer sockaddrs don't match
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:475] adb_close: 2048(lo-server:0)
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:475] adb_close: 2049(lo-client:57887)
adb I 03-23 09:00:59  7704  6108 sysdeps_win32.cpp:475] adb_close: 2050(accept:2048(lo-server:0))
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


Is this what you wanted?

Here is mine : (french savage, I'll translate the french part =)   )



Z:\>adb start-server
adb I 03-23 09:39:49  5064  5788 adb_trace.cpp:178] Android Debug Bridge version
 1.0.39
adb I 03-23 09:39:49  5064  5788 adb_trace.cpp:178] Revision 5943271ace17-androi
d
adb I 03-23 09:39:49  5064  5788 adb_trace.cpp:178]
adb I 03-23 09:39:49  5064  5788 adb_client.cpp:124] _adb_connect: host:version
adb I 03-23 09:39:50  5064  5788 sysdeps_win32.cpp:742] could not connect to tcp:5037: cannot connect to 127.0.0.1:5037: Une requ├¬te dÔÇÖenvoi ou de r├®ception de donn├®es nÔÇÖa pas ├®t├® autoris├®e car le socket nÔÇÖest pas connect├® et (lors de lÔÇÖenvoi sur un socket datagramme en utilisant un appel sendto) aucune adresse nÔÇÖa ├®t├® fournie. (10057)
adb I 03-23 09:39:50  5064  5788 adb_client.cpp:165] adb_connect: service host:start-server
* daemon not running. starting it now at tcp:5037 *
adb I 03-23 09:39:50  3088  3320 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-23 09:39:50  3088  3320 adb_trace.cpp:178] Revision 5943271ace17-android
adb I 03-23 09:39:50  3088  3320 adb_trace.cpp:178]
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:827] port 0 type tcp => fd 2048
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:1060] adb_socketpair: bound on port 52137
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:750] port 52137 type tcp => fd 2049
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:945] adb_socket_accept on fd2048 returns fd 2050
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:1087] adb_socketpair: client and peer sockaddrs don't match
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:475] adb_close: 2048(lo-server:0)
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:475] adb_close: 2049(lo-client:52137)
adb I 03-23 09:39:50  3088  3320 sysdeps_win32.cpp:475] adb_close: 2050(accept:2048(lo-server:0))
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon



Translate :

adb I 03-23 09:39:50  5064  5788 sysdeps_win32.cpp:742] could not connect to tcp:5037: cannot connect to 127.0.0.1:5037: A sending or receiving request is not authorize because the socket is not connected and (during the sending on a datagramme socket using a call sendto) no adress given. (10057)

reassigning to jmgao to see if he can work out what's going on here. (i worry that we might have to ask you to run a build that actually prints out the difference between the two sockaddrs. does anyone know whether https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx can trace network operations?)

smudunuri: we'd still be very interested if you can reproduce this.

Tried with the following steps to verify the bug.

OS: Windows 7 SP1 - 64 bit.
Studio Tested: 2.3.0

Followed the below steps.
1. Open studio with platform-tools 25.0.3
2. Go to SDK/Plaform-tools and run "adb devices"
3. Select the update channel in the studio to stable.
4. Update the platform-tools from 25.0.3 to 25.0.4
5. Go to SDK/Platform-tools and run "adb devices"

Updated platform-tools is working well.

I've uploaded a debug build with additional logging to https://drive.google.com/open?id=0B-WZo8dnekVTM3FjV0ZhMmx1MWs (too big to attach to the bug), could you try replacing your adb.exe with this and posting the output it gives?

@smudn : I tried your way... Didn't work

@jm : I don't have access to google drive (and most of the dl sites), is it possible to upload it somewhere else ? Or I'll do it next week.

Yeah, the fastboot we released was from a separate branch.

has anyone been able to try the version of adb in comment #17?

separately, for those who're seeing this: are you on IPv6 networks by any chance?

[Comment deleted]

this also happens to me on windows 10 (OS Build 14393.969) the device i connected was a Lenovo P-70 Android 5.1

although the command that crashed my adb was adb shell

please try the debug build in #17 with ADB_TRACE set to "all", and show us the log output. we can't reproduce this in-house, so we need more information from systems on which it fails.

[Comment deleted]

[Comment deleted]

here is the result from the debug build in comment #17

C:\Users\Loise\AppData\Local\Android\sdk\platform-tools>adb2 -s IBAAWC7S5H5HSGNR shell "echo 'ready'"
adb2 I 03-29 08:36:26  8576  6860 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb2 I 03-29 08:36:26  8576  6860 adb_trace.cpp:178] Revision 47a91c209b6d-android
adb2 I 03-29 08:36:26  8576  6860 adb_trace.cpp:178]
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:124] _adb_connect: host:version
adb2 I 03-29 08:36:26  8576  6860 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:157] _adb_connect: return fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2 I 03-29 08:36:26  8576  6860 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2 I 03-29 08:36:26  8576  6860 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:157] _adb_connect: return fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:245] adb_connect: return fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2 I 03-29 08:36:26  8576  6860 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2 I 03-29 08:36:26  8576  6860 commandline.cpp:762] shell -e 0x7e t=3 use_shell_protocol=false shell_type_arg=pty
adb2 I 03-29 08:36:26  8576  6860 commandline.cpp:762]
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:124] _adb_connect: host:version
adb2 I 03-29 08:36:26  8576  6860 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:157] _adb_connect: return fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:165] adb_connect: service shell:echo 'ready'
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2 I 03-29 08:36:26  8576  6860 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:124] _adb_connect: shell:echo 'ready'
adb2 I 03-29 08:36:26  8576  6860 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:101] writex: fd=2048 len=35 30303166686f73743a7472616e73706f 001fhost:transpo
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:91] Switch transport in progress
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:98] Switch transport success
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:101] writex: fd=2048 len=22 303031327368656c6c3a6563686f2027 0012shell:echo '
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26  8576  6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:157] _adb_connect: return fd 2048
adb2 I 03-29 08:36:26  8576  6860 adb_client.cpp:245] adb_connect: return fd 2048
adb2 I 03-29 08:36:26  8576  6860 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2 I 03-29 08:36:26  8576  9236 commandline.cpp:516] stdin_read_thread_loop(): pre unix_read_interruptible(fdi=0,...)
adb2 I 03-29 08:36:26  8576  6860 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=7
ready
adb2 I 03-29 08:36:26  8576  6860 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2 I 03-29 08:36:26  8576  6860 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=0


answering comment #21 nope not on an ipv6 network

i would like to add that adb install crashes too, here is the log for that

C:\Users\Loise\AppData\Local\Android\sdk\platform-tools>adb2.exe -s IBAAWC7S5H5HSGNR install "C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk
adb2.exe I 03-29 08:39:40  5852  9408 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb2.exe I 03-29 08:39:40  5852  9408 adb_trace.cpp:178] Revision 47a91c209b6d-android
adb2.exe I 03-29 08:39:40  5852  9408 adb_trace.cpp:178]
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:40  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:40  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2.exe I 03-29 08:39:40  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:40  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:40  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2.exe I 03-29 08:39:40  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2.exe I 03-29 08:39:40  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:40  5852  9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:165] adb_connect: service sync:
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:124] _adb_connect: sync:
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=35 30303166686f73743a7472616e73706f 001fhost:transpo
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:91] Switch transport in progress
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:98] Switch transport success
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=9 3030303573796e633a 0005sync:
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=46 53544154260000002f646174612f6c6f STAT&.../data/lo
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=16
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=16 got=16 53544154000000000000000000000000 STAT............
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=42568 53454e442c0000002f646174612f6c6f SEND,.../data/lo
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=8
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=8 got=8 4f4b415900000000 OKAY....
C:\Program Files (x86)\Appium\node_modules\appium\build\se...debug.apk: 1 file pushed. 1.3 MB/s (42500 bytes in 0.031s)
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=8 5155495400000000 QUIT....
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:165] adb_connect: service shell:pm 'install' '/data/local/tmp/settings_apk-debug.apk'
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:124] _adb_connect: shell:pm 'install' '/data/local/tmp/settings_apk-debug.apk'
adb2.exe I 03-29 08:39:41  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=35 30303166686f73743a7472616e73706f 001fhost:transpo
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:91] Switch transport in progress
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:98] Switch transport success
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:101] writex: fd=2048 len=63 303033627368656c6c3a706d2027696e 003bshell:pm 'in
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41  5852  9408 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2.exe I 03-29 08:39:41  5852  9408 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=46
        pkg: /data/local/tmp/settings_apk-debug.apk
adb2.exe I 03-29 08:39:41  5852  9408 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2.exe I 03-29 08:39:42  5852  9408 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=9
Success
adb2.exe I 03-29 08:39:42  5852  9408 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2.exe I 03-29 08:39:42  5852  9408 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=0
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:165] adb_connect: service shell:rm -f '/data/local/tmp/settings_apk-debug.apk'
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:124] _adb_connect: shell:rm -f '/data/local/tmp/settings_apk-debug.apk'
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:101] writex: fd=2048 len=35 30303166686f73743a7472616e73706f 001fhost:transpo
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:91] Switch transport in progress
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:98] Switch transport success
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:101] writex: fd=2048 len=56 303033347368656c6c3a726d202d6620 0034shell:rm -f
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42  5852  9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42  5852  9408 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2.exe I 03-29 08:39:42  5852  9408 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=0
adb2.exe I 03-29 08:39:42  5852  9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)

actually the commands do work as intended, but after the command finishes then the adb crashes, or so windows says "adb.exe has stopped working"

okay, amatsusah2 i'm un-duping your bug because you seem to have an unrelated problem. on the other bug can you show what output you're seeing? also the "problem signature" as in #4 on this bug would be helpful.

Hi, sorry it took so long for me to answer.

I downloaded the adb.exe debug version from #17 comment. Here are results:

for adb start-server
adb I 03-30 09:54:09  3760  9104 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-30 09:54:09  3760  9104 adb_trace.cpp:178] Revision 47a91c209b6d-android
adb I 03-30 09:54:09  3760  9104 adb_trace.cpp:178]
adb I 03-30 09:54:09  3760  9104 adb_client.cpp:124] _adb_connect: host:version
adb I 03-30 09:54:10  3760  9104 sysdeps_win32.cpp:737] could not connect to tcp:5037: cannot connect to 127.0.0.1:5037: ┼╗─ůdanie wys┼éania lub odebrania danych zosta┼éo zablokowane, poniewa┼╝ gniazd
o nie jest pod┼é─ůczone i (podczas wysy┼éania przez gniazdo datagramu przy u┼╝yciu wywo┼éania ÔÇ×wy┼Ťlij doÔÇŁ) nie podano adresu. (10057)
adb I 03-30 09:54:10  3760  9104 adb_client.cpp:165] adb_connect: service host:start-server
* daemon not running. starting it now at tcp:5037 *
adb I 03-30 09:54:10  4928  5472 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-30 09:54:10  4928  5472 adb_trace.cpp:178] Revision 47a91c209b6d-android
adb I 03-30 09:54:10  4928  5472 adb_trace.cpp:178]
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:822] port 0 type tcp => fd 2048
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:1061] adb_socketpair: bound on port 62529
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:745] port 62529 type tcp => fd 2049
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:946] adb_socket_accept on fd 2048 returns fd 2050
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:1086] adb_socketpair: peer sockaddr = 127.0.0.1:62531
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:1091] adb_socketpair: client sockaddr = 127.0.0.1:62530
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:1101] adb_socketpair: client and peer sockaddrs don't match
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:472] adb_close: 2048(lo-server:0)
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:472] adb_close: 2049(lo-client:62529)
adb I 03-30 09:54:10  4928  5472 sysdeps_win32.cpp:472] adb_close: 2050(accept:2048(lo-server:0))
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon


The polish part is as follows:
"The request of sending or receiving data was blocked, because port/socket(?) is not connected and (in the event of sending datagram via port/socekt using command 'send to') the address was not given."
Mind that I translated it myself.

hopefully https://android-review.googlesource.com/#/c/360090/ will address this. we'll have a build with that change for you to try soon...

Hello!
Could you please guide us when fix will be released?
We've faced with same problem with our Win7 machines.

--------------------------------------------------------------------------------
Output of adb from #17 post is:
adb I 04-10 15:24:25  5620  1424 adb_trace.cpp:178] Android Debug Bridge version
 1.0.39
adb I 04-10 15:24:25  5620  1424 adb_trace.cpp:178] Revision 47a91c209b6d-androi
d
adb I 04-10 15:24:25  5620  1424 adb_trace.cpp:178]
adb I 04-10 15:24:25  5620  1424 adb_client.cpp:124] _adb_connect: host:version
adb I 04-10 15:24:26  5620  1424 sysdeps_win32.cpp:737] could not connect to tcp
:5037: cannot connect to 127.0.0.1:5037: ╨Ч╨░╨┐╤А╨╛╤Б ╨╜╨░ ╨╛╤В╨┐╤А╨░╨▓╨║╤Г ╨╕╨╗
╨╕ ╨┐╨╛╨╗╤Г╤З╨╡╨╜╨╕╨╡ ╨┤╨░╨╜╨╜╤Л╤Е  (when sending on a datagram socket using a s
endto call) no address was supplied. (10057)
adb I 04-10 15:24:26  5620  1424 adb_client.cpp:165] adb_connect: service host:s
tart-server
* daemon not running. starting it now at tcp:5037 *
adb I 04-10 15:24:26  6056  5044 adb_trace.cpp:178] Android Debug Bridge version
 1.0.39
adb I 04-10 15:24:26  6056  5044 adb_trace.cpp:178] Revision 47a91c209b6d-androi
d
adb I 04-10 15:24:26  6056  5044 adb_trace.cpp:178]
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:822] port 0 type tcp => fd 20
48
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:1061] adb_socketpair: bound o
n port 64456
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:745] port 64456 type tcp => f
d 2049
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:946] adb_socket_accept on fd
2048 returns fd 2050
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:1086] adb_socketpair: peer so
ckaddr = 127.0.0.1:64458
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:1091] adb_socketpair: client
sockaddr = 127.0.0.1:64457
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:1101] adb_socketpair: client
and peer sockaddrs don't match
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:472] adb_close: 2048(lo-serve
r:0)
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:472] adb_close: 2049(lo-clien
t:64456)
adb I 04-10 15:24:26  6056  5044 sysdeps_win32.cpp:472] adb_close: 2050(accept:2
048(lo-server:0))
error: cannot open transport registration socketpair: Input/output error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon

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

(jmgao starting the process for 25.0.5 this afternoon...)

Project: platform/development
Branch: sdk-release

commit a017eb19b2ca4d5dc8f3fbae22933ffd579ca739
Author: Josh Gao <jmgao@google.com>
Date:   Wed Apr 19 11:32:40 2017

    Update platform-tools version to 25.0.5.
   
    Bug: http://b/37139725
    Bug: http://b/37282612
    Change-Id: I099f0cf9cde7f5fcefcf92420af3f716b5fd3773

M       sdk/plat_tools_source.prop_template

https://android-review.googlesource.com/375778
https://goto.google.com/android-sha1/a017eb19b2ca4d5dc8f3fbae22933ffd579ca739

25.0.5 has just been released: https://dl-ssl.google.com/android/repository/platform-tools_r25.0.5-windows.zip

Gostei

m

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.

Same problem, unable to create a plug-in

Fastboot of post #33 worked for me.

I am connecting directly without a hub.

Not work for me!

#33 fastboot gives me an error: permission denied

How do I now it got fix?

I tried sdk-platform-tool for version 26.0.2, and it cannot work.

Comment #33 works, to make it work : go to your finder : Comman + Maj + G, go to usr/local/bin, replace the old fastboot binaries by the old ones, then go to your terminal and run the command chmod +x ./fastboot.
(instead of ./fastboot, drag and drog the fastboot file from the folder to the terminal after chmod +x)

by the new one*

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?

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?

Yeah, here's the full platform tools zip that has mke2fs alongside fastboot:

Yes, i'm using platform tools 26.0.2, and mke2fs doesn't exit. Thanks for #55 full platform tools zip, it works :)

sdk-repo-darwin-platform-tools-4455170.zip not workin for me.

Same as #57 for me

tried method #8 provided, and even downgrade platform toos to 26.0.1, no lucky.

I cannot unarchive the file from #33 - how can I do that on Mac?

LOL

#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?

The comment #33 + comment #55 worked for me, thanks!

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.

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.

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'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)

#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...

thanks for clarifying the issue with the release notes.

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.)

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?

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.

this bug is for fastboot (which, other than updating the release notes, is fixed.)

https://issuetracker.google.com/70244520 is for adb.

release notes updated: https://developer.android.com/studio/releases/platform-tools.html.

Am I the only one still having this issue even when using the new platform-tools?

Remember to use ./fastboot from the download folder, not simply fastboot.

WOW! I totally forgot the "./" Sorry Mac noob here. It works. Thanks!

How should i install this new platform-tools to use it with just the command fastboot in terminal (without using the platform-tools directory)?

It still doesn't work!

It still doesn't work for me too.

I have the same problem

no devices/emulators found  @-@!

Not working for me either :/

Doesn't work! Please fix it!

#8
#6/
#80

no longer working for me

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

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.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)

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)

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

Hi Google,

are you going to fix that? Thanks! :)

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.

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?! :)

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

same thing here.. :(

same thing here.. :(

Still this error. This is absolutely ridiculous!

I want to know who has been changing and controlling my phone. Thank you, Cristal Gornto.

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

Still Not Working

Is it really that hard to fix this bug for google experts ????
Come on Google do something about it !!!

still does not work :(

sh-3.2# ./fastboot devices
ERROR: Unable to create a plug-in (e00002be)

this is still happening it is not fixed

I have to use a fast boot execute file from like 4 years ago lol

/sdk/platform-tools/fastboot
fastboot version 28.0.0-4797878.it works well

fastbooot command is not working on mac High Sierra

Support only​for​the​future​of​the​same​place​in​USB​debugging​only​to make sure that the product is not the same place as you can imagine​and​be​successful​in​your 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

#2

K

Google map

On Sat, Sep 1, 2018, 2:33 AM <buganizer-system@google.com wrote:

Google Domin

On Sat, Sep 1, 2018, 2:33 AM <buganizer-system@google.com wrote:

#55 Worked for me. Thanks

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

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.

tried another mac, only different with the last post is
OSX Version: 10.14.4 Beta (18E194d)

Same issue. macOS 10.14.4 Build: 18E220a

All you motherfuckers are bitches for hacking my phone

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)

Same issue for me on macOS 10.14.4 (18E226)

Tried multiple versions of fastboot and it has the same issue.

Same problem:

$ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)

macOS: 10.14.4
fastboot:  28.0.2-5303910

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

Exactly same issue on 10.14.4 (18E226)
$ fastboot devices
ERROR: Couldn't create a device interface iterator: (e00002bd)

Have any solutions? Same here in macos 10.14.4.

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?

maybe similar to this? https://forum.mongoose-os.com/discussion/1719/help-connecting-adafruit-huzzah32-to-new-macintosh

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

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

Fixed on any version？

This isn't fixed ... why it's marked with this status :
Status
Fixed

?

10 QT 5602026
Observing the same error while flashing on MAC Sierra ERROR: Couldn't create a device interface iterator: (e00002bd)

android-platform-tools 26.0.1 now does not work on OSX 10.14.5

welp.

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

fastboot version 29.0.0-5611747 - it works)

Unloked

MOSAAD

OBI

All fucking shit off china,delete ittt

Hello easy to you....u get chorme im chorme dev easy so ...no confius again

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