Hacks Guide Wiki - User contributions [en]

User:Kuhprii/History on the DS hacking scene

2025-04-25T19:10:39Z

Abdelali221:

Sources:

* https://gbatemp.net/threads/wondering-about-the-timeline-of-ds-hacking.663789/

* https://darkfader.blogspot.com/2005/

* https://pineight.com/ds/pass/#passme

* https://www.gameboy-advance.net/nintendo_ds/passme.htm

== The Release of the Nintendo DS ==
The Nintendo DS released November 21st, of 2004.

== 2005 ==

=== The first pass-through (January) ===
The developer DarkFader gets his hands on the Nintendo DS, he wants to hack it. Others in the community started to capture to traffic of the cartridge (I assume Metroid Demo). DarkFader then saw header data, as well as encrypted data. He then figured that the RSA on the back, didn't apply to the actual cartridge.

He then programmed an FPGA to make a pass-through that would let him capture and alter the data traffic from the cartridge. DarkFader made an etched PCB that went into the DS, and a cut GBC connecter that held a DS cartridge. He then altered the header and figured out he could run his own code from the Game Boy Advance slot.

Once he could run his own code, he made a program that modified a string of text in the Metroid Demo, and then continued executing. That was the first pass-through.

=== The first PassMe device (February) ===
A developer by the name of Natrium42 makes a pass-through based on DarkFader's FPGA. It is similar to a Game-Genie. It was pretty much the same as DarkFaders's FGPA, as it altered NDS cartridge header data, changing the run address points to the GBA slot. The main difference was that PassMe was more refined.

=== WiFiMe (April) ===
WiFiMe brought new ways to run homebrew. It ran through DS Download Play. This method required a specific wireless network card (Ralink RT2560). You also would need a program called WMB (Wireless Multiboot), that program uploads the homebrew to the console using DS Download Play. All of this works because the first version of DS Download Play used a run address from a header that wasn't located with the rest of the digitally signed code. WiFiMe specifically is a DS Download Play program that was extracted from SM64DS, it had it's run address changed to the GBA slot. This allowed WMB to act as DS, allowing you to send signed programs over to the DS.<blockquote>Note: Needs to be rewritten?</blockquote>

=== FlashMe (Spring, Unknown Month) ===
FlashMe is a modified version of the Nintendo DS firmware that checks the Game Boy Advance slot for DS code, and booting it if it is present. It also removes the signature check in DS Download Play, allowing users to send programs that didn't have Nintendo signatures via WMB.

=== Nintendo's fixes ===
Nintendo fixes the vulnerabilities present in firmware version 4. They added range checks to the DS card startup code which blocked PassMe devices. They also used a new run address in the signed section of DS Download Play blocking WiFiMe. The BIOS still has a vulnerability that allowed redirection of execution to the GBA SRAM space. It was also discovered that Nintendo Wi-Fi code overwrites an area of the firmware. The original FlashMe developers didn't know this and Mario Kart DS was bricking people's consoles.

=== PPFlash (Add later, Unknown month and season) ===
filler

=== PassMe2 (October) ===
PassMe2 is on the same hardware as the original, but there is a new program on the CPLD. What this program does is changes the header's run address to a BIOS call that goes to shellcode in the GBA SRAM. (Maybe add more)

User:Kuhprii/History on the Wii hacking scene

2025-04-18T19:16:41Z

Abdelali221: Abdelali221 moved page User:Kuhprii/History on the Wii hacking scene to Wii:History on the Wii hacking scene

#REDIRECT [[Wii:History on the Wii hacking scene]]

Wii:History on the Wii hacking scene

2025-04-18T19:16:41Z

Abdelali221: Abdelali221 moved page User:Kuhprii/History on the Wii hacking scene to Wii:History on the Wii hacking scene

=== 1 - How it started ===
The Wii Homebrew story started with the Team Twiizers, their name came from the exploit they made: The Tweezers attack.

==== How It Works: ====
The Tweezer attack takes advantage of how the Wii transitions into GameCube mode. During this process, the console clears a specific memory bank to prepare for the switch, but the team found that there's still some residual data on the other banks. They realised that they can use tweezers to short data lines and switch between memory banks, and gain access to this residual data. This led to the extraction of the Wii’s encryption keys.

==== The First Homebrew-ish: ====
With the encryption keys in hand, Bushing developed the first homebrew for the Wii: a Wii Remote monitor. This was achieved by modifying the Lego Star Wars game to execute custom code. A demonstration of this achievement is available on the WiiDatabase YouTube channel.

=== 2 - The Riivolution ===
Following the discovery of an exploit in ''The Legend of Zelda: Twilight Princess'' (known as the Twilight Hack), homebrew installation became significantly more accessible. This breakthrough led to the creation of the renowned '''Homebrew Channel'''—a dedicated Wii application that streamlined the process of launching homebrew software. Users simply had to copy files onto an SD card, and their homebrew applications would appear on the console’s menu.

==== HackMii Installer and BootMii: ====
Installing the Homebrew Channel required the '''HackMii Installer''', developed by Team Twiizers. This installer also included '''BootMii''', a software designed for brick prevention.

BootMii could be installed in two ways:

* '''As Boot2:''' A safer and highly effective method that could prevent bricks, but was only available if you have a vunerable Boot1.
* '''As an IOS (IOS 254):''' A method compatible with all Wiis (excluding vWiis), though less reliable for brick prevention.

BootMii’s main functions were NAND backup and brick recovery, managed through '''CEIL1NG_CAT''', the user interface falsely thought as being BootMii itself.

=== 3 - Homebrew and Piracy: An Ongoing Debate ===
The term "homebrew" is often associated with piracy, as unauthorized software modifications sometimes lead to illegal activity. The Wii was no exception.

==== Wanikoko's WAD Manager: ====
Piracy within the Wii community began with '''Wanikoko''' and his WAD Installer, which evolved into '''WAD Uninstaller''' and later '''WAD Manager'''. This tool allowed users to share Virtual Console (VC) and WiiWare WAD files online, leading to the spread of Wii games piracy.

==== cIOS and Backup Loaders: ====
Wanikoko’s '''cIOSes''' (custom IOSes) enabled Wii consoles to boot games from backups using loaders such as '''Neogamma''', which was the most popular option at the time. Despite being intended for legitimate personal backups, it facilitated game piracy.

=== 3.1 - Nintendo WFC and Online Cheating ===
Homebrew made cheating in online games remarkably easy. Tools like '''GeckoLoader''' allowed players to manipulate game mechanics, leading to severe unfairness and disrupting the experience for others. As a result, some Wii games became practically unplayable online due to high levels of cheating.

=== 4 - Evolution of Homebrew Since 2008 ===

==== '''2008''' ====

* Wanikoko released several tools, including the '''WAD Manager''' and '''SD/USB loader'''.

==== '''2009''' ====

* The '''Homebrew Browser''' was introduced, allowing users to download homebrew apps directly from their Wii.

==== '''2010''' ====

* '''Priiloader''' was released, providing additional brick protection and system menu hacks.

==== '''2011''' ====

* '''LetterBomb''', a new exploit that didn’t require a game disc, was discovered, making homebrew installation even easier.

==== '''2012''' ====

* The '''D2X cIOS''' project gained traction, improving compatibility with backup loaders.

==== '''2013''' ====

* The '''Devolution''' project was launched, allowing GameCube games to be played on the Wii without requiring a disc.

==== '''2014''' ====

* '''Nintendo WFC was shut down''', marking the end of official online multiplayer.
* '''Wiimmfi''' was launched, bringing online play back to the Wii community.

==== '''2015''' ====
* '''D2X cIOS''' was officially released, improving game compatibility and performance.

===== August 5th =====

*'''RiiConnect24''' began, with the '''News Channel''' being the first service to be revived.

In memory of Ben Byer (Bushing), who passed away on Monday, February 8th, 2016.

Wii:History on the Wii hacking scene

2025-04-18T19:11:56Z

Abdelali221:

Wii:History on the Wii hacking scene

2025-04-18T18:38:13Z

Abdelali221:

=== 1 - The Beginning: A Quick Look at Wii Hacking ===
The story of Wii homebrew begins with Team Twiizers (later known as fail0verflow), whose name originates from the exploit they pioneered—the Tweezer attack.

==== How It Works: ====
The Tweezer attack takes advantage of how the Wii transitions into GameCube mode. During this process, the system wipes a specific memory bank to prepare for the switch, but remnants of data still linger. Team Twiizers used physical tweezers to short data lines and switch between memory banks, gaining access to this residual data. This ultimately led to the extraction of the Wii’s encryption keys.

==== The First Steps Toward Homebrew: ====
With the encryption keys in hand, Bushing developed the first homebrew for the Wii: a Wii Remote monitor. This was achieved by modifying the Lego Star Wars game to execute custom code. A demonstration of this achievement is available on the WiiDatabase YouTube channel.

=== 2 - Riivolution: The Rise of Homebrew ===
Following the discovery of an exploit in ''The Legend of Zelda: Twilight Princess'' (known as the Twilight Hack), homebrew installation became significantly more accessible. This breakthrough led to the creation of the renowned '''Homebrew Channel'''—a dedicated Wii application that streamlined the process of launching homebrew software. Users simply had to copy files onto an SD card, and their homebrew applications would appear on the console’s menu.

==== HackMii Installer and BootMii: ====
Installing the Homebrew Channel required the '''HackMii Installer''', developed by Team Twiizers. This installer also included '''BootMii''', a software designed for brick prevention.

BootMii could be installed in two ways:

* '''As Boot2:''' A safer and highly effective method that could prevent bricks, but was only compatible with older Wii consoles.
* '''As an IOS (IOS 254):''' A method compatible with all Wiis (excluding vWiis), though less reliable for brick prevention.

BootMii’s main functions were NAND backup and brick recovery, managed through '''CEIL1NG_CAT''', the user interface often mistaken for BootMii itself.

=== 3 - Homebrew and Piracy: An Ongoing Debate ===
The term "homebrew" is often associated with piracy, as unauthorized software modifications sometimes lead to illegal activity. The Wii was no exception.

==== WAD Manager and Game Piracy: ====
Piracy within the Wii community began with '''Wanikoko''' and his WAD Installer, which evolved into '''WAD Uninstaller''' and later '''WAD Manager'''. This tool allowed users to share Virtual Console (VC) and WiiWare WAD files online, leading to widespread game piracy.

==== cIOS and Backup Loaders: ====
Wanikoko’s '''cIOSes''' (custom IOSes) enabled Wii consoles to boot games from backups using loaders such as '''Neogamma''', which was the most popular option at the time. Though originally intended for legitimate personal backups, this technology also facilitated game piracy.

=== 3.1 - Nintendo WFC and Online Cheating ===
Homebrew made cheating in online games remarkably easy. Tools like '''GeckoLoader''' allowed players to manipulate game mechanics, leading to severe unfairness and disrupting the experience for others. As a result, some Wii games became practically unplayable online due to rampant cheating.

=== 4 - Evolution of Homebrew Since 2008 ===

==== '''2008''' ====

* Wanikoko released several tools, including the '''WAD Manager''' and '''SD/USB loader'''.

==== '''2009''' ====

* The '''Homebrew Browser''' was introduced, allowing users to download homebrew apps directly from their Wii.

==== '''2010''' ====

* '''Priiloader''' was released, providing additional brick protection and system menu hacks.

==== '''2011''' ====

* '''LetterBomb''', a new exploit that didn’t require a game disc, was discovered, making homebrew installation even easier.

==== '''2012''' ====

* The '''D2X cIOS''' project gained traction, improving compatibility with backup loaders.

==== '''2013''' ====

* The '''Devolution''' project was launched, allowing GameCube games to be played on the Wii without requiring a disc.

==== '''2014''' ====

* '''Nintendo WFC was shut down''', marking the end of official online multiplayer.
* '''Wiimmfi''' was launched, bringing online play back to the Wii community.

==== '''2015''' ====
* '''D2X cIOS''' was officially released, improving game compatibility and performance.

===== August 5th =====

*'''RiiConnect24''' began, with the '''News Channel''' being the first service to be revived.

In memory of Ben Byer (Bushing), who passed away on Monday, February 8th, 2016.

Wii:History on the Wii hacking scene

2025-04-18T18:25:32Z

Abdelali221:

=== 1 - The Beginning: A Quick Look at Wii Hacking ===
The story of Wii homebrew begins with Team Twiizers (later known as fail0verflow), whose name originates from the exploit they pioneered—the Tweezer attack.

==== How It Works: ====
The Tweezer attack takes advantage of how the Wii transitions into GameCube mode. During this process, the system wipes a specific memory bank to prepare for the switch, but remnants of data still linger. Team Twiizers used physical tweezers to short data lines and switch between memory banks, gaining access to this residual data. This ultimately led to the extraction of the Wii’s encryption keys.

==== The First Steps Toward Homebrew: ====
With the encryption keys in hand, Bushing developed the first homebrew for the Wii: a Wii Remote monitor. This was achieved by modifying the Lego Star Wars game to execute custom code. A demonstration of this achievement is available on the WiiDatabase YouTube channel.

=== 2 - Riivolution: The Rise of Homebrew ===
Following the discovery of an exploit in ''The Legend of Zelda: Twilight Princess'' (known as the Twilight Hack), homebrew installation became significantly more accessible. This breakthrough led to the creation of the renowned '''Homebrew Channel'''—a dedicated Wii application that streamlined the process of launching homebrew software. Users simply had to copy files onto an SD card, and their homebrew applications would appear on the console’s menu.

==== HackMii Installer and BootMii: ====
Installing the Homebrew Channel required the '''HackMii Installer''', developed by Team Twiizers. This installer also included '''BootMii''', a software designed for brick prevention.

BootMii could be installed in two ways:

* '''As Boot2:''' A safer and highly effective method that could prevent bricks, but was only compatible with older Wii consoles.
* '''As an IOS (IOS 254):''' A method compatible with all Wiis (excluding vWiis), though less reliable for brick prevention.

BootMii’s main functions were NAND backup and brick recovery, managed through '''CEIL1NG_CAT''', the user interface often mistaken for BootMii itself.

=== 3 - Homebrew and Piracy: An Ongoing Debate ===
The term "homebrew" is often associated with piracy, as unauthorized software modifications sometimes lead to illegal activity. The Wii was no exception.

==== WAD Manager and Game Piracy: ====
Piracy within the Wii community began with '''Wanikoko''' and his WAD Installer, which evolved into '''WAD Uninstaller''' and later '''WAD Manager'''. This tool allowed users to share Virtual Console (VC) and WiiWare WAD files online, leading to widespread game piracy.

==== cIOS and Backup Loaders: ====
Wanikoko’s '''cIOSes''' (custom IOSes) enabled Wii consoles to boot games from backups using loaders such as '''Neogamma''', which was the most popular option at the time. Though originally intended for legitimate personal backups, this technology also facilitated game piracy.

=== 3.1 - Nintendo WFC and Online Cheating ===
Homebrew made cheating in online games remarkably easy. Tools like '''GeckoLoader''' allowed players to manipulate game mechanics, leading to severe unfairness and disrupting the experience for others. As a result, some Wii games became practically unplayable online due to rampant cheating.

=== 4 - Evolution of Homebrew Since 2008 ===

==== '''2008''' ====

* Wanikoko released several tools, including the '''WAD Manager''' and '''SD/USB loader'''.

==== '''2009''' ====

* The '''Homebrew Browser''' was introduced, allowing users to download homebrew apps directly from their Wii.

==== '''2010''' ====

* '''Priiloader''' was released, providing additional brick protection and system menu hacks.

==== '''2011''' ====

* '''LetterBomb''', a new exploit that didn’t require a game disc, was discovered, making homebrew installation even easier.

==== '''2012''' ====

* The '''D2X cIOS''' project gained traction, improving compatibility with backup loaders.

==== '''2013''' ====

* The '''Devolution''' project was launched, allowing GameCube games to be played on the Wii without requiring a disc.

==== '''2014''' ====

* '''Nintendo WFC was shut down''', marking the end of official online multiplayer.
* '''Wiimmfi''' was launched, bringing online play back to the Wii community.

==== '''2015''' ====

* '''D2X cIOS''' was officially released, improving game compatibility and performance.

===== August 5th =====

* '''RiiConnect24''' began, with the '''News Channel''' being the first service to be revived.

Wii:History on the Wii hacking scene

2025-04-18T18:03:10Z

Abdelali221: /* August 5th */

== 1 - A quick look at the beginning ==
The Wii hacking story started with Team Twiizers (A.K.A fail0verflow), their name came from the exploit they used... The Tweezer attack!

==== How it works: ====
Let's see how the Tweezer attack works, when the Wii switches to the GameCube mode it prepares the memory first by cleaning a specific bank of it, but the problem with that is that there is still some residual data left! The Team Twiizers used tweezers to switch between memory banks by shorting some data lines, which enabled them to access the residual data referred to earlier, which finally lead to them getting the encryption keys.

===== The First Homebrew-ish: =====
Now with the encryption keys in his hands, Bushing made the first homebrew for the Wii, which consist of a Wii Remote monitor. It was a modified version of the Lego Star Wars game released on the Wii which ran custom code made by him.

A video demonstrating that is available on the WiiDatabase YouTube channel.

== 2 - The Riivolution ==
After the discovery of an exploit with the game The Legend Of Zelda : Twilight Princess (A.K.A Twilight hack), Wii homebrew became easy to setup, which lead to the creation of the famous Homebrew Channel. This is a channel that you would install on your console to make launching homebrews way easier, just copy the files to an SD card and your homebrew will appear on the screen.

Installing the homebrew channel was done using the Hackmii Installer, an app developed by Team Twiizers, BootMii was also included in the Hackmii Installer.

BootMii is a software that's used as a brick prevention tool, you can either install it as Boot2 (The third Wii boot stage, way safer and brick preventive.) It requires an old enough Wii, or as an IOS (Specifically IOS 254) which is compatible with all Wiis (vWiis are NOT compatible), but it's less efficient for preventing bricks. The main uses of BootMii are : NAND dumping and Brick recovery, these are done using CEIL1NG_CAT (The user interface, wrongly thought as being BootMii itself).

=== 3 - Homebrew and piracy, a long story ===
When hearing the word homebrew the first thing that comes in mind is piracy (Piracy being a biproduct of homebrew). The Wii didn't escape this rule, piracy started with Wanikoko and their homebrew WAD Installer, which later became WAD Uninstaller and finally changed to WAD Manager. This tool enabled sharing VC and WiiWare WADs between people on the internet.

After that came Wanikoko's cIOSes, these are customized IOSes which enable loading backups using a loader such as Neogamma (Which was the best loader at the time), and they were intended to load your own backups, but lead to sharing pirated games again.

=== 3.1 - The Nintendo WFC and Cheating ===
Cheating became incredibly easy with homebrews (With GeckoLoader for example), and this made online games unplayable because of the unfairness that came with cheat codes.

=== 4 - How it evolved since 2008 ===

== 2008 ==
Wanikoko released several tools, such as his famous Wad manager, SD/USB loader?.

== 2009 ==
No data (yet).

== 2010 ==
No data (yet).

== 2011 ==
No data (yet).

== 2012 ==
No data (yet).

== 2013 ==
No data (yet).

== 2014 ==
2014 marks the end of the Nintendo WFC, and the beginning of Wiimmfi!

== 2015 ==
D2X CIOs was released.

===== August 5th =====
RiiConnect24 began, the News Channel was the first channel to be revived.

Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/

https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/

probably check failoverflow

Wii:History on the Wii hacking scene

2025-04-18T18:02:37Z

Abdelali221: /* 2015 */

== 1 - A quick look at the beginning ==
The Wii hacking story started with Team Twiizers (A.K.A fail0verflow), their name came from the exploit they used... The Tweezer attack!

==== How it works: ====
Let's see how the Tweezer attack works, when the Wii switches to the GameCube mode it prepares the memory first by cleaning a specific bank of it, but the problem with that is that there is still some residual data left! The Team Twiizers used tweezers to switch between memory banks by shorting some data lines, which enabled them to access the residual data referred to earlier, which finally lead to them getting the encryption keys.

===== The First Homebrew-ish: =====
Now with the encryption keys in his hands, Bushing made the first homebrew for the Wii, which consist of a Wii Remote monitor. It was a modified version of the Lego Star Wars game released on the Wii which ran custom code made by him.

A video demonstrating that is available on the WiiDatabase YouTube channel.

== 2 - The Riivolution ==
After the discovery of an exploit with the game The Legend Of Zelda : Twilight Princess (A.K.A Twilight hack), Wii homebrew became easy to setup, which lead to the creation of the famous Homebrew Channel. This is a channel that you would install on your console to make launching homebrews way easier, just copy the files to an SD card and your homebrew will appear on the screen.

Installing the homebrew channel was done using the Hackmii Installer, an app developed by Team Twiizers, BootMii was also included in the Hackmii Installer.

BootMii is a software that's used as a brick prevention tool, you can either install it as Boot2 (The third Wii boot stage, way safer and brick preventive.) It requires an old enough Wii, or as an IOS (Specifically IOS 254) which is compatible with all Wiis (vWiis are NOT compatible), but it's less efficient for preventing bricks. The main uses of BootMii are : NAND dumping and Brick recovery, these are done using CEIL1NG_CAT (The user interface, wrongly thought as being BootMii itself).

=== 3 - Homebrew and piracy, a long story ===
When hearing the word homebrew the first thing that comes in mind is piracy (Piracy being a biproduct of homebrew). The Wii didn't escape this rule, piracy started with Wanikoko and their homebrew WAD Installer, which later became WAD Uninstaller and finally changed to WAD Manager. This tool enabled sharing VC and WiiWare WADs between people on the internet.

After that came Wanikoko's cIOSes, these are customized IOSes which enable loading backups using a loader such as Neogamma (Which was the best loader at the time), and they were intended to load your own backups, but lead to sharing pirated games again.

=== 3.1 - The Nintendo WFC and Cheating ===
Cheating became incredibly easy with homebrews (With GeckoLoader for example), and this made online games unplayable because of the unfairness that came with cheat codes.

=== 4 - How it evolved since 2008 ===

== 2008 ==
Wanikoko released several tools, such as his famous Wad manager, SD/USB loader?.

== 2009 ==
No data (yet).

== 2010 ==
No data (yet).

== 2011 ==
No data (yet).

== 2012 ==
No data (yet).

== 2013 ==
No data (yet).

== 2014 ==
2014 marks the end of the Nintendo WFC, and the beginning of Wiimmfi!

== 2015 ==
D2X CIOs was released.

===== August 5th =====
RiiConnect24 began with the News Channel.

Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/

https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/

probably check failoverflow

Wii:History on the Wii hacking scene

2025-04-18T17:38:57Z

Abdelali221: /* Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/ */

== 1 - A quick look at the beginning ==
The Wii hacking story started with Team Twiizers (A.K.A fail0verflow), their name came from the exploit they used... The Tweezer attack!

==== How it works: ====
Let's see how the Tweezer attack works, when the Wii switches to the GameCube mode it prepares the memory first by cleaning a specific bank of it, but the problem with that is that there is still some residual data left! The Team Twiizers used tweezers to switch between memory banks by shorting some data lines, which enabled them to access the residual data referred to earlier, which finally lead to them getting the encryption keys.

===== The First Homebrew-ish: =====
Now with the encryption keys in his hands, Bushing made the first homebrew for the Wii, which consist of a Wii Remote monitor. It was a modified version of the Lego Star Wars game released on the Wii which ran custom code made by him.

A video demonstrating that is available on the WiiDatabase YouTube channel.

== 2 - The Riivolution ==
After the discovery of an exploit with the game The Legend Of Zelda : Twilight Princess (A.K.A Twilight hack), Wii homebrew became easy to setup, which lead to the creation of the famous Homebrew Channel. This is a channel that you would install on your console to make launching homebrews way easier, just copy the files to an SD card and your homebrew will appear on the screen.

Installing the homebrew channel was done using the Hackmii Installer, an app developed by Team Twiizers, BootMii was also included in the Hackmii Installer.

BootMii is a software that's used as a brick prevention tool, you can either install it as Boot2 (The third Wii boot stage, way safer and brick preventive.) It requires an old enough Wii, or as an IOS (Specifically IOS 254) which is compatible with all Wiis (vWiis are NOT compatible), but it's less efficient for preventing bricks. The main uses of BootMii are : NAND dumping and Brick recovery, these are done using CEIL1NG_CAT (The user interface, wrongly thought as being BootMii itself).

=== 3 - Homebrew and piracy, a long story ===
When hearing the word homebrew the first thing that comes in mind is piracy (Piracy being a biproduct of homebrew). The Wii didn't escape this rule, piracy started with Wanikoko and their homebrew WAD Installer, which later became WAD Uninstaller and finally changed to WAD Manager. This tool enabled sharing VC and WiiWare WADs between people on the internet.

After that came Wanikoko's cIOSes, these are customized IOSes which enable loading backups using a loader such as Neogamma (Which was the best loader at the time), and they were intended to load your own backups, but lead to sharing pirated games again.

=== 3.1 - The Nintendo WFC and Cheating ===
Cheating became incredibly easy with homebrews (With GeckoLoader for example), and this made online games unplayable because of the unfairness that came with cheat codes.

=== 4 - How it evolved since 2008 ===

== 2008 ==
Wanikoko released several tools, such as his famous Wad manager, SD/USB loader?.

== 2009 ==
No data (yet).

== 2010 ==
No data (yet).

== 2011 ==
No data (yet).

== 2012 ==
No data (yet).

== 2013 ==
No data (yet).

== 2014 ==
2014 marks the end of the Nintendo WFC, and the beginning of Wiimmfi!

== 2015 ==
D2X CIOs was released.

Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/

https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/

probably check failoverflow

Wii:History on the Wii hacking scene

2025-04-18T17:38:34Z

Abdelali221:

== 1 - A quick look at the beginning ==
The Wii hacking story started with Team Twiizers (A.K.A fail0verflow), their name came from the exploit they used... The Tweezer attack!

==== How it works: ====
Let's see how the Tweezer attack works, when the Wii switches to the GameCube mode it prepares the memory first by cleaning a specific bank of it, but the problem with that is that there is still some residual data left! The Team Twiizers used tweezers to switch between memory banks by shorting some data lines, which enabled them to access the residual data referred to earlier, which finally lead to them getting the encryption keys.

===== The First Homebrew-ish: =====
Now with the encryption keys in his hands, Bushing made the first homebrew for the Wii, which consist of a Wii Remote monitor. It was a modified version of the Lego Star Wars game released on the Wii which ran custom code made by him.

A video demonstrating that is available on the WiiDatabase YouTube channel.

== 2 - The Riivolution ==
After the discovery of an exploit with the game The Legend Of Zelda : Twilight Princess (A.K.A Twilight hack), Wii homebrew became easy to setup, which lead to the creation of the famous Homebrew Channel. This is a channel that you would install on your console to make launching homebrews way easier, just copy the files to an SD card and your homebrew will appear on the screen.

Installing the homebrew channel was done using the Hackmii Installer, an app developed by Team Twiizers, BootMii was also included in the Hackmii Installer.

BootMii is a software that's used as a brick prevention tool, you can either install it as Boot2 (The third Wii boot stage, way safer and brick preventive.) It requires an old enough Wii, or as an IOS (Specifically IOS 254) which is compatible with all Wiis (vWiis are NOT compatible), but it's less efficient for preventing bricks. The main uses of BootMii are : NAND dumping and Brick recovery, these are done using CEIL1NG_CAT (The user interface, wrongly thought as being BootMii itself).

=== 3 - Homebrew and piracy, a long story ===
When hearing the word homebrew the first thing that comes in mind is piracy (Piracy being a biproduct of homebrew). The Wii didn't escape this rule, piracy started with Wanikoko and their homebrew WAD Installer, which later became WAD Uninstaller and finally changed to WAD Manager. This tool enabled sharing VC and WiiWare WADs between people on the internet.

After that came Wanikoko's cIOSes, these are customized IOSes which enable loading backups using a loader such as Neogamma (Which was the best loader at the time), and they were intended to load your own backups, but lead to sharing pirated games again.

=== 3.1 - The Nintendo WFC and Cheating ===
Cheating became incredibly easy with homebrews (With GeckoLoader for example), and this made online games unplayable because of the unfairness that came with cheat codes.

=== 4 - How it evolved since 2008 ===

== 2008 ==
Wanikoko released several tools, such as his famous Wad manager, SD/USB loader?.

== 2009 ==
No data (yet).

== 2010 ==
No data (yet).

== 2011 ==
No data (yet).

== 2012 ==
No data (yet).

== 2013 ==
No data (yet).

== 2014 ==
2014 marks the end of the Nintendo WFC, and the beginning of Wiimmfi!

== 2015 ==
D2X CIOs was released.

== Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/ ==
https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/

probably check failoverflow

Wii:History on the Wii hacking scene

2025-04-18T17:37:41Z

Abdelali221:

== 1 - A quick look at the beginning ==
The Wii hacking story started with Team Twiizers (A.K.A fail0verflow), their name came from the exploit they used... The Tweezer attack!

==== How it works: ====
Let's see how the Tweezer attack works, when the Wii switches to the GameCube mode it prepares the memory first by cleaning a specific bank of it, but the problem with that is that there is still some residual data left! The Team Twiizers used tweezers to switch between memory banks by shorting some data lines, which enabled them to access the residual data referred to earlier, which finally lead to them getting the encryption keys.

===== The First Homebrew-ish: =====
Now with the encryption keys in his hands, Bushing made the first homebrew for the Wii, which consist of a Wii Remote monitor. It was a modified version of the Lego Star Wars game released on the Wii which ran custom code made by him.

A video demonstrating that is available on the WiiDatabase YouTube channel.

== 2 - The Riivolution ==
After the discovery of an exploit with the game The Legend Of Zelda : Twilight Princess (A.K.A Twilight hack), Wii homebrew became easy to setup, which lead to the creation of the famous Homebrew Channel. This is a channel that you would install on your console to make launching homebrews way easier, just copy the files to an SD card and your homebrew will appear on the screen.

Installing the homebrew channel was done using the Hackmii Installer, an app developed by Team Twiizers, BootMii was also included in the Hackmii Installer.

BootMii is a software that's used as a brick prevention tool, you can either install it as Boot2 (The third Wii boot stage, way safer and brick preventive.) It requires an old enough Wii, or as an IOS (Specifically IOS 254) which is compatible with all Wiis (vWiis are NOT compatible), but it's less efficient for preventing bricks. The main uses of BootMii are : NAND dumping and Brick recovery, these are done using CEIL1NG_CAT (The user interface, wrongly thought as being BootMii itself).

=== 3 - Homebrew and piracy, a long story ===
When hearing the word homebrew the first thing that comes in mind is piracy (Piracy being a biproduct of homebrew). The Wii didn't escape this rule, piracy started with Wanikoko and their homebrew WAD Installer, which later became WAD Uninstaller and finally changed to WAD Manager. This tool enabled sharing VC and WiiWare WADs between people on the internet.

After that came Wanikoko's cIOSes, these are customized IOSes which enable loading backups using a loader such as Neogamma (Which was the best loader at the time), and they were intended to load your own backups, but lead to sharing pirated games again.

=== 3.1 - The Nintendo WFC and Cheating ===
Cheating became incredibly easy with homebrews (With GeckoLoader for example), and this made online games unplayable because of the unfairness that came with cheat codes.

=== 4 - How it evolved ===

== 2008 ==
Wanikoko released several tools, such as his famous Wad manager, SD/USB loader?.

== 2009 ==

== 2010 ==

== 2011 ==

== 2012 ==

== 2013 ==

== 2014 ==
2014 marks the end of the Nintendo WFC, and the beginning of Wiimmfi!

== 2015 ==
D2X CIOs was released.

== Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/ ==
https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/

probably check failoverflow

User:Kuhprii

2025-04-18T17:23:18Z

Abdelali221:

[[User:Kuhprii|Kuhprii]] ([[User talk:Kuhprii|talk]])

Hi! I make history pages.

==== My pages: ====

* [[3DS:History_of_3DS_Hacking]] (was originally a userspace under my user, was moved to 3DS space, also revised by fox8091.)*
* [[User:Wariohax/History on the DS hacking scene]] (WIP)
* [[User:Wariohax/History on the Wii hacking scene]] (WIP)

Wii:History on the Wii hacking scene

2025-04-14T15:46:56Z

Abdelali221: added content

== 1 - A quick look at the beginning ==
The Wii hacking story started with Team Twiizers (A.K.A fail0verflow), their name came from the exploit they used... The Tweezer attack!

==== How it works: ====
Let's see how the Tweezer attack works, when the Wii switches to the GameCube mode it prepares the memory first by cleaning a specific bank of it, but the problem with that is that there is still some residual data left! The Team Twiizers used tweezers to switch between memory banks by shorting some data lines, which enabled them to access the residual data referred to earlier, which finally lead to them getting the encryption keys.

===== The First Homebrew-ish: =====
Now with the encryption keys in his hands, Bushing made the first homebrew for the Wii, which consist of a Wii Remote monitor. It was a modified version of the Lego Star Wars game released on the Wii which ran custom code made by him.

A video demonstrating that is available on the WiiDatabase YouTube channel.

== 2 - The Riivolution ==
After the discovery of an exploit with the game The Legend Of Zelda : Twilight Princess (A.K.A Twilight hack), Wii homebrew became easy to setup, which lead to the creation of the famous Homebrew Channel. This is a channel that you would install on your console to make launching homebrews way easier, just copy the files to an SD card and your homebrew will appear on the screen.

Installing the homebrew channel was done using the Hackmii Installer, an app developed by Team Twiizers, BootMii was also included in the Hackmii Installer.

BootMii is a software that's used as a brick prevention tool, you can either install it as Boot2 (The third Wii boot stage, way safer and brick preventive.) It requires an old enough Wii, or as an IOS (Specifically IOS 254) which is compatible with all Wiis (vWiis are NOT compatible), but it's less efficient for preventing bricks. The main uses of BootMii are : NAND dumping and Brick recovery, these are done using CEIL1NG_CAT (The user interface, wrongly thought as being BootMii itself).

=== 3 - Homebrew and piracy, a long story ===
When hearing the word homebrew the first thing that comes in mind is piracy (Piracy being a biproduct of homebrew). The Wii didn't escape this rule, piracy started with Wanikoko and their homebrew WAD Installer, which later became WAD Uninstaller and finally changed to WAD Manager. This tool enabled sharing VC and WiiWare WADs between people on the internet.

After that came Wanikoko's cIOSes, these are customized IOSes which enable loading backups using a loader such as Neogamma (Which was the best loader at the time), and they were intended to load your own backups, but lead to sharing pirated games again.

=== 3.1 - The Nintendo WFC and Cheating ===
Cheating became incredibly easy with homebrews (With GeckoLoader for example), and this made online games unplayable because of the unfairness that came with cheat codes.

Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/

https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/

probably check failoverflow

User:Kuhprii/History on the DS hacking scene

2025-04-13T21:33:40Z

Abdelali221: Clearer, i guess

== The Release of the Nintendo DS ==
The Nintendo DS released November 21st, of 2004.

== 2005 ==

=== The first pass-through ===
The developer DarkFader gets his hands on the Nintendo DS, he wants to hack it. Others in the community started to capture to traffic of the cartridge (I assume Metroid Demo). DarkFader then saw header data, as well as encrypted data. He then figured that the RSA on the back, didn't apply to the actual cartridge.

He then programmed an FPGA to make a pass-through that would let him capture and alter the data traffic from the cartridge. DarkFader made an etched PCB that went into the DS, and a cut GBC connecter that held a DS cartridge. He then altered the header and figured out he could run his own code from the Game Boy Advance slot.

Once he could run his own code, he made a program that modified a string of text in the Metroid Demo, and then continued executing. That was the first pass-through.

Wii:History on the Wii hacking scene

2025-04-13T20:34:11Z

Abdelali221: Added "The Riivolution"

Wii:History on the Wii hacking scene

2025-04-13T20:10:19Z

Abdelali221: Added an introduction

=== A quick look at the beginning... ===
The Wii hacking story started with Team Twiizers (A.K.A fail0verflow), their name came from the exploit they used... The Tweezer attack!

==== How it works : ====
Let's see how the Tweezer attack works, when the Wii switches to the GameCube mode it prepares the memory first by cleaning a specific bank of it, but the problem with that is that there is still some residual data left! The Team Twiizers used tweezers to switch between memory banks by shorting some data lines, which enabled them to access the residual data referred to earlier, which finally lead to them getting the encryption keys.

===== The First Homebrew-Ish : =====
Now with the encryption keys in his hands, Bushing made the first homebrew for the Wii, which consist of a Wii Remote monitor.

A video demonstrating that is available on the WiiDatabase YouTube channel.

Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/

https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/

probably check failoverflow