FJ Software

Can I please get some quality help with MyPhoneExplorer 1.82?

This application worked OK for a few months then stopped working.
I have spent days trying to get this to work again.

I have updated All ADB drivers.
Uninstalled, reinstalled all Samsung drivers to SAMSUNG USB Drivers for Mobile Phones_1.5.4.0.
Re Installed MyPhoneExplorer_DebugUpdate.exe.
Updated MyPhoneExplorer client via Android Market to v 1.0.18.

I finally got it working.
Then I rebooted, and again MyPhoneExplorer cannot connect to the device. Other PC apps such as QtADB and Odin are able to connect to phone consistently while MPE cannot. USB Debugging on device is ON.

I am a seasoned mainframe software engineer. I like MyPhoneExplorer but in all honesty this is getting to the point that my time is better spent investing in other software that can reliably connect, not just once in a while but on a regular basis. I only rely on MyPhoneExplorer for USB connection.

Log appears at the end of this message.

Thank you.

David
Windows XP Pro SP3
Samsung Galaxy S I9000

***** Begin Log File *****

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.2
Datum: 5/6/2012

12:35:49.26 Setting Port: 999
12:35:49.26 Setting Baud: 115200
12:35:49.29 Avaiable Ports: COM3=\Device\ssadmdm0;
12:35:49.53 Main Load frmSplash
12:35:49.57 Load frmSplash...
12:35:50.60 Hauptfenster wird geladen
12:35:50.87 Sidebar fertig geladen
12:35:51.12 UC SMS wird geladen
12:35:51.26 UC Phonebook wird geladen
12:35:51.38 UC Phonebook fertig geladen
12:35:51.38 UC Calls wird geladen
12:35:51.50 UC Organizer wird geladen
12:35:51.71 Organizer initiated
12:35:51.78 Startpage=1
12:35:51.79 UC Filebrowser wird geladen
12:35:51.90 UC Filebrowser fertig geladen
12:35:51.92 UC AppBrowser wird geladen
12:35:51.93 UC Notes wird geladen
12:35:51.95 UC Calls wird geladen
12:35:52.31 Broadcaster started
12:35:52.34 Sending broadcast
12:35:52.84 Sending broadcast
12:35:53.34 Sending broadcast
12:35:54.26 Closing Broadcaster
12:35:54.26 RunADBCommand: start-server
12:35:59.04 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
12:35:59.04 RunADBCommand: devices
12:35:59.17 ADB CommandResponse: List of devices attached
3733xxxxxxxx00EC device
12:35:59.17 Run DeviceTracker
12:35:59.21 Init Tracker
12:35:59.25 Device Tracker Message: OKAY00183733xxxxxxxx00EC device

12:35:59.25 RunADBCommand: -s 3733xxxxxxxx00EC forward tcp:5210 tcp:5210
12:35:59.35 ADB CommandResponse:
12:35:59.35 Try connecting to 127.0.0.1...
12:35:59.37 Socket closed
12:35:59.37 RunADBCommand: -s 3733xxxxxxxx00EC shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
12:35:59.85 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }
12:36:00.01 Try launch USB connection
12:36:00.06 Socket closed
12:36:00.32 Try launch USB connection
12:36:00.34 Socket closed
12:36:00.62 Try launch USB connection
12:36:00.63 Socket closed
12:36:00.92 Try launch USB connection
12:36:00.93 Socket closed
12:36:01.21 Try launch USB connection
12:36:01.23 Socket closed
12:36:01.51 Try launch USB connection
12:36:01.53 Socket closed
12:36:01.82 Try launch USB connection
12:36:01.84 Socket closed
12:36:02.12 Try launch USB connection
12:36:02.13 Socket closed
12:36:02.42 Try launch USB connection
12:36:02.43 Socket closed
12:36:02.71 Try launch USB connection
12:36:02.73 Socket closed
12:36:03.01 Try launch USB connection
12:36:03.03 Socket closed
12:36:03.32 Try launch USB connection
12:36:03.34 Socket closed
12:36:03.62 Try launch USB connection
12:36:03.63 Socket closed
12:36:03.92 Try launch USB connection
12:36:03.93 Socket closed
12:36:04.21 Connect to Android failed!
12:36:04.23 bOpened=False
12:36:04.25 Refresh ComDescriptions...
12:36:04.50 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_681C&MI_00\3733xxxxxxxx00EC_00
12:36:04.51 ErrMsg (Silent): Connection to phone could not be established!
12:36:04.60 Setting Lastuser: samsung GT-I9000 [3532xxxxxxx4455]
12:36:04.63 Lade Userdatenbank: samsung GT-I9000 [3532xxxxxxx4455]
12:36:04.85 LoadDatafile: Phonebook.dat(41135 Bytes)
12:36:05.20 Kontakte geladen
12:36:05.26 LoadDatafile: Calls.dat(210 Bytes)
12:36:05.32 Anrufe geladen
12:36:05.32 Organizer LoadUser DefaultTimeColWidth=210
12:36:05.40 LoadDatafile: Organizer.dat(222 Bytes)
12:36:05.45 Organizer geladen
12:36:05.46 LoadDatafile: Notes.dat(2231 Bytes)
12:36:05.50 Notizen geladen
12:36:05.50 Load SMS Data...
12:36:05.51 LoadDatafile: SMS.dat(124 Bytes)
12:36:05.51 SMS - Datenbank wird geladen...
12:36:05.53 SMS Laden - Readfile: 16 Split: 0 Parse: 15 HandleMultiSMS: 0 Nachrichten: 2
12:36:05.56 RefreshList (Archive): Addrows=0 Sort=0 MenuUpdate=0 Redraw=0
12:36:05.57 SMS Data Loaded...
12:36:05.57 SMS geladen
12:36:05.79 Hauptfenster fertig geladen
12:36:05.90 Init Android Connection for future connect via WiFi
12:36:05.90 Broadcaster started
12:37:24.92 Sending broadcast
12:37:25.42 Sending broadcast
12:37:25.92 Sending broadcast
12:37:26.92 Closing Broadcaster
12:37:26.92 RunADBCommand: start-server
12:37:27.03 ADB CommandResponse:
12:37:27.03 RunADBCommand: devices
12:37:27.15 ADB CommandResponse: List of devices attached
3733xxxxxxxx00EC device
12:37:27.15 RunADBCommand: -s 3733xxxxxxxx00EC forward tcp:5210 tcp:5210
12:37:27.26 ADB CommandResponse:
12:37:27.26 Try connecting to 127.0.0.1...
12:37:27.31 Socket closed
12:37:27.31 RunADBCommand: -s 3733xxxxxxxx00EC shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
12:37:27.88 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }
12:37:28.04 Try launch USB connection
12:37:28.06 Socket closed
12:37:28.35 Try launch USB connection
12:37:28.37 Socket closed
12:37:28.65 Try launch USB connection
12:37:28.67 Socket closed
12:37:28.95 Try launch USB connection
12:37:28.96 Socket closed
12:37:29.25 Try launch USB connection
12:37:29.26 Socket closed
12:37:29.54 Try launch USB connection
12:37:29.56 Socket closed
12:37:29.85 Try launch USB connection
12:37:29.87 Socket closed
12:37:30.15 Try launch USB connection
12:37:30.17 Socket closed
12:37:30.45 Try launch USB connection
12:37:30.46 Socket closed
12:37:30.75 Try launch USB connection
12:37:30.76 Socket closed
12:37:31.04 Try launch USB connection
12:37:31.06 Socket closed
12:37:31.35 Try launch USB connection
12:37:31.37 Socket closed
12:37:31.65 Try launch USB connection
12:37:31.67 Socket closed
12:37:31.95 Try launch USB connection
12:37:31.96 Socket closed
12:37:32.25 Connect to Android failed!
12:37:32.25 bOpened=False
12:37:32.25 Refresh ComDescriptions...
12:37:32.51 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_681C&MI_00\3733xxxxxxxx00EC_00
12:37:32.51 ErrMsg: Connection to phone could not be established!
12:37:33.90 WM_POWERBROADCAST 10
12:38:00.31 Broadcaster started
12:38:00.31 Sending broadcast
12:38:00.81 Sending broadcast
12:38:01.31 Sending broadcast
12:38:02.31 Closing Broadcaster
12:38:02.31 RunADBCommand: start-server
12:38:02.43 ADB CommandResponse:
12:38:02.43 RunADBCommand: devices
12:38:02.56 ADB CommandResponse: List of devices attached
3733xxxxxxxx00EC device
12:38:02.56 RunADBCommand: -s 3733xxxxxxxx00EC forward tcp:5210 tcp:5210
12:38:02.67 ADB CommandResponse:
12:38:02.67 Try connecting to 127.0.0.1...
12:38:02.71 Socket closed
12:38:02.71 RunADBCommand: -s 3733xxxxxxxx00EC shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
12:38:03.15 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }
12:38:03.31 Try launch USB connection
12:38:03.32 Socket closed
12:38:03.62 Try launch USB connection
12:38:03.63 Socket closed
12:38:03.92 Try launch USB connection
12:38:03.93 Socket closed
12:38:04.21 Try launch USB connection
12:38:04.23 Socket closed
12:38:04.51 Try launch USB connection
12:38:04.53 Socket closed
12:38:04.81 Try launch USB connection
12:38:04.82 Socket closed
12:38:05.12 Try launch USB connection
12:38:05.13 Socket closed
12:38:05.42 Try launch USB connection
12:38:05.43 Socket closed
12:38:05.71 Try launch USB connection
12:38:05.73 Socket closed
12:38:06.01 Try launch USB connection
12:38:06.03 Socket closed
12:38:06.31 Try launch USB connection
12:38:06.32 Socket closed
12:38:06.62 Try launch USB connection
12:38:06.63 Socket closed
12:38:06.92 Try launch USB connection
12:38:06.93 Socket closed
12:38:07.21 Try launch USB connection
12:38:07.23 Socket closed
12:38:07.51 Connect to Android failed!
12:38:07.51 bOpened=False
12:38:07.51 Refresh ComDescriptions...
12:38:07.76 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_681C&MI_00\3733xxxxxxxx00EC_00
12:38:07.76 ErrMsg: Connection to phone could not be established!
12:38:35.28 Refresh ComDescriptions...
12:38:35.46 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_681C&MI_00\3733xxxxxxxx00EC_00
12:38:35.93 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False
12:39:35.32 Device Tracker Message: 0000
12:39:36.79 DBT_DEVICEREMOVECOMPLETE: COM3
12:39:45.07 Device Tracker Message: 00193733xxxxxxxx00EC offline

12:39:45.43 DBT_DEVICEARRIVAL: COM3
12:39:46.06 Device Tracker Message: 00183733xxxxxxxx00EC device

12:39:46.15 RunADBCommand: start-server
12:39:46.23 ADB CommandResponse:
12:39:46.23 RunADBCommand: devices
12:39:46.29 ADB CommandResponse: List of devices attached
3733xxxxxxxx00EC device
12:39:46.29 RunADBCommand: -s 3733xxxxxxxx00EC forward tcp:5210 tcp:5210
12:39:46.37 ADB CommandResponse:
12:39:46.37 Try connecting to 127.0.0.1...
12:39:46.38 Socket closed
12:39:46.38 RunADBCommand: -s 3733xxxxxxxx00EC shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
12:39:46.82 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity (has extras) }

Warning: Activity not started, its current task has been brought to the front
12:39:46.98 Try launch USB connection
12:39:47.00 Socket closed
12:39:47.29 Try launch USB connection
12:39:47.31 Socket closed
12:39:47.59 Try launch USB connection
12:39:47.60 Socket closed
12:39:47.88 Try launch USB connection
12:39:47.90 Socket closed
12:39:48.18 Try launch USB connection
12:39:48.20 Socket closed
12:39:48.56 Try launch USB connection
12:39:48.57 Socket closed
12:39:48.79 Try launch USB connection
12:39:48.81 Socket closed
12:39:49.09 Try launch USB connection
12:39:49.10 Socket closed
12:39:49.38 Try launch USB connection
12:39:49.40 Socket closed
12:39:49.43 Refresh ComDescriptions...
12:39:49.68 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_681C&MI_00\3733xxxxxxxx00EC_00
12:39:49.70 Try launch USB connection
12:39:49.71 Socket closed
12:39:49.98 Try launch USB connection
12:39:50.00 Socket closed
12:39:50.29 Try launch USB connection
12:39:50.31 Socket closed
12:39:50.59 Try launch USB connection
12:39:50.60 Socket closed
12:39:50.88 Try launch USB connection
12:39:50.90 Socket closed
12:39:51.18 Connect to Android failed!
12:39:51.18 bOpened=False
12:39:51.18 ErrMsg (Silent): Connection to phone could not be established!
12:40:00.34 Refresh ComDescriptions...
12:40:00.51 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Android USB Modem FriendlyName=SAMSUNG Android USB Modem InstanceID=USB\VID_04E8&PID_681C&MI_00\3733xxxxxxxx00EC_00
12:40:01.03 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False

***** End Log File *****

Same sort of issue here with the latest Google ADB Interface Driver. As soon as I backed off to version 1.0.10.0 I could connect again but then I have other issues.

My phone is an HD2 running Xylo's 4.0.4 de-Odexed ICS with HWA and the Dorimanix Kernel - version milestone 5 Second Edition.

The phone itself works great. the connectivity to it with MyPhoneExplorer, not so great.

cmillens hat geschrieben:Same sort of issue here with the latest Google ADB Interface Driver. As soon as I backed off to version 1.0.10.0 I could connect again but then I have other issues.

My phone is an HD2 running Xylo's 4.0.4 de-Odexed ICS with HWA and the Dorimanix Kernel - version milestone 5 Second Edition.

The phone itself works great. the connectivity to it with MyPhoneExplorer, not so great.

Thank you cmillens!

I've been thinking much about what else might have changed to affect this on my PC and Google ADB Interface update came to mind.

What version of Google ADB Interface should I revert back to and how do I accomplish that? In SDK Manager/Extras I have Google USB Driver Rev.4.

As below I have suddenly, after a dream run lasting months, been unable to connect my Galaxy S. And it appears to be an ADB problem.
This software is way superior to anything Samsung offer and I would be very sad to have to give it up.
Out of interest since this problem with ADB drivers has started Kies can not longer see the phone either.
I have un-installed MPExplorer and rebooted and re-installed to no good effect so is it some piece of software we have on out phone? Don't know.

Any suggestions please.

Trevor

http://naturalprogression.wordpress.com ... ce-driver/

This may help guys.
I'm hopeful.

If it worked with older drivers and you have problems with new drivers then maybe it depends on the adb.exe which MyPhoneExplorer does use.

- Download this file: www.fjsoft.at/files/adb_v11.zip
- extract the file and overwrite the 3 included files to C:\Programs\MyPhoneExplorer\DLL

Please give feedback if this was the solution

Ty FJ,
just stumbled upon your post and it solved my current issue.
The link provided is broken but I simply copied the adb.exe AdbWinApi.dll and AdbWinUsbApi.dll files from my sdk folder to the MPE.
This goes to show that, since MPE apparently stopped development, incompatible adb versions are coming out and the new version needs to be deployed in the DLL folder of MPE.
Again, thanks FJ.
After,
- (un)installing KIES, MPE, ADB drivers and others 2 or 3 times.
- (un)installing device drivers 3 times.
- rebooting 3 times.
- (un)installing and clearing cache of MPE on the phone twice.
- connecting my phone via 5 different usb ports several times.
- updating my phone ROM
- playing with firewall rules on both the phone and the PC.
it turned out to be as simple as copying 3 files...

I'm guessing the issue will occur regularly if MPE doesn't get updated at some point.
Hope it can help others.

These files will be updated soon in the official setup