Repository navigation
Name a backup's donut while its empty boot0 cycles its bootrom - #166
Merged
Merged
Conversation
bboe
force-pushed
the
restore-cycling-donut
branch
3 times, most recently
from
November 12, 2026 10:12
824b8d3 to
7a2ad79
Compare
restore named a donut from backup.json only if it read as its bootrom when the run started, since only the bootrom's one handshake gives its hardware code. A donut whose boot0 header a stopped restore cleared does not stay there: on 2026-11-12 one read as nothing on USB for 39 s, then as its bootrom, over and over. Three restores that started in the gap named nothing, met the bootrom and stopped: ERROR: firebreak cannot tell which Echo this is, so it cannot say what to do with it. restore now hands the backup's device to twrp_entry, which uses it only in the bootrom step and only when the Echo is still unnamed. An Echo that names itself first keeps its own name, so a run started with nothing plugged in still tells a biscuit or radar from the backup's donut, and a biscuit or radar backup hands over nothing. A first version named the device whenever nothing was on USB at the start; with it the donut was restored from its bootrom, every written area reading back as skip, and booted its backup's 8349. Review found that it would also name any Echo plugged in later, so it moved here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The CHANGELOG and docs/unlocking.md quoted adb's "device ... not found" from a 2026-11-05 run with the Echo's real serial in it. It now reads SERIAL; nothing else in the repo names a real Echo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
bboe
force-pushed
the
restore-cycling-donut
branch
from
November 12, 2026 10:17
7a2ad79 to
ac81cee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A donut whose boot0 a stopped restore cleared cycles through its bootrom, absent from USB for about 39 seconds at a time. A restore started in that gap never took the device from the backup, then stopped at the bootrom. It now does; the hardware-code and CID checks still guard every write.
🤖 Generated with Claude Code