# FilzaSlop: a Filza fork that reaches app containers on unjailbroken iOS 18, 26 and 27 betas

> FilzaSlop is a fork of FilzaJailed that adds a sandbox escape, app container access and a PosterBoard Wallpaper Lab for iOS 18, iOS 26 and iOS 27 beta 1 to 4. It ships as an unsigned IPA whose bundle identifier must survive signing untouched, and the README warns that not every feature works on the two shipping versions.

**0xjohnnydev/FilzaSlop** — FilzaJailedDS fork with container access for iOS 18, iOS 26, and iOS 27 beta 1–4. See README for per-bug status.

- Repository: https://github.com/0xjohnnydev/FilzaSlop
- Stars: 439 · Forks: 45
- Language: Objective-C
- License: not declared
- Published: 2026-09-18 · Updated: 2026-09-18 · Language: en
- Canonical page: https://hysenlabs.com/projects/0xjohnnydev-filzaslop

## What FilzaSlop adds to a jailed file manager

Filza is a long-running iOS file manager. FilzaSlop is a fork of FilzaJailedDS, and the README lists three additions: a sandbox escape for iOS 18, iOS 26 and iOS 27 beta 1 to 4, app container access, and a PosterBoard Wallpaper Lab, plus a set of less prominent directories.

The audience is narrow and specific: people on modern iOS who have not jailbroken and still need to reach data that iOS normally keeps away from apps. That means developers inspecting their own app's container, people rescuing media or saves from an app that offers no export, and hobbyists who want to change wallpaper assets. If a Mac, a backup extractor or the app's own export already gets you the file, this is a harder path to the same result.

The project is candid about coverage. Its README carries the warning that not every feature currently works on iOS 18 or iOS 26, and asks users to open an issue when something breaks. Treat the version list as a claim about the escape, not a promise that the whole feature set behaves the same on each version.

## What the escape actually grants

The mechanism the README names is MobileHouseArrest. Container access comes from MobileContainerManager leases and sandbox extensions, and the project is careful about scope: FilzaSlop does not install a daemon and does not inject code into other processes. The leases and extensions belong to the Filza process, generated links and reports are stored in Filza's own data container, and deleting the app removes that container.

One consequence deserves emphasis because it surprises people. Files edited through a live container link are the real target files, so uninstalling FilzaSlop does not revert them, including Wallpaper Lab changes. There is no undo step hiding behind app deletion.

The paths the README lists give a fair picture of the reach:

```bash
/private/var/mobile/Containers/Data/Application/
/private/var/mobile/Containers/Shared/AppGroup/
/private/var/mobile/Containers/Data/PluginKitPlugin/
/private/var/mobile/Containers/Data/VPNPlugin/
/private/var/mobile/Containers/Data/InternalDaemon/
/private/var/mobile/Containers/Data/System/
/private/var/containers/Shared/SystemGroup/systemgroup.com.apple.mobilegestaltcache/Library/Caches/
```

That is application data, app groups, plugin containers and two system group caches. It is not a full filesystem view, and nothing in the README claims otherwise.

## Installing FilzaSlop and the signing trap

Distribution is an unsigned IPA on the Releases page. Unsigned means you must sign it before iOS will install it, and the signing step is where most attempts fail, because the bundle identity is load bearing rather than cosmetic.

The README gives the values that must survive signing:

```bash
CFBundleIdentifier:       com.apple.mobile.MobileHouseArrest
CodeDirectory identifier: com.apple.mobile.MobileHouseArrest
```

Changing either one disables the MobileHouseArrest path. A free Apple Account, also called a Personal Team, cannot currently sign the standalone IPA while keeping that identity: Apple rejects the identifier with error 9400 or 9401. Letting the signer create a unique bundle ID will produce an app that installs and does not work, and keeping the MobileHouseArrest CodeDirectory identifier under a normal bundle ID fails before launch with MismatchedBundleIDSigningIdentifier. The README's advice is direct: do not use automatic bundle ID, and a successful install with a changed identifier is not a working sandbox escape.

That leaves a paid certificate for standalone use. The README mentions certificate providers such as ArcticSign, notes they are independent of the project and that Apple can revoke their certificates, and points to the r/Jailbreak Discord and r/sideloaded for current recommendations before paying.

## LiveContainer mode and what it cannot reach

For free accounts there is a second path, marked experimental. Running the unsigned IPA as a guest inside LiveContainer avoids the standalone signing problem, but the README is explicit that this mode does not provide MobileHouseArrest access. FilzaSlop cannot browse or edit containers for App Store apps or other apps installed by iOS. It can manage only guest apps and data stored inside LiveContainer, and the project says to use the mode for that purpose only.

The setup is five steps: install LiveContainer with SideStore or AltStore using its normal automatic bundle ID, download the unsigned FilzaSlop IPA, open LiveContainer and add it with the plus button, and on iOS 26 or later configure JIT-less mode by importing the certificate from SideStore or AltStore. The ongoing cost is renewal, because Apple limits a Personal Team to three installed apps per device, ten registered App IDs and seven-day provisioning profiles, so LiveContainer has to be refreshed before its profile expires.

This is the honest summary of the free route: it works on files inside LiveContainer and nowhere else.

## Jailbreak detection, and what removing the URL scheme cannot undo

Release v1.1.0 changed how the app is visible to others. From that version on, FilzaSlop does not register filza:// or any other URL scheme, and the release build removes CFBundleURLTypes and fails if the key remains. There is no separate standard build. The point is to stop another app discovering the tool through a canOpenURL: check, and v1.1.0 additionally strips filza://, Dropbox, Box SDK and Google OAuth schemes from the IPA during the build.

The README is equally clear about the limit of that fix. Removing the scheme cannot clear a result another app already saved, and a canOpenURL: failure in a system log confirms only that the check returned negative. For a banking app that still reports a jailbreak, the documented sequence is to confirm FilzaSlop was deleted rather than offloaded or removed from the Home Screen, remove any older copy or LiveContainer guest, and ask the app's support team to reset device or account risk state, since reinstalling may not clear Keychain or server state. Two further notes matter: the bundled Filza app can store its own remote-service credentials in a Keychain access group that iOS may retain after deletion, while the injected FilzaSlop code uses no Keychain APIs and cannot read another app's saved state; and sandbox deny messages naming jailbreak paths, kern.bootargs or fork show a probe was blocked, not that the capability exists.

## FilzaJailed, the upstream this fork builds on

The comparison that matters is with the project FilzaSlop forks. FilzaJailed is the jailed branch of the same file manager, aimed at what an ordinary sideloaded app can already reach: the app's own documents, transfers in and out, and the file operations iOS permits without an escape. It is the safer default when your files are already somewhere a jailed app can see.

FilzaSlop's additions are precisely the parts that go further: the sandbox escape, container access for other apps' data, and the Wallpaper Lab. That is why the install is harder and why the failure modes are sharper. A jailed file manager that fails to sign is a nuisance; a container access tool that signs with the wrong identifier installs, launches and silently does nothing, which is the trap the README spends most of its signing section on.

Choose on what you actually need to touch. Moving files you already control belongs to the upstream tool. Reaching into another app's container is the only reason to take on FilzaSlop's signing constraints, beta-version caveats and detection fallout.

## Releases, update checks and the missing licence

The release notes are specific and worth reading in order. FilzaSlop v1.2.0, published on 2026-08-28, added an update check, embedded the release tag in the IPA for version comparison, enforced removal of URL schemes during packaging, documented the jailbreak-detection boundaries for issue #30, and built with the current installed iPhoneOS SDK. Its artifact is FilzaSlop-v1.2.0-unsigned.ipa with the SHA-256 printed in the notes. v1.1.0, published on 2026-08-18, stripped the URL schemes to prevent detection through canOpenURL:. v1.0.3, published on 2026-08-13, added archive and safer permanent deletion with a backup warning, fixed deletion across Filza's menus, and introduced the experimental LiveContainer mode.

The update checker queries this repository's latest published non-prerelease GitHub release when each installed version first launches, and again after 24 hours when the app next becomes active. It shows one alert per newer release with a link, and never downloads or installs anything. Its request carries no device identifier or Filza content, and it stores only the last check date, the installed version and the last alerted tag.

On licensing there is nothing to rely on. The repository has no licence field and no LICENSE file in its tree, so the usual default of all rights reserved applies and redistribution or derivative work has no granted permission. The last push was on 2026-08-28, and one supported target is a moving beta, so expect the escape to need rework as iOS 27 ships.

## Conclusion

FilzaSlop fits people running iOS 18, iOS 26 or iOS 27 beta 1 to 4 who need to read or edit another app's container and can sign an IPA with a paid certificate while preserving the com.apple.mobile.MobileHouseArrest identifier. It does not fit anyone hoping for a free-account install, since a Personal Team cannot keep that identifier and a changed identifier installs but disables container access, nor anyone who depends on banking apps on the same device, because a detection result saved before v1.1.0 is not cleared by the URL scheme removal. Read the per-version status in the README before you start, and confirm the SHA-256 of the v1.2.0 IPA matches e719ebb2b3babfb43c4d4e21904ec7c223f8e4ff5e634d4a2cbad9a5d103da27.

## FAQ

### Does FilzaSlop work without a jailbreak?

Yes, that is the point of the fork. You sideload and sign the unsigned IPA from the Releases page rather than jailbreaking, and the README lists a sandbox escape and app container access for iOS 18, iOS 26 and iOS 27 beta 1 to 4.

### What is FilzaSlop?

It is a fork of FilzaJailedDS, the jailed branch of the Filza file manager for iOS. The fork adds a sandbox escape, app container access, a PosterBoard Wallpaper Lab and access to some additional system directories.

### How do you get FilzaSlop on an iPhone?

Download the unsigned IPA from the project's Releases page and sign it before installing. A free Apple Account cannot sign it while keeping the com.apple.mobile.MobileHouseArrest identifier, so standalone use needs a paid certificate, or you can run it as an experimental LiveContainer guest with no container access.

### Does FilzaSlop support iOS 18?

The README lists a sandbox escape for iOS 18 as well as iOS 26 and iOS 27 beta 1 to 4. It also warns that not every feature currently works on iOS 18 or iOS 26, so check the per-version status before relying on a specific capability.

## Sources

- [0xjohnnydev/FilzaSlop on GitHub](https://github.com/0xjohnnydev/FilzaSlop)
- [Issues](https://github.com/0xjohnnydev/FilzaSlop/issues)
- [README](https://github.com/0xjohnnydev/FilzaSlop/blob/main/README.md)
- [Releases](https://github.com/0xjohnnydev/FilzaSlop/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/0xjohnnydev-filzaslop