3105: an iOS app-data browser and patch manager that needs an enterprise certificate

What 3105 actually solves, and for whom

iOS gives users no supported way to look inside another app's container. 3105 exists to fill that gap: it presents app data by a recognizable app name or stable identifier, and lets you search, preview, share, import, copy, move, rename, delete, create and extract ZIP archives, use tabs, and save favorites. On top of the browser it adds a content layer. Patches, wallpapers, dialer themes, and 3105's own features are downloaded from sources, tracked in an Installed library, and updated when a newer package appears. The README describes version 2.0 as turning 3105 from a collection of separate tools into one place to discover, install, and manage content.

The audience is narrow and stated plainly. The README calls 3105 research software for personal device management and tells you to keep a backup and use it only on devices and data you own. This is a tool for someone who already understands what a container is, who is comfortable with an enterprise certificate, and who accepts that app data modification can break an app's integrity or trip its jailbreak-detection policy. It is not a consumer file manager, and the compatibility table is deliberately conservative: only builds explicitly verified by the project are enabled.

How the container access and the patch pipeline fit together

The mechanism is named in the repository itself. The target bundle identifier is intentionally com.apple.mobile.MobileHouseArrest, and the README warns that changing it can break the MHA-C2 app-container workflow. MobileHouseArrest is the identity-trust path the project credits to 0xjohnny's MobileHouseArrest-PoC, alongside PoCs for a geod MobileContainerManager partDomain traversal, an InstallCoordination persisted-state and final-symlink chain, and cfprefsd zero-file creation. Those four techniques are the foundation the browser stands on, and the credits section lists them explicitly rather than hiding them behind a generic thanks.

Above that layer sit two package formats. Patches are portable .3105 files that can target multiple apps or App Groups, find the matching data on each device, and apply only the portions available there. A patch can replace files, edit plist or JSON content, expose text fields, switches and choices to the user, and optionally require a password; it can also restore original files after use. Dialer themes arrive as .3105pass packages and can follow the light, dark and bold keypad style detected on the device, while wallpapers ship as .tendies packages that the app downloads, previews, and removes from the Installed list. The iOS 17 and 18 range uses a kernel exploit that is opt-in behind a manual button, because the README states a failed attempt may restart the app.

Installing 3105 and taking a first look at an app container

There is no App Store download and no IPA in the source tree. The README states that the source tree does not contain certificates, provisioning profiles, signed applications, or IPA files, and that release assets may provide an unsigned IPA. Device functionality requires signing with an enterprise certificate, and the README lists SideStore, AltStore, 3uTools and LiveContainer as unsupported installation paths. So the first step is not a command; it is obtaining an enterprise signing identity and building or signing the app yourself.

The project layout is small enough to build in Xcode directly. The README shows the tree as the SwiftUI app, the Xcode project, and the documentation images:

3105/
├── ThreeOneOSFive/          # SwiftUI app, helpers, native bridges, localizations
├── ThreeOneOSFive.xcodeproj # Xcode project and 3105 scheme
└── docs/images/             # Repository artwork and current UI previews

Open ThreeOneOSFive.xcodeproj, select the 3105 scheme, and sign with your certificate. Do not rename the bundle identifier: the README says the target is intentionally com.apple.mobile.MobileHouseArrest and that changing it can break the MHA-C2 app-container workflow. Once the app is on the device, the Files experience is split into Workspace, Application and App Group areas, with hidden files, tabs, favorites, file information, and a simple plist editor. A reasonable first task is to open an Application area, pick an app you own, and inspect a plist before you install anything from a source. The README also points to docs/PATCH_GUIDE.md for the patch format, which is where you should go before writing a .3105 file, since the README itself only summarizes what a patch can do.

The signing wall is the real adoption cost

The most consequential limitation is not a missing feature. It is distribution. Requiring an enterprise certificate excludes most people who would otherwise try this, and the explicit exclusion of SideStore, AltStore, 3uTools and LiveContainer removes the paths a typical sideloading user would reach for first. If your only signing option is a free personal team, the README gives you no supported route at all.

Compatibility is the second wall. The verified range covers iOS 17.0 through 17.7 and 18.0 through 18.7.1 on a kernel exploit, iOS 26.0 through 26.6.1, and four specific iOS 27 builds: 24A5355q, 24A5370h, 24A5380h and 24A5390f. The README states that unlisted iOS 27 builds are marked unsupported rather than assumed compatible. That is an honest policy, but it means a device on a newer beta can be refused entirely. The kernel exploit path carries its own cost: it is opt-in behind a manual button because a failed attempt may restart the app, so you should not treat the iOS 17 and 18 workflow as a one-tap operation.

Two more boundaries are worth stating. The README says simulator screenshots demonstrate UI only and do not verify device-level access, so the preview images are not evidence that container access works on your hardware. And 3105 does not install a persistent jailbreak, bootstrap or daemon and does not inject code into third-party apps, yet it still uses device exploits and modifies app data, so the README declines to make a universal guarantee against every app's integrity or jailbreak-detection policy. If an app treats modified containers as tampering, that is a risk you accept, not one the project can rule out.

How 3105 differs from Filza and from the PosterBoard tools it credits

The closest comparison is Filza, the long-standing iOS file manager, and the README's credits point to FilzaSlop from the same researcher whose PoCs 3105 builds on. The difference in approach is that Filza is a general file browser first, whereas 3105 organizes the same container access around a content library: sources, downloads, an Installed list, update indicators, and typed packages. Patches in 3105 are declarative .3105 files that can target multiple apps and App Groups, expose user-configurable fields, and restore originals after use, rather than a manual sequence of file edits. That packaging is the actual product, not the file operations.

The PosterBoard side overlaps with Pocket Poster and Nugget, which the README credits alongside CrazyMind90, forcequitOS and Dopamine. Those projects approach wallpaper and system customization as their own tools; 3105 treats .tendies wallpapers as one more content type inside the same Installed library, downloaded from repository sources and removable from the same screen. Whether that consolidation is better depends on whether you want one app with a shared install and recovery flow or a set of narrower utilities. The README does not claim feature parity with any of them.

Maintenance, licensing and what upgrades cost you

The repository is not archived, and its most recent push was on 2026-09-14, the same day as the 2.0 release, following 1.1.1 and 1.1.0 on 2026-08-19. Releases are frequent enough that the Installed library's update indicators have something to point at, and the 2.0 notes describe a substantial restructuring rather than a patch-level change. The upgrade cost sits with the compatibility table: moving to a new iOS build is not automatic, because the project verifies builds individually and marks unlisted iOS 27 builds unsupported. If you depend on 3105, your device's iOS version is effectively part of your dependency set, and updating iOS can take the tool away until the project adds that build.

3105 is GPL-3.0, and the README says original portions of 3105 are licensed under it while third-party components are attributed in THIRD_PARTY_NOTICES.md. That file is the place to check before redistributing anything, since the project builds on several upstream PoCs and tools. This is a description of what the repository states, not legal advice; if you plan to ship a modified build or bundle it with other code, read LICENSE and THIRD_PARTY_NOTICES.md and get your own advice on how the GPL interacts with the upstream notices.

Editorial conclusion

3105 is for people who own the device, already work with enterprise signing, and run one of the verified builds listed in the compatibility table, since the README states that functionality requires an enterprise certificate and that SideStore, AltStore, 3uTools and LiveContainer are not supported installation paths. It is not for anyone who wants a normal sideloading workflow, for unlisted iOS 27 builds (the README marks them unsupported rather than assuming compatibility), or for production devices where an app container must not be touched. Before adopting it, confirm that your iOS version and build appear in the compatibility table, that your certificate route is enterprise-grade, and that you have a backup, because the README warns that a failed kernel exploit attempt may restart the app and that no universal guarantee can be made against every app's integrity or jailbreak-detection policy.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. Project website
3. README
4. Releases
5. YangJiiii/3105 on GitHub