Changes

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 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.  

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]], [[RVL_UJI_DIAG]], & [[Data Check & Log Check]]) that have leaked publicly. Since most 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 ==  

== Basic Overview ==  

* 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]] (or 121J) is inserted. It is unknown what role this disc serves during the manufacturing process exactly, as the publicly available version sourced from an [[RVT-H Reader]] is similar to the aforementioned 100J, but with a few more test programs and newer software. 121J includes programs which perform tests on the system and write the results to [[testlog.txt]] in addition to checking this file, so it can be assumed that it is at this phase of the setup process where these tests are executed.

* 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.

* Then, [[Data Check & Log Check]] (aka 0002) is installed 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.

* 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.

* 122E is then ran, an update partition-only disc which installs the base set of software (retail System Menu, channels, IOS, etc.) before the Wii is shipped.

* Wiis that are not BootMii as Boot2 vulnerable have a disc ID of "0003" in the factory section of the uid.sys as well. It's currently unknown what it does, but it is generally found immediately after 122E and right before any signs of retail usage (typically seen as the 00010000-00555045 of a disc's UPDATE partition.)  

* Some [[LU64+]] Wiis have a disc ID of "0003" in their [[uid.sys]] as well. It's currently unknown what it does, but it is generally found immediately after 122E and right before any signs of retail usage (typically seen as the 00010000-00555045 of a disc's UPDATE partition.)  

__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 it is 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 the console has a properly signed boot2, so there's no special factory behavior that boot1 has here.

Next up, [[boot2]] loads; the version of boot2 installed on a Wii once it comes out of the factory can only handle an encrypted NAND filesystem; the problem with that in the factory is that at this point the OTP has not been programmed, and since the OTP contains the console-unique NAND keys, it is impossible to have the NAND encrypted at this point. As such, the NAND is unencrypted, which the production version of boot2 cannot handle; presumably, a special factory version of boot2 (possibly boot2v0) is programmed on Wiis at this point, which can boot from unencrypted NAND filesystems and as such will continue boot as normal. The next thing to be loaded is the System Menu, although most likely not the retail System Menu as we know it; rather, a stripped-down version of the System Menu is loaded. While it isn't clear what exactly this System Menu is, one piece of evidence (someone obtaining a retail Wii with the NDEV menu installed on it) as well as common sense indicates that it is most likely the NDEV menu, intended for use on Wii development kits. This menu has minimal functionality compared to the retail menu, but all we need in the factory is the ability to read and boot discs, which it does provide; as such, it works just fine in the factory. It's unknown what version of the NDEV menu is used or what IOS is associated with it; it is possible that this changed over the Wii's lifespan with updates to the menu and its associated IOS.

Next, [[boot2]] loads; the version of boot2 installed on a Wii once it comes out of the factory can only handle an encrypted NAND filesystem; the problem with that in the factory is that at this point the OTP has not been programmed, and since the OTP contains the console-unique NAND keys, it is impossible to have the NAND encrypted at this point. As such, the NAND is unencrypted, which the production version of boot2 cannot handle; presumably, a special factory version of boot2 (possibly boot2v0) is programmed on Wiis at this point, which can boot from unencrypted NAND filesystems and as such will continue boot as normal. The next thing to be loaded is the System Menu. While it isn't clear what exactly this System Menu is, it is most likely a version of the [[NDEV Menu]]. It's unknown what version of the NDEV menu is used or what IOS is associated with it; it is possible that this changed over the Wii's lifespan with updates to the menu and its associated IOS.

== Setup ==

== Setup ==

At this point, a disc would be inserted to actually begin the process of setting up the system. While this disc presumably has an official name which is currently unknown, it will be referred to as "123J", as 123J is the Title ID of the disc (as evidenced by its presence in the uid.sys logs of all Wiis, as well as other NAND remnants). This disc most likely runs on IOS4 or IOS9 (it is possible that this changed over the Wii's lifecycle as well with updates to the disc), and, as far as we are aware, serves one main purpose; writing to the OTP chip and encrypting the NAND filesystem. However, there is one other possible task that 123J may have performed; updating boot1. As Nintendo issued various updates to boot1 throughout the Wii's lifecycle (most infamously the update that fixed the trucha bug within it, aka disabling bootmii/boot2 on newer Wiis), the most logical way to issue these updates would be by implementing a function to update boot1 within 123J before writing to the OTP area (since the OTP area contains the hash of boot1, if you want to update boot1, you have to update it before writing the hash). Nintendo also could have simply updated the boot1 version in their pre-prepared set of files programmed onto the system physically before it even hits the factory stations, although doing this through 123J seems more logical.

At this point, a disc would be inserted to begin the process of setting up the system. While this disc presumably has an official name which is currently unknown, it will be referred to as "123J", as 123J is the [[GameID]] of the disc (as evidenced by its presence in the [[uid.sys]] logs of all Wiis, as well as other NAND remnants). This disc most likely runs on IOS4 or IOS9 (it is possible that this changed over the Wii's lifecycle as well with updates to the disc), and, as far as we are aware, serves one main purpose; writing to the OTP chip and encrypting the NAND filesystem. However, there is one other possible task that 123J may have performed, which is updating boot1. As Nintendo issued various updates to boot1 throughout the Wii's lifecycle (most infamously the update that fixed the trucha bug within it, aka disabling bootmii/boot2 on newer Wiis), the most logical way to issue these updates would be by implementing a function to update boot1 within 123J before writing to the OTP area (since the OTP area contains the hash of boot1, if you want to update boot1, you have to update it before writing the hash). Nintendo also could have simply updated the boot1 version in their pre-prepared set of files programmed onto the system physically before it even hits the factory stations, although doing this through 123J seems more logical.

After writing data to the OTP (therefore locking boot1, and setting all of the sysem's console-unique encryption keys), 123J encrypts the console's NAND filesystem using the newly generated NAND keys; these are the very same keys you get in your keys.bin file along with a BootMii dump, which are needed to decrypt the NAND. Next, [[RVL AGING|a disc known as 100J, also titled 0000dead, RVL_DIAG, and RVLAGING]] is inserted; this disc contains the bulk of the factory testing procedures, and runs the majority of hardware tests. This disc was also used with [[RVT-H Reader]] development units, and as such we have obtained a copy of it, and are able to provide more exact information about how it works. More to be added soon {TODO)

After writing data to the OTP (therefore locking boot1, and setting all of the sysem's console-unique encryption keys), 123J encrypts the console's NAND filesystem using the newly generated NAND keys; these are the very same keys you get in your keys.bin file along with a BootMii dump, which are needed to decrypt the NAND. Next, [[RVL_DIAG|a disc known as 100J, also titled 0000dead and RVL_DIAG]] is inserted. This disc contains several test programs which could be used to verify the Wii's hardware as part of a quality control process. However, it is unknown what purpose this disc serves exactly during the retail Wii manufacturing process, as the [[RVL_UJI_DIAG]] (121J) disc which runs next has almost all of the same content as 100J, with a few extra programs and more recent software revisions. As the publicly available copies of both of these discs were dumped from [[RVT-H Reader]] units, it could be that the manufacturing & testing process for development kits differs from that of retail units, and as such, this ID could represent a completely different disc during the retail manufacturing process.

Now that 123J has finished running, having written the OTP, encrypted the NAND, and possibly updated boot1, it's time to start our testing procedure to make sure the console is in working order. The next disc inserted to start this procedure is known by its title ID as 121J; 121J is probably the most mysterious of the factory discs, as its apparent purpose doesn't make much sense, and we don't have many remnants of it or information about it. It appears that 121J is a disc focused around the GameCube mode of the Wii; it installs BC and MIOS (files needed for GC compatibility), and performs a test of the GameCube compatibility mode. This seemingly makes sense, but as you'll see soon, 121J isn't the last disc to run tests; it's not known why it specifically was used for testing GC compatibility. While this is all we really know about the mysterious 121J, there is one more tidbit; 121J creates the factory test log file, which is then written to by the next factory disc. It's not known why the file isn't created by the next disc, but this may indicate '''that 121J had a larger part in the testing role than we believe'''. As GameCube testing information isn't written to the testlog, it's possible that originally it was, and this was simply removed but the testlog was still created by 121J so the next disc wouldn't have to be modified.

The next disc inserted is the aforementioned [[RVL_UJI_DIAG]], with [[GameID]] 121J. The copy of this disc obtained from an RVT-H Reader includes several testing programs which could be used to ensure the integrity of a unit's hardware, as well as programs that run pre-defined tests, the results of which are then written to [[testlog.txt]]. It also contains [[serNoReg]], the program which registers the console's serial number using a mentioned but unseen piece of PC software. The retail version of 121J appears to include an additional step not present in the RVT-H version, as it installs a WAD titled 'DataChk.wad' to the NAND via a second partition with the ID '0002'. While this title is normally deleted from NAND after it is used, it is left behind on some Wiis for unknown reasons, and as such it has been obtained publicly and its behavior is detailed below.

The next disc is by far the most interesting. It does two things; installing an IOS used for testing, and installing a WAD file that does all the work.

 

Of course, we have this WAD file in full.

== Data Check and Log Check's role ==  

== Data Check and Log Check's role ==  

''See also: [[Data Check and Log Check]]''

''See also: [[Data Check and Log Check]]''

This disc and accompanying WAD file are known as "0002", but the in-program name is "DATA CHECK & LOG CHECK".  There are two known versions of this file, both dumped from separate Wiis; 1.5.0 and 1.5.1. The exact circumstances around the deletion of this file are unknown; it is NOT present on all Wiis after factory setup, in fact, it's absent from the majority of them. If you are reading this and have your Wii NAND dump at the ready, check it in ShowMiiWads, because you may find a new version of 0002. We're still not sure how this happens.

This disc and accompanying WAD file are known as "0002", but the in-program name is "DATA CHECK & LOG CHECK".  There are two known versions of this file, both dumped from separate Wiis; 1.5.0 and 1.5.1.

 

0002's exact purpose is unknown; it appears to verify the results of 121J by checking files on NAND as well as files from an SD card, in particular [[all.ini]]. all.ini is a list of tests near-identical to that which is present in 121J under the filename "master.dat"; it is unknown why 0002 requests this file, or why it was copied to NAND and therefore able to be retrieved from a retail Wii system.

Of course, that's just the meta info around 0002; what does it actually do? 0002 is the main app that runs all of the tests ran on each Wii during factory setup. However, 0002 doesn't actually contain any test programs; it reads and launches them off of an external SD card, based on a list of tests also present on said SD card known as all.ini. As this all.ini file is copied to NAND for an unknown reason, albeit removed afterwards, we also have a copy of it as bushing (RIP) salvaged it and uploaded it to HackMii. 0002 will read this file from the SD card, and launch test programs (in DOL format) from the SD card. As such, it's difficult to analyze 0002's behavior without actually having these test programs or all of the contents of the factory SD cards, as we only know about the all.ini and the presence of the test programs in it. It's worth noting that all.ini contains listings for test programs clearly intended only for Wii prototype models and even GameCube units of various types, meaning that it most likely dates back to pre-Wii and was used for some purpose on the GameCube; and that not all of the files are actually present on the factory SD cards, or at least not ran normally, as many of the programs would not even run on a standard retail Wii.

The final step is to install the System Menu, IOSes, and channels. This process is akin to a standard disc update, where a disc is inserted, the contents of it are read, and WAD files are installed from those contents. The disc that handles this is known as 122E. This disc appears to simply be an update partition, as the [[main.dol]] file which it leaves behind in the [[cache.dat]] of a system after it is inserted is a non-functional DOL file similar to those which are found in the update partitions of retail Wii discs. It can be presumed that Nintendo may have pressed several versions of this disc to keep the Wii's preinstalled software updated throughout its production run; however, none have been found publicly, nor is it known what the actual name or appearance of the disc is.

Once 0002 has executed all its tests and verified that the Wii's hardware is OK to ship out, there's still one more step; installing the System Menu, IOSes, and channels. This process is akin to a standard disc update, where a disc is inserted, the contents of it are read, and WAD files are installed from those contents. The disc that handles this is known as 122E. Not much is specifically known about it, but it's pretty clear what it does; it installs the files on it, and sets up the Wii to be unboxed by the customer for the first time. As such, there are presumably many versions of this disc, and whenever Nintendo wanted to do an update to the Wii's pre-installed software, they just issued an update to this disc. Once this disc has finished doing its stuff, you're done; the System Menu has been installed, all of the pre-installed software has been installed, and the Wii is ready for packaging up and shipping. 35-year-old Jenny goes out and buys the Wii from her local Target and spends 10 minutes trying to figure out how to set up the sensor bar, then gets past the language select screen and sets it up so she can finally play Zumba Fitness.

Once 122E has finished installing the base set of titles, the system's initial manufacturing & testing process is complete, and on the next boot the system will be running the retail [[Wii Menu]] on the initial setup screen.

{{Template:WiiNavbox}}

{{Template:WiiNavbox}}