This usually happens when another ADB tool from a third party Android SDK is running and conflicts with Genymotion Desktop built-in ADB.
To solve this:
- Make sure that no adb server is running. To kill any running adb servers, you can use the command
adb kill-serverOr kill any running ADB processes.
- Set Genymotion Desktop to use your third party Android SDK. Please refer to Configuring ADB for details.
- If it still does not work, try to reboot the host machine.
If it doesn't help, you may need to revert to Genymotion built-in ADB and make sure that no other ADB services are running before using Genymotion (step 1 from above).
However, you will not be able to use Genymotion and your third party ADB tool at the same time in this case.