Research / compatibility data last verified

Primary sourceBuild-specific
MisakaXX-RAY MANIFESTCheck build
GUIDE / 03

CANONICAL WORKFLOW

Every change needs an observable handoff.

Follow the sequence once, read the log, and stop on identity mismatch. A completed restore and an observed feature are deliberately separate.

Check compatibility first →Prepare and back up →Jump to revert
Identity path: BuildVersion, ProductType, ProductVersion, FirmwareVersion. Verification gate status UNTESTED. Change path: Select, Verify, Enable, Apply, Reboot.
01 / IDENTITY PATH02 / CHANGE PATH

SELECT → VERIFY → ENABLE → APPLY → REBOOT

The gate is the workflow.

Identity flows through four exact fields. Change flows through five commands. They cross only when the manifest belongs to the connected device and build.

  1. 01
    IdentifyVersion + build
  2. 02
    PrepareBackup + plist
  3. 03
    SelectMinimal flags
  4. 04
    VerifyFour fields
  5. 05
    ApplyRead the log
  6. 06
    Observe / RevertSeparate outcomes

COMPUTER BRANCH

Prepare the actual platform.

Do this before extracting, trusting, or selecting flags.

PLATFORM / 01

macOS

Use the matching macOS artifact from the chosen release. The 2.3 legacy prerelease is macOS-only.

  • Move the documented app artifact to Applications when the release instructs it.
  • If Gatekeeper blocks it, follow the repository’s xattr -c / Privacy & Security “Open Anyway” notes.
  • Connect, unlock and trust the device before verification.
macOS setup source
01

Identify build

Action
Open Settings → General → About and record the exact iOS/iPadOS version. Tap the version to reveal the build when available.
Expected signal
A version and build you can copy exactly.
Stop if
You only know “iOS 18” or a tutorial’s version.
Source / notes
Compatibility is build-specific; browser detection is intentionally not used.Evidence
02

Choose track

Action
Run the compatibility checker and compare product, channel, platform and dated claim.
Expected signal
One supported claim, a deliberate overlap choice, or an honest unknown.
Stop if
Your exact beta falls outside an explicit claim.
Source / notes
Newest system range does not mean the most stable release.Evidence
03

Back up

Action
Create a current backup and keep the original device-specific plist untouched.
Expected signal
A restorable backup plus a preserved original file.
Stop if
This is your daily driver and you cannot tolerate recovery time or data loss.
Source / notes
Both project repositories warn about bootloop risk.Evidence
04

Extract MobileGestalt

Action
Use the project-linked Shortcut to extract com.apple.MobileGestalt.plist from this exact device.
Expected signal
A device-specific plist with a known source device.
Stop if
The file came from another device, an old backup, or an untrusted upload.
Source / notes
MobileGestalt is identity-bearing input, not a generic configuration template.Evidence
Open the complete MobileGestalt extraction guide
05

Connect & trust

Action
Connect by USB, unlock the device and accept Trust prompts. Follow the platform prerequisite panel.
Expected signal
The desktop tool can see the connected, trusted device.
Stop if
Trust is not established or the platform dependency is missing.
Source / notes
Windows legacy setup requires Apple-distributed iTunes, not the Microsoft Store build.Evidence
Windows setup and detection macOS install and permissions
06

Verify match

Action
Confirm BuildVersion, ProductType, ProductVersion and FirmwareVersion match the connected device.
Expected signal
All four identity checks pass for the same device.
Stop if
Any field mismatches or the tool reports an unknown/pattern error.
Source / notes
The original Windows logic stops on identity mismatch.Evidence
07

Select minimal flags

Action
Enable one or the smallest practical set of flags after reading each capability caveat.
Expected signal
A small, documented change set you can later attribute and reverse.
Stop if
You do not understand a feature-specific side effect.
Source / notes
Minimal changes make observation and revert decisions clearer.Evidence
08

Apply

Action
Run the documented Apply command once and read the complete log.
Expected signal
A restore command completion or an actionable error—not proof of a visible feature.
Stop if
The log shows mismatch, pattern failure, interrupted restore or an unexpected setup state.
Source / notes
Repeated blind Apply is not a diagnostic method.Evidence
Open the complete Apply and outcome verification guide
09

Reboot / respring

Action
Use the release-documented reboot or respring step.
Expected signal
The device returns to a usable state and can be unlocked.
Stop if
The device loops, remains on a partial setup screen or does not return normally.
Source / notes
Some flags need a respring; others are checked only after reboot.Evidence
10

Restore Find My

Action
If the flow required disabling Find My, turn it back on after successful reboot.
Expected signal
Find My is restored to the user’s intended state.
Stop if
Account or activation state is unexpected.
Source / notes
The legacy Windows flow explicitly reminds users to restore it.Evidence
11

Observe result

Action
Check the specific setting or behavior you enabled and record what changed.
Expected signal
Observed outcome is tracked separately from restore status.
Stop if
There is no effect or an unrelated feature becomes unstable.
Source / notes
“Restore completed” and “feature observed” are different facts.Evidence
12

Revert

Action
Use only the project-documented reset/revert path and the original plist you preserved.
Expected signal
Selected flags return to the documented baseline where the tool can do so.
Stop if
The documented revert fails, the device is not usable, or recovery would require erase/restore.
Source / notes
This site does not promise a universal recovery method; seek project support.Evidence
Open the complete reset and recovery guide

AFTER APPLY

Record two statuses.

The desktop log describes the restore command. The device observation describes the feature. Neither should overwrite the other.

Restore statusCOMMAND COMPLETEDWhat the desktop command reported
Observed outcomeNOT YET OBSERVEDWhat changed on the device after reboot
STATIC EXAMPLE · NOT A LIVE DEVICE LOG
[identity] BuildVersion ........ MATCH
[identity] ProductType ......... MATCH
[identity] ProductVersion ...... MATCH
[identity] FirmwareVersion ..... MATCH
[restore]  command completed
[observe] feature outcome ..... NOT YET CHECKED