Difference between revisions of "Boot process"

Revision as of 22:54, 27 March 2009

The code components involved in the Wii's boot process are, in order:

boot0 A mask rom, run by the Starlet
boot1 Lives in a modifiable area of the NAND but cannot be changed due to its hash being stored in the OTP. Run by the Starlet.
boot2 A modifiable area of Flash, signature checked by Boot1, Run by the Starlet.
System Menu / System Menu's IOS The System Menu is the first visible user interface since it is the first code running on the PowerPC. It has higher access privileges compared to games (e.g. it can read and write to every savegame). Its signature is only checked upon installation. boot2 only makes sure that the HMAC signatures on the NAND's filesystem are valid.

@@ Line 4: / Line 4: @@
 * [[boot1]] Lives in a modifiable area of the NAND but cannot be changed due to its hash being stored in the [[Hardware/OTP|OTP]]. Run by the [[Starlet]].
 * [[boot2]] A modifiable area of Flash, signature checked by Boot1, Run by the [[Starlet]].
-* [[System Menu]] / System Menu's IOS The System Menu is the first visible user interface since it is the first code running on the PowerPC. It has higher access privileges compared to games (e.g. it can read and write to every savegame). It's signature is only checked upon installation. [[boot2]] only makes sure that the HMAC signatures on the NAND's filesystem are valid.
+* [[System Menu]] / System Menu's IOS The System Menu is the first visible user interface since it is the first code running on the PowerPC. It has higher access privileges compared to games (e.g. it can read and write to every savegame). Its signature is only checked upon installation. [[boot2]] only makes sure that the HMAC signatures on the NAND's filesystem are valid.
 {{stub}}