Research / compatibility data last verified

Primary sourceBuild-specific
BUILD MAP / 07

COMPATIBILITY / LEGACY MISAKAX 2.X

MisakaX 2.x supported iOS and iPadOS builds.

Choose between 2.2 and 2.3 by the exact device build and computer—not by the larger combined range in the repository README.

THE DIRECT ANSWER

There are two public 2.x routes.

MisakaX 2.2 is the Latest-labelled macOS and Windows release for the older range. MisakaX 2.3 is a newer-dated, macOS-only prerelease for 18.1 beta 5 through 18.2 beta 2. Neither release covers iOS 18.2 final or later.

PRODUCT
MisakaX 2.x only
DEVICE OS
iOS + iPadOS
RELEASES
2.2 Latest
2.3 Pre-release
VERIFIED

RELEASE FIRST

2.2 “Latest” and 2.3 “Pre-release” are both true.

GitHub’s Latest channel excludes prereleases. That is why the older 2.2 release owns the Latest badge while 2.3 has the newer date.

01 / PUBLIC ROUTELATEST

MisakaX 2.2

Published September 17, 2024

Claimed range
iOS/iPadOS 16.0–18.0 final; conflicting 18.1 beta 3/beta 4 edge
Attached apps
misakaX-2.2-macOS-edition.zip
misakaX-2.2-windows-edition.zip
Use this route when
Your device build is inside the older explicit range and your platform file exists.
Open official 2.2 release
02 / NARROW ROUTEPRE-RELEASE

MisakaX 2.3

Published November 9, 2024

Claimed range
iOS/iPadOS 18.1 beta 5–18.2 beta 2
Attached app
misakaX_macOS_v2.3.zip
No official Windows archive
Use this route when
Your exact build is inside the written range, you have macOS and you accept a prerelease.
Open official 2.3 prerelease

PRODUCTVERSION × BUILDVERSION × PLATFORM

The legacy MisakaX build matrix.

BuildVersion values mark useful boundaries; “varies” means the release does not publish a complete per-device build list. A range claim is not a measured success rate.

ProductVersionBuildVersionReleaseComputerDecision
16.0–17.xVaries by version/device2.2 LatestmacOS + WindowsInside the official 2.2 headline range. Feature and hardware checks remain separate.
18.0 beta–RCVaries by seed2.2 LatestmacOS + Windows18.0 RC was added before 2.2; the 2.2 changelog carries the line through final.
18.0 final22A33542.2 LatestmacOS + WindowsExplicitly named in the official 2.2 changelog.
18.0.122A3370Manual verificationDo not auto-routeNot named by 2.2; later issue context places it on the historical pre-patch side.
18.1 beta 1–3beta 3: 22B5034e2.2 claimmacOS + WindowsThe 2.2 headline explicitly reaches beta 3.
18.1 beta 422B5045gDocumentation conflictNo automatic routeThe same 2.2 page says beta 3 in its headline and beta 4 in its changelog.
18.1 beta 5–18.2 beta 222B5054e22C5109p22C5125e2.3 Pre-releasemacOS onlyOfficial beta-era window. Later beta seeds fit; stable/point releases are not a published build ledger.
18.2 beta 3 / RC / final and laterOutside the 2.x ceilingNo MisakaX 2.x routeNoneStop. The public 2.3 boundary ends at beta 2.

Why the table is conservative: the current repository README summarizes the combined legacy range as 16.0–18.2 beta 2. We keep each claim attached to the release that actually publishes it, its channel and its files.

THE 18.1 PATCH BOUNDARY

Dated evidence explains the contradiction.

The sequence matters. A report written before 2.3 shipped cannot cancel the later 2.3 claim, and 2.3 cannot retroactively prove 2.2 worked.

  1. 2.2 ships.

    The page publishes a beta 3 headline, a beta 4 changelog entry and both computer platforms.

  2. 18.1 beta 5 changes the boundary.

    Patch reporting and later no-effect reports describe the old SparseRestore path failing after the update.

  3. Issue #362 documents “not supported at this time.”

    That statement describes the period before a new MisakaX release claimed the patched builds.

  4. 2.3 ships as a macOS prerelease.

    Its own release note explicitly claims beta 5 through 18.2 beta 2.

CLAIMED ≠ TESTED ≠ WORKING

Read the label before the conclusion.

We use four evidence labels so a release sentence is not silently upgraded into a universal compatibility promise.

01 / RELEASE CLAIM

Maintainer wrote the range.

Strongest public routing evidence, but still not a model-by-model test matrix.

02 / METADATA FACT

The channel or file exists.

Proves release status and platform attachment—not a successful device outcome.

03 / DOCUMENTATION CONFLICT

Official statements disagree.

Shown as a stop state. We do not choose the more convenient version.

04 / OBSERVED RESULT

A user reports what happened.

Useful for diagnosing stages, but one report cannot establish a universal rate.

COMPUTER SPLIT

A supported build still needs the matching app.

The device range and computer asset are separate gates. Never use the 2.2 Windows archive as if it were 2.3.

macOS

2.2 and 2.3

Both releases publish a macOS archive. The 2.2 history names macOS 11+ and Intel support, but the short 2.3 note does not publish a complete architecture matrix.

Windows

2.2 only

2.2 publishes a Windows archive and requires non-Store desktop iTunes. 2.3 publishes no Windows app, so its device range has no official legacy Windows route.

Linux

No official 2.x app

The official MisakaX 2.x releases do not attach a Linux binary. A third-party port or mirror cannot inherit the release claim.

MISAKAX 2.X QUESTIONS

Versions, beta builds and computer support.

Direct answers for the legacy MisakaX line. Separate misaka26 and 3.0 beta claims belong in the full compatibility checker.

What iOS versions does legacy MisakaX support?

The public MisakaX 2.x releases cover different ranges. MisakaX 2.2 claims iOS and iPadOS 16.0 through 18.0 final, plus an inconsistent 18.1 beta edge. MisakaX 2.3 is a macOS-only prerelease that claims 18.1 beta 5 through 18.2 beta 2. A current README combines these into 16.0–18.2 beta 2, but that summary does not make one release cover the whole range.

Does MisakaX work on iOS 16 or iOS 17?

MisakaX 2.2 is the public Latest-labelled release whose official range starts at iOS/iPadOS 16.0, so it is the relevant legacy route for iOS 16 and 17. This is a release claim, not a promise that every feature works on every model or point release.

Does MisakaX 2.2 support iOS 18.0 final?

Yes as an official claim. The MisakaX 2.2 changelog explicitly names iOS 18.0 final as supported. Both macOS and Windows files are attached to that release.

Does MisakaX 2.2 support iOS 18.0.1?

The 2.2 release page does not explicitly name 18.0.1. A dated technical issue later referred to 18.0.1 as the historical working side of the 18.1 patch boundary, but that is not the same as a maintainer test record for every device. Treat 18.0.1 as a manual-verification case, not a clean row inherited from 18.0 final.

Does MisakaX 2.2 support iOS 18.1 beta 4?

The official page conflicts with itself: its headline stops at 18.1 beta 3, while its version 2.2 changelog says beta 4 is supported. We therefore do not present beta 4 as a confirmed automatic match. Record the exact BuildVersion and stop if you need certainty.

Does MisakaX support iOS 18.1 beta 5, 18.1 final or 18.1.1?

MisakaX 2.3 explicitly begins at 18.1 beta 5 and publishes a beta-era window through 18.2 beta 2. Later 18.1 beta seeds fit that written window, but 18.1 final and 18.1.1 are not individually named or backed by a build ledger. Our full checker does not turn those stable builds into a clean 2.3 match. The release also has only a macOS application asset.

Does MisakaX 2.3 support iOS 18.2 beta 2?

Yes as the exact upper endpoint of the official 2.3 prerelease claim. The reference BuildVersion is 22C5125e. Do not carry that result to 18.2 beta 3, RC or final.

Does MisakaX 2.x support iOS 18.2 final or later?

No public MisakaX 2.x release names 18.2 final or a later system. The 2.3 claim stops at 18.2 beta 2. Use the full compatibility checker to compare a separate product track; do not relabel a later build as beta 2.

Why is MisakaX 2.2 marked Latest when 2.3 is newer?

GitHub excludes prereleases from its normal Latest route. MisakaX 2.2 is a non-prerelease published on September 17, 2024, while the newer 2.3 release from November 9, 2024 is explicitly marked Pre-release. “Latest” describes the channel, not the newest publication date.

Can I use MisakaX 2.3 on Windows?

No official 2.3 Windows file is attached. The release has one application archive and its filename identifies macOS. The Windows file attached to 2.2 cannot be carried forward to the 2.3 compatibility range.

Can I use MisakaX 2.2 on Windows?

Yes, the official 2.2 release includes separate Windows and macOS archives. Its Windows instructions require desktop iTunes and specifically say not to use the Microsoft Store version. Platform availability still does not override the device-build boundary.

Does MisakaX 2.x support Intel Macs?

The 2.2 release history says Intel Mac support was added in version 1.9 and remained part of the later 2.2 release line. The sparse 2.3 release note does not publish an architecture matrix, so a macOS archive alone is not enough evidence to promise every Intel or Apple silicon configuration.

Does MisakaX support iPadOS and iPad?

Both official release ranges name iOS and iPadOS. That makes iPadOS part of the claimed system range, but it does not mean every iPhone-oriented flag has a useful iPad result. Match the system build first, then check the capability and hardware requirement separately.

Does a successful Apply or reboot prove my build is supported?

No. A release match, file preparation, restore completion, reboot and working feature are different checkpoints. Reports around the beta 4-to-beta 5 patch boundary include clean reboots with no applied change. Verify the final behavior instead of treating a success message as the result.

Does a supported MisakaX version mean every feature is supported?

No. The release range only routes the tool. Individual features can have narrower version, model, hardware or region requirements. For example, the current README gives its TrollStore Installer a much narrower range than the overall MisakaX utility. Check the capability after the release match.

Does MisakaX 2.x support iOS 15?

The overall public MisakaX 2.2 release range begins at iOS/iPadOS 16.0. A narrower feature line mentions the TrollStore Installer on some iOS 15 builds, but that does not establish general MisakaX 2.x compatibility on iOS 15. Do not expand a feature-specific statement into a tool-wide range.

Can I use MisakaX 2.x without a Mac or Windows PC?

Not through the official 2.x release workflow. MisakaX 2.2 publishes macOS and Windows desktop applications, and 2.3 publishes a macOS application. Extracting the input with an iPhone Shortcut does not replace the computer-side import, Apply and verification steps.

Should I downgrade iOS to use MisakaX 2.x?

This page does not recommend downgrading. Old signing windows and historical rollback advice are not current instructions, and a downgrade can erase data or fail entirely. Preserve your exact version and use a compatible current route only when the evidence is explicit.

Is legacy MisakaX the same as misaka26 or MisakaX 3.0 beta?

No. This page covers only the public MisakaX 2.2 and 2.3 releases. misaka26 and MisakaX 3.0 beta are separate product tracks with different channels, mechanisms and compatibility claims. Their ranges cannot be transferred to MisakaX 2.x.

PRIMARY RECORDS

Keep the decision attached to its source.

We verified the public state on . If a release page changes, compare the dated channel, range and attached filename before changing your route.

01

Missing the exact fields?

Find ProductVersion and BuildVersion
02

Already matched?

Follow the safe workflow
03

Different product name?

Compare MisakaX and misaka26