Why iOS 17 on a REDMI Phone Is Suddenly Everywhere

Why it is suddenly everywhere

1. 01

   UniXNU’s own README describes a general UEFI environment and driver loader for booting iOS and macOS on non-Apple ARM64 hardware. That makes the claimed REDMI demonstration a native-boot project, not another iOS-shaped Android launcher.

2. 02

   IT Home’s October 29 report says developer Jiang Lingxiacao reached the iOS 17 desktop on a REDMI K90 Pro Max with GPU rendering, multicore CPU scheduling, a 120Hz display and USB data working.

3. 03

   The same report lists camera, power and volume buttons, cellular baseband and speakers as unavailable. A scrolling desktop has arrived; the basic functions of a telephone have not.

4. 04

   The official myron device page is more cautious than the viral clips. It lists core and driver branches, but no device repository, board files, defconfig or real-device results, so independent reproduction is not yet documented.

The timeline

1. 2020-03The reverse experiment

   Corellium’s Project Sandcastle puts Android on the iPhone 7 and 7 Plus. Its official status table still shows no GPU, audio, cellular or camera support—a useful warning that booting is only the first milestone.

2. 2026-10-19UniXNU’s public repository appears

   The initial import establishes shared build tools, ARM64 support, OS profiles and reusable components rather than a one-off image for a single handset.

3. 2026-10-24An older Xiaomi joins in

   A developer demonstrates iOS 16.5 on a Xiaomi 8, with smooth desktop animation after GPU fixes but many hardware drivers still unfinished.

4. 2026-10-25The common layers move quickly

   UniXNU commits update GPU, display and SMMU components, CPU cluster descriptions and Safari-related support. The project’s documentation expands at the same pace.

5. 2026-10-29The REDMI clip spreads

   Reports relay Jiang Lingxiacao’s iOS 17 claim on the K90 Pro Max. The visual collision of Apple software and REDMI hardware earns the nickname “Hongguo,” a REDMI-Apple pun, in Chinese.

6. 2026-10-29The evidence ledger catches up

   UniXNU’s myron page records A8XX Adreno and CPU-affinity work, but explicitly says to treat the port as in progress until a device repository and real-phone logs appear.

How a REDMI phone can boot Apple’s OS

The first thing to discard is the idea of a skin. Android launchers have imitated iOS icons for years; they change what Android draws, not what sits underneath. UniXNU is attempting something much lower in the stack. Its README compares the project to OpenCore: a UEFI environment loads the drivers a machine needs, then hands control to the operating system. Shared repositories hold build tools and ARM64 support, SoC repositories describe a chip family, and device repositories are supposed to supply board configuration and hardware integration.

That architecture matters because ARM64 is a shared instruction set, not a shared computer. An iPhone and a Qualcomm-powered REDMI can both execute ARM64 instructions while disagreeing about almost everything around the CPU: memory maps, interrupt routing, storage controllers, graphics firmware, power management and the small processors that handle radios or cameras. XNU cannot ask a generic “phone” to draw a window. It needs a description of this exact board and drivers for this exact hardware.

The myron page makes that abstraction concrete. Its public branches contain A8XX Adreno register tables and CPU-affinity matching changes, plus separate UFS driver work. Those are not cosmetic patches. They are the vocabulary the kernel needs to find the graphics hardware, schedule work across cores and reach persistent storage.

A shipping Snapdragon flagship already carries months of this integration work—the largely invisible process behind the Snapdragon first-launch race. A community port has to reconstruct parts of it after the fact, for an operating system the handset was never designed to run. UniXNU’s real contribution is to turn repeated pieces of that reconstruction into shared components.

Why 120Hz is both impressive and incomplete

A fluid desktop compresses a difficult engineering problem into a video anyone can understand. The display must present frames, the GPU must render them, touch input must arrive with the right coordinates, and the CPU scheduler must keep the interface responsive. Raising that to 120Hz makes the achievement visible rather than theoretical.

But the missing list is a map of what remains. Cellular service involves a baseband and its firmware; audio has its own codecs, amplifiers and clocks; cameras combine sensors, power rails and image processors. Even a power button is another input path that cannot be assumed to work because a touchscreen does. These systems do not arrive for free after SpringBoard appears.

History gives the same lesson in reverse. Project Sandcastle’s Android build for the iPhone 7 supported the CPU, storage, display, touch, Wi-Fi and Bluetooth on selected hardware, while its official matrix marked GPU, audio, cellular and camera as unsupported. Six years later, the UniXNU checklist looks strikingly familiar. Cross-system phone ports progress subsystem by subsystem, not through one magical compatibility switch.

The more interesting story is the evidence gap

There are now two public versions of the K90 story. In the fast version, a developer video becomes a headline, the headline becomes a “REDMI plus Apple” joke, and the phone appears to have crossed an impossible boundary. In the slower version, UniXNU’s documentation lists what another developer could actually fetch, configure and verify. On October 29, those versions had not fully met.

That gap does not prove the demonstration false. It defines what is still missing: a published device repository, board-level files, a defconfig and real-device logs tied to exact revisions. The project’s own Xiaomi Pad 6S Pro page shows what a more mature record looks like, with source pins, build commands, implementation records and hardware observations attached to individual subsystems. Applying that standard is more useful than either blindly amplifying or dismissing the REDMI clip.

Why now, then? A shared UEFI framework has replaced some one-off porting work; GPU and display components advanced rapidly in late October; and several Xiaomi demonstrations arrived in the same news window. The K90 Pro Max supplied the perfect visual: a current Android flagship apparently running its rival’s interface. The engineering is the reason to stay after the joke fades. The next milestone worth watching is not a smoother clip, but a reproducible boot and one more previously silent subsystem coming online.

Key facts

Claimed OS

iOS 17

Device codename

myron

Boot layer

UEFI + UniXNU

Working in demo

GPU, CPU, 120Hz, USB

Still absent

Cellular, camera, audio

Public status

Work in progress

What the sources are saying

Common questions

Is this just an iOS theme running on Android?

That is not the claim. UniXNU is designed to load XNU through UEFI on non-Apple ARM64 hardware, so the project concerns native boot rather than an icon pack. For this specific REDMI port, however, the public device files and logs needed for independent reproduction are still incomplete.

Can the demonstrated phone make calls and take photos?

No such complete functionality has been reported. The October 29 accounts explicitly list the cellular baseband and camera as unavailable, alongside the speakers and hardware buttons.

Why target an older iOS release?

A port is built against specific kernel interfaces, OS images and driver assumptions. Starting with a known release lets developers pin those pieces instead of chasing a moving target. Support for one iOS version does not imply support for every later version.

What would turn the viral demo into a stronger milestone?

A public device repository with board files and defconfig, exact source revisions, reproducible build commands and real-device logs. After that, working Wi-Fi, audio, buttons or cellular hardware would each provide concrete evidence of further progress.