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

[nerezza]

Hi, I'm having issues with NUSAD. I've followed all the instructions but I keep getting a Microsoft.NET Framework errors while downloading NUS Downloader Command Line v0.2 by wiiNinja. It gets up to 'Grabbing 00000017...' and then I get the error (full details below).

I am able to proceed after this but then at the end of the download process there are errors, I believe signifying that several files are missing.
NUSAD instructs me to delete all files with an MD5 mismatch error, unfortunately I am new to this and I have no idea how to tell which ones they are (or where to locate them).

I would like to get this working as my primary goal is to be able to download, burn and play Wii games (too poor to afford to buy legit versions). Any help would be greatly appreciated.


MICROSOFT.NET ERROR DETAILS
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
at System.Windows.Forms.Control.DefWndProc(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
at System.Windows.Forms.RichTextBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3603 (GDR.050727-3600)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
nusd
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Evan%20Page/My%20Documents/Downloads/WiiHack/NUS%20Autodownloader%20v4.1.3/nusd.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:





When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

[pepxl]

rty updating you .NET Framework, get the updates at microsoft.com

 

[bkifft]

@xflak and the other ones who are interested in wtf is going on here:
only real difference in the ticket is at 0x01e6 which got incremented by one (thus the signature from 0x0004 to 0x0103 changed, too).
this gives the value 0x101b or 4123 which happens to be the newest version of IOS38 *scratches head*.
maybe they've changed the NUS to always serve the newest version, no regard which one was requested?

more later once i've compared a few more files

ok, using a md5 checksumer reveals that a few more files have changed :

three .app's, the .tmd and the .tik.

now lets fetch v4123 and compare it to the new v3867 ....


oh noes i'm right in my assumption: when requesting v3867 one gets v4123. (at least "nusd 0000000100000026 3867" and "nusd 0000000100000026 *" result in a perfect match of files).

does that mean goodbye legal download of old revisons from NUS?


oooook: IOS 50 is still availible in the not stub version (v4889). so are they only doing this for IOSes that serve as base for cIOSes?

 

[Riicky]

@xflak and the other ones who are interested in wtf is going on here:
only real difference in the ticket is at 0x01e6 which got incremented by one (thus the signature from 0x0004 to 0x0103 changed, too).
this gives the value 0x101b or 4123 which happens to be the newest version of IOS38 *scratches head*.
maybe they've changed the NUS to always serve the newest version, no regard which one was requested?

more later once i've compared a few more files

ok, using a md5 checksumer reveals that a few more files have changed :

three .app's, the .tmd and the .tik.

now lets fetch v4123 and compare it to the new v3867 ....


oh noes i'm right in my assumption: when requesting v3867 one gets v4123. (at least "nusd 0000000100000026 3867" and "nusd 0000000100000026 *" result in a perfect match of files).

does that mean goodbye legal download of old revisons from NUS?


oooook: IOS 50 is still availible in the not stub version (v4889). so are they only doing this for IOSes that serve as base for cIOSes?

Well if they really are blocking downloads of older IOS's..then let's hope someone around here was and is a pack rat and downloaded every one lol...I myself started to grab every version of every IOS b4 but gave up

 

[nerezza]

rty updating you .NET Framework, get the updates at microsoft.com

I have v3.5 installed. Tried installing the latest and it said it wasn't compatible? Idk.

 

[sasha_spb_ru]

oh noes i'm right in my assumption: when requesting v3867 one gets v4123. (at least "nusd 0000000100000026 3867" and "nusd 0000000100000026 *" result in a perfect match of files).

does that mean goodbye legal download of old revisons from NUS?

No no no, you just using nusd wrong.
Because you trying to get IOS38 using command "nusd 0000000100000026 3867" nusd will download it into folder "0000000100000026", and it will download v3867, of course.
But when you trying to get IOS38 using command "nusd 0000000100000026" nusd will get latest version (4123) in to SAME folder "0000000100000026" and it will cause merge of old and new files and your confusion.
Just rename or delete old folder, and versions will be different as always.

So as I understand, actually, content of old IOSes is not modified - only cert and/or tmd changed when nusd downloads files (they differ even when using different nusd versions for same file for download).
And I managed to get all upgrades from 4.1e to 4.2e with no MD5 mismatch, except only 4 files (IOSes 12, 13, 14, 28).
If modified cert and tmd not affects IOSes installation and functionality then it is no big deal.
Maybe someone who have older consoles with boot2 bootmii brick protection (my console is without bootmii boot2 support) can try to install some non important IOSes which have MD5 mismatch and let us know if they succeed?

 

[XFlak]

@xflak and the other ones who are interested in wtf is going on here:
only real difference in the ticket is at 0x01e6 which got incremented by one (thus the signature from 0x0004 to 0x0103 changed, too).
this gives the value 0x101b or 4123 which happens to be the newest version of IOS38 *scratches head*.
maybe they've changed the NUS to always serve the newest version, no regard which one was requested?
Nonononono, u are mistaken (thank god!)---Explanation below.----, but thx for looking into this, I need all the help I can get trying to make sense of this.

now lets fetch v4123 and compare it to the new v3867 ....
oh noes i'm right in my assumption: when requesting v3867 one gets v4123. (at least "nusd 0000000100000026 3867" and "nusd 0000000100000026 *" result in a perfect match of files).

I analyzed the same files u did (IOS38v3867 vs. IOS38v4123-the latest version), here are the results of my analysis (including MD5 hash's)
Both versions were DL'ed today (so after the 4.3 update)

883F48866F5D7B80850579BC63AE90BA *00000001---common, found in both versions
394298E4C9FF287E69020F2405423EB4 *0000000100000026.wad---changed
F86C53DB2297DA874B9358A7E84ABFAB *00000002---common, found in both versions
B7811E8362AB56034D9F152867F94915 *00000003---common, found in both versions
C1F6651E28C41D98514D786F90DA8553 *00000004---removed-found in v3867 but not latest version
3FF6465BAC262FD2B285A0490A98622B *00000005---common, found in both versions
66F8785414E0E9C031C89EB8829988DF *00000006---common, found in both versions
E99CE5BAF029ED7820147404CB24281B *00000007---common, found in both versions
C7D2C8F7E0FA2E9A81B0903951918D77 *00000008---common, found in both versions
1A62AF9463ED1C507B2AD98E60BF34DB *00000009---common, found in both versions
C163E716E5075391D60B2BE650A01D6D *0000000a---common, found in both versions
334CE4BA7EC9DB297756F30C6B6327F7 *0000000c---common, found in both versions
2CBBBA83873134E63F86493810F4EBD0 *0000000d---common, found in both versions
A6788A6C9180AB38EF74550CCF3D2D11 *00000012---removed-found in v3867 but not latest version
8438256B550C993E7C66FB8D13DF0F3E *00000013---common, found in both versions
E5657DD215A0657C03B9DDA3A6E19549 *00000014---removed-found in v3867 but not latest version
D36427EEDAD1B4E9A4B8E4CC793A9AB2 *00000015---new-found in latest version but not v3867
06246741BAB14F8CECB1944DDD033AC5 *00000016---new-found in latest version but not v3867
A9D44B11152A013A8648B813DD672898 *00000017---new-found in latest version but not v3867
5917CA6039338F83EF13E0743D1DFC83 *cetk---common, found in both versions
0E64181D31A6F6709F459705401029EC *tmd.3867---changed

as u can see, while some files have not changed from v3867 to v4123, 3 files have been removed and 3 others have been added, so the different IOSs versions are in fact different (as they should be).

I stick by by original analysis which stated that the only files to change were the *.cert and the *.tik (these files are explicitly present only when unpacking the wad though... which is why they are not in the above list). See a few posts back for the analysis, but that analysis was comparing the SAME unpacked version of IOS38, but one was grabbed before the 4.3 update and the other was grabbed after.

QUOTE(bkifft @ Jun 28 2010, 04:12 AM)

oooook: IOS 50 is still availible in the not stub version (v4889). so are they only doing this for IOSes that serve as base for cIOSes?

This is only happening to IOSs that have been changed/updated. So all historic versions of IOSs that were updated in the 4.3 update were changed in THIS LIST have changed. Even the old STUB IOS for IOS254v260 was changed after it was updated to Stub v65280. So this is not being done for IOSs serving as a base IOSs, but all IOSs that were updated.

I mentioned once before, that for all I know this could be standard ninty practice when an update comes out (since I only started analyzing IOSs after 4.2 update). Here is what I HOPE happened/happens with every update (only because it will explain everything to me).

I think that maybe whenever there is an update for an IOS, all the older IOS tik's are changed noting the most recent version #... the only factual info I am basing this on is the fact that u say the IOS38v3867 tik has been changed to note the most recent version number (so I could be wrong, and I am definitely wrong if u are mistaken).

If my theory is correct, then the IOS38v3610 tik grabbed from before the 4.3 update (see screenshot below) should note version 3867 is the most recent version... and IOS38v3610 tik grabbed from after the 4.3 update (see screenshot below) should reflect v4123 is the most recent version.

So could you please analyze these screenshots and tell me whether my guess is correct or not? That would be very helpful (somehow I think I am wrong... but its worth looking into).

IOS38v3610 tik grabbed from before the 4.3 update

Spoiler

IOS38v3610 tik grabbed from after the 4.3 update

Spoiler

edit:
@sasha, there are MANY IOSs that have changed, this is my list of older IOSs that have changed... as I mentioned before, I think only the cert and tik's have changed

Spoiler

* IOS9
* IOS12
* IOS13
* IOS14
* IOS15
* IOS17
* IOS21
* IOS22
* IOS28
* IOS31
* IOS33
* IOS34
* IOS35
* IOS36
* IOS37
* IOS38
* IOS53
* IOS55
* IOS56
* IOS57
* IOS61
* IOS70
* IOS254 (STUB)
* ALL System Menu Wads (so 4.2X, 4.1X, 3.2X etc.).

@anyone with bootmii as boot2, here are some tests is a test I would like to see done
-Install IOS60 and 4.1X System Menu (make sure u downloaded versions from AFTER the 4.3 update), then see if it works properly (ie. it doesn't delete the HBC)... then as an extra test, maybe install priiloader and see if the 4.1X system menu hacks still work (if the SM has changed in any way, I would think the SM hacks would stop working)
-download IOS38v3867 (make sure it was downloaded after the 4.3 update), then use that as a base IOS to install wanin's cIOS249 rev19 with base 38 (if u have wifi on the wii, u dont need to DL IOS38 before hand, u can just install the cIOS using NUS installation, as it will download IOS38v3867 on the fly from ninty servers). Then test if the cIOS249 works normally with apps like USB Loaders, Wad Managers, etc.

 

[XFlak]

Okay, good news! Below is a PM DARK Leader D sent me (I don't think he'll mind if I share his analysis, he's a cool guy

)which should clear up a few things, so I think we only need to test 1 thing now... test using the new IOS38v3687 as a base IOS for cIOS249rev19 works as it should.

Ok, I haven't actually tested any cIOS installations, but I have analyzed a IOS38 v3867 I just downloaded, and compared it's ticket to one I downloaded a while ago before the 4.3 update.

The results aren't really that interesting at all.

All that has happened is when the cetk is grabbed, the latest version is grabbed (don't know if older versions are stored on NUS like older tmds are. Maybe they could be?).

So all that is happening is that the ticket for the latest version is being used, nothing more.

The only things that have changed are the revision number of the IOS (as of sysmenu 3.3+, system titles have had their revision numbers in the tickets too), and of course the signature at the start of the ticket. That's it.

So this should not impact on anything, and everything should just work fine as it does now.

Hope that clears that up for you,
damysteryman
DARK Leader D

Thanks damysteryman!!!!

 

[Messiahlad]

mmm now Im wondering if it I could proceed with my mod.

currently:
pal wii with 3.2e installed and damysteryman's 3.6 cioscorp. I also use usb GX with my hard drive "custom- fan cooled 2.5 hd built into the base"

was hoping to use NUSAD to upgrade to 4.2e and install DARKCORP for discloader channel support and continue using usb GX.

So is it possible that all the files I have obtained are "safe" and I could continue with the mod.

-ps A friend of mine has a release day wii but i cant pry it from his grip.

 

[XFlak]

I suspect all the files grabbed from NUSAD are safe to install except for maybe the cIOSs. But installing a bad cIOS will NEVER result in brick (as 200+ IOSs are not used in normal wii functions, a bad cIOS could never brick anyone).

I hope to release v4.1.5 in 2-3 weeks with new features as well as have all this changed IOS business sorted out

 

[Messiahlad]

thanks for the reply. I might just install 4.2e without out stubs and and use my known cIOS collection to test it out. Then again it might be in my interests to wait until your next version comes out as bootmii is only installed as IOS and preloader is my failsafe. (psuedo old mod). Im gonna try to convince my friend to part with his old wii which i installed bootmii on it as boot2. If i can i'll start testing some of these new changes.

thanks again mate

 

[nerezza]

Alcohol!

That is all. Oh, plus I still can't get the fu**ing thing working

Oh well... Alcohol!

 

[Messiahlad]

Alcohol!

That is all. Oh, plus I still can't get the fu**ing thing working

Oh well... Alcohol!

I assume your on xp? One of my xp installs was doing this until I did the basic windows updates. My laptop I use to do the wii mods is xp with sp3 and .net on 3.5. Haven't gotten windows errors on it.
Might help? Can only try eh. Crack a longy try again

 

[rafao]

The NUSAD 4.1.5 will be configurable for Wii 4.3?
I am recent buy a wii and accidentally updated this.


Detail: My Wii is virgin.

 

[XFlak]

v4.1.5 will likely not support v4.3, but once 4.3 wii's can be hacked (hopefully soon), I will put out another update ASAP (v4.1.6)

 

[rafao]

Thanks, for answer XFlak, waiting ....

Good work.

 

[cheez203]

Amazing!

 

[Zeer]

I'm getting the same errors as nerezza. The program is crashing a lot with a .net error message appearing. When it does succeed, at the end it reports i have errors; my last try gave 34 errors. I'm not sure if it's safe to use these files or not. I was following TCSM guide and it instructed me to use this program...

Hi, I'm having issues with NUSAD. I've followed all the instructions but I keep getting a Microsoft.NET Framework errors while downloading NUS Downloader Command Line v0.2 by wiiNinja. It gets up to 'Grabbing 00000017...' and then I get the error (full details below).

I am able to proceed after this but then at the end of the download process there are errors, I believe signifying that several files are missing.
NUSAD instructs me to delete all files with an MD5 mismatch error, unfortunately I am new to this and I have no idea how to tell which ones they are (or where to locate them).

I would like to get this working as my primary goal is to be able to download, burn and play Wii games (too poor to afford to buy legit versions). Any help would be greatly appreciated.

 

[XFlak]

did u follow pepxl's suggestion to nerezza and perform a windows update to install .NET framework 3.5?

 

[XFlak]

Here's an update on my "Wiisearch" of the older IOSs that were changed
-only the tik and the cert files have changed (this I already noted in my prior posts)
-they operate exactly the same as they did before the change when installed on the wii
-they also operate exactly the same as they did before when used as a base wad for cIOS installations
*specifically I tested using the changed-older IOSs to install and run the HBC (using IOS34 and IOS61), install a fakesigned IOS36, and install many different cIOSs (using many different older-changed IOSs as base wads)

so what changes will need to be made to NUSAD?
... not much really (only 2 things), just update the md5 hash database (I pretty much finished this already), and I'm going to have to create new diff files to patch the changed-older base wads to properly create cIOSs in wad form (this could take some time... but its not a problem)

In Summation, v4.1.5 will fix all the errors people have been getting (plus have a few new features/downloads), but it will not support hacking virgin 4.3 Wii's (as a solution has not YET been released, but when one has been released, I'll start working on adding it into NUSAD)