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

[Etheboss]

Wii Backup Manager v4.3.0 build 69 is correct, I accidentally wrote v3.8.0 but it is v4.3.0

Xflak, actually the version number starts with a zero, and, but it's already said, new version is 0.4.4 build 73.

 

[XFlak]

thx, I'll update it to the most recent version for my next update, but I got a bunch of other things to do first

 

[Flinger]

I have a 8GB SanDisk Cruzer USB stick. According to the compatibility list it should work, but it probably needs to be WBFS not FAT32. I already ran the ModMii wizard and chose the FAT32 option. Is there a way to get this to work now? When I try to load it up as is it hangs for a split second then I see the light gray Wii squares before it pops up the normal Wii interface. So it is dropping back to the home screen.

 

[XFlak]

Confirm that you have \apps\usbloader_cfg\boot.dol on either the sd card or usb hdd. If you have that saved there and the forwarder channel continues to reload you back to the wii menu then it is likely a compatibility problem. If you need to format the HDD as wbfs to make it work, make sure u have the usbloader app on the sd card then format the HDD as WBFS using WiiBackupManager.

Cheers

 

[d3dcomplx]

I updated my softmods on a 4.2U wii. Everything went very smooth, no errors what-so-ever! This saved me a ton of time, Thank You so very much!

 

[MLRX]

@MLRX, are you sure it was copy_to_sd and not copy_to_usb? Have you tried more than once?

I just tryed building a plain 4.2U NAND without the Homebrew Filter Channel or anything extra like the Mii Channel and got a screen I hadn't seen before.
It also opened ShowMiiWads which I hadn't ever done before.
I tryed my original NAND setup and when it got to the part where it should have open ShowMiiWads, ModMii closed.

So you can see the error yourself, here is everything I typed into the program.

i agree
s
2
sd
d
u
4.2
y
y
dml
y
n
(at the part where it asks what channels you want installed)
s
n
n
n
n
y
n
n
(it now asks if you're ready)
y
(it downloads the wads and closes)

 

[XFlak]

worked perfectly fine for me. Can someone else please try the above and see if ModMii crashes? Thx!

 

[ChrisLuther]

Worked fine. Everything downloaded as it should and got the success page.

 

[Lucif3r]

I havnt followed the whole issue, so Im not 100% sure what the issue actually is but...

I ran ModMii and followed the step of MLRX, and everything went fine. No errors or download failures etc.

 

[MLRX]

I have no idea at all why it won't work. I've tryed it so many times to get the same outcome.
Could someone maybe zip up the NAND that they made using those settings and post it here please?

Edit: I think peerblock was blocking some downloads intrupting the process, which explains why it works without the extras. It works now. Thank you.

 

[XFlak]

Glad u got it working

 

[geovalley]

@MLRX: what OS are you running for ModMii? Which native language do you use?

@XFlak:

I remembered some time ago, I ran ModMii and it asked me if I want to enter the serial number as an option. It's gone. Found it's removed since 4.7.3. Is there a chance put it back? I think It's really a useful feature.
The reason is that I am using a JPN version Wii. I didn't like it but when we first bought it, it's the only available version Wii. I built a US version nand and ran it perfectly except every time I sync the wiimote between real and emulated, it's painful. It takes a long time (a minute or two or even three) to sync up until I found a way to modify the emulated nand serial number to the same as my physical Wii.
Right! Althought the number started LJHxxxx, there is a USA setting.txt available for me. After use it, no more re-sync any more.

 

[XFlak]

I had a bunch of ppl do extensive testing and they determined that the serial # in the setting.txt is irrelevant to the wiimote sync issue. If you want to build a custom setting.txt just open a cmd window in ModMii's support folder and type settings.exe {serial #}

 

[JoostinOnline]

I had a bunch of ppl do extensive testing and they determined that the serial # in the setting.txt is irrelevant to the wiimote sync issue. If you want to build a custom setting.txt just open a cmd window in ModMii's support folder and type settings.exe {serial #}

The reason it wasn't syncing at first is because setting.txt and SYSCONF together are what link the Wii remote.

 

[geovalley]

Well, could it be due to they are using the same region?
I am using different region and very very very very very very very hard to sync up unless using the one generated same serial number. But like you mentioned it worked using settings.exe.
This should be in a low priority changing if you are busy. No hustle

 

[tueidj]

The reason it wasn't syncing at first is because setting.txt and SYSCONF together are what link the Wii remote.

Wiimote information is stored in SYSCONF only. setting.txt is meant to contain static values that are never changed. The wii's serial number is not involved in anything to do with the wiimotes.

 

[XFlak]

thx for the clarification mate!

 

[JoostinOnline]

The reason it wasn't syncing at first is because setting.txt and SYSCONF together are what link the Wii remote.

Wiimote information is stored in SYSCONF only. setting.txt is meant to contain static values that are never changed. The wii's serial number is not involved in anything to do with the wiimotes.

So all it takes is SYSCONF? I thought it was the combination of the two.

 

[geovalley]

The reason it wasn't syncing at first is because setting.txt and SYSCONF together are what link the Wii remote.

Wiimote information is stored in SYSCONF only. setting.txt is meant to contain static values that are never changed. The wii's serial number is not involved in anything to do with the wiimotes.

Any code shows that? Then how to explain the long sync? I think some people said serial number to do with wiimote sync must have a reason or proof!
I don't have the code, but I do have the long sync problem unless using same serial number. Then syncing is just a snap
For what I am thinking, wiimote must have some kind of intelligence. Whenever we see things in Wii, we can only see in Wii system, which is where nand from. We don't see anything in wiimote. If we prove wiimote information stored in SYSCONF, it does not prove wiimote not store Wii serial number. To me, if I were the programmer for wiimote, I'll do this. It sounds like a common sense.

 

[tueidj]

Any code shows that? Then how to explain the long sync? I think some people said serial number to do with wiimote sync must have a reason or proof!
I don't have the code, but I do have the long sync problem unless using same serial number. Then syncing is just a snap.

http://wiibrew.org/w...uetooth_Pairing

Bluetooth pairing must be initiated by the host by sending a "Require Authentication" HCI command to its bluetooth device. The bluetooth device will ask the host for a link key, which must be rejected so it will ask for a PIN-Code. [...] If connecting by holding down the 1+2 buttons, the PIN is the bluetooth address of the wiimote backwards, if connecting by pressing the "sync" button on the back of the wiimote, then the PIN is the bluetooth address of the host backwards.
[...]
If the host successfully bonded with the wiimote and established an HID connection the wiimote will save the bluetooth address of the host and enable single press reconnection.

Common sense is storing the MAC address of the device you want to communicate with, not same randomly assigned id that won't let you directly talk to the system you're looking for.