Lines Matching refs:recovery

7 * Devices using recovery-as-boot (e.g. Pixels, which set BOARD\_USES\_RECOVERY\_AS\_BOOT)
13       # Pixel devices don't support booting into recovery mode with `fastboot boot`.
18 * Devices with a separate recovery image (e.g. Nexus)
24       # To boot into the new recovery image without flashing the recovery partition:
25       fastboot boot $ANDROID_PRODUCT_OUT/recovery.img
31     mmma -j bootable/recovery
46 `recovery-refresh` and `recovery-persist` executables exist only on systems without
53   contents of pmsg buffer into /data/misc/recovery/inject.txt. Test will pass if
56 Using `adb` under recovery
59 When running recovery image from debuggable builds (i.e. `-eng` or `-userdebug` build variants, or
61 allows `adb` communication. A device should be listed under `adb devices`, either in `recovery` or
66     1234567890abcdef    recovery
69 subset of `adb` commands are meaningful under recovery, such as `adb root`, `adb shell`, `adb push`,
71 recovery menu.
82 By default, `adbd` is always included into recovery image, as `/system/bin/adbd`. `init` starts
83 `adbd` service automatically only in debuggable builds. This behavior is controlled by the recovery
84 specific `/init.rc`, whose source code is at `bootable/recovery/etc/init.rc`.
96 `bootable/recovery/etc/init.rc` disables Android USB gadget (via sysfs) as part of the `fs` action
110 configuration](https://android.googlesource.com/device/google/wahoo/+/master/init.recovery.hardware…
120 recovery image doesn't honor the USB debugging toggle and the authorizations added under normal boot
121 (because such authorization data stays in /data, which recovery doesn't mount), nor does it support
122 authorizing a host device under recovery. We can use one of the following options instead.
137 Note that this mechanism applies to both of normal boot and recovery modes.