-
-
Save samchoi69/75d9bd164597338ff116b5a441e41a83 to your computer and use it in GitHub Desktop.
| # Windows | |
| 1. Open Windows Command Prompt | |
| 2. Run command | |
| "C:\Program Files (x86)\BlueStacks\HD-Adb.exe" shell | |
| # Within BlueStacks shell | |
| /system/xbin/bstk/su | |
| pm disable-user com.bluestacks.s2p | |
| # macOS | |
| 1. Open Terminal | |
| 2. Run command: | |
| /Applications/BlueStacks.app/Contents/MacOS/adb shell | |
| # Within BlueStacks shell | |
| /system/xbin/bstk/su | |
| pm disable-user com.bluestacks.s2p | |
| # Error: device not found | |
| # Kill the server with ADB | |
| # Make sure BlueStacks is running before you try to start ADB and disable the user | |
| # Windows | |
| "C:\Program Files (x86)\Bluestacks\HD-Adb.exe" kill-server | |
| #macOS | |
| /Applications/BlueStacks.app/Contents/MacOS/adb kill-server |
This is the new method that I used First, you need to install WSL or Linux VM. I used WSL.
(instructions here)
I figured I'd mention: as of Bluestacks 5.22.100, as far as I can tell, it seems to be aware that it's been tampered with and will terminate the android instance for "security reasons". Even reverting the hosts file edit won't fix this, requiring a full clean uninstall and reinstall. In my experience anyway.
EDIT:
Updated to add that this does seem to work on the MSI App Player, which is Bluestacks-based, and as of this post is on 5.22.75. This may indicate that either the "tampered" check is a new addition to Bluestacks, or that the MSI version just doesn't care. It did work, however, as their custom app-store believes it's been disconnected from the internet while everything else works fine.
And when I try the normal adb using the 5735 port -