Home
last modified time | relevance | path

Searched refs:flash (Results 1 – 10 of 10) sorted by relevance

/system/core/fastboot/
DREADME.md97 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 …]
Dfastboot.bash83 flash)
Dtask.cpp43 auto flash = [&](const std::string& partition) { in Run() local
56 do_for_partitions(pname_, slot_, flash, true); in Run()
Dfastboot.cpp2158 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/
DREADME.android60 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/
DREADME.md38 You need to flash the device with a HWASAN userdebug build. For a blueline
/system/extras/simpleperf/doc/
Dandroid_platform_profiling.md7 Here are some tips for Android platform developers, who build and flash system images on rooted
/system/core/fs_mgr/tests/
Dadb-remount-test.sh1471 fastboot flash vendor "${TMPDIR}/vendor.img" ||
1560 fastboot flash --force scratch ${img}
/system/core/fs_mgr/libsnapshot/android/snapshot/
Dsnapshot.proto160 // The update was implicitly cancelled, either by a rollback or a flash
/system/update_engine/
DREADME.md514 [`cros flash`]: https://chromium.googlesource.com/chromiumos/docs/+/master/cros_flash.md