Notes from inside your Wii

HackMii header image 2

The USB2 Release

August 14th, 2010 by dhewg · 65 Comments

Some of you may be familiar with a major problem in Wii homebrew land. Most applications and games found on wiibrew.org use libogc, which in turn relies on IOS. While most IOS versions have a USB module, it is limited to USB1, and its I/O throughput make some applications next to unusable when using USB mass storage devices, others have annoyingly long loading times.

The Wii game “Your Shape” changed this – it introduced a new IOS version: 58, and this is the first with an official USB2 module. Starting with the System Menu 4.3 update, IOS58 is available to every Wii.

Thanks to some serious work by tueidj, all homebrew applications can now utilize this USB2 module through libogc. The Homebrew Channel v1.0.8 is the first version supporting it.

IOS58 will be automatically installed when you update your Wii to System Menu 4.3. If you do not want to update, you can use Tantric’s clean IOS58 Installer.

The release notes:

HackMii Installer (v0.8):

  • IOS58 is chosen for The Homebrew Channel when installed. This is required for USB2 support. Other IOS versions are of course still supported, but USB will be limited to version 1.

BootMii beta 6 (v1.3):

  • Fixed the freeze when using the autoboot feature to load System Menu with a delay of zero.
  • The NAND backup no longer crashes when stumbling on uncorrectable pages.
  • A couple of fixes to the integrated SD browser.
  • The autoboot feature is ignored when launching the IOS version of BootMii.

The Homebrew Channel (v1.0.8):

  • General USB improvements for all IOS versions, this fixes the regression introduced in version 1.0.7.
  • USB2 support through IOS58.

A note about unofficial IOS versions: There have been IOS hacks for USB2 support for a long time now. Those rip the USB1 module out of an IOS, and replace it with a USB2 module. You may not care about the uglyness of this approach, the code quality of the replacing modules, or the risks associated with replacing a vanilla IOS. But some coders (us included) do, and outright refuse to use it. On top of that, those nasty hacks are mostly used for warez loaders. IOS58 relieves us of that burden.

The AHBPROT feature, which we described one year ago, allows you to bypass IOS to access devices directly from the PPC, eliminating the need for any IOS patches. Starting now, we will remove all cIOS poisoned applications from the wiibrew.org wiki.

Either grab the new installer here, or use the HBC online update (a confirmation dialog should pop up when launching an older version of HBC).

As always: Please link to this post instead of mirroring the binary, thanks.


Tags: Wii

65 responses so far ↓

  • 1 SifJar // Aug 14, 2010 at 8:00 am

    Nice update. And very quick after the last one too :)
    I’m sure many people will be glad to have better USB support.

  • 2 ketufe // Aug 14, 2010 at 8:14 am


    great work thank you for everything

  • 3 The MAZZTer // Aug 14, 2010 at 8:14 am

    I thought this release was broken because I couldn’t see any apps in the menu. Turns out I’m an idiot, didn’t have my SD card in… >_>

    Would be nice to have something displayed there if you have no SD card inserted or no apps installed instead of a blank UI.

  • 4 Slowking // Aug 14, 2010 at 8:47 am

    I fully understand and support your decision not to support cIOS. However I really disagree with removing applications from wiibrew that use cIOS.
    Nearly ever application on there supports cIOS for installation. I’m pretty sure you can’t just install stuff to NAND with AHBPROT. Or at least not without a lot of code and the risk of bricking stuff.

    Furthermore wiibrew is a wiki, so let the users decide what they want on there and what not. (except warez loaders ofcourse)

  • 5 marcan // Aug 14, 2010 at 8:58 am

    Applications that install cIOS are getting removed. Applications that (optionally) support cIOS (but don’t themselves install it) aren’t.

    Still, at this stage there is just about no use for cIOS within legit homebrew. Take it as an opportunity to port or improve your applications so they don’t depend on warez-laden IOSes.

  • 6 The2ndMessiah // Aug 14, 2010 at 9:13 am

    Awsome update, BUT! For some reason it doesn’t detect the apps in my “Western Digital My Passport Essential SE 1TB”. When I press 1 on the wiimote it shows that theres a USB Device I click it then press OK and nothing happens, please help.

  • 7 Slowking // Aug 14, 2010 at 9:16 am

    Well there is Priiloader, which needs a cIOS to install on newer System Menus, for example…

  • 8 ryan.cheeseisgood // Aug 14, 2010 at 9:16 am

    I hope this doesn’t end up as a double post.
    This doesn’t really have anything to do with the content of this post, but at the top of the page the archive link directs me to a 404 page…
    Thank you.

  • 9 marcan // Aug 14, 2010 at 9:20 am

    If you install stuff such as Priiloader all bets are off anyway.

  • 10 Slowking // Aug 14, 2010 at 9:28 am

    Well that’s kind of a snobish point of view, marcan. Priiloader provides some ver nice functions such as autoboot to HBC, for people without vulnerable boot2 and usefull patches to the system menu.

    So even if we leave out the brick protection, since you probably also don’t approve of custum channels, that’s still more than worth it.

  • 11 11rcombs // Aug 14, 2010 at 9:51 am

    Well, Slowking, you have a couple valid points, but your lack of proper grammar and spelling leaves your post about half-readible and half-nonsense. Pass fifth grade, then come back.

  • 12 SolidMario7 // Aug 14, 2010 at 9:56 am

    Thanks TT, looks like some good may just have just come out the 4.3 update. Looks like the “patched IOS” is dying but not dead, it still has a few uses (non pirate) even with IOS 58.

  • 13 Kage52124 // Aug 14, 2010 at 10:54 am

    I don’t think I agree too much with this move. DOP-Mii is a great app that can also be used for brick recovery, as well as installing customized IOS 36 for Gecko OS channel loading.

    Oh well, such is the heavy hand of anti-piracy I suppose. Thanks for the HBC and Bootmii updates! I love updating these more than once in any short time frame.

  • 14 Ogontz // Aug 14, 2010 at 10:58 am

    I’m just getting into Wii homebrew, and I spent about 7 hours yesterday reading the archives of this site. It’s really amazing what you all have put together in such a short period of time. And thanks for documenting it all so well!

  • 15 Slowking // Aug 14, 2010 at 11:36 am

    So why were DOP-Mii and WiiSCU removed?
    They can run on vanilla Nintendo IOSs and install vanilla other vanilla Nintendo IOSs such as IOS58.

    Using a cIOS is purely optional with both.

    Imo a pretty crappy move…

  • 16 Kage52124 // Aug 14, 2010 at 11:38 am

    In order to use DOP-Mii, you must have at least one IOS fakesigned, and if you don’t, it can get one via Trucha Bug Restorer.

    Even if both apps can install without customizing, they both also can, and that’s what their trying to get rid of.

  • 17 marcan // Aug 14, 2010 at 11:57 am

    If anyone wants to write a vanilla IOS installer that runs under a vanilla IOS and add it to Wiibrew they’re welcome. The only reason existing tools went is because they can also install cIOScrap.

  • 18 rickwii // Aug 14, 2010 at 12:57 pm

    @ Dhewg

    Will there be an sd exploit again since bannerbomb died?

  • 19 caitsith2 // Aug 14, 2010 at 1:31 pm

    Another valid reason for DOP-Mii to be removed. It unfortunately includes the boot2v4 wad, which infringes copyright.

  • 20 WiiCrazy // Aug 14, 2010 at 1:55 pm

    It seems the team is just having problems with herding the flock… and hence the move…

  • 21 jelmew // Aug 14, 2010 at 2:17 pm

    Another question. For this bootmii-update, do we need to rewrite bootmii to boot2 or could we just prepare a sd-card?

  • 22 Arikado // Aug 14, 2010 at 4:55 pm

    caitsith2: DOP-Mii definitely does NOT contain any WADs at all. I should know, I wrote it.

    The removal of DOP-Mii from WiiBrew was pushed by the motive expressed in this post: Patching IOSs is no longer necessary for any legitimate homebrew reasons (USB 2.0 support being the last) so TT/HackMii/WiiBrew no longer has any reason to put up with it. To that end, I fully support this motive as it will greatly simplify helping users solve their problems and keep their Wii’s safe.

    However, DOP-Mii can still do things with a legitimate purpose in mind (NAND/FS permissions patching of an IOS for example) so I will continue to develop the application along with Lunatik. I will simply cease recommending it to people via TT owned/sponsored sites as per their request.

  • 23 DCX2 // Aug 14, 2010 at 5:16 pm

    Does anyone have any idea why Gecko OS requires a fakesigned IOS in order to launch VC/WiiWare games?

    I don’t see the big deal about stuff being taken off wiibrew. If you really want it, it’s still going to be on the Internet, somewhere.

  • 24 Link // Aug 15, 2010 at 12:50 am

    Gecko OS does NOT necessarily need a cIOS. Admittedly I am running on 4.1 with PreLoader which is essentially only there to patch my system menu to refuse reading update partitions from discs. As of such my Wii can keep VERY OLD IOS files.. all IOS 36 and below files I use are old IOS. Gecko OS will check if your IOS 36 or 35 support ES_Identify which it requires to patch VC/WiiWare – if both of these do not, it will check the cIOS slots… if there is a cIOS allowing ES_Identify then it will use it instead.. if no cIOS supports it, it falls back to IOS36 again.

  • 25 qiantpune // Aug 15, 2010 at 2:24 am

    GeckoOS uses ES_Identify to gain access to the files that make up the virtuel console and wiiware games. Once it is allowed to read their contents, it reads the game into memory, loads the code handler & cheat file and starts the game. The identify also allows the game to read and save its data with the correct permissions set in the filesystem.

  • 26 tech3475 // Aug 15, 2010 at 3:13 am

    Do you plan to add all the functions of Cios into libogc (minus the piracy stuff of course) to allow the functions to be more easily available and more safely implemented?

    I personally prefer to use things like Dop-Mii to install newer IOS files and run games than to use the far riskier methods such as official Nintendo updates or wad installs.

    While I understand you wanting to remove cIOS, at the same time this sudden move seems a bit heavy handed and it’s not like devs will have time to rewrite their software quickly/safely, if at all.

  • 27 Toyoke // Aug 15, 2010 at 3:38 am

    Any news about new bannerbomb? Or we with 4.3 update have to do it with indiana ? Game is already ordered , but post is to slow….aghhrrrr…. Am just looking so forward to be a part of the homebrew users.

  • 28 caitsith2 // Aug 15, 2010 at 3:48 am


    And why is offset 0x0A7830 of Dop Mii v12 for 0x28B30 bytes have a SHA1 of BEE7299CCE2288D2B79CA8A87981C1B10A91A88B, and offset 0x0A7BC0 of Dop Mii v12.1 B1 for 0x28B30 bytes have a SHA1 of BEE7299CCE2288D2B79CA8A87981C1B10A91A88B, when a Wad of Boot2v4, freshly downloaded from NUS, also has a SHA1 of BEE7299CCE2288D2B79CA8A87981C1B10A91A88B. If this is NOT boot2v4 in the Dop Mii executable, then I don’t know what is.

  • 29 dhewg // Aug 15, 2010 at 4:29 am

    rickwii: I don’t know

    jelmew: Preparing the SD card is enough, the code that gets injected in the boot2 blocks didn’t change compared to the 0.7(b) installer

    tech3475: What functions? And this annual wiki cleaning happens one year after documenting AHBPROT. There was enough time.

  • 30 tech3475 // Aug 15, 2010 at 5:29 am

    By functions I meant capabilities, i.e. easy NAND access, etc.

    Although a year is a long time, I meant the removal after the announcement was sudden.

    Normally there is a delay to allow people to either make copies of what they want from what was one of the most documented places and to provoke authors to update their apps.

    A case of why fix something if it isn’t broken.

  • 31 LoganA // Aug 15, 2010 at 6:09 am

    repost under new account
    google.com/profiles/lo… // Aug 14, 2010 at 8:21 pm
    Then why is there a copy of boot2v4 wad in your source code tree as of r93 in trunk/data ?

  • 32 winmaster // Aug 15, 2010 at 11:03 am


    Bannerbomb cannot be fixed for 4.3.

  • 33 a // Aug 15, 2010 at 1:00 pm

    @Link and qiantpune:

    Thanks for the answers. However, I’m not sure that is what DCX2 was really asking about (if it was, then I am wondering about this). Could ES_Identify be used through HW_AHBPROT, and possibly make it where a custom/patched IOS is not needed to use channel cheats through GeckoOS? I understand that GeckoOS does not need a custom/patched IOS if you have old IOS files from Nintendo with ES_Identify, such as IOS36 v1042. However, not everyone can use those on their consoles.

  • 34 dhewg // Aug 15, 2010 at 2:49 pm

    There seems to be some confusion about the deletion of certain wiki pages. Let’s try to look at this from another point of view:

    We get lots of reports from our users who run into some kind of problem. A big chunk of those are always about modified IOSes, which caused a hiccup, a freeze, or in the worst case, a brick. Why did they install it? Because some app depends on it, some tutorial made of fail stated it, or some moron decided that its a smart move to replace every IOS on your NAND.

    That’s nothing more than an unnecessary risk. Installing modified IOSes is not required at all. Every single reason for the existence of the modified IOSes out there is either deprecated with AHBPROT, or it can be easily archived with non-permanent modifications.

    This nonsense needs to stop now. Noobs are bricking their Wiis out there for no reason. This move might look harsh, but it also sends a clear message.

    The ordinary user, who doesn’t know anything about the Wii internals, should not be pointed at tools which install unofficial IOSes.

    Coders need to wake up, and remove any spurious dependencies.

    Every app that can install a modified IOS has been deleted from wiibrew. That does not mean you can’t get it from somewhere else. But it means that a Wii homebrew newcomer will not instantly stumble upon a questionable app which risks your Wii for nothing.

  • 35 Steveice10 // Aug 15, 2010 at 3:08 pm

    As much as I want to switch from Patched IOS, I won’t until there ia an app to install IOS, System Menus, etc. and an app to install wads, both with decent GUIs, without patched IOS.

  • 36 kmeisthax // Aug 15, 2010 at 6:51 pm

    HW_AHBPROT is a much cleaner way to get full control over the Wii than modifying unstable proprietary Nintendo code. It’s written by people who can’t code C, we shouldn’t touch it outside of defined interfaces.

    I admit, I +trucha patched every new IOS I installed with WiiSCU, because I liked having the ability to play around with save files using ES_Identify hacks. But I also had BootMii, I understood exactly what IOS does, and I didn’t run Waninkoko crap 24/7. (I’ve used it once – because I wanted to disassemble a game – but I suck at reading PPC asm.)

    Today, your average Wii homebrew noob does not possess a BootMii-capable Wii, or even knows what IOS is other than “thing that keeps me from theming my System Menu.” The best we can do is, as a homebrew community, refrain from pointing him to tools which have known brick risk.

    A year ago we got the AHBPROT register, which means we don’t need IOS as anything but a bootstrap now. That’s been a year to test and implement PPC-side code for everything we want to do. So I think it’s fair to start depreciating cIOS-dependent utilities, starting with removing the installers of custom IOS code from the wiki. We can then move on to replacing broken IOS-based utilities with newer, cleaner PPC-pure code.

  • 37 YuriCPS // Aug 15, 2010 at 7:43 pm

    @ Dhewg

    After I updated Bootmii and the HBC, Categorii stopped working.

  • 38 bobjrsenior // Aug 15, 2010 at 8:57 pm

    I updated my hombrew channel today to version 0.8 and now my usb won’t work. It uses fat32 and has always worked great until now. Do you have a way to fix it so I can finally get brawl- on my wii?

  • 39 caitsith2 // Aug 16, 2010 at 1:25 am

    Dop-Mii v13 still contains boot2v4.wad. http://img269.imageshack.us/img269/9364/dopmiiboot2v4.png – If That is not boot2v4.wad in dop-mii, then I do not know what it is, since Every single hash algo was run against the specific selection.

  • 40 bobjrsenior // Aug 16, 2010 at 5:35 am

    Is there anyway to downgrade my homebrew to 0.7 so my usb will work again?

  • 41 utar // Aug 16, 2010 at 7:44 am

    I have a question I installed IOS58 using the stand alone installer but the Homebrew channel still reports it’s running IOS38. (I think it’s 38 I’m not in front of my Wii at the moment).

    I have even tried deleting IOS58 with Any Title Deleter and reinstalling without any joy.

    Any help would be appreciated.

  • 42 kmeisthax // Aug 16, 2010 at 8:20 am

    @utar: You have to reinstall Homebrew Channel for it to use the new IOS. The IOS it runs on is written to the TMD at install-time.

  • 43 utar // Aug 16, 2010 at 11:55 am

    Thanks, reinstalling the HBC worked.

  • 44 jrcolonial98 // Aug 16, 2010 at 1:56 pm

    Thanks TT, nice work.

  • 45 bezem // Aug 16, 2010 at 4:49 pm

    Hi I’m just curious, I was having issues with the 0.7 installer (Wii Slot Flashes), then when the 0.7b installer came about my issues ceased and I was able to complete the update fine. Now with 0.8 installer, the issue is back again (Wii Slot Flashes). I was just curious, is it possible the 0.7 installer is in place again, and not the 0.7b installer? Thanks!

  • 46 Steveice10 // Aug 17, 2010 at 5:55 am

    If IOS58 installer was made into a full IOS installer like Dop-Mii, it would be great for recovery and not use a patched IOS.

  • 47 google.com/accounts/o8… // Aug 17, 2010 at 3:36 pm

    I suppose this isn’t really the best place to ask, but since you said we ought to upgrade to 4.3, is there any way for me to upgrade from 3.4 to it without risking even that minuscule chance of bricking that came with 4.0 or 4.1 or whichever? I’ve been sitting on 3.4 this whole time due to paranoia that it might happen to me.

  • 48 Isaac // Aug 17, 2010 at 7:41 pm

    After installing this version of the homebrew channel and uninstalling bootmii IOS…I inserted my Netflix disk and it wanted me to update, even though I am already at 4.3
    I just launched it through geckoOS instead for today, is it safe to let it try to update from the disk?

  • 49 Phredreeke // Aug 18, 2010 at 4:12 am

    You should not update to 4.3, there’s no benefit to do so.

    Use this app instead: http://wiibrew.org/wiki/IOS58_Installer

  • 50 winmaster // Aug 18, 2010 at 8:30 am

    If you’re afraid of the boot2 update, run your Wii through an uninterruptable power supply while updating. You have a better chance of winning the lottery than having your Wii brick doing this.

  • 51 Fuglykirby // Aug 18, 2010 at 9:08 am

    I installed IOS58 and it seems much slower than IOS202 when it comes loading.Videos in WiiMC/games in emulators that utilize this ios58 have longer loading and buffering is longer too.

  • 52 tech3475 // Aug 18, 2010 at 2:00 pm

    /\ Actually, the dodgy boot2 update code Nintendo used could cause this to still happen.

    Does System Menu 4.3 actually include the boot2 update or did Nintendo learn nothing from the last disaster?

  • 53 winmaster // Aug 18, 2010 at 4:32 pm


    System Menu 4.3 didn’t come with a new boot2 update, but at 3.4, he still may have an outdated version of boot2.

  • 54 Isaac // Aug 18, 2010 at 7:36 pm

    Let me clarify, I updated to 4.1 with my Moster Hunter 3 disk. Then I updated to 4.2 online. Then I updated the Homebrew channel with the HackMii Installer v0.7 when it came out. Then I updated to 4.3. As of then Netflix was working just fine through the Wii menu. Then I updated the Homebrew channel to the latest version. Now when I have the Netflix disk in, the disk channel wants me to update.
    I’m not sure if I should let it, since it’ll try to update to 4.1 over a 4.3 !

  • 55 wiisixtyfour // Aug 18, 2010 at 10:04 pm


    Just let the Netflix disc update your Wii. It will only install whatever you’re missing.

  • 56 bobjrsenior // Aug 19, 2010 at 5:15 am

    I just updated my hombrew channel to 0.8 and now my usb won’t work. It always worked before the update so i wanted to know if theres a way to downgrade hombrew or fix it another way,

  • 57 Wiill // Aug 19, 2010 at 6:58 am


    here’s HMI 0.7 which will let you get HBC 1.0.7


  • 58 bobjrsenior // Aug 19, 2010 at 7:41 am

    I tried it but there no port in my wii that I can plug it in with.

  • 59 Isaac // Aug 19, 2010 at 8:36 pm

    I ended up using the online update instead since I trusted it more to update my 4.3 installation…it went very fast, a lot faster than when I updated to 4.3…I wonder if the new homebrew installer removed something else when I uninstalled the bootmii IOS. Very weird, but it works just fine now.

  • 60 winmaster // Aug 19, 2010 at 8:39 pm


    It didn’t install the full 4.3 update, because you already had 4.3. It just installed whatever it thought you were missing.

  • 61 KingLewy // Aug 20, 2010 at 5:30 am

    USB 2.0? Cool. At long last. Good work guys.

  • 62 Isaac // Aug 20, 2010 at 1:33 pm

    Yes, but it’s odd that it didn’t go missing until updating the homebrew channel and removing the bootmii IOS. The update on the Netflix disk certainly didn’t change.

  • 63 Jbc007 // Aug 20, 2010 at 1:53 pm

    By removing Bootmii/IOS, you no longer had IOS 254. That is all the Netflix disk wanted, and the stub IOS 254 was the only thing installed by the update.

  • 64 finno123 // Aug 25, 2010 at 7:16 am

    Does anyone know if you use a backup from a previous version of bootmii (beta 3) if I can still use it to restore on the new version of bootmii?

  • 65 Capt_Trips // Dec 7, 2010 at 6:16 pm

    I second finno123’s question: Can an updated bootmii restore an old nand dump from an old boot mii, Or, will this cause problems?

    Secondarily, I am expierencing a lot of bugs with FCEUGX and HBC v108 using IOS58. I’m sure it has to do with IOS58–seems to have memory addressing issues?

    I am not sure what to say, other than thanks for the hard work and nifty program, but, I think I miss Bootmii v.3 and IOS36–it all just ran smoother and looked brighter.

    I patiently await your advice, or next update.

You must log in to post a comment.