Hacking Wii Iso Scrubbing & Other Inquiries

[XofDiAcme]

What is the most recent version of the Wii Scrubbing Tool?

I have a Korean Iso that cannot be processed by Wii Backup Manager. I have the Korean common key from ModMii. As far as I understand USBLoaderGX should work completely fine with .iso files. However, I am interested in saving hard drive space.

Can the Wii Scrubbing Tool also reverse the process back to an untouched Iso as well?

---------------------------------------------------------------------------------------------------------------------------------------------------------------
What is the most recent version of DMToolBox for Gamecube Iso? Is this process also reversal?
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Is there any thread that discusses the compatibility of Vitrual Console injections for the Wii (not Wii U)? What are the lastest version of those tools? When testing the wads is running them on Dolphin sufficient?
---------------------------------------------------------------------------------------------------------------------------------------------------------------
The last question I have is regarding WiiWare wads. Suppose I dump the nand from my Wii console 4.3U. And then I add wads to my EmuNand with ShowMyWads. What would happen if one these wads is corrupt per say? Would I brick my Wii console? Or can I simply delete the wad without any major problems from the file on my SD card and start all over? Is there any known issues with using an SDXC class SD card formatted in FAT32 with the Wii (I am interested in 64GB Card)?

 

[FancyNintendoGamer567]

@XofDiAcme In WiiBackUpManager, in Files select your Korean ISO, then select it in WBM, then hit "Transfer" then WBFS. Then when it's done, transfer the WBFS to Drive 1 or 2 (depending on which slot has your USB drive selected).

 

[XofDiAcme]

Yeah, WBM does not work with KOR Iso. It is an known issue, because KOR Wii's have a different master key.

 

[GreyWolf]

Try Wiimm's ISO Tools.

 

[XofDiAcme]

Wiimm's Iso Tools is command only. I would rather have a program do it. I trust the developers more than my typing skills.

Apparently, Wii Scrubbing Tool is the best way to go about this situation. It already has the master key in its repository.
However, I am skeptical whether it is up-to-date. It is in v1.4 and has not been updated since 06/06/2010.

I will test this out for now.

 

[GreyWolf]

There are GUI front-ends for WIT, too. It's really not difficult to use, though.

 

[XofDiAcme]

Apparently, my KOR Iso is a bad dump. Maybe that is the reason why WiiBackupManager crashed.

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

And Wii Scrubber only compresses the Iso into another Iso. I looking forward to convert the original 4.5GB Iso into a wbfs. Is a wbfs just a compressed Iso with a different filename? Is that why USBLoaderGX can read Isos.

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

Nevermind. I just tested it out wbfs is not the same as a scrubbed iso. They are not even the same combined file size.

 

[GreyWolf]

WBFS is a sparse format. The data that is normally scrubbed out is unused so WBFS doesn't store it. It only keeps track of where the data was on the original disc.

 

[XofDiAcme]

Could somebody help answer the other inquires?
Q1 has been answered. Thank you, GreyWolf.

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

WBFS is a sparse format. The data that is normally scrubbed out is unused so WBFS doesn't store it. It only keeps track of where the data was on the original disc.

Interesting, but then why does wbfs result in even lower file size than a compressed iso.

Iso 4.5GB
Compressed Iso 4.2GB
Wbfs 4GB + 0.12GB = 4.12GB

(Hypo. Example)

 

[GreyWolf]

Could somebody help answer the other inquires?
Q1 has been answered. Thank you, GreyWolf.

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



Interesting, but then why does wbfs result in even lower file size than a compressed iso.

Iso 4.5GB
Compressed Iso 4.2GB
Wbfs 4GB + 0.12GB = 4.12GB

(Hypo. Example)

Dunno. May CISO removes more data? Gamecube and Wii discs have two sections: one that the console has access to and one the game does. The system area shouldn't ever be altered but maybe CISO makes it sparse it as well.

 

[XofDiAcme]

Dunno. May CISO removes more data? Gamecube and Wii discs have two sections: one that the console has access to and one the game does. The system area shouldn't ever be altered but maybe CISO makes it sparse it as well.

Yeah, its weird ain't.

Does anybody know what is the most recent version of Wii Virtual Console injectors for the original Wii (Not Wii U). And if GBATemp has a compatibility list for this. I could only find one for the Wii U. Main reason is that I do not want mess with the settings for Wii64 and VBAgx for each game. I much rather have the games as channels for sake of simplicity.

 

[XofDiAcme]

Yeah, its weird ain't.

Does anybody know what is the most recent version of Wii Virtual Console injectors for the original Wii (Not Wii U). And if GBATemp has a compatibility list for this. I could only find one for the Wii U. Main reason is that I do not want mess with the settings for Wii64 and VBAgx for each game. I much rather have the games as channels for sake of simplicity.

Also how do I change the options in USBLoaderGX to view the Game Disk Art instead of Channel when I am in the WiiFlow-like visualizer. Thanks.

 

[Cyan]

I suppose ciso only removes dummy sectors, not the update partition.
wbfs keeps only the game partition (deleting the update partition).

how do I change the options in USBLoaderGX to view the Game Disk Art instead of Channel

I suppose you don't talk about the disc's box (at the top, you swap the loader's style from list/grid/carousel/banner), but instead talk about seeing the rotating disc cover ?
Settings > GUI > Game windows > Rotating disc, instead of banner. I added a 3rd option "banner on banner mode", it keeps the animated banner if you are on banner layout, but use rotating disc on 3 other layouts.

What is the most recent version of DMToolBox for Gamecube Iso? Is this process also reversal?

Why use that tool ? compressed gamecube ISO are not always working. 1.3GB iso are often better.
of course, compressed iso works most of the time, but don't use any of the aligment option, just pick "raw" to just rename the folder/iso file to the one used by the loader.
you can use another tool if you only want proper filename : WiiBackupManager's author made a beta version (which was planed to integrate to WBM, but the author disappeared from the net)
http://www.wiibackupmanager.co.uk/gcit.html

Or maybe Greywolf's gc tool ? usually in his signature, but it's not there anymore.

Again, Wit is prefered.
if you want a GUI to Wit : https://wiimm.de/r/wiibafu

an the Wii Scrubbing Tool also reverse the process back to an untouched Iso as well?

yes, there are 2 tools doing it. only for wii games, no idea if it works with scrubbed gamecube games.

the full iso is useless, but it's possible to get it back for whatever reason, as long as you kept the update partition it can be restored 1:1.
there is a VERY old tool to inject update partitions into iso, but you need binary dumps of the updates partitions to restore. WUM (Wii Update Manager)

newest tool : https://gbatemp.net/threads/new-wii-unscrubber-swiit.511181/
can also restore update partitions, if you provide them. (no idea if it's using the same format than WUM, if that's the case it would be great as some people kept a lot of these dumps, though forbidden to share here)

I add wads to my EmuNand with ShowMyWads. What would happen if one these wads is corrupt per say? Would I brick my Wii console?

nothing, as you do it on your emuNAND, it can't affect your console because you didn't add them to your console.
if emuNAND doesn't work anymore, make a new dump.
if only one game doesn't work on emuNAND, there are lot of reasons, either the wad is bad, either you don't use proper settings, or you need neek emuNAND mode.

SDXC class SD card formatted in FAT32 with the Wii (I am interested in 64GB Card)?

I don't know if SDXC are working. keep using SDHC.

 

[FancyNintendoGamer567]

The last question I have is regarding WiiWare wads. Suppose I dump the nand from my Wii console 4.3U. And then I add wads to my EmuNand with ShowMyWads.

Dude, don't use SMW/N. I had to make someone suffer because SMN trucha signs IOSes, and that HBC doesn't like trucha signed IOS 58.

 

[Cyan]

no, that's fine !
the way he plan on using it is fine.

He wants to manage his emuNAND dump, not extract content from it to reinstall on his console. (at least, that's what I understood)
Just don't reinstall system files (IOS) extracted from that program
but games are fine. reinstalling Wiiware/VC is possible, but not safe (if the banner is bad, etc.) but having the fakesigned ticket/tmd is fine to launch such channels as long as you patched your corresponding system menu's IOS, or use a USB Loader to launch them.


the best solution is still to not install WADs to console's memory, and just use the emuNAND (manage it like you want, with this tool or not) and launch the games from it using backup loaders or neek.

 

[XofDiAcme]

I added a 3rd option "banner on banner mode", it keeps the animated banner if you are on banner layout, but use rotating disc on 3 other layouts.

How convenient this was exactly what I was looking for! I will give this a go. If it does not work I let you know.

...either you don't use proper settings, or you need neek emuNAND mode.

What the difference between Neek EmuNand and ShowMiiMyWads method. Which one would you recommend personally?
Thank you all your help.

 

[Cyan]

showMiiWad is just a tool to manage the files and games installed to your NAND copy.
you can use USBLoaderGX's wad manager to do the same (USBGX > settings > Features > Wad manager), you'll need the wad on SD to install/uninstall to your emuNAND.

the two method I talked about is the way to launch the games on your console directly from that NAND copy (called emuNAND).
There is a cIOS method : the console uses cIOS to redirects access from NAND to your emuNAND path in reatime. 80% of games are working that way. You should privilege this method first.
there is a neek method : the console is entirely redirected (not only the game when wanting to access the NAND). All the console is loaded from the NAND copy as if it was the full internal chipset. The advantage is that even the unpatched IOS are redirected, and games uses these unpatched version to load the game, with better compatibility (99%)

https://gbatemp.net/posts/6592730

 

[XofDiAcme]

I suppose ciso only removes dummy sectors, not the update partition.
wbfs keeps only the game partition (deleting the update partition).

Again, Wit is prefered.
if you want a GUI to Wit : https://wiimm.de/r/wiibafu

What exactly is this update partition on a technical level that you speak of? What function does it serve?
=
Wait, so Wit also scrub Gamecube isos. Interesting, I personally prefer the un-compressed 1.35GB iso
for personal usage, I was mainly asking this for preservation purposes. Scrubbed isos tend to be much
smaller in size than the actual iso when compressed by OpenArc or 7Zip. If this process where to be
reversal, this would be ideal to save bandwidth and disk space. And I agree, iso should NOT be post in this
site.

Do you happen know anything about the Wii Virtual Console injectors from the past? Was compatibility list
ever made for the Wii. I would prefer a Channel that is ready from the get-go than I manually configuring
an emulator for each game.

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

showMiiWad is just a tool to manage the files and games installed to your NAND copy.
you can use USBLoaderGX's wad manager to do the same (USBGX > settings > Features > Wad manager), you'll need the wad on SD to install/uninstall to your emuNAND.

the two method I talked about is the way to launch the games on your console directly from that NAND copy (called emuNAND).
There is a cIOS method : the console uses cIOS to redirects access from NAND to your emuNAND path in reatime. 80% of games are working that way. You should privilege this method first.
there is a neek method : the console is entirely redirected (not only the game when wanting to access the NAND). All the console is loaded from the NAND copy as if it was the full internal chipset. The advantage is that even the unpatched IOS are redirected, and games uses these unpatched version to load the game, with better compatibility (99%)

https://gbatemp.net/posts/6592730

Ha. So maybe I should just start off with Neek first, because it has a higher compatibility rate. emuNAND is in the SD
card right, no way to put that to a hard drive for more space?

 

[Cyan]

neek is harder to setup, and more heavy (requires console restart when using it, homebrew are not working)
but up to you, based on how you use it. when launching neek, as the console reboots entirely into a "redirected" NAND, it acts as if it was a real Wii, you see the System menu, you launch games as if it wasn't hacked.

if you like launching games from usb loader, I recommend cIOS mode for working games, and neek only for non working ones.
if you prefer launching games from system menu, you can use neek, but the system menu is limited to 48 channels. You can install more games at the same time, there's a hidden menu which lists all installed channels.

you can of course set emuNAND path to USB. but if the partition is bigger than 2TB, some games can have issues. some games check how much space is left on the Wii (512MB usually, so 32bit is enough to check size) and partition bigger than 2TB are reported as negative value in 32bit, games would need 64bit to get proper size for big partition, so some games will tell that you don't don't have enough free space to create the savegame file, while you have too many.

I still recommend cIOS mode, easy to setup and launch in usbgx.

 

[Wiimm]

More info about scrubbing: https://wit.wiimm.de/info/scrubbing.html