Changes

Besides on [[boot2v1]] units, this is the only time Nintendo ever pushed a boot2 update, and they did not test <code>ES_ImportBoot</code> very well, resulting in many [[brick|bricks]], which Nintendo refused to fix under the assumption that those [[Wii]]'s had homebrew on them. For this reason, the [[HackMii Installer]] has a custom installer to install BootMii.

Besides on [[boot2v1]] units, this is the only time Nintendo ever pushed a boot2 update, and they did not test <code>ES_ImportBoot</code> very well, resulting in many [[brick|bricks]], which Nintendo refused to fix under the assumption that those [[Wii]]'s had homebrew on them. For this reason, the [[HackMii Installer]] has a custom installer to install BootMii.

It should be noted that there were also some [[4.1]] discs, such as New Super Mario Bros. Wii, that still come with boot2v4. In general, stay away from updating any Wii with a version lower than 4.2.

There seems to be a bug where after ES_ImportBoot checks the hash of the written boot2, it calls ioctl 1 of [[:/dev/boot2]] (which seems to flush the write buffer, which is normally empty besides before IOS_Write returns, then write some metadata from the /dev/boot2 FD), then call ioctl 3 of /dev/boot2 (which presumably copied the updated boot2 to the backup copy) regardless of the hashing result. It is not known if this is what caused the bricks in 2009.

[[Category:Boot]]

[[Category:Boot]]