sebaash said:(FROM BOOTMII WEBSITE)s3phir0th115 said:I think I have a theoretical safe update method. But it would require preloader working with IOS70, and System Menu 4.2. You'd also need a cIOS or trucha vulnerable IOS and wad manager.
1. Load homebrew channel.
2. Load an app to install a trucha patched IOS70. (Or have someone cioscorp patch it, then install. Cioscorp 3.5 anyone?)
3. Load wad manager and install System Menu 4.2 from nusd. Exit. (This should take you back to the homebrew channel, before the system menu can interfere.)
4. Load preloader, and install it again, making sure the anti-anti-homebrew patches are applied to prevent the menu from deleting everything.
5. Go on happily.
Just my 2 cents.
but i don't wanna lost bootmi u.u
You wouldn't lose it. In fact, updating as I described wouldn't even touch the boot2 if one were to do it. Only updating through Nintendo would do that.
QUOTE(lolorlofl @ Sep 29 2009, 12:35 PM)
What does "The installed boot1 version prevents a boot2 install (-2) mean? Are you going to fix it?
No, it can't be fixed. Installing as boot2 is the most useful way to install BootMii, but it requires that we exploit a particularly silly bug in a part of the system that can not be changed under any circumstances. Nintendo finally fixed this bug in new Wiis that were released sometime in 2008. We have looked for a suitable replacement for this exploit, but have not found one, and it does not seem likely that anyone ever will.
Obviously talking about the updated boot2's in LU64 Wii's and in this update. Doesn't look like there's going to be a boot2 fix for this update anytime soon.
I don't think you understand what they said.
Boot 1 is readonly, meaning Nintendo cannot change it with any update. They are exploiting the boot1 in order to get bootmii as boot2 to work. Now, Nintendo may overwrite bootmii, but that doesn't mean putting bootmii back on is impossible. They simply must find another IOS exploit.