Files
LakrandClaude Opus 5.5 ae5e4531a5 Name every patch {component}-{effect}-{name}
The 117 bundled patch identifiers had grown five naming schemes
(kernel.x, jb.x, kernelcache_jb.x, txm_dev.x, bare names). Each one is now
{component}-{effect}-{name}:

- component: avpbooter, ibss, ibec, llb, txm, kernel, devicetree, dyld,
  preboot, or system-<binary> for a guest binary or file.
- effect: boot when the patch is boot-essential, exp when the standard
  preset leaves it off, cfw otherwise. A catalog test enforces this.
- name: snake_case, no hyphen, so the identifier splits from the right.

Record sites are now always <identifier>.<site>. The underscore-prefix
rule in covers(recordIdentifier:) and in the gate is gone: the new names
contain underscores, so kernel-boot-post_validation would otherwise have
covered kernel-boot-post_validation_unsigned. The 25 records that relied
on it (amfi_trustcache_1, launch_constraints_mov, sandbox_ext_N, ...) now
use a dot.

Old identifiers are not migrated. A VM whose PatchPlan or PatchSelection
names one must be patched again. The bundle becomes 2.2.0 and Launchpad
requires 2.2.0, so it never meets an old identifier from a bundle.

Launchpad's patch table shows Component, Effect and Name columns in place
of Identifier and Patch Set; the set moves to the detail line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 15:20:20 +09:00

2.0 KiB

Troubleshooting

Documentation · Host setup · Create a VM

vphone-vm is killed before the VM opens

Run vphone-cli host preflight. The CLI is unentitled and can explain an AMFI refusal of its signed vphone-vm companion. If you rebuilt, the cdhash changed: allow the new binaries with the bundled helper as described in host setup.

Virtualization is not available on this hardware

PV=3 guests cannot be nested. Boot on an Apple Silicon Mac rather than inside another macOS VM.

vm create printed vphoned success, but no VM is running

That is expected. Creation starts a temporary GUI boot, sends a real ping, and stops that boot before returning. Start the VM for use with vphone-cli vm launch <name>.

Stuck at “Press home to continue”

Use the VM window's Keys → Home action. The current JB workflow does not install a VNC server.

App exits with EXC_GUARD / GUARD_TYPE_MACH_PORT

The kernel patch kernel-boot-thread_guard_violation stops fatal Mach port guard delivery. It applies only on an iOS 18 base, where it is needed to boot, and every preset turns it on there. Other bases cannot select it, so an app that trips this guard on a 26.x base still exits. See issue #291.

Restore or first boot fails

Keep the VM in DFU until restore exits in a manual flow, and check that online ticket requests can reach Apple. For the complete pipeline, rerun vm create with a new name and -v for tool detail; avoid parallel VM creation when memory or disk is tight. Inspect firmware compatibility before combining an iPhone IPSW with a PCC image.

If the guest boots but vphoned does not answer, the first-boot check times out after 300 seconds. A GUI boot is used because a newly restored guest may not bring up vphoned during its first headless boot. See create and run for what the success marker proves.