I installed bluestacks version 0.10.0 on my PC.
When i run adb shell this command work fine,
But when i run adb root command and then run adb shell command it give error:device not found.
If i run adb kill-server and then adb shell it work fine.
Any Help?
Related
I am running a headless emulator (Android api 25) on a Ubuntu linux 14 server and I see the below output for the command-
$./adb devices
List of devices attached
emulator-5556 device
However, If i try to run any other command I get error
$./adb shell dumpsys deviceidle get deep
Can't find service: deviceidle
$./adb shell 'pm list packages -f'
Error: Could not access the Package Manager. Is the system running?
How can i verify that my emulator is functional?
is adb devices -l not working? it should show you the status of the device as well
try adb push, for eg
adb push foo.txt /sdcard/foo.txt
or adb install for eg
adb -s emulator-5556 install apkname.apk
these commands will work with any running emulator/device
all these commands are available on the documentation
I using android emulator in linux(Ubuntu16.04), The adb server seems not working normal.
root#ubuntu:~/santi/opengl# adb -P 15770 devices
List of devices attached
emulator-5770 device
root#ubuntu:~/santi/opengl# adb -P 15770 root
root#ubuntu:~/santi/opengl# adb -P 15770 kill-server
root#ubuntu:~/santi/opengl# adb -P 15770 devices
* daemon not running. starting it now on port 15770 *
* daemon started successfully *
List of devices attached
root#ubuntu:~/santi/opengl#
Thus the problem, when I restart adb server, the emulator not in adb devices again! Only if I restart the emulator, it shows again in adb devices.
The ADB version: Android Debug Bridge version 1.0.32
adb devices
adb root
adb kill-server
adb devices
Unbelievable! Above problem was caused by the emulator specified start port. As I start emulator with command:
emulator -avd template -gpu mesa -no-window -port 5680
The above port if > 5680, then device wont show after restart adb server, otherwise port <= 5680 it shows and definitely shows okay!
I've connected the smarthpone (rooted) to the PC (Linux) with ADB.
Eveything works fine excepts the fact that I can't unistall apps from shell. I've tried :
adb unistall com.mirsoft.passwordmemory
adb unistall -k com.mirsoft.passwordmemory
And I get the help message as return.
I've also tried:
adb shell pm unistall com.mirsoft.passwordmemory
adb shell pm unistall -k com.mirsoft.passwordmemory
Getting as return
Error: unknown command 'unistall'
followed by the help message.
Other commands works fine.
Am I doing something wrong?
uninstall has an n after the i. Use adb uninstall com.mirsoft.passwordmemory.
You can also try to uninstall with the rm command:
adb shell rm com.mirsoft.passwordmemory
Don't​ forget typically the su command to grant the super user permissions.
I just changed my PC, and now I have a problem with Android Studio, every time i try to run or compile an app it install it correctly, but then it cannot start the main activity of the app, if you need it this is the full Android studio output:
Waiting for device.
Target device: samsung-gt_i9000-3733E37B1ACB00EC
Uploading file
local path: C:\Users\Federico\swagmasta\TurnarioConapo1.0\app\build\outputs\apk\app-debug.apk
remote path: /data/local/tmp/feddycapdev.conapo.turnario
Installing feddycapdev.conapo.turnario
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/feddycapdev.conapo.turnario"
pkg: /data/local/tmp/feddycapdev.conapo.turnario
Launching application: feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity.
DEVICE SHELL COMMAND: am start -D -n "feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Error: Adb refused a command
I tried to manually run am start -D -n "feddycapdev.conapo.turnario/feddycapdev.conapo.turnario.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER from the adb shell, and it work correctly, some ideas on how could i fix it?
UPDATE : I tried running as admin, rebooting PC, reconnecting cable, killing all the adb.exe processes, killing the adb server and restarting it, noone of this worked.
Maybe it's a problem of driver? I'm using a Samsung Galaxy S for debugging, at the beginning the PC didn't recognized it, so I installed samsung USB driver, so maybe that's the real problem, but if i can install app to my device via adb the driver should be working right?
Please kill and start adb server from console or terminal using following commands:
adb kill-server
adb start-server
If it does not help try to restart your computer.
If you are getting
adb command not found
error then you have to go in platform-tools directory in Android SDK.
hope it helps!
It could be blocked by some other instance of adb.
Look into your task manager if you are not running another instance of adb.
I keep getting
ADB rejected shell command (ls -l /data):
and the command prompt when running adb shell tells me error: device not found although the emulator is open.
What I am doing wrong?
I assume you run adb from the command-line. Just do a adb kill-server and a adb start-server. After that your device(s) should be visible.