FJ Software

Every time I try to connect I get "connection to the phone could not be established. Phone could not be identified". I have tried this from two computers. One using Win7 32bit and the other Win7 64bit. I have tried USB with debugging on and every USB mode and have also tried WiFi. I have the latest Motorola drivers installed and have no problem connecting to the phone without MPE. I'm not sure if it matters or not but the phone is rooted. Any help would be greatly appreciated. Thanks.

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.0
Datum: 10/4/2010

12:10:11.57 Setting Port: 999
12:10:11.57 Setting Baud:
12:10:11.57 Avaiable Ports: COM3=\Device\ltmodem0;
12:10:11.58 Main Load frmSplash
12:10:11.60 Load frmSplash...
12:10:11.60 Show splash...
12:10:11.61 frmSplash geladen
12:10:13.78 Hauptfenster wird geladen
12:10:15.73 Sidebar fertig geladen
12:10:16.88 UC SMS wird geladen
12:10:17.08 UC Phonebook wird geladen
12:10:17.17 UC Phonebook fertig geladen
12:10:17.17 UC Calls wird geladen
12:10:17.23 UC Organizer wird geladen
12:10:17.48 Organizer initiated
12:10:17.58 Startpage=1
12:10:17.60 UC Filebrowser wird geladen
12:10:17.79 UC Filebrowser fertig geladen
12:10:17.79 UC AppBrowser wird geladen
12:10:17.82 UC Notes wird geladen
12:10:17.85 UC Calls wird geladen
12:10:17.95 Setting Lastuser:
12:10:17.97 Lade Userdatenbank:
12:10:18.05 Kontakte geladen
12:10:18.06 Anrufe geladen
12:10:18.06 Organizer geladen
12:10:18.06 Notizen geladen
12:10:18.07 SMS geladen
12:10:25.83 Hauptfenster fertig geladen
12:10:26.34 Downloader: RC=6 BytesMax=5 URL=http://www.fjsoft.at/myphoneexplorer/version.txt
12:10:42.67 Broadcaster started
12:10:42.67 Sending broadcast
12:10:43.16 Sending broadcast
12:10:43.68 Sending broadcast
12:10:44.68 Closing Broadcaster
12:10:44.68 RunADBCommand: start-server
12:10:44.91 ADB CommandResponse:
12:10:44.91 RunADBCommand: devices
12:10:45.17 ADB CommandResponse: List of devices attached
015A7A370E01C016 device
12:10:45.17 Run DeviceTracker
12:10:45.19 Init Tracker
12:10:45.19 RunADBCommand: forward tcp:5210 tcp:5210
12:10:45.22 Device Tracker Message: OKAY0018015A7A370E01C016 device

12:10:45.44 ADB CommandResponse:
12:10:45.44 Try connecting to 127.0.0.1...
12:10:45.55 Connect to Android OK
12:10:45.55 Settimeout: RT=2000 WT=500
12:10:45.55 bOpened=True
12:10:45.55 [TX]: AT+CGSN
12:10:45.71 [RX]: AT+CGSN
12:10:45.71 [RX]: A00000224440E5
12:10:45.71 [RX]: OK
12:10:45.71 Got no Model, close port
12:10:45.71 Androidsocket wird geschlossen 7
12:10:45.71 Port wurde geschlossen
12:10:45.72 Phone could not be identified
12:10:45.72 Refresh ComDescriptions...
12:10:45.73 MODEM: COM3 Enumerator=PCI LocationInfo=PCI bus 5, device 4, function 0 FriendlyName=Agere Win Modem InstanceID=PCI\VEN_11C1&DEV_0458&SUBSYS_9300141B&REV_00\4&5855BE9&0&20F0
12:10:45.74 ErrMsg: Connection to phone could not be established:
Phone could not be identified
12:22:36.23 Broadcaster started
12:22:36.23 Sending broadcast
12:22:36.73 Sending broadcast
12:22:37.24 Sending broadcast
12:22:38.24 Closing Broadcaster
12:22:38.24 RunADBCommand: start-server
12:22:38.54 ADB CommandResponse:
12:22:38.54 RunADBCommand: devices
12:22:38.77 ADB CommandResponse: List of devices attached
015A7A370E01C016 device
12:22:38.77 RunADBCommand: forward tcp:5210 tcp:5210
12:22:38.98 ADB CommandResponse:
12:22:38.98 Try connecting to 127.0.0.1...
12:22:39.08 Connect to Android OK
12:22:39.08 Settimeout: RT=2000 WT=500
12:22:39.08 bOpened=True
12:22:39.08 [TX]: AT+CGSN
12:22:39.23 [RX]: AT+CGSN
12:22:39.23 [RX]: A00000224440E5
12:22:39.23 [RX]: OK
12:22:39.23 Got no Model, close port
12:22:39.23 Androidsocket wird geschlossen 7
12:22:39.24 Port wurde geschlossen
12:22:39.24 Phone could not be identified
12:22:39.24 Refresh ComDescriptions...
12:22:39.25 MODEM: COM3 Enumerator=PCI LocationInfo=PCI bus 5, device 4, function 0 FriendlyName=Agere Win Modem InstanceID=PCI\VEN_11C1&DEV_0458&SUBSYS_9300141B&REV_00\4&5855BE9&0&20F0
12:22:39.26 ErrMsg: Connection to phone could not be established:
Phone could not be identified
12:27:03.25 Terminate Subclass
12:27:03.25 Terminate ADO
12:27:03.25 Unload Iconlib
12:27:03.25 Terminate Tray
12:27:03.26 Killing temporary Files
12:27:03.26 Terminate: Calls
12:27:03.26 Terminate: PB
12:27:03.26 Terminate: Notes
12:27:03.26 Terminate: Organizer
12:27:03.27 Terminate: SMS
12:27:03.28 ClosePort
12:27:03.28 Port wurde geschlossen
12:27:03.28 Form_QueryUnload -> Ende
12:27:03.28 Unload: frmSplash
12:27:03.29 Unload: fSocket
12:27:03.40 Form_Unload -> Ende

From the log it looks like it connects then it can not determine / does not know the model number.

My phone:
System version: Version.2.3.15.MB810.Verizon.en.US
Model number: DROIDX
Android version: 2.2

Log excerpt:


11:49:40.84 Broadcaster started
11:49:40.84 Sending broadcast
11:49:40.85 Got Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F19480B021E077B686B6D7D4B405D1938020000067D62776B603C322927055F5F44593F3F293E733D21242C3D6A
11:49:40.88 Got Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F19480B021E077B686B6D7D4B405D1938020000067D62776B603C322927055F5F44593F3F293E733D21242C3D6A
11:49:41.34 Sending broadcast
11:49:41.35 Got Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F19480B021E077B686B6D7D4B405D1938020000067D62776B603C322927055F5F44593F3F293E733D21242C3D6A
11:49:41.84 Sending broadcast
11:49:41.85 Got Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F19480B021E077B686B6D7D4B405D1938020000067D62776B603C322927055F5F44593F3F293E733D21242C3D6A
11:49:42.84 Try connecting to 192.168.2.236...
11:49:42.92 Connect to Android OK
11:49:42.92 Settimeout: RT=2000 WT=500
11:49:42.92 bOpened=True
11:49:42.92 [TX]: AT+CGSN
11:49:43.07 [RX]: AT+CGSN
11:49:43.07 [RX]: A000002243EABB
11:49:43.07 [RX]: OK
11:49:43.07 Got no Model, close port
11:49:43.07 Androidsocket wird geschlossen 7
11:49:43.07 Port wurde geschlossen
11:49:43.07 Phone could not be identified
11:49:43.07 Refresh ComDescriptions...
11:49:43.13 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_2A47&SUBSYS_20EC17AA&REV_07\3&B1BFB68&0&1B
11:49:43.13 PORT: COM5 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth Communications Port InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000000
11:49:43.20 MODEM: COM4 Enumerator=HDAUDIO LocationInfo=Internal High Definition Audio Bus FriendlyName=ThinkPad Modem Adapter InstanceID=HDAUDIO\FUNC_02&VEN_14F1&DEV_2C06&SUBSYS_17AA2122&REV_1000\4&2B9C4D19&0&0102
11:49:43.20 MODEM: COM6 Enumerator=USB LocationInfo=MB810 FriendlyName=Motorola USB Modem InstanceID=USB\VID_22B8&PID_41D8&MI_00\6&258AC344&1&0000
11:49:43.20 ErrMsg: Connection to phone could not be established:
Phone could not be identified
11:49:44.07 Got Broadcast: 002915373C17162E1D095E5F42533F0F06333A1C1D1F3A3B405F51522E31362B2F484A594B4804081E04636276692F38435B5549020202027E15041D11051E041116405F5C576D1417101A3D2B
11:49:47.56 Refresh ComDescriptions...
11:49:47.60 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_2A47&SUBSYS_20EC17AA&REV_07\3&B1BFB68&0&1B
11:49:47.60 PORT: COM5 Enumerator={95C7A0A0-3094-11D7-A202-00508B9D7D5A} Displayed=Bluetooth Communications Port InstanceID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}\BLUETOOTHPORT\1&30EE4AD&0&1000000000000
11:49:47.65 MODEM: COM4 Enumerator=HDAUDIO LocationInfo=Internal High Definition Audio Bus FriendlyName=ThinkPad Modem Adapter InstanceID=HDAUDIO\FUNC_02&VEN_14F1&DEV_2C06&SUBSYS_17AA2122&REV_1000\4&2B9C4D19&0&0102
11:49:47.65 MODEM: COM6 Enumerator=USB LocationInfo=MB810 FriendlyName=Motorola USB Modem InstanceID=USB\VID_22B8&PID_41D8&MI_00\6&258AC344&1&0000
11:49:48.23 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False

The problem is not the model, its the IMEI. The IMEI has to be a 15-Digit Number. Could it be possible that you changed your IMEI cause of the roots ? I don't think that a "normal" Model will use a invalid IMEI

EDIT: is your DroidX a CDMA-Phone ?

My phone is not rooted.
It has an MEID number.
It does not (appear to) have an IMEI number.

Yes, my Droid is a CDMA phone.

This is the beta of the desktop-app: http://www.fjsoft.at/files/MyPhoneExplo ... Update.exe

Install it and try again

What a quick resolution. Thank you.
With the beta update (installed on top of the original), I am able to connect to the phone.

Great app. Donation made - thanks!

Edit: If you want any info or logs from the beta, please let me know. Feel free to email me directly:
darrenk
1972
@
gmail.com

Thank you so much for the quick resolution to my problem. I just installed the beta and everything works great. Fantastic app and great support.

followed the instructions outlined in this thread but still can't connect. Here is the log info:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.0
Datum: 10/5/2010

11:33:09.58 Setting Port:
11:33:09.58 Setting Baud:
11:33:09.59 Avaiable Ports: COM0=;
11:33:09.70 Main Load frmSplash
11:33:09.83 Load frmSplash...
11:33:09.83 Show splash...
11:33:09.84 frmSplash geladen
11:33:11.06 Hauptfenster wird geladen
11:33:11.22 Sidebar fertig geladen
11:33:11.41 UC SMS wird geladen
11:33:11.50 UC Phonebook wird geladen
11:33:11.55 UC Phonebook fertig geladen
11:33:11.55 UC Calls wird geladen
11:33:11.58 UC Organizer wird geladen
11:33:11.67 Organizer initiated
11:33:11.70 Startpage=1
11:33:11.70 UC Filebrowser wird geladen
11:33:11.75 UC Filebrowser fertig geladen
11:33:11.75 UC AppBrowser wird geladen
11:33:11.77 UC Notes wird geladen
11:33:11.77 UC Calls wird geladen
11:33:11.80 Setting Lastuser:
11:33:11.83 Lade Userdatenbank:
11:33:11.84 Kontakte geladen
11:33:11.84 Anrufe geladen
11:33:11.86 Organizer geladen
11:33:11.86 Notizen geladen
11:33:11.87 SMS geladen
11:33:12.22 Hauptfenster fertig geladen
11:33:14.30 Downloader: RC=6 BytesMax=5 URL=http://www.fjsoft.at/myphoneexplorer/version.txt
11:33:16.42 Refresh ComDescriptions...
11:33:16.84 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False
11:34:11.35 OK pressed in settingswindow
11:34:11.37 Set first swap of settings
11:34:11.37 Apply new holidays
11:34:11.37 Holidays applied
11:34:11.37 Second swap of settings set
11:34:11.37 Everything is done
11:34:14.55 Broadcaster started
11:34:14.55 Sending broadcast
11:34:15.07 Sending broadcast
11:34:15.59 Sending broadcast
11:34:16.55 Closing Broadcaster
11:34:16.55 RunADBCommand: start-server
11:34:19.52 ADB CommandResponse:
11:34:19.52 RunADBCommand: devices
11:34:20.66 ADB CommandResponse: List of devices attached
11:34:20.66 Run DeviceTracker
11:34:20.69 Init Tracker
11:34:20.69 Connect to Android failed!
11:34:20.69 bOpened=False
11:34:20.69 No device attached to USB
11:34:20.69 Refresh ComDescriptions...
11:34:20.77 ErrMsg: Connection to phone could not be established:
No device attached to USB
11:34:20.77 Device Tracker Message: OKAY0000
11:34:27.82 Broadcaster started
11:34:27.82 Sending broadcast
11:34:28.33 Sending broadcast
11:34:28.83 Sending broadcast
11:34:29.80 Closing Broadcaster
11:34:29.80 RunADBCommand: start-server
11:34:29.85 ADB CommandResponse:
11:34:29.85 RunADBCommand: devices
11:34:29.91 ADB CommandResponse: List of devices attached
11:34:29.91 Connect to Android failed!
11:34:29.91 bOpened=False
11:34:29.91 No device attached to USB
11:34:29.91 Refresh ComDescriptions...
11:34:29.99 ErrMsg: Connection to phone could not be established:
No device attached to USB
11:34:33.66 Refresh ComDescriptions...
11:34:34.11 StickyNotesPath=C:\WINDOWS\Sysnative\StikyNot.exe FileExists=False

Thanks!

When you see the Errormessage:

Connection to phone could not be established:
No device attached to USB

There is a Help-Button. Click on this button and check all points which are listed there.

On droidx usb-debugging is reached through setting/applications/development

The "moto" application that autoruns when I connection to win7 installed various drivers as I changed from pc, to media to mass storage on my usb configuration app on the droidx.

the PC option for droiodx/usb connection worked with mpe.

But I had to jump start the mpe-droid connection the first time, i.e. droidx connected with the droidx myphone* app running and THEN open the myphoneexplore pc application.

Using f1 did not seem to work until after the connection was jump started.



Configuration:
win7 64 bit vmware under fusion

windows mobility center 64 bit already installed for reasons not related to myphoneexplorer

droidx 2.3


Initial view of myphone* is great. But I'll try and test it more later, especially outlook features.

Big THANKS to the person starting this thread!!! And "thumbs up" to the developer.

K