shortening this guide for my personal use.

Discussion in 'Wii - Hacking' started by lithium210, Aug 6, 2009.

  1. lithium210
    OP

    lithium210 GBAtemp Fan

    Member
    423
    13
    Oct 16, 2003
    United States
    another question.. trying to update my friends wii to 4.1 with waninkoko's updater since his 3.2 is already softmodded. already have a nanddump.

    here's the guide im trying to follow:

    -Run Firmware-Update 4.1

    -Run IOS60 Installer:

    Select “NO” for install IOS61.

    Select “YES” for Install IOS60.

    Select “YES” for Patch IOS60.

    Select “NO” for install shop channel.

    -Run Preloader .29 (dont foget to set hacks.ini to 4.0u NOT 3.2u in SD card)

    -Run CIOSCORP Installer

    -Run Wad Manager and install CIOS60BF.wad:

    The Wii System will now have a “SYSTEM DATA IS CORRUPT" error message but do not worry.

    -Turn off Wii. Hold reset to enter preloader. Launch homebrew channel and reinstall preloader again.

    -All Done!

    --------------------------

    my question is, i dont want preloader (installing startpatch 4.1) in there so if i follow the guide this way would i run into any problems? i mean i shouldnt even be posting this since i have bootmii and could easily just reinstall the nand.

    -Run Firmware-Update 4.1

    -Run IOS60 Installer:

    Select “NO” for install IOS61.

    Select “YES” for Install IOS60.

    Select “YES” for Patch IOS60.

    Select “NO” for install shop channel.

    -Run Preloader .29 (SKIPPING THIS PART)

    -Run CIOSCORP Installer (INSTALLING CIOSCORP 3.2 FOR DISC CHANNEL LOADING & GC SUPPORT)

    -Run Wad Manager and install CIOS60BF.wad (IS THIS NECESSARY???)

    -Installing CIOS38Rev14

    The Wii System will now have a “SYSTEM DATA IS CORRUPT" error message but do not worry. (WILL I STILL GET THIS MESSAGE IF I DONT HAVE PRELOADER INSTALLED????)
     
  2. lithium210
    OP

    lithium210 GBAtemp Fan

    Member
    423
    13
    Oct 16, 2003
    United States
    oh nevermind, i just read that cioscorp 3.2 that just came out fixes any issues with error messages.