Changes

* Another disc is ran. This disc is known as "0000dead" or "DE AD" in hex as it appears in [[uid.sys]]. This disc's TMD content index matches that of [[RVL_DIAG]] as dumped from an [[RVT-H Reader]]; while the development version of RVL_DIAG uses the IDs "100J" and "0000", it is likely to be the same as the retail 0000dead disc. This disc runs a variety of stress tests known as "aging tests" on the system, and registers the system's serial number over a [[Waikiki]] using PC software.

* Another disc is ran. This disc is known as "0000dead" or "DE AD" in hex as it appears in [[uid.sys]]. This disc's TMD content index matches that of [[RVL_DIAG]] as dumped from an [[RVT-H Reader]]; while the development version of RVL_DIAG uses the IDs "100J" and "0000", it is likely to be the same as the retail 0000dead disc. This disc runs a variety of stress tests known as "aging tests" on the system, and registers the system's serial number over a [[Waikiki]] using PC software.

* Another disc known as [[RVL_UJI_DIAG]] is inserted.. It is currently unknown what this disc does, but it is known to use IOS9 (while 0000dead and 123J use IOS4).

* Another disc known as [[RVL_UJI_DIAG]] is inserted. It is currently unknown what this disc does, but it is known to use IOS9 (while 0000dead and 123J use IOS4).

* Afterwards, a disc with ID "122E" is inserted, which installs [[Data Check & Log Check]] (aka 0002) to NAND via "DataChk.wad". This program checks the logs written by RVL_UJI_DIAG, as well as other test data, to ensure that the testing process was successful.

* Afterwards, a disc with ID "122E" is inserted, which installs [[Data Check & Log Check]] (aka 0002) to NAND via "DataChk.wad". This program checks the logs written by RVL_UJI_DIAG, as well as other test data, to ensure that the testing process was successful.

__TOC__

__TOC__

== Preloading ==

== Preloading ==

Every Wii is preloaded at the hardware level with a couple pieces of software; these are already present on the Wii and will run when the Wii is powered on at the factory. The first of these pieces of software is boot0, the first piece of code ran on the Wii after power-on (which will stay the same from when it is physically programmed onto the chip to after factory setup, since it cannot physically be modified), which will check the Wii's OTP (one-time programmable) memory chip, and seeing that it is blank (as it is written to later in the process, using up its one opportunity to program it), determines that we are in the factory and continues with boot by loading boot1 from the NAND; after factory setup, there are keys present within this area, which boot0 uses to verify your copy of boot1, but during first factory boot this is neither possible nor needed, so boot0 skips it.  Next, boot1 loads from the NAND. Boot1 works as usual by verifying the signature of the boot2 on the NAND, then loading it; this process is identical as long as you have a properly signed boot2, so there's no special factory behavior that boot1 has here.

Every Wii is preloaded at the hardware level with a couple pieces of software; these are already present on the Wii and will run when the Wii is powered on at the factory. The first of these pieces of software is boot0, the first piece of code ran on the Wii after power-on (which will stay the same from when it is physically programmed onto the chip to after factory setup, since it cannot physically be modified), which will check the Wii's OTP (one-time programmable) memory chip, and seeing that it is blank (as it is written to later in the process, using up its one opportunity to program it), determines that we are in the factory and continues with boot by loading boot1 from the NAND; after factory setup, there are keys present within this area, which boot0 uses to verify your copy of boot1, but during first factory boot this is neither possible nor needed, so boot0 skips it.  Next, boot1 loads from the NAND. Boot1 works as usual by verifying the signature of the boot2 on the NAND, then loading it; this process is identical as long as you have a properly signed boot2, so there's no special factory behavior that boot1 has here.