3105's compatibility table is a list of build numbers, and its screenshots are from the simulator

The previews demonstrate the interface and nothing about the device

The warning at the top of the page says two things at once: that 3105 is research software for personal device management, and that the simulator screenshots demonstrate the interface only and do not verify device-level access. That second clause governs everything the Preview section shows. Since the app's entire value is reading app containers that a normal sandboxed app cannot reach, an image of a file browser running in the simulator says nothing about whether any of it works on hardware. It also sets the tone for the rest of the page, which repeats the boundary in different forms rather than arguing past it. Anyone judging the project has to take someone else's device as evidence, not this repository.

Compatibility is four beta build numbers, not an iOS version

The table is a list of ranges and exact builds rather than major versions. iOS 17 covers 17.0 through 17.7 and iOS 18 covers 18.0 through 18.7.1, both annotated as kernel exploit. iOS 26 covers 26.0 through 26.6.1 with no mechanism named, and iOS 27 is given as four specific builds: developer beta 1 as `24A5355q`, beta 2 as `24A5370h`, beta 3 paired with public beta 1 as `24A5380h`, and beta 4 paired with public beta 2 as `24A5390f`. Unlisted iOS 27 builds are marked unsupported rather than assumed compatible. On 17 and 18 the exploit is opt-in behind a manual button, and the stated reason is blunt: a failed attempt may restart the app.

The bundle identifier is deliberately Apple's MobileHouseArrest

The installation notes contain the project's sharpest admission. Device functionality requires signing with an enterprise certificate. The target bundle identifier is intentionally `com.apple.mobile.MobileHouseArrest`, and changing it breaks the MHA-C2 app-container workflow, so the app presents itself under Apple's own identifier because that is what the container workflow expects. SideStore, AltStore, 3uTools and LiveContainer are all named as unsupported installation paths. The source tree contains no certificates, no provisioning profiles, no signed applications and no IPA files, though release assets may provide an unsigned IPA. In practice this is a research build you sign yourself, which is also why the responsible-use section asks you to keep a backup.

Three package formats with three different jobs

Content arrives as three kinds of file with three names. Portable `.3105` patches are the functional ones: one patch can target several apps and App Groups, find the matching data on each device, expose user-configurable text fields, switches and choices, optionally require a password, replace files, edit plist and JSON content, and restore the original files after use. `.3105pass` packages are dialer themes that follow the light, dark or bold keypad style detected on the device. `.tendies` packages are PosterBoard wallpapers, and their descriptions can carry preview images. On top of that, 3105's own features are installable content too, with Cleaner added in 2.0 and Lock Screen Footnote and Supervised mode offered on supported iOS 27 builds. Version 2.0 also rewrote the recovery paths, with improved backup, reset, restore and active-patch removal flows and clearer feedback after each action. That matters more than it sounds for a tool that overwrites files inside other apps' containers: removing a patch has to put back what was there, and the page states patches restore their original files after use.

A patch spanning several apps applies only the portion each device has

The 2.0 notes describe a partial-application model that is easy to misread. A single patch can target multiple apps and App Groups, find the matching data on each device, and apply the portions available on that device. What it does not describe is a failure mode, so it is worth being explicit about what that implies: with a multi-target patch, the device that has all the target data gets the full patch and the device with partial data gets the part that fits, without the page promising an error. Installed library entries carry update indicators when a newer package is available, and the marketplace adds For You and New discovery alongside per-source browsing, each with download progress and an installation result.

The Files area reaches cookies and account databases by design

The redesigned Files experience is the part to look at first if you own the device, because it defines what the app can see. It is organised into Workspace, Application and App Group areas, plus hidden files, tabs, favourites, file information and a simple plist editor, and the browser locates app data by a recognizable app name or a stable identifier. The file operations list is broad: search, preview, share, import, copy, move, rename, delete, and creating or extracting ZIP archives. The responsible-use section then names the corresponding hazard in its own words: do not publish logs, app containers, cookies, account databases or patch payloads containing personal data, and report security-sensitive issues privately to the maintainer.

One Xcode project, three directories, and credits that name the research

The whole source tree is small enough to state exactly:

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

Alongside those sit `README.vi.md`, `THIRD_PARTY_NOTICES.md` and a changelog, and the original portions are under GPL v3 while third-party components stay under their upstream terms. The credits name the developer and then the research the app stands on: FilzaSlop and four proof-of-concept repositories covering an identity-trust bug, a `partDomain` traversal, a persisted-state and final-symlink chain, and a zero-file creation issue, alongside work from Pocket Poster, CrazyMind90, forcequitOS and Dopamine. Releases came in a burst, 1.1.0 and 1.1.1 an hour apart on 2026-08-19, then 2.0 on 2026-09-14, which is also the last push.

Editorial conclusion

3105 suits someone who already manages their own device, understands that app containers hold cookies and account databases, and wants a browser and patch manager for that data without installing a persistent jailbreak. It does not suit anyone looking for a sideloading path, since SideStore, AltStore, 3uTools and LiveContainer are named as unsupported and an enterprise certificate is required. Before trusting it, check your exact build against the compatibility table rather than your iOS major version, back up the device as the warning asks, and remember that the previews on the page are simulator captures that verify nothing about device-level access.

Frequently asked questions

Official sources

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