Digging Into The Twilight Hack That Brought Us Wii Homebrew

With each new game console, there’s an effort to get around whatever restrictions exist to run your own software on it. In the case of the Nintendo Wii, the system was cracked through one of its most popular games — The Legend of Zelda: Twilight Princess. How this hack works was recently covered in detail by [Skawo].

The key for this ‘Twilight Hack‘ is to use a modified game save that allows you to run arbitrary code from an SD card, something which was first patched out of the Wii firmware with version 3.3. As shown in the video using the source code, the basic concept is that the name of Link’s horse in the game is changed in the save file to be longer than the allocated buffer, which leads to a buffer overflow that can be used to reach the application loader code.

Interestingly, while the horse’s name can only be 8 characters long, and the buffer is 16 bytes (due to ShiftJIS two-byte encoding), the save file loading code allocates no less than 100 bytes, for some reason. Since the code uses strcpy() instead of strncpy() (or C11’s strncpy_s()), it will happily keep copying until it finds that magic 0x00 string terminator. Basically the horse can have any name that fits within the save file’s buffer, just with no null-byte until our specially crafted payload has been copied over.

Although it took Nintendo a few months to respond to this hack, eventually it was patched out in a rather brutal fashion by simply searching for and wiping any modified save files. Naturally this didn’t stop hackers from finding ways to circumvent this save file check, which led to more counter-fixes by Nintendo, which led to more exploits, ad nauseam.

Even with firmware update 4.0 finally sunsetting the Twilight Hack, hackers would keep finding more ways to get their previous Homebrew Channel installed, not to mention so that they could keep watching DVDs on a Wii.

Continue reading “Digging Into The Twilight Hack That Brought Us Wii Homebrew”

You’ve All Seen A Hackintosh, But Have You Seen One On A Wii?

The Intel era of Apple Macs led to so-called “Hackintoshes”, more normal PCs running x86 MacOS X. Now Bryan Keller proves that a Hackintosh isn’t restricted to the x86 era, not by doing it with a modern ARM version, but by going back to PowerPC, and the Nintendo Wii.

The Wii can be thought of in hardware terms as not too far from a Mac G3 with a little less memory, having a PowerPC 750-family processor, a close relative as those in the first generation of MacOS X capable Macs. Since the roots of MacOS X are shared with its open-source equivalent Darwin, he reasons it should be possible to port just enough Darwin to the Wii to enable the closed-source OS X to run on top of it. He’s running OS X 10.0, the earliest version from 2001.

The write-up is a fascinating path through writing a bootloader and running a patched kernel that flashes the Wii LEDs, and then the process of making the Wii’s very different hardware from a Mac, accessible to the OS. It boots from an SD card and uses a framebuffer for display so perhaps it’s not as fast as you might hope, but he gets it working. Even for someone not versed in MacOS or the Wii, it’s a good write-up that makes its points accessible.

Something that makes us happy about this piece of work is its place in the greater picture, after all the Wii has found itself running classic MacOS too.

Ordering Pizza On The Nintendo Wii (Again)

The Nintendo Wii first launched in 2006, and quickly became a fixture in living rooms around the world. It offered motion-controlled bowling, some basic internet features, and a pretty decent Zelda game. On top of all that, though, you could also use it to order a pizza, as [Retro Game Attic] demonstrates.

The Wii used to organize different features of the console into “channels.” Way back in the day, you could install the Demae Channel on your Wii in Japan, which would let you order fast food from various outlets using the Demaecan service.

The Demae Channel service was discontinued in 2017. However, it has since been resurrected by WiiLink, which is a homebrew project which replicates the functionality of the original Nintendo WiiConnect 24 and Wi-Fi Connection servers. As it stands, you can load the WiiLink version of the Demae Channel (or Food Channel) on to your Wii, and use it to order pizza from your local Domino’s Pizza. It only works in the United States and Canada right now, and there are no other restaurants available, at least until further development is completed to add JustEat compatibility. It’s not entirely clear how much of the functionality was recreated from the original Demae Channel; what is clear is that plenty of custom development has been done on the WiiLink version to integrate it with modern delivery services.

What’s so exciting about this is how well it actually works. The app perfectly nails the classic Wii Channel visual style. It also seems to integrate well with the Domino’s API for digital orders, even displaying simple updates on holiday opening hours and order times. Pricing data and images of the pizzas are all available right in the app, and you can even make modifications. It might be a gimmick… but it actually works. Notably, though, the app avoids any stickiness with handling payment—thankfully, pay-on-delivery is still legitimate in the pizza world in 2026.

Will this revolutionize how you order pizza on a daily basis? Probably not. Is it one of the coolest Wii hacks we’ve seen in a while? Undeniably. Video after the break.

Continue reading “Ordering Pizza On The Nintendo Wii (Again)”

Yes, Gemini, A Wii Server Is Possible

When [Reit Tech] needed something to do with an old Nintendo Wii, he turned to Google. When the AI overview told him it could not be used as a server, he had his mission: prove that clanker wrong. It already runs Doom, so what else is there to do?

Of course should not that hard: Linux has been available on the Wii for years now. In fact there are several; he settles on “Arch, btw”, after trying Debian, Ubuntu, and even NetBSD. “Of course it runs NetBSD”– but NetBSD didn’t work with his USB network adapter, which is sadly as predictable as the hardware running NetBSD.

OK, it’s not vanilla Arch; it’s the Wii-Linux Continuation Project, based on ArchPOWER fork that compiles Arch for PPC. As the young YouTuber was surprised to discover, despite not being a PC or particularly powerful, the Wii has a PowerPC CPU. (He might be younger than the console, so we’ll give him a pass.) Wii-Linux couldn’t run the USB adapter either (appropriate apologies were offered to NetBSD), but it turns out the internal Ethernet adapter was available all along.

As a file server, python-based Copyparty worked flawlessly, but the rust-based Minecraft server he picked was not particularly usable. A little optimization would fix that, since you can serve Minecraft from an ESP32 and the Wii absolutely has more horsepower than that. Doubtless he could have loaded a web-server, and proved Google’s AI summary wrong, but the iPad-induced ADHD we all suffer from these days kicks in, so he settled for posting a screenshot of someone else’s blog, hosted on a Wii from NetBSD. So the LLM was wrong from the get-go, but the tour of “what home-brew loaded OSes still work in 2025” was certainly educational.

We could hunt that Wii-based blog down for you, but we’d be reluctant to link to it anyway: while the AI summary is wrong, and you can use the Wii as a server, that doesn’t mean it makes a good one. We’d don’t feel the need to inadvertently DDOS some poor unsuspecting shmuck’s Nintendo, so we’ll let you try and find it yourself.

Just be warned that all of this Wii hacking may not rest on the best of foundations. Continue reading “Yes, Gemini, A Wii Server Is Possible”

An Open-Source Wii U Gamepad

Although Nintendo is mostly famous for making great games, they also have an infamous reputation for being highly litigious not only for reasonable qualms like outright piracy of their games, but additionally for more gray areas like homebrew development on their platforms or posting gameplay videos online. With that sort of reputation it’s not surprising that they don’t release open-source drivers for their platforms, especially those like the Wii U with unique controllers that are difficult to emulate. This Wii U gamepad emulator seeks to bridge that gap.

The major issue with the Wii U compared to other Nintendo platforms like the SNES or GameCube is that the controller looks like a standalone console and behaves similarly as well, with its own built-in screen. Buying replacement controllers for this unusual device isn’t straightforward either; outside of Japan Nintendo did not offer an easy path for consumers to buy controllers. This software suite, called Vanilla, aims to allow other non-Nintendo hardware to bridge this gap, bringing in support for things like the Steam Deck, the Nintendo Switch, various Linux devices, or Android smartphones which all have the touch screens required for Wii U controllers. The only other hardware requirement is that the device must support 802.11n 5 GHz Wi-Fi.

Although the Wii U was somewhat of a flop commercially, it seems to be experiencing a bit of a resurgence among collectors, retro gaming enthusiasts, and homebrew gaming developers as well. Many games were incredibly well made and are still experiencing continued life on the Switch, and plenty of gamers are looking for the original experience on the Wii U instead. If you’ve somehow found yourself in the opposite position of owning of a Wii U controller but not the console, though, you can still get all the Wii U functionality back with this console modification.

Thanks to [Kat] for the tip!

RTEMS Statement Deepens Libogc License Controversy

Earlier this month we covered the brewing controversy over libogc, the community-developed C library that functions as the backbone for GameCube and Wii homebrew software. Questions about how much of the library was based on leaked information from Nintendo had been circulating for decades, but the more recent accusations that libogc included code from other open source projects without proper attribution brought the debate to a head — ultimately leading Wii Homebrew Channel developer Hector Martin to archive the popular project and use its README as a central point to collect evidence against libogc and its developers.

At the time, most of the claims had to do with code being taken from the Real-Time Executive for Multiprocessor Systems (RTEMS) project. Martin and others in the community had performed their own investigations, and found some striking similarities between the two codebases. A developer familiar with both projects went so far as to say that as much as half the code in libogc was actually lifted from RTEMS and obfuscated so as to appear as original work.

While some of these claims included compelling evidence, they were still nothing more than accusations. For their part, the libogc team denied any wrongdoing. Contributors to the project explained that any resemblance between libogc code and that of either leaked Nintendo libraries or other open source projects was merely superficial, and the unavoidable result of developing for a constrained system such as a game console.

But that all changed on May 6th, when the RTEMS team released an official statement on the subject. It turns out that they had been following the situation for some time, and had conducted their own audit of the libogc code. Their determination was that not only had RTEMS code been used without attribution, but that it appeared at least some code had also been copied verbatim from the Linux kernel — making the license dispute (and its solution) far more complex.

Continue reading “RTEMS Statement Deepens Libogc License Controversy”

Libogc Allegations Rock Wii Homebrew Community

Historically, efforts to create original games and tools, port over open source emulators, and explore a game console’s hardware and software have been generally lumped together under the banner of “homebrew.” While not the intended outcome, it’s often the case that exploring a console in this manner unlocks methods to run pirated games. For example, if a bug is found in the system’s firmware that enables a clever developer to run “Hello World”, you can bet that the next thing somebody tries to write is a loader that exploits that same bug to play a ripped commercial game.

But for those who are passionate about being able to develop software for their favorite game consoles, and the developers who create the libraries and toolchains that make that possible, the line between homebrew and piracy is a critical boundary. The general belief has always been that keeping piracy at arm’s length made it less likely that the homebrew community would draw the ire of the console manufacturers.

As such, homebrew libraries and tools are held to a particularly high standard. Homebrew can only thrive if developed transparently, and every effort must be taken to avoid tainting the code with proprietary information or code. Any deviation could be the justification a company like Nintendo or Sony needs to swoop in.

Unfortunately, there are fears that covenant has been broken in light of multiple allegations of impropriety against the developers of libogc, the C library used by nearly all homebrew software for the Wii and GameCube. From potential license violations to uncomfortable questions about the origins of the project, there’s mounting evidence that calls the viability of the library into question. Some of these allegations, if true, would effectively mean the distribution and use of the vast majority of community-developed software for both consoles is now illegal.

Continue reading “Libogc Allegations Rock Wii Homebrew Community”