mond: editing MobileGestalt on iOS 27.0 beta 1 to 4

What mond edits, and the exact iOS builds it accepts

MobileGestalt is the property store iOS uses to describe a device: its model, region behaviour and a long list of capability flags. mond is a tool for changing entries in that store on a device that is not jailbroken in the classic sense, which is why its version table is so narrow. The README states support for iOS 27.0 dev beta 1 through 4 and iOS 27.0 public beta 1 through 2. Everything else is listed as unsupported, including iOS 26.x and earlier, dev beta 5 and later, and public beta 3 and later. That is not a soft recommendation. A Gestalt key written against the wrong build can leave the device in a state it will not boot out of, and the repository carries a warning block saying some tweaks have the potential to brick your device. The audience is therefore small and specific: people already running one of those beta builds who want to change a device property, usually to test region behaviour or to make an app believe it is running on different hardware. If you are on a shipping iOS release, mond is not for you, and the support table says so in its first row.

Three tools in one app: Gestalt editor, Pocket Poster, HouseArrest browser

The implemented list in the README names three components. The MobileGestalt Editor is the core: it reads and writes Gestalt keys. Pocket Poster is the second, and the README does not describe what it does beyond naming it, so treat the name as the only confirmed fact. The HouseArrest File Browser is the third, and it is the most technically interesting, because it does not depend on a jailbreak. HouseArrest is an iOS service that lets an app reach into the container of another app when it holds the right entitlements, and a browser built on it gives you file access scoped to whatever the entitlement grants. The README credits the underlying work: forcequit for bad_query, johnny for the MCM bug class, and jailbreak.party for PartyUI, GestaltView and the implementation of neon's respring method. Those credits tell you the app is assembled from a small set of known exploit primitives rather than a single kernel patch, which is also why the supported build range is a handful of betas wide. A planned Gestalt Keys browser is listed but not implemented, so today you work against keys you already know rather than browsing a catalogue.

Installing mond and making a first Gestalt change

The README does not give command line install steps. What the repository shows is an Xcode project, mond.xcodeproj, alongside a mond/ source directory, and the README links a Discord server for support and a GitHub issues page. Releases are tagged, with 2.2 and 2.0 published in August 2026 and a development tag alongside them. The practical route is to open the project in Xcode and build it to a device running a supported beta, or to obtain a signed build from the project's release page. Because no CLI is documented, there is no honest command sequence to print here for installation. Once the app is on the device, the workflow is: select a Gestalt key, read its current value, write the new value, and respring using the method the credits attribute to neon. Respringing is what makes the change take effect, and it is also where the known issue about tweaks disappearing on reboot bites. The README does not document a rollback path or an automatic backup of the original key value, so record the previous value yourself before writing anything. The warning block at the top of the README is the only risk guidance the project offers, and it is one sentence long.

The known issues are the real specification

Four known issues are listed, and each one narrows the tool's usefulness. Tweaks may disappear on reboot, which means a change you verify today may not survive a restart, and the README does not say which keys are affected. Apple Intelligence spoofing does not work on iPhone 15, a device-specific failure the project has stopped taking questions about on GitHub, directing users to Discord instead. Disable Region restrictions may be broken on some versions and devices, phrased with enough hedging that it is not a reliable feature on any given build. The iPad entry is the sharpest: iPadOS UI and related tweaks may not work and may bootloop the device. A bootloop is not a cosmetic bug, and the README states it plainly rather than burying it. Read together, these issues describe a tool that works on a narrow slice of hardware and software and fails in ways that range from annoying to unrecoverable. The absence of a documented recovery procedure is the largest gap in the documentation.

How mond differs from a jailbreak and from desktop MobileGestalt tools

The obvious alternative is a full jailbreak with a tweak like a MobileGestalt editor injected through a jailbreak package manager. The difference is scope and mechanism. A jailbreak patches the system broadly and gives you a persistent environment with package management, but it is not available for iOS 27.0 betas, which is exactly the window mond targets. mond instead uses a set of specific bug classes, named in the credits as bad_query and the MCM bug class, plus HouseArrest for file access, and it lives as a normal app on a non-jailbroken device. That trade means no persistence guarantees, which is consistent with the reboot issue, and no package ecosystem. Desktop tools that edit a Gestalt plist inside an IPSW or a backup operate on files at rest and never touch a running device, so they cannot change live behaviour and cannot bootloop anything. mond is the opposite: it changes a running device, which is the source of both its usefulness and its risk. If your goal is to inspect a Gestalt file offline, a desktop approach is safer and mond is the wrong tool. If your goal is to change how a running beta build reports itself, mond is one of very few options, and the narrow version table is the price.

Licence, maintenance and what an upgrade costs you

mond is licensed AGPL-3.0. That is a strong copyleft licence with a network clause. If you fork it and offer a modified version as a service, the AGPL's source disclosure terms apply, and any distributed derivative must carry the same licence. For someone building the Xcode project for personal use on their own device, the practical effect is that you can read and modify the source freely, but you cannot fold it into a closed product. This is not legal advice; read the LICENSE file in the repository root. On maintenance, the last push to main was on 2026-08-19, and the most recent tagged releases are 2.2 from 2026-08-17 and 2.0 from 2026-08-16, with a development tag at the same timestamp as the last push. The repository is not archived. The upgrade cost is unusual: because support is tied to specific beta builds, moving to a newer iOS beta can take you outside the supported range entirely, and the table already marks dev beta 5 and later and public beta 3 and later as unsupported. An iOS update is therefore a potential loss of the tool, not just a version bump.

Editorial conclusion

Adopt mond only if you are running an iOS 27.0 dev beta 1 to 4 or public beta 1 to 2 build and you accept that the README says some tweaks can brick the device. Anyone on iOS 26.x or earlier, on dev beta 5 or later, or on public beta 3 or later should not install it, because the support table marks those versions unsupported. Before touching anything, confirm your exact build against that table and back up, since the known issues list tweaks disappearing after a reboot. Verify first whether your device is an iPhone 15, where Apple Intelligence spoofing is documented as not working, or an iPad, where the README says UI tweaks may not work and may bootloop the device.

Frequently asked questions

Official sources

1. Issues
2. License: AGPL-3.0
3. README
4. Releases
5. rooootdev/mond on GitHub