Legacy iOS Kit: downgrade, jailbreak and blobs for old iPhones on Linux and macOS

What Legacy iOS Kit does that iTunes and Finder do not

Apple's own restore path only serves versions that are still signed. Legacy iOS Kit exists to work around that: it restores and downgrades devices to versions Apple no longer signs, using OTA update servers, saved SHSH blobs, or in some cases no blobs at all. The README describes it as an all-in-one tool to restore/downgrade, save SHSH blobs, jailbreak legacy iOS devices, and more.

The audience is narrow and clearly defined by the project itself. Legacy iOS Kit defines legacy devices as all iOS devices vulnerable to a bootrom exploit, checkm8 and older. That covers all 32-bit devices, plus some 64-bit A7 through A11 models. Devices that received iOS 16 or newer get limited functionality only, such as sideloading, and features like the SSH ramdisk are explicitly not supported on them.

Beyond restoring, the feature list includes hacktivation for the iPhone 2G, 3G, 3GS and iPhone 4 GSM, jailbreaking, saving onboard SHSH blobs, booting an SSH ramdisk, sideloading IPA files, clearing NVRAM, device activation through ideviceactivation, and app and data management utilities. Baseband handling is part of the restore flow too: the latest baseband is flashed for certain A5/A6 devices, including the iPhone 4S, 5, 5C, iPad 4 and iPad mini 1.

How the restore and downgrade paths actually differ

Legacy iOS Kit is not one mechanism. It is a menu of methods with different prerequisites, and picking the wrong one is the main way to waste an evening.

The OTA path is the simplest: the device downloads a still-signed OTA version from Apple's servers. The README lists iOS 8.4.1 for the iPhone 4S, 5, iPad 2, 3, 4, iPad mini 1 and iPod touch 5, iOS 6.1.3 for the iPhone 4S and iPad 2 (except iPad2,4), and iOS 10.3.3 for A7 devices: iPhone 5S, iPad Air 1 and iPad mini 2 except iPad4,6. iPhone 5C and iPad mini 3 are explicitly not supported by OTA downgrades.

The blob path applies where a version is unsigned but you saved an SHSH blob while it was signed. Restoring with SHSH blobs is supported on the older 32-bit list (iPhone 2G through 5C, iPad 1 through 4 and mini 1, iPod touch 1 through 5) and on some 64-bit devices including the iPhone 5S, 6, 6S, SE 2016 and 7, iPad Air 1 and 2, iPad mini 2, 3 and 4, and iPod touch 6 and 7. On those 64-bit devices, which versions you can reach depends on SEP and baseband compatibility, though the README notes that SEP/BB compatibility no longer matters for A9(X)/A10(X) devices thanks to turdus merula. A separate futurerestore path covers iOS 14.3 to 15.x and 16.6+ blobs on the iPhone 8 and X, iPad 5 and the first-generation iPad Pro models, without SSH ramdisk support.

powdersn0w is a third approach. It restores supported 32-bit devices to unsigned versions, and the README is careful about the wording: without is in quotes because powdersn0w uses iOS 5 or 7 blobs for the iPod touch 3 and A4 devices, but those blobs are signed for everyone to use. Other supported devices are described as true blobless. The iPhone 2G, 3G, 3GS, iPhone 4 GSM and CDMA, iPod touch 1, 2 and 3 and iPad 1 fall into the blobless downgrade category, with 2.0 as the lowest downgradable version; going to 1.x does not work. There is also a tethered path for the iPhone 4 (3,2 and 3,3), 4S, 5 and 5C, iPad 2, 3, 4 and mini 1, and iPod touch 3, 4 and 5.

That vocabulary matters. A tethered restore means the device needs help from a computer to boot, which is a different daily experience from an untethered one. The README links separate wiki pages for the iPod touch 3 and iPad 1 to iOS 6 (and iOS 7 for iPad 1) untethered, and for the iPod touch 4 to iOS 7 tethered. Read those before choosing a target version.

Installing Legacy iOS Kit on Linux and macOS

The README does not carry install steps inline. It says the tool is supported on Linux and macOS and points to the How to Use wiki page for instructions. The repository layout is small: a restore.sh script at the top level, plus bin/ and resources/ directories. That is the entry point you should expect to run.

Because the README defers to the wiki, the honest first step is to open that page and follow it for your distribution. A typical session looks like this, cloning the repository and running the script from its directory:

git clone https://github.com/LukeZGD/Legacy-iOS-Kit
cd Legacy-iOS-Kit
./restore.sh

The script presents a menu. From there you choose the operation (restore/downgrade, save SHSH blobs, jailbreak, SSH ramdisk, and so on), and the tool walks through device detection and version selection. The exact prompts are not reproduced in the README, so treat the wiki as the reference rather than guessing at flags.

One command-line detail the README does document is that two features require explicit flags: dumping and stitching baseband to an IPSW requires --disable-bbupdate, and dumping and stitching activation records to an IPSW requires --activation-records. Those are the only flags named in the README, so do not assume others exist.

macOS is listed as supported, and the README mentions sideloading IPA files on Linux and macOS. Windows is not mentioned anywhere as a supported platform. If you are on Windows, the wiki is the place to check for any workaround; the README itself offers none.

Where Legacy iOS Kit will not help you

The supported device tables are the first filter, and they exclude more than people expect. iPhone 5C and iPad mini 3 cannot use OTA downgrades at all, though they still support restoring to other versions with SHSH blobs. iPad mini 2 support for iOS 10.3.3 excludes the iPad4,6 model. iOS 6.1.3 OTA support excludes the iPad2,4.

Jailbreak coverage is version-dependent rather than universal. The README states that all 32-bit devices can be jailbroken on nearly any iOS version, available on iOS versions 3.0 to 9.3.4 with some small exceptions, and then gives per-device detail: the iPhone 2G and iPod touch 1 are limited to 3.1.3, the iPhone 3G and iPod touch 2 to 4.2.1, 4.1 and 3.1.3, the iPhone 3GS to all release versions from 3.0 to 6.1.6, and other devices to versions from 3.1.3 to 9.3.4 with exceptions the README truncates. If your device and version sit outside those ranges, the jailbreak menu will not save you.

Devices that received iOS 16 or newer are the clearest wrong-tool case. They get limited functionality such as sideloading, and SSH ramdisk is not supported. If that is your hardware, most of what makes this project interesting is unavailable.

Finally, the maintenance picture is a real constraint. The last push to the repository was on 2022-07-04, and the latest release, tagged Latest-v26.08.37, carries the same date. Nothing in the README indicates ongoing development. Restore workflows depend on Apple's servers and on third-party services such as Cydia blob servers and sep.lol; a script that has not been pushed since 2022-07-04 may still work, but you are relying on external endpoints that can change without notice.

Legacy iOS Kit against futurerestore and the Windows alternatives

The closest comparison inside the project's own documentation is futurerestore. Legacy iOS Kit uses futurerestore for one specific job: restoring iOS 14.3 to 15.x and 16.6+ SHSH blobs on the iPhone 8 and X, iPad 5 and the first-generation iPad Pro models. On those devices the SSH ramdisk is not supported, so the tool is acting as a front end to futurerestore rather than replacing it.

The difference in approach is scope. futurerestore is a single-purpose restorer built around blobs and SEP/BB compatibility. Legacy iOS Kit wraps that plus OTA downgrades, powdersn0w, DRA v6, tethered restores, jailbreaking, SSH ramdisks, blob saving from both the device and Cydia servers, hacktivation, IPA sideloading, app and data management, and miscellaneous utilities like pairing a device or exporting battery info. If your task is one of those, the wrapper saves assembling the pieces yourself. If your task is a modern 64-bit restore with blobs, futurerestore is the underlying engine either way.

On Windows, the related searches point to a question the README does not answer: is there an alternative for Windows? The README lists Linux and macOS only. The honest position is that the project does not document a Windows path, and any Windows workflow would come from the wiki or from community instructions outside the README. Do not plan a Windows-only setup around this tool without checking the wiki first.

Licence and the cost of a 2022 codebase

Legacy iOS Kit is licensed under GPL-3.0. For anyone running it locally to restore their own hardware, that is unremarkable. It matters if you intend to redistribute a modified copy or bundle the scripts into another product, because GPL-3.0 carries source-disclosure obligations for derivative works. The repository also ships a LICENSE file at the top level, which is the text to read rather than a summary; this is not legal advice, and if you are shipping something commercial you should have the licence reviewed.

Upgrade cost is the more practical question. The last push was on 2022-07-04, so there is no stream of fixes to pull. Updating means re-cloning or pulling main and accepting whatever state it is in, with no changelog beyond the release tag. On the plus side, the tool's dependencies are largely external services and the device itself, so a stale checkout is not automatically broken. On the minus side, when an endpoint changes, there is no upstream commit coming. Keep a known-good copy of the repository alongside the device-specific notes from the wiki, because the wiki pages are where the per-model caveats live.

Editorial conclusion

Legacy iOS Kit is for people with a 32-bit iPhone, iPad or iPod touch (or one of the listed 64-bit models) who have a Linux or macOS machine to run it on, and who accept that the repository has not been pushed to since 2022-07-04. It is not for Windows users, for devices that shipped with iOS 16 or newer, or for anyone who needs a supported, vendor-backed tool. Before running anything, read the How to Use and Troubleshooting wiki pages, confirm your exact model against the supported device tables, and check the wiki page for the specific operation you intend to perform, because support varies by model, target version and method.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes