1. iOS on Android Phones: What Has Been Shown
Hobbyists are now booting Apple's iOS 16 on Android phones, and demonstration videos of the feat have been spreading on X. A clip of iOS running on a Redmi Note 12, posted on October 18, has passed 2 million views, while a separate developer has shared a build running on a Nothing 3a. The results are rough, but they suggest iOS may no longer be bound to Apple's own devices.
Until recently, running Apple's mobile operating system on non-Apple hardware was treated as a practical impossibility for outside developers. The latest demonstrations do not amount to a usable phone, and several of them lack independent confirmation. Even so, they are drawing attention because the direction of travel has been, for years, almost entirely one way: people had put Android on iPhones, but not the reverse.
The practical question for readers is how much of this is demonstrated and how much is promised. Two public builds exist in some form, a third is described by its authors as nearly finished, and the viral videos show only a few seconds of each device in operation. What follows sorts the verifiable details from the claims that still rest on a video clip and a social media post.
2. Why Does It Matter That iOS Is Tied to Apple Hardware?
iOS is designed to run only on Apple hardware, which means that choosing a phone has traditionally meant choosing its software as well. A buyer who prefers Apple's operating system must purchase an iPhone, and a buyer who wants a less expensive or differently designed handset has had to accept Android or another system. That coupling is central to how Apple sells its products.
If the barrier were to break, the consequences would extend beyond hobbyist curiosity. Cheap or old phones could, in principle, run software they were never sold with. A person holding an aging Android device might one day be able to try an Apple interface on it, and developers could study how the software behaves on different chips and components.
For now, that remains a hypothetical. The projects described so far are experiments, and their authors are open about the gaps. The significance lies in what the demonstrations imply rather than in what they currently deliver.
Apple's control over the pairing also shapes the wider market. Because the software is available only on its own phones, the company can set the pace of updates, decide which chips and components support each release, and keep the whole experience consistent. Any development that loosens that connection, even as a hobby project, touches the foundation of that strategy, which is why a clip of a mid-range Android handset showing an Apple lock screen travels so quickly.
3. Has Anyone Done the Reverse Before?
Running a rival operating system on an iPhone has precedent. A project called iDroid let early iPhones boot Android in April 2010. About a decade later, Corellium's Project Sandcastle put Android 10 on iPhones built around Apple's A10 chip.
Those efforts showed that Apple's phones could be coaxed into running software from the other camp. The reverse direction has proved much harder. As the observation circulating alongside the new videos puts it, nobody had been able to make it work the other way around until now.
The asymmetry has a plausible explanation. Android is built to accommodate a wide variety of devices from many manufacturers, whereas iOS was written for a narrow, tightly controlled set of chips and components. Moving Apple's software onto a different processor and driver landscape means supplying the pieces that Apple's own hardware normally provides.
Each side of the divide also carries different expectations about openness. Android's code is largely public and routinely adapted by hardware makers, so loading it onto a foreign device is a question of compatibility. Apple's system, in contrast, assumes the presence of particular processors, a particular boot process and a closed set of drivers, and a developer who wants to run it elsewhere must recreate those assumptions piece by piece.
4. Which Projects Are Involved?
The closest publicly available code is a project called ios-sweet, hosted on GitHub and built for the Redmi Note 10 Pro. It pairs Apple's publicly released XNU kernel, patched to run on the Snapdragon 732G processor, with unmodified iOS 16.7.16 files taken from an iPhone X. In other words, the kernel is adapted to the Android phone's chip, while the operating-system files layered on top come directly from Apple's own hardware.
Some background helps explain why the kernel is the first hurdle. A kernel is the core of an operating system, the layer that manages the processor, memory and connected hardware and that every application depends on. XNU is the kernel at the center of Apple's platforms, and because Apple has released its source, developers can adapt it to a new processor. Other layers, including the drivers that handle wireless radios, audio and graphics, are far harder to reproduce, which is why those functions are the ones missing in the working builds.
The project's readme describes the work as an experimental bring-up and not a usable phone operating system. The Redmi Note 10 Pro reaches the lock screen, the home screen, Control Center and Settings, and touch input and the physical buttons respond. Wi-Fi, Bluetooth, mobile data, audio and the camera do not work, and the gesture used to exit an app does nothing.
A separate group calling itself OOSexGang says its HackiOS project runs iOS 16.5 on a Poco X5 Pro, using a custom UEFI and the XNU kernel. The person sharing that demonstration notes that no source code is public and that the claim has not been independently verified. On October 16, a developer who posts as Md Ismail Šojal described HackiOS as a full rewrite of code intended to run actual iOS on Android hardware, saying that the pieces are in the final polishing stage, and added that the project would be free and open, with no paywalls.
A newer clip posted on October 19 shows Safari on the device downloading an Android application package and then failing to run it. That outcome is ordinary iOS behavior, since Apple's system does not execute Android apps, and it serves mainly as a demonstration that the browser and network stack are functioning in that particular build.
5. How Well Does iOS Actually Run on These Phones?
The limitations are considerable. On the Redmi Note 10 Pro, iOS reaches the home screen, but Wi-Fi, mobile data and audio do not work. With no graphics driver available, the processor draws the screen in software, which yields roughly 20 to 30 frames per second. The first boot takes four to five minutes while the Apple logo remains on display.
Those figures describe a proof of concept, not a daily driver. A phone without connectivity, sound or a working camera cannot perform the basic functions that people expect from a handset. The developers present the work as a milestone along a longer path, with each missing driver representing a further piece of engineering.
There are also practical warnings. Installing the software wipes the phone's Android user data and largely disables its security protections. The developers advise against keeping anything personal on a device used this way.
Frame rate gives a sense of the gap. Smooth, modern phone interfaces typically aim for 60 frames per second, and a display drawn by the main processor without a graphics driver at 20 to 30 frames per second falls well short of that. The slow first boot points the same way, indicating that the system is still working without the optimizations and drivers that a finished port would include.
6. What Is Driving the Sudden Progress?
The wave of demonstrations is being linked to artificial intelligence tools and faster code shipping. Calif.io jailbroke an iPhone 18 Pro on stage at the Hexacon conference in Paris, with root access surviving a reboot. Jailbreaking removes the restrictions Apple places on its devices, giving users deeper control than the manufacturer normally allows.
A free toolkit called REA, short for Reverse Engineer Anything, lets AI coding assistants analyze software. Among the examples cited was a developer's demonstration of the game GTA V running on iOS. Tools of that kind shorten the time needed to understand complex code, which is typically the slowest part of porting software to unfamiliar hardware.
None of this proves that AI tools produced the Android demonstrations, and the article reporting on them frames the connection as a trend rather than a confirmed cause. Still, the timing of several reverse-engineering feats within a short period fits the idea that the cost of this kind of research is falling.
Reverse engineering means studying a finished program to work out how it operates, often without access to its source code. It involves reading machine instructions, tracing how components communicate and testing assumptions repeatedly. Tools that speed up the reading and explaining of unfamiliar code can compress what might once have been months of effort, which is why the combination of such tools with a motivated community of hobbyists draws attention.
7. Should Anyone Install It, and What Comes Next?
Given the loss of connectivity, the removal of security protections and the erasure of existing data, the builds are suited only to developers and enthusiasts who are prepared to treat a phone as an experimental board. They are not meant for anyone who relies on a device for communication, banking or storing personal information.
What to watch is whether the promised releases appear and whether independent developers can reproduce the claims that currently rest on videos. The ios-sweet code is available for inspection, while the HackiOS project has not published its source. If its authors follow through on their stated plan to release it openly, outside engineers will be able to test the claims directly.
The longer-term question is whether missing drivers for wireless, audio and graphics can be written. Each one that works would move these experiments closer to a usable system, and each would sharpen the question of how firmly Apple's software remains tied to Apple's hardware.
Readers should also keep the reliability of the evidence in mind. A video shows that a screen appeared, not that a system is stable, complete or reproducible by others. Until independent developers can build the projects from public code and report matching results, claims such as the Poco X5 Pro demonstration should be read as unconfirmed, regardless of how many views the footage collects.