3 ms·
I screwed around with trying to chroot into a macOS arm image on a jailbroken iPad a month ago, but got stuck because the executables were compiled for arm64e,
by easton 5y ago
I screwed around with trying to chroot into a macOS arm image on a jailbroken iPad a month ago, but got stuck because the executables were compiled for arm64e, not arm64 (and the arch command for whatever reason was present in iPadOS but didn’t do anything). Suppose even if I had been able to get past that, maybe not a whole lot farther. I’d think that a lot of the environment differences would be taken away if you chrooted into a macOS file system rather than trying to replace iOS piece by piece, is there a reason why I’m off base?
- spijdar 5y agoYou'd get stuck at the same place as the author, at the kernel driver/module level. Chrooting to a Mac image wouldn't load the needed IOKit modules, although I'm not familiar enough with Darwin/OSX/iOS to say if you could load said modules with a jailbreak. My understanding is modern/recent jailbreaks only allow running unsigned code, not full kernel access.