Hacking QUICK/NEWBIE QUESTIONS here!

  • Thread starter Thread starter OSW
  • Start date Start date
  • Views Views 608,355
  • Replies Replies 4,024
  • Likes Likes 7
Thank you very much.
There are still things I'm trying to figure out.

For example, I didn't fully understand why cIOS are installed.
From the information I've read, there's no downside to installing cIOSs, but I haven't yet understood the purpose of the installation.
On the one hand, as I understand it, they are operating systems that "frees" the Wii, allowing additional uses such as USB access.
On the other hand, I've read in other places that installing cIOSs is no longer necessary because HW_AHBPROT (what is it?) is a better and less "intrusive" approach and should be part of the HomeBrwe.
This got me confused.

In addition, I've seen many recommendations for the Open Shop Channel (at - scwii/org [sorry. can't post links, newbie limitations]). In all the different explanations I've been exposed to, the installation is done directly to the SD card and not to an external hard drive.
I've come to terms with the fact that a SD card will be needed on the device permanently. I even found an old 32GB MicroSD card. How reliable is it? I don't know.
Of course, I'll make a NAND backup and keep it on two different computers (I understood that the backup files will be nand.bin and keys.bin - is that so?).
But, what happens if the MicroSD card in the Wii stops working? How will this affect the use of the console? Obviously, everything installed/saved on the card will not be accessible, but will the device itself continue to work? Will inserting another card and transferring files to it be essentially "as if nothing happened"?
 
Unfortunately, the 32GB MicroSD card that I found is faulty and unusable. Back to wondering if I should purchase a NEW card or use the old 4 / 8 GB card without keeping it in the console.
How will it affect the Open Shop Channel downloads etc.
 
How can I extract the Save Icon from a .bin file?
Like I know how I can get the banner in Dolphin but for the life of me I can't figure out how to get the Save Icon (I already booted the game and saved)
 
From the information I've read, there's no downside to installing cIOSs
Yup, at any time only 1 application title is running on the CPU and 1 IOS on the coprocessor, with very few exceptions (eg the Wii Menu loading and insisting on rendering the banner of any directly user-accessible title) all others are not merely unused but completely ignored

For example, I didn't fully understand why cIOS are installed.
On the one hand, as I understand it, they are operating systems that "frees" the Wii, allowing additional uses such as USB access.
On the other hand, I've read in other places that installing cIOSs is no longer necessary because HW_AHBPROT (what is it?) is a better and less "intrusive" approach and should be part of the HomeBrwe.
This got me confused.
First we have to define "CIOS", literally it means "Custom IOS" so at face value any IOS that is not 100% original and signed is a CIOS (eg re-enabling trucha and/or RiiConnect24 patches), but it's common to reserve the term for "major" mods that include things like software optical drive emulation (the basis of USB loaders), automatic support for copied DVDs, gamecube to wiimote simulation, etc;

Since you mentioned "USB access", all IOSes already support USB because it's used for Bluetooth and therefore Wiimotes; USB2 support did in fact originate in a CIOS (conventionally installed in "slot" 202) but since it became part of official IOS58 & 59, CIOS202 largely became irrelevant to homebrews that don't need those "heavy" features, as you can see by your HBC almost certainly being built to use IOS58...

AHBPROT means a title can freely read and write any memory, which theoretically would indeed mean there's no point in installing pre-modding IOSes as they could do the same on the fly to the in-memory copy of the already running IOS; and this is the case for "light" mods (like modern title installers/uninstallers that traditionally needed a trucha-enabled IOS to accept fakesigned titles), but alas:
  • AHBPROT is a relatively recent development, at least for a funny redefinition of "recent" relative to the Wii being a mainstream console - it was discovered in mid 2009 https://hackmii.com/2009/08/of-tmds-and-hardware/ but it pretty much meant nothing for well over a year, I don't recall said "modern" title managers being popular before 2012 or so and many people in 2010 were still interested in DVDX (a previous homebrew solution for reading movie/data DVDs which basically used a lesser AHBPROT limited to the optical drive)
  • Corollary - it is useless for most older system tool homebrews (depending on vintage it might switch to CIOS249 expecting it to have trucha, if older it might want it on 36 or 35, in any of these cases the active IOS is reloaded so the effects of AHBPROT cease anyway)
  • Those "heavy" mods are invasive and have to be customized for every "base" of the CIOS, which also explains why there's a limited choice of them (compare to enabling trucha, which AFAIK is literally one of two search-and-replace jobs out of all official IOSes)

In all the different explanations I've been exposed to, the installation is done directly to the SD card and not to an external hard drive.
Yes, most homebrew is "installed" to [FAT16 or 32] [SD or USB] - which are generally freely interchangeable, as opposed to internal storage which is accessed rather differently + of limited capacity + very inconvenient to directly manage for the user + ...
So while it's possible to package homebrews into titles (channels), as very easily proven by the HBC's existence, it is uncommon to do that in favor of forwarders (homebrew whose only real purpose is to run another... almost invariably from said sources)

I've come to terms with the fact that a SD card will be needed on the device permanently. I even found an old 32GB MicroSD card. How reliable is it? I don't know.
Of course, I'll make a NAND backup and keep it on two different computers (I understood that the backup files will be nand.bin and keys.bin - is that so?).
But, what happens if the MicroSD card in the Wii stops working? How will this affect the use of the console? Obviously, everything installed/saved on the card will not be accessible, but will the device itself continue to work? Will inserting another card and transferring files to it be essentially "as if nothing happened"?
Obviously it depends on what you do with it (after all the point of modding consoles is that you're dissatisfied with how the manufacturer is trying to unilaterally forcing you to use it), but a stock Wii never requires an SD card, and installing a few custom channels or even BootMii as boot2 and/or Priiloader doesn't change that - the console will still work "like original or better" without add-on storage;
of course you won't have access to any stuff that was on SD/USB but you can very easily replace them (I won't say it's useless to backup your SD/USB, but honestly the original downloads of most homebrews are more "valuable" than their files as "installed" on your external storage - so yes, the answer to your last questions is Yes)

Of course, I'll make a NAND backup and keep it on two different computers (I understood that the backup files will be nand.bin and keys.bin - is that so?).
Yup, but again - yes, having a backup is always better than not having it, but you'll use it more often to extract it for Dolphin/emunands/etc than to restore it (if you can have Bootmii as boot2 fair enough, but if you can only have it a IOS254, know that to restore a backup "in emergency" you'll need the following things, all working: boot1, boot2, Wii Menu IOS, Wii Menu with Priiloader, BootMii's IOS254, a GC controller and a working GC socket 1 just in case you have an horizontal or mini model; but if you have the first four, you can run other homebrew to actually fix the direct problem
Unfortunately, the 32GB MicroSD card that I found is faulty and unusable. Back to wondering if I should purchase a NEW card or use the old 4 / 8 GB card without keeping it in the console.
How will it affect the Open Shop Channel downloads etc.
As said, most homebrew (including that "app store") only saves to SD/USB
Depending on the vintage of titles (homebrew and commercial) that you're going to use, it may be smart to grab a SDSC card (2 GB or less)
 
  • Like
Reactions: SimpleUser1
Hey guys I am having some trouble with Wii flow. My wii games are recognized but send me straight to the Wii home menu when booted. Can someone take a look at my syscheck and point me in the right direction? Thanks.

Some things to note:
-I am using a Samsung t7 SSD plugged into slot 0, it is formatted with ISFSHax USB partition plugin.
-My gamecube games dumps boot and work perfectly fine, no problems.
-I uninstalled and reinstalled all my cIOS to rule that out.
-Ive used wiiflow start configurator and set it to force 248,249,250,251. None get wii games to boot
 

Attachments

  • wbfs folder.png
    wbfs folder.png
    59.4 KB · Views: 42
  • SysCheck.rar
    SysCheck.rar
    687 bytes · Views: 26
@Ryccardo - THANK YOU. I have no words on your detailed responce.
I did not understand half of it and I am aware there is so much more to learn in the "wii world". As I wrote not long ago, up until a week or two I have never ever used a gaming console of any kind.

You mentioned Dolphin and I came across of that emulator name. If memory serves, it is used for GameCube files (I think I read it is an emulator for PC but based on what you wrote it seems to be for wii).

As of now, the main goal is to softmod the wii device and transfer the CDs to a hard drive. Maybe later down the lane also using the Open Shop Channel and even purchasing other CDs and down the wii rabbit hole, time will tell.
As the console is not mine and it will be returned next week to it's owner, at this point I would like to keep it as simple as possible.

I downloaded the ModMii portable version and started the wizard.
In all the tutorials I read and the few YouTube guides watched - they ALL mentioned to write down the MAC address as it will be needed for the process of the LetterBomb exploit. Furthermore, the LetterBomb website writes that the MAC address is "Necessary to create and sign the correct file".
B-U-T, when I went trough the ModMii wizard - at no point - I was asked to enter the MAC address, I added a screenshot of the wizard summery.
Why was I not asked for the MAC address? (might be because the current version is 3.4E?)
Is this normal? Should I go ahead with the files the ModMii generated and softmod the console?

Screenshot:
MiiMod.jpg
 
Yes that's normal because you're not on 4.3, modmii will have u use a different exploit that accomplishes the same thing but doesn't require Mac address information from you
Thank you!

I have just finished reading carefully the extremely helpful guide generated by ModMii (WOW!!!!).
The guide indicated that the exploit used is Bannerbomb v1 (first time I've encountered this exploit) and the way to run the exploit seems to be different. Where in order to run LetterBomb one needs to go the message board, in order to run Bannerbomb v1 one needs to go into the options menu, choose data management etc.

I must say, I am confused.
My understanding is that one of the steps in the guide generated by ModMii will also update the wii menu from 3.4 to 4.3.
I also understood that one should be careful, even avoid, updating a modded wii system.
In this case, on the one hand, the exploit (Bannerbomb v1) is used for older systems (if I understood correctly, for 3.x-4.1 systems), so, logic says that the order of ModMii guide is first to use the exploit and after that, somehow, the system will be updated to 4.3. I have full confidence that there will not be an issue with the system update, but I am confused.

On the tutorials I saw, there always were 44 WADs installed.
But, in this specific case, ModMii generated 45 WADs.
Is the extra WAD the system update from 3.4 to 4.3? [WAD #44 is named: "SystemMenu_4.3E_v514"]
 
Correct. Video guides will often forget to mention that the wads listed in ModMii guides are unique to your situation, so the number of wads as well as which specific ones will differ from whatever video you saw.

ModMii is my baby, I'm glad to hear you're finding it helpful :)
 
I also understood that one should be careful, even avoid, updating a modded wii system.
As a general advice this is true - "modded things" may interact badly with "new official things" or viceversa, so it would be smart to research and understand the changes and all of their implications before updating a modded console (or, really, any other tech product)

But the Wii had its last model launched in 2012 (and well understood by the turn of 2020),
and its latest update in 2014 (but that was a minor fix for an IOS used only by one (1) Japanese game; the last "significant" change, and even that is an embarrassingly generous term, was in 2010),
and the interactions between software components are well understood (I went out of my way to mention the 1 title + 1 IOS system immediately, because it has many more or less obvious implications)
→ so if your "mods" are sufficiently recent, they won't be bothered by "recent" updates;

besides, there are (multiple!) exploits available even on a fully updated system,
→ so even if you hypothetically failed on the previous point and updating removed the HBC, CIOSes, etc (or, of course, a human removed them for whatever reason) it's very possible to get them back :)

In this case, on the one hand, the exploit (Bannerbomb v1) is used for older systems (if I understood correctly, for 3.x-4.1 systems), so, logic says that the order of ModMii guide is first to use the exploit and after that, somehow, the system will be updated to 4.3. I have full confidence that there will not be an issue with the system update, but I am confused.
While a very necessary first step, ironically these entrypoint exploits do very little of the job - loading some homebrew from somewhere, but once that happens they cease to affect the system...

(The above is simplified and therefore a little misleading, but in the Wii/PS2 architecture you can get away for a surprisingly long time and depth - I assume you won't be trying to develop a competitor to the Hackmii Installer - with this understanding :) )

...so the fact you used Bannerbomb 1 instead of whatever of the other 10+ exploits is irrelevant to installing Wii Menu 4.3 (even if Bannerbomb 1 happens to be incompatible with Wii Menu 4.3), but it would have been irrelevant as soon as you saw the HBC on screen the first time!

Yup, this is again the title-and-IOS model: at first you had Wii Menu 3.4 and IOS50, the exploit turned that* into the Hackmii Installer and IOS50, and when you backed out of it at the end the console was running the HBC and presumably IOS58

* all the wiimote power cycles when you run something are because the title and/or the IOS are changing!
 
  • Like
Reactions: SimpleUser1
As a general advice this is true - "modded things" may interact badly with "new official things" or viceversa, so it would be smart to research and understand the changes and all of their implications before updating a modded console (or, really, any other tech product)

But the Wii had its last model launched in 2012 (and well understood by the turn of 2020),
and its latest update in 2014 (but that was a minor fix for an IOS used only by one (1) Japanese game; the last "significant" change, and even that is an embarrassingly generous term, was in 2010),
and the interactions between software components are well understood (I went out of my way to mention the 1 title + 1 IOS system immediately, because it has many more or less obvious implications)
→ so if your "mods" are sufficiently recent, they won't be bothered by "recent" updates;

besides, there are (multiple!) exploits available even on a fully updated system,
→ so even if you hypothetically failed on the previous point and updating removed the HBC, CIOSes, etc (or, of course, a human removed them for whatever reason) it's very possible to get them back :)


While a very necessary first step, ironically these entrypoint exploits do very little of the job - loading some homebrew from somewhere, but once that happens they cease to affect the system...

(The above is simplified and therefore a little misleading, but in the Wii/PS2 architecture you can get away for a surprisingly long time and depth - I assume you won't be trying to develop a competitor to the Hackmii Installer - with this understanding :) )

...so the fact you used Bannerbomb 1 instead of whatever of the other 10+ exploits is irrelevant to installing Wii Menu 4.3 (even if Bannerbomb 1 happens to be incompatible with Wii Menu 4.3), but it would have been irrelevant as soon as you saw the HBC on screen the first time!

Yup, this is again the title-and-IOS model: at first you had Wii Menu 3.4 and IOS50, the exploit turned that* into the Hackmii Installer and IOS50, and when you backed out of it at the end the console was running the HBC and presumably IOS58

* all the wiimote power cycles when you run something are because the title and/or the IOS are changing!
Don't forget that poorly region changed wii's that were originally Korean can 003 brick from official updates. Updating using modmii is however safe no matter the Wii's history
 
  • Like
Reactions: jeannotte
Thank you both for your in-depth insights.

I finally came around to go ahead with the softmodding. I have the time and with the research done the past few weeks made me feel comfortable enough. I am aware that I don't fully understand all the ins and outs.

Anyway, unfortunately, I came into a dead end. I have 2 different MicroSD cards and both failed to load on the wii.
Both were formatted to FAT32 and I tried several cluster sizes 4, 16 and 32KB.
One MicroSD card is a 64GB Samsung EVO.
The other is a 8GB Silicone Power (SP).

I tried 2 different SD adapters (from Micro to full size SD).

The cards are read perfectly on the laptop. I tried a USB to MicroSD adapter and the laptop's built-in SD card reader.

When I connect the card to the wii, nothing "pops up" on the main screen. My understanding is that I should see a SD icon on the bottom left side of the screen, but nothing apears.

The guide that was generated by MiiMod suggested using Bannerbomb v1.
As instructed, I browsed to: Wii Options, Data Management, Channels, SD Card.
On the screen there was a notice: The device inserted in the SD Card Slot can't be used.

I wonder what would you suggest from this point.
The wii is - RVL-001 (EUR) the was never modded, probably never connected to the internet.
Current version is: 3.4E.

Should I connect it the the internet, have the system update to 4.3E and try again the MiiMod with the new parameters?
Should I try and look around for a full size SD card and try with it? If so, what is the recommended minimal capacity?
Any other ideas / suggestions?

Thank you
 
Anyway, unfortunately, I came into a dead end. I have 2 different MicroSD cards and both failed to load on the wii.
One MicroSD card is a 64GB Samsung EVO.
The other is a 8GB Silicone Power (SP).
So, two SDHCs - support for which debuted* in 4.0 :( :)

* for the Wii Menu only - each and every title has its own SD and Wiimote drivers, so even on a fully updated console you won't get SDHC support in Brawl, etc

When I connect the card to the wii, nothing "pops up" on the main screen. My understanding is that I should see a SD icon on the bottom left side of the screen, but nothing apears.
That icon was also added in 4.0 (and is always visible, it just turns from gray to blue when a card is inserted)

Should I try and look around for a full size SD card and try with it? If so, what is the recommended minimal capacity?
It's not the adapter (this time - they do suck otherwise for reliability reasons)

You would need an SDSC (maximum 2 GB), or a different exploit (if it even exists, no idea if str2hax works on 3.4, bluebomb as currently implemented doesn't, and most everything else will also require SDSC), or just to update and try again if you don't believe it was a poorly region changed Korean model
 
  • Like
Reactions: SimpleUser1
I think you need to update to use SDHC and SDXC cards you can use modmii to update your wii.
Thanks!
I've checked the changelog history of the wii system menu on nintendo's website (link).
The first update in the Wii menu 4.0 is:
  • The Wii console can now use SDHC (SD High Capacity) Cards with a maximum of 32GB of storage. Games and channels which read from or save to SD Cards will continue to support only SD Cards.
So, it surly seems that in order to use SDHC one needs to update the wii.
I've seen on reddit reports that wii owners use 256 GB or even 516 GB with their wii, but the changelog has nothing regarding supporting SDXC.

Thank you for your suggestion, but, I am not sure how I can use ModMii to update the console if I don't have a SD/MicroSD card that will be read by the wii.

Anyway, if I find a 2GB card, will that be sufficient to go ahead?
Afterwards, so I just copy the files from the 2GB card and transfer them to the 64GB card? The 64GB card will be the "wii card" from now until it fails...
 
Anyway, if I find a 2GB card, will that be sufficient to go ahead?
Afterwards, so I just copy the files from the 2GB card and transfer them to the 64GB card? The 64GB card will be the "wii card" from now until it fails...
Sure, a NAND backup at little more than 512 MB will be by very far the largest thing you'll deal with in the process, until you start dealing with game backups :)
And yes, you can freely transfer files between cards

I've seen on reddit reports that wii owners use 256 GB or even 516 GB with their wii, but the changelog has nothing regarding supporting SDXC.
The Wii, DSi, 3DS, WiiU don't support SDXC, but that requires understanding what a SDXC is:

According to the official SD Association standards, you can have:
  • A first generation SDSC, up to 1 GB, that must be partitioned with MBR and have a single FAT16 partition
  • A second generation SDSC, up to 2 GB, that must be partitioned with MBR and have a single FAT16 partition
  • A SDHC, up to 32 GB, that must be partitioned with MBR and have a single FAT32 partition
  • A SDXC, up to 2048 GB, that must be partitioned with MBR and have a single EXFAT partition
  • A SDUC, up to 128 TB, that must be partitioned with GPT (I think) and have a single EXFAT partition

Those consoles don't support EXFAT (which is both somewhat different than the others, and patented in the 2 countries in the world that accept software patents, which happen to be exactly the ones where Nintendo of America and Nintendo Co. Ltd. are), but since the protocol is the same between SDHC and SDXC, if you reformat the card and end up with the following nonstandard thing:
  • A card with SDXC written on the sticker, up to 2048 GB, partitioned with MBR and a FAT32 partition
it will work in most SDHC-compatible gear :)
 
Thank you both for your in-depth insights.

I finally came around to go ahead with the softmodding. I have the time and with the research done the past few weeks made me feel comfortable enough. I am aware that I don't fully understand all the ins and outs.

Anyway, unfortunately, I came into a dead end. I have 2 different MicroSD cards and both failed to load on the wii.
Both were formatted to FAT32 and I tried several cluster sizes 4, 16 and 32KB.
One MicroSD card is a 64GB Samsung EVO.
The other is a 8GB Silicone Power (SP).

I tried 2 different SD adapters (from Micro to full size SD).

The cards are read perfectly on the laptop. I tried a USB to MicroSD adapter and the laptop's built-in SD card reader.

When I connect the card to the wii, nothing "pops up" on the main screen. My understanding is that I should see a SD icon on the bottom left side of the screen, but nothing apears.

The guide that was generated by MiiMod suggested using Bannerbomb v1.
As instructed, I browsed to: Wii Options, Data Management, Channels, SD Card.
On the screen there was a notice: The device inserted in the SD Card Slot can't be used.

I wonder what would you suggest from this point.
The wii is - RVL-001 (EUR) the was never modded, probably never connected to the internet.
Current version is: 3.4E.

Should I connect it the the internet, have the system update to 4.3E and try again the MiiMod with the new parameters?
Should I try and look around for a full size SD card and try with it? If so, what is the recommended minimal capacity?
Any other ideas / suggestions?

Thank you
If you're instructed to use bannerbomb v1 it's because you're on an older system menu version. The sd icon on the main menu is not found on some old system menus. So if you follow your modmii guide, it will show you how to launch bannerbomb v1 via the wii options / data management menu

Edit: also u can fully softmod the wii except for bootmii without an SD card
 
Sure, a NAND backup at little more than 512 MB will be by very far the largest thing you'll deal with in the process, until you start dealing with game backups :)
And yes, you can freely transfer files between cards
Excellent!
I looked around for a 1 or 2GB card, hopefully I'll borrow one from a neighbor and once system will be updated to 4.3E, I'll use the 64GB one.

So if you follow your modmii guide, it will show you how to launch bannerbomb v1 via the wii options / data management menu
Thank you!
In one of previous message I wrote

The guide that was generated by MiiMod suggested using Bannerbomb v1.
As instructed, I browsed to: Wii Options, Data Management, Channels, SD Card.
On the screen there was a notice: The device inserted in the SD Card Slot can't be used.

Anyway, one of my neighbors thinks he has a 2GB SD/MicroSD card from an old digital camera. I will borrow it in a couple of hours and will let you know if that did the trick.
 
  • Like
Reactions: XFlak
If you have internet on your wii you can use str2hax instead of bannerbomb. After having done so, the hbc should be able to read your larger card, u can softmod/upgrade to a newer system menu which will then also hopefully be able to read your larger capacity sd card should u need that functionality
 
DONE!!!
Thank you so much!
The wii console was modded. I followed the ModMii generated guide to the letter.

I used a 2GB MicroSD card and an adapter from MicroSD to full size SD. Worked perfectly.

After completing the guide I managed transferring one of the CDs to an external USB HDD, ejected the CD, and lunched the game through USB Loader GX and it worked.
Goal accomplished. (now I wonder if the owner of the wii well ask me to do more things for the console.)

A few suggestions and questions.

Suggestion:
  • Consider adding to the ModMii generated guide a BOLD notice, if the system menu is lower than 4.0, that in order to use the Bannerbomb v1 exploit the user MUST use a 1 or 2 GB SD card following with an explanation that if the version is lower than 4.0 the console can only read SDSC cards and in order to create a NAND backup there should be about 528 MB of free space, hence, the user should use a 1 or 2 GB card.

  • In part 5 (Install and Configure Priiloader) of the ModMii generated guide there is a list of suggested hacks to enable in the priiloader.
    The WAD installing step is AFTER enabling hacks in the priiloader. As the system update from 3.4E to 4.3E is part of the WADs installation, the first time I launched the priiloader the system version was 3.4E.
    When I followed the steps to enable the suggested hack list, only 5 out the 7 where in the priiloader hacks list (when system version was 3.4E). The two missing were - Wiimmfi Patch v4 & Remove NoCopy Save File Protection.
    After installing all the 45 WADs generated by ModMii, including the system update from 3.4E to 4.3E, I went back to the priiloader and this time the missing 2 where there, with the other 5. Totaling enabling all 7 hacks suggested. I would suggest noting this in the guide.

  • In part 6 (Install WADs) - may I please suggest adding a step between steps C and D. Once the user is in the screen where all the WADs are listed, the >> is set on the first line [..]. May I suggest adding a step to the guide that instructs the user to press the arrow down button once so that the >> crosser will be pointing at the first WAD and only then to hold the + button for 2 seconds as instructed on step D.

Questions:
  1. Does the wii still need the SD card in order to run games through the USB Loader GX and an external hard drive?
    If possible, I think it is preferred making the console safe as possible. The console will be returned to it's owner who has young kids, young and curious. I would like to avoid any "mishappening" if they brows to a menu they should not. If the SD card is not in the wii, they will not be able to accidently find themself in the WAD manager / bootmii or anywhere "dangerous" for the wii system.

    My understating is that at this point the main usage of the SD card will be to recover the NAND backup - is that so?

    Is there ANY downside in ejecting the SD card from the wii? The usage of the console will be transferring the CDs to the external HDD and playing the games through the USB Loader GX.


  2. I might be able to put my hands on a few GameCube CDs and saw there is a way to save them on the external HDD and run them on the wii console.
    Can they be played with wii controllers or MUST use GameCube controllers?


  3. I've created 2 NAND backups.
    1. Immediately after using the Bannerbomb v1 exploit, installing the HomeBrew Channel & Bootmii (only as an ios, could not install as boot2).
      The version of the system was still 3.4 E

    2. After installing all the 45 WADs & after configuring the priiloader as suggested on the generated guide.
      The version of the system was 4.3E.
In the unlikely event that the system would brick, does it matter what backup to choose? Is there a preferred one?​
Thank you​
 
Last edited by SimpleUser1,
  • Like
Reactions: Ryccardo

Site & Scene News

Popular threads in this forum