Scrcpy: ERROR: "adb push" returned with value 1

Created on 26 Jun 2018  Â·  66Comments  Â·  Source: Genymobile/scrcpy

When I try to run this scrcpy cmd from eclipse, it says 'ERROR: "adb push" returned with value 1'. please help.

adb

Most helpful comment

failed to get feature set: more than one device/emulator

adb devices

List of devices attached
*** devices
*** devices

you need find YOUR_DEVICE_CODE
some string or IP address on these *

scrcpy -s YOUR_DEVICE_CODE

All 66 comments

Which system? Put the path of your adb in your PATH.

@Jesna12 - Is that all there is to the error? Was there anything else with it? For example, I had this error

adb: error: failed to get feature set: more than one device/emulator
2018-07-05 14:23:58.610 scrcpy[31572:326844] ERROR: "adb push" returned with value 1

And it was because I had an emulator running.

This error occurs every time the adb command returns a non-zero value. There may be several causes.

Yep, the above was an example, I believe @Jesna12 only copied the last line in that response.

failed to get feature set: more than one device/emulator

adb devices

List of devices attached
*** devices
*** devices

you need find YOUR_DEVICE_CODE
some string or IP address on these *

scrcpy -s YOUR_DEVICE_CODE

I tried providing device code along with scrcpy. Then the error says "adb: error: cannot stat 'scrcpy-server.jar': No such file or directory ERROR:adb push returned with value 1"

adb disconnect
then choose one of these depending on how you are connecting to your device
adb usb // for usb
adb tcpip 5555 // for adb over wifi

Hello,

I'd like to mirror my Oculus Go on my MacBook with adb & scrcpy.

MacBookPro 14.2
macOS High Sierra 10.13.6-

For this I set the Oculus Go in the developer mode.
Install adb on my MacBook and go to the directory with the terminal.

Now I enter the following commands:

./adb shell ip route (to get the IP address)
./adb tcpip 5555
./adb connect 192.168.178.49 (to connect the Oculus Go via WLAN)

Now I go with the terminal into the directory where Scrcpy is located and try the following commands:

scrcpy -b 25M
scrcpy -b 25M-c 1000: 1000: 110: 220
scrcpy -c 1000: 1000: 110: 220
scrcpy -s 192.168.178.xx

Then I get the following error messages with each command:
ERROR: "adb push" returned with value 1

Can someone help me here?

Greetings
Maik

Thx rom1v

Thank you, but I think that my scrcpy does not work!

For example, if I enter scrcpy in the terminal and correct path, the same error message comes up!

2018-08-16 21: 58: 20.234 scrcpy [1148: 73353] ERROR: "adb push" returned with value 1

Does anyone have an idea here?
Maybe I made it wrong?

What is the result of adb devices in that terminal?

Maiks-MBP:platform-tools maiksteidel$ ./adb devices
List of devices attached

Maiks-MBP:platform-tools maiksteidel$ ./adb connect 192.168.178.49:5555
connected to 192.168.178.49:5555

And then scrcpy fails? (even if you unplugged the USB before adb connect)

Yes, I do not connect the device at all.
I connect via Wifi and then enter the scrcpy command and then the following message appears:
2018-08-16 22: 42: 45.102 scrcpy [5086: 114904] ERROR: "adb push" returned with value 1

Can you check if scrcpy works at all?
Maybe I installed it wrong?
Have everything with the command ...
/ usr / bin / ruby -e "$ (curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
everything installed and then the command
brew install scrcpy
Taken!

Can you check if scrcpy works at all?

Yes, it does :wink:

When you get this adb push error, does adb shell works?

Does _scrcpy_ work over usb?

What is the result of scrcpy -v?

Hello, many thanks for your help.
Unfortunately I can only test your suggestion tonight.
Thanks again... :)

When you get this adb push error, does adb shell works?
Unfortunately I do not know, but I can connect with adb my Oculus Go via WLAN.

Does scrcpy work over usb?
I installed scrcpy with the two commands on my MacOS.
It's in the / usr / local / bin folder.

What is the result of scrcpy -v?

scrcpy v1.3

dependencies:

  • SDL 2.0.8
  • libavcodec 58.18.100
  • libavformat 58.12.100
  • libavutil 56.14.100

I am very grateful for your time.

Thank you :)

Does /usr/local/share/scrcpy/scrcpy-server.jar exist?

Does this command work:

adb push /usr/local/share/scrcpy/scrcpy-server.jar /data/local/tmp/

?

And this one:

SCRCPY_SERVER_PATH=/usr/local/share/scrcpy/scrcpy-server.jar scrcpy

?

"Does /usr/local/share/scrcpy/scrcpy-server.jar exists?"
Yes, the folder exists.

"Does this command work:
adb push /usr/local/share/scrcpy/scrcpy-server.jar /data/local/tmp/ ?"
Yes, there seem to be a lot of tests or something. Do you need the text?

"And this one:
SCRCPY_SERVER_PATH=/usr/local/share/scrcpy/scrcpy-server.jar scrcpy ?"
Maiks-MBP:adbscr maiksteidel$ SCRCPY_SERVER_PATH=/usr/local/share/scrcpy/scrcpy-server.jar scrcpy
exec: No such file or directory
2018-08-17 19:04:24.315 scrcpy[5384:228786] ERROR: "adb push" returned with value 1
Maiks-MBP:adbscr maiksteidel$ SCRCPY_SERVER_PATH=/usr/local/share/scrcpy/scrcpy-server.jar
Maiks-MBP:adbscr maiksteidel$
Nothing happens!

adb push /usr/local/share/scrcpy/scrcpy-server.jar /data/local/tmp/
Yes, there seem to be a lot of tests or something. Do you need the text?

Yes, please (at least a part of it). Does it start with something like:

Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
...

?

exec: No such file or directory

So it does not find your adb.

What is the result of adb --version? echo $PATH? which adb?
Where is your adb installed?

Ah, I just noticed that you executed adb using ./adb, so it is probably in your current folder, but not in your PATH.

You can specify a custom path for your adb:

ADB=./adb scrcpy

Alternatively, you could install adb on Mac OS, e.g. from homebrew:

brew cask install android-platform-tools

When I following command ...
"ADB=./adb scrcpy"
my MacBook has mirrored the Oculus Go.
Yipieeeeee

I will always try this now and hope that it continues to work.

Your suggestion...
"Alternatively, you could install adb on Mac OS, e.g. from homebrew:
brew cask install android platform tools"
I will not enter first, because I'm afraid that it will not work!

I will try to repeat this day by day and would be happy if the problem is solved.
I am very grateful to you.
I wish you a nice weekend.

Maik

my MacBook has mirrored the Oculus Go.
Yipieeeeee

:+1:

I will not enter first, because I'm afraid that it will not work!

:fearful:

You might also be interested in:

When I try to mirror my android phone it says

adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
Press any key to continue...

Please help me :'(

@rom1v

When I try to mirror my android phone it says

adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
Press any key to continue...

Please help me :'(

i got same issue here please

@rizkysptr

Does your phone enable adb debugging?

I have ran into this issue a few times and disabling and enabling USB debugging fixes it.

I tried providing device code along with scrcpy. Then the error says "adb: error: cannot stat 'scrcpy-server.jar': No such file or directory ERROR:adb push returned with value 1"

I had the same issue, it seems there was a spelling mistake. The file "scrcpy-server.jar" was named "scrpy-server.jar" in my machine

From snapd over centos 7 (using snap install --edge --classic scrcpy) is fail. Says same error:

* failed to start daemon
adb: error: failed to get feature set: cannot connect to daemon
ERROR: "adb push" returned with value 1

I installed the adb from yum package and run adb shell and works fine, but the scrcpy is fail.

I try usin the native adb:

# ADB=$(which adb) scrcpy
exec: No such file or directory
ERROR: Command not found: [/usr/bin/adb], [push], [/usr/local/share/scrcpy/scrcpy-server.jar], [/data/local/tmp/scrcpy-server.jar]
ERROR: (make 'adb' accessible from your PATH or define its fullpath in the ADB environment variable)
ERROR: Could not execute "adb push"

Ok, the scrcpy is in snap directory:

# find / -iname "scrcpy-server.jar"
/var/lib/snapd/snap/scrcpy/131/usr/local/share/scrcpy/scrcpy-server.jar
^C
# ADB=$(which adb) SCRCPY_SERVER_PATH=/var/lib/snapd/snap/scrcpy/131/usr/local/share/scrcpy/scrcpy-server.jar scrcpy
exec: No such file or directory
ERROR: Command not found: [/usr/bin/adb], [push], [/var/lib/snapd/snap/scrcpy/131/usr/local/share/scrcpy/scrcpy-server.jar], [/data/local/tmp/scrcpy-server.jar]
ERROR: (make 'adb' accessible from your PATH or define its fullpath in the ADB environment variable)
ERROR: Could not execute "adb push"

I try upload the jar manualy and works fine:

# adb push /var/lib/snapd/snap/scrcpy/131/usr/local/share/scrcpy/scrcpy-server.jar /data/local/tmp/
381 KB/s (22470 bytes in 0.057s)
# adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
zeroflte:/ $ ls -lah /data/local/tmp/*.jar                                     
-rw-rw-rw- 1 shell shell 22K 2019-07-13 01:02 /data/local/tmp/scrcpy-server.jar

The scrcpy works fine on ubuntu and snapd, but on raspberry pi with centos 7 and snapd no work. I want stream my phone on raspberry, plug the audio, and raspberry to the tv (no smart) using hdmi output.

How to resolve this?

* failed to start daemon
adb: error: failed to get feature set: cannot connect to daemon

Weird. Something blocking it?
https://stackoverflow.com/questions/52173657/android-studio-error-cannot-connect-to-daemon/52185036

# ADB=$(which adb) scrcpy
exec: No such file or directory
ERROR: Command not found: [/usr/bin/adb], [push], [/usr/local/share/scrcpy/scrcpy-server.jar], [/data/local/tmp/scrcpy-server.jar]

So /usr/bin/adb causes exec: No such file or directory… :thinking:
By the way, it seems you are running this as _root_ (your prompt is #), you shouldn't (but that does not explain).

What is the result of:

ls -l usr/bin/adb
/usr/bin/adb devices
echo $PATH

Do you have a ~ in your PATH? (see https://github.com/Genymobile/scrcpy/issues/12#issuecomment-374981039)

# pwd
/root
# adb version
Android Debug Bridge version 1.0.31
# which adb
/usr/bin/adb
# ls -l /usr/bin/adb
-rwxr-xr-x. 1 root root 146404 dic  6  2017 /usr/bin/adb
# /usr/bin/adb devices
List of devices attached 
081608b1a0b91805    device
# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/var/lib/snapd/snap/bin:/root/bin
# cat /etc/centos-release
CentOS Linux release 7.6.1810 (AltArch)
# adb shell
zeroflte:/ $ uname -a
Linux localhost 3.10.61-12572046 #1 SMP PREEMPT Sun Mar 18 04:39:12 KST 2018 aarch64

The snap run into a jail enviroment, can not access to root folders of system operative. Need connect to more permisions. It is a snap package problem. But anyway can not connect to phone using the native adb from scrcpy.

Yes, i remove the [root@localhost ~] for less content. My phone is a Samsung Galaxy s6 no root.

Given:

# which adb
/usr/bin/adb
# ls -l /usr/bin/adb
-rwxr-xr-x. 1 root root 146404 dic  6  2017 /usr/bin/adb
# /usr/bin/adb devices
List of devices attached 
081608b1a0b91805    device

This seems very weird to me:

# ADB=$(which adb) scrcpy
exec: No such file or directory
ERROR: Command not found: [/usr/bin/adb], [push], [/usr/local/share/scrcpy/scrcpy-server.jar], [/data/local/tmp/scrcpy-server.jar]

Does this work:

/usr/bin/adb push /usr/local/share/scrcpy/scrcpy-server.jar /data/local/tmp/scrcpy-server.jar

?

If yes, create a small C program:

#include <stddef.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

int main(int argc, char *argv[]) {
    if (argc != 2) {
        fprintf(stderr, "Syntax: %s adb\n", argv[0]);
        exit(1);
    }
    const char *adb = argv[1];
    execlp(adb, adb, "devices", (char *) NULL);
    return 1;
}

Save it to doexec.c, and compile with:

gcc doexec.c -o doexec

Does this work:

./doexec /usr/bin/adb

?

Yes, the push works fine, the c program says:

# nano doexec.c
# gcc doexec.c -o doexec
# file doexec
doexec: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=43e3efb40569337f1ce50424280246dd65ab7a68, not stripped
# ./doexec /usr/bin/adb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached 
081608b1a0b91805    device

The snap app run in jail on /var/lib/snapd/snap/scrcpy/131/, when set the adb path /usr/bin/adb realy try get from /var/lib/snapd/snap/scrcpy/131/usr/bin/adb. The custom path no works. Need modify the snap package for access to external files. But anyway have 2 problems, the snap package and the unable access only from centos.

I was experiencing the same issue as OP and a few others with my Windows 7 PC and Pixel 3XL.

I had tried everything suggested but was still having issues: adb was added to PATH, manually stopped/started server, etc. but to no avail. Finally, as other comments have stated, toggling Developer Options is what it took to resolve the error:

adb: error: failed to get feature set: no devices/emulators found ERROR: "adb push" returned with value 1 Press any key to continue...

But, more importantly, simply toggling the USB Debugging on/off didn't work. I realized I was never getting the prompt to authorize my PC on the phone as others have commented.

To resolve this, I dragged the notifications menu down and then dragged down on the "Android System ... USB" pinned notification to change the USB Preferences and choose how my phone was connecting to my PC (Power Only, File Transfer, Tethering, etc.).

The following steps caused my phone to recognize that USB Debugging was enabled and prompted the authorization for my PC while phone was connected:

  1. Disabled Developer options (which disabled USB Debugging)
  2. Re-enabled Developer options
  3. Re-enabled USB Debugging
  4. Dragged down notification slider and opened USB Preferences
  5. Left "USB Controlled by" to "This Device" so the phone controls the connection
  6. Set "Use USB For" to "PTP"
  7. Windows detected the new device/connection type and automatically installed "PTP" drivers for the USB connection
  8. Received the prompt to authorize my PC to debug the Pixel3XL, accepted the prompt
  9. Ran scrcpy.exe successfully

I was also running into the error described here and this issue was resolved by bao1410227's suggestion to copy my PC's ADB files into the scrcpy folder.

Hope this helps someone!

INFO: scrcpy 1.10 <https://github.com/Genymobile/scrcpy>
adb: error: failed to copy 'D:\Download\Compressed\platform-tools_r29.0.2-windows\scrcpy-win64-v1.10\scrcpy-server.jar' to '/data/local/tmp/scrcpy-server.jar': remote couldn't create file: Permission denied
D:\Download\Compressed\platform-tools_r29.0.2-windows\scrc...rver.jar: 0 files pushed. 0.8 MB/s (22546 bytes in 0.025s)
ERROR: "adb push" returned with value 1
Press any key to continue...

any clue why i got permission denied?

See #665

I did the following on windows 10:

adb tcpip 5555
adb connect _MY IP_:5555 (usb connected)
then disconnected usb
scrcpy

INFO: scrcpy 1.10 https://github.com/Genymobile/scrcpy
adb server version (40) doesn't match this client (41); killing...

  • daemon started successfully
    adb: error: failed to get feature set: no devices/emulators found
    ERROR: "adb push" returned with value 1
    Press any key to continue...

Help me with this please

You don't use the same adb version (40) for adb connect. Use the one from the _scrcpy_ folder (version 41).

Used to get that error every time coming back from sleep on my MacBook. I just wrapped scrcpy in a script with "adb kill-server" right before it. Doesn't take much longer and has been very reliable in getting it to work. Only problem I guess would be calling it in the middle of a debugging session but can always restart

It's simpler just not to use another (old) version of adb elsewhere (update them all).

just write the command adb kill-server ,it worked for me and i hope will do for you also.

$ adb kill-server
$ adb connect <your_phone_or_android_stb_ip_address>:<port_number>
$ scrcpy

NB: default port number is 5555

This problem is that there are other adb.exe files in the system and the correct system PATH path is not set, resulting in an inconsistency between the adb version and the scrcpy requirement. The solution is to delete the redundant adb.exe file or set the correct PATH path

Hi, first of all thanks for this great software.

I'm trying to get it up and running on my machine.

Got a sucessful build, but after running scrcpy I get this error:

INFO: scrcpy 1.12.1 <https://github.com/Genymobile/scrcpy>
adb: error: connect failed: no devices/emulators found
ERROR: "adb push" returned with value 1

USB debuggin is properly enabled on my Samsung Galaxy A9... Tried enabling/disbling it several times as suggested by various users, but didn't work.

Android Studio info is this:

Android Studio 3.5.1
Build #AI-191.8026.42.35.5900203, built on September 25, 2019
JRE: 1.8.0_202-release-1483-b49-5587405 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-11-amd64

OS is Debian 9 Stretch

Troubleshooting system I got this:

adb --version 
Android Debug Bridge version 1.0.36
Revision 1:7.0.0+r33-1

adb devices
List of devices attached

which adb
/usr/bin/adb

ls -l /usr/bin/adb
lrwxrwxrwx 1 root root 37 abr 24  2017 /usr/bin/adb -> ../lib/android-sdk/platform-tools/adb

echo $PATH
/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin

I'm out of ideas, please help.

Cheers :)

OK so your device is not detected by your computer.

Do you see it in lsusb?

Android Debug Bridge version 1.0.36

Firstly, your adb is old. Try to update to 1.0.41.

If adb devices still does not detect your device, try with adb from the packages (apt install adb).

In particular, some udev rules might be missing: check /etc/udev/rules.d/51-android.rules (or similar). But from my experience, on Debian 9 it should work out-of-the-box.

Just tried changing the USB cable to another port and I got the phone to show up on the list of devices:

Bus 001 Device 111: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy series, misc. (MTP mode)

adb devices
List of devices attached
adb server version (41) doesn't match this client (36); killing...
* daemon started successfully *
2ae05f20540d7ece    device

After running scrcpy my phone shows up for one sec on my laptop, but then dissapears

INFO: scrcpy 1.12.1 <https://github.com/Genymobile/scrcpy>
[100%] /data/local/tmp/scrcpy-server.jar
INFO: Initial texture: 1080x2216
WARN: Device disconnected
WARN: Device disconnected

If you rerun adb devices after that, does it say:

adb server version (41) doesn't match this client (36); killing...

?

If yes, then you have another program on your computer which executes adb 36.

Find this program, and either stop it, or make it use adb 41.

I just recorded a video of my terminal to let you see what I get

Find the zip attached to this message with the mp4 file.

I was wondering how could I use your version of adb (41) because I already tried sudo apt install adb and it says I have the latest one available...

troubleshooting-scrcpy.zip

WARN: Device disconnected

If you rerun adb devices after that, does it say:

adb server version (41) doesn't match this client (36); killing...

?

If yes, then you have another program on your computer which executes adb 36.

Find this program, and either stop it, or make it use adb 41.

BTW.... the answer to your question is no.... it doesn't show that message you wrote.

Cheers :)

Your computer loses the connection with the device. You should try with another USB port or another USB cable. See #281 and #283.

Your computer loses the connection with the device. You should try with another USB port or another USB cable. See #281 and #283.

or check that your phone hasn't switched back to just charging. mine does that a couple times a day and i have to put it back on transfer files.

On Manjaro KDE 20.0.1 testing build and having issues launching Scrcpy. Hopefully the below will help you help me resolve the issue.

[gravedigger@Digger ~]$ adb disconnect
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
disconnected everything
[gravedigger@Digger ~]$ adb usb
error: no devices/emulators found
[gravedigger@Digger ~]$ adb usb //
error: no devices/emulators found
[gravedigger@Digger ~]$ adb devices
List of devices attached

[gravedigger@Digger ~]$ scrcpy -v
scrcpy 1.13

dependencies:
 - SDL 2.0.8
 - libavcodec 57.107.100
 - libavformat 57.83.100
 - libavutil 55.78.100
[gravedigger@Digger ~]$ adb push /usr/local/share/scrcpy/scrcpy-server.jar /data/local/tmp/
adb: error: failed to get feature set: no devices/emulators found
[gravedigger@Digger ~]$ SCRCPY_SERVER_PATH=/usr/local/share/scrcpy/scrcpy-server.jar scrcpy
.INFO: scrcpy 1.13 <https://github.com/Genymobile/scrcpy>
stat: No such file or directory
ERROR: '/usr/local/share/scrcpy/scrcpy-server.jar' does not exist or is not a regular file
[gravedigger@Digger ~]$ ./usr/local/share/scrcpy/scrcpy-server.jar
bash: ./usr/local/share/scrcpy/scrcpy-server.jar: No such file or directory
[gravedigger@Digger ~]$ adb --version
Android Debug Bridge version 1.0.41
Version 29.0.6-1
Installed as /usr/bin/adb
[gravedigger@Digger ~]$ echo $PATH
/home/gravedigger/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin
[gravedigger@Digger ~]$ which adb
/usr/bin/adb
[gravedigger@Digger ~]$ adb
Android Debug Bridge version 1.0.41
Version 29.0.6-1
Installed as /usr/bin/adb

global options:
 -a         listen on all network interfaces, not just localhost
 -d         use USB device (error if multiple devices connected)
 -e         use TCP/IP device (error if multiple TCP/IP devices available)
 -s SERIAL  use device with given serial (overrides $ANDROID_SERIAL)
 -t ID      use device with given transport id
 -H         name of adb server host [default=localhost]
 -P         port of adb server [default=5037]
 -L SOCKET  listen on given socket for adb server [default=tcp:localhost:5037]

general commands:
 devices [-l]             list connected devices (-l for long output)
 help                     show this help message
 version                  show version num

networking:
 connect HOST[:PORT]      connect to a device via TCP/IP
 disconnect [[HOST]:PORT] disconnect from given TCP/IP device, or all
 forward --list           list all forward socket connections
 forward [--no-rebind] LOCAL REMOTE
     forward socket connection using:
       tcp:<port> (<local> may be "tcp:0" to pick any open port)
       localabstract:<unix domain socket name>
       localreserved:<unix domain socket name>
       localfilesystem:<unix domain socket name>
       dev:<character device name>
       jdwp:<process pid> (remote only)
       acceptfd:<fd> (listen only)
 forward --remove LOCAL   remove specific forward socket connection
 forward --remove-all     remove all forward socket connections
 ppp TTY [PARAMETER...]   run PPP over USB
 reverse --list           list all reverse socket connections from device
 reverse [--no-rebind] REMOTE LOCAL
     reverse socket connection using:
       tcp:<port> (<remote> may be "tcp:0" to pick any open port)
       localabstract:<unix domain socket name>
       localreserved:<unix domain socket name>
       localfilesystem:<unix domain socket name>
 reverse --remove REMOTE  remove specific reverse socket connection
 reverse --remove-all     remove all reverse socket connections from device

file transfer:
 push [--sync] LOCAL... REMOTE
     copy local files/directories to device
     --sync: only push files that are newer on the host than the device
 pull [-a] REMOTE... LOCAL
     copy files/dirs from device
     -a: preserve file timestamp and mode
 sync [all|data|odm|oem|product|system|system_ext|vendor]
     sync a local build from $ANDROID_PRODUCT_OUT to the device (default all)
     -l: list files that would be copied, but don't copy them

shell:
 shell [-e ESCAPE] [-n] [-Tt] [-x] [COMMAND...]
     run remote shell command (interactive shell if no command given)
     -e: choose escape character, or "none"; default '~'
     -n: don't read from stdin
     -T: disable pty allocation
     -t: allocate a pty if on a tty (-tt: force pty allocation)
     -x: disable remote exit codes and stdout/stderr separation
 emu COMMAND              run emulator console command

app installation (see also `adb shell cmd package help`):
 install [-lrtsdg] [--instant] PACKAGE
     push a single package to the device and install it
 install-multiple [-lrtsdpg] [--instant] PACKAGE...
     push multiple APKs to the device for a single package and install them
 install-multi-package [-lrtsdpg] [--instant] PACKAGE...
     push one or more packages to the device and install them atomically
     -r: replace existing application
     -t: allow test packages
     -d: allow version code downgrade (debuggable packages only)
     -p: partial application install (install-multiple only)
     -g: grant all runtime permissions
     --abi ABI: override platform's default ABI
     --instant: cause the app to be installed as an ephemeral install app
     --no-streaming: always push APK to device and invoke Package Manager as separate steps
     --streaming: force streaming APK directly into Package Manager
     --fastdeploy: use fast deploy
     --no-fastdeploy: prevent use of fast deploy
     --force-agent: force update of deployment agent when using fast deploy
     --date-check-agent: update deployment agent when local version is newer and using fast deploy
     --version-check-agent: update deployment agent when local version has different version code and using fast deploy
     --local-agent: locate agent files from local source build (instead of SDK location)
     (See also `adb shell pm help` for more options.)
 uninstall [-k] PACKAGE
     remove this app package from the device
     '-k': keep the data and cache directories

debugging:
 bugreport [PATH]
     write bugreport to given PATH [default=bugreport.zip];
     if PATH is a directory, the bug report is saved in that directory.
     devices that don't support zipped bug reports output to stdout.
 jdwp                     list pids of processes hosting a JDWP transport
 logcat                   show device log (logcat --help for more)

security:
 disable-verity           disable dm-verity checking on userdebug builds
 enable-verity            re-enable dm-verity checking on userdebug builds
 keygen FILE
     generate adb public/private key; private key stored in FILE,

scripting:
 wait-for[-TRANSPORT]-STATE
     wait for device to be in the given state
     STATE: device, recovery, rescue, sideload, bootloader, or disconnect
     TRANSPORT: usb, local, or any [default=any]
 get-state                print offline | bootloader | device
 get-serialno             print <serial-number>
 get-devpath              print <device-path>
 remount [-R]
      remount partitions read-write. if a reboot is required, -R will
      will automatically reboot the device.
 reboot [bootloader|recovery|sideload|sideload-auto-reboot]
     reboot the device; defaults to booting system image but
     supports bootloader and recovery too. sideload reboots
     into recovery and automatically starts sideload mode,
     sideload-auto-reboot is the same but reboots after sideloading.
 sideload OTAPACKAGE      sideload the given full OTA package
 root                     restart adbd with root permissions
 unroot                   restart adbd without root permissions
 usb                      restart adbd listening on USB
 tcpip PORT               restart adbd listening on TCP on PORT

internal debugging:
 start-server             ensure that there is a server running
 kill-server              kill the server if it is running
 reconnect                kick connection from host side to force reconnect
 reconnect device         kick connection from device side to force reconnect
 reconnect offline        reset offline/unauthorized devices to force reconnect

environment variables:
 $ADB_TRACE
     comma-separated list of debug info to log:
     all,adb,sockets,packets,rwx,usb,sync,sysdeps,transport,jdwp
 $ADB_VENDOR_KEYS         colon-separated list of keys (files or directories)
 $ANDROID_SERIAL          serial number to connect to (see -s)
 $ANDROID_LOG_TAGS        tags to be used by logcat (see logcat --help)
 $ADB_LOCAL_TRANSPORT_MAX_PORT max emulator scan port (default 5585, 16 emus)
[gravedigger@Digger ~]$ snap install --edge --classic scrcpy
snap "scrcpy" is already installed, see 'snap help refresh'
[gravedigger@Digger ~]$ adb push
adb: push requires an argument
[gravedigger@Digger ~]$ adb push /var/lib/snapd/snap/scrcpy/131/usr/local/share/scrcpy/scrcpy-server.jar /data/local/tmp/
adb: error: failed to get feature set: no devices/emulators found
[gravedigger@Digger ~]$ 381 KB/s

Did you install it via snap?

The snap binary starts a container/chroot, which may be very confusing with adb and scrcpy server path (cf #464).

I suggest you to try a non-snap version (try to build from sources).

Did you install it via snap?

The snap binary starts a container/chroot, which may be very confusing with adb and scrcpy server path (cf #464).

I suggest you to try a non-snap version (try to build from sources).

OK just uninstalled and then built from source and still getting. Thanks for the quick reply.

INFO: scrcpy 1.13 <https://github.com/Genymobile/scrcpy>
adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
2020-07-21 13:25:58.243 scrcpy[91800:486388] INFO: scrcpy 1.14 <https://github.com/Genymobile/scrcpy>
/usr/local/Cellar/scrcpy/1.14_1/share/...pped. 1.4 MB/s (33142 bytes in 0.023s)
[server] INFO: Device: samsung SM-G935F (Android 8.0.0)
2020-07-21 13:25:59.939 scrcpy[91800:486388] INFO: OpenGL shaders: ENABLED
2020-07-21 13:25:59.940 scrcpy[91800:486388] INFO: Created renderer: opengl
2020-07-21 13:25:59.940 scrcpy[91800:486388] INFO: Renderer: opengl
2020-07-21 13:25:59.940 scrcpy[91800:486388] INFO: OpenGL version: 2.1 NVIDIA-10.4.14 310.90.30.05b27
2020-07-21 13:25:59.940 scrcpy[91800:486388] WARN: Trilinear filtering disabled (OpenGL 3.0+ or ES 2.0+ required)
2020-07-21 13:25:59.952 scrcpy[91800:486388] INFO: Initial texture: 1080x1920
2020-07-21 13:26:02.786 scrcpy[91800:486388] WARN: Device disconnected

please help me
always disconnected

@jeroapriyansah (please do not post in a thread totally unrelated)

Try with another USB cable/port (#281 #283).

@rom1v Thanks broo

how to sound in scrcpy android 8?

I did it;

open the CMD and go to the FOLDER where your files are.

cd C:scrcpy-win64-v1.14

write "adb kill-server"
C:scrcpy-win64-v1.14> adb kill-server

and after connet again

C:scrcpy-win64-v1.14> scrcpy.exe

Worked with me

i am getting this error can anyone help........
i have enabled usb debgging in my android device.

C:Windowssystem32>scrcpy
INFO: scrcpy 1.16 https://github.com/Genymobile/scrcpy
adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
Press any key to continue...

pls Where i write "scrcpy -s (my_number-serial)"? :(

On Windows (I guess):

  • press Windows+r
  • type cmd.exe and press Enter, it will open a terminal
  • type cd C:\the\path\to\your\scrcpy\directory (adapt the path)
  • type the command you want (scrcpy -s xxxxxxx)

If you're on Windows, you don't have to edit your path. Just copy adb into the scpy folder:
PS C:UsersMaLaCoiDDownloadsscrcpy> .scrcpy.exe
INFO: scrcpy 1.16 https://github.com/Genymobile/scrcpy
adb server version (36) doesn't match this client (41); killing...

  • daemon started successfully
    adb: error: failed to get feature set: no devices/emulators found
    ERROR: "adb push" returned with value 1
    Press any key to continue...

PS C:UsersMaLDownloadsscrcpy> cp 'C:Program Files (x86)Minimal ADB and Fastbootadb.exe' .

PS C:UsersMaLaCoiDDownloadsscrcpy> .scrcpy.exe
INFO: scrcpy 1.16 https://github.com/Genymobile/scrcpy
[100%] /data/local/tmp/scrcpy-server.jar
[server] INFO: Device: Google Chromecast (Android 10)
INFO: Renderer: direct3d
INFO: Initial texture: 1920x1080

I am getting the same error but I don't understand what I have to do please help

Ketikkan 'adb kill-server' , lalu enter.
Kemudian ketikkan 'adb start-server' enter.
setelah itu masuk lagi ke adb device

Was this page helpful?
0 / 5 - 0 ratings

Related issues

swamikamal picture swamikamal  Â·  3Comments

fleytman picture fleytman  Â·  4Comments

sennight picture sennight  Â·  3Comments

YurieCo picture YurieCo  Â·  4Comments

BloodPHamtOm picture BloodPHamtOm  Â·  3Comments