Forum Discussion
reeejoshy
5 years agoHonored Guest
ok..... I got it going on WIN10......
I searched for ADB.exe in c: .... found it in a Sidequest folder...... ( recently installed side quest)
opened that location in powershell from file manager ( shft - rightclick inside folder area. and context menu displays select open powershell window here .....
I used the following commands to get it to go .... ( note the .\ before the adb.exe )
then put on the quest headset and it had the debuggin message waitng for me ( usb cable was plugged into it from pc)
clicked the always remember button and hit allow...
Your welcome internet !!!! :smile:
I searched for ADB.exe in c: .... found it in a Sidequest folder...... ( recently installed side quest)
opened that location in powershell from file manager ( shft - rightclick inside folder area. and context menu displays select open powershell window here .....
I used the following commands to get it to go .... ( note the .\ before the adb.exe )
PS C:\Users\josha\AppData\Roaming\SideQuest\scrcpy> .\ADB.EXE kill-server
PS C:\Users\josha\AppData\Roaming\SideQuest\scrcpy> .\ADB.EXE start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
PS C:\Users\josha\AppData\Roaming\SideQuest\scrcpy> .\ADB.EXE devices
List of devices attached
1PASE9AZ3GK141 unauthorized
then put on the quest headset and it had the debuggin message waitng for me ( usb cable was plugged into it from pc)
clicked the always remember button and hit allow...
Your welcome internet !!!! :smile:
jknight20252025
4 years agoHonored Guest
Help I tried this and it said that the system could not find the path specified.