leoppark94 · Oct 29, 2026 · coderabbitai · Oct 29, 2026
diff --git a/docs/getting-started/writing-the-image.md b/docs/getting-started/writing-the-image.md
@@ -5,7 +5,7 @@ description: "Write an Armbian image to an SD card with Armbian Imager, or flash
 ---
 # Writing the image to your media
 
-There are multiple ways to deploy the image to your board. The easiest and most common option is to write the Armbian Image to your SD-Card. 
+There are multiple ways to deploy the image to your board. The easiest and most common option is to write the Armbian Image to your SD-Card.
 
 ## Flash to SD Card
 
@@ -160,6 +160,69 @@ Steps:
     The board is not in EDL mode, or the cable is data-only. Re-enter EDL mode as
     in step 1, try a different USB cable or port, and reconnect.
 
+### SpacemiT
+
+SpacemiT boards such as the **Firefly AIBOX-K3** keep their bootloader in SPI
+NOR flash. Their vendor U-Boot may not enumerate removable media, so the image
+is written directly to the board's **UFS** storage with SpacemiT's flashing
+suite, **TitanTools / TitanFlasher**, over USB. The suite runs on Windows, and
+on Linux as an AppImage.
+
+1. Download the Armbian image and unpack it if it is compressed, for example
+   with `unxz`.
+
+2. Split the image into its two partitions. On the AIBOX-K3 the layout is
+   fixed by the vendor firmware: `bootfs` starts at 12 MiB and is 256 MiB,
+   `rootfs` starts at 268 MiB and fills the rest of the image.
+
+    ``` bash
+    dd if=Armbian-...-aibox-k3-....img of=bootfs.img bs=1M skip=12 count=256
+    dd if=Armbian-...-aibox-k3-....img of=rootfs.ext4 bs=1M skip=268
+    ```pa
-    ```pa
+    ```
-    ```pa
+    ```
+
+    Images built for a different layout need their own offsets; read them with
+    `fdisk -l` first in that case.
+
+3. Download the firmware package that the board vendor provides and unpack it.
+   It contains the partition layout and the bootloader images.
+
+4. Put the board into flashing mode:
+    - **MaskRom**: hold the **Boot** button while connecting power.
+
+5. Open TitanFlasher and go to **Dev Tools** and **USB Download**. Click
+   **Scan Devices** and select the board, which is detected as a DFU device.
+   Choose the unpacked vendor directory with **Local Dir**.
+
+    ![TitanFlasher USB Download](../images/titanflasher-usb-download.png)
+
+6. TitanFlasher lists every partition of the layout. Press **Replace** next to
+   `bootfs` and `rootfs` and select the files from step 2. Leave the other
+   partitions as they are.
+
+7. Press **Start Flashing**, then power-cycle the board.
+
+!!! note "Replacing the bootloader"
+
+    Only `bootfs` and `rootfs` belong to Armbian. Leave the remaining
+    partitions selected only if you also want to restore the vendor
+    bootloader into SPI NOR. In that case enable **Configure Partition File**
+    and select both `partition_4M.json` (NOR) and `partition_universal.json`
+    (UFS).
+
+![Select partition file](../images/titanflasher-partition-file.png)
+
+!!! note "Sector size"
+
+    Armbian images for these boards use 4 KiB sectors because the UFS reports
+    4096-byte logical sectors. A 512-byte image cannot mount its boot partition
+    on this storage.
+
+!!! tip "Vendor manual"
+
+    See the [SpacemiT flashing tool manual](https://www.spacemit.com/community/document/info?lang=en&nodepath=tools%2Fuser_guide%2Fflasher_user_guide.md)
+    and the [Firefly AIBOX-K3 firmware upgrade guide](https://wiki.t-firefly.com/en/AIBOX-K3/upgrade_firmware.html)
+    for the full description of the interface.
+
 ---
 
 **Previous:** [Choosing an Armbian image](choosing-an-image.md)

diff --git a/docs/images/titanflasher-partition-file.png b/docs/images/titanflasher-partition-file.png
diff --git a/docs/images/titanflasher-usb-download.png b/docs/images/titanflasher-usb-download.png