Skip to content

Run a virtual iPhone on an Apple Silicon Mac.

Swift

Record the macOS 26.6.2 host results and what macOS 27 is needed for

Lakr233ebbf3b6ded0b
diff --git a/Documents/Guides/compatibility.md b/Documents/Guides/compatibility.md
index c13fac0b..670eaeb8 100644
--- a/Documents/Guides/compatibility.md
+++ b/Documents/Guides/compatibility.md
@@ -51,6 +51,36 @@ day: `iPhone17,3 27.0.1 + 26.4-23E5207q` with the patch boots to the guest
and answers a vphoned `device.info`. Bundle 2.6.0 is the first release that
carries it.
+## macOS 26.6.2 hosts
+
+Checked on 2026-10-23 on Mac mini M4 hosts (Mac16,10, 16 GB, macOS 26.6.2 25G83) with Core Bundle 2.12.1. Every machine was created from nothing, from the CLI: the research-board pairings stage their kernelcache mix as the user and link it with sudo, then `sudo vphone-cli vm create`. A default is the newest pairing `fw catalog` gives that device on this Mac, as Launchpad's New Machine selects. Each machine then booted twice headless: vphoned answered, `device.info` reported the release, and the guest's serial log showed no panic.
+
+| Guest | Firmware | cloudOS | Result |
+| --- | --- | --- | --- |
+| iPhone17,3 | iOS 27.0.1 (default) | `26.4-23E5207q` | template build, clone, two boots |
+| iPhone18,2 | iOS 27.0.1 (default) | `26.4-23E5207q` | template build, clone, two boots |
+| iPad16,1 | iPadOS 27.0.1 (default) | `26.4-23E5207q` | template build, clone, two boots |
+| iPhone17,3 | iOS 26.6.2 | `26.4-23E5207q` | template build, clone, two boots |
+| iPhone17,3 | iOS 26.6.2 | `26.6-23G71` | research board: native KDK extraction, macOS 26 link with no auth stubs left, 28 kernelcache patches, two boots |
+| iPhone17,3 | iOS 26.5 | `26.5-23F75` | research board, as above |
+| iPhone17,3 | iOS 26.4 | `26.4-23E244` | research board, as above |
+| iPhone17,3 | iOS 18.6.2 | `26.1-23B85` | template build, clone, two boots |
+| iPhone11,6 | iOS 18.7.2 (default) | `18.7.2-22H43` | Minimal, mix linked over ssh by the kmutil of a macOS 15.7.7 VM, two boots |
+| iPhone11,6 | iOS 18.6 | `18.6-22G86` | as above: the first boot of this recipe |
+| iPhone11,6 | iOS 18.7 | `18.7-22H20` | as above: the first boot of this recipe |
+| Watch7,18 | watchOS 26.4 (default) | `26.4-23E244` | `watchos` preset, watch kernelcache mix, two boots |
+| AppleTV5,3 | tvOS 26.6 (default) | `26.4-23E5207q` | `tvos` preset, two boots |
+| AppleTV14,1 | tvOS 26.6 (default on macOS 26) | `26.4-23E5207q` | `tvos-4k` preset, 26.6 OTA userland, two boots |
+| AudioAccessory5,1 | HomePod Software 27.0 (default on macOS 26) | `26.4-23E5207q` | `homepod-mini` preset, two boots |
+| AppleTV14,1 | tvOS 27.0 | — | refused before any download: needs macOS 27 |
+| AudioAccessory5,1 | HomePod Software 27.2 | — | refused before any download: needs macOS 27 |
+
+The tvOS 27.0 (24J361) and HomePod Software 27.2 (24K120) OTAs compress their payload with LZRAVEN, which only macOS 27 unpacks. On an older Mac `fw catalog` leaves them out, so Launchpad's default for those devices is tvOS 26.6 and HomePod Software 27.0, and naming one is refused before anything is downloaded.
+
+cloudOS 26.7 (23H20) has no iPhone release to pair with. Staged with iOS 26.6.2's userland, its mix links and its 28 kernelcache patches apply; the CFW patch `_vm_fault_enter_prepare` finds no site in that kernel. It has not booted.
+
+`vphone-escalator`'s allowlist is kept in amfid's memory, so it is lost when amfid restarts, as it did once on these hosts mid-run. Launchpad allows the bundle again when AMFI refuses it; from the CLI, run the `vphone-escalator allow` command `host preflight` prints again.
+
## Other iPhone models
See [Other iPhone models](iphone-models.md).
diff --git a/Research/0_binary_patch_comparison.md b/Research/0_binary_patch_comparison.md
index c26e9ab6..b4ed4a6d 100644
--- a/Research/0_binary_patch_comparison.md
+++ b/Research/0_binary_patch_comparison.md
@@ -3728,6 +3728,21 @@ it was not ("Invalid root hash", `apfs_sealvolume` exit 65 in
for `apfs_sealvolume`, which needs the device; the mount changed the volume
after the mtree described it. It attaches the image with `-noMount` now.
+On macOS 26.6.2 two more steps failed (2026-10-23, Mac mini M4):
+
+- `diskutil image attach -mountPoint` refuses a folder that does not exist
+ ("Mount point … doesn't exist", exit 64), and the merge attached at a fresh
+ `<tmp>/volume` it had not created. Every preset that merges the restore
+ image (watchos, minimal) stopped there. The folder is created first now.
+- The watchOS 26.4 system image has no partition map: its APFS container
+ spans the whole file, and `diskutil image resize` grows it no further than
+ that ("Requested size exceeds maximum size"; min 11.05 GB, max = current =
+ 11.26 GB once merged). Left at that size, `apfs_sealvolume` ran out of space
+ remapping the fsroot tree with 541 MB free (ENOSPC, exit 65). `growImage`
+ now extends the file and runs `diskutil apfs resizeContainer <container> 0`,
+ which gave the same image 2.7 GB free. The iOS images, which diskutil can
+ grow, are resized as before.
+
The binaries the merge patches (`launchd_cache_loader`, `mobileactivationd`)
are re-signed in Apple's ad-hoc shape (`VPhoneSignOptions.Style.appleAdHoc`),
like the stock binaries around them. The guest's TXM is stock here: it takes
diff --git a/Research/Firmware/homepod_mini_support.md b/Research/Firmware/homepod_mini_support.md
index c2bf0d75..01751e9b 100644
--- a/Research/Firmware/homepod_mini_support.md
+++ b/Research/Firmware/homepod_mini_support.md
@@ -138,6 +138,16 @@ preserved. See [Sound Glow](homepod_sound_glow.md) for evidence and build detail
The host label now records the actual installed userland after disk commit,
preserving cloudOS; preparation alone continues to report the restore base.
+The 27.2 OTA needs a Mac on macOS 27. Its `payloadv2` chunks are `pbzm`:
+LZRAVEN (`COMPRESSION_LZRAVEN`, 0xD05), which libcompression gained in macOS
+27. On macOS 26.6.2 neither AppleArchive nor `aa` reads them, and the creation
+stopped at "payload.000 could not be read: ioError. Download the OTA again."
+although the archive matched AppleDB's SHA-256 (2026-10-23). The catalog
+records the requirement (`VPhoneOTARelease.minimumHostMacOS`): on an older Mac
+`fw catalog` and the default pairing stop at HomePod Software 27.0, an explicit
+27.2 source is refused before anything is downloaded, and staging refuses a
+`pbzm` chunk by name.
+
## Validation
Validated on 2026-10-22 with four CPUs, 4 GiB memory and a 32 GB disk:
diff --git a/Research/Firmware/tvos_support.md b/Research/Firmware/tvos_support.md
index a5a23b2a..bee7222c 100644
--- a/Research/Firmware/tvos_support.md
+++ b/Research/Firmware/tvos_support.md
@@ -436,6 +436,16 @@ layout is the 26.6 one: monolithic, no cryptex, `payloadv2` chunks, the root
filesystem's `.mtree`, `.root_hash` and `.trustcache`, and the J255 device tree.
(Checked on the AppleTV11,1 27.0 OTA, a plain zip, from its central directory.)
+The 27.0 OTA needs a Mac on macOS 27. Its `payloadv2` chunks are `pbzm`, not
+`pbzx`: LZRAVEN (`COMPRESSION_LZRAVEN`, 0xD05), which libcompression gained in
+macOS 27, and a chunk's first block decodes to `YAA1` only there. On macOS
+26.6.2 neither AppleArchive nor `aa` reads it, and the creation failed after
+the restore, when `cfw install` unpacked the userland (2026-10-23). The catalog
+records the requirement (`VPhoneOTARelease.minimumHostMacOS`): on an older Mac
+`fw catalog` and the default pairing stop at tvOS 26.6, an explicit 27.0 source
+is refused before anything is downloaded, and staging refuses a `pbzm` chunk by
+name.
+
So a 27 guest is the 26.6 one with a later OTA: the HD's last IPSW, 26.6, is
the restore base and only the userland changes. `VPhoneOTARelease.baseVersion`
records the base an OTA goes over. The 4K's tvOS 27.0 pairing names the OTA