Prepare MisakaX: make recovery real before Apply.

Create a current backup to a Mac or Windows computer and wait until Apple’s interface shows the new completion date and time. An encrypted local backup preserves additional categories such as Health, Activity and Keychain. Keep an iCloud backup too if you use it, but do not treat it as the computer recovery point required by this checklist.

Not for this preparation gate. iCloud Backup is useful and always encrypted, but its contents differ from a computer backup and some data is synced separately rather than stored inside the backup. We require a current computer backup as a distinct recovery option; using both methods gives you alternatives.

Use encryption if you need Health, Activity and Keychain data included. Store the backup password somewhere you can recover independently of the phone. An encrypted backup without its password cannot be restored, so this page treats a forgotten or unrecorded password as a stop condition.

Stop and do not count that existing backup as a usable recovery point. Apple says it cannot be restored without its password. On iOS 11 or later and iPadOS, Apple documents Reset All Settings as the route to remove the old backup password and create a new encrypted backup; this resets device settings, and the new password does not unlock earlier backups. Finish and verify the new backup before returning to MisakaX.

No. Apple says a computer backup contains almost all device data and settings, but excludes items such as Face ID or Touch ID settings, Apple Pay information, Apple Mail data and content already synced to iCloud. Health, Activity and Keychain require encryption. Know what your chosen method does not contain.

Wait for the backup operation to finish, then confirm that Finder, Apple Devices or iTunes shows the expected date and time for the latest local backup. Open Manage Backups or the iTunes Devices list and locate that record. A visible record proves completion was reported; it is not a guarantee that every future restore will succeed.

Do not perform a destructive restore merely as a test. Verify the completed date and time, backup location, encryption lock and known password. If Apple reports that a backup is corrupt or incompatible, stop and resolve that before MisakaX. A real restore is a separate operation with its own data and software risks.

Yes where Finder or Apple Devices offers Archive under Manage Backups. Archiving keeps the pre-change snapshot distinguishable from later automatic backups. Label its date in your preparation record and do not rename, move or edit individual files inside the backup directory.

Use Manage Backups in Finder or Apple Devices and choose Show in Finder or Show in Explorer. Apple also documents the MobileSync backup location for Mac and separate Windows locations depending on the Apple software used. Do not edit files inside the backup folder.

No. The computer backup is a broad recovery source. com.apple.MobileGestalt.plist is device-specific input used by the Misaka workflow and a separate rollback reference. Preserve the untouched original in two controlled locations; do not assume one replaces the other.

No. The file must come from the exact target device. The owner-linked guides warn against reuse, and an owner issue records a second connected iPhone receiving the wrong device’s Gestalt and entering a bootloop. Disconnect every non-target device before selecting or applying a file.

No. Connect only the target device. A reported misaka26 incident involved one phone being unplugged and Apply affecting another connected phone with the first device’s Gestalt. One device, one cable path, one original file and one preparation record is the safe boundary.

Do not proceed without authorization from the organization that manages the device. A community report describes Company Portal management failing after misaka26 and requiring a full restore. This is one incident, not a measured probability, but profile ownership and policy make a managed device a hard stop for this guide.

Look for a supervision message at the top of the main Settings page, then open Settings → General → VPN & Device Management. Inspect any installed profile and identify who controls it. If it belongs to work or school, or you are unsure, stop and ask the administrator.

Not automatically. That screen can contain different profile types. Open the entry and identify its owner and purpose. An organization-owned management profile, a supervision message or uncertainty is a stop; do not delete a profile merely to make this checklist pass.

Leave Find My on while creating the backup and preparation record. Confirm that you know the Apple Account password and can complete account verification. Turn Find My off only immediately before the documented Apply step if your chosen flow requires it, then turn it back on after the device returns and the result is verified.

Legacy guides associate the requirement with the backup-restore operation. Find My also enables Activation Lock, and Apple requires the Apple Account password to turn Find My off, erase or reactivate the device. We do not ask you to remove that protection earlier than necessary.

Stop. Do not attempt an account bypass or begin a restore-based change when you cannot manage Activation Lock. Recover account access through Apple first. Never enter your Apple Account password into this site or a third-party MisakaX page.

The owner does not publish a universal percentage or gigabyte minimum, so we do not invent one. The computer must have enough free space to complete the full backup without an error, and both devices need stable power for the planned session. Stop if either could shut down or the computer reports insufficient disk space.

Preserve the archived pre-change backup first. If you later create a post-change backup, label it separately so it cannot be mistaken for the recovery point captured before Apply. Do not let a new automatic backup silently replace your only known pre-change record.

No. Removing the desktop application is not the same as restoring the original MobileGestalt or running the documented reset path. That is why this checklist preserves the original file and a pre-change device record before the app is used.

No. A backup is a recovery option, not a prevention mechanism or recovery guarantee. Exact build compatibility, a device-matched MobileGestalt file and a single target device still matter. If you cannot tolerate downtime, data loss or an erase/restore escalation, do not proceed.

No. Current MisakaX and misaka26 workflows use a desktop application and this page requires a computer backup. An iCloud-only, IPA or browser-based route is not equivalent to the documented workflow.