Skip this step if you already know the package name. The following sequence of commands is what worked for me on a non-rooted device:ĭetermine the package name of the app, e.g. You are receiving this because you were mentioned.None of these suggestions worked for me, because Android was appending a sequence number to the package name to produce the final APK file name (this may vary with the version of Android OS). Reply to this email directly, view it on GitHub, or unsubscribe. I also checked *adb shell ls /system/bin/app_** and *adb shell ls /vendor/bin/app_** getting "no such file or directory". On Windows that usually translates to %USERPROFILE%.android, but keys might end up in C:\Windows\System32\config\systemprofile.android in some cases.Īdb push ~/.android/adbkey.pub /data/misc/adb/adb_keys Bibliography FootnotesĬ:\scrcpy-win64-v1.23\scrcpy-server.jar: 1 file pushed, 0 skipped. In Linux the directory location is $HOME/.android/. In Lollipop, the ADB keys (after authorization) are saved in /data/misc/adb/adb_keys. Verify options are not present before do it: adb shell "grep '' /system/build.prop" adb shellĮcho '# Enable ADB' > /system/build.propĮcho '=1' > /system/build.propĮcho '=1' > /system/build.propĮcho '=mtp,adb' > /system/build.propįor the RSA verification that you asked to bypass, I don't know whether it would work in your device, but it worked in my little experiment.
Same as "Settings > Developer Opcions > USB debugging" ON
0 kommentar(er)
