My experience with 4.2u..

Discussion in 'Wii - Hacking' started by Antics, Oct 1, 2009.

  1. Antics

    Antics Member

    May 30, 2009
    United States
    First off, screw Nintendo for their epic fail. My favorite part is they began bricking Wiis while trying to remove brick protection...XD

    Anyways, I modded my friend Shawn's Wii quite a while ago. Updated to 4.0u, trucha IOS60, cIOS 222,223, 249.
    He called me today while I was at school;
    "I got a letter from Nintendo saying there was an update"
    "Please tell me you didn't.."
    "*ten seconds of silence*"

    You get the picture.
    Anyways, I grabbed my copy of Brawl and decided to have a go at restoring his Wii to it's once former glory.

    Smash Stack to LoadMii, attempt HackMii 0.5, no go. No vulnerable IOSes
    LoadMii once again, but this time to TBR; code dump.
    LoadMii once more, Wad Manager, install a CiosCorp copy of IOS60....success.... :wtf:
    LoadMii into Any Title Deleter, delete the stub IOSes of 222, 223, 249, etc. so I could reinstall them.
    LoadMii into cIOS installer with IOS60, install rev 14.
    LoadMii into Wad Manager with IOS249, reinstall older Nintendo version of IOS15 (for BootMii) and System Menu 4.0u.
    BannerBomb into BootMii, it says it can be installed as Boot2. (I thought only Nintendo could do any large modification to Boot2? It let me install BootMii on v4...Or, am I mistaken and all that matters is the Boot1 exploit for BootMii install? :/)

    Long story short, its back to normal with 4.2u officially gone thanks to a NAND backup.

    My concern here is, am I missing something? How the hell did it let me install a cIOS60 in wad form?
    Doesn't that exploit the trucha bug, which, Nintendo surely has fully patched in (or prior to) 4.2?

    I just though that perhaps I would voice my experiences.
    Thanks to the creators of all the programs I used [​IMG]

    On a side note,
    after the hell I went through attempting different methods of fixing this issue, I will happily say that I will never update any Wii past 4.0 ever again, nor will any of my friends. Nintendo attempted to fix homebrew and in their wake, left many legitimate users without Wiis.
    I'm actually quite interested in watching their stock the next few weeks to see if it drops due to warranty repairs.
  2. Szalkow

    Szalkow RawkSD Cheerleader

    Jul 9, 2009
    United States
    Nintendo may try to squash a few of the existing homebrewers, but mostly they're trying to prevent any future instances of homebrew use.

    My guess would be that the Wii either had several IOSes patched which were not updated (the update probably covered the Hackmii installer's list of 'usual subjects') or you had a WAD manager which knew to check IOS 250. Nintendo would have difficulty overwriting that IOS, which is installed as a fakesigned failsafe cIOS which the highest possible version number (funnily enough, the 4.2 update does include a 250 stub but its version number isn't high enough).

    As for boot2 BootMii, only Nintendo and the HackMii folks have had any success modifying it; while initial reports suggested that the new boot2 install would prevent Bootmii reinstallation, this has obviously been proven false (and they can't fix the boot1 exploit via update anyway). boot2 *can* be modified via update, which has resulted in a fair number of bricks among legitimate users whose boot2 installations failed.

    4.1 might come in handy for those who want to stay current or play WSR, but I see no reason to use 4.2 at this time.