Repository navigation
device/dipper: record stage-0 facts and first light - #330
Conversation
Add Dipper device metadata, support package and firmware staging. Record non-A/B safety rules and hardware evidence without owner network identities. Keep local SSH settings out of the public tree.
|
Thank you for all this work, and for writing down so carefully what the hardware said. The first-light notes, the read-only stock backup with checksums on the phone, and keeping NV read-only throughout are exactly the habits this project runs on. Phones without A/B slots are welcome. Keeping stock on slot A is how we avoid bricking phones during development, not a permanent requirement, so a Mi 8 port can become a supported device. #383 adds a section to CONTRIBUTING §3.1 for phones without a second slot. To get there, a few changes:
A notes-only PR with the stage-0 facts and your first-light record is something I can take straight away while the rest comes together. |
Keep the early-probe lesson without linking to the kernel config removed from this notes-only PR.
The USB endpoint is project-standard and not needed to record first light; keep the public note free of private-range IPs.
|
Follow-up: the Dipper device bring-up now has a separate ready PR, #505. It adds a RAM-only descriptor and build path; it refuses flash/push/install and keeps UFS read-only. Kernel prerequisites are public in linux-omarchy-mobile PRs #218–#221; the button recovery entry is in #499. Wi-Fi and per-device identity remain disabled until the identity path reads persist with debugfs without mounting it. The kernel build and hardware probe are still pending. |
ac40d81 to
8680364
Compare
|
Thank you for cutting this down to the notes, and for working through every point from my last comment. I checked them one by one against the branch:
The identifier and blob checks pass on the branch. CI is waiting for my approval, and I'll approve it. One thing has to change before I can merge this as a record, because it's about what was written on the phone. The first-light record and the storage guard. Line 51 says "The storage guard works as designed:
Before the phone's next boot, either here or in a follow-up notes PR: the first version's state file records a lot more than first light, and the notes should hold it too. That means the NFS-root Omarchy sessions on 10-30, 10-31 and 11-02; the modem starts under Smaller things:
When I merge, I'll write the squash message myself. The branch's earlier commits ("add Xiaomi Mi 8 support … Record non-A/B safety rules", the bluez and panel commits, the merge of main) describe code that isn't in it any more. The title is fine as it is. |
|
Thank you for rewriting the first-light record. It now says plainly that the boot ran an unpublished tree, that a temporary init widened the allowlist for I checked each point from my last comment against the new head:
One correction of my own: on the kernel PR I doubted that the upstream FTS5 series had been tested on the Mi 8. David's cover letter says it was ("Also, tested on Xiaomi Mi 8"), so your sentence is right. If you link the cover letter instead of patch 4/5, the citation will say so directly. When I merge, I'll write the squash message myself, as I said last time. The title is fine. |
|
2026-11-09 update on the outstanding checks: the current On this handset, an attended hold of Power alone for more than 10 seconds restarted it. Volume Down + Power then entered fastboot; read-only variables confirmed product No PR #505 image has been booted and no partition has been written. The installed dirty kernel still has the root mounted read-write and logged failure to set the qcom watchdog timeout. The updated notes distinguish those old-kernel results from the pending PR-image probe. |
|
Thank you for this round. Everything from my last list is in: the dates of the Two things in the new 2026-11-09 entry need another look. The entry and your replies disagree. The entry (committed at 08:52 UTC) says
What the phone was running. The entry shows the old first-light kernel with the root on One more small thing: please quote the exact journal line about setting the And a nit: #221 is closed, so it can come out of the list of successor PRs. When I merge, I'll write the squash message myself. The title is fine. |
|
Thank you, this is a big step: the first boot of #505's own image, recorded with the checks the runbook asked for. Three things before I merge: 1. Please keep each boot. The commits show three RAM boots today: 2. What 3. One wording fix. "FTS5 PR #219 is now merged upstream": #219 was merged into this project's kernel branch ( And one suggestion for the next RAM boot, not a condition: you've tried the Power-hold restart from Android. On another phone, Power alone did nothing under our kernel, so it's worth one attended try while the RAM image is running and healthy, with Volume Down + Power ready for fastboot. When I merge, I'll write the squash message myself. The title is fine. |
|
I updated the notes in
The exact stock recovery package is not in the retained local artifacts, but the recovery header check matches the 4.9 MIUI kernel you suggested. |
|
Updated the device notes: holding Power for 10 seconds restarted the phone back into Android under both the installed system and the Omarchy Mobile RAM kernel. The earlier “not tested under our kernel” qualification has been removed. |
|
The notes now include the partial NFS-root run from #503: image hash, NFS/systemd handover, persistent guard log confirmations for 85 partitions and six UFS disks, generic Arch ARM root limitation, and the missing direct sysfs capture/post-#484 check. |
|
Thank you for all of this. The record now answers what I asked: Two fixes to the record, and then I'll merge. Neither needs another boot. 1. The list of boots, and the two hashes aren't lost. You wrote that the first two image hashes are no longer in your artifacts. They are in this branch's own history:
Could you add one table of the day's RAM sessions to the notes? By my count there are seven now: those two, 2. "Stock". Your 10-29 section says the phone runs a custom Android 14 ROM with Magisk on a 4.9.337 kernel, not MIUI. So the Two smaller things for the same push:
I'll write the squash message myself; the title will be |
|
I rechecked the exact local image with SHA-256 |
|
Added the final exact-image hardware record in the latest PR head |
|
Thank you for the three pushes since my last comment, and above all for the correction in The four points from my last comment are still open. I think they crossed with your pushes, so here they are again, with what changed since. None needs a boot. 1. One table of the RAM sessions. It matters more now than yesterday, because the file's paragraphs switch between images and one image turned out to be something else. By my reading there are about eleven sessions:
One row each: date, sha256, what it was built from as far as you know, the state of 2. What 3. "Stock". The file still says "the stock recovery image", "stock 4. Two short additions.
Small things for the same push: "Hence I'll write the squash message myself; the title will be |
|
Updated the notes in commit |
|
Thank you, @quatrixone. I'm merging this. One thing for your next push to the notes, not for this one: the table's last two rows say |
…0 RAM boots (derekross#330) The Xiaomi Mi 8's installed-system facts read on 2026-10-29 (SDM845, single boot partition, EA8074 panel, ST FTS5 touch), the first light on an unpublished kernel with its limits, and a table of the eleven RAM-only sessions of 2026-11-09 and 11-10 with each image's sha256, source and storage-guard state. Notes only; no captures or identifiers, and nothing here is a recovery procedure yet.
Summary
Record the Xiaomi Mi 8 (
dipper) stock hardware facts, the historical 2026-10-29 first-light result, and the additional storage and modem activity that can be established from the available notes. This is a notes-only change.The note contains no captures, serials, MAC addresses, Wi-Fi credentials, or private host/path details. Device support code and shared changes remain in their own PRs.
The current RAM-only image and storage guard keep UFS read-only by design. The historical
recoveryimage checksum,logdumpbackup coverage, exact intervening boot sequence and first-light mount options still need source/backup verification before these notes can serve as a recovery record. No phone action was performed for this revision.Checks
git diff --check— passed