Same with cygwin as command prompt, not working. But adb/adb shell reboot from android works as expected so no need to check drivers. I have any possible reboot/shutdown command you can imagine coded in QtADB and it goes through all of them if it retuns some kind of error so that's not the case.I dunno - I tend to use cygwin, but even using the basic windows command prompt adb shell reboot seems to work. I won't be able to check the drivers until I'm home. It makes little sense but could QtADB be the differentiating factor here?
Even tried recovery commands like "adb shell recovery --just_exit" which according to twrp code should exit the gui and restart the phone but it just restarts the gui without rebooting.
And btw fix_permissions script is not working, even in android.
Last edited: