en/cubie/a7a/getting-started/install-system/ufs-system/no-reader

[giscus[bot]]

en/cubie/a7a/getting-started/install-system/ufs-system/no-reader

UFS modules offer significantly faster read/write speeds compared to microSD cards and eMMC modules, making them an excellent choice for users looking to enhance system performance and boot times.

https://docs.radxa.com/en/cubie/a7a/getting-started/install-system/ufs-system/no-reader

[thecurryspice]

Probably worth mentioning that the files available Downloads page are .xz archives and need to be decompressed to .img before dd-ing it onto the UFS module.
After downloading the <variant>.img.xz,

Either pipe directly (no temp space needed)

xz -dc <variant>.img.xz | sudo dd of=/dev/sda bs=4M status=progress

Or

xz -d <variant>.img.xz
sudo dd if=<variant>.img of=/dev/sda bs=4M status=progress

Now using sudo fdisk -l /dev/sda should show the same partitions/sectors as mentioned.

[tangzz-radxa]

Thanks for flagging this — the gap is real and your example is exactly the missing piece. I just opened a docs PR that adds an explicit unxz step (mirroring the existing pattern in docs/rock5/rock5t/getting-started/install-os/emmc_boot.md) plus both options you described:

• unxz <variant>.img.xz then sudo dd if=<variant>.img of=/dev/sda bs=4M status=progress
• pipe directly: xz -dc <variant>.img.xz | sudo dd of=/dev/sda bs=4M status=progress

PR: #1833

CN and EN versions updated in sync.