Searched refs:flash (Results 1 – 9 of 9) sorted by relevance
/system/core/fastboot/ |
D | fastboot.bash | 83 flash)
|
D | README.md | 88 Host: "flash:bootloader" request to flash the data to the bootloader 90 Client: "INFOerasing flash" indicate status / progress 91 "INFOwriting flash" 124 by "boot", "ramdisk", "flash", etc. The client 139 flash:%s Write the previously downloaded image to the 196 partition. Unlike the "flash" command, this has 364 minute during long operations, e.g. writing to flash.
|
D | fastboot.cpp | 1436 auto flash = [&, this](const std::string& partition_name) { in FlashImage() local 1448 do_for_partitions(image.part_name, slot, flash, false); in FlashImage() 1737 auto flash = [&](const std::string& partition_name) { in wipe_super() local 1740 do_for_partitions(partition, slot, flash, force_slot); in wipe_super() 2050 auto flash = [&](const std::string &partition) { in Main() local 2063 do_for_partitions(pname, slot_override, flash, true); in Main()
|
/system/core/fs_mgr/tests/ |
D | adb-remount-test.sh | 1432 fastboot flash vendor || 1491 check_eq "${A}" "${B}" system after flash vendor 1497 check_eq "${A}" "${B}" system/priv-app after flash vendor 1503 vendor content after flash vendor 1507 --warning vendor content after flash vendor 1566 fastboot flash --force ${scratch_partition} ${img}
|
/system/timezone/ |
D | README.android | 71 5) Build/flash a device image with the changes and run CTS: 163 3) Build/flash a device image with the changes and run CTS tests:
|
/system/extras/simpleperf/doc/ |
D | android_platform_profiling.md | 12 Here are some tips for Android platform developers, who build and flash system images on rooted
|
/system/core/fs_mgr/libsnapshot/android/snapshot/ |
D | snapshot.proto | 113 // The update was implicitly cancelled, either by a rollback or a flash
|
/system/update_engine/ |
D | README.md | 251 flash`], AU autotests, etc. Similarly the updater server uses this file to 427 the image on the device using cros flash, etc. or use `cros deploy` to only 515 * Use [`cros flash`]. It internally uses the update_engine to flash a device 636 [`cros flash`]: https://chromium.googlesource.com/chromiumos/docs/+/master/cros_flash.md
|
/system/core/adb/ |
D | protocol.txt | 261 "flash_ramdisk,5038,........\n" "fail,flash write error\n"
|