Troubleshooting device connection

Ensure the device is powered on and has sufficient battery charge.
Use a high-quality USB data cable (not a charging-only cable).
If using a hub, try a direct connection to the PC.
Try a different USB port on the computer; the rear ports are directly connected to the motherboard.
Test with a different cable and/or PC to rule out hardware issues.
Confirm that the PC’s USB ports are working properly.

Verify that the correct driver(s) for the device are installed.
For iOS devices, ensure iTunes or direct Apple drivers are installed.
Use Windows Device Manager to verify that the device is detected and that the drivers are functioning.
Check for multiple/conflicting installed drivers and remove outdated or conflicting ones.
Restart the device if the screen unlock is known.
For Android: Try toggling USB debugging off and then back on.

Check that developer options are enabled.

In developer options, ensure “Stay awake”, “Allow USB debugging” and Verify apps via USB” are all set correctly.

Ensure USB connection type is set correctly (Android: File Transfer mode, not Charging).
Start the MOBILedit Forensic Connector app manually and select USB mode.
For iOS: Ensure "Trust this computer" has been accepted.
Check for USB Restricted Mode on iOS and disable it if necessary.
Check for any mobile device management software on the device.

Ensure that no conflicting software is running (e.g., Huawei HiSuite, other forensic tools).
Check that the device is not “tied” to another running process (e.g. adb)
Disable or adjust antivirus/firewall/security software that might block device communication.
Ensure Windows security policies allow communication with the device.
Verify that there are no system policies preventing device access (e.g., company-managed devices with MDM restrictions).
Ensure that you are not using a virtual machine.

5. Advanced Troubleshooting

Check for device security settings that might restrict access, according to the manufacturer. (E.g. Auto Blocker for Samsung)
Try booting the device into Safe Mode to see if a third-party app is interfering.
Ensure the device and PC OS are up to date, as older versions may have connectivity issues.
If no success, restart both the device (if PIN known) and PC, then retry.
Use adb in a terminal window to see if a device is recognised by typing “adb devices”.