USB Connection problem

For user who dont speak german please use this part of my forum
user_deleted

USB Connection problem

Beitrag von user_deleted »

Hello,

I use MPE with a Samsung Galaxy S4 Androïd mobile.

MPE works perfectly with a wifi or Bluetooth connection but I can't make it work with a USB connection.

I much prefer wifi connection when I am at home (it's my wifi network) , but elsewhere (holidays) I prefer to use USB connection :

* If I choose the option "Connect via Autodetect", it automatically connects through wifi . Do I have to change something on the client then?
* If I choose the option "Connect via USB cable", I get this error message in my french version of MPE :


Pas de périphérique USB détecté


In english, it could be :

No USB device detected


* KIES3 is installed on my PC and so drivers are then.
* USB-Debugging is enabled on my mobile.

An other problem might be linked to this one. If I want to launch the "Ecran virtuel" ("Virtual screen"?) command in tools menu, when I am connected via wifi, I get the same error message :

Pas de périphérique USB détecté / No USB device detected



Danke Schön for your help
MarioSaraylian
Beiträge: 3
Registriert: So 27. Mai 2012, 09:02

Beitrag von MarioSaraylian »

I am having the same problem with HTC M8 GSM on Viper 3.1.0 ROM you really need to provide a logfile get any support on this. Capture the log file from within settings and paste it here.
FJ
Site Admin
Beiträge: 32106
Registriert: Mi 15. Feb 2006, 01:16
Wohnort: Tirol
Kontaktdaten:

Beitrag von FJ »

You can post the logfile after the error message was shown. Also check the device manager of windows. There should be a entry called like "SAMSUNG ADB Interface" when the phone is connected.
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.

Bitte benutzt auch die Forum-Suche bzw. die FAQ
mtstek
Beiträge: 4
Registriert: Mi 26. Nov 2014, 23:13

Beitrag von mtstek »

I have Samsung Galaxy S4 with firmware 4.4.4 and HP laptop (company PC).
MPE works fine with my desktop at home via WIFI network but haven't yet tried it via USB.

I'm having connection problem with HP laptop at work via AutoDetect, USB, Bluetooth. Saying "No device attached to USB" even though the Samsung KIES3 is detecting my phone perfectly.

Any sugestions for me to check?

Thanks,
FJ
Site Admin
Beiträge: 32106
Registriert: Mi 15. Feb 2006, 01:16
Wohnort: Tirol
Kontaktdaten:

Beitrag von FJ »

@mtstek: Did you enable USB-Debugging on the phone ? Did you read the FAQ ?
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.

Bitte benutzt auch die Forum-Suche bzw. die FAQ
mtstek
Beiträge: 4
Registriert: Mi 26. Nov 2014, 23:13

Beitrag von mtstek »

Yes I did and I rebooted the phone. Restarted MPE and still got same message.
Zuletzt geändert von mtstek am Sa 29. Nov 2014, 00:22, insgesamt 1-mal geändert.
Koelner
Beiträge: 1691
Registriert: Do 11. Okt 2012, 21:12
Wohnort: Deutschland

Beitrag von Koelner »

Enabling the Debug-mode does not necessarily reboot the phone.
Have you checked if the Debug-mode is really active?
Nur Geduld! Mit der Zeit wird aus Gras Milch.
user_deleted

Beitrag von user_deleted »

FJ hat geschrieben:You can post the logfile after the error message was shown. Also check the device manager of windows. There should be a entry called like "SAMSUNG ADB Interface" when the phone is connected.


Thanks but where can I find this logfile and which is its name?

I do not find it in C:\Program Files\MyPhoneExplorer folder and subfolders

Thanks
mtstek
Beiträge: 4
Registriert: Mi 26. Nov 2014, 23:13

Beitrag von mtstek »

Koelner hat geschrieben:Enabling the Debug-mode does not necessarily reboot the phone.
Have you checked if the Debug-mode is really active?


I checked it is active (with a checkmark) and also media device (when the phone is connected) connected as MTP. Just for a heck of it, I tried USB cable came with the phone and different USB ports - no help.
FJ
Site Admin
Beiträge: 32106
Registriert: Mi 15. Feb 2006, 01:16
Wohnort: Tirol
Kontaktdaten:

Beitrag von FJ »

@daej: Menu-File-Settings-Show logfile

@mtstek:
You can post the logfile after the error message was shown. Also check the device manager of windows. There should be a entry called like "SAMSUNG ADB Interface" when the phone is connected.
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.

Bitte benutzt auch die Forum-Suche bzw. die FAQ
mtstek
Beiträge: 4
Registriert: Mi 26. Nov 2014, 23:13

Beitrag von mtstek »

Here's my logfile when phone is connected via USB cable. And I see SAMSUNG Android ADB interface entry as you can in this logfile (after installing Samsung USB driver). Then comes another error "Access denied! Please confirm the secutrity message on your phone!". I'm running from company laptop with Win8.
Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.6
Datum: 12/1/2014

09:23:07.77 Setting Port: 999
09:23:07.77 Setting Baud: 115200
09:23:07.77 Avaiable Ports: COM3=\Device\Serial0;
09:23:07.80 Main Load frmSplash
09:23:07.83 Load frmSplash...
09:23:07.85 Show splash...
09:23:07.86 frmSplash geladen
09:23:08.66 Hauptfenster wird geladen
09:23:08.93 Sidebar fertig geladen
09:23:09.02 UC SMS wird geladen
09:23:09.06 UC Phonebook wird geladen
09:23:09.10 UC Phonebook fertig geladen
09:23:09.10 UC Calls wird geladen
09:23:09.13 UC Organizer wird geladen
09:23:09.19 Organizer initiated
09:23:09.21 Startpage=3
09:23:09.22 UC Filebrowser wird geladen
09:23:09.28 UC Filebrowser fertig geladen
09:23:09.28 UC AppBrowser wird geladen
09:23:09.30 UC Notes wird geladen
09:23:09.31 UC Calls wird geladen
09:23:09.36 Setting Lastuser:
09:23:09.38 Lade Userdatenbank:
09:23:09.41 Kontakte geladen
09:23:09.41 ParseDialedCalls needed 0ms
09:23:09.42 Anrufe geladen
09:23:09.44 Organizer LoadUser DefaultTimeColWidth=155
09:23:09.44 Organizer geladen
09:23:09.44 Notizen geladen
09:23:09.44 SMS geladen
09:23:10.30 Hauptfenster fertig geladen
09:23:45.61 DBT_DEVICEARRIVAL: COM4
09:23:49.59 Refresh ComDescriptions...
09:23:49.60 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_9C3D&SUBSYS_198F103C&REV_04\3&21436425&0&B3
09:23:49.60 MODEM: COM4 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&270C27A&0&0001
09:23:55.90 Refresh ComDescriptions...
09:23:55.90 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_9C3D&SUBSYS_198F103C&REV_04\3&21436425&0&B3
09:23:55.90 MODEM: COM4 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&270C27A&0&0001
09:24:01.04 OK pressed in settingswindow
09:24:01.07 Set first swap of settings
09:24:01.07 Apply new holidays
09:24:01.08 Holidays applied
09:24:01.09 Second swap of settings set
09:24:01.09 Everything is done
09:24:03.74 RunADBCommand: start-server
09:24:07.84 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
09:24:07.84 RunADBCommand: devices
09:24:07.91 ADB CommandResponse: List of devices attached
e11f4611 unauthorized
09:24:07.91 Run DeviceTracker
09:24:07.92 Init Tracker
09:24:07.93 Device Tracker Message: OKAY0016e11f4611 unauthorized

09:24:07.93 Connect to Android failed!
09:24:07.93 bOpened=False
09:24:07.93 Access denied! Please confirm the security message on your phone!
09:24:07.93 Refresh ComDescriptions...
09:24:07.93 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_9C3D&SUBSYS_198F103C&REV_04\3&21436425&0&B3
09:24:07.93 MODEM: COM4 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&270C27A&0&0001
09:24:07.94 ErrMsg: Connection to phone could not be established:
Access denied! Please confirm the security message on your phone!
09:24:29.24 RunADBCommand: start-server
09:24:29.31 ADB CommandResponse:
09:24:29.31 RunADBCommand: devices
09:24:29.38 ADB CommandResponse: List of devices attached
e11f4611 unauthorized
09:24:29.38 Connect to Android failed!
09:24:29.38 bOpened=False
09:24:29.38 Access denied! Please confirm the security message on your phone!
09:24:29.38 Refresh ComDescriptions...
09:24:29.38 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_9C3D&SUBSYS_198F103C&REV_04\3&21436425&0&B3
09:24:29.39 MODEM: COM4 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&270C27A&0&0001
09:24:29.39 ErrMsg: Connection to phone could not be established:
Access denied! Please confirm the security message on your phone!
09:24:36.15 Refresh ComDescriptions...
09:24:36.15 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_9C3D&SUBSYS_198F103C&REV_04\3&21436425&0&B3
09:24:36.15 MODEM: COM4 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&270C27A&0&0001
09:24:38.12 OK pressed in settingswindow
09:24:38.14 Set first swap of settings
09:24:38.14 Apply new holidays
09:24:38.15 Holidays applied
09:24:38.16 Second swap of settings set
09:24:38.16 Everything is done
09:24:40.89 RunADBCommand: start-server
09:24:40.92 ADB CommandResponse:
09:24:40.92 RunADBCommand: devices
09:24:40.95 ADB CommandResponse: List of devices attached
e11f4611 unauthorized
09:24:40.95 Connect to Android failed!
09:24:40.95 bOpened=False
09:24:40.95 Access denied! Please confirm the security message on your phone!
09:24:40.95 Refresh ComDescriptions...
09:24:40.95 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_9C3D&SUBSYS_198F103C&REV_04\3&21436425&0&B3
09:24:40.95 MODEM: COM4 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&270C27A&0&0001
09:24:40.95 ErrMsg: Connection to phone could not be established:
Access denied! Please confirm the security message on your phone!
09:24:57.55 Refresh ComDescriptions...
09:24:57.55 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_9C3D&SUBSYS_198F103C&REV_04\3&21436425&0&B3
09:24:57.55 MODEM: COM4 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&270C27A&0&0001
09:24:58.75 Device driver info:
09:24:58.75 Devices with ADB Interface: SAMSUNG Android ADB Interface
09:24:58.80 ADB Devices: SAMSUNG Android ADB Interface
09:24:58.80 Portable devices: SAMSUNG-SGH-I337
09:24:58.80 Unknown devices: Bluetooth Peripheral Device, Bluetooth Peripheral Device, Bluetooth Peripheral Device, Bluetooth Peripheral Device, Keyboard_Filter_01, Bluetooth Peripheral Device, Bluetooth Peripheral Device
rajbp
Beiträge: 4
Registriert: Do 9. Jan 2014, 23:56

Error: Connection to phone could not be established

Beitrag von rajbp »

FJ/Members,
i have Win8.1 64bit, Xolo Q800 device with android 4.2.1, MPE 1.8.6 installed yesterday
checked for the ADB, looks good
but still get the Error: Connection to phone could not be established
uninstalled MPE client in phone, still no go
log file details:
Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.6
Datum: 12/12/2014

23:31:17.06 Setting Port: 999
23:31:17.06 Setting Baud: 115200
23:31:17.06 Avaiable Ports: COM0=;
23:31:17.06 Main Load frmSplash
23:31:17.07 Load frmSplash...
23:31:17.07 Show splash...
23:31:17.09 frmSplash geladen
23:31:17.79 Hauptfenster wird geladen
23:31:17.92 Sidebar fertig geladen
23:31:17.99 UC SMS wird geladen
23:31:18.04 UC Phonebook wird geladen
23:31:18.07 UC Phonebook fertig geladen
23:31:18.07 UC Calls wird geladen
23:31:18.12 UC Organizer wird geladen
23:31:18.21 Organizer initiated
23:31:18.23 Startpage=1
23:31:18.24 UC Filebrowser wird geladen
23:31:18.31 UC Filebrowser fertig geladen
23:31:18.31 UC AppBrowser wird geladen
23:31:18.32 UC Notes wird geladen
23:31:18.34 UC Calls wird geladen
23:31:18.37 Setting Lastuser:
23:31:18.38 Lade Userdatenbank:
23:31:18.43 Kontakte geladen
23:31:18.43 ParseDialedCalls needed 0ms
23:31:18.48 Anrufe geladen
23:31:18.49 Organizer LoadUser DefaultTimeColWidth=135
23:31:18.49 Organizer geladen
23:31:18.49 Notizen geladen
23:31:18.49 SMS geladen
23:31:18.81 Hauptfenster fertig geladen
23:31:20.52 Broadcaster started
23:31:20.52 Start UPnP Discovery
23:31:20.52 Sending broadcast
23:31:21.02 Sending broadcast
23:31:21.52 Sending broadcast
23:31:25.52 Connect to Android failed!
23:31:25.52 bOpened=False
23:31:25.52 Failed to obtain the IP-address of the phone
23:31:25.52 Refresh ComDescriptions...
23:31:25.52 ErrMsg: Connection to phone could not be established:
Failed to obtain the IP-address of the phone
23:31:30.06 Refresh ComDescriptions...
23:31:34.58 OK pressed in settingswindow
23:31:34.61 Set first swap of settings
23:31:34.61 Apply new holidays
23:31:34.62 Holidays applied
23:31:34.62 Second swap of settings set
23:31:34.62 Everything is done
23:31:36.15 Closing Broadcaster
23:31:36.15 RunADBCommand: start-server
23:31:40.45 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
23:31:40.45 RunADBCommand: devices
23:31:40.53 ADB CommandResponse: List of devices attached
23:31:40.53 Run DeviceTracker
23:31:40.56 Init Tracker
23:31:40.58 Device Tracker Message: OKAY0000
23:31:40.58 Broadcaster started
23:31:40.59 Start UPnP Discovery
23:31:40.59 Sending broadcast
23:31:41.10 Sending broadcast
23:31:41.62 Sending broadcast
23:31:45.58 Connect to Android failed!
23:31:45.58 bOpened=False
23:31:45.58 USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
23:31:45.58 Refresh ComDescriptions...
23:31:45.58 ErrMsg: Connection to phone could not be established:
USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
23:31:57.28 Closing Broadcaster
23:31:57.28 RunADBCommand: start-server
23:31:57.35 ADB CommandResponse:
23:31:57.35 RunADBCommand: devices
23:31:57.43 ADB CommandResponse: List of devices attached
23:31:57.43 Broadcaster started
23:31:57.43 Start UPnP Discovery
23:31:57.43 Sending broadcast
23:31:57.94 Sending broadcast
23:31:58.45 Sending broadcast
23:32:02.44 Connect to Android failed!
23:32:02.44 bOpened=False
23:32:02.44 USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
23:32:02.44 Refresh ComDescriptions...
23:32:02.44 ErrMsg: Connection to phone could not be established:
USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
23:32:13.32 UPnP Device: Internet gateway device
23:32:15.63 UPnP Device: Internet gateway device
23:33:09.88 Closing Broadcaster
23:33:09.88 RunADBCommand: start-server
23:33:09.96 ADB CommandResponse:
23:33:09.96 RunADBCommand: devices
23:33:10.06 ADB CommandResponse: List of devices attached
23:33:10.06 Broadcaster started
23:33:10.06 Start UPnP Discovery
23:33:10.06 Sending broadcast
23:33:10.09 UPnP Device: Internet gateway device
23:33:10.56 Sending broadcast
23:33:11.06 Sending broadcast
23:33:15.06 Connect to Android failed!
23:33:15.07 bOpened=False
23:33:15.07 USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
23:33:15.07 Refresh ComDescriptions...
23:33:15.07 ErrMsg: Connection to phone could not be established:
USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
23:35:38.59 Refresh ComDescriptions...
23:35:40.76 Device driver info:
23:35:40.76 Devices with ADB Interface:
23:35:40.82 ADB Devices:
23:35:40.82 Portable devices: File-CD Gadget , SDC, File-CD Gadget
23:35:40.82 Unknown devices: XOLO Q800 -> Problem Code: 0x1C (28) [FAILED_INSTALL], <unknown device>

appreciate your assistance at the earliest
FJ
Site Admin
Beiträge: 32106
Registriert: Mi 15. Feb 2006, 01:16
Wohnort: Tirol
Kontaktdaten:

Beitrag von FJ »

@mtstek: there was no security message on the phone when you tried to connect ?
- in the phone you can reset the "USB Debugging permissions" -> do this
- try another USB-Cabel
- try another USB-Port
- do NOT use USB-Hubs

@rajbp: ADB is NOT OK. The ADB-Drivers for your phone are missing:
23:35:40.82 Unknown devices: XOLO Q800 -> Problem Code: 0x1C (2Cool [FAILED_INSTALL], <unknown device>
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.

Bitte benutzt auch die Forum-Suche bzw. die FAQ
yard
Beiträge: 7
Registriert: Mo 3. Okt 2011, 22:53

Xperia Go ST27i Windows 7 64 bit USB connection problem

Beitrag von yard »

I have trouble connect my Sony Xperia Go ST27i to new installed Windows 7 64bit. MyPhoneExplorer don´t connect via cable.

- Debugging mode enabled
- Installed drivers PC Companion - phone is visible in "normal" mode in Windows and PC Companion SW
- usb cable is correct and functional with MyPhoneExplore in other PC and OS
- USB 3.0 port is used
- Phone rebooted, debugging mode disabled/enabled

no result, no connection in USB mode

where may be a problem. I can´t find other ADB drivers specified for this phone
omadawn
Beiträge: 12
Registriert: Do 3. Nov 2011, 13:27

same problem with LG L5

Beitrag von omadawn »

Everything ok, WIN XP DETECTS the phone USB connection but not myphonexplorer....

here is the log:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.6
Datum: 24-09-2015

16:50:09.34 Setting Port: 999
16:50:09.34 Setting Baud: 115200
16:50:09.34 Avaiable Ports: COM1=\Device\Serial0;
16:50:09.34 Main Load frmSplash
16:50:09.36 Load frmSplash...
16:50:09.36 Show splash...
16:50:09.42 frmSplash geladen
16:50:10.39 Hauptfenster wird geladen
16:50:10.78 Sidebar fertig geladen
16:50:11.02 UC SMS wird geladen
16:50:11.09 UC Phonebook wird geladen
16:50:11.17 UC Phonebook fertig geladen
16:50:11.17 UC Calls wird geladen
16:50:11.25 UC Organizer wird geladen
16:50:11.41 Organizer initiated
16:50:11.53 Startpage=1
16:50:11.55 UC Filebrowser wird geladen
16:50:11.73 UC Filebrowser fertig geladen
16:50:11.73 UC AppBrowser wird geladen
16:50:11.77 UC Notes wird geladen
16:50:11.78 UC Calls wird geladen
16:50:11.87 Setting Lastuser:
16:50:11.89 Lade Userdatenbank:
16:50:12.08 Kontakte geladen
16:50:12.08 ParseDialedCalls needed 0ms
16:50:12.16 Anrufe geladen
16:50:12.16 Organizer LoadUser DefaultTimeColWidth=125
16:50:12.16 Organizer geladen
16:50:12.16 Notizen geladen
16:50:12.17 SMS geladen
16:50:13.37 Hauptfenster fertig geladen
16:50:17.69 RunADBCommand: start-server
16:50:21.84 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
16:50:21.84 RunADBCommand: devices
16:50:21.94 ADB CommandResponse: List of devices attached
16:50:21.94 Run DeviceTracker
16:50:21.95 Init Tracker
16:50:21.98 Device Tracker Message: OKAY0000
16:50:21.98 Connect to Android failed!
16:50:21.98 bOpened=False
16:50:21.98 No device attached to USB
16:50:21.98 Refresh ComDescriptions...
16:50:21.98 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
16:50:21.98 ErrMsg: Connection to phone could not be established:
No device attached to USB
16:52:08.31 RunADBCommand: start-server
16:52:08.40 ADB CommandResponse:
16:52:08.40 RunADBCommand: devices
16:52:08.49 ADB CommandResponse: List of devices attached
16:52:08.49 Connect to Android failed!
16:52:08.49 bOpened=False
16:52:08.49 No device attached to USB
16:52:08.49 Refresh ComDescriptions...
16:52:08.49 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
16:52:08.49 ErrMsg: Connection to phone could not be established:
No device attached to USB
16:52:40.88 Refresh ComDescriptions...
16:52:40.88 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
16:52:45.65 Device driver info:
16:52:45.65 Devices with ADB Interface:
16:52:45.71 ADB Devices:
16:52:45.71 Portable devices: LG-E610
16:52:45.71 Unknown devices: LG-E610 -> Problem Code: 0x1C (28) [FAILED_INSTALL]
justcosmic1
Beiträge: 26
Registriert: Fr 30. Sep 2011, 22:33

Unreliable USB?ADB connection

Beitrag von justcosmic1 »

I know this is an old thread, but I thought I would just let you know that I stoppedusing USB with my old Galaxy S4 some years back thinking it was the USB port on the phone.
But I have since experienced similar things so far with my LG V20 even though I am able to execute ADB commands via terminal fine.
I tworked fine yesterday - I synced contacts from T-Bird.
Then today no change except a reboot of the computer and I can't get it to connect.
I have tried changing the ADB drivers, killing any active ADB tasks and so on, but still no joy.
Yes I will have a closer look back at this thread...and remind myself how to do/where to find logs.
Would be great if there are any tweaks on MPE side that could help.
WiFi is OK - but for file transfer not so much.
Failing that I am almost tempted to look at an OTG USB-c to Network adapter connection instead. But obviously not ideal - and no guarantees it would work either.
Zuletzt geändert von justcosmic1 am Do 10. Dez 2020, 02:32, insgesamt 1-mal geändert.
justcosmic1
Beiträge: 26
Registriert: Fr 30. Sep 2011, 22:33

Beitrag von justcosmic1 »

Here's a log file:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.15
Datum: 10/12/2020

01:17:04.23 Windows Version=6.1
01:17:04.24 Setting Port: 999
01:17:04.24 Setting Baud: 115200
01:17:04.24 Avaiable Ports: COM4=\Device\QCUSB_COM4_1; COM5=\Device\QCUSB_COM5_3; COM16=\Device\LGANDNETDIAG1; COM17=\Device\LGANDNETMDM0;
01:17:04.24 Main Load frmSplash
01:17:04.26 Load frmSplash...
01:17:05.00 Hauptfenster wird geladen
01:17:05.27 Sidebar fertig geladen
01:17:05.80 UC SMS wird geladen
01:17:05.92 UC Phonebook wird geladen
01:17:05.98 UC Phonebook fertig geladen
01:17:05.98 UC Calls wird geladen
01:17:06.09 UC Organizer wird geladen
01:17:06.19 RefreshToday...
01:17:06.19 RefreshToday fertig
01:17:06.22 Organizer initiated
01:17:06.22 Startpage=1
01:17:06.22 UC Filebrowser wird geladen
01:17:06.48 UC Filebrowser fertig geladen
01:17:06.48 UC AppBrowser wird geladen
01:17:06.50 UC Notes wird geladen
01:17:06.52 UC Calls wird geladen
01:17:06.59 Setting Lastuser: LGE LG-VS995 [5BFC9EDA-83F3-4CB3-A93A-EE8BC21853BB]
01:17:06.61 PasswordCheck OK, check Userfolder, G_AppData=C:\Users\Justin\AppData\Roaming\MyPhoneExplorer
01:17:06.61 CheckUserDirectory for: LGE LG-VS995 [5BFC9EDA-83F3-4CB3-A93A-EE8BC21853BB]
01:17:06.61 Userfolder=C:\Users\Justin\AppData\Roaming\MyPhoneExplorer\LGE LG-VS995 [5BFC9EDA-83F3-4CB3-A93A-EE8BC21853BB]
01:17:06.61 ParseModell
01:17:06.62 Lade Userdatenbank: LGE LG-VS995 [5BFC9EDA-83F3-4CB3-A93A-EE8BC21853BB]
01:17:06.93 LoadDatafile: pb_metadata.xml(3793 Bytes)
01:17:06.95 LoadDatafile: Phonebook.dat(555493 Bytes)
01:17:07.81 Sorting search dictionary with 1626 items...
01:17:08.96 Kontakte geladen
01:17:08.96 LoadDatafile: Calls.dat(17468 Bytes)
01:17:08.98 ParseDialedCalls needed 16ms
01:17:09.30 Anrufe geladen
01:17:09.30 Organizer LoadUser DefaultTimeColWidth=122
01:17:09.34 LoadDatafile: Organizer.dat(3474 Bytes)
01:17:09.35 LoadDatafile: cal_metadata.xml(364 Bytes)
01:17:09.35 RefreshToday...
01:17:09.35 RefreshToday fertig
01:17:09.36 Organizer geladen
01:17:09.37 LoadDatafile: Notes.dat(23193 Bytes)
01:17:09.43 Notizen geladen
01:17:09.43 Load SMS Data...
01:17:09.44 LoadDatafile: Messages.dat(114632 Bytes)
01:17:09.44 MMS - Datenbank wird geladen...
01:17:09.53 MMS Laden - Readfile: 0 Split: 0 Parse: 94 Nachrichten: 424
01:17:09.55 LoadDatafile: MessageArchive.dat(3158918 Bytes)
01:17:12.31 MMS Archiv laden - Parse: 2777
01:17:14.78 RefreshList (Archive): Addrows=1388 Sort=905 MenuUpdate=16 Redraw=0
01:17:14.89 SMS Data Loaded...
01:17:14.89 SMS geladen
01:17:14.95 Version check...
01:17:15.03 Hauptfenster fertig geladen
01:17:15.05 GotAppCommand: ConnectAutoplay
\\?\USB#VID_1004&PID_62CE&MI_00#7&36df3633&1&0000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}

01:17:15.47 UPnP-ID to DeviceSerial: LGUS9962cb2b26
01:17:15.47 ClosePort called
01:17:15.47 Port wurde geschlossen
01:17:16.56 Connect via USB
01:17:16.57 RunADBCommand: start-server
01:17:22.10 ADB CommandResponse: * daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
01:17:22.10 RunADBCommand: devices
01:17:25.82 ADB CommandResponse: List of devices attached
* daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
01:17:25.82 Run DeviceTracker
01:17:27.83 Connect with ADB failed (DeviceTracker)
01:17:27.84 Connect to Android failed!
01:17:27.84 bOpened=False
01:17:27.84 No device attached to USB
01:17:27.84 Refresh ComDescriptions...
01:17:27.85 PORT: COM4 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Diagnostics 9225 InstanceID=USB\VID_05C6&PID_9225&MI_01\7&2A658210&0&4_01
01:17:27.86 PORT: COM16 Enumerator=USB Displayed=LGE Mobile for VZW USB Serial Port InstanceID=USB\VID_1004&PID_62CE&MI_03\7&36DF3633&1&0000
01:17:27.87 MODEM: COM17 Enumerator=USB Displayed=LGE Mobile for VZW USB Modem FriendlyName=LGE Mobile for VZW USB Modem InstanceID=USB\VID_1004&PID_62CE&MI_01\7&36DF3633&1&0000
01:17:27.88 MODEM: COM5 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Modem 9225 FriendlyName=Qualcomm Gobi 2000 HS-USB Modem 9225 InstanceID=USB\VID_05C6&PID_9225&MI_02\7&2A658210&0&4_02
01:17:27.88 ErrMsg: Connection to phone could not be established:
No device attached to USB
01:22:21.37 Connect via USB
01:22:21.37 RunADBCommand: start-server
01:22:26.29 ADB CommandResponse: * daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
01:22:26.29 RunADBCommand: devices
01:22:29.94 ADB CommandResponse: List of devices attached
* daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
01:22:29.94 Run DeviceTracker
01:22:31.94 Connect with ADB failed (DeviceTracker)
01:22:31.94 Connect to Android failed!
01:22:31.95 bOpened=False
01:22:31.95 No device attached to USB
01:22:31.95 Refresh ComDescriptions...
01:22:31.96 PORT: COM4 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Diagnostics 9225 InstanceID=USB\VID_05C6&PID_9225&MI_01\7&2A658210&0&4_01
01:22:31.97 PORT: COM16 Enumerator=USB Displayed=LGE Mobile for VZW USB Serial Port InstanceID=USB\VID_1004&PID_62CE&MI_03\7&36DF3633&1&0000
01:22:31.98 MODEM: COM17 Enumerator=USB Displayed=LGE Mobile for VZW USB Modem FriendlyName=LGE Mobile for VZW USB Modem InstanceID=USB\VID_1004&PID_62CE&MI_01\7&36DF3633&1&0000
01:22:31.98 MODEM: COM5 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Modem 9225 FriendlyName=Qualcomm Gobi 2000 HS-USB Modem 9225 InstanceID=USB\VID_05C6&PID_9225&MI_02\7&2A658210&0&4_02
01:22:31.99 ErrMsg: Connection to phone could not be established:
No device attached to USB
01:22:48.23 DBT_DEVICEREMOVECOMPLETE: COM16
01:22:53.42 DBT_DEVICEARRIVAL: COM16
01:22:57.42 Refresh ComDescriptions...
01:22:57.43 PORT: COM4 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Diagnostics 9225 InstanceID=USB\VID_05C6&PID_9225&MI_01\7&2A658210&0&4_01
01:22:57.43 PORT: COM16 Enumerator=USB Displayed=LGE Mobile for VZW USB Serial Port InstanceID=USB\VID_1004&PID_62CE&MI_03\7&36DF3633&1&0000
01:22:57.43 MODEM: COM17 Enumerator=USB Displayed=LGE Mobile for VZW USB Modem FriendlyName=LGE Mobile for VZW USB Modem InstanceID=USB\VID_1004&PID_62CE&MI_01\7&36DF3633&1&0000
01:22:57.44 MODEM: COM5 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Modem 9225 FriendlyName=Qualcomm Gobi 2000 HS-USB Modem 9225 InstanceID=USB\VID_05C6&PID_9225&MI_02\7&2A658210&0&4_02
01:22:57.44 ShowBalloontip: MyPhoneExplorer - Detected new device on COM16:
LGE Mobile for VZW USB Serial Port
01:23:09.14 Connect via USB
01:23:09.14 RunADBCommand: start-server
01:23:12.75 ADB CommandResponse: * daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
01:23:12.75 RunADBCommand: devices
01:23:16.28 ADB CommandResponse: List of devices attached
* daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
01:23:16.28 Run DeviceTracker
01:23:18.29 Connect with ADB failed (DeviceTracker)
01:23:18.29 Connect to Android failed!
01:23:18.29 bOpened=False
01:23:18.29 No device attached to USB
01:23:18.29 Refresh ComDescriptions...
01:23:18.31 PORT: COM4 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Diagnostics 9225 InstanceID=USB\VID_05C6&PID_9225&MI_01\7&2A658210&0&4_01
01:23:18.31 PORT: COM16 Enumerator=USB Displayed=LGE Mobile for VZW USB Serial Port InstanceID=USB\VID_1004&PID_62CE&MI_03\7&36DF3633&1&0000
01:23:18.32 MODEM: COM17 Enumerator=USB Displayed=LGE Mobile for VZW USB Modem FriendlyName=LGE Mobile for VZW USB Modem InstanceID=USB\VID_1004&PID_62CE&MI_01\7&36DF3633&1&0000
01:23:18.33 MODEM: COM5 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Modem 9225 FriendlyName=Qualcomm Gobi 2000 HS-USB Modem 9225 InstanceID=USB\VID_05C6&PID_9225&MI_02\7&2A658210&0&4_02
01:23:18.33 ErrMsg: Connection to phone could not be established:
No device attached to USB
01:23:32.21 Refresh ComDescriptions...
01:23:32.21 PORT: COM4 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Diagnostics 9225 InstanceID=USB\VID_05C6&PID_9225&MI_01\7&2A658210&0&4_01
01:23:32.22 PORT: COM16 Enumerator=USB Displayed=LGE Mobile for VZW USB Serial Port InstanceID=USB\VID_1004&PID_62CE&MI_03\7&36DF3633&1&0000
01:23:32.22 MODEM: COM17 Enumerator=USB Displayed=LGE Mobile for VZW USB Modem FriendlyName=LGE Mobile for VZW USB Modem InstanceID=USB\VID_1004&PID_62CE&MI_01\7&36DF3633&1&0000
01:23:32.22 MODEM: COM5 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Modem 9225 FriendlyName=Qualcomm Gobi 2000 HS-USB Modem 9225 InstanceID=USB\VID_05C6&PID_9225&MI_02\7&2A658210&0&4_02
01:23:34.54 Device driver info:
01:23:34.56 Devices with ADB Interface: Android ADB Interface
01:23:34.74 ADB Devices: Android ADB Interface
01:23:34.74 Portable devices: LG-VS995
01:23:34.74 Unknown devices:
justcosmic1
Beiträge: 26
Registriert: Fr 30. Sep 2011, 22:33

Beitrag von justcosmic1 »

This is an ADB command window I opened after and the script I used to kill running tasks and re-detect the phone:


Z:\Downloads\Main_Downloads\MobilePhoneStuff\LG-V20\Minimal_ADB_Fastboot_v1.4.3>
adb devices
* daemon not running; starting now at tcp:5037
could not read ok from ADB Server
* failed to start daemon
adb.exe: failed to check server version: cannot connect to daemon

Z:\Downloads\Main_Downloads\MobilePhoneStuff\LG-V20\Minimal_ADB_Fastboot_v1.4.3>
netstat -ano | findstr 5037
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 10960
TCP 127.0.0.1:5037 127.0.0.1:51577 ESTABLISHED 10960
TCP 127.0.0.1:5037 127.0.0.1:51578 ESTABLISHED 10960
TCP 127.0.0.1:5037 127.0.0.1:51607 ESTABLISHED 10960
TCP 127.0.0.1:5037 127.0.0.1:51609 ESTABLISHED 10960
TCP 127.0.0.1:51577 127.0.0.1:5037 ESTABLISHED 12836
TCP 127.0.0.1:51578 127.0.0.1:5037 ESTABLISHED 11784
TCP 127.0.0.1:51607 127.0.0.1:5037 ESTABLISHED 10852
TCP 127.0.0.1:51609 127.0.0.1:5037 ESTABLISHED 13704

Z:\Downloads\Main_Downloads\MobilePhoneStuff\LG-V20\Minimal_ADB_Fastboot_v1.4.3>
tasklist|findstr 10960
adb.exe 10960 Console 1 7,504 K

Z:\Downloads\Main_Downloads\MobilePhoneStuff\LG-V20\Minimal_ADB_Fastboot_v1.4.3>
taskkill /f /t /im adb.exe
SUCCESS: The process with PID 10960 (child process of PID 10272) has been termin
ated.
SUCCESS: The process with PID 10272 (child process of PID 11784) has been termin
ated.
SUCCESS: The process with PID 12836 (child process of PID 11784) has been termin
ated.
SUCCESS: The process with PID 10852 (child process of PID 11784) has been termin
ated.
ERROR: The process with PID 13704 (child process of PID 11784) could not be term
inated.
Reason: There is no running instance of the task.

Z:\Downloads\Main_Downloads\MobilePhoneStuff\LG-V20\Minimal_ADB_Fastboot_v1.4.3>
adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
LGUS9962cb2b26 device


Z:\Downloads\Main_Downloads\MobilePhoneStuff\LG-V20\Minimal_ADB_Fastboot_v1.4.3>
justcosmic1
Beiträge: 26
Registriert: Fr 30. Sep 2011, 22:33

Beitrag von justcosmic1 »

Then after doing that in the command window this is the log file from MPE (from that point)

No device attached to USB
01:36:40.89 Refresh ComDescriptions...
01:36:40.89 PORT: COM4 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Diagnostics 9225 InstanceID=USB\VID_05C6&PID_9225&MI_01\7&2A658210&0&4_01
01:36:40.90 PORT: COM16 Enumerator=USB Displayed=LGE Mobile for VZW USB Serial Port InstanceID=USB\VID_1004&PID_62CE&MI_03\7&36DF3633&1&0000
01:36:40.90 MODEM: COM17 Enumerator=USB Displayed=LGE Mobile for VZW USB Modem FriendlyName=LGE Mobile for VZW USB Modem InstanceID=USB\VID_1004&PID_62CE&MI_01\7&36DF3633&1&0000
01:36:40.91 MODEM: COM5 Enumerator=USB Displayed=Qualcomm Gobi 2000 HS-USB Modem 9225 FriendlyName=Qualcomm Gobi 2000 HS-USB Modem 9225 InstanceID=USB\VID_05C6&PID_9225&MI_02\7&2A658210&0&4_02
01:36:43.46 Device driver info:
01:36:43.48 Devices with ADB Interface: Android ADB Interface
01:36:43.66 ADB Devices: Android ADB Interface
01:36:43.66 Portable devices: LG-VS995
01:36:43.66 Unknown devices:
justcosmic1
Beiträge: 26
Registriert: Fr 30. Sep 2011, 22:33

Beitrag von justcosmic1 »

Sorry for all the long log file posts! But hopefully you may see something that I can't in there;
It appears that MPE is seeing the device just fine, but failing to connect. I have tried uninstalling and reinstalling the client - and as you see ADB connection between the phone and the computer is working fine in command prompt. In case it's important; I don't always have to kill the active task via ADB after trying to connect to MPE.
No messages coming up on phone and ADB/file sharing etcetera is enabled.
I am running Android 11 (LOS 18.0), but as mentioned before I have had issues on my previous phone too.
Meanwhile I will keep trying.
Antworten