Will it work on my phone?
About ten phones and tablets run iOS or iPadOS today (see Projects). Every other device needs a port. How much work that is depends mostly on the chip inside, so this page groups phones by chip family instead of listing models.
The basics your phone needs
- An unlockable bootloader that supports
fastboot boot(starting an image from the PC without flashing it). Xiaomi, Poco, OnePlus, Pixel and most Motorola phones can do this. Samsung phones use Odin instead of fastboot, so the loader has to be flashed to the BOOT partition instead (the Galaxy S7 port does this). Huawei bootloaders can't be unlocked anymore. LG shut down its official unlock service at the end of 2021, so an LG phone (like the V60 in the community ports) only works if it's already unlocked or has an unofficial unlock method. - Ideally a Snapdragon chip. Most working ports are on Qualcomm hardware, but a Pixel 6a (Tensor) and a Galaxy S7 (Exynos) port also boot iOS.
- Enough RAM. The iPhone X has 3 GB, but iOS 16 gets by with less: the Pixel (2016) port runs on 2 GB. HackiOS also loads the whole system image (about 2.5 GB) into RAM, so 6 GB or more is the safe target there.
- Storage the project can read. Most projects keep iOS on the phone's flash and have drivers for UFS, the storage in most mid-range and high-end phones. eMMC phones (common in budget models) need a new storage driver first. HackiOS can run entirely from RAM, so storage matters less for a first boot there.
- A screen the bootloader leaves on. Every project starts by drawing into the image buffer the bootloader or UEFI uses for its logo. Almost all Android phones leave the screen on like this.
Which project to start from
Pick the project or community port whose device is closest to yours. Same chip is best, same chip family is next. A port that's already on a similar chip often saves more work than the original project, so check the community ports too.
- HackiOS if your phone has a Snapdragon 778G or a close relative, if your phone already has a Mu-Silicium (Windows on ARM) UEFI port, or if you want GPU, Wi-Fi and sound to build on.
- ios-sweet if your phone has a Snapdragon 730/732G, or if you'd rather start with a smaller codebase that boots with a simple shim and no UEFI. Most community ports started here, so there's probably one with a chip close to yours.
- UniXNU if you have a tablet and want iPadOS, or a recent high-end Snapdragon.
Chip families
| Chip | Chance | What a port involves |
|---|---|---|
| Snapdragon 778G / 778G+ / 782G (SM7325) e.g. POCO X5 Pro 5G, Xiaomi 11 Lite 5G NE, Galaxy A52s |
Best (HackiOS) | Same chip as the HackiOS phone. You need a UEFI port for your phone (copy the closest Mu-Silicium device of the same chip), then change the board details: screen, touch controller, buttons. GPU, Wi-Fi and sound use the same Qualcomm subsystems with different addresses and firmware. Samsung models still have the Odin problem. |
| Snapdragon 730 / 730G / 732G (SM7150) e.g. Poco X3 NFC, Poco X3, Redmi Note 10 Pro Max, Mi 9T, Mi Note 10, Pixel 4a |
Best (ios-sweet) | Same chip as the ios-sweet phone, so the kernel side mostly works as is. You change the board details: screen size, touch controller, button wiring, memory layout. If the phone uses a different touch chip, that driver needs a new protocol. |
| Snapdragon from 2018 on 845, 855, 865, 870, 888, 8 Gen 1/2/3, 7xx, 690, 750G and most newer chips with UFS |
Good | Same building blocks as the 732G and 778G phones: the same interrupt controller type, the same kind of power controller (RPMh) and the same serial engines for I²C. Mostly the addresses differ, so a port means updating a few config values (memory map, storage, screen) and pointing the touch and button drivers at your phone's hardware. The Pixel 4 (855), LG V60 (865) and POCO M8 (6 Gen 3) ports show it works. The newest chips (8 Gen 1 and later) change a few blocks, like a newer PMIC bus, and need more work. |
| Older or budget Snapdragon 820/821, 835, 625, 636, 660, and budget chips with older cores like the 662, 665, 680, 685 |
Possible | These use an older power controller (RPM instead of RPMh), so powering the touch chip needs new code. The oldest ones (820/821, 835 and similar) also have an older I²C block, so their touch drivers have to be rewritten too. Many of them have eMMC storage. Their CPU cores are an older ARM generation (ARMv8.0) than the iPhone X's chip. The Redmi Note 12 (685) port shows iOS 16 still runs: the kernel has to be built for the older cores, and because the small cores can't use 16 KB memory pages, it uses a 4 KB-page kernel to run all eight. The Redmi Note 12 and the first Google Pixel (821, using the iPhone 8 firmware) go furthest: GPU drawing, Wi-Fi and charging all work on both. |
| Google Tensor (Pixel 6 and later) | Possible | The bootloader supports fastboot boot, and the Pixel 6a port shows ios-sweet's approach carries over. But the chip is Google's own design, built on Samsung's platform up to Tensor G4, and shares almost nothing with Snapdragon, so the storage setup, memory map and every driver are new. |
| MediaTek (Helio, Dimensity) | Probably not | Different hardware from the ground up, bootloaders that are often hard to unlock, and vendor kernel sources that are harder to learn from. It's not impossible, but it would be a new project rather than a port. |
| Samsung Exynos | Hard | Different hardware from Snapdragon, so every driver is new, and there's no fastboot boot: the loader goes into the BOOT partition. The Galaxy S7 (Exynos 8890) port reaches the iOS setup screen this way, so it can be done. |
| Unisoc, Kirin | Probably not | Same story as MediaTek, and Huawei bootloaders can't be unlocked. |
Quick answers
Can I try it without flashing anything?
With HackiOS, yes. It starts with fastboot boot, which doesn't touch the boot partitions, and keeps iOS in RAM, so a reboot brings Android back. It also runs in QEMU on a Linux PC with no phone at all. ios-sweet also boots with fastboot boot, but its iOS system lives in the userdata partition, so you have to flash that, and Android's data is erased.
Can I run iPadOS on my Android tablet?
Yes, it's been done. UniXNU runs iPadOS 17 on the Xiaomi Pad 6S Pro (Snapdragon 8 Gen 2), using the firmware of the 2017 iPad Pro. See Projects.
Can it run iOS 17, 18 or newer?
Not with iPhone firmware. Every iPhone that runs iOS 17 or newer is built for pointer authentication (arm64e), and most mid-range chips, like the Snapdragon 732G and 778G, don't have it. So for iPhone firmware the path stops at iOS 16 on the iPhone X and iPhone 8. Newer chips that do have pointer authentication (Snapdragon 8 Gen 1 and later, for example) could in theory run newer iPhone firmware, but no project does that yet. (Why an iPhone X?)
iPads are different. The 2017 iPad Pro (up to iPadOS 17) and the 7th-generation iPad (up to iPadOS 18) use the plain arm64 build. That's how UniXNU runs iPadOS 17.
How do I find out which chip I have?
Search your model on GSMArena and look at the "Chipset" line, or install an app like CPU-Z. The storage type (UFS or eMMC) is listed there too.