Frequently Asked Questions


What is Wiiubru?

“Wiiubru” is an online community centered around Wii U homebrew discussions and development.

Recently, this also includes the hosting of homebrew, tools, and services that try to make homebrew more accessible to end users.

Such services/tools include:

  • /appstore – Hosting of various homebrew ELF/RPX files for use with Homebrew Launcher
  • /go – Quick way to download, run, and install homebrew on any stock Wii U
  • /mocha – Quick-start into the Mocha CFW for users who don’t have Haxchi installed
  • /x – Legacy launching of sd:/wiiu/apps/homebrew_launcher/homebrew_launcher.elf

Various community resources are also provided to help troubleshoot and discuss homebrew installation and development.

Such resources include:

  • /forum – Discuss homebrew (including occasionally exploit development) on a public forum
  • /irc – Speak directly with others users who use/develop/support Wii U Homebrew
  • /guide – Brief walkthrough of various approaches to run homebrew on console
  • /rip – Frequently updated list of users who have reported bricking their console

Who is on “Team Wiiubru”?

“Wiiubru.com” was originally started by Pwsincd as a .mp4 exploit hosting service for userland homebrew, before the Kernel Exploit was released. It has since grown into focusing on providing the services/resources above. “We” are not a console hacking team, and there is no major distinction made between the “Admins” of Wiiubru and normal everyday users who show up out of the wood work.

As a result of this, the rules behind who is allowed to join and speak in chat/forums is fairly permissive. There are no permanent bans, and users are not kicked for speaking keywords.

What’s some cool Wii U homebrew?

Some favorites include HID-to-VPAD, Flappy Bird, Haxchi, or any of the emulators!

I would like to get into developing Wii U homebrew, where do I start?

You can start by consulting the homebrew development guide on Wiiubrew.org. If you encounter troubles, you can stop by the Wiiubru chat to ask for assistance.

Another great way to get started is to look at the source of your favorite homebrew and play with it or reach out to its creator for more information.

If you’re not a team, why are you “releasing” things, like the fw.img Booter?

If I could go back in time and remove “Team Wiiubru” from being associated with the fw.img Booter, I would. That IOSU exploit implementation occured publicly in this thread with the collective knowledge of many users spanning around 7 months in time. This was particularly accelerated by an anonymous user posting the high-level overview of uhshax to wiiubrew.org.

Once the exploit was working, several people were taking the public work and using it with Smea’s public iosuhax to try to boot into rednand. This is a potentially dangerous operation to be advising users to blindly run and use. Since all of the work was done under the public eye, there was no way to prevent people from talking about it and trying it. As a result, this gbatemp post was made, alongside the Wiiubru Twitter. Here “Team Wiiubru” was presented as a cohesive team to try to dissuade users from blindly trying things until they were ready. The “Team Wiiubru” moniker has since been removed from CFW Booter.

Why wasn’t the IOSU exploit work done in private?

Up until exploit hacking started being discussed, Wiiubru was only focused on being a place where people who support Wii U homebrew could talk. This includes the hosting and development of homebrew. The general philosophy and vibe of the chat/forums was that sharing resources and working in the open was the best way to be as a community who cares about making the most of their device.

With the permissive rules on chat/forums, it’s not like any of the Wiiubru Admins would be able to have made the work private unless those people involved decided to make it private. However, at the time, it still seemed like doing it out in the open was the best way to get things done. This isn’t necessarily wrong, given that it allowed anyone to take part in working on the exploit. One of the primary reasons Datalogger and Pwsincd set up the forums in the first place was to combat some of the privateness/hostility that had teased the scene up until then (Hykem, 5.5.1 kexploit, etc).

Despite that, it’s clear that those who saw the ensuing chaos that went down after the first public IOSU exploit implementation have a little more appreciation for the dangerous line private groups walk between code sharing and pressure behind finishing/releasing their work. In the case of the Wii U, it was one teasing group after another, which is probably why the public work even was able to get as far as it got.

Post-IOSU-exploit, Wiiubru continues to focus on running, developing, and installing Homebrew, and making that easier for the average user to be able to get more out of the device that they own. Some users within the community may also still be focused on exploit development, but it is unfair to categorize that as the “primary goal” of any Wiiubru-provided resources.

If Wiiubru believes in openness, why have Wiiubru at all, when “official” channels such as #wiiudev and wiiubrew.org exist?

Those communities do exist, continue to exist, and have their place. But the attitude of the moderators and specifically how they treat other users tends to be less laid back and more professional. This is a good thing, but it tends to the chat being more silent than not, pages involving certain resources (title installation, backup loading) being censored, or users being automatically kicked for mentioning certain keywords.

It’s important to remember that while such communities ostensibly support Homebrew usage and development, by definition there’s no “official” homebrew community. It seems natural that smaller communities should arise and have different attitudes, where certain people may prefer one style to the other. It’s also important to note that it’s not like joining communities is mutually exclusive.

Is Switchbru.com a joke?

No! Switchbru is not a joke. There simply isn’t any Switch homebrew available yet. Currently the only service that it provides is SwitchBru DNS for Internet browsing, although Reswitched DNS is better if you are interested in update blocking.

Hopefully in the near future with advancements from the scene, you will see Switch homebrew resources popping up on Switchbru

You guys don’t really think you can hack the Switch do you?

“Us guys” have not claimed that, nor should it appear that way. The primary purpose of Switchbru is not, and given the current progress of the Reswitched team, shouldn’t ever be exploiting the Switch. The exact role that Switchbru plays will likely change in the future, but once userland code exec is ready it’s safe to say that the chat and forums will be a place to discuss Switch homebrew developing and early homebrew game usage, such as Space Game or C@ve type games. It’s easy to imagine that it would provide an alternative place to do so rather than #switchdev or nxbrew.org, just as it has for Wii U homebrew development.

In general the Reswitched team’s approach thus far seems much healthier than the way that the Wii U was treated (“Wii U is dead”, “it’s just the Wii U”, etc), and the popularity of the Switch will likely help as well. There’s no reason to assume that a 7-month-long public exploit thread should ever have to take place when such a positive community like Reswitched exists. If you would like to talk about Switch exploit development, the Reswitched discord channel is a great place to do it.

I don’t like the name

Well, this isn’t a question… Sorry! 😛