Repository navigation
install-phone: preserve development boot-update policy and serial pin - #563
Conversation
|
Thanks, Chris. Small and well tested, and descriptors without the key keep today's behaviour exactly. Before it leaves draft, could you update the header comment near the top (it still says AUTO_WRITE=yes), mention |
d8a473b to
0141cb8
Compare
|
Thanks, Chris. All three documentation points from last time are in, and the One thing changed under you today: #641 landed and gave I tried exactly that on a scratch merge: main's |
…encies (#561) Records the Pixel 6a's persistent desktop on its development kernel, what can and can't be reproduced from published sources, the one slot-success write with its before and after bytes, and the hold on further marking. Lists the split pull requests (#562, #563, #565) and the kernel pull requests the port still waits on. Documentation only. Co-Authored-By: OpenAI Codex <noreply@openai.com>
Keep the existing --serial pin unchanged. Accept only yes or no for the descriptor boot-update policy before preparing an image or contacting a phone; omitted policy retains the existing release image. Verify the prepared development image and fail-before-query behavior. Co-Authored-By: Codex <noreply@openai.com>
0141cb8 to
7fca38e
Compare
|
Thanks, Chris. This is exactly what I asked for: I ran Merging. I'll drop "and serial pin" from the title when I squash. |
…encies (derekross#561) Records the Pixel 6a's persistent desktop on its development kernel, what can and can't be reproduced from published sources, the one slot-success write with its before and after bytes, and the hold on further marking. Lists the split pull requests (derekross#562, derekross#563, derekross#565) and the kernel pull requests the port still waits on. Documentation only. Co-Authored-By: OpenAI Codex <noreply@openai.com>
…ed root's AUTO_WRITE (derekross#563) A descriptor may set `BOOT_UPDATE_AUTO_WRITE=no` so that an installed development root keeps its test kernel: the installer writes that value as `AUTO_WRITE` in `/etc/omamobile/boot-update.conf`. Without the key the file says `AUTO_WRITE=yes` as before, and any other value is refused before image preparation or any fastboot query. What the installer itself writes doesn't change. Co-Authored-By: Codex <noreply@openai.com>
Preserve a development installation's test kernel by accepting descriptor BOOT_UPDATE_AUTO_WRITE=yes|no and writing that AUTO_WRITE value into the prepared root. Omitted settings retain yes. Invalid values refuse before phone queries or image preparation.
The delta now contains only this policy, its documentation and fixtures. Main's --serial implementation is retained; the redundant FASTBOOT_SERIAL mechanism is removed.
Validation on main 6ee77fb: full tests/all, policy and the complete fake-fastboot installer suite pass, including default/development image contents, invalid-policy refusal and main's serial checks. All installer execution used fixtures; no physical installation, flash or partition write occurred. Independent review found no remaining source blocker. Fresh published-head CI is tracked below.
Published-head validation: both Policy and Tests (tests/all, every package) passed on
7fca38e634b6810721b73d15ded01164656d7d62. The complete combined local integration also passes tests/all and tests/packages with PYTHONUNBUFFERED unset, matching CI.