1,386
edits
Changes
From Rare Gaming Dump
Revised the basic overview at the start. Page itself needs MAJOR rewrites to reflect it though.
This article presents known information concerning the factory process of the Nintendo Wii.
This article presents known information concerning the factory process of the Nintendo Wii.
Please note that our information on this topic is limited. It is mostly based on information from a single old HackMii article (which, to be fair, provides a lot of information), as well as assumptions. While that's not a great base for something like this, there isn't really a whole lot we can do about it; the only place we can really go from here is analyzing whole NAND dumps for remains, and once we figure out how to do that, we will gain some insights, but we still won't be able to answer every question without some kind of amazing discovery like the factory discs being dumped, which isn't bound to happen anytime soon. So while this may turn out to be inaccurate and end up being updated in the future, this is the process to the best of our understanding right now.
Please note that our information on this topic is limited. It is mostly based on information from old HackMii articles, assumptions, [[uid.sys]] dumps, and the few pieces of the process ([[RVL_DIAG]] & [[Data Check & Log Check]]) that have leaked publicly. Since the majority of the pieces of this process are not publicly available, we can only piece together how the entire process works from the information which is available, so this may not be a perfect description of the process.
== Basic Overview ==
* During hardware manufacturing, [[boot0]] is imprinted into the Mask ROM inside the [[Starlet]].
* During initial programming of the NAND chip, unknown versions of [[boot1]] and [[boot2]] are flashed to NAND provisionally, along with an unknown (likely [[NDEV Menu|NDEV]]) System Menu and a corresponding [[IOS]] version.
* Setup begins by inserting a disc with the game ID of "123J". This disc most likely generates the console-unique NAND keys and other console-unique data, and writes them to the [[OTP]] chip along with encrypting the NAND with said keys. It may also update boot1, since this can only be done before the NAND keys are written to OTP.
* Another disc, or possibly a separate partition of the same disc, is ran. This disc appears as "DE AD" as hex in [[uid.sys]], and creates a TMD under the name "0000dead". This disc likely has an unknown role in the aforementioned NAND encryption process.
* Another disc is inserted with the title ID of "121J". This disc is likely the retail version of [[RVL_DIAG]], the development version of which has ID "100J"; this disc runs a full stress-testing suite on the system, which is detailed further in said article.
* 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 121J, as well as other test data, to ensure that the testing process was successful.
* 122E then reboots, and installs a number of WADs from the SD card, which likely include all of the IOS, channel, and menu files which are required for the console to function normally. Once 122E is finished, the console has been fully set up and is ready to ship.
__TOC__
__TOC__
== Preloading ==
== Preloading ==
