Hacking D2X and cIOS 249 Confusion

[rysluoive]

ah, yeah, letter bomb, sorry
bannerbomb was for 4.1

Though, banner bomb was easier, it needed only a file copied to the SD, no MAC or specific date required to generate the file for SD.

Hi!
I've just finished the installation of the Hbc and the syscheck.Here are the results:

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: PAL
System Menu 4.3E (v514)

Drive date: 02.13.2007
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x11
Console ID: 122730385
Console Type: Wii
Shop Channel Country: Greece (79)
Boot2 v4
Found 85 titles.
Found 46 IOS on this console. 18 of them are stubs.

IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249 (rev 65280): Stub
IOS250 (rev 65280): Stub
IOS254 (rev 65280): Stub
BC v6
MIOS v10
Report generated on 02/06/2018.

Thank you!

 

[Cyan]

thank you.
I guess I was wrong, the console doesn't seem to have been hacked before

I recommend that you launch hackmii installer again (from HBC this time, put the elf in /apps/hackmiii/ folder! or do the letterbomb again but it's not needed)
From the hackmii installer, install Bootmii as IOS. It will install it in slot 254, and replace your current "stub" (which means dummy, useless, empty slot)

Then you can proceed with the d2x cIOS installation steps to add base57 in slot 249.

 

[ScarletDreamz]

SetMiiUp perhaps? O:

 

[rysluoive]

thank you.
I guess I was wrong, the console doesn't seem to have been hacked before

I recommend that you launch hackmii installer again (from HBC this time, put the elf in /apps/hackmiii/ folder! or do the letterbomb again but it's not needed)
From the hackmii installer, install Bootmii as IOS. It will install it in slot 254, and replace your current "stub" (which means dummy, useless, empty slot)

Then you can proceed with the d2x cIOS installation steps to add base57 in slot 249.

Hi!I've just install the bootmii as IOS and d2x v8 final using your instructions from the previous post:
what : d2x v8 final
where : 249
base : 57
version : 21008
Press A to install

when complete, you can do it again (not necessary, but might be useful one day) with this changes :
where : 250
base : 56
Is it possible to check if everything is OK?
SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: PAL
System Menu 4.3E (v514)

Drive date: 02.13.2007
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x11
Console ID: 122730385
Console Type: Wii
Shop Channel Country: Greece (79)
Boot2 v4
Found 85 titles.
Found 46 IOS on this console. 17 of them are stubs.

IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249 (rev 65280): Stub
IOS250 (rev 65280): Stub
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 02/06/2018.

Thank you very much!

 

[ScarletDreamz]

Cios are still not installed, you will need to redo the process, use SetMiiUp to save yourself some time.

 

[rysluoive]

Cios are still not installed, you will need to redo the process, use SetMiiUp to save yourself some time.

I am sorry I post the wrong results.Here are the correct ones:
SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: PAL
System Menu 4.3E (v514)

Drive date: 02.13.2007
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x11
Console ID: 122730385
Console Type: Wii
Shop Channel Country: Greece (79)
Boot2 v4
Found 85 titles.
Found 46 IOS on this console. 15 of them are stubs.

IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249[57] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS250[56] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 02/06/2018.
Thank you very much!

 

[ScarletDreamz]

IOS249[57] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS250[56] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0

There you go! That should to the job.

 

[Cyan]

you have all you'll need for all useful homebrew. (old homebrew used different cIOS, but you will not use them, so don't worry)

now, most homebrew uses the IOS in slot 58 to access ann the hardware : SD, USB, Internal memory (NAND chipset), wiimote, etc.
the patched IOS (cIOS) are used only by USB Loaders as they are specifically written to redirect disc access to external device (SD or USB) to read games from there instead of disc.

most game should work fine with the IOS based on IOS57, that you installed in slot 249. This is the default slot used by USBLoaders.
few games might require IOS56, that you installed in slot 250. you can set that slot individually, per game, if needed, and keep slot 249 for all others.

Your setup is different than the "common practice", because I made you install base 57 on slot 249 by default, while historically most users did the contrary (install base56 in slot249).
but more games work better with 57, and users have to set slot 250 in the loader's setting.
installing it the way I told you, don't don't have to change the "default" slot to get that compatibility.
so far, I know only 2 games which work with 56 instead of 57.

Just remember your own setup, and know that when you'll read guide/tuto/users telling to "use 250", you should be using 249 instead

 

[rysluoive]

you have all you'll need for all useful homebrew. (old homebrew used different cIOS, but you will not use them, so don't worry)

now, most homebrew uses the IOS in slot 58 to access ann the hardware : SD, USB, Internal memory (NAND chipset), wiimote, etc.
the patched IOS (cIOS) are used only by USB Loaders as they are specifically written to redirect disc access to external device (SD or USB) to read games from there instead of disc.

most game should work fine with the IOS based on IOS57, that you installed in slot 249. This is the default slot used by USBLoaders.
few games might require IOS56, that you installed in slot 250. you can set that slot individually, per game, if needed, and keep slot 249 for all others.

Your setup is different than the "common practice", because I made you install base 57 on slot 249 by default, while historically most users did the contrary (install base56 in slot249).
but more games work better with 57, and users have to set slot 250 in the loader's setting.
installing it the way I told you, don't don't have to change the "default" slot to get that compatibility.
so far, I know only 2 games which work with 56 instead of 57.

Just remember your own setup, and know that when you'll read guide/tuto/users telling to "use 250", you should be using 249 instead

Thank you very much both of you especially you,Cyan!I 've installed the USBLoaderGX and I even managed to run my first backup game from a usb thumb stick using the WiiBackupManager! Everything works great!!! Now,I might try the Nintendont and some emulators.

 

[Cyan]

oh, your thumb stick is working?
flash drives are usually not working, or having issues (freezes when trying to write, download cover, dump a disc, etc.)
you'll know it's the device's fault if you encounter a freeze, it will be fixed with using HDD.
Or, you are lucky and your flash drive works fine

enjoy

 

[sideskroll]

you have all you'll need for all useful homebrew. (old homebrew used different cIOS, but you will not use them, so don't worry)

now, most homebrew uses the IOS in slot 58 to access ann the hardware : SD, USB, Internal memory (NAND chipset), wiimote, etc.
the patched IOS (cIOS) are used only by USB Loaders as they are specifically written to redirect disc access to external device (SD or USB) to read games from there instead of disc.

most game should work fine with the IOS based on IOS57, that you installed in slot 249. This is the default slot used by USBLoaders.
few games might require IOS56, that you installed in slot 250. you can set that slot individually, per game, if needed, and keep slot 249 for all others.

Your setup is different than the "common practice", because I made you install base 57 on slot 249 by default, while historically most users did the contrary (install base56 in slot249).
but more games work better with 57, and users have to set slot 250 in the loader's setting.
installing it the way I told you, don't don't have to change the "default" slot to get that compatibility.
so far, I know only 2 games which work with 56 instead of 57.

Just remember your own setup, and know that when you'll read guide/tuto/users telling to "use 250", you should be using 249 instead

Hey man, was reading around the forum (killing some time...) And I became POSSESSED by the urgent need to ask you why yoy always recommend base57? I always use base 56 and have not found a single game that fails to work properly (well, aside from tintin obviously).
Is there something I should know?
How is 57 preferable over 56? What's the difference?
Just out of curiosity .I understand cIOS and the way they work etc. Only need to know whats the difference between those 2 bases (and well, why do some guides recommend installing base 58 as well, for games that use USB peripherals I presume)?

 

[Cyan]

because some games need it (Call of duty, Just dance2017 ) and other games work fine with 57 too, so why keep telling users to install base56 on the default slot and base57 on slot250 and tell them to switch the setting to slot250 because slot249 is not good? you'd better just install the better one in the default slot.

Though, you might have seen thread where users reported base57 doesn't work with Spyro's USB accessory (the NFC gate), and only works with base 56.
a lot of people came asking how to fix call of duty and Just dance, because they follow the common softmod guides. I just think more people want to play call of duty and just dance than people wanting to play Spyro.
I don't know if a lot of other games require IOS56, but so far I got only 2 reports of games not working with 57. So, I guess it's the same ratio (spyro+another I forgot, against Cod+Just Dance). I just base my choice on the number of helped users, and think 57 is better as default.

Base58 on the contrary, is less compatible. A lot of game just black screens at launch.
very few games should need base58, as IOS57 seems to work find.
I guess base58 is needed only on specific games requiring IOS58 (games using WiiSpeak?) but I never tested any, so I can't tell for sure.

 

[sideskroll]

because some games need it (Call of duty, Just dance2017 ) and other games work fine with 57 too, so why keep telling users to install base56 on the default slot and base57 on slot250 and tell them to switch the setting to slot250 because slot249 is not good? you'd better just install the better one in the default slot.

Though, you might have seen thread where users reported base57 doesn't work with Spyro's USB accessory (the NFC gate), and only works with base 56.
a lot of people came asking how to fix call of duty and Just dance, because they follow the common softmod guides. I just think more people want to play call of duty and just dance than people wanting to play Spyro.
I don't know if a lot of other games require IOS56, but so far I got only 2 reports of games not working with 57. So, I guess it's the same ratio (spyro+another I forgot, against Cod+Just Dance). I just base my choice on the number of helped users, and think 57 is better as default.

Base58 on the contrary, is less compatible. A lot of game just black screens at launch.
very few games should need base58, as IOS57 seems to work find.
I guess base58 is needed only on specific games requiring IOS58 (games using WiiSpeak?) but I never tested any, so I can't tell for sure.

Oh... I see. So there's no difference at all. I thought maybe one was "faster" and the other more compatible. Something like that...
You know what. I'll help you out
I KNOW all of my games run fine and I KNOW I use base56. So I'll just switch to 57 and report if any stop working.

 

[Cyan]

the 56 is reading over USB slightly faster than 57. (very slightly, might not even be noticeable in some games. You need games with long loading screens, like One piece for example)
that's why it was decided to install 56 as default back when cIOS rev18 was released.

I just pick 57 to prevent telling users to edit their slot and use 250 instead of the default one, or else they will ask why Cod doesn't work

 

[sideskroll]

the 56 is reading over USB slightly faster than 57. (very slightly, might not even be noticeable in some games. You need games with long loading screens, like One piece for example)
that's why it was decided to install 56 as default back when cIOS rev18 was released.

I just pick 57 to prevent telling users to edit their slot and use 250 instead of the default one, or else they will ask why Cod doesn't work

Ahahahahhahaha .Gotcha
Never heard of this "One Piece" though so I can't comment.
Guess I'll stick to my trusty 56 then. (You know, I actually have to go the OTHER way around to get it to use 56? I have to edit the loader to use 250 since that's where I have my 56 )

 

[Madridi]

@Cyan

Haven't updated my Wii since 2008/2009, so I have some questions. Instead of making a new thread, I'll ask what I remember here:

- My Wii, like yours, has a wiikey. I remember it we were advised to stay on system menu 4.1 (or was it 4.2?) and not update to 4.3. I dont remember what the reason was. It broke some compatibility or something? Anyway, is that still the case or should I update? I also remember wiikey releasing an update a few years later (1.99b) .. I didnt update to that. Is that the best FW for it?

- I see advice about installing d2x v8.. I see d2x went all the way up to beta 10r57 before it stopped being developed. Is there any reason we are sticking with v8? Any disadvantages from not updating?

- Are cIOS in 202, 222, 223 no longer necessary? Is d2x on IOS 249 and 250 with base 56 and 57 the ULTIMATE combination? No disadvantages whatsoever?

- I remember restoring trucha bug to IOS 37/38 among others, is that no longer necessary?

- I see priiloader was updated recently, do you recommend updating?

- Back in the day, CFG, USB Loader GX, Wiiflow were the best 3 USB loaders as far as I remember.. Is this still the case? I notices several of these projects have several forks. I would like to have the best version of each on my HBC. Can you direct me to those? Cause I'm not sure the ones in the official thread for each ones apply anymore.

- I assume MultiModManager (MMM) is the still the best WAD installer?

- What do you think of DOP-Mii? I remember using it as a All in 1 tool, but by the time I stopped bothering with the wii, the latest versions of that program had issues. Is it good to use now? I also think there are several versions of that program. Any specific one?

- Same question as above, but about syscheck. I remember there were issues with the latest versions at the time, and I see there are different versions now (GX, HDE, etc..) .. Can you guide me to the best one?

I think that's all my questions at the moment. They are more than I thought lol. Thanks!

 

[Cyan]

- v4.2 broke something (region free I think?) from wiikey, and affected games launched from the disc channel. there's no problem updating to 4.3 if you use USBLoaders to launch the game.
Wiikey released few 1.9x version, I don't remember if last one is b or s (it was always done to fix a specific game, like s version to fix dual layer for Smash bros, etc.)
I can do some search if needed, but again as long as you don't play burned disc from disc channel then wiikey version has no effect and will never conflict. (except if you try to dump a dual layer game without the S version)

- v8 is the same as v10 r52
v9 is the same as v10 r53
d2x got a version increase due to vWii release, v9 was beta and unstable so instead of releasing it the developer decided to revert the changes and make v8 compatible with vWii instead. But to prevent confusion with "v8 vWii being newer than v9 wii" he decided to make them both v10 and v10 alternative, for both Wii and vWii.
don't update to v10-alt (r53) it's buggy. keep either v8 or update to v10 r52 (no reason).

- Hermes' cIOS are rarely used now, and probably useless. they don't even work on vWii, and all games are working (well, almost, there are still incompatible/anti piracy checked games).
the 249-56 and 250-57 is the common setup and all (relative) games will work. though, some games will require base57 (call of duty, just dance 2017)
That's why I recommend only base57 when I tell users to install only ONE cIOS to make a minimalist installation guide. one single cIOS on the console plays 99% of games. (there are still games like Tintin or Driver not working)


- I never used Priiloader, but installed it recently on my brother's console to bypass the menu and HBC (because my nephew deleted homebrew by mistake. I locked everything and only USBGX is now possible to use on the console).
If you have bootmii boot2, you don't "need" priiloader, but it could be useful if you want menu hacks (like auto press A at boot, prevent disc update, etc.) but personally I don't need it as I bypass the system menu completely with boot2->hbc
do like you want after updated to 4.3
If you have a wiikey, chances are you have bootmii possible into boot2, as long as you have a NAND backup (or your keys) you can rescue your console in case of brick.
If you don't have boot2, then yes you should install priiloader as it's the best way to bypass and fix semi-brick state.

as for Updating it if you already have v0.7, I don't know what is really improved. I don't think you need it. the feature which could have been useful is not working as intended so it's useless.
Don't risk updating.
Except that if you update the system menu, and you already have priiloader + hacks, the adresses will not match anymore! you might have to follow modmii if you want to update your console and get all latest IOS and system version.

- CFG was good for wii, but I don't know if it's still updated.
Now both USBLoaderGX and Wiiflow are up to date with latest possibilities (nintendont, vWii)

I don't know the latest wiiflow, because there's a "mod thread" which is probably newer than the official one.
the latest usbgx is in my signature, official pinned thread or on sourceforge's official repository.

- MultiModManager was never the best one, never liked it cause it's closed source, breaking GPL, etc.
it's old and I don't know if it has been updated/maintained to support AHBAccess instead of cIOS236.
Best manager is probably this one, for both Wii and vWii : https://github.com/FIX94/Some-YAWMM-Mod/releases
it works with the official IOS58, no need to have any cIOS to manage wads.

- DOPMii ... I always mix that name with another tool. Is that the "automated softmod tool" like Pimpmywii, or the system IOS manager?
if it's the IOS manager, it was nice back in the time, as you could check and edit your cIOS yourself.
I don't think it's needed now, it works only on Wii (not vWii) and it could be dangerous.
If it's the "pimpmywii" clone, don't use it! don't trust tools editing your console in batch for you.

or you think about ModMii instead of DOPMii?

- Syscheck is just listing your IOS slots, you can use old version without issue, but latest/best/maintained version is probably in my signature too.

 

[The Real Jdbye]

because some games need it (Call of duty, Just dance2017 ) and other games work fine with 57 too, so why keep telling users to install base56 on the default slot and base57 on slot250 and tell them to switch the setting to slot250 because slot249 is not good? you'd better just install the better one in the default slot.

Though, you might have seen thread where users reported base57 doesn't work with Spyro's USB accessory (the NFC gate), and only works with base 56.
a lot of people came asking how to fix call of duty and Just dance, because they follow the common softmod guides. I just think more people want to play call of duty and just dance than people wanting to play Spyro.
I don't know if a lot of other games require IOS56, but so far I got only 2 reports of games not working with 57. So, I guess it's the same ratio (spyro+another I forgot, against Cod+Just Dance). I just base my choice on the number of helped users, and think 57 is better as default.

Base58 on the contrary, is less compatible. A lot of game just black screens at launch.
very few games should need base58, as IOS57 seems to work find.
I guess base58 is needed only on specific games requiring IOS58 (games using WiiSpeak?) but I never tested any, so I can't tell for sure.

I believe there's only one game that needs IOS58, it's some fitness game (Your Shape) that used USB 2.0.
So most people probably won't need it. Unless you have the camera accessory that came with the legit game it's probably unplayable anyway.

 

[Madridi]

- v4.2 broke something (region free I think?) from wiikey, and affected games launched from the disc channel. there's no problem updating to 4.3 if you use USBLoaders to launch the game.
Wiikey released few 1.9x version, I don't remember if last one is b or s (it was always done to fix a specific game, like s version to fix dual layer for Smash bros, etc.)
I can do some search if needed, but again as long as you don't play burned disc from disc channel then wiikey version has no effect and will never conflict. (except if you try to dump a dual layer game without the S version)

- v8 is the same as v10 r52
v9 is the same as v10 r53
d2x got a version increase due to vWii release, v9 was beta and unstable so instead of releasing it the developer decided to revert the changes and make v8 compatible with vWii instead. But to prevent confusion with "v8 vWii being newer than v9 wii" he decided to make them both v10 and v10 alternative, for both Wii and vWii.
don't update to v10-alt (r53) it's buggy. keep either v8 or update to v10 r52 (no reason).

- Hermes' cIOS are rarely used now, and probably useless. they don't even work on vWii, and all games are working (well, almost, there are still incompatible/anti piracy checked games).
the 249-56 and 250-57 is the common setup and all (relative) games will work. though, some games will require base57 (call of duty, just dance 2017)
That's why I recommend only base57 when I tell users to install only ONE cIOS to make a minimalist installation guide. one single cIOS on the console plays 99% of games. (there are still games like Tintin or Driver not working)


- I never used Priiloader, but installed it recently on my brother's console to bypass the menu and HBC (because my nephew deleted homebrew by mistake. I locked everything and only USBGX is now possible to use on the console).
If you have bootmii boot2, you don't "need" priiloader, but it could be useful if you want menu hacks (like auto press A at boot, prevent disc update, etc.) but personally I don't need it as I bypass the system menu completely with boot2->hbc
do like you want after updated to 4.3
If you have a wiikey, chances are you have bootmii possible into boot2, as long as you have a NAND backup (or your keys) you can rescue your console in case of brick.
If you don't have boot2, then yes you should install priiloader as it's the best way to bypass and fix semi-brick state.

as for Updating it if you already have v0.7, I don't know what is really improved. I don't think you need it. the feature which could have been useful is not working as intended so it's useless.
Don't risk updating.
Except that if you update the system menu, and you already have priiloader + hacks, the adresses will not match anymore! you might have to follow modmii if you want to update your console and get all latest IOS and system version.

- CFG was good for wii, but I don't know if it's still updated.
Now both USBLoaderGX and Wiiflow are up to date with latest possibilities (nintendont, vWii)

I don't know the latest wiiflow, because there's a "mod thread" which is probably newer than the official one.
the latest usbgx is in my signature, official pinned thread or on sourceforge's official repository.

- MultiModManager was never the best one, never liked it cause it's closed source, breaking GPL, etc.
it's old and I don't know if it has been updated/maintained to support AHBAccess instead of cIOS236.
Best manager is probably this one, for both Wii and vWii : https://github.com/FIX94/Some-YAWMM-Mod/releases
it works with the official IOS58, no need to have any cIOS to manage wads.

- DOPMii ... I always mix that name with another tool. Is that the "automated softmod tool" like Pimpmywii, or the system IOS manager?
if it's the IOS manager, it was nice back in the time, as you could check and edit your cIOS yourself.
I don't think it's needed now, it works only on Wii (not vWii) and it could be dangerous.
If it's the "pimpmywii" clone, don't use it! don't trust tools editing your console in batch for you.

or you think about ModMii instead of DOPMii?

- Syscheck is just listing your IOS slots, you can use old version without issue, but latest/best/maintained version is probably in my signature too.

Thanks for the info. I will spend some time doing research on some of this answers tomorrow and reply back with questions/clarifications

 

[Madridi]

- v4.2 broke something (region free I think?) from wiikey, and affected games launched from the disc channel. there's no problem updating to 4.3 if you use USBLoaders to launch the game.
Wiikey released few 1.9x version, I don't remember if last one is b or s (it was always done to fix a specific game, like s version to fix dual layer for Smash bros, etc.)
I can do some search if needed, but again as long as you don't play burned disc from disc channel then wiikey version has no effect and will never conflict. (except if you try to dump a dual layer game without the S version)

- v8 is the same as v10 r52
v9 is the same as v10 r53
d2x got a version increase due to vWii release, v9 was beta and unstable so instead of releasing it the developer decided to revert the changes and make v8 compatible with vWii instead. But to prevent confusion with "v8 vWii being newer than v9 wii" he decided to make them both v10 and v10 alternative, for both Wii and vWii.
don't update to v10-alt (r53) it's buggy. keep either v8 or update to v10 r52 (no reason).

- Hermes' cIOS are rarely used now, and probably useless. they don't even work on vWii, and all games are working (well, almost, there are still incompatible/anti piracy checked games).
the 249-56 and 250-57 is the common setup and all (relative) games will work. though, some games will require base57 (call of duty, just dance 2017)
That's why I recommend only base57 when I tell users to install only ONE cIOS to make a minimalist installation guide. one single cIOS on the console plays 99% of games. (there are still games like Tintin or Driver not working)


- I never used Priiloader, but installed it recently on my brother's console to bypass the menu and HBC (because my nephew deleted homebrew by mistake. I locked everything and only USBGX is now possible to use on the console).
If you have bootmii boot2, you don't "need" priiloader, but it could be useful if you want menu hacks (like auto press A at boot, prevent disc update, etc.) but personally I don't need it as I bypass the system menu completely with boot2->hbc
do like you want after updated to 4.3
If you have a wiikey, chances are you have bootmii possible into boot2, as long as you have a NAND backup (or your keys) you can rescue your console in case of brick.
If you don't have boot2, then yes you should install priiloader as it's the best way to bypass and fix semi-brick state.

as for Updating it if you already have v0.7, I don't know what is really improved. I don't think you need it. the feature which could have been useful is not working as intended so it's useless.
Don't risk updating.
Except that if you update the system menu, and you already have priiloader + hacks, the adresses will not match anymore! you might have to follow modmii if you want to update your console and get all latest IOS and system version.

- CFG was good for wii, but I don't know if it's still updated.
Now both USBLoaderGX and Wiiflow are up to date with latest possibilities (nintendont, vWii)

I don't know the latest wiiflow, because there's a "mod thread" which is probably newer than the official one.
the latest usbgx is in my signature, official pinned thread or on sourceforge's official repository.

- MultiModManager was never the best one, never liked it cause it's closed source, breaking GPL, etc.
it's old and I don't know if it has been updated/maintained to support AHBAccess instead of cIOS236.
Best manager is probably this one, for both Wii and vWii : https://github.com/FIX94/Some-YAWMM-Mod/releases
it works with the official IOS58, no need to have any cIOS to manage wads.

- DOPMii ... I always mix that name with another tool. Is that the "automated softmod tool" like Pimpmywii, or the system IOS manager?
if it's the IOS manager, it was nice back in the time, as you could check and edit your cIOS yourself.
I don't think it's needed now, it works only on Wii (not vWii) and it could be dangerous.
If it's the "pimpmywii" clone, don't use it! don't trust tools editing your console in batch for you.

or you think about ModMii instead of DOPMii?

- Syscheck is just listing your IOS slots, you can use old version without issue, but latest/best/maintained version is probably in my signature too.

So I finally got some time to update my Wii.

- Yes, 4.2 broke region free. That's it. Thanks for the reminder. So I stayed at 4.1U, while upgrading all other IOS to versions before stubs.

- About wiikey, no I am not referring to 1.9x.. There is a version that was released a few years later called 1.99b. It has a thread here on gbatemp and you even have replies in it lol. I am wondering if that version fixed everything?

- I have 2 consoles. My US one that is chipped with a wiikey is a launch model, so it has bootmii as boot2. My other console is European. It has bootmii as IOS iirc. I think I have BOOT2v3 on that console.

- So I did some research about usbloaders, seems like GX and cfg mod (a fork of the original) are the best, followed by wiiflow mod. Haven't had a chance to test them all thoroughly but it's worth mentioning for information purposes

- About wadmanagers, not sure why you think MMM was never the best. I don't k ow about GPL violations and it being closed source, but from end user perspective it is a very useful program that is multifunctional. It can install IOS directly from NUS, and patch them on the fly. I tried the one you linked and it worked great, but I saw no difference between that and MMM in terms of usage. Maybe tastes I guess. I kept them both in HBC, thanks

- No I didn't make a mistake with the name. I do mean Dop-Mii (formally known as Dop-IOS). It has an integrated syscheck (which I'm not sure it works), and can download missing channels or IOS from Nintendo servers and path them in the fly just like MMM. It might be redundant with the existence of MMM, but it's worth checking out
And no, I don't use stuff like cioscorp or darkcorp or pimpmywii. I don't like programs like that, and I don't think they are particularly safe.

---------

Ok so now, after some updates, here is my latest syscheck in my chipped Wii:

Spoiler: Syscheck

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: NTSC-U
System Menu 4.1U (v449)
Priiloader installed
Drive date: 09.07.2006
Homebrew Channel 1.1.0 running on IOS58

Hollywood v0x11
Console ID: 41302344
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v2
Found 134 titles.
Found 52 IOS on this console. 2 of them are stubs.

IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 10): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 257): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS17 (rev 1032): No Patches
IOS20 (rev 12): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2576): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 4889): Trucha Bug, NAND Access
IOS51 (rev 4633): No Patches
IOS52 (rev 5661): No Patches
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6174): Trucha Bug, NAND Access
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 6687): Trucha Bug, NAND Access
IOS80 (rev 6944): Trucha Bug, NAND Access
IOS202[60] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[38+37] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS236[36] (rev 65535, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS246[57] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS247[58] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS248[56] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS249[56] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
IOS255 (rev 31337): Flash Access
BC v5
MIOS v9
Report generated on 03/19/2018.

Some cIOS I have from long ago. What do think about my set up above? Anything I should add/remove?

And finally, you are the perfect person to ask this since you have a chipped Wii with bootmii as boot2 as well: if you notice, I didn't upgrade MIOS, BC, and my BOOT2 is v2

2 questions:
- Does updating BC and MIOS affect wiikey for GameCube games in anyway, or are they safe to update?
- I assume I should NOT update boot2v2 to boot2v4? Or should I update and I can still reinstall bootmii? I kept it without upgrading until I get some info.

Thanks again for the help