ANDROID 17 IS RUNNING ON AN IPHONE. It works because of a flaw burned into the chip that Apple can't patch — not with any update, ever. And part of the port was written by AI, which is now the real argument.
THERE IS AN IPHONE RUNNING ANDROID 17 RIGHT NOW, AND NO SOFTWARE UPDATE WILL EVER STOP IT. Not a theme, not a launcher, not a skin — the Android kernel booting on Apple hardware, because the flaw that allows it is burned into the chip at the factory and cannot be changed.
THE DOOR
Every iPhone starts the same way: the first code that runs lives in the boot ROM inside the chip itself, burned in at manufacture. That code checks that the next stage is signed by Apple, and that stage checks the next, all the way up to iOS. It's a chain of trust, and the first link is physical.
In September 2019, a researcher going by axi0mX published checkm8 — a bug in that boot ROM affecting every chip from the A5 through the A11, which is the iPhone 4S through the iPhone X.
Because the boot ROM is read-only, there is no software update that can fix it. Apple patched it in later chips. The old ones stay open forever. The limits are real — it needs a cable and a computer, and it doesn't survive a restart — but it means the owner of that phone, not Apple, decides what it boots.
THE CHAIN
Getting Android onto an iPhone takes four steps, and each one is somebody else's project:
checkm8 opens the door. PongoOS, from the checkra1n jailbreak team, takes over. m1n1 — a bootloader built by the Asahi Linux team for Apple's Mac chips — starts a kernel. And Halium-based Linux teaches that kernel to drive an iPhone's hardware. Android runs on top.
The project doing it now is Snowcastle, and its repository is public: LineageOS/android_device_apple_snowcastle, created in March 2026, maintained by a developer who goes by Yumi Yukimura. The first public build was Android 16 on the iPhone 8, 8 Plus and X. By September it was Android 17, and the iPhone 7 family and two iPads had joined.
THE HISTORY
None of this is new, which is the part people forget.
In 2008, a hacker called Planetbeing got the Linux kernel running on the original iPhone. By April 2010, Android booted on it, dual-booting next to Apple's software. Two of the people involved — David Wang and Chris Wade — later co-founded Corellium, a company Apple took to court.
In March 2020, Corellium released Project Sandcastle: Android 10 on an iPhone 7. No graphics acceleration, no audio, no calls, no camera. It booted, and then it sat there for six years without another update.
THE LAWSUIT
Apple sued Corellium in August 2019 — not over Android, but over its business of running virtual iPhones for security researchers. In December 2020 a federal judge ruled that was fair use. In 2023 the Eleventh Circuit agreed, describing iOS as functional operating software outside the core of copyright. The remaining claims settled quietly in December 2023.
That ruling matters here: it's why a research tool that runs iOS can exist at all — and why the descendants of Sandcastle can keep going.
WHAT ACTUALLY WORKS
The honest list, from the project's own support notes:
On every supported device: the display, the buttons, USB and storage.
Only on the iPhone 7 Plus and the 2019 iPod touch: Wi-Fi, Bluetooth and the battery.
No: camera, speakers, or graphics acceleration — every pixel is drawn by the processor, and under heavy load the phone can shut itself off.
No calls or mobile data.
And the detail that tells you how early this is: Linux can't write to Apple's storage format yet, so apps and data live in memory. Restart the phone and they're gone.
Two tricks make it work without breaking anything. Android doesn't get its own partition — its files sit in a folder inside the iPhone's storage, next to iOS, and get mounted at boot. And Snowcastle ships none of Apple's firmware: at boot it opens the copy of iOS still on the phone and pulls the Wi-Fi, Bluetooth, touch and power firmware out of it. The rule is written into the project — do not share builds with Apple's files inside.
THE AI QUESTION
Here's where it stops being a gadget story.
In October, the developer wrote on the project's GitHub page that they don't fully understand some of the code — mostly the HAL layer — and depend on AI coding agents. On November 8, that paragraph was deleted, along with a section about leaving LineageOS. The commit message: remove no longer wanted sections. It's still in the public history.
The AI involvement isn't hidden. Since June, more than 300 of their changes to LineageOS have carried labels naming the AI tools that helped write them — models from OpenAI, Anthropic and Alibaba. The latest Snowcastle commit lists Claude as a co-author.
And that's where the community split. LineageOS's rule is simple: anyone submitting code must be able to understand and explain it. The m1n1 bootloader Snowcastle relies on carries a rule inherited from Asahi Linux — no AI or LLM tools, for legal reasons. The README notes the main Halium team won't accept a Wi-Fi and Bluetooth implementation that came out of an AI-assisted fork.
The developer's own account of why is the most interesting sentence in the whole story: a hand-written driver that was ugly and didn't work on some hardware got almost no attention for months. A vibe-coded one that looked clean and worked on everything they tested got reviewers combing through it and proposing rules about AI-written code.
So the real question the project raises isn't whether AI can write a driver. It's the one the developer can't answer for you: if an AI writes the parts you don't understand, is it still your port?
THE NEXT DOOR
checkm8 stops at the A11. But in July a separate project went public describing itself as a boot ROM exploit for Apple's A12 and A13 — the iPhone XS and iPhone 11 generations — and it needs a small Raspberry Pi board between the cable and the phone, because a normal computer's USB port can't send what it requires.
If that holds up, the list of iPhones Apple can never fully patch gets longer.
SPLASH’S READ
You bought the phone. The question this story asks is whether you bought the right to decide what runs on it.
On most devices the answer is no, and it's enforced by software — a signature check that can be updated. On these older iPhones the answer is yes, and it's enforced by physics: a read-only chip with a bug nobody can reach back and fix. Apple's control there was never physical. It was contractual, and the contract lost to a cable.
The AI argument underneath it is the part I'd watch. Every open-source project is about to have this fight, and the shape is already visible: the gate isn't the code, it's whether a human can stand behind it. LineageOS's rule — you must be able to explain what you submitted — is going to be the model, because the alternative is a codebase nobody can maintain.
And the funniest detail is the one that says everything about how we build now: nobody looked at the ugly hand-written driver for months, and everybody combed through the clean one a machine wrote. We're not judging code by whether it works anymore. We're judging it by whether we can tell.
WHAT WE COULDN’T CONFIRM
The developer's identity. They go by Yumi Yukimura and that's how the project identifies them; we're not speculating past that.
Whether the A12/A13 exploit is real. It's described as public since July, but we haven't seen independent confirmation that it works, and it requires extra hardware.
What Apple will do about any of this. The boot ROM flaw affects chips Apple stopped shipping years ago. There's no patch to issue and no statement to get.
Whether Snowcastle ships a usable daily build. It doesn't — no camera, no speakers, no calling, no persistence across a restart, and Google's apps don't install yet.