As such, it is impossible to downgrade boot1 to enable the use of a modified boot2 on Wiis which do not have a boot1 version which is vulnerable to the fakesigning bug, therefore making it impossible to install BootMii as boot2 (or other custom boot2 solutions) on these Wiis. ![]() It is unknown if this issue was ever encountered outside of this update, since this is believed to be the only time that a boot2 update was deployed to existing systems.īoot2 is verified by boot1, a program which cannot be changed on normal retail systems after factory setup due to boot0 verifying it against a fixed hash in the non-rewritable OTP. Upon the release of the 4.2 System Menu update, which is believed to be the first time that a boot2 update was deployed to existing systems, it was discovered that a flaw in the ES_ImportBoot function used to update boot2 lead to the bricking of consoles which were installing the update. 0 is used at the factory to install the first few titles, 1 is only seen on prerelease consoles including those with the Startup Disc Menu installed, 2 is seen on earlier units, 3 came preinstalled on some newer systems, 4 was deployed to all Wiis with a system menu update and preinstalled on some systems before the update, 5 was distributed on the Wii mini and some newer RVL-101 systems. ![]() ![]() For more information, check here.īoot2 is the Wii's third-stage bootloader it is stored in the BroadOn WAD format, which includes a ticket that is encrypted with the common key and signed.īoot2 versions 0 through 5 are known to exist.
0 Comments
Leave a Reply. |