Tethered iOS 27 jailbreak
  • Swift 49.9%
  • Python 20.1%
  • Shell 17.7%
  • C 6.7%
  • Objective-C 4.9%
  • Other 0.7%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-11-15 21:25:34 +05:30
.github/ISSUE_TEMPLATE Add Liter8 bug report template 2026-10-20 10:27:55 +05:30
device provision: set keychain owners through /usr/sbin/chown and match the stock wheel group 2026-11-14 17:29:07 +05:30
docs provision: set keychain owners through /usr/sbin/chown and match the stock wheel group 2026-11-14 17:29:07 +05:30
fixtures kernel: scope the tfp0 slide to the kernel task 2026-11-01 16:33:10 +05:30
payloads feat(fw): install the os_log reader during provisioning 2026-11-02 19:31:18 +05:30
scripts feat(fw): install the os_log reader during provisioning 2026-11-02 19:31:18 +05:30
Sources cli: version 0.3.1 2026-11-14 17:48:39 +05:30
Tests provision: set keychain owners through /usr/sbin/chown and match the stock wheel group 2026-11-14 17:29:07 +05:30
tools feat(fw): install the os_log reader during provisioning 2026-11-02 19:31:18 +05:30
vendor Initial public release 2026-09-13 11:07:34 +05:30
.gitignore firmware: add iOS 27.2.1 (24B156) for all three boards 2026-11-13 20:19:48 +05:30
.gitmodules Initial public release 2026-09-13 11:07:34 +05:30
AGENTS.md feat(liter8): keep Wi-Fi network passwords across reboots without SEP 2026-11-02 18:17:57 +05:30
CODEBASE_GUIDE.md profiles: promote 27.2.1 24B156 to reviewed on iPhone 11 2026-11-14 13:10:23 +05:30
LICENSE Initial public release 2026-09-13 11:07:34 +05:30
Makefile feat(liter8): keep Wi-Fi network passwords across reboots without SEP 2026-11-02 18:17:57 +05:30
Package.resolved refactor(liter8): adopt swift-argument-parser for scoped help 2026-10-08 19:25:48 +05:30
Package.swift refactor(liter8): adopt swift-argument-parser for scoped help 2026-10-08 19:25:48 +05:30
README.md Update README.md 2026-11-15 21:25:34 +05:30
requirements.txt Initial public release 2026-09-13 11:07:34 +05:30
setup.sh fix(liter8): rebuild idevicerestore when the cached binary cannot run 2026-10-02 18:04:42 +05:30

Liter8

Tethered iOS 27 jailbreak for iPhone 11.

iOS Device Boot Buy me a coffee

iPhone 11 on iOS 27.2.1: fastfetch over root SSH, Sileo, and the home screen with Sileo and TrollStore Lite

Important

Tethered. The phone only boots from pwn DFU with fw boot, so the Mac has to be there every single time. No Mac, no boot.

iPhone 11 only (iPhone12,1, n104ap). I don't own another A13 device, so that's all I'm willing to claim.

Status

Works

  • Boot: normal boot to the home screen, root SSH, apt and Sileo, TrollStore, apps launch
  • App Store: Apple ID sign-in and app installs
  • Tweaks: ElleKit injection, ObjC and C function hooks. See using the tweak loader
  • Keychain
  • tfp0: kernel read/write for libkrw0-tfp0, with fw get-boot --tfp0
  • Cellular: no flags needed. SIM ready, carrier bundle matched, registered on the network
  • Calls and SMS: over IMS, carried by WiFi Calling, so they need WiFi connected and WiFi Calling on
  • Developer tools: USB lockdown pairing, same-boot RemoteXPC reconnect, QuickTime capture, and CoreDevice process listing and screenshots once the DeveloperDiskImage jobs are up

Doesn't work yet

  • SEP, and passcode with it
  • Cellular data, and VoLTE with it. The bearer comes up with a real carrier address and the modem acknowledges every instruction, but nothing ever comes back. Narrowed to inside the baseband, with everything above it ruled out: the blocker, and what was eliminated
  • Apple services, iCloud included (the App Store is the exception, see above). Push has no token, because minting one needs a real activation record, which needs a SEP-attested key. Measured, not assumed
  • MobileBackup2. Both clients reach the service and negotiate, then the backup fails because the boot has no normal persona state

PRs welcome on any of these, especially SEP.

Supported firmware

Firmware Build iPhone 11 11 Pro 11 Pro Max
iOS 27.0 beta 4 24A5390f run - -
iOS 27.0 RC 24A435 run - -
iOS 27.0 24A437 - experimental experimental
iOS 27.0.1 24A446 run experimental experimental
iOS 27.2 beta 1 24B5084k run - -
iOS 27.2 beta 2 24B5089g run - -
iOS 27.2 beta 3 24B5099f run - -
iOS 27.2 beta 4 24B5110a run - -
iOS 27.2 24B119 run experimental experimental
iOS 27.2.1 24B156 run experimental experimental
iOS 27.3 beta 1 24C5037i run experimental experimental

run: I did an erase restore, booted it normally, then rebooted and it came back up.

experimental: resolves, and you can use it with --experimental, but nobody has confirmed it on that phone. The 11 Pro and Pro Max have profiles and no device to test on. If you own one and try it, tell me what happens and I'll change the tag.

Warning

fw restore-cfw pulls a fresh APTicket from Apple during the restore, so once Apple stops signing a build you can't install it anymore. A row stays in the table because I tested it, not because you can still use it today. Check signing first.

A build that isn't in the table extracts for research only, and make-cfw, restore, boot and provision all refuse it. The profiles don't carry offsets either, so adding a build isn't a matter of pasting numbers in. The resolvers work them out at runtime.

Install

You need macOS 14 or newer, Xcode command line tools with Swift 6, and Homebrew.

brew install \
  sevenzip blacktop/tap/ipsw gnu-tar coreutils zstd ldid-procursus sshpass autoconf automake libtool pkg-config \
  libimobiledevice libimobiledevice-glue libirecovery libusbmuxd libplist libtatsu libzip curl
git clone --recurse-submodules https://github.com/Xplo8E/liter8.git
cd liter8
make setup
make release

The binary ends up at .build/release/liter8.

Usage

Everything lands in one work directory: WORK_DIR, or --work-dir, or the directory you're standing in if you set neither.

Run the steps in order, every time. Each one eats the output of the one before it. Coming back to a phone days later, restart from fw make-cfw rather than guessing where you left off.

Caution

Step 3 wipes the phone. Erase restore, everything gone, no undo. Read the IPSW path, the device, the build, the board and the work dir twice before you hit enter.

1. Prepare the IPSW

export WORK_DIR="$PWD/.liter8"
.build/release/liter8 fw prepare --file /path/to/firmware.ipsw

The build comes from BuildManifest.plist, not the file name. IPSW_FILE works in place of --file.

2. Build the CFW

.build/release/liter8 fw make-cfw

3. Restore it

Phone in pwn DFU, then:

.build/release/liter8 fw restore-cfw

It checks the CFW over, starts a local TSS proxy to catch the restore ticket on its way through, and shuts the proxy down once idevicerestore exits.

4. Boot the SSH ramdisk

Back to pwn DFU.

.build/release/liter8 fw get-rd
.build/release/liter8 fw boot-rd

5. Provision

The phone is in the SSH ramdisk now.

.build/release/liter8 fw bootstrap --check
.build/release/liter8 fw bootstrap
.build/release/liter8 fw prepare-rootfs
.build/release/liter8 fw provision --check
.build/release/liter8 fw provision
.build/release/liter8 fw unmount-rootfs

6. Boot iOS

pwn DFU again.

.build/release/liter8 fw get-boot
.build/release/liter8 fw boot

Tip

Take the SIM out before going through Setup on a fresh restore. Cellular data doesn't work, so Setup can hang waiting on the network. Put it back once you're on the home screen.

7. Finish the bootstrap

Wait until you can SSH into the booted OS, then:

.build/release/liter8 fw finalize --check
.build/release/liter8 fw finalize
.build/release/liter8 fw finalize --check

The second --check is just so you can see it went through.

Build options: --serial, --tfp0, and what TXM ships with

--serial on fw make-cfw, fw get-rd and fw get-boot writes serial=3 into the boot args, which moves the kernel console onto the UART. Useful when a boot dies early. The downside is the phone screen goes quiet, no boot log on the device anymore. It's off by default, and because it gets baked in at build time you have to pass it to each command separately.

--tfp0 on fw get-boot adds the tfp0 kernel patches used by libkrw0-tfp0. iPhone 11 only, on every build in the table except 27.0 beta 4. Off by default. The slide is handed out only when the kernel task is the one being asked about, so every other process keeps its real TASK_DYLD_INFO and lldb still sees a module list.

TXM: fw get-boot always builds TXM with its code-signing policy flags on (any signature, unrestricted local signing, relaxed profile trust, CS enforcement disabled, unrestricted task_for_pid) plus the patches C function hooks need. CoreTrust stays enforced. The boot manifest records it as txmPlan: boot-permissive.

Optional: debugger and TrollStore

Not part of the jailbreak. The device needs internet for this one, because apt resolves the dependencies on the phone.

.build/release/liter8 fw setup-debugger

Installs debugserver, re-signed so hardware breakpoints work, plus the TrollStore Lite helper. Then:

ssh -p 2222 root@localhost \
  'nohup /var/jb/usr/bin/debugserver-16 127.0.0.1:1237 --attach=<pid> >/var/root/ds.log 2>&1 &'
ssh -N -L 1237:127.0.0.1:1237 -p 2222 root@127.0.0.1

lldb -o 'platform select remote-ios' -o 'process connect connect://127.0.0.1:1237'
(lldb) breakpoint set -H -n <symbol>

-H is not optional: software breakpoints are silently dropped on this platform. Attaching to a daemon also needs a DeviceSupport tree for your exact build, or lldb hangs on connect. Both are explained in debugging platform daemons.

How it works

Liter8 doesn’t ship offset tables. Each time you build, it opens the actual binaries (iBoot, the kernel, TXM, a few userland daemons and the DeviceTree) and finds every patch site from scratch using strings, cross-references, control flow and the instructions around it. If an anchor can’t be found, or turns up in more than one place, it stops rather than take a guess.

A patch is three things: where to write, the bytes that should already be there, and the bytes that replace them. Nothing gets written until every patch in the plan has been checked. If a site still has its original bytes, the patch gets applied. If it already has the new bytes, it’s left alone. If it has anything else, the whole plan is rejected. So a plan either goes in completely or not at all, and running it a second time won’t break anything.

The Swift side does all of this. It also works out which firmware you gave it by reading BuildManifest.plist, and it handles IMG4, IM4P and APTickets. The Python side is mostly plumbing. It moves disk images around, stages files, runs idevicerestore and the USB tools, and takes the phone through each stage. Whenever a binary needs patching, Python hands it to the Swift binary, so you won’t find any patch logic or offsets in the Python code.

Firmware profiles don’t contain offsets either. A profile only decides which signature and payload variants match a given kernel. Every step that talks to the phone also checks the firmware identity again for itself instead of trusting an earlier check.

For the source layout and how execution moves through it, see CODEBASE_GUIDE.md.

Docs

Using it

Design

Research and device runs

Contributing and support

Start with CONTRIBUTING.md. If you're porting a firmware, read ADDING_FIRMWARE_SUPPORT.md too.

PRs are welcome on anything under Doesn't work yet, especially SEP. The 11 Pro and Pro Max are open too: if you own one and want to take the port on, I'll help where I can. Or if you'd rather help on the hardware side, there's a coffee link and that's what it'd go towards. Either route is fine, and so is neither.

Credits

None of this starts without these people.

License

MIT, see LICENSE. Submodules, tools and payloads keep their own licenses.

Star History

Star History Chart