Hacking Best Way to Mod Any Wii: ModMii for Windows: Official Support Thread

[pplucky]

I've now twice tried to install the latest cios 249 base 56 r21-d2x-v3 modmii (r21003)
but cfg list's it in cios info: as
ios 249 base: ?? (r21003)

my ios 250 base: 57 r21-d2x-v3 modmii (r21003) shows up fine.

It also happens to me with slot 248, but I suppose that is because I changed the default slot from 249 to 248.

I should have:

ios 248 base: 57 r21-d2x-v3 modmii (r21003)

and I also have

ios 248 base: ?? (r21003).

 

[Fox888]

Yep i got the same thing as pplucky

change the r21d2xv3 249 version with base 37 and 38 to

247 base 37 and 248 base 38 they show this :

ios247 base ?? (rev21)
ios248 base ?? (rev21)
ios249 base 56 r21-d2x-v3 ModMii (r21)
ios250 base 57 r21-d2x-v3 ModMii (r65535)

so changing the default ios slots gives an base ??

 

[pplucky]

Yep i got the same thing as pplucky

change the r21d2xv3 249 version with base 37 and 38 to

247 base 37 and 248 base 38 they show this :

ios247 base ?? (rev21)
ios248 base ?? (rev21)
ios249 base 56 r21-d2x-v3 ModMii (r21)
ios250 base 57 r21-d2x-v3 ModMii (r65535)

so changing the default ios slots gives an base ??

Changing default IOS slot probably generates a different IOS hash (which is the basis for this IOS base recognition in Cfg Usb Loader).

@Xflak: what do you think of engineering with oggzee/Dr. Clipper the generation of an hash file from ModMii, based on the downloaded cIOS files? If Cfg Usb Loader could read that file instead of having it somewhere fixed in the source, that would be awesome!

Thanks in advance.

 

[chop]

But I haven't changed anything, I've installed the wad file that I downloaded as is.

 

[RavRob]

installing 4.1 will not make a difference to backup disc playback, so don't waste ur time. Just reinstall your cIOS249 and that should get neogamma working again. All neogamma uses to play backup discs is cIOS249 and the disc

Wii #3 can't play backup discs, but u know that already

Worked the very best XFlak


Thanks

 

[oggzee]

@Xflak: what do you think of engineering with oggzee/Dr. Clipper the generation of an hash file from ModMii, based on the downloaded cIOS files? If Cfg Usb Loader could read that file instead of having it somewhere fixed in the source, that would be awesome!

That's not a bad idea, if it's possible to automate all the hashes..?
An output like this is what I would need:

Spoiler

CODEÂÂÂÂ{ 249, {0x00ed2993, 0x0bae0cb2, 0xc7e430a2, 0x2e6eaf18, 0x156a9a70}, "37 r21-d2x-v1" },
ÂÂÂÂ{ 249, {0x00d74607, 0x2d3fe23e, 0x47ecb019, 0x0f5d4380, 0x37ea6b50}, "38 r21-d2x-v1" },
ÂÂÂÂ{ 249, {0x003d11ce, 0x4eb3b8bb, 0xe2c02fda, 0x5f879e74, 0x44a257de}, "56 r21-d2x-v1" },
ÂÂÂÂ{ 249, {0x00ba4b4f, 0x27803366, 0x8d9121fa, 0x954eb5d5, 0x92242691}, "57 r21-d2x-v1" },
ÂÂÂÂ{ 249, {0x00475dce, 0x81a744dd, 0xf24157e4, 0x870fa3d8, 0xfc39fa8a}, "37 r21-d2x-v2" },
ÂÂÂÂ{ 249, {0x00711af6, 0x017c48d4, 0xea0267d3, 0x1666600b, 0x38a8fe16}, "38 r21-d2x-v2" },
ÂÂÂÂ{ 249, {0x00815782, 0x8604fe34, 0x474653b5, 0xbdbc5651, 0xf43b427a}, "56 r21-d2x-v2" },
ÂÂÂÂ{ 249, {0x00d8e857, 0x8c96eb52, 0x4d006568, 0x95cf5415, 0xdb7712e8}, "57 r21-d2x-v2" },
ÂÂÂÂ{ 249, {0x0054e91c, 0xe022e307, 0x26d72e03, 0x53b6e157, 0x42adbe49}, "37 r21-d2x-v3" },
ÂÂÂÂ{ 249, {0x000bd035, 0xe649cc22, 0x8bf647c5, 0xe0710e6a, 0xd79a5355}, "38 r21-d2x-v3" },
ÂÂÂÂ{ 249, {0x00b8ca9c, 0x9b4053a3, 0x8de94a72, 0x1192fce5, 0x098e7404}, "56 r21-d2x-v3" },
ÂÂÂÂ{ 249, {0x00e8e05f, 0x2aa4cd1e, 0x8c8f5529, 0x498f259b, 0xfa41258e}, "57 r21-d2x-v3" },
ÂÂÂÂ{ 249, {0x0028dbf1, 0x3827be46, 0x28c82eb2, 0x122325c3, 0xc72dbd46}, "58 r21-d2x-v3" },

only for the non-standard cioses and only for 249 slot, other slots are calculated automatically, or at least should...
for more details:
http://code.google.com/p/cfg-loader/source...ce/source/sys.c

 

[pplucky]

only for the non-standard cioses and only for 249 slot, other slots are calculated automatically, or at least should...
for more details:
http://code.google.com/p/cfg-loader/source...ce/source/sys.c

I would allow the possibility of one adding a non-common slot (like 248, which I use) to the file, also based on ModMii's generated hash.

Modmii could have an option just to generate the hashes for IOS common slots (like it does already now) and write them in the file, or also include other hashes for other slots...

Currently I need to keep an Excel file in order to keep track of which cIOS I have installed in each slot... With this, no one would need such a thing, as Cfg USB Loader (along with ModMii) would do the trick!

 

[goku1980]

having an issue with tranfering .wbfs games to the sneek format im stuck at ***** wit:wiimms iso tool v1.18a.beta2 r1861 been there for 20 mins any ideas?

 

[XFlak]

That's not a bad idea, if it's possible to automate all the hashes..?
An output like this is what I would need:

Spoiler

ÂÂÂÂ{ 249, {0x00ed2993, 0x0bae0cb2, 0xc7e430a2, 0x2e6eaf18, 0x156a9a70}, "37 r21-d2x-v1" },
ÂÂÂÂ{ 249, {0x00d74607, 0x2d3fe23e, 0x47ecb019, 0x0f5d4380, 0x37ea6b50}, "38 r21-d2x-v1" },
ÂÂÂÂ{ 249, {0x003d11ce, 0x4eb3b8bb, 0xe2c02fda, 0x5f879e74, 0x44a257de}, "56 r21-d2x-v1" },
ÂÂÂÂ{ 249, {0x00ba4b4f, 0x27803366, 0x8d9121fa, 0x954eb5d5, 0x92242691}, "57 r21-d2x-v1" },
ÂÂÂÂ{ 249, {0x00475dce, 0x81a744dd, 0xf24157e4, 0x870fa3d8, 0xfc39fa8a}, "37 r21-d2x-v2" },
ÂÂÂÂ{ 249, {0x00711af6, 0x017c48d4, 0xea0267d3, 0x1666600b, 0x38a8fe16}, "38 r21-d2x-v2" },
ÂÂÂÂ{ 249, {0x00815782, 0x8604fe34, 0x474653b5, 0xbdbc5651, 0xf43b427a}, "56 r21-d2x-v2" },
ÂÂÂÂ{ 249, {0x00d8e857, 0x8c96eb52, 0x4d006568, 0x95cf5415, 0xdb7712e8}, "57 r21-d2x-v2" },
ÂÂÂÂ{ 249, {0x0054e91c, 0xe022e307, 0x26d72e03, 0x53b6e157, 0x42adbe49}, "37 r21-d2x-v3" },
ÂÂÂÂ{ 249, {0x000bd035, 0xe649cc22, 0x8bf647c5, 0xe0710e6a, 0xd79a5355}, "38 r21-d2x-v3" },
ÂÂÂÂ{ 249, {0x00b8ca9c, 0x9b4053a3, 0x8de94a72, 0x1192fce5, 0x098e7404}, "56 r21-d2x-v3" },
ÂÂÂÂ{ 249, {0x00e8e05f, 0x2aa4cd1e, 0x8c8f5529, 0x498f259b, 0xfa41258e}, "57 r21-d2x-v3" },
ÂÂÂÂ{ 249, {0x0028dbf1, 0x3827be46, 0x28c82eb2, 0x122325c3, 0xc72dbd46}, "58 r21-d2x-v3" },

only for the non-standard cioses and only for 249 slot, other slots are calculated automatically, or at least should...
for more details:
http://code.google.com/p/cfg-loader/source...ce/source/sys.c

just to make sure I'm understanding this right, you are suggesting ModMii generate a file with the data above so cfg usb loader can identify new cIOSs by its hashes in the external file? And I would imagine if no matches are found in the external file, or if no such file exists then it would still show up as "???"

anyways, it would be easy to distribute that file in many ways, but certainly I could have ModMii build it, I would just need the hashes... and I'm not sure how to generate the above output. I'm sure some1 like FIX94 would be able to offer their help, or I could prolly get it done personally with a little guidance.


edit:
on a side note to anyone interested, my latest ModMii beta has the sneek installer issues all sorted out

 

[zizer]

thank XFlak, sneek installer work but it is only r150

 

[oggzee]

just to make sure I'm understanding this right, you are suggesting ModMii generate a file with the data above so cfg usb loader can identify new cIOSs by its hashes in the external file? And I would imagine if no matches are found in the external file, or if no such file exists then it would still show up as "???"

anyways, it would be easy to distribute that file in many ways, but certainly I could have ModMii build it, I would just need the hashes... and I'm not sure how to generate the above output. I'm sure some1 like FIX94 would be able to offer their help, or I could prolly get it done personally with a little guidance.

Actually i would just copy & paste that file into the source and rebuild.
But if you don't have these hashes readily available then we'll just have to keep on with the old method that is generating the hashes from an installed cios.
I also don't know how one would create the hashes without installing the cios.

 

[pplucky]

Actually i would just copy & paste that file into the source and rebuild.But that would not solve it for the non-common cIOS slots...like the ones customized through ModMii...

QUOTE(oggzee @ Mar 15 2011, 10:49 AM) But if you don't have these hashes readily available then we'll just have to keep on with the old method that is generating the hashes from an installed cios.
I also don't know how one would create the hashes without installing the cios.

This means that we either use the common cIOS slots or we have to keep this info elsewhere!

 

[oggzee]

Actually i would just copy & paste that file into the source and rebuild.But that would not solve it for the non-common cIOS slots...like the ones customized through ModMii...

QUOTE(oggzee @ Mar 15 2011, 10:49 AM) But if you don't have these hashes readily available then we'll just have to keep on with the old method that is generating the hashes from an installed cios.
I also don't know how one would create the hashes without installing the cios.

This means that we either use the common cIOS slots or we have to keep this info elsewhere!

If cfg has a hash for slot 249 it is able to detect that same cios in any other slot.
In fact it only contains hashes for slot 249 all others slots hashes are calculated.
That's the way it already works, or at least it should.

 

[pplucky]

Actually i would just copy & paste that file into the source and rebuild.But that would not solve it for the non-common cIOS slots...like the ones customized through ModMii...

QUOTE(oggzee @ Mar 15 2011, 10:49 AM) But if you don't have these hashes readily available then we'll just have to keep on with the old method that is generating the hashes from an installed cios.
I also don't know how one would create the hashes without installing the cios.

This means that we either use the common cIOS slots or we have to keep this info elsewhere!

If cfg has a hash for slot 249 it is able to detect that same cios in any other slot.
In fact it only contains hashes for slot 249 all others slots hashes are calculated.
That's the way it already works, or at least it should.

Then I have to tell you that it either doesn't work well or it is related to the fact that ModMii recently changed the d2x versions to 21003 instead of maximizing it

... Probably the second, no?

 

[XFlak]

...the old method that is generating the hashes from an installed cios...

Can you please direct me to an explanation as to how to do this? Is there an option in cfg usb-loader to calculate the hashes? Please forgive my ignorance, but I want to help.

Also, I noticed on the source of sys.c that you have hashes for ModMii 249 and ModMii 250 cIOSs... why is that? I thought you said u only needed to have the hash for 249 and other slots are not required. If for some reason there were major differences between ModMii 249 and ModMii 250 in the past, it will be because I was using Leathl's patchios.exe to change the version and slot numbers for 250 cIOSs but not 249 cIOSs. However, this has changed, and now I am using patchios.exe to change the version number even for 249 cIOSs to 21003, so we shouldn't need hashes for 250 d2x cIOSs going forward to recognize them.

 

[pplucky]

...the old method that is generating the hashes from an installed cios...

Can you please direct me to an explanation as to how to do this? Is there an option in cfg usb-loader to calculate the hashes? Please forgive my ignorance, but I want to help.

If you use v66 of Cfg Usb Loader, press 1 and 1 again to go to Global Options, you have an option called 'Show cIOS info', which will determine the cIOS installed in your Wii. After that, choose option 'Write debug.log'.

After this, if you check your usb-loader folder in your SD card or HDD, you should have 2 relevant files: debug.log and ioshash.txt, where you have the hash for the cIOS installed in the slot used to run Cfg Usb Loader...

 

[robjanssen]

A friend of mine has used ModMii to softmod his Wii with firmware 4.0.
ModMii recommends upgrading to 4.1
He chosed "Extra Brick Protection" and "DarkWiiRedTheme"
After completing the guide his Wii is bricked.
He installed BootMii boot2, so i hope he can restore his Wii.

But what went wrong?

With the "Extra Brick Protection" the following IOS is (also) downloaded:
IOS70v16687(IOS70v6687[FS-ES-NP]).wad
But 4.1 has systemenu in IOS 60.
Can this be wrong?

 

[XFlak]

What went wrong is probably you guys didn't follow the instructions to the letter. Or you could've installed other wads u had saved to the sd card by mistake. Another explanation is that something went wrong when installing your 4.1 dark wii system menu or patched IOS60. A couple other people have had issues where they weren't able to access their wii settings, but then they reinstalled the system menu (normal or themed) and that fixed their problem.
Anyways, u have bootmii @ boot2, just load it using an SD card with the bootmii folder which was created when u made a nand backup {if you're missing the folder, u can use ModMii to build config files for bootmii ("C" from Main Menu)}, then u can either restore your nand dump or access the HBC to try reinstalling the system menu and\or system menu IOS (IOS60).

To answer your other question, a patched IOS60 would've also been downloaded, and IOS70 is part of extra brick protection in case someone ever tries to install a 4.2 SM without its SM IOS.

@pplucky, thx for the info! I guess it's about time I update my cfg usb loader!

 

[oggzee]

Then I have to tell you that it either doesn't work well or it is related to the fact that ModMii recently changed the d2x versions to 21003 instead of maximizing it

... Probably the second, no?
Yes the 21003 hashes have not been added yet, but will soon.
edit: added in v66c

QUOTE(XFlak @ Mar 15 2011, 02:39 PM) Also, I noticed on the source of sys.c that you have hashes for ModMii 249 and ModMii 250 cIOSs... why is that? I thought you said u only needed to have the hash for 249 and other slots are not required. If for some reason there were major differences between ModMii 249 and ModMii 250 in the past, it will be because I was using Leathl's patchios.exe to change the version and slot numbers for 250 cIOSs but not 249 cIOSs. However, this has changed, and now I am using patchios.exe to change the version number even for 249 cIOSs to 21003, so we shouldn't need hashes for 250 d2x cIOSs going forward to recognize them.

The slot 250 hashes are commented out, I think they were required before the auto calculations for different slots was implemented...
(actually all modmii hashes based on official ioses are commented out, only the special 21+19 and d2x are required)

 

[hazzarduk1]

@Xflak, its only a minor issue, but the Homebrew browser on page 2 of modmii is too old to connect to the new servers as codemii has changed the way it connects recently. worked fine downloading and updating hbb myself and not using modmii though