<![CDATA[Sick Gaming - Nintendo Mods]]>

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/sickgaming/domains/sickgaming.net/public_html/inc/plugins/htmlposts.php on line 137

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/sickgaming/domains/sickgaming.net/public_html/inc/plugins/htmlposts.php on line 137

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /home/sickgaming/domains/sickgaming.net/public_html/inc/plugins/htmlposts.php on line 137
<![CDATA[Sick Gaming - Nintendo Mods]]> https://sickgaming.net/ Sun, 12 Apr 2026 21:03:51 +0000 MyBB <![CDATA[Basic do's and DO NOT'S of vWii modding]]> https://sickgaming.net/thread-82807.html Wed, 14 Jan 2015 17:00:01 -0200 whatsasick]]> https://sickgaming.net/thread-82807.html Safe (should be ok to run without worry):
- homebrew that does not install anything or require installation, or even better, ones that do not write to NAND at all
- installing The Homebrew Channel. While this does install to NAND, this is the most reputable of all Wii homebrew launchers, and the authors (Team Twiizers) make sure it is as safe as possible before they release it.

Potential risk of brick but still more or less doable (make sure you have a NAND backup, or at the very least a key dump from the modified xyzzy + hardware programmer):
- Installing channel wads (same reason as on regular Wii, mainly only if they have a bad banner or something, otherwise if they are confirmed ok, then they should be safe)
- Installing non-critical system parts, like game IOS, patched IOS, or cIOS into unused slots (such as d2x v10 vWii version), as long as one is installing vWii versions only on vWii, and regular Wii versions only on regular Wii (they are not used by System Menu and should be fine to remove and reinstall if you screw them up)
- Modifying 1-513 "BC-WFS". According to crediar, this is used by vWii to be able to load up and give compatibility to Dragon Quest X. Dragon Quest uses it's own "WFS" formatted USB drive, so that is probably why. BC-WFS is encrypted, so it cannot be successfully modified until the encryption is publicly cracked. But messing it up should not harm anything on vWii other than Dragon Quest X.

Will brick if you do it wrong, you can do these [b]BUT[/b] only do if you know EXACTLY what you are doing: (a NAND dump, and at the very least a xyzzy key dump + hardware programmer will be the ONLY thing to save you if you screw up, due to no bootmii as boot2 on vWii)
- Modifying System Menu IOS in any way (is currently IOS80)
- Modifying 1-512 "BC-NAND". According to crediar, this title is needed by vWii to be able to load NAND titles, like channels. Messing this up would break channel loading, which is no good, but disc games should still work. Breaking this would be harder to fix due to the inability to load channels. It is also encrypted, so cannot be successfully modified until the encryption is publicly cracked.

DO NOT do, this stuff is just plain stupid and confirmed as not working and brick causing:
- Installing regular Wii IOS on vWii. Installing non-critical IOS will result in those IOS having very limited functionality and crashing very easily, installing old System Menu IOS (IOS 80 atm) will cause vWii to brick.
- Installing vWii IOS on regular Wii. This actually seems worse than the inverse. While Wii IOS maybe actually load up on vWii but still crash when trying anything, vWii IOS on regular Wii will not work at all. Also, users have reported very strange Wii bricks (among them being myself and FIX94) from installing vWii IOS on them, even non-critical ones... I have no clue why they do this, but new IOS for new hardware, there has got to be a reason somewhere.
- Installing vWii IOS wad files on vWii packed from a vWii NAND dump using a program on your PC. The program used to create the Wad file is fake signing the ticket. While it install fine and seems to works fine on vWii, it bricks the Update feature of the WiiU Mode, and prevent reinstalling The Homebrew Channel on vWii!
- Installing older IOS, or stub IOS, or deleting IOS that you do not want anymore.
- Modifying vWii System Menu in any way, including priiloader or "themes". Do not modify the System Menu's .dol, it has extra encryption that has not been publicly cracked yet. Also cannot install priiloader for the same reason. Since vWii System Menu is not the same as regular Wii's System menu, regular Wii "themes" are not compatible, and will brick vWii. AFAIK there are no vWii themes released at this time, and I myself am unsure about making or installing my own myself, as I have not tried it yet.
- Deleting The Homebrew Channel if it doesn't work anymore. The homebrew channel is not working because you messed the IOSes. The Homebrew Channel is working fine, do not ever delete it! it's your most easiest way to restore and fix a bricked vWii. If you delete The Homebrew Channel, it will be harder to fix your console.
- Deleting Forwarder Channels if you bricked your vWii. Same as The Homebrew Channel, a forwarder can be found useful to unbrick your console. Don't delete ANYTHING if you think your console is not working. Ask to other users on the forum first. It will save your console.
- Trying to do or install anything at all if you do not know what you are doing, seriously, read up and learn about everything before attempting to mod anything, this should be a given!

What is recommended to do:
- Install The Homebrew Channel.
- Then run the modified xyzzy v1.2.1 unnofficial provided by DarkMatterCore on your vWii via HBC. It will dump your vWii's unique per-console encryption keys that are needed to decrypt and re-encrypt a dump of your vWii's NAND on PC, useful in case if you brick vWii, you can (or send it to someone who can) dump the vWii's NAND into PC using a hardware programmer, like an Infectus (no longer manufactured) or Progskeet, and then decrypt it to alter it and fix it, then re--encrypt and reflash the fixed NAND dump onto the vWii's NAND chip. Especially useful due to there not being any vWii version of BootMii.
- Educate yourself on whatever it is you want to do before doing it, do not just follow guides without learning about what each part does. Be lazy and you could pay the price for it someday!
- Again, only mess around with important stuff if you know EXACTLY what you are doing beforehand. It is your own responsibility if you end up bricking anything. As you can see above, there are several things, that if you break them, can only be fixed with hardware programmer + keys from xyzzy.

Now do keep in mind though, if you DO brick your WiiMode vWii, Wii U mode will still function fine, you will just no longer have any Wii Backwards Compatibility though. But still, hopefully this still does not happen to you.

Long story short, all that is needed is some education, plus awareness of what could happen, and some common sense.
Having those unique per-console keys helps too :P
Especially since: performing any sort of "unauthorized technical modifications", AKA any of this, will void your console's warranty! Remember that too.]]> Safe (should be ok to run without worry):
- homebrew that does not install anything or require installation, or even better, ones that do not write to NAND at all
- installing The Homebrew Channel. While this does install to NAND, this is the most reputable of all Wii homebrew launchers, and the authors (Team Twiizers) make sure it is as safe as possible before they release it.

Potential risk of brick but still more or less doable (make sure you have a NAND backup, or at the very least a key dump from the modified xyzzy + hardware programmer):
- Installing channel wads (same reason as on regular Wii, mainly only if they have a bad banner or something, otherwise if they are confirmed ok, then they should be safe)
- Installing non-critical system parts, like game IOS, patched IOS, or cIOS into unused slots (such as d2x v10 vWii version), as long as one is installing vWii versions only on vWii, and regular Wii versions only on regular Wii (they are not used by System Menu and should be fine to remove and reinstall if you screw them up)
- Modifying 1-513 "BC-WFS". According to crediar, this is used by vWii to be able to load up and give compatibility to Dragon Quest X. Dragon Quest uses it's own "WFS" formatted USB drive, so that is probably why. BC-WFS is encrypted, so it cannot be successfully modified until the encryption is publicly cracked. But messing it up should not harm anything on vWii other than Dragon Quest X.

Will brick if you do it wrong, you can do these [b]BUT[/b] only do if you know EXACTLY what you are doing: (a NAND dump, and at the very least a xyzzy key dump + hardware programmer will be the ONLY thing to save you if you screw up, due to no bootmii as boot2 on vWii)
- Modifying System Menu IOS in any way (is currently IOS80)
- Modifying 1-512 "BC-NAND". According to crediar, this title is needed by vWii to be able to load NAND titles, like channels. Messing this up would break channel loading, which is no good, but disc games should still work. Breaking this would be harder to fix due to the inability to load channels. It is also encrypted, so cannot be successfully modified until the encryption is publicly cracked.

DO NOT do, this stuff is just plain stupid and confirmed as not working and brick causing:
- Installing regular Wii IOS on vWii. Installing non-critical IOS will result in those IOS having very limited functionality and crashing very easily, installing old System Menu IOS (IOS 80 atm) will cause vWii to brick.
- Installing vWii IOS on regular Wii. This actually seems worse than the inverse. While Wii IOS maybe actually load up on vWii but still crash when trying anything, vWii IOS on regular Wii will not work at all. Also, users have reported very strange Wii bricks (among them being myself and FIX94) from installing vWii IOS on them, even non-critical ones... I have no clue why they do this, but new IOS for new hardware, there has got to be a reason somewhere.
- Installing vWii IOS wad files on vWii packed from a vWii NAND dump using a program on your PC. The program used to create the Wad file is fake signing the ticket. While it install fine and seems to works fine on vWii, it bricks the Update feature of the WiiU Mode, and prevent reinstalling The Homebrew Channel on vWii!
- Installing older IOS, or stub IOS, or deleting IOS that you do not want anymore.
- Modifying vWii System Menu in any way, including priiloader or "themes". Do not modify the System Menu's .dol, it has extra encryption that has not been publicly cracked yet. Also cannot install priiloader for the same reason. Since vWii System Menu is not the same as regular Wii's System menu, regular Wii "themes" are not compatible, and will brick vWii. AFAIK there are no vWii themes released at this time, and I myself am unsure about making or installing my own myself, as I have not tried it yet.
- Deleting The Homebrew Channel if it doesn't work anymore. The homebrew channel is not working because you messed the IOSes. The Homebrew Channel is working fine, do not ever delete it! it's your most easiest way to restore and fix a bricked vWii. If you delete The Homebrew Channel, it will be harder to fix your console.
- Deleting Forwarder Channels if you bricked your vWii. Same as The Homebrew Channel, a forwarder can be found useful to unbrick your console. Don't delete ANYTHING if you think your console is not working. Ask to other users on the forum first. It will save your console.
- Trying to do or install anything at all if you do not know what you are doing, seriously, read up and learn about everything before attempting to mod anything, this should be a given!

What is recommended to do:
- Install The Homebrew Channel.
- Then run the modified xyzzy v1.2.1 unnofficial provided by DarkMatterCore on your vWii via HBC. It will dump your vWii's unique per-console encryption keys that are needed to decrypt and re-encrypt a dump of your vWii's NAND on PC, useful in case if you brick vWii, you can (or send it to someone who can) dump the vWii's NAND into PC using a hardware programmer, like an Infectus (no longer manufactured) or Progskeet, and then decrypt it to alter it and fix it, then re--encrypt and reflash the fixed NAND dump onto the vWii's NAND chip. Especially useful due to there not being any vWii version of BootMii.
- Educate yourself on whatever it is you want to do before doing it, do not just follow guides without learning about what each part does. Be lazy and you could pay the price for it someday!
- Again, only mess around with important stuff if you know EXACTLY what you are doing beforehand. It is your own responsibility if you end up bricking anything. As you can see above, there are several things, that if you break them, can only be fixed with hardware programmer + keys from xyzzy.

Now do keep in mind though, if you DO brick your WiiMode vWii, Wii U mode will still function fine, you will just no longer have any Wii Backwards Compatibility though. But still, hopefully this still does not happen to you.

Long story short, all that is needed is some education, plus awareness of what could happen, and some common sense.
Having those unique per-console keys helps too :P
Especially since: performing any sort of "unauthorized technical modifications", AKA any of this, will void your console's warranty! Remember that too.]]> <![CDATA[Getting Started With Wii Homebrew Channel (Letterbomb)]]> https://sickgaming.net/thread-82781.html Thu, 01 Jan 2015 19:57:26 -0200 xSicKx]]> https://sickgaming.net/thread-82781.html
First off, you should (hopefully) already know that the Homebrew Channel is simply a loader of homebrew, it doesn't do an awful lot by itself. You need to download at least one homebrew app and put it on your SD card or USB drive before HBC will become truly useful.

A common choice for a first homebrew is the Homebrew Browser, found here: [wiibrew.org] This piece of homebrew connects to the internet and allows you to download other homebrew apps and games. Go ahead and download it from that page. The file you download will be a ZIP archive. Your OS probably includes a tool for extracting ZIP archives. On Windows, you can right click and choose "Extract all".

Inside, you will find a folder called "homebrew_browser". Within this folder are a few files: the file called "boot.dol" is the actual app itself, the file called "icon.png" is the icon that will be displayed in HBC and the file called "meta.xml" contains a few details about the app (name, author, description etc.) that will be displayed in HBC. The other files are used by Homebrew Browser. Most apps you download will have boot.dol, icon.png and meta.xml, although the only essential file is boot.dol (or sometimes boot.elf, depending on the app).

Now on either an SD card or a USB drive, create a folder called "apps". Make sure this folder is not within any other folders, and also make sure the name is all in lowercase letters.

Next copy the "homebrew_browser" folder into the "apps" folder.

Connect your SD/USB device to your Wii and load HBC. If using a USB device, you may need to press 1 on the Wii Remote and change the storage device being used. You should see the Homebrew Browser appearing. Click it and choose "Load".

Enjoy.]]>
First off, you should (hopefully) already know that the Homebrew Channel is simply a loader of homebrew, it doesn't do an awful lot by itself. You need to download at least one homebrew app and put it on your SD card or USB drive before HBC will become truly useful.

A common choice for a first homebrew is the Homebrew Browser, found here: [wiibrew.org] This piece of homebrew connects to the internet and allows you to download other homebrew apps and games. Go ahead and download it from that page. The file you download will be a ZIP archive. Your OS probably includes a tool for extracting ZIP archives. On Windows, you can right click and choose "Extract all".

Inside, you will find a folder called "homebrew_browser". Within this folder are a few files: the file called "boot.dol" is the actual app itself, the file called "icon.png" is the icon that will be displayed in HBC and the file called "meta.xml" contains a few details about the app (name, author, description etc.) that will be displayed in HBC. The other files are used by Homebrew Browser. Most apps you download will have boot.dol, icon.png and meta.xml, although the only essential file is boot.dol (or sometimes boot.elf, depending on the app).

Now on either an SD card or a USB drive, create a folder called "apps". Make sure this folder is not within any other folders, and also make sure the name is all in lowercase letters.

Next copy the "homebrew_browser" folder into the "apps" folder.

Connect your SD/USB device to your Wii and load HBC. If using a USB device, you may need to press 1 on the Wii Remote and change the storage device being used. You should see the Homebrew Browser appearing. Click it and choose "Load".

Enjoy.]]> <![CDATA[How to Hack your Wii using LetterBomb (Fast and easy) Tutorial]]> https://sickgaming.net/thread-57670.html Tue, 18 Mar 2014 01:52:11 -0200 xSicKx]]> https://sickgaming.net/thread-57670.html LetterBomb, which is an incredibly simple way to hack your Wii. It only takes about five minutes to accomplish. Here's how to do it.

First things first, you are going to need the following:

A Nintendo Wii, obviously, but make sure it's running System Menu 4.3
An SD or SDHC card with some free space—it can have other stuff on it.

Step One: Get Your Wii's MAC Address

Before you can do anything, you need to go find your Wii's MAC Address. Go to your Wii's home screen and click the Wii Options button. Once it loads, choose Wii Settings. From there, navigate to the second page and click the Internet button. Finally, click the Console Information button and you will have your Wii's MAC address. Either write this down or just leave it up on your screen.

Step Two: Generate the LetterBomb.zip File

Now get on your computer and go to

Hidden Content

Reply to this thread to unlock the contents

and enter your Wii's MAC address. You will also need to type in what you see in the captcha image. Once you've filled those things out, cut the red or the blue wire. It doesn't really matter. This will generate a LetterBomb.zip file that will start downloading.

Step Three: Prepare the SD Card

Now insert your SD or SDHC card into your computer, because we're going to need to copy some files onto it. First, unzip the LetterBomb.zip file on your computer. Next, drag the contents of the zip to your SD or SDHC card. When it's done copying, eject it, and put it in your Wii.

Step Four: Open the LetterBomb

Back on the Wii, head on over to the Wii Message Center. There's going to be a new message for you with a bomb in it, but where that message is going to be will depend on your time zone and when you generated the file. In most cases, it will be in yesterday's mail, but it could be today or a couple of days ago. You'll know when you see it. When you're ready to pull the trigger, just click on the LetterBomb message icon. The process will take about a minute, so be patient. You'll have a hacked Wii when it's done.

If you run into any issues along the way it's probably because you don't have the right version of the Wii System Menu. If you try to use LetterBomb with the wrong version, it'll freeze your Wii. Not to worry—just force-reboot your Wii, make sure you update properly, and try again. Obviously you want to do the update beforehand, but in the event you forget it's not really a big deal.

Step Five: Install BootMii and the Homebrew Channel

Once LetterBomb is done, it will tell you to press 1 to continue. Do that and you'll be able to use your WiiMote to start installing things. What you're really interested in is the Homebrew Channel, but BootMii will provide you with some extra features (like backup). Once everything is installed, you'll be all set.

And it's that simple guys!

Thanks is appreciated.

xSicKxSkiLLs]]> LetterBomb, which is an incredibly simple way to hack your Wii. It only takes about five minutes to accomplish. Here's how to do it.

First things first, you are going to need the following:

A Nintendo Wii, obviously, but make sure it's running System Menu 4.3
An SD or SDHC card with some free space—it can have other stuff on it.

Step One: Get Your Wii's MAC Address

Before you can do anything, you need to go find your Wii's MAC Address. Go to your Wii's home screen and click the Wii Options button. Once it loads, choose Wii Settings. From there, navigate to the second page and click the Internet button. Finally, click the Console Information button and you will have your Wii's MAC address. Either write this down or just leave it up on your screen.

Step Two: Generate the LetterBomb.zip File

Now get on your computer and go to

Hidden Content

Reply to this thread to unlock the contents