microSD system card
The default FPLinux build runs entirely from RAM and forgets everything at power-off. The microSD system card keeps the Linux system on a microSD card instead: installed packages, Bluetooth pairings and your files survive a cold start. The profile selects boot and storage behavior; it does not establish hardware support.
Every cold start still begins from the PC with a fresh USB load. The profile determines which parts come from the PC and which come from the card:
| Target | Profile | Loaded over USB | Read from the card |
|---|---|---|---|
| UMS9117 targets with system-card support | microsd-uboot |
U-Boot | Linux boot image and ext4 system root |
| Xiaomi Qin 1s+ | microsd-root |
Linux | ext4 system root |
Use a profile only if your phone supports it. Check its support status and phone page for card and feature limits, including any features tested only in the RAM profile. The Qin profile uses a Linux source checkout or ordinary Linux runner archive, with its loader stages included in the build.
Build the card image
Section titled “Build the card image”Prepare any phone data you want in the system card from the checkout you will build; see Device data. Another checkout may have refreshed the shared personal store with different preparation inputs. UMS9117’s automatic preparation uses the default RAM build. Run device-data prepare in the selected checkout, then build the system-card profile explicitly. The RAM data capsule does not update firmware or the boot image on a card that is already written.
For a supported UMS9117 phone, use its exact target in place of nokia-ta1618:
./fplinux build nokia-ta1618 --profile microsd-ubootFor the Xiaomi Qin 1s+, select its profile explicitly:
./fplinux build xiaomi-qin-1s-plus --profile microsd-rootThe build directory printed after output: contains FPLINUX.img.xz, a compressed image of a whole card. The build never writes to a card. To find the directory later, run ./fplinux inspect bundle with the same target, profile and build type and read its bundle: line.
Prepare the card
Section titled “Prepare the card”FPLINUX.img.xz is a complete disk image with its own partition table, not a file to copy onto an existing filesystem. Writing it replaces the card’s partition table and everything on the card.
| Profile | Partition | Initial size | Filesystem | Label | Contents |
|---|---|---|---|---|---|
microsd-uboot |
1 | 64 MiB | FAT32 | FPLBOOT |
FPLINUX.ITB boot image |
microsd-uboot |
2 | 64 MiB | ext4 | FPLROOT |
the system, mounted as / |
microsd-root |
1 | 64 MiB | FAT32 | FPLDATA |
empty |
microsd-root |
2 | 512 MiB | ext4 | FPLROOT |
the system, mounted as / |
On the first boot, Linux extends partition 2 and its filesystem to the end of the card. Later boots leave a full-size partition unchanged.
Never write the image from a system that runs from the same card. To rewrite a system card inside the phone, boot the default RAM system first, stop everything that uses the card and unmount all of its filesystems. Read the image back and compare it before the next microSD boot.
Boot from the card
Section titled “Boot from the card”-
With the phone powered off, insert the prepared card.
-
Start the loader with the profile you built and connect the phone when it asks, as in Run FPLinux. Choose the command for your phone:
PC — UMS9117 ./fplinux run nokia-ta1618 --profile microsd-ubootPC — Xiaomi Qin 1s+ ./fplinux run xiaomi-qin-1s-plus --profile microsd-rootOn UMS9117,
--boot microsdis an alternative to--profile microsd-uboot. It always selects that profile and cannot select Qin’smicrosd-root. Use either--bootor--profile, not both. -
Leave the card in the phone for the whole session.
When reconnecting or checking the running build, pass the same profile and build type you selected.
What persists
Section titled “What persists”Everything on the ext4 root survives a cold start: installed packages, Bluetooth pairing records and your files. Files in RAM filesystems such as /tmp do not.
With microsd-uboot, keep FPLBOOT for the boot image. Do not mount it as application storage at /mnt/card.
Shut down
Section titled “Shut down”The system card cannot be unmounted or removed while Linux runs, and sync alone does not make it safe to cut power. Before you cut power or remove the card, shut down as described in Power.
Standalone archives
Section titled “Standalone archives”An ordinary Linux archive packaged for the system-card profile contains FPLINUX.img.xz. Pass --boot microsd for UMS9117 or --profile microsd-root for Qin to ./fplinux package. Prepare the card from that file first; the archive’s runner then loads the phone. See Standalone archive and Packaging.