mirror of
https://github.com/Lakr233/vphone-cli.git
synced 2026-10-01 23:54:35 +08:00
LakrandClaude Opus 5
b323fc4ec7
Every Jailbreak* type, file and directory in the firmware patcher is now CustomFirmware*: Kernel/JailbreakPatches -> Kernel/CustomFirmwarePatches, KernelJailbreakPatch* -> KernelCustomFirmwarePatch*, IBootJailbreakPatcher, KernelJailbreakPatcher(Base), FirmwareKernelJailbreakPatchSet. The kernel patch set is com.vphone.patchset.kernel.cfw and provides vphone.kernel.cfw; the patcher's gate component is kernelcache_cfw; the `fw patch-component` verb is kernel-cfw; log lines print [CFW]. The `extended` preset is now `experimental`, which is what it has always been: every patch the bundle declares, including ones a freshly restored guest may not survive. Launchpad's machine inspector stops showing the raw restore variant and names the firmware instead — Standard Custom Firmware, Experimental Custom Firmware, or Unknown Firmware for anything else. Left alone deliberately: /var/jb and .jbroot-<hex> are rootless and roothide's naming, not ours; vphoned's `jailbreak` API object and the device-info panel that renders it describe that same environment; and FirmwarePipeline.Variant.jb keeps its spelling because its raw value is recorded in every existing VM's RestoreInfo, which is why the inspector maps it rather than rewriting it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
3.1 KiB
3.1 KiB
Research library
Project overview · User documentation
This directory keeps the evidence behind firmware patches, restore and the self-contained host runtime. The current public workflow is JB only. Many notes record earlier experiments and command names; use the user guides and vphone-cli --help for current instructions.
Start here
- Patch comparison is the canonical per-component inventory. Its regular/dev/exp columns are historical.
- Firmware manifest and origins explains the hybrid firmware inputs.
- CFW kernel patch notes and the individual patch index lead to the kernel evidence.
- Native restore design and self-contained runtime explain the host migration.
By subject
| Subject | Notes |
|---|---|
| Firmware and boot chain | Manifest and origins, iBoot patches, TXM full chain, TXM JB patches, selector 24, variant differences |
| Kernel | CFW overview, patcher verification, FairPlay kexts, base validation 1–5, 11–15, 16–20, sandbox hooks, individual patch notes |
| Other patches and captures | Launchd jetsam, user-mode hypervisor references, reference capture |
| Restore | DFU probe, in-process restore |
| Host and archives | Binary split, runtime dependency tiers, archive extraction contracts, libarchive validation |
| Guest interaction and VM identity | DevMode XPC, keyboard events, machine identifier, RootHide bootstrap base |
| Historical project records | Migration ledger, manifest refactoring summary |
KernelSymbols/ holds symbol datasets and indexes; Reference/ holds source references when present. They are evidence inputs, not steps for running the distributed app. The files in History/ are preserved snapshots and may describe scripts or variants that have since been removed.