- Gecko os code boot.elf update#
- Gecko os code boot.elf Patch#
- Gecko os code boot.elf full#
- Gecko os code boot.elf software#
This ensures that boot1 is also untouchable (you’ll brick your Wii if you try). It loads boot1 from the beginning of NAND and verifies it against a hash stored in non-writable memory. The very first piece of code that runs is boot0, which is part of the mask artwork of the Hollywood chipset and thus entirely untouchable. Let’s revisit the boot sequence of the Wii.
Gecko os code boot.elf update#
You’d have to deliberately brick your Wii to kill BootMii, excluding one particular type of update by Nintendo (we’ll get to that later).
Gecko os code boot.elf software#
By being such an early hook, BootMii-Core is also the most brick-resistant piece of software that can be written for the Wii. A mere fraction of a second after you hit the power button on your console, BootMii-Core will already be running and you’ll have the ability to do anything at that point.
Gecko os code boot.elf full#
What it does is give us full control of the console as early in the boot process as possible. Instead, today I’ll talk about the part of BootMii that was demoed in the video: BootMii-Core.īootMii-Core is a very important piece of BootMii, ideologically speaking. We’re still working on designing and building most of it, so don’t expect detailed explanations about the still-to-be-written pieces. Now, I’ve said that BootMii is a platform. This might become handy if, for example, Nintendo decides to start banning homebrewers from online games. By keeping BootMii separate from the existing system for the most part, we can switch it on and off at will. While we will be taking control of the system, we want to accomplish that while minimizing any changes to the existing system.
Now we’ll have control and Nintendo’s software will have to go through us to do anything.īefore going into details though, I must mention another subtle but important detail about how we’ve decided to go about designing BootMii. Instead of being users of the system, doomed to hacking our ways from the inside, we’re going to turn the tables around. Of course, we don’t expect the latter to happen (we have / will find more holes), but nonetheless it’s still unnerving to a degree.īootMii – let’s call it the BootMii platform – is about changing that.
Gecko os code boot.elf Patch#
And at any time Nintendo can come and update the entire system to patch all the holes. Starfall gets rid of some annoyances of the system menu, but it’s an ugly low-level filesystem hack that will get erased with any Nintendo update. PatchMii was developed to get rid of some of the restrictions of IOS – but it’s not particularly practical, and only really works for one IOS at a time. Now, there have been some hacks around the system, of course. This isn’t a bad thing (it provides many bits of code that we don’t have to write), but it also means we have to follow its rules. Every piece of Wii Homebrew currently depends on Nintendo’s IOS. We can avoid updates and try to understand the existing system, but we’re still dependent on it. Sure, we can run our own stuff, but ultimately we’re users of the system – everything we do has to go through Nintendo’s software. Up until now, we’ve had little control over what software our Wiis truly run. The first thing that you need to realize is that BootMii isn’t a single application or hack – it’s a platform for hacks. The hardware in the video is merely for debugging. Oh, and by the way, before I bore you and you stop reading this, at least note that BootMii is entirely software-based. I think it’s time to answer some questions about what it really is, what it does, and how it will help you. A few days ago I posted a video of something that we’ve come to call BootMii.