Skip to content

flame: split opt-in boot plumbing from pending writes - #56

Draft
wirelessjoe wants to merge 1 commit into
derekross:mainfrom
wirelessjoe:fix/flame-boot-plumbing
Draft

wirelessjoe wants to merge 1 commit into
derekross:mainfrom
wirelessjoe:fix/flame-boot-plumbing

Conversation

@wirelessjoe

@wirelessjoe wirelessjoe commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

What and why

Part (a) of the requested split of #17, following Derek's current review. Based directly on current main 671b089; conflicts with the old proposal have been resolved.

Opt-in boot-method and root-build plumbing, preserving current main's SOC-compatible/AVB checks and serial-pinned Fastboot calls. Loader and stock-recovery roles are separate; userdata staging/writing is refused and GPT repair is absent. Native root use requires the companion runtime package.

Device and build

  • Phone: Pixel 4 (flame) for the historical bring-up; this revision is host-validated. No phone is contacted by these tests.
  • Kernel: historical handset 7.0.0-sm8150; no new hardware boot claimed.
  • Packages: None; tooling and native payload sources.

Checks

  • tools/pr-check origin/main
  • tests/all
  • Area prefixes, version bumps where applicable, AI Co-Authored-By and no AI Signed-off-by

Host policy/tests/all and serial/role/hash/erase/guard fixtures passed. The exact refreshed payload has not been booted; old installed-image hardware results are evidence only, not validation of new bytes.

The full unrelated package run in the older Debian/root harness has four failures also reproduced on unmodified main (mirror, mmd, sensors and speaker-tuning). Touched package suites pass with current jq behavior. Optional QML/Lua/root-image/provisioning fixture checks report skips. This is not a claim that every package test passed in that harness; CI uses Arch and a normal user.

On the phone

No hardware changes in this review refresh. A read-only attempt to collect a current tools/phone-smoke report could not reach the connected USB endpoint, so no fresh report is attached. Historical results stay explicitly separate from the exact new source/build. Native boot and runtime deployment remain owner-approved gates; the signed complete root and Android rollback cycle have not been repeated.

The original #17 retains the historical discussion and an immutable source snapshot; companion links and merge ordering are listed there. No firmware, calibration, identifiers, credentials or binary images are published. The earlier intermittent runtime reset remains unexplained.

Companions: runtime #55, boot #56, ssh #57, metadata #58, docs #59. Runtime #55 must be available before native boot/root use; the metadata proposal #58 stays held for policy.

Preserve current main's descriptor and serial-pinning protections while
adding the explicit flame loader path. Reject userdata staging/writes
and keep GPT repair out pending policy. Offline fixtures cover role,
slot, hash, erase, selection and first-guard failures.

Co-Authored-By: Codex <noreply@openai.com>
@derekross

Copy link
Copy Markdown
Owner

Thanks, this reads well, and I'm happy with it. I checked that nothing changes for the Tensor phones: the android-v4 path asks for the same keys and still sets slot B active, the ext4 options only change for DEVICE=flame FLAME_NATIVE=1, and install-phone still refuses flame. Your flash path writes only boot_b, pinned to one phone, never changes the active slot, and refuses a userdata role. The tests pass on their own and with the other four merged in. I also confirmed the pinned U-Boot commit and its defconfig are public.

One thing to say plainly: since flashing boot_b clears slot-successful:b (your BOOT-PLAN item 2), a loader install with this plumbing will always end at "slot B success is clear; staying in fastboot" until the GPT question in #58 is settled. That's the right behaviour, and your docs say it. I'll merge this right after #55, so main never has the plumbing without its runtime.

A few small suggestions, none blocking:

  • native/init stops its guard loop with kill -9 -1 and then hands over without checking again. One storage_guard || exit 1 right before exec switch_root would close that window, as the Pixel init does with its last check.
  • The label check uses blkid -s LABEL -o value. Busybox's blkid prints the whole line for that, which caught us out on the Pixels. e2label from e2fsprogs (already in the image) doesn't depend on which blkid comes first on PATH.
  • If userdata's LUN isn't sda on some boot (the letters moved once), the init stops with "No userdata partition". That fails safe, but it's worth a sentence in the README's recovery section.

bc-abe pushed a commit to bc-abe/omarchy-mobile that referenced this pull request Oct 27, 2026
* bin/omamobile: count fastboot devices without grep -q under pipefail

grep -q exits at the first line, so with two phones listed fastboot's
second write gets SIGPIPE and the pipeline fails under pipefail: flash
said "phone not in fastboot" instead of "2 phones in fastboot", and
tests/images-layout failed about one run in three on main. It failed
closed, never flashing, but with the wrong reason. grep -c >/dev/null
reads to the end (AGENTS.md's gotcha); capture had the same pattern.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* omamobile-modem 0.1.5: the profile reads five NV partitions, not four

The comment at the top of the chroot profile said four; the loop copies
modem_a, efs, efs_backup, modem_userdata and persist. Pointed out on derekross#22.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* DEVICES: the Pixel 9a's row from its merged notes

tegu's notes (merged with derekross#44) carry a phone-smoke report from the 9a:
the DSI panel, Panthor rendering the desktop, gpio-keys, Wi-Fi joining,
Bluetooth powered, the gauge, audio through the AoC and three sensors.
The row still said simpledrm and fixed clocks with those cells at no. They
are WIP and marked unpublished kernel, since the 9a's board DTS isn't
public yet; Wi-Fi points at kernel derekross#56.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@W4HO-ham W4HO-ham mentioned this pull request Oct 28, 2026
10 of 14 tasks
derekross added a commit that referenced this pull request Oct 30, 2026
The matrix and the Wanted list against what has merged since #140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were
  closed because they landed unchanged through kernel #134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the
  2026-10-28 notes. Touch stays WIP: kernel #134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel #133)
  and the kernel option with the touch notes (#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names
  its open kernel PR, #116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133)
  records it scanning through its own UART; kernel #98 and #98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes
  the merged tier 1 auto-sleep (#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open #171, #172, #174-#176.
- Wanted: coral's #52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (#55, #56, #58,
  #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and
  kernel #115, both open.

The Pixel 9a row and the Pixel 9 family line are left to #165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
derekross pushed a commit that referenced this pull request Nov 2, 2026
…ing (#307)

The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to.

- **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel #178 on #156, both in review) and brcmfmac (kernel #56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after #178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did.
- **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (#268, #275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, #284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word.
- **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel #125's boot, which also checks the panel ID).
- **Charging, Haptics, Torch, NFC:** kernel #161, #96, #104 and #105 are merged.
- **USB net:** the rescue also handles a replug the gadget didn't see (#280).

The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel #99), the panel ID (kernel #125), the RTC without the PMIC interrupt (kernel #55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers.

Closes #307

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

A friendly check-in: this has had no activity for about 11 days and now conflicts with main. If you're still working on the flame port, a rebase onto main will get it moving again, and I'm happy to review. If I don't hear back within a week I'll close it to keep the queue tidy; it can be reopened any time.

robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The matrix and the Wanted list against what has merged since derekross#140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were
  closed because they landed unchanged through kernel derekross#134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the
  2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133)
  and the kernel option with the touch notes (derekross#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names
  its open kernel PR, derekross#116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133)
  records it scanning through its own UART; kernel derekross#98 and derekross#98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes
  the merged tier 1 auto-sleep (derekross#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176.
- Wanted: coral's derekross#52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58,
  derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and
  kernel derekross#115, both open.

The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ing (derekross#307)

The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to.

- **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (derekross#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel derekross#178 on derekross#156, both in review) and brcmfmac (kernel derekross#56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after derekross#178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did.
- **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (derekross#268, derekross#275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, derekross#284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word.
- **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel derekross#125's boot, which also checks the panel ID).
- **Charging, Haptics, Torch, NFC:** kernel derekross#161, derekross#96, derekross#104 and derekross#105 are merged.
- **USB net:** the rescue also handles a replug the gadget didn't see (derekross#280).

The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel derekross#99), the panel ID (kernel derekross#125), the RTC without the PMIC interrupt (kernel derekross#55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers.

Closes derekross#307

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants