MyPhoneExplorer suddenly won't connect

Anmeldedatum: 04.06.2012 Beiträge: 19

I suddenly cannot connect my Google Nexus 4 with MyPhoneExplorer. It has worked perfectly up until now and just suddenly stopped for no reason.

Yes, the client is running
Yes, USB debugging is on
Yes, the phone drivers have been installed and reinstalled
Yes, ADB has been installed and reinstalled
Yes, I am able to connect to the device using ADB in the command line
Yes, the client and desktop are the correct corresponding versions
Yes, I've tried rebooting both devices
Yes, I've tried different cables
Yes, I've tried different ports
Yes, I've tried clearing the data folder and INI file
Yes, I've reinstalled the client on my phone

I cannot, for the life of me, figure out what is going on here and I'm pulling my hair out!

Here is the debug log:

Code:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.4
Datum: 2013-02-26

18:40:48.22 Setting Port: 999
18:40:48.22 Setting Baud: 115200
18:40:48.22 Avaiable Ports: COM3=Winachsf0;
18:40:48.22 Main Load frmSplash
18:40:48.24 Load frmSplash...
18:40:48.24 Show splash...
18:40:48.24 frmSplash geladen
18:40:48.83 Hauptfenster wird geladen
18:40:49.00 Sidebar fertig geladen
18:40:49.13 UC SMS wird geladen
18:40:49.17 UC Phonebook wird geladen
18:40:49.22 UC Phonebook fertig geladen
18:40:49.22 UC Calls wird geladen
18:40:49.27 UC Organizer wird geladen
18:40:49.42 Organizer initiated
18:40:49.45 Startpage=2
18:40:49.48 DoItemUpdate
18:40:49.53 DoItemUpdate fertig
18:40:49.53 UC Filebrowser wird geladen
18:40:49.61 UC Filebrowser fertig geladen
18:40:49.61 UC AppBrowser wird geladen
18:40:49.62 UC Notes wird geladen
18:40:49.64 UC Calls wird geladen
18:40:49.69 Setting Lastuser: LGE Nexus 4 [353918056022490]
18:40:49.70 Lade Userdatenbank: LGE Nexus 4 [353918056022490]
18:40:49.73 LoadDatafile: pb_metadata.xml(3074 Bytes)
18:40:49.73 LoadDatafile: Phonebook.dat(50131 Bytes)
18:40:50.06 Kontakte geladen
18:40:50.06 LoadDatafile: Calls.dat(23779 Bytes)
18:40:50.56 Anrufe geladen
18:40:50.56 Organizer LoadUser DefaultTimeColWidth=99
18:40:50.59 LoadDatafile: Organizer.dat(187360 Bytes)
18:40:50.98 LoadDatafile: cal_metadata.xml(299 Bytes)
18:40:50.98 DoItemUpdate
18:40:51.06 DoItemUpdate fertig
18:40:51.34 Organizer geladen
18:40:51.34 LoadDatafile: Notes.dat(2853 Bytes)
18:40:51.36 Notizen geladen
18:40:51.36 Load SMS Data...
18:40:51.37 LoadDatafile: SMS.dat(713482 Bytes)
18:40:51.37 SMS - Datenbank wird geladen...
18:40:52.78 SMS Laden - Readfile: 16 Split: 16 Parse: 1372 HandleMultiSMS: 16 Nachrichten: 4425
18:40:52.81 LoadDatafile: SMSArchive.dat(2321238 Bytes)
18:40:53.24 SMS Archiv laden - Parse: 468
18:40:56.14 RefreshList (Archive): Addrows=1357 Sort=749 MenuUpdate=31 Redraw=16
18:40:57.24 SMS Data Loaded...
18:40:57.24 SMS geladen
18:40:57.72 Hauptfenster fertig geladen
18:40:57.82 Init Android Connection for future connect via USB
18:40:57.82 RunADBCommand: start-server
18:41:01.93 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
18:41:01.93 Run DeviceTracker
18:41:01.95 Init Tracker
18:41:01.98 Device Tracker Message: OKAY0000
18:43:05.63 Device Tracker Message: 0019007aab7cc5112a9e offline

18:43:21.37 RunADBCommand: start-server
18:43:21.43 ADB CommandResponse:
18:43:21.43 RunADBCommand: devices
18:43:21.49 ADB CommandResponse: List of devices attached
007aab7cc5112a9e offline
18:43:21.49 RunADBCommand: forward tcp:5210 tcp:5210
18:43:21.54 ADB CommandResponse:
18:43:21.54 Try connecting to 127.0.0.1...
18:43:22.05 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
18:43:22.10 ADB CommandResponse:
18:43:22.10 Try launch USB connection
18:43:22.71 Try launch USB connection
18:43:23.30 Try launch USB connection
18:43:23.91 Try launch USB connection
18:43:24.50 Try launch USB connection
18:43:25.11 Try launch USB connection
18:43:25.71 Try launch USB connection
18:43:26.31 Connect to Android failed!
18:43:26.31 bOpened=False
18:43:26.31 Refresh ComDescriptions...
18:43:26.31 MODEM: COM3 Enumerator=HDAUDIO Displayed=ThinkPad Modem FriendlyName=ThinkPad Modem InstanceID=HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_17AA201B&REV_0900\4&151A0ED9&0&0102
18:43:26.31 ErrMsg: Connection to phone could not be established!
18:44:24.60 RunADBCommand: start-server
18:44:24.64 ADB CommandResponse:
18:44:24.64 RunADBCommand: devices
18:44:24.71 ADB CommandResponse: List of devices attached
007aab7cc5112a9e offline
18:44:24.71 RunADBCommand: forward tcp:5210 tcp:5210
18:44:24.75 ADB CommandResponse:
18:44:24.75 Try connecting to 127.0.0.1...
18:44:25.27 RunADBCommand: shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
18:44:25.32 ADB CommandResponse:
18:44:25.32 Try launch USB connection
18:44:25.92 Try launch USB connection
18:44:26.52 Try launch USB connection
18:44:27.13 Try launch USB connection
18:44:27.72 Try launch USB connection
18:44:28.33 Try launch USB connection
18:44:28.92 Try launch USB connection
18:44:29.53 Connect to Android failed!
18:44:29.53 bOpened=False
18:44:29.53 Refresh ComDescriptions...
18:44:29.53 MODEM: COM3 Enumerator=HDAUDIO Displayed=ThinkPad Modem FriendlyName=ThinkPad Modem InstanceID=HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_17AA201B&REV_0900\4&151A0ED9&0&0102
18:44:29.53 ErrMsg: Connection to phone could not be established!

Verfasst am: Mi Feb 27, 2013 19:58

epp_b,

have you read this thread?

Greetings
dupondt

Anmeldedatum: 10.02.2013 Beiträge: 12

Can U connect with USB or Bluetooth?

I've had a similar problem, & the only way it was corrected was to deploy a backup copy of my PC's operating system when MPE was working fine.
My system restore would not restore because some files were erased. U might try restoring your OS to before the MPE problem.

Please post back your results.

Anmeldedatum: 04.06.2012 Beiträge: 19

I can connect via wifi, but not USB. I have tried this on two different computers now, same result.

EDIT: Also, I just upgraded adb and authorized the phone as instructed on that link. Still doesn't work.

EDIT #2: never mind, I hadn't realized that MPE needs it's own isolated copy of ADB.

Anmeldedatum: 05.10.2011 Beiträge: 1

MPE can apparently only communicate with one computer at a time. I noticed this when I installed the MPE on my laptop. I could not then get in contact with my PC until I shut down the MPE on my laptop.

Informationen zum Datenschutz auf dieser Website