Problem connecting with USB cable

[Philipeau]

Hello,

I can not run MyPhoneExplorer 1.8.7 to connect my Samsung S5 mini with my computer windows 7 sp1 (64 bits) by USB. I get the message "connection to the phone could not be established."

Yet I MyPhoneExplorer installed on the computer and on the phone, Samsung drivers installed on my computer (with SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33), enabled on the phone development options> USB debugging and authorization for the computer.

Can you help me ?
Philippe

[Philipeau]

Hello,

After several tests, I discovered that the problem was the firewall ZoneAlarm free. He blocked the access of USB MyPhoneExplorer.

I uninstalled the latest version of ZoneAlarm (141_048_000) to replace the previous (141_011_000). Surprise: with this version usb access works great!

Philippe

[ricarso solis]

hola me gustaria hacer una pregunta el firewall ZoneAlarm sirve para tablet por que tengo el problema mi pc no me lee la tablet conectado con el usb[/url][/list][/list][/code]

[Philipeau]

hola,
probar esta versión 141_011_000 : funciona para mí. : http://filehippo.com/fr/download_zoneal ... all/64530/
Philippe

[Steffie]

Today i experienced the identical symptoms as described above by Philipeau [my phone is Motorola Moto G2]. Whilst i cannot recall exactly when i previously used MPE before today, it was not more than 1 week ago, & might only have been a few days -- it worked perfectly then.

Given that Win10 receives updates every few days or so, i can't rule out a possibility that one of those might have broken the USB comms of MPE. Also, relatively recently i did upgrade ZoneAlarm Free AV & FW from 141_011_000 to 141_048_000, so i got excited when i read Philipeau's solution. Sadly, downgrading my ZA to that previous version did not help me.

Does anyone have any good ideas i can try pls?

[dvhttn]

Try Firewall off completely (Zonealarm and Windows)
Different cable
Different USB port(s)

Tried wifi?

[Steffie]

Thanks for your suggestions dvhttn. Happily i can update the post with news that i've now fixed it. When yesterday i manually downgraded ZA from 141_048_000 to 141_011_000, my method [as the cliché goes] "seemed like a good idea at the time"... rather than actually fully uninstall 048, reboot, install 011 fresh, reboot, then test MPE, i was lazy & merely installed 011 over 048. Oops.

After sleeping on it i realised this morning my laziness might be why MPE Connect still failed yesterday, ie, maybe some vestiges of 048 had not been overwritten by 011, & this perpetuated the MPE fault? To test that hypothesis this morning, & equally to test if the MPE problem was related to ZA at all, or maybe instead to the recent Win10 updates, i launched my other Win10 VM which i knew had not yet received any of the recent Win10 updates, & whose ZA was still 011. First i installed MPE into this 2nd VM, plugged in my USB cable, & confirmed that as hoped, MPE & phone connected just fine. Next i allowed the Win10 updates to proceed & complete, rebooted, retested MPE, & confirmed that phone connection still worked [& ZA here remained 011]. Hence this exonerated Win10 updates from any blame... this time.

Encouraged, i returned to my primary Win10 VM [both VMs run inside my primary on-metal OS of Linux Mint x64 17.3 KDE]. Here i fully uninstalled ZA [011], rebooted, fresh-installed 011, rebooted, & tried MPE... yay, it now once more connects & syncs with phone.

I emailed ZA with a link to this forum page, in case they're interested in this info to fix their latest [defective] version.