Run full iOS 16.5 firmware on Android Devices

Original Article ↗ Hacker News Discussion ↗

A new project shows iOS 16.5 firmware booting on certain Android phones and in QEMU, using AI-assisted reverse engineering to adapt Apple’s XNU kernel to non-Apple hardware. Commenters are split on its practical value: core features like cellular, Bluetooth, charging, Apple ID, and App Store access don’t yet work, limiting it to a research bench rather than a daily-driver OS. Still, many see it as a significant proof of concept with implications for jailbreaking, device ownership, potential iPhone clones, and the broader impact of AI on closed ecosystems.

Overall reaction

  • Many find the project “mad” and impressive, akin to Hackintosh for phones.
  • Others question its practical value, calling it a cool but mostly research/hobby effort, “on par with cutting off my leg before playing soccer.”

Technical state and limitations

  • Runs iOS 16.5 on selected Android devices and QEMU; later iOS versions are believed harder due to newer security (e.g., Secure Page Table Monitor / Trusted Execution Monitor).
  • Current major gaps:
    • No App Store, Apple ID, iCloud, or other iServices, partly due to missing Secure Enclave / FairPlay support.
    • Cellular and Bluetooth do not work yet.
    • Charging under the custom kernel does not work; the phone only discharges.
  • It is framed as a “research bench,” not a daily-driver ROM: sessions are time-limited and return logs to a loader.
  • Some are surprised camera works, noting other alt-OS projects often fail there.

Use cases and motivations

  • Research/jailbreaking value: full kernel control, fully jailbroken-style iOS not possible on locked iPhones.
  • Curiosity / hacking culture: similar motivation to Hackintosh and postmarketOS.
  • Niche desires:
    • Running iOS-only music production apps or other iOS-exclusive software on cheaper Android tablets/phones.
    • Blue iMessage bubbles are mentioned, but others doubt iMessage will work due to device attestation.
  • Several argue they’d rather see Android or Linux on Apple hardware instead.

Security, legality, and clones

  • Concerns about:
    • Security hardening making future ports much harder.
    • Malware/spyware risk in trendy AI-assisted firmware projects that spread quickly.
  • Debate about potential for realistic iPhone clones; some think this will boost convincing fakes, others note Apple’s secure boot chain and Secure Enclave make true replicas extremely difficult.
  • Legal risks (DMCA, trademark/counterfeit law) are brought up, with comparisons to fake watches and prior Apple IP battles.

AI’s role and future prospects

  • Multiple commenters note that AI assistants are already being used to:
    • Pilot phones over adb/fastboot and iterate kernels.
    • Reverse-engineer and customize firmware (including non-phone devices like Garmin).
  • Some expect agents to rapidly extend device support and usability in 6–12 months; others doubt portability and stability, given iOS’s tight coupling to specific hardware.