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.

Yes I just tested and that flag fixes the issue.

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

Yes that is correct.  The  ADB_OSX_USB_CLEAR_ENDPOINTS=1 fixed the issue when I was on previous MacOS version. Do you want me to update to 34.0.1?

(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

Any insights from the logs?

I just upgraded and have the same problem. If I use emulators for debugging everything is fine. When I connect my usb debugging device, Flutter Daemon stops working.

ps. I'm on MacOs Ventura 13.3

UPDATE: I connected my phone with WiFi debugging and using adb connect <ip-address>:<port-number> command, it works. It would appear to be just a USB Debugging issue.

I have the same problem, my mac version is MacOs Ventura13.3. This phenomenon does not occur on all devices, only in certain.

Yes I have also noticed all these things. WiFi debugging works fine when trying to do an ADB install. And it works on 33.0.3.

Since we have a fair number of folks who're impacted, please assist in identifying the active ingredient here:
     - Are you all on Intel Mac host laptops (vs Intel ARM/M1)? If so, please let us know your host kernel version (e.g. 13.3).
     - Since it *appears* that the device-side is also a dependency, please provide the details about the Android device as well (both successful as well as unsuccessful), and any other relevant information (e.g workaround such as 33.0.3, enable the environment variable for 34.0.0 and later).

@do.topevolutions@gmail:
>>If I use emulators for debugging everything is fine. When I connect my usb debugging device, Flutter Daemon stops working.
What's the emulator Android API level (which succeeded)?
What's the physical device API level (that failed)?
Do *all* devices succeed against 33.0.3?

@zhoujianbo1205@gmail:
@nenti1980@gmail:
@christophe.dongieux@gmail:
Please provide additional information for the table below (Intel Mac vs ARM M1 Mac? Macbook kernel version? successfully connected Android version? unsuccessful Android version? Workaround if/any)

@alech@ifit; Host: Intel Mac/i9  formerly 12.6.3 kernel; Successful device:<Android 13?>; Unsuccessful device:<?> Workaround: 34.0.0, 34.0.1 worked with env var setting, 33.0.3 succeeded
@alech@ifit; Host: Intel Mac/i9  upgraded to 13.3 kernel; Successful device:<Android 13?>; Unsuccessful device:<?> Workaround: 34.0.0, 34.0.1 failed, 33.0.3 succeeded
@do.topevolutions@gmail;Host: <Intel Mac? 13.3 Ventura kernel>; Successful device:<emulator Android ver?>; Unsuccessful device:<physical device version: ?> Workaround: <33.0.3 works?>
@zhoujianbo1205@gmail; Host: <Intel Mac?> 13.3 Ventura kernel; Successful device:<Android 13?>; Unsuccessful device:<?> Workaround: <?>
@nenti1980@gmail; Host: <Intel Mac? kernel?>; Successful device:<Android 13?>; Unsuccessful device:<?> Workaround:<?>
@christophe.dongieux@gmail; Host: <Intel Mac? kernel?>; Successful device:<Android 13?>; Unsuccessful device:<?> Workaround: 34.0.0, 34.0.1 failed, 33.0.3 succeeded

The device I have been testing on is Android 9 that has had the issues. In the past it worked on Android 7, though I haven't tested recently. Only workaround I have found for Android 9 after updating to MacOS version 13.3 is using previous platform tools version 33.0.3.

Android

ARM M1 Mac;
Darwin Kernel Version 22.4.0;
Android 9, but different devices with the same version have different connection results.
Currently using adb version 33.0.3 with no issues.

Any updates on this issue?

For the immediate short-term, can you please test out the following:
   $ export ADB_LIBUSB=1
   $ adb kill-server && adb root

I hope you'll be able to get past that IOService error ( "usb_osx.cpp:170] Unable to create an interface plug-in (e00002be)") when attempting to execute `adb install <>`

Am I ok to update to platform tools version 34.0.1 or should I stay on 34.0.0?

We're on track to release 34.0.3 shortly (which includes a fastboot resolution). Meanwhile, yes - you can upgrade to 34.0.1 if you so wish (subject to the workaround above,  if/when you run into the known problem on Intel/Mac).

Ok sounds good. Thank you.

Anything okay

Ok

Ok

Thephong.dthap2023@gmail.com.google.android.play.games&st

It works abspultyely fine after installing mac os venture using open core i faced the issue with adb unable to locate adb or you can say my android device was not detected in android studio after running the commands it works fine.
export ADB_LIBUSB=1
adb kill-server && adb root

ATTN:al...@ifit.com

but @<en...@google.com>
"so in the meantime, there are lots of other more bugs to look at, that we're already convinced are real.

you can make this bug more convincing by trying to work out what the actual variable is --- is it some specific model of mac? is it only some specific macOS versions? android versions? is there anything interesting in logcat?"

   Isn't that your job? I guess someone should get you some type of underling to pick up your slack. I mean, I'm just saying.
                     ..l.. (-_-) ..l..

Latest Mac OS X Ventura 13.5 (22G74) on M2 Macbook (was also reproduced on 2014 Intel Macbook with the latest Big Sur).
Device: moto g6
Android version: 9

The latest adb doesn't work. It hangs for any command like adb install, adb shell, etc.

Workaround:
1. Download older adb from https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip
2. export PATH=~/Downloads/platform-tools:$PATH
3. adb kill-server
4. You may need to reconnect your device

Please fix this bug, it is very annoying.

Do you see the following log entry (in the adb server logs)?
adb E 08-25 08:19:46 97552 2437794 usb_osx.cpp:175] Unable to create an interface plug-in (e00002be)

What version of Android device are you seeing this against?

Can you please try the same workflow (`adb install <apk>`) on a tcpip connection (using `adb connect ip:port`)? yes, you'll need to initially connect over USB but once you establish tcpip connectivity that should get you past this issue (since this's not something that most users encounter, and the underlying root-cause has to do more with Apple than AOSP).

Fix bug report issue my phone app

Did you try resolving the issue with the ADB_LIBUSB env variable set to "1"?

Hi any estimate when the fix will be released? This is impacting a lot our productivity. Even an alpha channel would be helpful

The default for MacOS platforms are already libusb (34.0.5 release, which is the latest downloadable one).
Alternatively, set the env variable mentioned in comment#87

Still having issues on the 34.0.5 release. Now when it hangs we cannot run `adb kill-server` to restart adb and have to kill the process at the OS level.

Release Notes: https://developer.android.google.cn/tools/releases/platform-tools

Is there a solution for this issue yet , still facing the same problems with adb install

>>Now when it hangs we cannot run `adb kill-server` to restart adb and have to kill the >>process at the OS level.

It should *not* hang. If it does, the logs need to be uploaded to an appropriate bug (spanning `adb kill-server` )

@rkoncina@hubspot.com: What's your host platform? Did you try ADB_LIBUSB? Do you have host/server logs? What's your Android kernel version? Do you have hubs in the middle? Can you reliably reproduce this? Assuming you have a fragile infrastructure (host, cables, hubs, test infra), consider switching to ADB_LIBUSB or Wireless transport (if applicable).

---------- Forwarded message ---------
From: <buganizer-system@google.com>
Date: Mon, Oct 16, 2023, 6:42 PM
Subject: Re: Issue 270205252: ADB install not working on Android 9 with
latest platform tools version 34.0.0
To: <b-system+404257552@google.com>
Cc: <schultrodney928@gmail.com>


Replying to this email means your email address will be shared with the
team that works on this product.

https://issuetracker.google.com/issues/270205252

*Changed*
status:  In Progress (Accepted)  →  Fixed

*sh...@google.com <sh...@google.com> added comment #90
<https://issuetracker.google.com/issues/270205252#comment90>:*
https://android-review.git.corp.google.com/c/platform/packages/modules/adb/+/2754050

_______________________________

*Reference Info: 270205252 ADB install not working on Android 9 with latest
platform tools version 34.0.0*
component:  Android Public Tracker > App Development > SDK > platform tools
> adb <https://issuetracker.google.com/components/192795>
status:  Fixed
reporter:  al...@ifit.com
assignee:  sh...@google.com
cc:  al...@ifit.com, ja...@google.com, sh...@google.com, and 3 more
type:  Bug
access level:  Default access
priority:  P2
severity:  S2
blocking:  269001731 <https://issuetracker.google.com/issues/269001731>
duplicate issue:  288902771
<https://issuetracker.google.com/issues/288902771>, 304807297
<https://issuetracker.google.com/issues/304807297>
retention:  Component default



Generated by Google IssueTracker notification system

You're receiving this email because you are subscribed to updates on Google
IssueTracker issue 270205252
<https://issuetracker.google.com/issues/270205252> where you have the role:
starred.
Unsubscribe from this issue.
<https://issuetracker.google.com/issues/270205252?unsubscribe=true>

Follow steps below to capture logs from your Mac M1. Since the failure in your environment occurs over a wide time window, it's important to
identify the approximate timestamp at which you suspect connectivity dropped.

   Host debugging:
   - set ADB_TRACE (dynamic setting)
   - aosp-master$ export ADB_TRACE=all
   - On MacOS, the logs can be found in the directory pointed by the TMPDIR environment variable.
   -$ tail -f /tmp/adb*.log
     adb I 02-08 09:30:25 139670 139670 main.cpp:62] Android Debug Bridge version 1.0.41
     <snip>

    Device-side (adbd) debugging:
    Set trace_mask on
    Restart the daemon and analyze the logs. Caveat is that the device-logs tend to be noisy.
   $ adb shell getprop persist.adb.trace_mask
   1
   $ adb shell setprop persist.adb.trace_mask 0
   $ adb shell pkill adbd
   $ adb shell
   # cd /data/adb
     /data/adb # ls -al
     total 23
     drwx------  2 root   root   3488 2022-02-08 18:04 .
    drwxrwx--x 49 system system 4096 2022-01-18 12:13 ..
    -rw-------  1 root   root   8521 2022-02-08 18:05 adb-2022-02-08-18-04-49-18527
    Error(s) that you may run into, and resolution:
    $ adb shell setprop persist.adb.trace_mask 0
    Failed to set property 'persist.adb.trace_mask' to '0'.
    See dmesg for error reason.
    $ adb root
    $ adb shell setprop persist.adb.trace_mask 0

>>happens on the emulator, usb-C cable (tried 2 different ones, with 2 different original Apple hubs) and on Wi-Fi debugging connection.
FYI, `WiFi Debugging` runs over a different transport therefore it might make sense to open a separate bug for any failure you
experience over that transport. In fact, libusb transport is also distinct from the legacy transport (as far as the possible failure point which is likely USB, is concerned).

One other question: do you experience this failure from adb alone? (if you eliminate Android Studio from this equation)
Studio interacts with the adb server (and is itself the equivalent of the adb client).
If not, the Studio logs are also relevant.

Log/trace instructions are on aosp: https://android-review.git.corp.google.com/c/platform/packages/modules/adb/+/2845056

Keep the rhythm step by step

El mar., 28 de noviembre de 2023 18:33, <buganizer-system@google.com>
escribió:

Very much appreciated but I don't know how to make you leave me alone and quit stalking me for the person at 3958 Madison Street she is not interested in my intruders of my life good luck with it's not due to anything I have done for you to re think what you are embarking on

On Wed, Dec 20, 2023, 02:03 <buganizer-system@google.com> wrote:

henokdegefe@gmail.com 

所以，现在这个bug已经被修复了吗？

Dit not work on my tecno spark 8c

On Sun, Mar 3, 2024, 4:59 AM <buganizer-system@google.com> wrote:

لايتم تثبيت البرنامج او اتطبيقات بشكل اصحيح لان الحزمة لا تقبل يفشل اتثبيت وشكرا

Install all new

حلو

Here's a host log from one of our devices that fails to recognize the attached device (adb devices returns nothing) on ADB 35.0.1

The device is a MacBook Pro M3 with Sonoma 14.5.

I've not been able to find someone to reproduce the indefinite install hang on 35+, yet, but I know we had this in the past (unfortunately without collecting host logs). I'll continue to ask around.