| /bootable/recovery/ |
| D | Android.mk | 48 libbase.recovery \
49 liblog.recovery \
50 librecovery_ui.recovery
66 make_f2fs.recovery \
67 fsck.f2fs.recovery \
68 sload_f2fs.recovery
72 mkfs.erofs.recovery \
73 dump.erofs.recovery \
74 fsck.erofs.recovery
80 LOCAL_REQUIRED_MODULES += recovery-persist
[all …]
|
| D | README.md | 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
[all …]
|
| D | Android.bp | 137 "recovery.cpp",
150 recovery: true,
154 name: "recovery",
155 recovery: true,
179 "e2fsdroid.recovery",
183 "mke2fs.conf.recovery",
184 "mke2fs.recovery",
186 "ueventd.rc.recovery",
192 name: "recovery-persist",
199 "recovery-persist.cpp",
[all …]
|
| D | CleanSpec.mk | 49 $(call add-clean-step, rm -rf $(PRODUCT_OUT)/recovery/root/sbin)
52 $(call add-clean-step, rm -rf $(PRODUCT_OUT)/recovery/root/system/lib64/libinstall.so)
68 …DUCT_OUT)/obj/PACKAGING/target_files_intermediates/*-target_files-*/SYSTEM/bin/install-recovery.sh)
69 …CT_OUT)/obj/PACKAGING/target_files_intermediates/*-target_files-*/SYSTEM/etc/recovery-resource.dat)
70 …PRODUCT_OUT)/obj/PACKAGING/target_files_intermediates/*-target_files-*/SYSTEM/recovery-from-boot.p)
|
| D | recovery-persist.rc | 2 mkdir /data/misc/recovery 0770 system log
3 exec_background - system log -- /system/bin/recovery-persist
|
| D | recovery-refresh.rc | 2 exec_background - system log -- /system/bin/recovery-refresh
|
| D | .clang-format | 1 # bootable/recovery project uses repohook to apply `clang-format` to the changed lines, with the
13 # default behavior for bootable/recovery project.
|
| D | recovery_main.cpp | 125 boot.recovery[sizeof(boot.recovery) - 1] = '\0'; // Ensure termination in get_args()
126 std::string boot_recovery(boot.recovery); in get_args()
134 } else if (boot.recovery[0] != 0) { in get_args()
|
| /bootable/recovery/minadbd/ |
| D | README.md | 5 recovery-specific use cases. Generally speaking, `adbd` = `libadbd` + `libadbd_services`, whereas
8 Although both modules may be installed into the recovery image, only one of them, or none, can be
12 or `none` respectively. Upon starting recovery mode, `adbd` is started in debuggable builds by
14 `bootable/recovery/etc/init.rc`.
16 - `minadbd` is started by `recovery` as needed.
17 - When requested to start `minadbd`, `recovery` stops `adbd` first, if it's running; it then forks
21 - `minadbd` communicates with `recovery` to fulfill requests regarding package installation. See
22 the comments in `bootable/recovery/install/adb_install.cpp` for the IPC protocol between
23 `recovery` and `minadbd`.
24 - Upon exiting `minadbd`, `recovery` restarts `adbd` if it was previously running.
|
| D | Android.bp | 82 "//bootable/recovery/install",
88 recovery: true,
|
| /bootable/recovery/tests/unit/ |
| D | bootloader_message_test.cpp | 36 strlcpy(boot.recovery, "message1\nmessage2\n", sizeof(boot.recovery)); in TEST()
58 strlcpy(boot.recovery, "random message", sizeof(boot.recovery)); in TEST()
68 ASSERT_EQ(expected, std::string(boot.recovery)); in TEST()
86 ASSERT_EQ("recovery\n", std::string(boot.recovery)); in TEST()
108 ASSERT_GE(expected.size(), sizeof(boot.recovery)); in TEST()
112 ASSERT_EQ(expected.substr(0, sizeof(boot.recovery) - 1), std::string(boot.recovery)); in TEST()
113 ASSERT_EQ('\0', boot.recovery[sizeof(boot.recovery) - 1]); in TEST()
|
| D | uncrypt_test.cpp | 137 ASSERT_EQ(message_in_bcb, std::string(boot.recovery)); in SetupOrClearBcb()
140 ASSERT_LE(message_in_bcb.size(), sizeof(boot.recovery)); in SetupOrClearBcb()
141 size_t left = sizeof(boot.recovery) - message_in_bcb.size(); in SetupOrClearBcb()
142 ASSERT_EQ(std::string(left, '\0'), std::string(&boot.recovery[message_in_bcb.size()], left)); in SetupOrClearBcb()
|
| /bootable/recovery/etc/ |
| D | init.rc | 1 import /init.recovery.${ro.hardware}.rc
86 service recovery /system/bin/recovery
87 socket recovery stream 422 system system
88 seclabel u:r:recovery:s0
91 service adbd /system/bin/adbd --root_seclabel=u:r:su:s0 --device_banner=recovery
110 write /config/usb_gadget/g1/idVendor 0x${ro.recovery.usb.vid}
124 write /sys/class/android_usb/android0/idVendor ${ro.recovery.usb.vid}
149 write /sys/class/android_usb/android0/idProduct ${ro.recovery.usb.adb.pid}
155 write /sys/class/android_usb/android0/idProduct ${ro.recovery.usb.adb.pid}
161 write /sys/class/android_usb/android0/idProduct ${ro.recovery.usb.fastboot.pid}
[all …]
|
| /bootable/recovery/recovery_utils/ |
| D | Android.bp | 53 // A utility lib that's local to recovery (in contrast, libotautil is exposed to device-specific
80 // to the recovery ramdisk.) Hence, minadbd_test must link to it
97 "//bootable/recovery",
98 "//bootable/recovery/install",
99 "//bootable/recovery/minadbd",
100 "//bootable/recovery/tests",
|
| /bootable/recovery/bootloader_message/ |
| D | bootloader_message.cpp | 204 LOG(INFO) << "Writing BCB " << boot.command << " " << boot.recovery; in update_bootloader_message()
214 memset(boot->recovery, 0, sizeof(boot->recovery)); in update_bootloader_message_in_struct()
218 std::string recovery = "recovery\n"; in update_bootloader_message_in_struct() local
220 recovery += s; in update_bootloader_message_in_struct()
222 recovery += '\n'; in update_bootloader_message_in_struct()
225 strlcpy(boot->recovery, recovery.c_str(), sizeof(boot->recovery)); in update_bootloader_message_in_struct()
239 LOG(INFO) << "Writing BCB cmd: " << boot.command << " args: " << boot.recovery; in write_reboot_bootloader()
|
| /bootable/deprecated-ota/tests/unit/ |
| D | applypatch_modes_test.cpp | 61 recovery = GetEmmcTargetString(recovery_file); in SetUp()
62 ASSERT_FALSE(recovery.empty()); in SetUp()
73 std::string recovery; member in ApplyPatchModesTest
184 ASSERT_EQ(0, InvokeApplyPatchModes({ "applypatch", "--check", recovery })); in TEST_F()
|
| /bootable/deprecated-ota/tests/unit/host/ |
| D | update_simulator_test.cpp | 333 { "RECOVERY/RAMDISK/etc/recovery.fstab", fstab_content_ },
354 string recovery_img_string = "recovery.img";
359 { "IMAGES/recovery.img", "" },
362 { "RECOVERY/RAMDISK/etc/recovery.fstab", fstab_content_ },
374 "EMMC:/dev/block/by-name/recovery:%zu:%s", recovery_img_string.size(), recovery_sha1.c_str());
|
| /bootable/recovery/tests/manual/ |
| D | recovery_test.cpp | 51 TEST(recovery, refresh) { in TEST() argument
69 TEST(recovery, persist) { in TEST() argument
|
| /bootable/recovery/tests/ |
| D | Android.bp | 33 "bootable/recovery",
89 // recovery image for unittests.
100 "testdata/recovery.img",
|
| /bootable/recovery/tools/image_generator/ |
| D | ImageGenerator.mf | 1 Main-Class: com.android.recovery.tools.ImageGenerator
|
| D | README.md | 5 under recovery mode. And thus we don't need to do the manual work by running
20 strings in xml format, e.g. bootable/recovery/tools/recovery_l10n/res/
|
| /bootable/deprecated-ota/applypatch/ |
| D | vendor_flash_recovery.rc | 1 service vendor_flash_recovery /vendor/bin/install-recovery.sh
|
| /bootable/recovery/tools/recovery_l10n/ |
| D | README.md | 5 cd bootable/recovery && mma -j32
34 image works by running graphic tests under the recovery mode.
|
| /bootable/deprecated-ota/tests/ |
| D | Android.bp | 22 "bootable/recovery/tests",
85 "bootable/recovery/tests",
|
| /bootable/libbootloader/gbl/libmisc/src/ |
| D | lib.rs | 66 recovery: [u8; 768], field
110 recovery: [0; 768], in default()
|