Previous iPhones (A7 through A11) allowed more flexibility in loading custom, "patcher" Ramdisks. With the A12, Apple enforced PAC extensively in the kernel and iBoot. A custom Ramdisk built for an iPhone X will simply on an iPhone XR because the cryptographic signatures in the pointers won’t match.
Why would a professional or hobbyist want to load a Ramdisk on an iPhone XR? iphone xr ramdisk
Prior to the A12 (on devices like the iPhone 7 and 8), the primary exploitation method was "limera1n" or "checkm8" at a lower level that allowed for easier permanent modifications (tethered jailbreaks). However, the iPhone XR is not vulnerable to the standard checkm8 exploit in the same way older devices are because it lacks the hardware flaw present in the A5-A11 chips. Previous iPhones (A7 through A11) allowed more flexibility
These are modified versions of the official Ramdisk designed to grant shell access (SSH) or allow file system mounting without passcode entry. Historically, tools like redsn0w or idevicerestore used custom Ramdisks. For the iPhone XR, modern tools like (for checkm8 devices) do not work because the XR is not vulnerable to checkm8. Instead, tools like SSH Ramdisk for A12 devices rely on a different exploit chain (e.g., blackbird or kfd ). Why would a professional or hobbyist want to