This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
# Phase-0.7 offline installation review package
|
||||
|
||||
Status: **DO NOT INSTALL**. This package contains exact offline-reviewed
|
||||
artifacts and evidence only. It contains no deployment command and grants no
|
||||
authority to contact a PS5.
|
||||
|
||||
The package inventory must bind these exact binaries:
|
||||
|
||||
- `chimera-elfldr-phase07.elf`: 397000 bytes,
|
||||
SHA-256 `63e810982471eb40cae3a20aa9df9a0a02892f420e429874fae4e99aa400b561`;
|
||||
- `chimera-payload-manager-phase07.elf`: 99560 bytes,
|
||||
SHA-256 `8fecf8241a46246eddbd21e8bb4d875f5d76f1f4f4c6a11384df1f131aa5e5b1`;
|
||||
- `chimera-gfx-lifecycle-probe.elf`: 112680 bytes,
|
||||
SHA-256 `bfb4a5cc768e162fe4c2fddf41c3978e152722918a39085277fd172cb95a7182`.
|
||||
|
||||
Before a later installation, the existing on-device paths, sizes, and SHA-256
|
||||
values must be captured and backed up. Installation permission for the two
|
||||
runtime components does not authorize transferring or executing the lifecycle
|
||||
probe.
|
||||
@@ -0,0 +1,25 @@
|
||||
# Phase-0.7 rollback preparation
|
||||
|
||||
Status: **OFFLINE PREPARED; NOT DEPLOYED**.
|
||||
|
||||
The stock elfldr v0.23 release asset is included when the offline package is
|
||||
generated:
|
||||
|
||||
- size: 397000 bytes;
|
||||
- SHA-256:
|
||||
`092d16ee0ede0c494947efd38d1a17bbd7cc4b022d3858ea898833c188c703e8`.
|
||||
|
||||
The exact stock Payload Manager v0.3.1 binary is not present in the offline
|
||||
workspace. Its previously verified installed/release identity is:
|
||||
|
||||
- size: 2050320 bytes;
|
||||
- SHA-256:
|
||||
`518740adbacccb9094fadb07dd424c53ee290f38306449ccc9d6957fdf813c0b`.
|
||||
|
||||
Therefore any later installation must first make a byte-for-byte backup of the
|
||||
actual installed Payload Manager and verify that exact hash. If it differs,
|
||||
stop. The rollback set is not complete until that on-device backup exists.
|
||||
|
||||
Rollback authorization is separate from installation authorization. This
|
||||
document intentionally contains no connection, copy, service-start, or
|
||||
execution command.
|
||||
Reference in New Issue
Block a user