FJ Software Foren-Übersicht  
 Homepage   •  Suchen   •  FAQ   •  Mitgliederliste   •  Registrieren   •  Login
 usb connect not working on galaxy s3 Nächstes Thema anzeigen
Vorheriges Thema anzeigen
Neues Thema eröffnenNeue Antwort erstellen
Autor Nachricht
r0j0e



Anmeldedatum: 22.08.2014
Beiträge: 2

BeitragVerfasst am: Fr Aug 22, 2014 09:36 Antworten mit ZitatNach oben

downloaded the drivers, downloaded the client apps on both my phone and pc, even downloaded samsung kies, have developer options and usb debuggin enabled.

running 4.3 android. usb mode does not work. log is below for my gti9300 samsung galaxy s3. please help


Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.6
Datum: 2014/08/22

08:58:50.77 Setting Port: 999
08:58:50.77 Setting Baud: 115200
08:58:50.78 Avaiable Ports: COM1=\Device\Serial1; COM3=\Device\Serial0;
08:58:50.78 Main Load frmSplash
08:58:50.78 Load frmSplash...
08:58:50.78 Show splash...
08:58:50.79 frmSplash geladen
08:58:51.22 Hauptfenster wird geladen
08:58:51.32 Sidebar fertig geladen
08:58:51.41 UC SMS wird geladen
08:58:51.44 UC Phonebook wird geladen
08:58:51.46 UC Phonebook fertig geladen
08:58:51.46 UC Calls wird geladen
08:58:51.48 UC Organizer wird geladen
08:58:51.52 Organizer initiated
08:58:51.55 Startpage=1
08:58:51.55 UC Filebrowser wird geladen
08:58:51.59 UC Filebrowser fertig geladen
08:58:51.59 UC AppBrowser wird geladen
08:58:51.59 UC Notes wird geladen
08:58:51.60 UC Calls wird geladen
08:58:51.62 Setting Lastuser:
08:58:51.63 Lade Userdatenbank:
08:58:51.67 Kontakte geladen
08:58:51.67 ParseDialedCalls needed 0ms
08:58:51.69 Anrufe geladen
08:58:51.69 Organizer LoadUser DefaultTimeColWidth=135
08:58:51.69 Organizer geladen
08:58:51.69 Notizen geladen
08:58:51.69 SMS geladen
08:58:51.86 Hauptfenster fertig geladen
08:58:57.09 RunADBCommand: start-server
08:59:01.27 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
08:59:01.27 RunADBCommand: devices
08:59:01.32 ADB CommandResponse: List of devices attached
08:59:01.32 Run DeviceTracker
08:59:01.33 Init Tracker
08:59:01.33 Device Tracker Message: OKAY0000
08:59:01.33 Connect to Android failed!
08:59:01.33 bOpened=False
08:59:01.33 No device attached to USB
08:59:01.33 Refresh ComDescriptions...
08:59:01.33 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1E3D&SUBSYS_3397103C&REV_04\3&11583659&0&B3
08:59:01.33 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
08:59:01.33 ErrMsg: Connection to phone could not be established:
No device attached to USB
09:01:12.77 RunADBCommand: start-server
09:01:12.84 ADB CommandResponse:
09:01:12.84 RunADBCommand: devices
09:01:12.86 ADB CommandResponse: List of devices attached
09:01:12.86 Connect to Android failed!
09:01:12.87 bOpened=False
09:01:12.87 No device attached to USB
09:01:12.87 Refresh ComDescriptions...
09:01:12.87 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1E3D&SUBSYS_3397103C&REV_04\3&11583659&0&B3
09:01:12.87 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
09:01:12.87 ErrMsg: Connection to phone could not be established:
No device attached to USB
09:01:16.20 Refresh ComDescriptions...
09:01:16.20 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1E3D&SUBSYS_3397103C&REV_04\3&11583659&0&B3
09:01:16.20 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
09:01:25.70 OK pressed in settingswindow
09:01:25.77 Set first swap of settings
09:01:25.79 Apply new holidays
09:01:25.79 Holidays applied
09:01:25.80 Second swap of settings set
09:01:25.80 Everything is done
09:01:28.18 RunADBCommand: start-server
09:01:28.23 ADB CommandResponse:
09:01:28.23 RunADBCommand: devices
09:01:28.26 ADB CommandResponse: List of devices attached
09:01:28.26 Broadcaster started
09:01:28.26 Start UPnP Discovery
09:01:28.26 Sending broadcast
09:01:28.53 UPnP Device: Print Server ps-pit4
09:01:28.62 UPnP Device: AXIS M3203 - 00408CC5056F
09:01:28.75 UPnP Device: AXIS M3203 - 00408CC50574
09:01:28.76 Sending broadcast
09:01:28.81 UPnP Device: PIT0308
09:01:29.01 UPnP Device: AXIS P3353 - 00408CE367C7
09:01:29.26 Sending broadcast
09:01:29.46 UPnP Device: AXIS M3203 - 00408CC50570
09:01:29.53 UPnP Device: AXIS M3203 - 00408CE5C13A
09:01:29.90 UPnP Device: PIT0218
09:01:29.95 UPnP Device: AXIS M3024-L - 00408CEC2ECE
09:01:29.97 UPnP Device: PIT0209
09:01:30.34 UPnP Device: PIT0275
09:01:30.46 UPnP Device: PIT0212
09:01:30.66 UPnP Device: AXIS M3203 - 00408CC5056E
09:01:30.71 UPnP Device: PIT0309: NICHOLAW:
09:01:30.77 UPnP Device: AXIS M3203 - 00408CC50573
09:01:30.79 UPnP Device: AXIS P3353 - 00408CE367C5
09:01:30.93 UPnP Device: PIT0311
09:01:30.97 UPnP Device: PIT0312
09:01:30.99 UPnP Device: PIT0203
09:01:31.09 UPnP Device: PIT0188
09:01:31.15 UPnP Device: PIT0296
09:01:31.26 UPnP Device: PIT0145
09:01:31.84 UPnP Device: PIT0332
09:01:31.99 UPnP Device: AXIS M3203 - 00408CC1D958
09:01:32.04 UPnP Device: AXIS M3203 - 00408CC5056C
09:01:32.07 UPnP Device: PIT0372
09:01:32.20 UPnP Device: PIT0156
09:01:32.35 UPnP Device: PIT0269
09:01:32.38 UPnP Device: PIT0358
09:01:32.53 UPnP Device: PIT0267
09:01:33.26 Connect to Android failed!
09:01:33.26 bOpened=False
09:01:33.26 USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
09:01:33.26 Refresh ComDescriptions...
09:01:33.26 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1E3D&SUBSYS_3397103C&REV_04\3&11583659&0&B3
09:01:33.26 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
09:01:33.26 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
09:02:00.16 Closing Broadcaster
09:02:00.16 RunADBCommand: start-server
09:02:00.20 ADB CommandResponse:
09:02:00.20 RunADBCommand: devices
09:02:00.23 ADB CommandResponse: List of devices attached
09:02:00.23 Broadcaster started
09:02:00.23 Start UPnP Discovery
09:02:00.23 Sending broadcast
09:02:00.25 UPnP Device: PIT0212
09:02:00.25 UPnP Device: AXIS M3203 - 00408CC5056C
09:02:00.26 UPnP Device: AXIS M3024-L - 00408CEC2ECE
09:02:00.26 UPnP Device: PIT0311
09:02:00.26 UPnP Device: AXIS M3203 - 00408CC50574
09:02:00.26 UPnP Device: PIT0145
09:02:00.26 UPnP Device: AXIS M3203 - 00408CE5C13A
09:02:00.26 UPnP Device: PIT0332
09:02:00.26 UPnP Device: AXIS M3203 - 00408CC5056E
09:02:00.26 UPnP Device: AXIS M3203 - 00408CC50573
09:02:00.26 UPnP Device: PIT0275
09:02:00.26 UPnP Device: PIT0308
09:02:00.26 UPnP Device: AXIS M3203 - 00408CC50570
09:02:00.27 UPnP Device: AXIS M3203 - 00408CC5056F
09:02:00.27 UPnP Device: PIT0209
09:02:00.27 UPnP Device: AXIS P3353 - 00408CE367C7
09:02:00.27 UPnP Device: PIT0309: NICHOLAW:
09:02:00.27 UPnP Device: PIT0296
09:02:00.27 UPnP Device: AXIS P3353 - 00408CE367C5
09:02:00.27 UPnP Device: PIT0358
09:02:00.27 UPnP Device: AXIS M3203 - 00408CC1D958
09:02:00.27 UPnP Device: PIT0372
09:02:00.27 UPnP Device: PIT0269
09:02:00.27 UPnP Device: PIT0267
09:02:00.27 UPnP Device: PIT0203
09:02:00.38 UPnP Device: PIT0188
09:02:00.45 UPnP Device: PIT0156
09:02:00.45 UPnP Device: PIT0312
09:02:00.46 UPnP Device: PIT0218
09:02:00.47 UPnP Device: Print Server ps-pit4
09:02:00.75 Sending broadcast
09:02:01.26 Sending broadcast
09:02:05.24 Connect to Android failed!
09:02:05.24 bOpened=False
09:02:05.24 USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
09:02:05.24 Refresh ComDescriptions...
09:02:05.24 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1E3D&SUBSYS_3397103C&REV_04\3&11583659&0&B3
09:02:05.24 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
09:02:05.25 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
09:02:10.85 Closing Broadcaster
09:02:10.86 RunADBCommand: start-server
09:02:10.88 ADB CommandResponse:
09:02:10.88 RunADBCommand: devices
09:02:10.90 ADB CommandResponse: List of devices attached
09:02:10.90 Broadcaster started
09:02:10.90 Start UPnP Discovery
09:02:10.90 Sending broadcast
09:02:10.92 UPnP Device: AXIS M3203 - 00408CC5056F
09:02:10.92 UPnP Device: PIT0311
09:02:10.92 UPnP Device: PIT0209
09:02:10.92 UPnP Device: AXIS M3203 - 00408CC50574
09:02:10.92 UPnP Device: AXIS M3203 - 00408CC50573
09:02:10.92 UPnP Device: PIT0308
09:02:10.92 UPnP Device: AXIS M3203 - 00408CE5C13A
09:02:10.92 UPnP Device: PIT0358
09:02:10.93 UPnP Device: PIT0275
09:02:10.93 UPnP Device: PIT0203
09:02:10.93 UPnP Device: PIT0145
09:02:10.93 UPnP Device: AXIS P3353 - 00408CE367C7
09:02:10.93 UPnP Device: PIT0212
09:02:10.93 UPnP Device: AXIS P3353 - 00408CE367C5
09:02:10.93 UPnP Device: AXIS M3203 - 00408CC5056C
09:02:10.93 UPnP Device: PIT0269
09:02:10.93 UPnP Device: AXIS M3203 - 00408CC50570
09:02:10.93 UPnP Device: PIT0296
09:02:10.93 UPnP Device: AXIS M3203 - 00408CC1D958
09:02:10.93 UPnP Device: PIT0309: NICHOLAW:
09:02:10.93 UPnP Device: AXIS M3203 - 00408CC5056E
09:02:10.93 UPnP Device: PIT0332
09:02:10.94 UPnP Device: PIT0188
09:02:10.94 UPnP Device: PIT0372
09:02:10.94 UPnP Device: PIT0267
09:02:10.94 UPnP Device: AXIS M3024-L - 00408CEC2ECE
09:02:11.12 UPnP Device: PIT0218
09:02:11.12 UPnP Device: PIT0312
09:02:11.12 UPnP Device: PIT0156
09:02:11.13 UPnP Device: Print Server ps-pit4
09:02:11.42 Sending broadcast
09:02:11.93 Sending broadcast
09:02:15.91 Connect to Android failed!
09:02:15.91 bOpened=False
09:02:15.91 USB cable: No device attached to USB
WiFi: Failed to obtain the IP-address of the phone
09:02:15.91 Refresh ComDescriptions...
09:02:15.92 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1E3D&SUBSYS_3397103C&REV_04\3&11583659&0&B3
09:02:15.92 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
09:02:15.92 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
09:03:04.24 Refresh ComDescriptions...
09:03:04.24 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1E3D&SUBSYS_3397103C&REV_04\3&11583659&0&B3
09:03:04.24 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
09:03:05.50 Device driver info:
09:03:05.50 Devices with ADB Interface:
09:03:05.55 ADB Devices:
09:03:05.55 Portable devices: GT-I9300
09:03:05.55 Unknown devices:
Benutzer-Profile anzeigenPrivate Nachricht senden
DBoydNL



Anmeldedatum: 02.09.2014
Beiträge: 4

BeitragVerfasst am: Di Sep 02, 2014 15:19 Antworten mit ZitatNach oben

Uhm, my Galaxy S3 is running Android 2.3.6.
I used to be able to connect USB and synchronize. Didn't do it all summer long. Tried again today: cannot connect. No USB device connected. The advice to make sure that the ADB drivers for my phone are installed is incredibly unhelpful. How about giving a link and instructions on how to do that.

I thought I followed instructions and it ended up installing Kies, which made no difference what so ever.

Like I said: this USED to work. Now, it no longer does. Debugging is still turned on on my phone.

No idea what to do.

D. Boyd
Benutzer-Profile anzeigenPrivate Nachricht senden
r0j0e



Anmeldedatum: 22.08.2014
Beiträge: 2

BeitragVerfasst am: Di Sep 02, 2014 16:16 Antworten mit ZitatNach oben

DBoydNL hat Folgendes geschrieben:
Uhm, my Galaxy S3 is running Android 2.3.6.
I used to be able to connect USB and synchronize. Didn't do it all summer long. Tried again today: cannot connect. No USB device connected. The advice to make sure that the ADB drivers for my phone are installed is incredibly unhelpful. How about giving a link and instructions on how to do that.

I thought I followed instructions and it ended up installing Kies, which made no difference what so ever.

Like I said: this USED to work. Now, it no longer does. Debugging is still turned on on my phone.

No idea what to do.

D. Boyd


don't you want to update your android version? i think it said somewhere that the most recent versions only support the last few android releases, 2.3.6 is very old.
Benutzer-Profile anzeigenPrivate Nachricht senden
FJ
Site Admin


Anmeldedatum: 15.02.2006
Beiträge: 31928
Wohnort: Tirol

BeitragVerfasst am: Fr Sep 05, 2014 22:15 Antworten mit ZitatNach oben

It seems that the AFB-Drivers were not installed. They are included in Samsung KIES

_________________
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
Benutzer-Profile anzeigenPrivate Nachricht sendenE-Mail sendenICQ-Nummer
Beiträge der letzten Zeit anzeigen:      
Neues Thema eröffnenNeue Antwort erstellen


 Gehe zu:   



Nächstes Thema anzeigen
Vorheriges Thema anzeigen
Du kannst keine Beiträge in dieses Forum schreiben.
Du kannst auf Beiträge in diesem Forum nicht antworten.
Du kannst deine Beiträge in diesem Forum nicht bearbeiten.
Du kannst deine Beiträge in diesem Forum nicht löschen.
Du kannst an Umfragen in diesem Forum nicht mitmachen.

Powered by phpBB © 2001, 2002 phpBB Group :: FI Theme :: Alle Zeiten sind GMT + 1 Stunde
Deutsche Übersetzung von phpBB.de