Quick Answer: Erosion-CN is a Simplified Chinese fork of the jailbreakdotparty/Erosion project. It edits the MobileGestalt device-property cache on iOS and iPadOS, and the project claims full write support only on iOS 27.0 through 27.2.1 and 27.3 beta 1. Its own documentation warns that bad edits can cost you features or trigger activation problems, so back up first.
Erosion-CN is a research tool for MobileGestalt, the system library that answers questions about your device, such as its hardware model and which features it reports as available. The project's latest release, v0.8.5, wraps that cache in a Chinese interface with a long list of toggles. Most coverage focuses on what the switches promise. The more useful question is what happens after you flip one, and what it costs you when the change doesn't stick.
What Erosion-CN actually is
The project is a fork of the upstream jailbreakdotparty/Erosion repository, licensed under GPLv3. According to the Erosion-CN README, it adds full Simplified Chinese localization, rewrites the file-write logic, and builds on the open-source worse_query project for container access.
The README makes several claims that deserve a close read. It says the fork fixes a bug where changes reverted after a reboot, and it describes a dynamic lookup of the cache's descriptor table on the device itself rather than hard-coded offsets. It also lists more than 720 binary CacheData slots and says it promoted 14 existing features to dual-write status. None of these numbers have been independently verified in the material I was given, so treat them as the project's own description of its work.
Think of it as a diagnostic and editing front end, not a one-tap upgrade. Its value depends entirely on whether the underlying cache accepts your edit, and that's where most of the complexity sits.
Why a successful write can still revert at reboot
Here's the counter-intuitive part: a write that returns "success" tells you almost nothing about whether the change will survive a reboot. iOS validates its cached device data during startup. If the file's structure, ownership, or contents don't match what the system expects, the cache can be discarded and rebuilt from the factory copy.
The README explains this failure mode in detail. It says the upstream code replaced the cache file through a temporary copy, which changed the file's identity and ownership metadata, so the system rejected it on boot. Erosion-CN's stated fix is to overwrite the file in place, read it back, and roll back automatically if the readback doesn't match. That's the correct design principle: verify the result from disk, not from the return code.
The lesson applies beyond this tool. If you're evaluating any system-level modifier, ask three questions. Does it read the result back from disk? Does it keep a snapshot it can restore? Does it tell you what it will change before it changes it? Erosion-CN's README says it does all three, which is a good sign, but it's a claim you should verify on your own device rather than accept on faith.
Version support: where the tool works and where it doesn't
The README draws a hard line between firmware versions. Here's how the claims break down.
| Platform version | Project's stated support | What it means in practice |
|---|---|---|
| iOS / iPadOS 27.0 – 27.2.1, 27.3 beta 1 | Full support, including cache reads and writes | The only range where the project claims safe persistent writes |
| iOS / iPadOS 26.0 – 26.7.2 | Partial support, no MobileGestalt writes | Read-oriented features such as wallpaper and container browsing work; the cache-editing features don't |
| Other versions | Not listed | Treat as unsupported, since cache layouts change between releases |
Notice the gap in the middle. Cache formats shift between major releases, and a tool that reads offsets from the live library is only as reliable as its validation gate. The README says the tool refuses to write when its checks fail, such as a non-unique cache UUID match or an unexpected file length. That refusal is a feature. If the tool won't write on your build, the right response is to stop, not to force it.
If you update your device after installing, re-check the support table first. A minor OS update can break assumptions even within a supported major version.
The risks the project itself documents
Erosion-CN's own FAQ is candid about what can go wrong, which is rare in this space. Three failure modes stand out.
First, lost functionality. The FAQ describes cases where a change to a regional or carrier-related setting made an option disappear from the system UI until the device was fully power-cycled. A soft respring isn't enough, because background daemons keep their old values until a cold boot. That's a hard lesson: a visible change and a fully applied change are not the same event.
Second, activation problems from leftover supervision artifacts. The FAQ warns that some older modification tools left fake configuration profiles behind, and those can cause a setup-assistant lockout after a system update. A leftover profile is not harmless clutter. It can block the device at the exact moment you need it to work. The project's advice is to avoid faking supervision on a personal device at all, and that's sound advice regardless of which tool you use.
Third, identity mismatches. Changing the hardware identifier the system reads can cause validation failures in other subsystems that check it against what the hardware actually is. The README warns that doing this on certain models can break entire feature sets. Anything that alters how the device identifies itself carries risk well beyond the single setting you touched.
Most people stop reading at the feature list. Don't. The failure modes are the part that determines whether you're still happy with your phone in a month.
Sideloading, App Group access, and why certificates matter
Erosion-CN needs an App Group entitlement to reach the shared containers it uses. The README says you need a sideloading tool that preserves or injects that entitlement, such as SideStore, AltStore, Feather, Sideloadly, Impactor, or iLoader, or a developer certificate that includes App Group rights.
This is where many readers get tripped up. A free personal Apple ID signs an app for a limited period, and when the signature expires, the app stops launching. If the tool is in the middle of a reset or restore when that happens, you can end up with a half-finished state. That's one reason the project stresses making a full computer backup before doing anything.
Sideloading also widens your trust boundary. You're granting a third-party app access to system-adjacent containers, and you're relying on the signing tool to handle your Apple ID responsibly. Only use tools whose source you've read or whose maintainers you trust, and never hand over credentials to a source you can't identify.
Backups are the only real undo button
The project describes a dual backup design: a local original snapshot, plus a copy kept in a system-level shared container so it can survive an uninstall. That's clever, and it's worth understanding why it exists. A backup that lives only inside the app you're modifying is fragile, because removing the app can remove the backup too.
Even so, a backup inside the device is not a substitute for a backup on your computer. If a cache edit goes badly, your restore path has to work, and a full computer backup (via Finder or iTunes on Windows) gives you a known-good state that doesn't depend on the tool being intact. Make that backup before the first change, not after the first problem.
Know the limits of this advice, too. I haven't been able to verify the README's restore claims on a real device, so don't count on them until you've tested the restore path yourself on a spare or non-critical device.
Who should skip this tool
Skip Erosion-CN if your phone is your work device, your only phone, or one you can't afford to have offline for a few days. Skip it if you're on a firmware version outside the project's listed range, or if you can't tolerate the possibility of an activation lockout. And skip it if you're not comfortable reading a README in English or Chinese and checking the claims yourself.
Also weigh the account and policy side. Changing regional or device-identity settings may conflict with the terms of service of Apple or your carrier, and the project's own disclaimer places the risk on you. That's a real consideration, not legal boilerplate.
Where the tool does make sense is in a research context: a spare device, a controlled test environment, or a study of how iOS validates its own configuration. Used that way, it's a useful window into a part of the system most people never see.
Frequently Asked Questions
what is erosion-cn and what does it do?
Erosion-CN is a Simplified Chinese fork of the Erosion project, built for iOS and iPadOS system-configuration research. It reads and edits the MobileGestalt device-property cache through a sideloaded App Group container. The project claims full write support on iOS 27.0 through 27.2.1 and 27.3 beta 1, with partial, read-oriented support on iOS 26.
is erosion-cn safe to use on my iPhone?
Safety depends on your device and your backup habits, not just the tool. The project documents failure modes including lost features, lockouts from leftover profiles, and identity mismatches. Make a full computer backup first, test on a non-critical device if you can, and only use it on a phone you own.
why do mobilegestalt changes revert after a reboot?
iOS validates its cached device data at boot. If a write changes the file's identity, ownership, or structure, the system can discard the cache and rebuild it from the factory copy. Verifying the result by reading it back from disk is the reliable way to confirm a change persisted.
do i need supervision mode to use erosion-cn?
The project says no. It also warns against faking supervision on a personal device, because leftover fake profiles can cause an activation lockout after a system update. If you find old profiles from another tool, check and remove them before updating.
can i undo erosion-cn changes if something goes wrong?
The project offers a restore path to the original cache and a shared-container backup, but its restore claims should be tested before you rely on them. Your most dependable undo is a full computer backup taken before the first change.
Before you install anything like this, take a full computer backup, check the version table against your firmware, and read the project's restore guide. Then, if you're working on a spare device, try the read-only features first and note exactly what changes. Pass this checklist to anyone who's wrestling with a MobileGestalt problem before they reach for a one-tap fix.