diff --git a/device/tegu/FINGERPRINT-PLAN.md b/device/tegu/FINGERPRINT-PLAN.md index 73b17337f..3c9bdf88d 100644 --- a/device/tegu/FINGERPRINT-PLAN.md +++ b/device/tegu/FINGERPRINT-PLAN.md @@ -1,7 +1,7 @@ # Fingerprint plan (tegu / zumapro): fingerprint unlock on the palmtop -Status (2026-10-27, night): **F0, F2, F6a and F6b passed; F3-F5 and F6c wait for D1.** Earlier: **research and plan only, nothing run on the palmtop for +Status (2026-10-28): **F0 and F2-F5 passed (F4, the first RPMB write, on 2026-10-27 under D1 = A); F6a and F6b passed; F6c waits for the factory calibration, which the owner fetched on 2026-10-28.** Earlier: **research and plan only, nothing run on the palmtop for fingerprint.** Stage 16 of ALL-HARDWARE-PLAN (private). The Pixel 7 Pro stack works ([cheetah FINGERPRINT-PLAN](../cheetah/FINGERPRINT-PLAN.md), opt-in); this plan says what carries over to the Pixel 9a and what is new. @@ -202,6 +202,10 @@ New for tegu: (`dd` from the node found by `PARTNAME`), and `persist` is read from the off-phone backup image, not mounted on the palmtop (f2fs: a read-only mount can still run recovery). Never add them to `UFS_RW`. +- `fastboot oem udfps update-cal`, or any other `oem` command that writes, + doesn't run without Derek's explicit go and a named exception: it writes + `mfg_data`, outside slot B and `userdata`. Every `fastboot oem` step in a + runbook pins the serial with `-s`. - `sg` stays blacklisted from autoload; the runner loads it and binds only the RPMB LUN's node. - `gpp1` is shared with the touchscreen reset (`gpp1-1`): the fingerprint pin @@ -232,7 +236,14 @@ New for tegu: Neither choice can roll back the RPMB: its write counter and superblocks move at the first run either way. -**Decision:** _not taken yet._ +**Decision (2026-10-27): A, with the stores as block devices.** Taken by +the owner (W4HO) at the console on 2026-10-27, evening: he never runs +stock Android, so nothing is written outside `userdata` and stock on slot A +is left to need a factory reset if it's ever booted. Within A, the stores +are loop devices of Linux-owned images in `/var/lib/omamobile-fp` +(`td.img`, `tdp.img`; step F4b), so storageproxyd gets its `-m` limit from +a block device and maps `0` and `persist/0` the way stock does, but onto +those images, never onto `trusty_userdata` or `trusty_persist`. ## 7. Runbook @@ -321,6 +332,33 @@ requests, `fs_ready`, Trusty's log mounting its stores (TD new under A). retry loop, collect the logs. Rollback: stop the unit; the RPMB cannot be rolled back. Risk: irreversible for the RPMB; low for the running system. +### F4b: the store images (TD and TDP as block devices; risk: low) + +Only on the 9a (the runner maps them only there, and only when the files +exist). Both live in `/var/lib/omamobile-fp` (0700, root), are made on the +palmtop and are **never committed or copied off it** (they hold Trusty's +secure-storage state): + +```sh +# TD: a fresh, empty 128 MiB store; storageproxyd takes its -m limit from it +truncate -s 128M /var/lib/omamobile-fp/td.img && chmod 600 /var/lib/omamobile-fp/td.img +# TDP: the F3 copy of trusty_persist (read-only copy, same size). Before the +# first mapped run it is persist-ss/0; after it, that path is the link and the +# copy is persist-ss/0.before-map.