SOLVED : USB connection fails, WiFi is ok

Anmeldedatum: 07.09.2016 Beiträge: 8

Hello,

MPE was unable to connect via USB.
Was working fine, but abruptly stopped being able to connect via USB.
WiFi is ok.

Android adb server was unable to start.

The issue was Windows Sandbox feature (Windows10 May 2020 update).

MPE works fine if Windows Sandbox feature is turned off.

The log file - before and after - is attached.

Can the developer can kindly look into this, for the next update - to maybe change the TCP port - so that MPE on USB can be used when Windows Sandbox feature is ON.

Thank you.

====Windows Sandbox feature ON and MPE does NOT work on USB =======================
Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.14
Datum: 30-Jun-20

21:47:00.06 Windows Version=10.0
21:47:00.06 Setting Port: 999
21:47:00.06 Setting Baud: 115200
21:47:00.06 Avaiable Ports: COM1=\Device\Serial0;
21:47:00.06 Main Load frmSplash
21:47:00.08 Load frmSplash...
21:47:01.42 Hauptfenster wird geladen
21:47:01.69 Sidebar fertig geladen
21:47:01.95 UC SMS wird geladen
21:47:02.04 UC Phonebook wird geladen
21:47:02.11 UC Phonebook fertig geladen
21:47:02.11 UC Calls wird geladen
21:47:02.22 UC Organizer wird geladen
21:47:02.38 Organizer initiated
21:47:02.51 Startpage=3
21:47:02.54 UC Filebrowser wird geladen
21:47:02.73 UC Filebrowser fertig geladen
21:47:02.73 UC AppBrowser wird geladen
21:47:02.75 UC Notes wird geladen
21:47:02.78 UC Calls wird geladen
21:47:02.84 Setting Lastuser: LENOVO Lenovo PB-6505M [868922041557618]
21:47:02.86 PasswordCheck OK, check Userfolder, G_AppData=C:\ExtraApps\MyPhoneExplorer\Data\MyPhoneExplorer
21:47:02.86 CheckUserDirectory for: LENOVO Lenovo PB-6505M [868922041557618]
21:47:02.86 Userfolder=C:\ExtraApps\MyPhoneExplorer\Data\MyPhoneExplorer\LENOVO Lenovo PB-6505M [868922041557618]
21:47:02.86 ParseModell
21:47:02.88 Lade Userdatenbank: LENOVO Lenovo PB-6505M [868922041557618]
21:47:03.12 LoadDatafile: pb_metadata.xml(8716 Bytes)
21:47:03.14 LoadDatafile: Phonebook.dat(751124 Bytes)
21:47:03.81 Sorting search dictionary with 4035 items...
21:47:07.50 Kontakte geladen
21:47:07.50 LoadDatafile: Calls.dat(106585 Bytes)
21:47:07.57 ParseDialedCalls needed 16ms
21:47:08.29 Anrufe geladen
21:47:08.29 Organizer LoadUser DefaultTimeColWidth=226
21:47:08.37 LoadDatafile: Organizer.dat(182889 Bytes)
21:47:08.52 LoadDatafile: cal_metadata.xml(2076 Bytes)
21:47:08.65 Organizer geladen
21:47:08.67 LoadDatafile: Notes.dat(51298 Bytes)
21:47:08.68 LoadDatafile: notes_metadata.xml(114 Bytes)
21:47:08.72 Notizen geladen
21:47:08.72 Load SMS Data...
21:47:08.72 LoadDatafile: Messages.dat(33827 Bytes)
21:47:08.72 MMS - Datenbank wird geladen...
21:47:08.74 MMS Laden - Readfile: 0 Split: 0 Parse: 15 Nachrichten: 143
21:47:08.74 LoadDatafile: MessageArchive.dat(31435 Bytes)
21:47:08.75 MMS Archiv laden - Parse: 16
21:47:08.90 RefreshList (Archive): Addrows=0 Sort=16 MenuUpdate=0 Redraw=0
21:47:09.00 SMS Data Loaded...
21:47:09.00 SMS geladen
21:47:09.16 Version check...
21:47:09.32 Hauptfenster fertig geladen
21:47:09.35 Init Android Connection for future connect via USB
21:47:09.35 RunADBCommand: start-server
21:47:09.39 ADB CommandResponse:
21:47:09.39 Run DeviceTracker
21:47:11.39 Connect with ADB failed (DeviceTracker)
21:47:11.39 Init Android Connection for future connect via WiFi
21:47:11.40 Start UPnP Discovery
21:47:11.40 Broadcaster started
21:47:11.47 UPnP Device: D-Link DSL-2750U
21:47:26.62 Sending GCM Push...
21:47:27.07 Connect via USB
21:47:27.07 Closing Broadcaster
21:47:27.08 RunADBCommand: start-server
21:47:32.26 ADB CommandResponse: * daemon not running; starting now at tcp:5037
* daemon started successfully
21:47:32.26 RunADBCommand: devices
21:47:32.35 ADB CommandResponse: List of devices attached
HZC90259 device
21:47:32.35 Run DeviceTracker
21:47:32.38 Init Tracker
21:47:32.41 Device Tracker Message: OKAY0010HZC90259 device

21:47:32.41 RunADBCommand: -s "HZC90259" forward tcp:5210 tcp:5210
21:47:32.49 ADB CommandResponse: error: cannot bind listener: cannot bind to 127.0.0.1:5210: An attempt was made to access a socket in a way forbidden by its access permissions. (10013)
21:47:32.49 Try connecting to 127.0.0.1...
21:47:33.04 RunADBCommand: -s "HZC90259" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
21:47:33.24 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }
21:47:33.39 Try launch USB connection
21:47:34.01 Try launch USB connection
21:47:34.60 Try launch USB connection
21:47:35.20 Try launch USB connection
21:47:35.80 Try launch USB connection
21:47:36.39 Try launch USB connection
21:47:37.00 Try launch USB connection
21:47:37.60 Try launch USB connection
21:47:38.21 Try launch USB connection
21:47:38.80 Try launch USB connection
21:47:39.40 Connect via FixedIP:
21:47:39.40 Connect via WiFi
21:47:39.41 Broadcaster started
21:47:39.41 Start UPnP Discovery
21:47:39.41 Sending broadcast
21:47:39.41 Try connecting to 10.20.11.170 (cached WifiIP)...
21:47:39.53 UPnP Device: D-Link DSL-2750U
21:47:39.93 Sending broadcast
21:47:40.44 Sending broadcast
21:47:46.41 Connect via Bluetooth
21:47:46.41 Connect Bluetooth...
21:47:46.45 No Bluetooth API was found.
21:47:46.45 No Bluetooth Radio found
21:47:46.45 Connect to Android failed!
21:47:46.45 bOpened=False
21:47:46.45 WiFi: Failed to obtain the IP-address of the phone
Bluetooth: There was no Bluetooth-Stack found on your PC. Activate Bluetooth or plug in your Bluetooth-Stick.
21:47:46.45 Refresh ComDescriptions...
21:47:46.45 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
21:47:46.45 ErrMsg: Connection to phone could not be established:
WiFi: Failed to obtain the IP-address of the phone
Bluetooth: There was no Bluetooth-Stack found on your PC. Activate Bluetooth or plug in your Bluetooth-Stick.
21:47:52.46 Refresh ComDescriptions...
21:47:52.47 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
21:47:54.88 Device driver info:
21:47:54.88 Devices with ADB Interface: ADB Device
21:47:54.91 ADB Devices:
21:47:54.91 Portable devices: Lenovo Tab V7
21:47:54.91 Unknown devices: <unknown device>
========================

====Windows Sandbox feature OFF and MPE works on USB =======================
Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.14
Datum: 01-Jul-20

11:27:24.82 Windows Version=10.0
11:27:24.83 Setting Port: 999
11:27:24.83 Setting Baud: 115200
11:27:24.83 Avaiable Ports: COM1=\Device\Serial0;
11:27:24.83 Main Load frmSplash
11:27:24.84 Load frmSplash...
11:27:25.95 Hauptfenster wird geladen
11:27:26.16 Sidebar fertig geladen
11:27:26.41 UC SMS wird geladen
11:27:26.49 UC Phonebook wird geladen
11:27:26.55 UC Phonebook fertig geladen
11:27:26.55 UC Calls wird geladen
11:27:26.64 UC Organizer wird geladen
11:27:26.79 Organizer initiated
11:27:26.88 Startpage=3
11:27:26.91 UC Filebrowser wird geladen
11:27:27.13 UC Filebrowser fertig geladen
11:27:27.13 UC AppBrowser wird geladen
11:27:27.15 UC Notes wird geladen
11:27:27.17 UC Calls wird geladen
11:27:27.23 Setting Lastuser: LENOVO Lenovo PB-6505M [868922041557618]
11:27:27.27 PasswordCheck OK, check Userfolder, G_AppData=C:\ExtraApps\MyPhoneExplorer\Data\MyPhoneExplorer
11:27:27.27 CheckUserDirectory for: LENOVO Lenovo PB-6505M [868922041557618]
11:27:27.27 Userfolder=C:\ExtraApps\MyPhoneExplorer\Data\MyPhoneExplorer\LENOVO Lenovo PB-6505M [868922041557618]
11:27:27.27 ParseModell
11:27:27.29 Lade Userdatenbank: LENOVO Lenovo PB-6505M [868922041557618]
11:27:27.50 LoadDatafile: pb_metadata.xml(8720 Bytes)
11:27:27.52 LoadDatafile: Phonebook.dat(751368 Bytes)
11:27:28.21 Sorting search dictionary with 4035 items...
11:27:31.26 Kontakte geladen
11:27:31.26 LoadDatafile: Calls.dat(107367 Bytes)
11:27:31.32 ParseDialedCalls needed 16ms
11:27:31.97 Anrufe geladen
11:27:31.97 Organizer LoadUser DefaultTimeColWidth=226
11:27:32.03 LoadDatafile: Organizer.dat(183340 Bytes)
11:27:32.18 LoadDatafile: cal_metadata.xml(2076 Bytes)
11:27:32.31 Organizer geladen
11:27:32.32 LoadDatafile: Notes.dat(51298 Bytes)
11:27:32.33 LoadDatafile: notes_metadata.xml(114 Bytes)
11:27:32.36 Notizen geladen
11:27:32.36 Load SMS Data...
11:27:32.36 LoadDatafile: Messages.dat(33391 Bytes)
11:27:32.36 MMS - Datenbank wird geladen...
11:27:32.38 MMS Laden - Readfile: 0 Split: 0 Parse: 15 Nachrichten: 142
11:27:32.38 LoadDatafile: MessageArchive.dat(32135 Bytes)
11:27:32.39 MMS Archiv laden - Parse: 0
11:27:32.52 RefreshList (Archive): Addrows=0 Sort=16 MenuUpdate=0 Redraw=0
11:27:32.61 SMS Data Loaded...
11:27:32.61 SMS geladen
11:27:32.71 Version check...
11:27:32.87 Hauptfenster fertig geladen
11:27:32.90 Init Android Connection for future connect via USB
11:27:32.90 RunADBCommand: start-server
11:27:32.97 ADB CommandResponse:
11:27:32.97 Run DeviceTracker
11:27:33.00 Init Tracker
11:27:33.03 Device Tracker Message: OKAY0010HZC90259 device

11:27:33.03 Init Android Connection for future connect via WiFi
11:27:33.04 Start UPnP Discovery
11:27:33.04 Broadcaster started
11:27:33.12 UPnP Device: D-Link DSL-2750U
11:27:34.76 Sending GCM Push...
11:27:35.10 Connect via USB
11:27:35.11 Closing Broadcaster
11:27:35.11 RunADBCommand: start-server
11:27:35.17 ADB CommandResponse:
11:27:35.17 RunADBCommand: devices
11:27:35.25 ADB CommandResponse: List of devices attached
HZC90259 device
11:27:35.25 RunADBCommand: -s "HZC90259" forward tcp:5210 tcp:5210
11:27:35.31 ADB CommandResponse:
11:27:35.31 Try connecting to 127.0.0.1...
11:27:35.32 Socket closed
11:27:35.33 RunADBCommand: -s "HZC90259" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
11:27:35.60 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }
11:27:35.76 Try launch USB connection
11:27:35.88 Connect to Android OK (127.0.0.1)
11:27:35.88 Settimeout: RT=2000 WT=500
11:27:35.88 bOpened=True

Anmeldedatum: 03.07.2020 Beiträge: 2

I didn't have the experience of an earlier user who found a solution that allowed for USB connection in Win 10. Their machine may be Win 10 Pro but mine is Win 10 Home so Sandbox, virtualization isn't available, That means their solution doesn't seem to work: it can't be turned on or off, which enables MPE through the USB connection.

Does anyone have another fix or workaround? I can access every file on my phone directly on my laptop as before, but no files with MPE after the Win 10 1909 upgrade unless I use WiFi.

John

Anmeldedatum: 07.09.2016 Beiträge: 8

Seeing the MPE log file immediately after a failed USB attempt can be very helpful.

If you can post it here, other users (or I) may be able to help.

Regards.

Anmeldedatum: 03.07.2020 Beiträge: 2

Thanks, Padua

Here's the MPE log file immediately after a failed USB attempt, as you asked. I think it's a bit repetitive, but I hope you can follow:

17:56:20.77 ClosePort called
17:56:20.77 Androidsocket wird geschlossen 7
17:56:20.77 Port wurde geschlossen
17:56:20.80 Closing Broadcaster
17:56:23.68 Connect via USB
17:56:23.69 RunADBCommand: start-server
17:56:23.95 ADB CommandResponse:
17:56:23.95 RunADBCommand: devices
17:56:24.23 ADB CommandResponse: List of devices attached
17:56:24.23 Connect to Android failed!
17:56:24.23 bOpened=False
17:56:24.23 No device attached to USB
17:56:24.23 Refresh ComDescriptions...
17:56:24.24 ErrMsg: Connection to phone could not be established:
No device attached to USB
17:56:54.11 Connect via USB
17:56:54.11 RunADBCommand: start-server
17:56:54.37 ADB CommandResponse:
17:56:54.37 RunADBCommand: devices
17:56:54.62 ADB CommandResponse: List of devices attached
17:56:54.63 Connect to Android failed!
17:56:54.63 bOpened=False
17:56:54.63 No device attached to USB
17:56:54.63 Refresh ComDescriptions...
17:56:54.63 ErrMsg: Connection to phone could not be established:
No device attached to USB
18:00:17.28 DBT_DEVICEARRIVAL: COM3
18:00:17.91 DBT_DEVICEARRIVAL: COM4
18:00:21.28 Refresh ComDescriptions...
18:00:21.32 PORT: COM3 Enumerator=BTHENUM Displayed='Mi Phone' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&0001038F_PID&1200\7&20010894&0&F460E249B065_C00000000
18:00:21.33 PORT: COM4 Enumerator=BTHENUM Displayed=Standard Serial over Bluetooth link InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\7&20010894&0&000000000000_00000000
18:00:21.33 ShowBalloontip: MyPhoneExplorer - Detected new device on COM4:
Standard Serial over Bluetooth link
18:00:54.26 Connect via USB
18:00:54.26 RunADBCommand: start-server
18:00:54.60 ADB CommandResponse:
18:00:54.60 RunADBCommand: devices
18:00:54.88 ADB CommandResponse: List of devices attached
18:00:54.88 Connect to Android failed!
18:00:54.90 bOpened=False
18:00:54.90 No device attached to USB
18:00:54.90 Refresh ComDescriptions...
18:00:54.91 PORT: COM3 Enumerator=BTHENUM Displayed='Mi Phone' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&0001038F_PID&1200\7&20010894&0&F460E249B065_C00000000
18:00:54.91 PORT: COM4 Enumerator=BTHENUM Displayed=Standard Serial over Bluetooth link InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\7&20010894&0&000000000000_00000000
18:00:54.91 ErrMsg: Connection to phone could not be established:
No device attached to USB
18:01:15.96 Refresh ComDescriptions...
18:01:15.97 PORT: COM3 Enumerator=BTHENUM Displayed='Mi Phone' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&0001038F_PID&1200\7&20010894&0&F460E249B065_C00000000
18:01:15.97 PORT: COM4 Enumerator=BTHENUM Displayed=Standard Serial over Bluetooth link InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\7&20010894&0&000000000000_00000000
18:01:24.94 Fritzbox found by default Hostname
18:01:27.82 Device driver info:
18:01:27.82 Devices with ADB Interface:
18:01:27.99 ADB Devices:
18:01:27.99 Portable devices: MI MAX 3, Card Reader
18:01:27.99 Unknown devices: Bluetooth Peripheral Device, SMS/MMS, <unknown device>, Bluetooth Peripheral Device, Bluetooth Peripheral Device

Informationen zum Datenschutz auf dieser Website