Autor |
Nachricht |
danielfsr1003
Anmeldedatum: 13.01.2014
Beiträge: 1
Wohnort: United States
|
Verfasst am:
Di Jan 14, 2014 00:07 |
  |
Dear all,
After updating my phone to the last version of the android system, I'm not able to connect my phone to MyPhoneExplorer.
I already downloaded the latest version of the drivers, Kies suite and still is not working, the debugin option is selected so no clue
See below the log that I received when trying to do the sync.
Any help here is much appreciated,
Thank you very much.
Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.5
Datum: 1/13/2014
16:15:15.33 Setting Port: 999
16:15:15.33 Setting Baud: 115200
16:15:15.33 Avaiable Ports: COM1=\Device\Serial0; COM3=\Device\ssudmdm0000;
16:15:15.37 Main Load frmSplash
16:15:15.49 Load frmSplash...
16:15:15.50 Show splash...
16:15:15.51 frmSplash geladen
16:15:17.05 Hauptfenster wird geladen
16:15:18.15 Sidebar fertig geladen
16:15:18.84 UC SMS wird geladen
16:15:18.89 UC Phonebook wird geladen
16:15:18.93 UC Phonebook fertig geladen
16:15:18.93 UC Calls wird geladen
16:15:18.97 UC Organizer wird geladen
16:15:19.06 Organizer initiated
16:15:19.09 Startpage=3
16:15:19.10 UC Filebrowser wird geladen
16:15:19.27 UC Filebrowser fertig geladen
16:15:19.27 UC AppBrowser wird geladen
16:15:19.28 UC Notes wird geladen
16:15:19.30 UC Calls wird geladen
16:15:19.57 RunADBCommand: start-server
16:15:19.86 ADB CommandResponse:
16:15:19.86 RunADBCommand: devices
16:15:19.90 ADB CommandResponse: List of devices attached
c5b114f2 offline
16:15:19.90 Run DeviceTracker
16:15:19.94 Init Tracker
16:15:19.94 Device Tracker Message: OKAY0011c5b114f2 offline
16:15:19.94 RunADBCommand: forward tcp:5210 tcp:5210
16:15:19.98 ADB CommandResponse:
16:15:19.99 Try connecting to 127.0.0.1...
16:15:20.50 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
16:15:20.54 ADB CommandResponse:
16:15:20.54 Try launch USB connection
16:15:21.14 Try launch USB connection
16:15:21.73 Try launch USB connection
16:15:22.34 Try launch USB connection
16:15:22.93 Try launch USB connection
16:15:23.54 Try launch USB connection
16:15:24.13 Try launch USB connection
16:15:24.75 Connect to Android failed!
16:15:24.75 bOpened=False
16:15:24.75 Refresh ComDescriptions...
16:15:24.80 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
16:15:24.80 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&123261C1&2&0001
16:15:24.80 ErrMsg (Silent): Connection to phone could not be established!
16:15:25.66 Setting Lastuser: samsung SAMSUNG-SGH-I747 [IMEI]
16:15:25.68 Lade Userdatenbank: samsung SAMSUNG-SGH-I747 [IMEI]
16:15:25.92 LoadDatafile: pb_metadata.xml(4054 Bytes)
16:15:25.98 LoadDatafile: Phonebook.dat(21007 Bytes)
16:15:26.12 Kontakte geladen
16:15:26.17 LoadDatafile: Calls.dat(34144 Bytes)
16:15:26.22 ParseDialedCalls needed 16ms
16:15:26.65 Anrufe geladen
16:15:26.66 Organizer LoadUser DefaultTimeColWidth=112
16:15:26.79 LoadDatafile: Organizer.dat(240462 Bytes)
16:15:27.22 LoadDatafile: cal_metadata.xml(688 Bytes)
16:15:27.54 Organizer geladen
16:15:27.55 LoadDatafile: notes_metadata.xml(114 Bytes)
16:15:27.55 Notizen geladen
16:15:29.59 Refresh ComDescriptions...
16:15:29.59 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
16:15:29.60 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&123261C1&2&0001
16:15:30.62 StickyNotesPath=C:\Windows\system32\StikyNot.exe FileExists=True
16:15:30.66 StickyNotesTitle=Sticky Notes  |
_________________ Daniel S. |
|
   |
 |
dgleaner
Anmeldedatum: 14.01.2014
Beiträge: 1
|
Verfasst am:
Di Jan 14, 2014 19:31 |
  |
|
  |
 |
jsyeed
Anmeldedatum: 14.01.2014
Beiträge: 1
|
Verfasst am:
Di Jan 14, 2014 23:53 |
  |
here is my debug log
Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.5
Datum: 15/01/2014
08:45:19.30 Setting Port: 999
08:45:19.30 Setting Baud: 115200
08:45:19.30 Avaiable Ports: COM1=\Device\Serial1; COM3=\Device\Serial0;
08:45:19.30 Main Load frmSplash
08:45:19.32 Load frmSplash...
08:45:19.32 Show splash...
08:45:19.33 frmSplash geladen
08:45:19.86 Hauptfenster wird geladen
08:45:19.94 Sidebar fertig geladen
08:45:19.97 UC SMS wird geladen
08:45:19.99 UC Phonebook wird geladen
08:45:20.00 UC Phonebook fertig geladen
08:45:20.00 UC Calls wird geladen
08:45:20.04 UC Organizer wird geladen
08:45:20.08 Organizer initiated
08:45:20.10 Startpage=1
08:45:20.10 UC Filebrowser wird geladen
08:45:20.15 UC Filebrowser fertig geladen
08:45:20.15 UC AppBrowser wird geladen
08:45:20.15 UC Notes wird geladen
08:45:20.15 UC Calls wird geladen
08:45:20.18 Setting Lastuser:
08:45:20.19 Lade Userdatenbank:
08:45:20.19 Kontakte geladen
08:45:20.19 ParseDialedCalls needed 0ms
08:45:20.24 Anrufe geladen
08:45:20.24 Organizer LoadUser DefaultTimeColWidth=112
08:45:20.24 Organizer geladen
08:45:20.24 Notizen geladen
08:45:20.24 SMS geladen
08:45:20.57 Hauptfenster fertig geladen
08:45:21.79 Downloader: RC=0 BytesMax=0 URL=http://www.fjsoft.at/myphoneexplorer/version.txt
08:45:23.52 RunADBCommand: start-server
08:45:27.61 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
08:45:27.61 RunADBCommand: devices
08:45:27.66 ADB CommandResponse: List of devices attached
08:45:27.66 Run DeviceTracker
08:45:27.68 Init Tracker
08:45:27.68 Device Tracker Message: OKAY0000
08:45:27.68 Connect to Android failed!
08:45:27.68 bOpened=False
08:45:27.68 No device attached to USB
08:45:27.68 Refresh ComDescriptions...
08:45:27.88 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
08:45:27.88 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1D3D&SUBSYS_102617AA&REV_05\3&11583659&0&B3
08:45:28.08 ErrMsg: Connection to phone could not be established:
No device attached to USB
08:45:50.74 Refresh ComDescriptions...
08:45:50.91 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
08:45:50.91 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1D3D&SUBSYS_102617AA&REV_05\3&11583659&0&B3
08:45:51.71 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False |
|
|
  |
 |
schneid
Anmeldedatum: 15.01.2014
Beiträge: 1
|
Verfasst am:
Mi Jan 15, 2014 00:45 |
  |
I am rooted with the MDK bootloader with and JB 4.3 Verizon ML1 custom ROM. This app works fine. Maybe it is do the new locked bootloader and Knox. |
|
|
  |
 |
FJ
Site Admin
Anmeldedatum: 15.02.2006
Beiträge: 31928
Wohnort: Tirol
|
Verfasst am:
So Jan 19, 2014 14:28 |
  |
Known Android problem which came with the update to 4.3.
Solution: Below the setting "USB Debugging" in the developer options of the phone you should find something like "Revoke USB debugging authorizations", choose this, plug in your phone again and then confirm the security prompt which is shown when you try to connect with MyPhoneExplorer. |
_________________ 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 |
|
    |
 |
MJA
Anmeldedatum: 25.01.2014
Beiträge: 2
|
Verfasst am:
Sa Jan 25, 2014 20:14 |
  |
I have tried everything: downloaded the latest version of MPE; downloaded the USB (ADB) drivers for Samsung Galaxy S3; enabled USB debugging; revoked previous USB debugging authorisations. Still no joy; get the same message every time - cannot establish connection to phone. Log below. Please can you help as I depend on this!
************************
Programmversion: 1.8.5
Datum: 25/01/2014
17:46:11.32 Setting Port: 999
17:46:11.32 Setting Baud: 115200
17:46:11.32 Avaiable Ports: COM3=\Device\ssudmdm0000;
17:46:11.32 Main Load frmSplash
17:46:11.32 Load frmSplash...
17:46:11.32 Show splash...
17:46:11.35 frmSplash geladen
17:46:11.85 Hauptfenster wird geladen
17:46:12.12 Sidebar fertig geladen
17:46:12.20 UC SMS wird geladen
17:46:12.25 UC Phonebook wird geladen
17:46:12.29 UC Phonebook fertig geladen
17:46:12.29 UC Calls wird geladen
17:46:12.35 UC Organizer wird geladen
17:46:12.46 Organizer initiated
17:46:12.54 Startpage=1
17:46:12.54 UC Filebrowser wird geladen
17:46:12.63 UC Filebrowser fertig geladen
17:46:12.63 UC AppBrowser wird geladen
17:46:12.65 UC Notes wird geladen
17:46:12.67 UC Calls wird geladen
17:46:12.75 Setting Lastuser: samsung GT-I9305 [IMEI]
17:46:12.76 Lade Userdatenbank: samsung GT-I9305 [IMEI]
17:46:12.81 LoadDatafile: pb_metadata.xml(2902 Bytes)
17:46:12.82 LoadDatafile: Phonebook.dat(572250 Bytes)
17:46:15.42 Kontakte geladen
17:46:15.45 LoadDatafile: Calls.dat(844 Bytes)
17:46:15.46 ParseDialedCalls needed 16ms
17:46:15.59 Anrufe geladen
17:46:15.59 Organizer LoadUser DefaultTimeColWidth=101
17:46:15.62 LoadDatafile: Organizer.dat(172352 Bytes)
17:46:16.38 LoadDatafile: cal_metadata.xml(1013 Bytes)
17:46:16.71 Organizer geladen
17:46:16.73 LoadDatafile: Notes.dat(8146 Bytes)
17:46:16.78 Notizen geladen
17:46:16.78 Load SMS Data...
17:46:16.78 LoadDatafile: SMS.dat(353602 Bytes)
17:46:16.78 SMS - Datenbank wird geladen...
17:46:18.07 SMS Laden - Readfile: 0 Split: 16 Parse: 1266 HandleMultiSMS: 15 Nachrichten: 1634
17:46:18.71 RefreshList (Archive): Addrows=0 Sort=0 MenuUpdate=0 Redraw=0
17:46:19.25 SMS Data Loaded...
17:46:19.25 SMS geladen
17:46:19.68 Hauptfenster fertig geladen
17:46:19.79 Init Android Connection for future connect via USB
17:46:19.79 RunADBCommand: start-server
17:46:23.95 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
17:46:23.95 Run DeviceTracker
17:46:23.98 Init Tracker
17:46:24.01 Device Tracker Message: OKAY001942f721159f4e8fc3 offline
17:46:26.68 RunADBCommand: start-server
17:46:27.37 ADB CommandResponse:
17:46:27.37 RunADBCommand: devices
17:46:27.45 ADB CommandResponse: List of devices attached
42f721159f4e8fc3 offline
17:46:27.45 RunADBCommand: forward tcp:5210 tcp:5210
17:46:27.51 ADB CommandResponse:
17:46:27.51 Try connecting to 127.0.0.1...
17:46:28.03 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
17:46:28.09 ADB CommandResponse:
17:46:28.09 Try launch USB connection
17:46:28.70 Try launch USB connection
17:46:29.29 Try launch USB connection
17:46:29.90 Try launch USB connection
17:46:30.50 Try launch USB connection
17:46:31.09 Try launch USB connection
17:46:31.70 Try launch USB connection
17:46:32.29 Connect to Android failed!
17:46:32.29 bOpened=False
17:46:32.29 Refresh ComDescriptions...
17:46:32.42 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&159F6D9E&1&0001
17:46:32.42 ErrMsg: Connection to phone could not be established!
17:51:11.38 Refresh ComDescriptions...
17:51:11.53 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&159F6D9E&1&0001
17:51:12.04 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False
17:51:44.78 OK pressed in settingswindow
17:51:44.87 Set first swap of settings
17:51:44.88 Apply new holidays
17:51:44.90 Holidays applied
17:51:44.90 Second swap of settings set
17:51:44.90 Everything is done
17:52:12.62 RunADBCommand: start-server
17:52:12.71 ADB CommandResponse:
17:52:12.71 RunADBCommand: devices
17:52:12.79 ADB CommandResponse: List of devices attached
42f721159f4e8fc3 offline
17:52:12.79 RunADBCommand: forward tcp:5210 tcp:5210
17:52:12.85 ADB CommandResponse:
17:52:12.85 Try connecting to 127.0.0.1...
17:52:13.37 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
17:52:13.43 ADB CommandResponse:
17:52:13.43 Try launch USB connection
17:52:14.04 Try launch USB connection
17:52:14.63 Try launch USB connection
17:52:15.25 Try launch USB connection
17:52:15.84 Try launch USB connection
17:52:16.43 Try launch USB connection
17:52:17.04 Try launch USB connection
17:52:17.63 Connect to Android failed!
17:52:17.63 bOpened=False
17:52:17.63 Refresh ComDescriptions...
17:52:17.76 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&159F6D9E&1&0001
17:52:17.76 ErrMsg: Connection to phone could not be established!
17:52:24.78 RunADBCommand: start-server
17:52:24.85 ADB CommandResponse:
17:52:24.85 RunADBCommand: devices
17:52:24.93 ADB CommandResponse: List of devices attached
42f721159f4e8fc3 offline
17:52:24.93 RunADBCommand: forward tcp:5210 tcp:5210
17:52:25.00 ADB CommandResponse:
17:52:25.00 Try connecting to 127.0.0.1...
17:52:25.51 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
17:52:25.57 ADB CommandResponse:
17:52:25.57 Try launch USB connection
17:52:26.18 Try launch USB connection
17:52:26.78 Try launch USB connection
17:52:27.38 Try launch USB connection
17:52:27.98 Try launch USB connection
17:52:28.57 Try launch USB connection
17:52:29.18 Try launch USB connection
17:52:29.78 Connect to Android failed!
17:52:29.78 bOpened=False
17:52:29.78 Refresh ComDescriptions...
17:52:29.90 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&159F6D9E&1&0001
17:52:29.90 ErrMsg: Connection to phone could not be established!
17:56:13.35 Refresh ComDescriptions...
17:56:13.50 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&159F6D9E&1&0001
17:56:14.01 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False
17:58:07.01 OK pressed in settingswindow
17:58:07.07 Set first swap of settings
17:58:07.09 Apply new holidays
17:58:07.09 Holidays applied
17:58:07.10 Second swap of settings set
17:58:07.10 Everything is done
17:58:17.84 RunADBCommand: start-server
17:58:17.90 ADB CommandResponse:
17:58:17.90 RunADBCommand: devices
17:58:17.98 ADB CommandResponse: List of devices attached
42f721159f4e8fc3 offline
17:58:17.98 RunADBCommand: forward tcp:5210 tcp:5210
17:58:18.04 ADB CommandResponse:
17:58:18.04 Try connecting to 127.0.0.1...
17:58:18.56 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
17:58:18.62 ADB CommandResponse:
17:58:18.62 Try launch USB connection
17:58:19.23 Try launch USB connection
17:58:19.82 Try launch USB connection
17:58:20.43 Try launch USB connection
17:58:21.03 Try launch USB connection
17:58:21.62 Try launch USB connection
17:58:22.23 Try launch USB connection
17:58:22.82 Connect to Android failed!
17:58:22.82 bOpened=False
17:58:22.82 Refresh ComDescriptions...
17:58:22.93 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&159F6D9E&1&0001
17:58:22.95 ErrMsg: Connection to phone could not be established!
17:58:28.51 Refresh ComDescriptions...
17:58:28.63 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\6&159F6D9E&1&0001
17:58:29.15 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False |
|
|
  |
 |
MJA
Anmeldedatum: 25.01.2014
Beiträge: 2
|
Verfasst am:
Sa Jan 25, 2014 20:33 |
  |
It seems that Windows Security Centre was blocking some aspects of MPE on my computer. I got a dialogue box telling me this and giving me the option of allowing access, which I did. After this I got the security prompt on my phone that I hadn't had before and - for now at any rate - things seem to be syncing OK! Thanks very much for the excellent advice in the FAQ and this string. |
|
|
  |
 |
steveisonlinenow
Anmeldedatum: 28.01.2014
Beiträge: 1
|
Verfasst am:
Di Jan 28, 2014 16:15 |
  |
I followed the instrcutiosn and it worked for me. I didnt have the USB debugging option under developers under settings. I had to go to ABOUT DEVICE under SETTING , scroll down to BUILD (its greyed out) , press it 7 times (I know!) and on the 5th press it tells you you are 2 steps away from beign a deveoper. Carry on until 7th press or it telsls you you are a developer. Go back to SETTING and I saw Deveoper OPtions. Press that and scrolled to USB DEBUGGING . Under that is also REVOKE USb debugging autorization. Click on REVOKE USB AUTORIZATION and got a securty mesage. Accepted it. Unplugged phone from PC and then shut down and loaded back up again Phoen Eexporer on the PC and then got a security message on the PHONE S3 - RSA token ... do you want to accept. Hit ACCEPT and then it connected to the PC . Hope this helps others. |
|
|
  |
 |
|