It's the boot1 thats has the exploit not the boot2. Nintendo updating the boot2 deletes the extra code that bottmii installs so you just need to reinstall it. So you'll have boot2v4 with bootmii. It's not the boot2 that has the exploit, it just so happens that when they started shipping Wiis...
It's not the boot2 that exploitable but rather the boot1 which allows extra code in the boot2 to run. So Nintendo wipe your boot2 and install their latest version but they can't patch the boot1 (it's read only) so you just need to reinstall it.
No your software is very good and says when the IOS isn't trucha signed so I know 36 was patched. I removed 37 with any title deleter and reinstalled it.
Worked like a charm!
Good work!!!
I downgraded IOS15, used 15 to install 36. When using 36 to install 37 I get...
ES_AddtitleStart returned: -1035
Has your installed IOS37 a higher revision than 3612?
IOS37 installation failed.
If I select IOS37 to launch the software it says I'm on version 3612.
Any ideas? I'm using a 2...
Just turn off Standby Connection in the Wii Connect 24 menu. Then there's no standby setting just off and it works from the WiiMote. Good for those of us with USB drives powered from the USB port!!!
So what part of the Wii gets hot? It would be pretty lazy to turn the fan on when the drive is in use if it's the graphics chip that gets hot. Is it the DVD drive/chip get hot?
It's the new HBC. If you install HBC 1.0.1 it's meant to fix it....although it hasn't for me on FW 4.0. Still can't use my Kingston 4GB Class 6 card although it works in the Wii System.
Bring on HBC 1.0.3!!!