Skip to content

flame: document native recovery and direct ABL gates - #59

Open
wirelessjoe wants to merge 2 commits into
derekross:mainfrom
wirelessjoe:docs/flame-native-results
Open

wirelessjoe wants to merge 2 commits into
derekross:mainfrom
wirelessjoe:docs/flame-native-results

Conversation

@wirelessjoe

@wirelessjoe wirelessjoe commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

What and why

Part (e) 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.

Separate the native runbook/results, buttons-only recovery warning and bounded validation script. Document the shared builder-supplied :2222 key and read-write /realroot bind. Agent evidence is one table row plus the unresolved-reset limit. Assess #52's direct-ABL recipe as an unverified flame candidate: the retained Image header has text_offset=0, while the report requires 0x80000. The basic recovery procedure does not require landing the held GPT proposal.

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.

Checks

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

Policy/tests/all and script parsing passed. The Image header was inspected read-only on the host. No new boot, flash, PMIC/PON operation, package deployment, or coral hardware claim is included.

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.

Explain the shared rescue key and read-write /realroot bind, state
buttons-only recovery for this handset, and shorten agent evidence.
Separate measured flame results from the coral direct-ABL report and
record the retained Image's text-offset mismatch. No new hardware result
is claimed.

Co-Authored-By: Codex <noreply@openai.com>
derekross added a commit that referenced this pull request Oct 26, 2026
…lags as a named exception

Two decisions the Qualcomm ports (#17/#55-#59 flame, #52 coral, #25
alioth) were waiting on:

- AGENTS.md said never to run an unsuffixed fastboot flash, but our own
  tools/install-phone already flashes userdata that way behind its guards.
  The rule now says so: userdata has no slots, and it is flashed only
  through install-phone.
- On the Pixel 4 family the A/B slot flags live in GPT attributes, so
  marking slot B bootable is a partition-table write the storage guard
  can't block. It is allowed only as a narrow exception named per device
  in CONTRIBUTING §3.1 (LUN, sectors, bit, CRCs), done by hand once per
  boot-image install, with the flags recorded before and after, a
  rollback for a corrupted GPT and a way back. Never automatic. No device
  has an entry yet.

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

Copy link
Copy Markdown
Owner

Thanks, the docs are much clearer now: the rescue key and /realroot, buttons-only recovery, the shorter agent note, and keeping the direct-ABL recipe a candidate rather than adopting coral's results are all what I hoped for.

One wording fix before merging: the "Boot-success correction" row in RESULTS.md calls the GPT write an "explicit owner-approved one-time GPT exception". On main that reads as if the project had granted an exception, and it hasn't yet (#58). Something like "a write past the storage guard, made on 2026-10-19 with the owner's approval, before the project's policy decision (see BOOT-PLAN)" keeps the record accurate.

Smaller things:

derekross added a commit that referenced this pull request Oct 26, 2026
…lags as a named exception (#60)

* AGENTS, CONTRIBUTING: userdata through install-phone; Qualcomm slot flags as a named exception

Two decisions the Qualcomm ports (#17/#55-#59 flame, #52 coral, #25
alioth) were waiting on:

- AGENTS.md said never to run an unsuffixed fastboot flash, but our own
  tools/install-phone already flashes userdata that way behind its guards.
  The rule now says so: userdata has no slots, and it is flashed only
  through install-phone.
- On the Pixel 4 family the A/B slot flags live in GPT attributes, so
  marking slot B bootable is a partition-table write the storage guard
  can't block. It is allowed only as a narrow exception named per device
  in CONTRIBUTING §3.1 (LUN, sectors, bit, CRCs), done by hand once per
  boot-image install, with the flags recorded before and after, a
  rollback for a corrupted GPT and a way back. Never automatic. No device
  has an entry yet.

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

* DEVICES: the PinePhone Pro's codename and starting point

The Wanted row had "-" as its codename, which omamobile.org prints next
to the SoC ("-, Rockchip RK3399S"). It takes mainline's board name,
pinephone-pro, and names that device tree, already in our kernel, as the
starting point (promised on #47).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolve the DEVICES.md conflict with main's PinePhone Pro row by moving
the Pixel 4 note into its matrix row's Boot cell, and word the 10-19 GPT
write as made before the project's slot-flag policy, as asked in review.

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

Copy link
Copy Markdown
Owner

I resolved the DEVICES.md conflict with main (the PinePhone Pro row landed in the same spot) and made the two small text changes from my last comment myself, to save you a round: the Pixel 4 note now sits in the matrix row's Boot cell, and the RESULTS row describes the 10-19 GPT write as made before the project's slot-flag policy. Please pull before your next push. This still merges after #55 and #56, since it describes them.

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

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>
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