Device Manager looks correct, but the command prompt returns blank. Solution: The driver is installed, but Windows is using the wrong driver stack.
When you plug a standard Android phone into a Windows PC while the phone is turned on, Windows automatically installs generic drivers (MTP) so you can transfer photos. However, if you turn the phone off and boot into (usually by holding Volume Up while connecting the USB cable), Windows sees a completely different device.
Advanced users can force the driver to recognize the device by editing the .inf file.
This is the most direct way to resolve the "waiting for device" error in your terminal. Can't See S1Boot Fastboot - Get Started - Sailfish OS Forum
