Flashing safely
Flashberry deliberately separates image creation from physical-device writes.
The flash target uses the dedicated privileged flasher container.
Identify the target
Inspect block devices on the host and determine the whole-disk node for the SD
card. A typical removable device might be /dev/sdb or /dev/mmcblk0, but you
must verify this on your machine.
Unmount every partition belonging to the target before continuing.
Flash
Flashberry rejects:
- paths that are not block devices;
- partitions instead of whole disks;
- mounted disks or disks with mounted partitions.
It asks for the literal confirmation yes before writing.
Select an explicit image
By default, Flashberry chooses the newest .img or .img.zst in out/. To
remove ambiguity, provide IMAGE explicitly:
When a .zst.sha256 file accompanies a compressed image, the checksum is
verified before the destructive write starts.
Danger
Do not use FLASHBERRY_FORCE=1 merely to bypass a mounted-device rejection.
Treat that rejection as evidence that the target is still in use.