Patch active TXM for normal JB boot#361
Open
xhzq233 wants to merge 2 commits into
Open
Conversation
Collaborator
|
|
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.
Summary
Patch the release TXM image that the restore manifest marks as loaded by iBoot, and install the patched TXM into the Preboot FUD handoff path during JB/EXP install.
Reproduction
devmode_statusor atask_for_pidsmoke test.BuildManifest.plistTXM entries.Local manifest evidence shows normal boot loads
Firmware/txm.iphoneos.release.im4p, while the old pipeline patchedFirmware/txm.iphoneos.research.im4p.Before
FirmwarePipelineselectedFirmware/txm.iphoneos.research.im4pfor TXM patching.After
FirmwarePipelinepatchesFirmware/txm.iphoneos.release.im4p, matching the active manifest entry.Ramdisk/txm.img4to/private/preboot/<boot-hash>/usr/standalone/firmware/FUD/Ap,TrustedExecutionMonitor.img4..pre-vphoneon first replacement.Ramdisk/txm.img4is signed from the restore-tree release TXM aftermake fw_patch_jbormake fw_patch_exphas already applied the variant TXM patches. The ramdisk step refreshes the base trustcache patch and preserves the existing dev/JB/EXP TXM bytes.Verification
The syntax and compile checks exited 0.
make patcher_buildreported nothing to do.Manifest evidence:
Runtime smoke test from local VM:
Preboot TXM hash verification: