#Install bootmii as boot2 or ios install#
#Install bootmii as boot2 or ios drivers#
#Install bootmii as boot2 or ios update#
#Install bootmii as boot2 or ios full#
#Install bootmii as boot2 or ios software#

#Install bootmii as boot2 or ios full#

BootMii lets you run ARM (Starlet) code, which gives you full control (including the possibility of running PPC code).

#Install bootmii as boot2 or ios software#

Since BootMii as a separate IOS doesnвЂ™t participate in the boot process, it is obviously 100% safe (unless Nintendo does something stupid like crash if any unsigned software is found, but thatвЂ™s not going to happen because it would cause legal trouble as well).Д¬ode execution: This is pretty simple. Boot2 hasnвЂ™t been updated yet, so this gives BootMii as SysMenu IOS a slightly better chance than Preloader, which would suffer from the same issue if either the System Menu IOS or boot2 are updated to perform this check. BootMii as an IOS, on the other hand, could cause a bad brick if boot2 is updated to check the signature of the installed System Menu IOS.

#Install bootmii as boot2 or ios update#

The only way an update could brick a Wii with BootMii as boot2 would be due to a deliberate sabotage attempt by Nintendo (вЂњif we detect bootmii, deliberately brick that WiiвЂќ), which wonвЂ™t happen because they would likely be held legally liable for the damage. This would remove it, but that wouldnвЂ™t cause a brick. This is because boot1 canвЂ™t be changed, so the only thing that will affect it is a boot2 update. Update safety: BootMii as boot2 is essentially 100% safe. None of the options will survive a targeted attack вЂ“ this is just a measure of how likely a вЂњnormalвЂќ update will remove them. Interestingly, BootMii as a regular IOS is more likely to survive, simply because it would be installed alongside existing software and wonвЂ™t be overwritten by any update. BootMii as IOS would be overwritten with a System Menu IOS update, and Preloader would be overwritten with a System Menu update, both of which happen often and are pretty likely. Update resistance: BootMii as boot2 is likely to survive updates, because itвЂ™ll only be overwritten if boot2 is updated. Of note is that BootMii-boot2 doesnвЂ™t require anything on NAND that is dependent on your NAND keys, so the parts of NAND that are required are exactly the same (at least among Wiis with the same boot1 version). Preloader also depends on the System Menu IOS and runs on the PPC side, so it only saves you from brick problems that affect the System Menu (although these are pretty popular, so itвЂ™s still significant) вЂ“ it wonвЂ™t help for anything affecting IOS.

#Install bootmii as boot2 or ios drivers#

However, it doesnвЂ™t require any PPC code to run, nor does it run any additional drivers (for example, WC24), so some failure modes related to system files are eliminated. BootMii as IOS does quite a bit worse, because it does require a sane NAND Filesystem, and also a sane enough structure that the original boot2 wonвЂ™t choke on it. BootMii-boot2 will run even if your entire NAND Filesystem is hosed, and only requires the first megabyte or so of NAND to be intact (containing boot1 and boot2). This is basically a completely safe option, but also the least powerful one.Д«rick resistance: BootMii as boot2 has high brick resistance because it _only_ relies on boot1 and boot2, which are in a reserved area of NAND. It would be useful for people who want to use software designed to run under BootMii (that is, using custom ARM code, not IOS) starting from code under IOS, without regard for having it run on boot or brick-safety. вЂњLowвЂќ doesnвЂ™t mean crap, it means lower than вЂњMediumвЂќ or вЂњHighвЂќ.Д«ootMii as (separate) IOS is a special case. Note that the metrics on the table are mostly relative to one another.

Compatible with return: does вЂњReturn to Wii MenuвЂќ run it?.

#Install bootmii as boot2 or ios install#

Low-level install: how easy it is to install using a hardware programmer.

Complexity: how many things can go wrong while using it.

Code execution: what kinds of code you can actually run with it.

Update safety: chances of causing a brick when the Wii is updated in the future.Update resistance: chances of surviving a Nintendo update.Brick resistance: chances of it helping you if you brick your Wii.HereвЂ™s a table comparing the following attributes of the four solutions: Since people seem to love to compare Preloader to BootMii, IвЂ™m going to throw it in the comparison as well. We wonвЂ™t support them when BootMii first comes out (lest we delay it even further), but one or more of them might come in the future. There are pros and cons to these options, and theyвЂ™re not as good as installing BootMii as boot2, but they are possibilities worth exploring. However, there is a way of accomplishing some of BootMiiвЂ™s goals on those Wiis, by installing BootMii as the System MenuвЂ™s IOS, or as an entirely separate IOS, for example. A modified boot2 will not run on them, period. What will happen to those new Wiis that have it?ДЄt first, BootMii will not be compatible with those Wiis.

From the checker statistics, weвЂ™re seeing about 10% of Wiis with the new boot1 (all newer ones).