Hacking Best Way to Mod Any Wii: ModMii for Windows: Official Support Thread

[Maxternal]

Hmmm... when I launch YAWMM, it asks for a source device. When I select Wii SD Slot it responds with ERROR! (ret = -1).

That's ... umm ... wierd
You have NAND emulation disabled right? (if you chose SD as a NAND emulation device first ... if it actually asked you for it ... it will be blocked from being used as anything else.) NAND emulation will break the installation anyhow so DON'T use it.

If that doesn't work, there's always the option of trying to install it from a USB drive instead, I guess.

 

[Noun]

That's ... umm ... wierd
You have NAND emulation disabled right? (if you chose SD as a NAND emulation device first ... if it actually asked you for it ... it will be blocked from being used as anything else.) NAND emulation will break the installation anyhow so DON'T use it.

If that doesn't work, there's always the option of trying to install it from a USB drive instead, I guess.

I assume that NAND emulation is disabled, because I haven't done anything to enable it, as far as I know. I'm cleaning up USB drive right now to explore my options.

Thanks for your help.

 

[XFlak]

have u tried using ModMii's hackmii solutions function?

 

[Noun]

I assume that NAND emulation is disabled, because I haven't done anything to enable it, as far as I know. I'm cleaning up USB drive right now to explore my options.

Thanks for your help.

I'm also unable to mount a USB drive. Error -1...

 

[Noun]

have u tried using ModMii's hackmii solutions function?

The HackMii solutions function is exactly what I've been trying to use.

I've noticed that MMM loads IOS80 v6944 through LetterBomb, and IOS60 v6400 through HBC. Neither of which will permit loading a different IOS or to install & patch IOS36.

 

[Maxternal]

I'm also unable to mount a USB drive. Error -1...

Ouch. Well, I'd say to try the SD card with all of the IOS above 200 first (the SD card SHOULD be easier to mount) and then, if that fails, start from the lowest and try them all. This is really weird.

I would ask for a syscheck log to have some idea what's going on but I have a feeling that would fail, too ... it's always worth a try, though.

 

[Noun]

Ouch. Well, I'd say to try the SD card with all of the IOS above 200 first (the SD card SHOULD be easier to mount) and then, if that fails, start from the lowest and try them all. This is really weird.

I would ask for a syscheck log to have some idea what's going on but I have a feeling that would fail, too ... it's always worth a try, though.

I can't even adjust the IOS in MMM. If I select "Load another IOS", the system crashes (Error -4352).

I tried to generate a syscheck log through Syscheck GX, but it wouldn't load. I tried with DOP-Mii as well, but it crashes after the start page.

 

[Maxternal]

I can't even adjust the IOS in MMM. If I select "Load another IOS", the system crashes (Error -4352).

I tried to generate a syscheck log through Syscheck GX, but it wouldn't load. I tried with DOP-Mii as well, but it crashes after the start page.

Have you tried other IOS's in Yet Another WAD Manager Mod? It only asks once when it's starting up so you'd have to restart back to the HBC for each test.

Also, IF you have any forwarder channels installed you could replace the boot.dol they run off the SD card with the one from MMM. That might give it the AHBPROT patch it needs to install correctly.

 

[Noun]

Have you tried other IOS's in Yet Another WAD Manager Mod? It only asks once when it's starting up so you'd have to restart back to the HBC for each test.

Also, IF you have any forwarder channels installed you could replace the boot.dol they run off the SD card with the one from MMM. That might give it the AHBPROT patch it needs to install correctly.

Hmm... YAWMM first asks to select a source device for me. I can't get it past the SD card error.

 

[Maxternal]

Hmm... YAWMM first asks to select a source device for me. I can't get it past the SD card error.

If it's asking for that FIRST and doesn't ask for anything else before that you MIGHT have a config file in there that you made with ModMii, too. Other wise it should first ask some other questions before asking for the device.

In the WAD folder see if there's a file called wm_config.txt. If there is, try moving, removing, or renaming it and running YAWMM again.

 

[Noun]

If it's asking for that FIRST and doesn't ask for anything else before that you MIGHT have a config file in there that you made with ModMii, too. Other wise it should first ask some other questions before asking for the device.

In the WAD folder see if there's a file called wm_config.txt. If there is, try moving, removing, or renaming it and running YAWMM again.

Nope, no config file is present.

 

[Maxternal]

Nope, no config file is present.

Hmm, that's weird because it's supposed to ask you for the IOS first and THEN ask about NAND emulation if you chose either 249 or 250 as an IOS and THEN ask to choose between SD or USB. I'm not sure what to tell you at this point.

 

[gooddegenerate]

Someone told me that looking at m syscheck that my stuff seemed outdated so I thought I'd ask, and check with modmii since I've never updated on it before.. (I bought my wii premodded then did some tweaking later on like adding d2x and dios mios and what not)

Anyway, I uploaded system check and then used modmii's syscheck udpater to see what it said I needed..

My sysCheck.cvs file is as follow:

sysCheck v2.1.0b18 by Double_A and R2-D2199
...runs on IOS58 (rev 6176).
 
Region: NTSC-U
System Menu 4.3U (v513)
Priiloader installed
Drive date: 2008.12.18
Homebrew Channel 1.1.0 running on IOS58
Hollywood v0x21
Boot2 v4
Found 109 titles.
Found 52 IOS on this console. 6 of them are stub.
 
IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 54321): Trucha Bug
IOS10 (rev 768): Stub
IOS11 (rev 54321): Trucha Bug
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 523): No Patches
IOS16 (rev 54321): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS17 (rev 1032): No Patches
IOS20 (rev 54321): Trucha Bug
IOS21 (rev 782): ES Identify, NAND Access
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 54321): Trucha Bug
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3349): Trucha Bug, ES Identify, NAND Access
IOS36 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 3869): Trucha Bug, NAND Access
IOS38 (rev 3867): Trucha Bug, ES Identify, NAND Access
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 54321): Trucha Bug
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5406): Trucha Bug, NAND Access
IOS55 (rev 5406): Trucha Bug, NAND Access
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 54321): Trucha Bug
IOS61 (rev 5662): No Patches
IOS70 (rev 54321): Trucha Bug
IOS80 (rev 54321): Trucha Bug
IOS90 (rev 54321): Trucha Bug
IOS202[60] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 65535, Info: hermes-v4.0): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[38] (rev 65535, Info: hermes-v4.0): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS236 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS247 (rev 65535): Trucha Bug, NAND Access, USB 2.0
IOS248 (rev 65535): Trucha Bug, NAND Access, USB 2.0
IOS249[56] (rev 21009, Info: d2x-v9beta(r49)): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21009, Info: d2x-v9beta(r49)): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
 
Report generated on 2013/03/13.

and what modmii says I need after syscheck updater:

Your unique list of WADs to install are as follows:
 
    IOS11v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    IOS20v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    IOS30v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    IOS40v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    IOS50v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    IOS52v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    IOS60v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    IOS70v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    IOS80v16174(IOS60v6174[FS-ES-NP-VP-DIP])
    cIOS202[60]-v5.1R
    cIOS222[38]-v4
    cIOS223[37-38]-v4
    cIOS224[57]-v5.1R
    cIOS249[56]-d2x-v8-final
    cIOS250[57]-d2x-v8-final
    IOS9-64-v1034
    IOS15-64-v1032
    IOS21-64-v1039
    IOS35-64-v3608
    IOS36-64-v3608
    IOS37-64-v5663
    IOS38-64-v4124
    IOS53-64-v5663
    IOS55-64-v5663
    IOS62-64-v6430

Now, I'm just curious.. if I were to install all those wads right there, would it mess up my wii or cause incompatibility issues or anything? If so, which wads do I really need to update?

 

[jodur]

Mulit Mod Manager needs to be updated to work with new wii remotes!

It was a long time until i used modmii, but i noticed that modmii is using a version of "mmm" who isn't recompiled to support the new wii remotes!!

 

[Etheboss]

That is correct jodur, modmii always downloads from the source, so this means the source is never updated.

You can maybe solve this by doing on of the following:
1. download the svn and recompile yourself with the new libs.
2. make a patch and submit it on the mmm google code svn page.
3. ask the developer to update the app.

Or hope somebody else is willing to do it

 

[Warrior522]

The built-in bannerbomb is resulting in a black screen. What gives? Firmware 4.2, USA.

 

[XFlak]

@gooddegenerate, it's totally safe to install those files. I recommend you install them all, but the only ones that will impact the performance of you're usbloader is cIOS249 and cIOS250.

@noun,
have you tried wiimod?

@Warrior522,
Do you have boot.elf saved to the root of your SD card? Are you loading bannerbomb via the sd card button on the main wii menu, not via the data management screen? Have you tried different versions of bannerbomb? Have you tried a different SD card? Do you have any wii games like super smash brothers brawl or lego star wars, lego indiana jones etc that u can use instead of bannerbomb to softmod your wii?

 

[X BattousaiX]

Xflak, if you have a moment, could you get back to me? I'm having some issues with downloading all the files from modmii. I've got the installer, and I'm using the old Console command version of the installer. Everything is fine until the generate guide and download files, whereupon the guide generates properly, but file #12, wilbrand, fails to download.

I've changed the line as recommended in the modmii.bat file, but that hasn't fixed my problem. Here's an image http://i1113.photobucket.com/albums/k503/Hackedglitch265/Modmiierror.jpg.

I'm using a launch wii with system menu 4.3U. I don't think I did anything wrong (I followed the video guide), so I'm baffled as to what is causing this. Not to mention this isn't even saving on my sd card, which rules out any possible space issues (well over 400-500 gb free space). Any ideas on how to fix/work around this? It'd be much appreciated.

EDIT: all other files downloaded properly, so its just that one file.

Spoiler

• Your chosen options

This guide was generated using the following parameters:

• Install and\or update all recommended softmods
• Current System Menu is 4.3U
• Desired System Menu is 4.3U
• Install Dark Wii Red Theme
• Do not update active IOSs (can be enabled in options)
• Do not Install a cMIOS (can be enabled in options)
• Install a USB-Loader Forwarder Channel (can be disabled in options)

• Important Notes

• This guide does NOT require a Wifi connection on your Wii.
• An SD card formatted to FAT32 required (best results are with SD cards, SDHC cards will only work on System Menu's 4.0 or above).
• If you get errors during any of the steps reformat your SD card as FAT or FAT32
• Turn off WiiConnect24 and take out all gamecube memory cards/controllers when modding the Wii (unless instructed otherwise).
• If your Wii ever freezes, hold the power button on the Wii for 5 seconds to power it off then try again.
• Don’t ever accept a new Nintendo update without first googling to see if it’s safe. The last update (to 4.3) was released in late June 2010. If you accept an official Nintendo update after modding the Wii, you may lose some or all of your modifications.
• Never uninstall a system menu or IOS.
• Do not install untested WADs/themes without Bootmii or Priiloader installed.
• This custom guide is great start, but Wii modding is always evolving. Check for updates online, and remember, google is your friend.
• If you have questions, a more detailed guide can be found at www.sites.google.com/site/completesg/

• Hacking your Wii

• Installing The Homebrew Channel (HBC) and Bootmii

Note:

1. 1. 
      if this Wii was previously modified, and it has either the HBC, BootMii as Boot2, or a Forwarder Channel installed, you can use that instead of an exploit.

1. 1. 
      If using BootMii as Boot2 to install the HBC, turn on your Wii with the SD Card inserted and BootMii will load. Go To the SD menu and load bootmini.elf. This will load the Hackmii Installer allowing you to reinstall the HBC.

1. 1. 
      If using a Forwarder Channel, just save the boot.elf/dol from the app you want to load (ie. SD:\apps\hackmii_installer\boot.elf or SD:\apps\MMM\boot.dol) to the location used by your

specific

1. 1. 
      Forwarder Channel (ie. SD:\apps\usbloader\boot.dol). Then start the channel and the Hackmii Installer will load allowing you to reinstall the HBC. Note, if your forwarder channel only loads dol's and not elf's, launch MMM's boot.dol, then use its "App Manager" to load the Hackmii Installer.

Wilbrand

1. 1. 
      Requirements: an SD or SDHC card

1. 1. 
      Go to the "Messageboard" on your Wii and navigate to Yesterday. Click on the envelope with the pink Bomb icon.

1. 1. 
      This runs the Hackmii Installer. Use the installer to install the Homebrew Channel (HBC) and Bootmii as IOS and Bootmii as Boot2 (if possible).

Note:

1. 1. 
      If you get a "no vulnerable IOS" error message, run ModMii again and this time select the "Hackmii Solutions" option and follow the new instructions before continuing this guide.

• Making a NAND backup

1. 1. 
      While inside the Homebrew Channel, load BootMii by pressing home and clicking Launch Bootmii.

1. 1. 
      Press the power button on the Wii 3 times to get to the last option, then press the reset button (you can also navigate with a Gamecube controller).

1. 1. 
      Press reset to choose the first option, then follow the directions on the screen to make your NAND backup (bad blocks are no problem).

1. 1. 
      Backup the Bootmii folder, nand.bin, and keys.bin elsewhere and erase from the SD card (or rename it). You'll need these in case of emergencies, so don't lose them.

1. 1. 
      Go back to The Homebrew Channel.

Note:

1. 1. 
      if Bootmii was installed as boot2, then it will show up as soon as the Wii is turned on AS LONG AS it finds the bootmii folder (mentioned above) on the root of the SD card.

• Install a patched IOS236

1. 1. 
      Start the Homebrew Channel.

VERY IMPORTANT!

1. 1. 
      In the Homebrew channel, if you do not have a working internet connection already set up, you will see an icon flashing in the bottom right corner of the screen indicating its inability to initialize the network. You should wait for the icon to stop flashing OR let it flash for 30-60 seconds before proceeding otherwise these apps may error shortly after being launched. If you encounter this harmless error, power off the Wii and repeat this step from the beginning. To increase your chances of success, add a working internet connection to your Wii via the official Wii Settings Menu, but be sure to say "No" when asked to perform an update.

1. 1. 
      You only need to perform ONE of the below methods.

1. 1. 
      Once either method successfully installs IOS236, you can move onto the next step.

1. 1. • Method A: Using IOS236 Installer

1. 1. • 
        After waiting 30-60 seconds for the HBC to attempt to initialize the network, launch "IOS236 Installer v5 MOD".

Note:

1. 1. • 
        This app must be launched using HBC v1.0.7 or higher in order to work properly.

1. 1. • 
        It should say "IOS236 installation is complete!" and return to The Homebrew Channel.

1. 1. • 
        If you experience errors, keep trying and it should eventually work.

1. 1. • 
        If you continue to experience errors you can try using Simple IOS Patcher instead.

1. 1. • Method B: Using Simple IOS Patcher

1. 1. • 
        After waiting 30-60 seconds for the HBC to attempt to initialize the network, launch "Simple IOS Patcher".

Note:

1. 1. • 
        This app must be launched using HBC v1.0.7 or higher in order to work properly.

1. 1. • 
        Choose "IOS36" (already selected by default) and push A, then select "Install IOS to slot" and choose 236. Select "Install patched IOS36" leaving the 4 patches set to "yes" and press A, then choose "Load IOS from SD card". Confirm your choice with the A button and, when prompted, push A to continue the installation. When the installation is finished press the B button to exit the Main Menu.

1. 1. • 
        If you experience errors, keep trying and it should eventually work.

1. 1. • 
        If you continue to experience errors you can try using IOS236 Installer instead.

• Install Priiloader

1. 1. 
      Launch "Priiloader 236 Mod" via the Homebrew Channel

1. 1. 
      After the Priiloader Installer loads, press + to install it.

1. 1. 
      After successfully installing Priiloader, access it by powering off the Wii, then powering it back on while holding reset until you see the Priiloader menu.

1. 1. 
      You should install some system menu hacks now (by going to System Menu hacks option).

RECOMMENDED HACKS

1. 1. • Block Disc Updates
      • Block Online Updates
      • Replace Health Screen
      • Move Disc Channel

1. 1. 
      The priiloader menu is white by default, you can change it to black in the Priiloader settings if you prefer.

1. 1. 
      One of the special functions of Priiloader is that it can autoboot any app/file instead of the system menu. Some apps (like crazyIntro) can't be used without it.

1. 1. 
      For details on how to do so, visit

www.sites.google.com/site/completesg/system-hacks/priiloader

• Install WADs

1. 1. 
      Load Multi-Mod Manager (MMM) via the HomeBrew Channel.

1. 1. 
      If IOS236 is not already loaded, select "Load another IOS", then select IOS236

Note:

1. 1. 
      If this step fails with error -ret 2011 or other, you may need to retry patching IOS236. If the Wii was previously softmodded, you can try loading cIOS250 (or others like 202,222,223,224,236,249)

1. 1. 
      In Multi-Mod Manager's main menu, go down to select "WAD Manager".

1. 1. 
      Install the following WADs from the WAD folder (this list of WADs is unique to the information you provided ModMii).

1. 1. 
      Be careful not to install any additional WADs that may have been previously saved in this folder (they may be safe, but I cannot say for sure).

1. 1. 
      Mark each of the following WADs for installation by navigating to each WAD and hitting "+"

1. 1. 
      Alternatively, you can hold "+" for 2 seconds to select all the WADs in the folder.

1. 1. 
      After you've marked all the WADs listed below, press 'A' twice to install them.

1. 1. 
      If any files fail to install properly, they will remain marked for installation, so just retry installing those files.

Your unique list of WADs to install are as follows:

1. 1. • IOS11v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • IOS20v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • IOS30v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • IOS40v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • IOS50v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • IOS52v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • IOS60v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • IOS70v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • IOS80v16174(IOS60v6174[FS-ES-NP-VP-DIP])
      • cIOS202[60]-v5.1R
      • cIOS222[38]-v4
      • cIOS223[37-38]-v4
      • cIOS224[57]-v5.1R
      • cIOS249[56]-d2x-v8-final
      • cIOS250[57]-d2x-v8-final
      • IOS58-64-v6176
      • USBLoader(s)-ahbprot58-SD-USB-v11b-IDCL

1. 1. 
      The above underlined forwarder channel will load the first file it finds from the following list:

1. 1. • SD+USB:\apps\usbloader\boot.dol
      • SD+USB:\apps\usbloader\boot.elf
      • SD+USB:\apps\usb-loader\boot.dol
      • SD+USB:\apps\usb-loader\boot.elf
      • SD+USB:\apps\usbloader_cfg\boot.dol
      • SD+USB:\apps\usbloader_cfg\boot.elf
      • SD+USB:\apps\WiiFlow\boot.dol
      • SD+USB:\apps\WiiFlow\boot.elf
      • SD+USB:\apps\usbloader_gx\boot.dol
      • SD+USB:\apps\usbloader_gx\boot.elf

Note:

1. 1. 
      IOS58 is required for the forwarder to launch apps from an SD Card and hard drives formatted as FAT32, NTFS, ext2, ext3 and ext4. It also supports meta.xml arguments and is able to launch apps with direct hardware access.

• Reinstall the Homebrew Channel (if applicable)

1. 1. 
      In the HomeBrew Channel, hit the "home" button. In the top right corner you will see the IOS used by the HBC.

1. 1. 
      If the HBC is using IOS58 and your HBC is not upside-down, you can skip this step.

1. 1. 
      If the HBC is not using IOS58 or it is upside-down, you should continue with this step to reinstall it.

1. 1. 
      Launch the HackMii_Installer via the HBC.

1. 1. 
      Use the Hackmii Installer to fix/re-install the HBC (using IOS58). Once you've successfully reinstalled the HBC, you can move onto the next step of the guide.

1. 1. 
      If the HBC is failing to load the HackMii_Installer (just blackscreens), instead launch the Hackmii Installer using the method described in the first Step.

• Install Custom Wii Menu Theme using MyMenuifyMod (optional)

WARNING

1. 1. 
      : DO NOT INSTALL THEMES WITHOUT PROTECTION (BOOTMII, PRIILOADER AND NAND BACKUP) AND ONLY INSTALL THEMES FOR YOUR SPECIFIC SYSTEM MENU VERSION AND REGION!

1. 1. 
      Launch MyMenuifyMod from the HBC.

1. 1. 
      Navigate to the theme you would like to install that corresponds to your specific System Menu Version (4.3U) then press A to install it.

1. 1. 
      If you ever decide to restore the original Menu Wii theme, simply launch MyMenuifyMod again, navigate to 000000XX_4.3U.app and press "A" to install it.

• After modding your Wii

After you are done modding your Wii, you can optionally delete any unnecesarry files by using ModMii's "File Cleanup" Feature.

If you used Bannerbomb and choose not to use the File Cleanup feature, in order to avoid having your Wii freeze when accessing the SD Card Menu, you should delete the "aktn" folder where bannerbomb is saved (SD:\private\wii\title\aktn), or rename the entire "private" folder.

At this point you're practically done.
Now you should be downloading the latest homebrew applications and setting them up on your SD Card (or FAT32 USB Hard Drive) so they can be launched via the HBC.

For playing your backups off a USB hard drive, run the USB-Loader Setup feature from ModMii's Main Menu.

For downloading applications, you should:

• Check out ModMii's batch download pages as it has many popular apps available for download.
• Download Homebrew Browser via ModMii to get many popular apps, but this is an online only Wii application.
• For those without internet on their Wii, check out this list of Homebrew applications.

Another great resource is webrewwii.blogspot.com

After getting whatever apps you want, you should get a boot.dol file and possibly a icon.png and meta.xml.
For HBC to read your SD/USB correctly, your card must be structured SD:/apps/application name/boot.dol
If you have a *.dol not named boot.dol, rename it boot.dol, otherwise it will not be recognized by the HBC.
(optional: the icon.png and meta.xml should be saved in the same place as the boot.dol)

• Credits, Supporting Apps, and Sources

ModMii was written entirely by me, XFlak; however, without the help of many other very talented people ModMii would not exist.
Some people have contributed supporting files or programs, others have shared their knowledge, some have provided ideas and others have given their time.
I have tried my best to recognize everyone's contribution to ModMii regardless of how big or small it is. If I've forgotten someone, please notify me and I'll add them to the credits as quickly as possible.



If you would like to contribute to the project, or have ideas, please send me a PM and we can discuss it further in private.

• Support XFlak

If ModMii worked for you, please vote in favour of the program HERE
Check out my Top Channels
Check out my Crazy Intro Videos

I've tried ignoring the menu theme and it cut it down from 27 to 25 files, but wilbrand still fails to download. I've run out of ideas as to what to do >.<

Edit 2: After reviewing the first post, I noticed I had failed to properly rewrite the code. I deleted all the files and re-installed mod mii and properly corrected the lines in the code of the modmii.bat. However, I'm now finding myself in the situation that Both wilbrand and hackmii installer are failing. I have no clue as to what I am doing to fail this much v.v

 

[Killercal]

I recently re-hacked my wii with modmii and reformatted my usb hd to FAT32 from WBFS. Now a lot of the games that used to work will not work, they just go to a black screen when launched from USBConfig, any idea what I could be missing? I'm running menu 4.2U and selected USB and FAT32 in Modmii.

 

[XFlak]

if u used modmii properly all should be working fine. You probably made a mistake somewhere. Please post a syscheck log in spoilers, or just load it using modmii to see if anything is amiss.

@X BattousaiX,
U running windows 8 or something?
Try opening a cmd window where wilbrand.exe is saved (ModMii's temp folder) and enter the following:

wilbrand.exe 0017ab4ba245 mm/dd/yyyy 4.3U "X:"

just insert the correct date and replace X: with the drive letter of your sd card (or the path of your copy to sd folder)