Hacking NOOB PARADISE - ask away

[frog27]

Reinstalling the system menu WAD will overwrite Priiloader, so you need to proceed carefully. If you mess up, you won't have Priiloader to save you. Installing Priiloader is unlikely to cause this kind of problem. What did you do beforehand that likely led to this issue? Did you enable any of the hacks in Priiloader?

If you have access to the Homebrew Channel, follow this guide to post a sysCheck:


Also, do you have bootmii installed as boot2?

I was trying to install bootmii when I discovered the problem. The instructions on the website were really vague so I couldn't figure it out. The only things I installed were Nintendont which was working fine and priiloader. I activated the region free, and no update from disc/online system menu hacks but disabling them didn't fix anything.

System check below.

Spoiler

aa 01 bd 67, 7c 20 dc 28, 9c c6 b0 c9, 48 4b d3 f7, cd bc 4b 10

IOS57 base hash:
e7 46 07 56, 4c e8 69 2f, cd e1 19 02, 26 d6 a1 dd, 82 4c ef 0c

IOS56 base hash:
1b cc cf 07, f1 0c d5 12, be 96 9a a5, d2 36 67 98, 30 71 e6 81

IOS55 base hash:
c5 00 19 41, 22 18 21 92, b6 39 c9 d2, 05 fe 3f b3, 43 36 ae 0c

IOS53 base hash:
78 68 c0 50, 5c d6 d5 15, 65 d7 d8 0f, f0 a2 d9 d4, 9e 1d 7d fb

IOS48 base hash:
8d 53 7a 4a, 09 51 e5 6b, 2b 65 c8 27, f0 47 bb 72, c3 5c da e2

IOS46 base hash:
f5 e0 93 27, 26 cb 68 7b, ac e7 cc 86, 39 77 71 d1, ba 9e 42 36

IOS45 base hash:
08 58 11 20, 6b 3a e5 9f, b9 10 16 8b, 8a ea 06 3d, 9c 14 80 ef

IOS43 base hash:
f8 46 be 02, 74 e7 90 a3, d9 00 9a ae, d5 95 3f 77, e3 3f ad 2a

IOS41 base hash:
6c ad 7f 85, b6 87 e3 c3, 17 4e 5c 79, 99 fd 01 83, 16 55 fa 6f

IOS38 base hash:
f5 77 6b 66, cd 74 12 ee, 19 12 5c 11, 54 bf d7 3e, d7 e4 af 4b

IOS37 base hash:
32 c7 bc 54, 92 f6 17 e2, 64 26 e3 ce, bd 36 9f 40, 42 ea e8 02

IOS36 base hash:
29 36 80 06, 7d 22 7e 9f, 1c b1 af 70, 32 69 25 6d, 73 fb 14 55

IOS35 base hash:
58 5e 04 25, 45 d4 e2 8e, 98 fe 0d cd, 76 d0 71 d6, ac 17 a0 9c

IOS34 base hash:
68 8a 19 ae, c4 9f 57 fb, 11 1b 31 49, 2b 4d b4 85, 25 a6 3f 72

IOS33 base hash:
fc cf c4 1b, fc 8c 12 9e, 1f 67 5b 42, d4 3d 10 d6, 56 4f f5 f9

IOS31 base hash:
71 5f d8 87, 67 3e 32 4c, 53 c5 00 ce, 2b 50 14 f7, f2 ff e8 31

IOS28 base hash:
5c cd 08 24, 19 7b 9a 02, 17 55 5d f9, 39 dc dc 49, 73 ea 75 6a

IOS22 base hash:
8d 84 49 8b, f5 ba 6c a8, f0 58 64 10, 40 25 cd 1c, 25 9b 8a f6

IOS21 base hash:
91 ba e4 26, 1b 49 f0 95, e0 8c 21 17, e1 fa 8b e9, 92 6d eb 1b

IOS17 base hash:
77 7b 4c cb, 9a fb fe fc, 20 ee 4c 0e, 58 a1 6b ff, a0 20 a2 23

IOS15 base hash:
74 7c e3 33, 83 94 97 d7, a2 86 67 47, 55 61 83 0a, d0 3c 60 48

IOS14 base hash:
3d 56 0e 38, ce 93 90 4f, 42 b7 8f e9, b7 86 f1 a8, f9 39 b6 ce

IOS13 base hash:
5e a2 9d 72, 7e 56 37 26, 3f 62 3d 78, 1c 03 d2 f3, f5 40 52 5c

IOS12 base hash:
ba bf a4 78, da 4e 06 ec, f0 53 1a f0, 7f ad e2 eb, ff 3f cb 5d

IOS9 base hash:
7c 7a 60 0f, e4 85 77 89, 64 5a a1 a0, be a3 4d 59, 83 68 75 a6

 

[Lacius]

I was trying to install bootmii when I discovered the problem. The instructions on the website were really vague so I couldn't figure it out. The only things I installed were Nintendont which was working fine and priiloader. I activated the region free, and no update from disc/online system menu hacks but disabling them didn't fix anything.

System check below.

Spoiler

aa 01 bd 67, 7c 20 dc 28, 9c c6 b0 c9, 48 4b d3 f7, cd bc 4b 10

IOS57 base hash:
e7 46 07 56, 4c e8 69 2f, cd e1 19 02, 26 d6 a1 dd, 82 4c ef 0c

IOS56 base hash:
1b cc cf 07, f1 0c d5 12, be 96 9a a5, d2 36 67 98, 30 71 e6 81

IOS55 base hash:
c5 00 19 41, 22 18 21 92, b6 39 c9 d2, 05 fe 3f b3, 43 36 ae 0c

IOS53 base hash:
78 68 c0 50, 5c d6 d5 15, 65 d7 d8 0f, f0 a2 d9 d4, 9e 1d 7d fb

IOS48 base hash:
8d 53 7a 4a, 09 51 e5 6b, 2b 65 c8 27, f0 47 bb 72, c3 5c da e2

IOS46 base hash:
f5 e0 93 27, 26 cb 68 7b, ac e7 cc 86, 39 77 71 d1, ba 9e 42 36

IOS45 base hash:
08 58 11 20, 6b 3a e5 9f, b9 10 16 8b, 8a ea 06 3d, 9c 14 80 ef

IOS43 base hash:
f8 46 be 02, 74 e7 90 a3, d9 00 9a ae, d5 95 3f 77, e3 3f ad 2a

IOS41 base hash:
6c ad 7f 85, b6 87 e3 c3, 17 4e 5c 79, 99 fd 01 83, 16 55 fa 6f

IOS38 base hash:
f5 77 6b 66, cd 74 12 ee, 19 12 5c 11, 54 bf d7 3e, d7 e4 af 4b

IOS37 base hash:
32 c7 bc 54, 92 f6 17 e2, 64 26 e3 ce, bd 36 9f 40, 42 ea e8 02

IOS36 base hash:
29 36 80 06, 7d 22 7e 9f, 1c b1 af 70, 32 69 25 6d, 73 fb 14 55

IOS35 base hash:
58 5e 04 25, 45 d4 e2 8e, 98 fe 0d cd, 76 d0 71 d6, ac 17 a0 9c

IOS34 base hash:
68 8a 19 ae, c4 9f 57 fb, 11 1b 31 49, 2b 4d b4 85, 25 a6 3f 72

IOS33 base hash:
fc cf c4 1b, fc 8c 12 9e, 1f 67 5b 42, d4 3d 10 d6, 56 4f f5 f9

IOS31 base hash:
71 5f d8 87, 67 3e 32 4c, 53 c5 00 ce, 2b 50 14 f7, f2 ff e8 31

IOS28 base hash:
5c cd 08 24, 19 7b 9a 02, 17 55 5d f9, 39 dc dc 49, 73 ea 75 6a

IOS22 base hash:
8d 84 49 8b, f5 ba 6c a8, f0 58 64 10, 40 25 cd 1c, 25 9b 8a f6

IOS21 base hash:
91 ba e4 26, 1b 49 f0 95, e0 8c 21 17, e1 fa 8b e9, 92 6d eb 1b

IOS17 base hash:
77 7b 4c cb, 9a fb fe fc, 20 ee 4c 0e, 58 a1 6b ff, a0 20 a2 23

IOS15 base hash:
74 7c e3 33, 83 94 97 d7, a2 86 67 47, 55 61 83 0a, d0 3c 60 48

IOS14 base hash:
3d 56 0e 38, ce 93 90 4f, 42 b7 8f e9, b7 86 f1 a8, f9 39 b6 ce

IOS13 base hash:
5e a2 9d 72, 7e 56 37 26, 3f 62 3d 78, 1c 03 d2 f3, f5 40 52 5c

IOS12 base hash:
ba bf a4 78, da 4e 06 ec, f0 53 1a f0, 7f ad e2 eb, ff 3f cb 5d

IOS9 base hash:
7c 7a 60 0f, e4 85 77 89, 64 5a a1 a0, be a3 4d 59, 83 68 75 a6

Make sure you follow the guide on how to post a sysCheck.

 

[frog27]

Make sure you follow the guide on how to post a sysCheck.

Whoops, wrong file.

Spoiler

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: NTSC-U
System Menu 4.3U (v513)
Priiloader installed
Drive date: 07.14.2008
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x21
Console ID: 95461547
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v4
Found 63 titles.
Found 47 IOS on this console. 18 of them are stubs.

IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249 (rev 65280): Stub
IOS250 (rev 65280): Stub
IOS254 (rev 65280): Stub
BC v6
MIOS v10
Report generated on 08/01/2019.

 

[klm_spitfire]

Sorry if I'm interrupting @frog27.

I have a question about cIOS's. There's a lot of guides saying to 'install cIOS W, with base X, into slot Y, using revision Z' but I've yet to find an explanation for why these configurations were selected in the first place. What purpose do they serve?

To give an example, there's wii.guide. Seems solid, but it does nothing to explain the reasoning or history behind why this specific configuration was selected:
Select cIOS: v10 beta52 d2x-v10-beta52
Select cIOS base: 56
Select cIOS slot: 249
Select cIOS version: 65535

There's also ModMii. Seems solid, but it suggests installing a plethora of cIOS and modifications without explaining a single shread of rationale.

Is there anywhere I can go to read up on the differences between cIOS configurations, slots, etc? Why should I choose ModMii's bloated installation process as opposed to wii.guide's leaner process (i.e, 3 cIOS installations)? While at the end of the day I'll still follow the guides, I'd like to informedly follow them, not blindly follow them. Thanks!

 

[Lacius]

Whoops, wrong file.

Spoiler

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: NTSC-U
System Menu 4.3U (v513)
Priiloader installed
Drive date: 07.14.2008
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x21
Console ID: 95461547
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v4
Found 63 titles.
Found 47 IOS on this console. 18 of them are stubs.

IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249 (rev 65280): Stub
IOS250 (rev 65280): Stub
IOS254 (rev 65280): Stub
BC v6
MIOS v10
Report generated on 08/01/2019.

In this case, I would recommend doing the following:

1. Run HackMii Installer v1.2 from the Homebrew Channel.
2. Check if it allows you to install BootMii as boot2. If it does, do it. If not, install BootMii as an IOS.
3. Power off the system.
4. If you were able to install BootMii as boot2, make a NAND backup in BootMii now. Otherwise, skip this step.
5. Download ModMii.
6. Download v4.3U of the system menu in ModMii manually (Press 1, type 4.3U, and download)
   
7. Exit ModMii.
8. Drag your sysCheck into ModMii.exe or the shortcut.
9. Follow the instructions to download all of the recommended files in ModMii.
10. Put the 4.3U system menu WAD with the others (in the COPY_TO_SD folder) if it isn't already there.
11. Put everything in COPY_TO_SD onto your SD card.
12. Follow the outputted guide, starting with the "Install a patched IOS236" step.

--------------------- MERGED ---------------------------

Sorry if I'm interrupting @frog27.

I have a question about cIOS's. There's a lot of guides saying to 'install cIOS W, with base X, into slot Y, using revision Z' but I've yet to find an explanation for why these configurations were selected in the first place. What purpose do they serve?

To give an example, there's wii.guide. Seems solid, but it does nothing to explain the reasoning or history behind why this specific configuration was selected:
Select cIOS: v10 beta52 d2x-v10-beta52
Select cIOS base: 56
Select cIOS slot: 249
Select cIOS version: 65535

Is there anywhere I can go to read up on the differences between cIOS configurations, slots, etc? While at the end of the day I'll still follow the guides, I'd like to informedly follow them, not blindly follow them. Thanks!

IOS is like the operating system. Different IOS versions are different branches, and they're used under specific circumstances. For example, when loading the game Skyward Sword, it's going to use IOS56 to run. "56" stands of the slot where IOS56 is installed.

A cIOS is a customized IOS.

1. The cIOS version (e.g. d2x-v10-beta52) is the version of the modifications. Different versions by different people include different modifications. This is the part that's made by hacking developers.
2. The base is which IOS is to be modified. For example, if I want to play a pirated copy of Skyward Sword using a USB loader, I need to use a cIOS with a base of IOS56. The modifications above will modify a copy of IOS56 in this example.
3. The slot is where the cIOS will be installed. IOS56 is installed in slot 56, for example. A cIOS needs to be installed at a high numbered slot so it doesn't overwrite a regular IOS (e.g. 249). cIOS249 is installed as though it were a legitimate IOS called IOS249 (but there's no such thing, aside from the empty "stub" IOS249 used by Nintendo to try to overwrite cIOS 249).
4. Each IOS has revision numbers. This allows IOS files to be updated by Nintendo. IOS56, for example, has five revisions (including the initial release) on the Wii. A higher revision number means it's newer. A cIOS is usually installed with 65535 as the revision label so it isn't overwritten by a Nintendo update. 65535 tells the Wii that it's the highest possible version, due to how hex works.

 

[klm_spitfire]

In this case, I would recommend doing the following:

1. Run HackMii Installer v1.2 from the Homebrew Channel.
2. Check if it allows you to install BootMii as boot2. If it does, do it. If not, install BootMii as an IOS.
3. Power off the system.
4. If you were able to install BootMii as boot2, make a NAND backup in BootMii now. Otherwise, skip this step.
5. Download ModMii.
6. Download v4.3U of the system menu in ModMii manually (Press 1, type 4.3U, and download)
   
7. Exit ModMii.
8. Drag your sysCheck into ModMii.exe or the shortcut.
9. Follow the instructions to download all of the recommended files in ModMii.
10. Put the 4.3U system menu WAD with the others (in the COPY_TO_SD folder) if it isn't already there.
11. Put everything in COPY_TO_SD onto your SD card.
12. Follow the outputted guide, starting with the "Install a patched IOS236" step.

--------------------- MERGED ---------------------------


IOS is like the operating system. Different IOS versions are different branches, and they're used under specific circumstances. For example, when loading the game Skyward Sword, it's going to use IOS56 to run. "56" stands of the slot where IOS56 is installed.

A cIOS is a customized IOS.

1. The cIOS version (e.g. d2x-v10-beta52) is the version of the modifications. Different versions by different people include different modifications. This is the part that's made by hacking developers.
2. The base is which IOS is to be modified. For example, if I want to play a pirated copy of Skyward Sword using a USB loader, I need to use a cIOS with a base of IOS56. The modifications above will modify a copy of IOS56 in this example.
3. The slot is where the cIOS will be installed. IOS56 is installed in slot 56, for example. A cIOS needs to be installed at a high numbered slot so it doesn't overwrite a regular IOS (e.g. 249). cIOS249 is installed as though it were a legitimate IOS called IOS249 (but there's no such thing, aside from the empty "stub" IOS249 used by Nintendo to try to overwrite cIOS 249).
4. Each IOS has revision numbers. This allows IOS files to be updated by Nintendo. IOS56, for example, has five revisions (including the initial release) on the Wii. A higher revision number means it's newer. A cIOS is usually installed with 65535 as the revision label so it isn't overwritten by a Nintendo update. 65535 tells the Wii that it's the highest possible version, due to how hex works.

I see, thanks! So the Wii only reserves 2 bytes for each IOS revision label and by setting the label to the max possible value we prevent slot overwrites from official updates? Neat, that's nice to know. Regarding cIOS versions, wii.guide suggests installing the modified IOS 56, 57, and 58, into the slots 249, 250, and 251. To use your example, if I load a pirated copy of Skyward Sword using a USB loader does the USB loader always expect cIOS 56 to be in slot 249? And what about 57 and 58 in order to access different system resources? I assume these are used by other games? Do mainstream USB loaders always expect cIOS 57 and 58 to be in slots 250 and 251?

 

[Lacius]

I see, thanks! So the Wii only reserves 2 bytes for each IOS revision label, hence the reason for setting it to 2^16 (i.e, the maximal value for a 2 byte number)?

That is correct.

Regarding cIOS versions, wii.guide suggests installing the modified IOS 56, 57, and 58, into the slots 249, 250, and 251. To use your example, if I load a pirated copy of Skyward Sword using a USB loader does the USB loader always expect cIOS 56 to be in slot 249?

That depends on which USB loader you're using. Some auto-detect, and some don't. Regardless, Skyward Sword will require cIOS 249 in this (common) example.

And what about 57 and 58? I assume these are used by other games?

A lot of different IOS branches are used by games. Twilight Princess uses IOS9, Animal Crossing uses IOS38, etc. Almost all games, however, can run using IOS56 (or a cIOS that uses IOS56 as a base), and the games that can't need IOS57 or IOS58.

Do mainstream USB loaders always expect cIOS 57 and 58 to be in slots 250 and 251?

That is correct.

 

[frog27]

In this case, I would recommend doing the following:

1. Run HackMii Installer v1.2 from the Homebrew Channel.
2. Check if it allows you to install BootMii as boot2. If it does, do it. If not, install BootMii as an IOS.
3. Power off the system.
4. If you were able to install BootMii as boot2, make a NAND backup in BootMii now. Otherwise, skip this step.
5. Download ModMii.
6. Download v4.3U of the system menu in ModMii manually (Press 1, type 4.3U, and download)
   
7. Exit ModMii.
8. Drag your sysCheck into ModMii.exe or the shortcut.
9. Follow the instructions to download all of the recommended files in ModMii.
10. Put the 4.3U system menu WAD with the others (in the COPY_TO_SD folder) if it isn't already there.
11. Put everything in COPY_TO_SD onto your SD card.
12. Follow the outputted guide, starting with the "Install a patched IOS236" step.

--------------------- MERGED ---------------------------


IOS is like the operating system. Different IOS versions are different branches, and they're used under specific circumstances. For example, when loading the game Skyward Sword, it's going to use IOS56 to run. "56" stands of the slot where IOS56 is installed.

A cIOS is a customized IOS.

1. The cIOS version (e.g. d2x-v10-beta52) is the version of the modifications. Different versions by different people include different modifications. This is the part that's made by hacking developers.
2. The base is which IOS is to be modified. For example, if I want to play a pirated copy of Skyward Sword using a USB loader, I need to use a cIOS with a base of IOS56. The modifications above will modify a copy of IOS56 in this example.
3. The slot is where the cIOS will be installed. IOS56 is installed in slot 56, for example. A cIOS needs to be installed at a high numbered slot so it doesn't overwrite a regular IOS (e.g. 249). cIOS249 is installed as though it were a legitimate IOS called IOS249 (but there's no such thing, aside from the empty "stub" IOS249 used by Nintendo to try to overwrite cIOS 249).
4. Each IOS has revision numbers. This allows IOS files to be updated by Nintendo. IOS56, for example, has five revisions (including the initial release) on the Wii. A higher revision number means it's newer. A cIOS is usually installed with 65535 as the revision label so it isn't overwritten by a Nintendo update. 65535 tells the Wii that it's the highest possible version, due to how hex works.

So that fixed my system menu thank you for all the help but now Priiloader seems to be uninstalled. The system boots to the regular wii menu the button in the homebrew channel seems to just be the priiloader installer. Should I install it again or is there some other way to access priiloader? Holding the reset button while booting doesn't do anything.

 

[Lacius]

So that fixed my system menu thank you for all the help but now Priiloader seems to be uninstalled. The system boots to the regular wii menu the button in the homebrew channel seems to just be the priiloader installer. Should I install it again or is there some other way to access priiloader? Holding the reset button while booting doesn't do anything.

Also unrelated but whenever I try to use the homebrew browser it crashes after about a minute and gives me a screen posted below.

By installing the 4.3U system menu, you overwrote Priiloader. It needs to be reinstalled.

Before you reinstall Priiloader, make a NAND backup in BootMii if you haven't already done so.

 

[frog27]

By installing the 4.3U system menu, you overwrote Priiloader. It needs to be reinstalled.

Before you reinstall Priiloader, make a NAND backup in BootMii if you haven't already done so.

All set and working thanks.

 

[klm_spitfire]

That is correct.


That depends on which USB loader you're using. Some auto-detect, and some don't. Regardless, Skyward Sword will require cIOS 249 in this (common) example.


A lot of different IOS branches are used by games. Twilight Princess uses IOS9, Animal Crossing uses IOS38, etc. Almost all games, however, can run using IOS56 (or a cIOS that uses IOS56 as a base), and the games that can't need IOS57 or IOS58.


That is correct.

Thanks, that makes a lot of sense!

Might be getting a bit more into the weeds, but is the general idea that USB loaders inspect pirated/backed-up games, detect the IOS they require and, if IOS57 or IOS58 is required, the game is loaded with a cIOS based on IOS 57 or 58; and otherwise, the game is loaded with a cIOS based on IOS56? Also, what resources do games that load with IOS 57 and 58 have that most other games don't need?

 

[Lacius]

Might be getting a bit more into the weeds, but is the general idea that USB loaders inspect pirated/backed-up games, detect the IOS they require and, if IOS57 or IOS58 is required, the game is loaded with a cIOS based on IOS 57 or 58; and otherwise, the game is loaded with a cIOS based on IOS56?

That's how they generally work.

Also, what resources do games that load with IOS 57 and 58 have that most other games don't need?

Many USB loaders will display the required IOS for each game on the menu. Apps like Wii Backup Manager do the same. If it's IOS57, you should use a cIOS with that as a base. If it's IOS58 (rare), you should use a cIOS with that as a base. If it's anything else, you should use a cIOS with IOS56 as a base.

 

[klm_spitfire]

Thanks! You've given me a lot of clarity. Did some reading and I see that games that use IOS58, like Your Shape, leverage support for the 2nd USB port -- while other games don't. Neat.

So it would seem like the ModMii guide has a very bloated setup process as compared to the guide I referenced earlier, wii.guide. What is the need of installing all of the additional IOS's? It seems like overkill. I mean, here's the list of IOS installations ModMii proposed to me:

Spoiler: ModMii IOS List

• IOS11v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS20v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS30v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS40v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS50v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS52v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS60v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS70v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS80v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• cIOS202[60]-v5.1R
• cIOS222[38]-v4
• cIOS223[37-38]-v4
• cIOS224[57]-v5.1R
• cIOS249[57]-d2x-v8-final
• cIOS250[56]-d2x-v8-final
• RVL-mios-v10
• IOS9-64-v1034
• IOS12-64-v526
• IOS13-64-v1032
• IOS14-64-v1032
• IOS15-64-v1032
• IOS17-64-v1032
• IOS21-64-v1039
• IOS22-64-v1294
• IOS28-64-v1807
• IOS31-64-v3608
• IOS33-64-v3608
• IOS34-64-v3608
• IOS35-64-v3608
• IOS36-64-v3608
• IOS37-64-v5663
• IOS38-64-v4124
• IOS41-64-v3607
• IOS43-64-v3607
• IOS45-64-v3607
• IOS46-64-v3607
• IOS48-64-v4124
• IOS53-64-v5663
• IOS55-64-v5663
• IOS56-64-v5662
• IOS57-64-v5919
• IOS58-64-v6176
• IOS61-64-v5662
• IOS62-64-v6430

--------------------- MERGED ---------------------------

For instance, ModMii proposes installing "RVL-mios-v10", but I'd only install that custom MIOS if I wished to use DIOS MIOS, right? Doesn't seem necessary given we have Nintendont.

--------------------- MERGED ---------------------------

Or are some of those IOS's official IOS that ModMii recommends installing for general compatibility? Sorry for all the questions haha.

 

[XFlak]

If the filename states IOS then it's an original IOS. If it reads cIOS then it's a custom/modified IOS.

The disc channel on a virgin wii will detect what standard IOS is needed by the particular game and load that (I. E. IOS36). This is very different from usb loaders which will use whatever cIOS is installed to slot 249 (or 250, or a whatever slot is selected in the settings). USB loaders DO NOT inspect games and load different IOSs based on the game. Rather we have different cIOSs with different compatibility. That's why you have more than 1 installed so of 1 doesn't work for a particular game you can switch to a different cios slot for just that 1 particular game. In any case, this is all rendered moot now because we have 1 CIOS that works in all situations for just about all games. This is the cios modmii will tell u to install to slot 249 (in older versions it was slot 250) is of course d2x Cios 249 base 57 v8 final (which is the same as v10 beta 52). So really that's all you need, but no harm in installing backup cios's to other unused slots.

Now there are a handful of games that don't work with any cios, for these you would need to set up sneek or neek, this is basically an emulated wii system running off a hard drive or SD card. This will work much the same wii as the disc channel of a virgin wii like I described above, where it will load the unique IOS called for by the specific game. Then it gets even more confusing because you can have a USB loader that can also use neek in combination with a CIOS to basically get the best of both worlds. Check out modmii's usage page, I wrote up a pretty decent description of what sneek is and how it works on that page.

Modmii will have u install a cMIOS because it will work with original gamecube discs as well as backup discs (assuming the wii hardware is capable). This can be disabled in ModMii's settings.

Edit:
ModMii will have you update your standard original unmodified IOSs by default (again this can be disabled in the settings). By installing these, it will ensure the wii can play the latest original discs from the disc channel without requiring an internet connect to conduct an official Nintendo update (which may also overwrite some other mods in the process). So by installing these IOSs it basically serves to update the wii while still avoiding an official update.

There's some other software out there like pimp my wii and ciosCorp or darkCorp that will install patched cIOSs overwriting ALL the standard IOSs. This allows you to play backup discs from the disc channel without a modchip... but it messed up a bunch of other shit in the process (all to avoid having 5o load backup discs from an app versus the disc channel, so silly if you ask me). This kind of set up is generally frowned upon in the community, and to be honest it's obsolete and inferior since the scene has evolved to usb loaders instead of backup discs. Anyway, modmii will overwrite any IOSs that are patched that shouldn't be with the same original unmodified versions that you would get from a Nintendo update. This allows critical software to behave normally, like the hackmii installer.

There's a solid reason for everything modmii recommends in its "bloated installation". Modmii installs extra brick protection that is difficult to explain but long story short, if u downgrade certain wii's, or upgrade certain other wii's, you can brick your console. Modmii installs a patched ios60 (an optimal one size fits all system menu IOS, originally from 4.1 firmware) to the IOS slots used by ALL system menu's. This will save these types of wii's from bricking during AND after the softmod process. So if after you use modmii and you decide to downgrade a newer LU64+ wii to 3.2 for no good reason but stupidity, you won't brick. Anyway, this too can be disabled but I felt the need to respond and justify your "bloated installation" comment. It's all good though, and I hope this long post helps to clarify things for you

 

[SonicRings]

I can actually just plug the disc drive back in, no need for swapping drives. The problem with this drive is the plastic mechanism that seats the disc once inserted. Everything motorized works, and it can read discs, but the plastic piece that seats the disc doesn't work. It needs a little manual help that I can provide with my fingers when the Wii is open.

Therefore, the drive should work perfectly fine as long as no discs are involved. The Wii should detect it as plugged in and working just fine with no disc in.

I'll post back in maybe a dozen or so hours with my progress!

I've plugged the cable back into the drive so now all the drive's cables are plugged in, and I'm happy to report that the Wii no longer crashes. I've launched Sonic Colors 6 times, well over the usual max of 3 times, and it didn't crash once.

At the same time this is kind of a bummer because I was really hoping to make a silent Wii, but that looks like it's not possible (at least not without desoldering the motors, which I'm not willing to do as I don't like to make irreversible changes.) It looks like this Wii will be sitting on my pile of Wiis with a "disc drive does not function" sticker slapped on ¯\_(°□°)_/¯

 

[klm_spitfire]

@XFlak

Thanks for your response! You definitely helped clarify a lot for me, especially with respect to ModMii. I do apologise if my word choice came across as direspectful, that definitely wasn't my intent. It was somewhat baffling to see how much more comprehensive ModMii was compared to other guides floating around the web. I wasn't really sure what everything it recommended installing was used for, and it felt like a lot to install given I didn't really understand the items' individual purposes. Now that I have that understanding, it seems perfectly reasonable and logical

To make sure I follow, the installables I listed in my previous post can be summarized as:

• The latest official version of IOS 9, 12, ..., 62 which are being installed in order to provide compatibility with any original game disks which require the latest versions of said IOS's.
• A patched IOS 60 which is installed in place of of IOS 11, 20, ..., 80 and is designed to prevent potential issues with the Wii should an incompatible downgrade / upgrade occur.
  
• Custom IOS's (i.e, 202, 222, ..., 250) for use by custom software and backup loaders which provide different compatibility levels with respect to the software / games they can run -- although cIOS 249 based on IOS 56 provides the broadest compatibility for playing backup games.
• A cMIOS for use with playing backup GameCube games.

Is that worded correctly?

Also, I've got some more related questions lol:

1. What does the "64" in the name of the official IOS files indicate (i.e, IOSXX-64-vXXXX)?
2. In your opinion, is there a strong benefit for using a cMIOS in lieu of Nintendont?
3. If I do hit an edge-case game that isn't compatible with cIOS 249, how would I determine which of the fallback cIOS's to load? Is there a compatibility list somewhere (perhaps contained within ModMii that I might've missed)?

--------------------- MERGED ---------------------------

Oh, and on an unrelated note, does anyone know why my Wii is able to successfully install Bootmii to /boot2 yet is unable to actually display the Bootmii menu before booting into the System Menu? I've tried playing with Bootmii's configuration file to no avail, the settings don't seem to be having any sort of effect.

 

[tswntk]

• The latest official version of IOS 9, 12, ..., 62 which are being installed in order to provide compatibility with any original game disks which require the latest versions of said IOS's.
• A patched IOS 60 which is installed in place of of IOS 11, 20, ..., 80 and is designed to prevent potential issues with the Wii should an incompatible downgrade / upgrade occur.
  
• Custom IOS's (i.e, 202, 222, ..., 250) for use by custom software and backup loaders which provide different compatibility levels with respect to the software / games they can run -- although cIOS 249 based on IOS 56 provides the broadest compatibility for playing backup games.
• A cMIOS for use with playing backup GameCube games.

Is that worded correctly?

Also, I've got some more related questions lol:

1. What does the "64" in the name of the official IOS files indicate (i.e, IOSXX-64-vXXXX)?
2. In your opinion, is there a strong benefit for using a cMIOS in lieu of Nintendont?
3. If I do hit an edge-case game that isn't compatible with cIOS 249, how would I determine which of the fallback cIOS's to load? Is there a compatibility list somewhere (perhaps contained within ModMii that I might've missed)?

--------------------- MERGED ---------------------------

Oh, and on an unrelated note, does anyone know why my Wii is able to successfully install Bootmii to /boot2 yet is unable to actually display the Bootmii menu before booting into the System Menu? I've tried playing with Bootmii's configuration file to no avail, the settings don't seem to be having any sort of effect.

not correct:

a. patches ios 60 is installed only to ios 60,70,80, (and 90?) which are system menu ios required for system menu 4.1,4.2 and 4.3 in case messed up system downgrade/upgrade or hackig korean Wii
b. with Nintendont, you won't need cMios; so it is better to use original Mios (as suggested by Modmii - RVL-mios-v10)
2. cMios are actually obseleted by Nintendont
3. If cios 249 doesn't work then try cios 250/251. If nothing works, cherck you game if it is not corrupted and then ask for help here

c. Are you sure you have installed bootmii as boot2 not as ios? Only the earlier batches of Wii (produced before 2009) have a vunerable boot2 that can accept bootmii as boot2. Newer Wii has that vunerable boot2 patched so you can only install bootmii as ios which is "useless" for brick protection. In that case , priiloader is a must/only brick protection you have.

 

[SonicRings]

not correct:

a. patches ios 60 is installed only to ios 60,70,80, (and 90?) which are system menu ios required for system menu 4.1,4.2 and 4.3 in case messed up system downgrade/upgrade or hackig korean Wii
b. with Nintendont, you won't need cMios; so it is better to use original Mios (as suggested by Modmii - RVL-mios-v10)
2. cMios are actually obseleted by Nintendont
3. If cios 249 doesn't work then try cios 250/251. If nothing works, cherck you game if it is not corrupted and then ask for help here

c. Are you sure you have installed bootmii as boot2 not as ios? Only the earlier batches of Wii (produced before 2009) have a vunerable boot2 that can accept bootmii as boot2. Newer Wii has that vunerable boot2 patched so you can only install bootmii as ios which is "useless" for brick protection. In that case , priiloader is a must/only brick protection you have.

Wait what, I don't remember saying any of that lol

 

[klm_spitfire]

a. patches ios 60 is installed only to ios 60,70,80, (and 90?) which are system menu ios required for system menu 4.1,4.2 and 4.3 in case messed up system downgrade/upgrade or hackig korean Wii

In the list of installables I referenced above, ModMii has the following files:

• IOS11v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS20v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS30v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS40v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS50v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS52v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS60v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS70v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS80v16174(IOS60v6174[FS-ES-NP-VP-DIP])

All of these files have the same filename suffix: "(IOS60v6174[FS-ES-NP-VP-DIP])". I presumed this meant that all of these IOS are patched versions of IOS 60. If that's not the case, how come IOS11, IOS20, IOS30, etc, are all denoted with the same suffix?

b. with Nintendont, you won't need cMios; so it is better to use original Mios (as suggested by Modmii - RVL-mios-v10)
2. cMios are actually obseleted by Nintendont

I see, my apologies. I somehow mistook that file, RVL-mios-v10, as the installer file for a cMIOS, not the latest official MIOS. That clears that up, and makes perfect sense. I agree that there shouldn't be a need for a cMIOS given Nintendont exists.

3. If cios 249 doesn't work then try cios 250/251. If nothing works, cherck you game if it is not corrupted and then ask for help here

Gotcha. This reminds me of a question I had earlier. Maybe I missed it, but how come ModMii doesn't seem to install cIOS 251 with a 58 base, whereas some other guides do? @XFlak

c. Are you sure you have installed bootmii as boot2 not as ios? Only the earlier batches of Wii (produced before 2009) have a vunerable boot2 that can accept bootmii as boot2. Newer Wii has that vunerable boot2 patched so you can only install bootmii as ios which is "useless" for brick protection. In that case , priiloader is a must/only brick protection you have.

Yup, I have it installed to both /boot2 and as an IOS with both installations claiming to be successful. I've got Priiloader installed to counteract the issue with /boot2, but it's really strange. I even have a second, old Wii (with a failing GPU) that I was able to get BootMii working properly with. There's a few other people online who've reported the same issue I'm running into, but no one seemed to be able to figure out what's happening...

--------------------- MERGED ---------------------------

Wait what, I don't remember saying any of that lol

Lmaoooo

 

[tswntk]

In the list of installables I referenced above, ModMii has the following files:

• IOS11v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS20v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS30v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS40v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS50v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS52v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS60v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS70v16174(IOS60v6174[FS-ES-NP-VP-DIP])
• IOS80v16174(IOS60v6174[FS-ES-NP-VP-DIP])

All of these files have the same filename suffix: "(IOS60v6174[FS-ES-NP-VP-DIP])". I presumed this meant that all of these IOS are patched versions of IOS 60. If that's not the case, how come IOS11, IOS20, IOS30, etc, are all denoted with the same suffix?

not sure about IOS11, maybe really ancient system menu IOS?
IOS 52 I think is Korean related. Note, if you update via Nintendo officially without protection, Korean Wii will brick.
The others are system menu IOS prior to system menu 4.0. Unless you want to downgrade so far back, you can leave them or install them just in case.

Gotcha. This reminds me of a question I had earlier. Maybe I missed it, but how come ModMii doesn't seem to install cIOS 251 with a 58 base, whereas some other guides do?

cIOS base on 58 have really low game compatibility; that maybe why Modmii doesn't recommend it. I heard some musical games (not my type of games) may require it. You can leave it until you really need it or install it manually just in case. Some games may require cIOS with base 38 to be fully functional (like using usb keyboards) too.

Yup, I have it installed to both /boot2 and as an IOS with both installations claiming to be successful. I've got Priiloader installed to counteract the issue with /boot2, but it's really strange. I even have a second, old Wii (with a failing GPU) that I was able to get BootMii working properly with. There's a few other people online who've reported the same issue I'm running into, but no one seemed to be able to figure out what's happening...

beats me... You may check online with the Wii's serial number to see if it really is bootmii@boot2 compatible. https://gbatemp.net/threads/bootmii-boot2-wii-serial-numbers.205180/