Lines Matching refs:adb

11       adb reboot bootloader
22       adb reboot bootloader
34     adb root
35     adb sync data
38     adb shell /data/nativetest/recovery_unit_test/recovery_unit_test
41     adb shell /data/nativetest64/recovery_unit_test/recovery_unit_test
56 Using `adb` under recovery
61 allows `adb` communication. A device should be listed under `adb devices`, either in `recovery` or
64     $ adb devices
69 subset of `adb` commands are meaningful under recovery, such as `adb root`, `adb shell`, `adb push`,
70 `adb pull` etc. Since Android Q, `adb shell` no longer requires manually mounting `/system` from
75 ### `adb devices` doesn't show the device.
77     $ adb devices
93 If `adbd` service has been started but device not shown under `adb devices`, use `lsusb(8)` (on
114 ### `adb devices` shows the device, but in `unauthorized` state.
116     $ adb devices
124  * **Option 1 (Recommended):** Authorize a host device with adb vendor keys.
131     $ export ADB_VENDOR_KEYS=/path/to/adb/private/key
132     $ adb kill-server
133     $ adb devices
141    * `ro.adb.secure` has a value of `0`.
143 Both of the two conditions need to be satisfied. Although `ro.adb.secure` is a runtime property, its