Wii:History on the Wii hacking scene - Revision history

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

2025-04-18T19:16:41Z

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

← Older revision		Revision as of 19:16, 18 April 2025
(No difference)

Abdelali221 at 19:11, 18 April 2025

2025-04-18T19:11:56Z

Abdelali221 at 18:38, 18 April 2025

2025-04-18T18:38:13Z

← Older revision		Revision as of 18:38, 18 April 2025
Line 65:		Line 65:

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

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

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

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


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

Abdelali221 at 18:25, 18 April 2025

2025-04-18T18:25:32Z

Show changes

Abdelali221: /* August 5th */

2025-04-18T18:03:10Z

August 5th

← Older revision		Revision as of 18:03, 18 April 2025
Line 52:		Line 52:

	===== August 5th =====		===== August 5th =====
	RiiConnect24 began ~~with~~ the News Channel.		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/		Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/

Abdelali221: /* 2015 */

2025-04-18T18:02:37Z

2015

← Older revision		Revision as of 18:02, 18 April 2025
Line 50:		Line 50:
	== 2015 ==		== 2015 ==
	D2X CIOs was released.		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/		Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/

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

2025-04-18T17:38:57Z

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

← Older revision		Revision as of 17:38, 18 April 2025
Line 51:		Line 51:
	D2X CIOs was released.		D2X CIOs was released.

	== Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/ ==		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/		https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/

	probably check failoverflow		probably check failoverflow

Abdelali221 at 17:38, 18 April 2025

2025-04-18T17:38:34Z

← Older revision		Revision as of 17:38, 18 April 2025
Line 25:		Line 25:
	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.		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 ===		=== 4 - How it evolved since 2008 ===

	== 2008 ==		== 2008 ==
Line 31:		Line 31:

	== 2009 ==		== 2009 ==
			No data (yet).

	== 2010 ==		== 2010 ==
			No data (yet).

	== 2011 ==		== 2011 ==
			No data (yet).

	== 2012 ==		== 2012 ==
			No data (yet).

	== 2013 ==		== 2013 ==
			No data (yet).

	== 2014 ==		== 2014 ==

Abdelali221 at 17:37, 18 April 2025

2025-04-18T17:37:41Z

@@ Line 25: / Line 25: @@
 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/
+=== 4 - How it evolved ===
 https://gbatemp.net/threads/part-of-the-wii-hacking-history-summer-2008-to-2009.521275/
 probably check failoverflow

Abdelali221: added content

2025-04-14T15:46:56Z

added content

← Older revision		Revision as of 15:46, 14 April 2025
Line 11:		Line 11:

	== 2 - The Riivolution ==		== 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 ~~available~~ to ~~anyone~~, 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.		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.		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).		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/		Sources found:https://gbatemp.net/threads/the-early-history-of-wii-modding.243461/

← Older revision		Revision as of 19:11, 18 April 2025
Line 1:		Line 1:
	=== 1 - ~~The Beginning: A Quick Look at Wii Hacking~~ ===		=== 1 - How it started ===
	The story ~~of Wii homebrew begins~~ with Team Twiizers ~~(later known as fail0verflow)~~, ~~whose~~ name ~~originates~~ from the exploit they ~~pioneered—the Tweezer~~ attack.		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 ~~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 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 ~~Steps Toward~~ Homebrew: ====		==== 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~~: The Rise of Homebrew~~ ===		=== 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 ~~compatible with older Wii consoles~~.		* '''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 ~~often mistaken for~~ BootMii itself.		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 ~~and Game Piracy~~: ====		==== 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 ~~widespread 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 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. ~~Though originally~~ intended for legitimate personal backups, ~~this technology also~~ facilitated game piracy.		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 ~~rampant~~ 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 ===		=== 4 - Evolution of Homebrew Since 2008 ===