scrcpy: device unauthorized.
Huawei Mate 20 Pro
Dev Settings/USB Debugging = on
I get this:
adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
ERROR: "adb push" returned with value 1
Press any key to continue...
PS C:\scrcpy-win64> adb devices
List of devices attached
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully
LHS7N************* unauthorized
PS C:\scrcpy-win64>
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 19 (1 by maintainers)
If the device is in
unauthorizedstate as listed byadb devices(i.e. if USB debugging is enabled but not allowed on the device), then you can do the following steps.scrcpy --otg(see OTG)Now your device is authorized. You can run
scrcpy.You have two problems here:
adb). If this running daemon is not reexecuted as soon as it is killed, executingadb devicesone more time should not printadb server version (40) doesn't match this client (39); killing.... You should find the software which executesadbv39.unauthorizedif you didn’t authorize the connection on your device. A popup should open when you connect a device viaadb. Some buggy devices don’t always show this popup immediately. In that case, tryadb kill-server; adb start-server, unplug-replug, and if nothing works, use an oldadb(v39 or v36).https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#conflicts-between-adb-versions
(note: if you use the snap version, I suggest you try a non-snap version to use the same adb)
I will suggest trying all solution given above
and then try this if you are using ubuntu then go to home/.android and delete the adbkey then try above steps again like adb kill-server this should work now. note: if there is no .android then turn of show hidden files then it will be visible
In my case I’ve used
Spaceinstead ofEnter. Apart from that, thank you @rom1v and scrcpy for saving my life and 43GB of memories ❤️Oh, due to USB limitations on Windows, OTG mode does not work when USB debugging is enabled: #3050.
You should try on Linux (even a live USB of the latest Ubuntu is sufficient).
this giving this error INFO: Killing adb daemon (if any)… ERROR: I didn’t find any USB devices when I ran the command. and yet yes remains unauthorized. remembering that my phone’s screen is totally broken over with USB debugging turned on. any more way i can leave from unauthorized to device.
bro can you help with a doubt of mine? how can I take my device from unauthorized only with cmd commands. why the screen of my phone this all destroyed I used it by scrcpy most of nowhere stopped mirroring and began to appear this unauthorized always and I can not enable by the phone why the screen is broken as I allow to device only using cmd or other commands that my Windows support ? please any answer or explain whether of the right or not
@oujibahei https://stackoverflow.com/a/25546300/1987178