Repository navigation
omamobile: keep ram-only fastboot recovery guarded - #918
Open
quatrixone wants to merge 1 commit into
Open
quatrixone wants to merge 1 commit into
quatrixone wants to merge 1 commit into
Conversation
Permit only the reboot-to fastboot recovery path for a ram-only device. Refuse persistent image and install commands, and stop without sysrq when reboot-to is ignored. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
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.
Split the shared BOOT_METHOD=ram-only handling out of #714.
A ram-only descriptor may use
omamobile fastbootthrough the installedreboot-to bootloaderpath. Image construction, flash, push and initramfscommands remain refused. If reboot-to is ignored, the command stops instead
of using the unverified sysrq fallback.
Checks:
tests/boot-method,tests/all,tools/pr-check origin/main.No on-device run was done in this PR.