hakuX Puts Original Xbox Games on Android Handhelds, and You Do Not Need a BIOS

2026-10-27 · News and analysis

Affiliate disclosure: This article contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

For years the answer to "can my Android handheld emulate the original Xbox" was no. We said so ourselves, in print, on this site. That answer is now out of date.

An emulator called hakuX shipped version 1.0.0 on 23 October 2026, then 1.1.0 the next day, then 1.2.0 three days after that. The 1.0.0 release threw out the emulator's entire core and replaced it. The 1.1.0 release added support for GPUs that are not Adreno. The 1.2.0 release brought back Xbox system link, so two handhelds on the same Wi-Fi can see each other as consoles on a LAN.

There is a more useful detail buried under all of that, and it is the reason we are writing this up rather than just adding a line to an existing page. hakuX needs no BIOS, no MCPX ROM and no hard disk image. That requirement is the single biggest reason original Xbox emulation stayed a niche hobby. It is gone, and almost nobody has noticed.

The Short Version

• Original Xbox emulation now works on Android. Not Xbox 360. If you came here looking for 360 games, see our Xbox 360 emulation on Android handhelds guide instead.
• You need only your own disc images. hakuX reads ISO and XISO files. The project's own requirements say no BIOS, no MCPX ROM and no hard disk image is needed, and that it ships no copyrighted Xbox software.
• It is not .so files. If someone told you this emulator loads .so files, that was a garbled "dot ISO". A .so is an Android system library and has nothing to do with game discs.
• Adreno is the supported tier. Qualcomm Snapdragon handhelds are what this was built for. Mali, Xclipse and PowerVR support arrived in 1.1.0 and is labelled experimental by the project itself.
• This is not xemu on Android. xemu still has no Android build at all. hakuX began as a fork of an Android xemu port, and as of 1.0.0 the shared code is essentially down to the audio.
• It is free, and it always will be. The project says so directly. If you paid for it anywhere, you were scammed.
• It is four days old in its current form. Treat it as early software that happens to work well, not as a finished emulator.

Every Setup Guide You Will Find Is Already Wrong

This is the part worth your time, because it will save you an afternoon and a bad decision.

Search for how to set up hakuX and you will find instructions telling you to create a BIOS folder and fill it with three files. An MCPX boot ROM called mcpx_1.0.bin. An Xbox flash ROM, usually a file named after a well known community BIOS. A hard disk image called xbox_hdd.qcow2. You will also be told to download an APK named app-release.apk.

All four of those instructions are out of date.

The BIOS pack sites and setup guides are describing the older app that hakuX was originally forked from, and hakuX's own releases before version 1.0.0. The 1.0.0 release reimplemented the Xbox kernel in native code. There is no longer a BIOS to load, because there is no longer a virtual machine booting a real console ROM. The asset name changed too, so a guide pointing at app-release.apk is pointing at a build from April.

Why this matters more than a stale filename: those three files are copyrighted Xbox system software. Tracking them down means going to places we will not send you, to get something you do not need. Skip all of it. Put your own disc images in a folder, point the app at the folder, and that is the setup.

We frame all emulation around playing games you already own. Dump your own discs.

How It Works

The 1.0.0 rewrite is genuinely interesting, and it explains why this runs on hardware that had no business running it.

The original Xbox ran an x86 CPU, which is the same family your laptop uses and a completely different family from the ARM chip in your handheld. hakuX runs the game's x86 code through a JIT built on FEX, which is the same class of tool as Apple's Rosetta or box64 on Linux. Our translation layers explained guide covers how that category works if you want the background.

The graphics side is the clever bit. The Xbox's GPU was the NV2A, and a game talks to it by writing a stream of commands called a push buffer. Rather than simulating the chip, hakuX reads that command stream and turns it into Vulkan calls. That is high level emulation, and it is why a phone GPU can keep up.

Audio is the Xbox's MCPX unit, which is the one significant piece still carried over from xemu, running out through Android's AAudio.

One note on how it was built, offered as a fact rather than a verdict. The project's committed developer notes reference an AI assisted review of the new core, with 65 findings tracked against commits. Several emulator projects we have covered this year have disclosed something similar. In this case the software works, and the review notes are unusually open about what is still technical debt.

Which Handhelds Actually Run It

hakuX was tuned for Adreno, which is the GPU in Qualcomm Snapdragon chips. That is the tier to be in.

There is a detail here that tells you how seriously to take this project. Its developer notes list the test devices, and two of the three are retro handhelds rather than phones. An AYN Odin 3 at 120 Hz is the main one. A Retroid Pocket 5 at 60 Hz is the second. Both are running Turnip drivers. This is being built on the hardware you actually own.

For what runs, we are quoting other people, because we have not tested this ourselves. Android Authority reported Halo 2 at full speed on a Retroid Pocket G2, and Project Gotham Racing 2 playable on both that device and the Anbernic RG 55G1. On a Retroid Pocket 5 at double resolution they listed Blood Wake, Burnout 3, Fable, MechAssault, Ninja Gaiden Black and Morrowind as running well. RetroDodo tested a Retroid Pocket Duo and a Retroid Pocket Nova and reported most of what they tried running acceptably.

The RG 55G1 result is the one that should make you sit up. That is an entry tier Snapdragon handheld, and its Adreno GPU is exactly why we noted at launch that Snapdragon buys you the widest emulator support on Android. This is that bet paying off.

The Duke Problem

Controllers are handled automatically, and the way it works is worth understanding because the Xbox pad was strange.

When you connect a controller, hakuX assigns it to the next free player slot and builds a mapping for it by reading what the device reports. It checks which axes exist to decide whether your right stick is on one pair of axes or another. It checks whether your triggers report as triggers or as brake and accelerator. It checks whether your d-pad is a hat or four buttons. You do not configure anything, and you can still remap everything afterwards.

Then there is the Duke. The original Xbox controller had two buttons modern pads do not have, called white and black. By default hakuX puts them on your L1 and R1, and moves the real triggers to L2 and R2. So your shoulder buttons are not shoulder buttons. They are the white and black buttons, and once you know that, a lot of confusing control schemes in Xbox era games suddenly make sense.

The second oddity is that the Duke's A, B, X, Y, white and black were all pressure sensitive, reporting anything from 0 to 255. Your handheld's face buttons are simple on or off switches. So a press always reports maximum pressure. For almost everything this is invisible. In the handful of games that read how hard you are pressing, usually driving games, you get full input or nothing.

One honest caveat from the code. Android can only reliably tell two identical controllers apart when they report a unique id, which generally means Bluetooth. Two identical wired pads can end up swapping their saved mappings.

High Frame Rate Mods

hakuX ships 60 and 120 fps mods for 13 games, enabled from a long press in the library.

These are not emulator settings. They are byte patches applied to the game's executable as it is read off the disc image, plus replacement disc files where needed. Each mod is keyed to one specific disc release, because a patch address that is right for one version is wrong for another. The project generates the more complex ones with scripts rather than writing them by hand.

Of the games the release notes name directly, Halo 2 gets a 60 fps mod that draws characters, vehicles and objects at the higher rate while effects stay at 30. Dead or Alive 2 gets a 120 fps mod. We are not going to guess at the rest of the list from internal title IDs, so check in the app.

Worth knowing: some of these mods uncap the frame rate honestly and some tie the game's speed to how fast your device can actually render. The descriptions in the app tell you which is which. If a race starts running in slow motion, that is the mod behaving as documented rather than a bug.

System Link Works Again

The 1.2.0 release is the one that made us raise an eyebrow.

Original Xbox multiplayer ran over system link, where you connected consoles on a LAN. hakuX now does this. Two handhelds on the same Wi-Fi find each other the way two Xboxes on a hub would. Devices that cannot see each other's broadcasts, because they are on different subnets or across a VPN, can be added by address. There is also support for XLink Kai, which tunnels system link over the internet.

Each emulated console gets its own serial number, network address and online key. If you copy your hard disk across to a second device, the app offers to generate a fresh identity, because two consoles sharing one identity cannot see each other. That is a thoughtful detail for software this young.

Nobody seems to have written about this yet, and it is the most novel thing in the release. Four player Xbox LAN play, on handhelds, over your home Wi-Fi.

It Is Free, and the Scene Has a History Here

The project's own documentation includes a blunt notice. hakuX is free and always will be. If you paid for it in any form, whether a store purchase, a subscription, an in app unlock, a premium build or an app that repackages it, you were scammed and should ask for a refund.

That warning exists for a reason. In March 2026 an unofficial paid port of xemu appeared on the Play Store, published by someone unconnected to the xemu team, charging money for free software. The xemu developers acknowledged it and said a free official Android release was coming.

Seven months later, that official Android build has not appeared. We checked xemu's releases on 27 October 2026. Every single file is a Linux AppImage, a Windows build or a macOS build. There is no APK. The Android original Xbox emulator that people are actually using is a fork that outran the promise.

There is a cautionary tale alongside it. An app called Xanite was announced as an Xbox and Xbox 360 emulator for Android and arrived as a user interface with no working emulation inside, bundling copyrighted BIOS files on the way. If you are searching for an Xbox emulator on Android and find several options, that history is why you should be careful which one you install.

We do not link to code hosting or name individual developers. Download hakuX from the project's own releases page and nowhere else.

What This Is Not

Three things to be clear about.

It is not an Xbox 360 emulator. Different console, different architecture, completely different problem. That scene on Android is covered in our Xbox 360 emulation on Android handhelds guide.

It is not xemu running on Android. The creator has said the current build is no longer a xemu fork, and the 1.0.0 notes back that up. The repository's origin still records the fork, and the audio is still xemu's, but the CPU, GPU and kernel are not.

It is not finished. Three releases in four days is a project moving fast, not a project that has settled. Some games will not boot. The experimental GPU paths are labelled experimental because they are.

The Bottom Line

If you own an Adreno powered Android handheld, you can play original Xbox games on it today, and the setup is now easier than it has ever been on any platform. No BIOS. No hard disk image. Your own disc images in a folder.

That is a real change, and it arrived quietly in the space of four days while everyone was looking at the 360.

Frequently Asked Questions

Does hakuX need a BIOS or an Xbox hard disk image?

No. Versions 1.0.0 and later reimplement the Xbox kernel in native code, so there is nothing to load. The project's requirements explicitly state that no BIOS, MCPX ROM or hard disk image is needed. Any guide telling you otherwise is describing an older build or a different app.

What file format do my games need to be in?

ISO or XISO disc images, dumped from discs you own. Archives will not work, so extract any ZIP or 7Z first. If someone told you it loads .so files, they misheard "dot ISO". A .so file is an Android system library.

Will it run on my handheld?

If it has an arm64 processor, Vulkan support and a Qualcomm Adreno GPU, you are in the supported tier. Mali, Xclipse and PowerVR gained experimental support in version 1.1.0, so they may work with rough edges. Devices without Vulkan are out.

Is this the same thing as xemu?

No. hakuX started as a fork of an Android port of xemu, but version 1.0.0 replaced the CPU emulation, the graphics and the kernel. The audio is the main piece still shared. xemu itself has no Android build, and as of 27 October 2026 it has never shipped one.

Can it emulate Xbox 360 games?

No. hakuX is an original Xbox emulator only. The 360 is a different architecture and a much harder problem, handled by entirely separate projects.

Do I have to pay for it?

No, and you should not. The project states that it is free and always will be, and that anyone who charged you for it scammed you. Get it from the project's own releases page rather than an app store listing or a mirror.

Why does my L1 button do something strange in games?

Because by default it is not a shoulder button. The original Xbox controller had extra buttons called white and black, and hakuX maps them to L1 and R1, pushing the real triggers out to L2 and R2. You can remap this in the controller settings.

Can I play multiplayer with a friend?

Locally, yes, as of version 1.2.0. Two devices on the same Wi-Fi network discover each other as consoles on a LAN would. Over the internet there is XLink Kai support, which needs a helper running on a computer on your network.

Related Reading

• Original Xbox Emulation on Handhelds in 2026
• Halo: Combat Evolved on Android Handhelds
• Xbox 360 Emulation on Android Handhelds
• How to Emulate Retro Games on Android
• Translation Layers Explained
• Best Phones for Emulation in 2026

Written 27 October 2026. Every technical claim about hakuX comes from its own documentation, release notes and source code, retrieved that day. We have not run this software and we publish no performance figures of our own. All emulation should use game files from hardware you legally own.