Frequently Asked Questions

No. It runs on a stock, non-jailbroken device. It does not obtain root access and does not modify the system partition. One caveat: some installation paths — the TrollHelper route, for instance — do assume the device is already jailbroken. That is a limitation of that particular delivery method, not of the mechanism itself. Check the guide for your version.

No. This is the single most important difference from ordinary self-signing tools. Self-signed apps rely on a personal developer certificate and typically have to be re-signed every 7 days or they stop opening. Apps installed through this mechanism do not expire when a certificate lapses, and they still open after a restart — on supported iOS versions.

A narrow set, decided entirely by version: part of the range from iOS 14.0 to 16.6.1, plus iOS 17.0. The underlying flaw was fixed in iOS 17.0.1 and later, and there is currently no method for those versions. See the compatibility page for the full breakdown.

No, and it is a hard limit. The mechanism depends on one specific component flaw; once it is patched, the affected versions lose support permanently. There is no substitute method and no "newer tool" that restores it. Anything claiming otherwise — a tutorial, a download page, a video — should be treated as suspect.

The tooling is open source and the code can be inspected publicly; it does not phone home or collect data. The real risk comes from the apps you install, not from the mechanism. Packages obtained from unofficial sources may have been modified, so only install software whose origin you trust.

This is a known consequence on iOS 15 and later, not a failed installation. When the system reloads its icon cache, the app is demoted from a system-level to a user-level signing state, and it can no longer be launched. The fix is to configure the persistence helper as part of installation; if you have already run into it, follow the recovery steps in the persistence helper guide.

Three common causes: the app is not compatible with your iOS version; the app is missing a capability declaration it needs at runtime; or the package itself is incomplete. Try a different build of the app first — the mismatch between app and OS is a far more likely culprit than the installation procedure.

Yes, and usually irreversibly. Minor updates within the same major version are generally harmless, but a major-version update has a high chance of disabling the entire mechanism, leaving installed apps unable to open. Before updating, confirm the target version is still within the supported range.

These apps cannot be removed the usual way by long-pressing the icon. You need to uninstall from within the tooling app that manages them. If that tool will not launch either, reinstalling it is how you regain control.

Because third-party copies carry real risk. We do not host, mirror or forward any installation files — every link points at the project’s official repository. Files held by third parties can be swapped and are frequently the wrong version, which is the root cause behind a large share of "I followed the guide and it failed" reports.

Largely no. The flaw was patched in iOS 17.0.1, and no publicly available method exists for anything after it. Most of what circulates on video platforms and download sites is there to attract traffic, and a good deal of it repackages entirely unrelated files as a "new version of the tool".

Two things. First, confirm the target version is still inside the supported range — a major-version jump will very likely break the mechanism. Second, back the device up completely, including one local backup through a computer; do not rely on iCloud alone. Update only after the backup is done.