Scribd Logo
Upload

Welcome to Scribd!

  • 4 views

    Untitled

    Uploaded by

    Huzaifah Shaheed
    The document contains log entries from an Android device related to discovering and connecting to an ADB over Wi-Fi device. It records the device finding an ADB service on its local network with a specific name, IP address, and port numbers for the TLS connection and pairing protocols. The device is then able to successfully connect to the ADB service.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Untitled

    Uploaded by

    Huzaifah Shaheed
    4 views2 pages
    The document contains log entries from an Android device related to discovering and connecting to an ADB over Wi-Fi device. It records the device finding an ADB service on its local network with a specific name, IP address, and port numbers for the TLS connection and pairing protocols. The device is then able to successfully connect to the ADB service.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document contains log entries from an Android device related to discovering and connecting to an ADB over Wi-Fi device. It records the device finding an ADB service on its local network with a specific name, IP address, and port numbers for the TLS connection and pairing protocols. The device is then able to successfully connect to the ADB service.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    4 views2 pages

    Untitled

    Uploaded by

    Huzaifah Shaheed
    The document contains log entries from an Android device related to discovering and connecting to an ADB over Wi-Fi device. It records the device finding an ADB service on its local network with a specific name, IP address, and port numbers for the TLS connection and pairing protocols. The device is then able to successfully connect to the ADB service.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    of 2

    2023-02-12 15:18:46 20452 20452 E/WirelessAdbSetupGuideActivity: goto Open

    WifiDebug
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: onServiceFound name: adb-R5CN80WRCXX-
    zjAXPV, type: _adb-tls-connect._tcp., host: null, port: 0, network: 127, txtRecord:
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: onServiceFound name: adb-R5CN80WRCXX-
    zjAXPV, type: _adb-tls-connect._tcp., host: null, port: 0, network: 127, txtRecord:
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: onServiceResolved name: adb-R5CN80WRCXX-
    zjAXPV, type: ._adb-tls-connect._tcp, host: /192.168.8.104, port: 45843, network:
    127, txtRecord: #v=ADB_SECURE_SERVICE_VERSION
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: onServiceResolved name: adb-R5CN80WRCXX-
    zjAXPV, type: ._adb-tls-connect._tcp, host: /192.168.8.104, port: 45843, network:
    127, txtRecord: #v=ADB_SECURE_SERVICE_VERSION
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: resolvedService.host.hostAddress
    192.168.8.104
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: it.hostAddress
    fe80::3089:61ff:fe4a:94b3%wlan0
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: resolvedService.host.hostAddress
    192.168.8.104
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: it.hostAddress 192.168.8.104
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: onServiceResolved true
    2023-02-12 15:19:51 20452 20452 E/WirelessAdbManager: found tls connect port 45843
    2023-02-12 15:19:51 20452 20473 E/AdbMdns: onDiscoveryStopped _adb-tls-connect._tcp
    2023-02-12 15:20:04 20452 20452 E/WirelessAdbSetupGuideActivity:
    gotoNotificationSetting
    2023-02-12 15:20:08 20452 20452 E/WirelessAdbSetupGuideActivity: goto Wifi Pairing
    2023-02-12 15:20:08 20452 20452 E/WirelessAdbManager: start adbmns
    2023-02-12 15:20:08 20452 20473 E/AdbMdns: onDiscoveryStarted _adb-tls-pairing._tcp
    2023-02-12 15:20:47 20452 20473 E/AdbMdns: onServiceFound name: adb-R5CN80WRCXX-
    zjAXPV, type: _adb-tls-pairing._tcp., host: null, port: 0, network: 127, txtRecord:
    2023-02-12 15:20:47 20452 20473 E/AdbMdns: onServiceFound name: adb-R5CN80WRCXX-
    zjAXPV, type: _adb-tls-pairing._tcp., host: null, port: 0, network: 127, txtRecord:
    2023-02-12 15:20:48 20452 20473 E/AdbMdns: onServiceResolved name: adb-R5CN80WRCXX-
    zjAXPV, type: ._adb-tls-pairing._tcp, host: /192.168.8.104, port: 33369, network:
    127, txtRecord:
    2023-02-12 15:20:48 20452 20473 E/AdbMdns: onServiceResolved name: adb-R5CN80WRCXX-
    zjAXPV, type: ._adb-tls-pairing._tcp, host: /192.168.8.104, port: 33369, network:
    127, txtRecord:
    2023-02-12 15:20:48 20452 20473 E/AdbMdns: resolvedService.host.hostAddress
    192.168.8.104
    2023-02-12 15:20:48 20452 20473 E/AdbMdns: it.hostAddress
    fe80::3089:61ff:fe4a:94b3%wlan0
    2023-02-12 15:20:48 20452 20473 E/AdbMdns: resolvedService.host.hostAddress
    192.168.8.104
    2023-02-12 15:20:48 20452 20473 E/AdbMdns: it.hostAddress 192.168.8.104
    2023-02-12 15:20:48 20452 20473 E/AdbMdns: onServiceResolved true
    2023-02-12 15:20:48 20452 20452 E/WirelessAdbManager: found tls pairing port
    2023-02-12 15:20:48 20452 20473 E/AdbMdns: onDiscoveryStopped _adb-tls-pairing._tcp
    2023-02-12 15:21:01 20452 20452 E/WirelessAdbManager: startParing code 988114
    2023-02-12 15:21:01 20452 23213 E/WirelessAdbManager: paring host is ip6-localhost
    2023-02-12 15:21:01 20452 23213 E/WirelessAdbManager: paring port is 33369
    2023-02-12 15:21:01 20452 23213 E/WirelessAdbManager: paring code is 988114
    2023-02-12 15:21:02 20452 23213 E/WirelessAdbManager: connect host is ip6-localhost
    2023-02-12 15:21:02 20452 23213 E/WirelessAdbManager: connect port is 45843
    2023-02-12 15:21:02 20452 23213 E/WirelessAdbManager: fixPhantomLimited okay
    2023-02-12 15:33:18 32306 32306 D/WirelessAdbManager: init 1.4.2
    2023-02-12 15:33:18 32306 32306 E/WirelessAdbManager: searchTlsTcp
    2023-02-12 15:33:18 32306 32306 E/WirelessAdbManager: start adbmns
    2023-02-12 15:33:19 32306 32306 D/WirelessAdbManager: init okay
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: onDiscoveryStarted _adb-tls-connect._tcp
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: onServiceFound name: adb-R5CN80WRCXX-
    zjAXPV, type: _adb-tls-connect._tcp., host: null, port: 0, network: 127, txtRecord:
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: onServiceFound name: adb-R5CN80WRCXX-
    zjAXPV, type: _adb-tls-connect._tcp., host: null, port: 0, network: 127, txtRecord:
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: onServiceResolved name: adb-R5CN80WRCXX-
    zjAXPV, type: ._adb-tls-connect._tcp, host: /192.168.8.104, port: 45843, network:
    127, txtRecord: #v=ADB_SECURE_SERVICE_VERSION
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: onServiceResolved name: adb-R5CN80WRCXX-
    zjAXPV, type: ._adb-tls-connect._tcp, host: /192.168.8.104, port: 45843, network:
    127, txtRecord: #v=ADB_SECURE_SERVICE_VERSION
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: resolvedService.host.hostAddress
    192.168.8.104
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: it.hostAddress
    fe80::3089:61ff:fe4a:94b3%wlan0
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: resolvedService.host.hostAddress
    192.168.8.104
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: it.hostAddress 192.168.8.104
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: onServiceResolved true
    2023-02-12 15:33:19 32306 32306 E/WirelessAdbManager: found tls connect port 45843
    2023-02-12 15:33:19 32306 32351 E/AdbMdns: onDiscoveryStopped _adb-tls-connect._tcp

    You might also like