Quick Answer: Erosion-CN is a Simplified Chinese fork of the open-source Erosion project, an iOS and iPadOS utility for inspecting and editing the MobileGestalt cache. According to its README, it adds backup, diff preview, and read-back verification. It is sideloaded, not App Store software, and its README says writes are supported only on iOS 27.x.
If you've searched for a way to tweak deep device settings without jailbreaking, you've probably run into the same question: how do you change something Apple keeps in a system cache without breaking the phone? The Erosion-CN project, published on its GitHub repository, is one attempt to answer it. Its README describes a sideloaded toolkit built on the worse_query sandbox research, with a Chinese interface and a set of safety features the upstream version lacked. I'll walk through what it claims, what those claims mean in practice, and where the real risks sit.
What MobileGestalt is and why people edit it
MobileGestalt is the system library apps call to ask questions like "what model is this?" or "does this device support a given feature?" Its answers are stored in a cached property list on disk. Changing that cache is the mechanism behind most of the "unlock a hidden feature" tweaks you've seen online.
The part most guides skip is that the cache is validated at boot. Editing the file is not enough. If the file's structure, ownership, or checksums don't match what the system expects, iOS can discard it and rebuild it from factory values. The README makes this point directly. It says earlier versions of the upstream tool could appear to work, then revert after a restart. Whether that failure mode is fully fixed in Erosion-CN is something only long-term testing on many devices can establish.
What the fork changes compared with upstream
According to the README, the fork makes several changes to the upstream Erosion project, which is maintained at jailbreakdotparty/Erosion:
- Full Simplified Chinese localization of the interface.
- Forced in-place overwrites instead of temporary-file replacement, so the cache keeps its original inode and ownership.
- Type-aware plist editing that preserves booleans and floating-point values, which the README says caused camera failures in the upstream version.
- Diff preview before applying, showing old and new values side by side.
- Automatic snapshot and read-back verification, with rollback if the written file doesn't match.
- Backup integrity checks using SHA-256 and a marker that keeps the backup out of iCloud sync.
These are sensible engineering choices. Diff previews and rollback matter most, because the failure you're guarding against is a half-written system file, not a bad setting. The README's own claim is that a truncate-then-write pattern could leave an empty file after a power loss. The fork switches to a write-in-place strategy with a full flush (F_FULLFSYNC on Apple's APFS). That reduces the window for corruption, but it doesn't eliminate it, and you should still treat every write as something you may need to undo.
Which devices and versions the README actually supports
The README lists full support for iOS and iPadOS 27.0 through 27.2.1, plus 27.3 beta 1. iOS 26.x is listed as partial, with the important caveat that writing to MobileGestalt isn't supported there. Its feature list reads more like a configuration and browsing tool on iOS 26 than a system modifier.
| Area | iOS 27.0–27.2.1 / 27.3 beta 1 | iOS 26.0–26.7.2 |
|---|---|---|
| Read MobileGestalt values | Supported | Supported |
| Write to MobileGestalt cache | Supported (per README) | Not supported |
| Lock Screen wallpaper and dial customization | Supported | Supported |
| Container browsing | Supported | Partial |
| Backup and restore of app data | Supported | Partial |
Two things stand out. First, a reader on iOS 26 gets a much smaller tool than the headline suggests. Second, the README's feature list is self-reported. Nothing on the page links to independent test results.
The signing requirement is the real gatekeeper
Erosion-CN doesn't install like a normal app. The README says it needs at least one valid App Group entitlement, which means you have to sign it yourself with a tool such as SideStore, AltStore, Feather, Sideloadly, Impactor, or iLoader. Free Apple ID signing typically expires after seven days, so you'll re-sign regularly, and some signing methods strip or fail to keep the entitlement.
Here's the catch most readers miss. A tool that depends on a particular entitlement is only as stable as the signing path you choose. The README says the app detects the App Group at runtime and logs whether it's present. Check that log before you change anything. If the App Group isn't detected, the tool shouldn't be writing anything, and you shouldn't force it.
Risk, limits, and the things a responsible expert would flag
This is where I'd slow you down. The README itself warns that modifying system configuration carries risk, and that's accurate. Three caveats deserve more weight than the feature list.
- Software can't add hardware. Many "unlock" tweaks only flip a flag. If the underlying chip, radio, or sensor isn't present, the feature won't work, and it may fail in unexpected ways. The README mentions Apple Intelligence hardware checks, which is a reminder that the phone's silicon, not the cache, sets the real limit.
- Regional and carrier settings have side effects. The README says a wrong write could affect baseband or eSIM behavior. Those failures can be hard to diagnose and hard to undo without a computer restore.
- Claims are not independently verified. Everything about "no revert after reboot" and "safe rollback" comes from the project's own documentation. Treat it as a hypothesis until other testers confirm it on your exact model and build.
The counter-intuitive point here is that the safety features are most valuable when you don't use them. The diff preview and snapshot exist so you can see exactly what changed and return to the original state. If you skip the backup, the tool is far more dangerous than its polished interface suggests.
Before you touch anything
If you still want to experiment, sequence matters more than the tool itself.
- Make a full computer backup of the device using Finder or iTunes, and confirm it restores. Don't rely on iCloud alone.
- Export the original MobileGestalt snapshot the tool offers, and store it off-device.
- Read the diff preview line by line. If you can't explain what a key controls, don't change it.
- Restart and verify that the change persists after a reboot, and check that the camera, cellular, and Face ID still work.
- Know the restore path. The project's RESTORE documentation exists for a reason. Read it before you apply anything.
Here's where many people go wrong: they test one change, see it stick, and then stack five more. Change one thing at a time, and wait a day between changes so you can spot delayed failures.
Frequently Asked Questions
What is Erosion-CN?
Erosion-CN is a Simplified Chinese fork of the open-source Erosion iOS utility, published on GitHub under GPLv3. According to its README, it reads and edits the MobileGestalt cache on iOS and iPadOS devices, adds backup and rollback features, and requires a sideloaded install with an App Group entitlement. It is not an App Store app and is not endorsed by Apple.
How do I use Erosion-CN safely on my iPhone?
Start with a full computer backup and confirm it restores. Install the app with a supported signing tool, check that the App Group is detected, and read the diff preview before applying any change. Apply one change at a time, reboot, and confirm the device still works normally before making another.
Why does a MobileGestalt change sometimes revert after a restart?
iOS validates the cached MobileGestalt file at boot. If the file's structure, ownership, or checksums don't match what the system expects, it can be discarded and rebuilt from factory values. The README says earlier upstream versions had this problem and that the fork addresses it, but independent confirmation on your own device is the only real test.
Final takeaway
Erosion-CN is a serious, well-documented attempt to make MobileGestalt editing safer, and its diff preview and rollback design are worth studying even if you never install it. Its feature claims are the project's own, its iOS 27 write support is the headline, and its risks are real. Before you try it, make a full computer backup, verify the App Group is detected, and change one setting at a time. Try the backup-and-restore check on a spare device this week, and note how long the restore takes. If you're helping someone wrestling with an iOS Erosion-CN setup, send them this checklist first.