Quote:
Originally Posted by booklover2005
No, the backup definitely did not work. I reached the part of the instructions where I am supposed to open the Windows PowerShell in the folder where I have the platform-tools extracted. I had trouble getting the "adb connect localhost:{5555}" working - it kept telling me: ADB : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program.
|
PowerShell needs you to prefix the command with .\ to run a local command. When I try running adb from a admin PowerShell session, I get the following suggestion:
Quote:
|
Suggestion [3,General]: The command adb.exe was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb.exe". See "get-help about_Command_Precedence" for more details.
|
This works with PowerShell 5.1.22621.963 or PowerShell 7.3.3.
Quote:
Originally Posted by booklover2005
I went into Advanced System Settings > Environment Variables and added the path in, and then when I went back to the PowerShell, it allowed me to but the "adb connect localhost" in, and gives me this message back: adb.exe: usage: adb connect HOST[:PORT].
But when I try to open cmd.exe and put in "adb backup com.amazon.kindle" I receive the message "WARNING: adb backup is deprecated and may be removed in a future release
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: unable to connect for backup: no devices/emulators found"
|
Double check the port shown in Bluestacks when you enabled adb. On mine, it showed 62047 as the port. So my command line was "adb.exe connect 127.0.0.1:62047" or using PowerShell syntax, ".\adb.exe connect 127.0.0.1:62047"