Wii:History on the Wii hacking scene: Difference between revisions
From Hacks Guide Wiki
More actions
Abdelali221 (talk | contribs) No edit summary |
Abdelali221 (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
=== 1 - | === 1 - How it started === | ||
The story | The Wii Homebrew story started with the Team Twiizers, their name came from the exploit they made: The Tweezers attack. | ||
==== How It Works: ==== | ==== How It Works: ==== | ||
The Tweezer attack takes advantage of how the Wii transitions into GameCube mode. During this process, the | 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 | ==== 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. | 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 | === 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. | 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. | ||
| Line 16: | Line 16: | ||
BootMii could be installed in two ways: | BootMii could be installed in two ways: | ||
* '''As Boot2:''' A safer and highly effective method that could prevent bricks, but was only | * '''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. | * '''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 | 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 === | === 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. | The term "homebrew" is often associated with piracy, as unauthorized software modifications sometimes lead to illegal activity. The Wii was no exception. | ||
==== WAD Manager | ==== 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 | 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: ==== | ==== 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. | 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 === | === 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 | 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 === | === 4 - Evolution of Homebrew Since 2008 === | ||