Searched refs:flash (Results 1 – 10 of 10) sorted by relevance
| /system/core/fastboot/ |
| D | README.md | 97 Host: "flash:bootloader" request to flash the data to the bootloader
99 Client: "INFOerasing flash" indicate status / progress
100 "INFOwriting flash"
133 by "boot", "ramdisk", "flash", etc. The client
148 flash:%s Write the previously downloaded image to the
178 flash %s Flash a given partition. Optional arguments include
195 optimized flash super task. Fastboot will explicitly pattern match the
202 update-super ---> generate optimized flash super task
204 flash {dynamic partition}
242 partition. Unlike the "flash" command, this has
[all …]
|
| D | fastboot.bash | 83 flash)
|
| D | task.cpp | 43 auto flash = [&](const std::string& partition) { in Run() local
56 do_for_partitions(pname_, slot_, flash, true); in Run()
|
| D | fastboot.cpp | 2158 auto flash = [&](const std::string& partition_name) { in wipe_super() local
2161 do_for_partitions(partition, slot, flash, force_slot); in wipe_super()
|
| /system/timezone/ |
| D | README.android | 60 5) Build/flash a device image with the changes and run CTS:
186 3) Build/flash a device image with the changes and run tests from "IANA rules data changes" section.
|
| /system/nfc/src/fuzzers/ |
| D | README.md | 38 You need to flash the device with a HWASAN userdebug build. For a blueline
|
| /system/extras/simpleperf/doc/ |
| D | android_platform_profiling.md | 7 Here are some tips for Android platform developers, who build and flash system images on rooted
|
| /system/core/fs_mgr/tests/ |
| D | adb-remount-test.sh | 1471 fastboot flash vendor "${TMPDIR}/vendor.img" ||
1560 fastboot flash --force scratch ${img}
|
| /system/core/fs_mgr/libsnapshot/android/snapshot/ |
| D | snapshot.proto | 160 // The update was implicitly cancelled, either by a rollback or a flash
|
| /system/update_engine/ |
| D | README.md | 514 [`cros flash`]: https://chromium.googlesource.com/chromiumos/docs/+/master/cros_flash.md
|