Hacking In search of the “ideal” IOS setup

[gamecaptor]

Hello all,

I’ve been doing some research on IOS’s for the Wii and one thing I can’t seem to figure out is there such thing as a “ideal” for an IOS configuration. I see there is some discrepancies with which bases to use for Waninkoko’s cIOSX and Hermes IOS’, but what about the IOS’ less than 200? Which version of IOS58 should I be running? Which IOSs need to have the Trucha Bug installed? Is ES Identify or NAND access necessary on the lower IOSs? There are questions that I can’t seem to find the answer to and I am hoping the community can offer some insight to this for me.

My goal would be to have a section added to the Complete Softmod Guide (http://www.completesoftmodguide.tk/) that would have an IOS “best practices” section. This section would essentially state that if you run sysCheck, this is what it should look like to be as good as you can get. It seems to me that people like to experiment with their Wii’s and brick them (seen LOTS of these posts as I’m trolling the forums). I want to help people not screw up their Wii’s if at all possible (which in turn would mean if I can come up with an ideal, then I would need to come up with a guide on how to get there, but one thing at a time).

On the topic of Waninkoko’s cIOSX and Hermes IOS’, since there seems to be a lot of conflict which way to set these up, maybe a description of the variables added to this “best practices” section would let some people make good/informed decisions. I found this information on some other posts:

IOS249[57]-v19 (rev19 of Waninkokos cIOS) = Recommend by Waninkoko. Improves speed for USB loading. However, some Games might not work.
IOS250[38]-v65535 (rev19 of Waninkokos cIOS) = Stable IOS with the ability to install Wads

IOS202[60]-v65535 (v5 of Hermes cIOS) = USB2.0 for MPlayer, WiiXplorer and stuff
IOS222[38]-v65535 (v5 of Hermes cIOS) = Stable IOS with the ability to install Wads
IOS223[37]-v65535 (v5 of Hermes cIOS) = For use with Music Games with USB devices like Rock Band, Guitar Hero...
IOS224[57]-v65535 (v5 of Hermes cIOS) = Better speed for USB loading. However, some Games might not work

Something like this (with more detailed info) might prove useful.

To help move this along, I took a virgin 4.0 Wii (US) through a softmod process and documented the IOS changes along the way. Below are those steps with links to the sysCheck reports

1. This is a sysCheck with a virgin Wii 4.0 (minus the HBC and BootMii installed)
http://cid-a21e1c8f1f16c524.office.live.co...04.0%20Wii.xlsx

2. Used Multi-Mod Manager v13.2 to install the patched IOS36
http://cid-a21e1c8f1f16c524.office.live.co...%20Install.xlsx
(Only change is IOS15 dropped from rev 266 to rev 257, IOS36 went up from rev 3094 to 3351 and the Trucha Bug was added to both)

3. Using IOS36, installed Waninkoko’s 4.2 Update
http://cid-a21e1c8f1f16c524.office.live.co...2%20Update.xlsx
(Added IOS56, IOS57 and IOS 70. Change the version and added Trucha Bug for all existing IOSs. Added ES Identify and NAND Access to most IOSs)

4. Using IOS36, installed Waninkoko’s 4.3 Update
http://cid-a21e1c8f1f16c524.office.live.co...3%20Update.xlsx
(I choose yes to 'Patch IOS/System Menu'. It error-ed when trying to install IOS80, but everything else seemed to install fine).

5. Installed Waninkoko’s cIOSX v20b and Hermes v5.1 (I used the bases that are listed above)
http://cid-a21e1c8f1f16c524.office.live.co...%20Install.xlsx

Here is where I have stopped. I’m sure I am way off from making this a “best partice” IOS setup, which is why I am turning to you for guidance.

For good measure I have two other sysChecks from other Wiis. These are wildly different from the one I just took the process through.
Black Wii
http://cid-a21e1c8f1f16c524.office.live.co...lack%20Wii.xlsx
White Wii
http://cid-a21e1c8f1f16c524.office.live.co...hite%20Wii.xlsx

I would greatly appreciate any input you could provide.

Regards.

 

[mike333]

I’ve been doing some research on IOS’s for the Wii and one thing I can’t seem to figure out is there such thing as a “ideal” for an IOS configuration. I see there is some discrepancies with which bases to use for Waninkoko’s cIOSX and Hermes IOS’, but what about the IOS’ less than 200? Which version of IOS58 should I be running? Which IOSs need to have the Trucha Bug installed? Is ES Identify or NAND access necessary on the lower IOSs? There are questions that I can’t seem to find the answer to and I am hoping the community can offer some insight to this for me.My signature explains it.

My goal would be to have a section added to the Complete Softmod Guide (http://www.completesoftmodguide.tk/) that would have an IOS “best practices” section. This section would essentially state that if you run sysCheck, this is what it should look like to be as good as you can get. It seems to me that people like to experiment with their Wii’s and brick them (seen LOTS of these posts as I’m trolling the forums). I want to help people not screw up their Wii’s if at all possible (which in turn would mean if I can come up with an ideal, then I would need to come up with a guide on how to get there, but one thing at a time).Best practices for 'wanna hack my wii' users? Here are some:
- finish school so You could read and understand things
- read, ask, read again, ask again, then maybe do something
- do not trust any tutorials, find other ones and ask about differences between them
- do not install just everything - less is more
- bootmii as boot2 if you can
- if locked boot2 use another recovery method, priiloader maybe
- nand backup made often
- do not rush in updates, wait some time and read about bricks they made

On the topic of Waninkoko’s cIOSX and Hermes IOS’, since there seems to be a lot of conflict which way to set these up, maybe a description of the variables added to this “best practices” section would let some people make good/informed decisions. I found this information on some other posts:
[...]
Something like this (with more detailed info) might prove useful.

http://gwht.wikidot.com/ios236
http://gwht.wikidot.com/ios249
That's all You need for most cases.
QUOTE(gamecaptor @ Sep 2 2010, 02:40 AM)

To help move this along, I took a virgin 4.0 Wii (US) through a softmod process and documented the IOS changes along the way. Below are those steps with links to the sysCheck reports
[...]
2. Used Multi-Mod Manager v13.2 to install the patched IOS36
(Only change is IOS15 dropped from rev 266 to rev 257, IOS36 went up from rev 3094 to 3351 and the Trucha Bug was added to both)
[...]
(Added IOS56, IOS57 and IOS 70. Change the version and added Trucha Bug for all existing IOSs. Added ES Identify and NAND Access to most IOSs)
[...]
Here is where I have stopped. I’m sure I am way off from making this a “best partice” IOS setup, which is why I am turning to you for guidance.
[...]
I would greatly appreciate any input you could provide.

Please, just die now...

 

[qwertymodo]

Yeah, basically best practice is for all IOSes base 56
250->base 37

However, as I said, this one has a lot more options, therefore it is open to debate. But hey, you have as many open slots as you do bases, and way more, so you can pretty much do whatever you want.

 

[mike333]

Yeah, basically best practice is for all IOSes

 

[mauifrog]

I should look just like this

IOS Version, FakeSign, ES_Identify, NAND, Flash
"250 (v65535)",Enabled,Enabled,Enabled,Disabled -base 57 v20 -default cios
"249 (v17)",Enabled,Enabled,Enabled,Disabled -base 38 v17, triforce supportbase
"248 (v65535)",Enabled,Enabled,Enabled,Disabled -base 56 -v20
"247 (v65535)",Enabled,Enabled,Enabled,Disabled -base 37 -v20
"236 (v54321)",Enabled,Enabled,Enabled,Disabled TBR v1.12 X4 patches
"224 (v65535)",Enabled,Enabled,Enabled,Disabled base -57 v5.1
"223 (v4)",Enabled,Enabled,Disabled,Disabled base 37/38 v4
"222 (v4)",Enabled,Enabled,Disabled,Disabled base 38 v4
"202 (v65535)",Enabled,Enabled,Enabled,Disabled base 60 v5.1
"90 (v54321)",Enabled,Enabled,Disabled,Disabled dip
"80 (v54321)",Enabled,Enabled,Disabled,Disabled dip
"70 (v54321)",Enabled,Enabled,Disabled,Disabled dip
"60 (v54321)",Enabled,Enabled,Disabled,Disabled dip
"58 (v6175)",Disabled,Disabled,Disabled,Disabled
"56 (v5405)",Disabled,Disabled,Disabled,Disabled
"50 (v54321)",Enabled,Enabled,Disabled,Disabled dip
"37 (v3869)",Disabled,Disabled,Disabled,Disabled
"36 (v54321)",Enabled,Enabled,Enabled,Disabled dip
"35 (v3349)",Disabled,Disabled,Disabled,Disabled
"34 (v3348)",Disabled,Disabled,Disabled,Disabled
"33 (v3091)",Disabled,Disabled,Disabled,Disabled
"30 (v54321)",Enabled,Enabled,Disabled,Disabled dip
"28 (v1550)",Disabled,Disabled,Disabled,Disabled
"22 (v1037)",Disabled,Disabled,Disabled,Disabled
"21 (v782)",Disabled,Disabled,Disabled,Disabled
"20 (v54321)",Enabled,Enabled,Disabled,Disabled dip
"17 (v775)",Disabled,Disabled,Disabled,Disabled
"16 (v54321)",Enabled,Enabled,Disabled,Enabled
"15 (v523)",Disabled,Disabled,Disabled,Disabled
"14 (v520)",Disabled,Disabled,Disabled,Disabled
"13 (v273)",Disabled,Disabled,Disabled,Disabled
"11 (v54321)",Enabled,Enabled,Disabled,Disabled dip
"9 (v54321)",Enabled,Enabled,Disabled,Disabled dip

This is what I do, any tell others to do.

 

[dn_angel000]

@qwertymoto: I think u meant 202-> base 60

 

[xfcrowman]

I see bright future but need second opinion.

For now AHBPROT is in:
- IOS236 Installer v2
- priiloader v0.5 installer
Missing ones (for me at least):
- DOP-Mii (under development)
- Waninkoko's IOS249 (anyone know something more?)

When they update we could nuke IOS236 from orbit - no longer needed.

You may already know this, but you can already compile the latest version of Dop-mii (called WiInstaller), and it can use AHBPROT to install any IOS.

There are also some other apps that use AHBPROT: Tantric's emulators, wiixplorer, and ftpii (need to compile on your own).

QUOTEMy question:
Is there any way to disable AHBPROT by nintendo using software update?
Same question about hardware update (just like boot2).

I would like to know the answer to this question as well. It would be unfortunate if future software/hardware updates render this new method of full hardware access useless.

 

[qwertymodo]

@qwertymoto: I think u meant 202-> base 60

Nah, IOS57 > IOS60... but it's your Wii, do whatever you want

Anyway, the fact that homebrew is likely to move away from IOS202 in favor of IOS58 + AHBPROT once the IOS58 code makes the mainline libogc makes it nearly irrelevant.

 

[mike333]

You may already know this, but you can already compile the latest version of Dop-mii (called WiInstaller), and it can use AHBPROT to install any IOS.
Wiinstal should be avoided. Untested/broken/pesky application.
I'll wait a little bit for clarification.
QUOTE(xfcrowman @ Sep 2 2010, 01:34 PM) There are also some other apps that use AHBPROT: Tantric's emulators, wiixplorer, and ftpii (need to compile on your own).

New method is covered by libogc or apps uses their own implementation?
I smell bricks coming.

 

[qwertymodo]

New method is covered by libogc or apps uses their own implementation?
I smell bricks coming.

The USB2.0 code via IOS58 is in the current svn libogc. However, it hasn't made it to a stable release yet. The AHBPROT code is basically just checking if the flag is set and then accessing the hardware as usual, so no problems there. It's really no different than DVDX besides the method of checking for it.

 

[mike333]

The USB2.0 code via IOS58 is in the current svn libogc. However, it hasn't made it to a stable release yet. The AHBPROT code is basically just checking if the flag is set and then accessing the hardware as usual, so no problems there. It's really no different than DVDX besides the method of checking for it.

Thanks for clarification.

 

[xfcrowman]

Wiinstal should be avoided. Untested/broken/pesky application.
I'll wait a little bit for clarification.

I was not aware of this - thanks for letting me know. I had compiled this a few days ago, but I will do the same as you and just wait for an official version to be released.

 

[gamecaptor]

Hello all,

thank you for adding to this thread. I was looking over the Wii IOS Wiki (http://en.wikipedia.org/wiki/IOS_(firmware)#IOS) and was thinking that maybe a section with a description of the various IOSs and their versions might be good to add to this. At least it would be a starting point for a "best practices" and could be useful for current/future developers.

 

[mike333]

At least it would be a starting point for a "best practices" and could be useful for current/future developers.

HB community progressively shift towards practice:
- update to latest HBC
- launch wii update
- never look back

In above scenario there is no such thing as "cool" IOS version for IOSes

 

[gamecaptor]

I just finished up the list of Wii IOSes. I pulled the info off Dop-Mii v13. I'm looking into putting this info into Wikipedia:
http://cid-a21e1c8f1f16c524.office.live.co...p;groupUpsell=0

Hey Mike333 (or anyone else), on the subject of IOSes less than 200, so none of the IOSes should have any patches on them. So the ideal setup would look like this (assuming you are on 4.3):
BC v6
MIOS v10
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 525): No Patches
IOS13 (rev 1031): No Patches
IOS14 (rev 1031): No Patches
IOS15 (rev 1031): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1031): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1038): No Patches
IOS22 (rev 1293): No Patches
IOS28 (rev 1806): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3607): No Patches
IOS33 (rev 3607): No Patches
IOS34 (rev 3607): No Patches
IOS35 (rev 3607): No Patches
IOS36 (rev 3607): No Patches
IOS37 (rev 5662): No Patches
IOS38 (rev 4123): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS53 (rev 5662): No Patches
IOS55 (rev 5406): No Patches
IOS56 (rev 5661): No Patches
IOS57 (rev 5918): No Patches
IOS58 (rev 6175): No Patches
IOS60 (rev 6400): Stub
IOS61 (rev 5661): No Patches
IOS70 (rev 6687): No Patches
IOS80 (rev 6943): No Patches

 

[mike333]

Hey Mike333 (or anyone else), on the subject of IOSes less than 200, so none of the IOSes should have any patches on them. So the ideal setup would look like this (assuming you are on 4.3):
[...]
IOS70 (rev 6687): No Patches
[...]

I don't think so:
http://wiibrew.org/wiki/IOS_History

Just Stop now. You will brick wii by mistake.

 

[gamecaptor]

aye! That is exactly what I was looking to do. Clearly didn't look hard enough

Thanks mike333.

 

[Arm the Homeless]

Hey Mike333 (or anyone else), on the subject of IOSes less than 200, so none of the IOSes should have any patches on them. So the ideal setup would look like this (assuming you are on 4.3):
[...]
IOS70 (rev 6687): No Patches
[...]

I don't think so:
http://wiibrew.org/wiki/IOS_History

Just Stop now. You will brick wii by mistake.

He's on 4.3, he doesn't need IOS70.

 

[mike333]

Hey Mike333 (or anyone else), on the subject of IOSes less than 200, so none of the IOSes should have any patches on them. So the ideal setup would look like this (assuming you are on 4.3):
[...]
IOS70 (rev 6687): No Patches
[...]

I don't think so:
http://wiibrew.org/wiki/IOS_History

Just Stop now. You will brick wii by mistake.

He's on 4.3, he doesn't need IOS70.

I have never said otherwise.

 

[gamecaptor]

Ok mike333, believe it or not, I am paying attention to everything that you are telling me. With that said, I did a NAND restore back defaults (I’m no expert with the Wii, but I am smart enough to have BootMii and Priiloader installed and take NAND backups often

So I started with a clean slate and a sandbox to play with. I attempted to follow the instructions from your signature, but the IOS236 would keep crashing when I would try and install it, so I had to go a more traditional route; ignoring anything other then what I think is absolutely needed.

Here is my sysCheck. Do you have any recommendations for me with this setup?

sysCheck v2.0 by Double_A
...runs on IOS61 (rev 5405).

Region: NTSC-U
System Menu 4.2 (v-2145571844)
Hollywood v0x21
Console ID: 133235344
Boot2 v4

Found 57 titles.
Found 37 IOS on this console. 10 of them are stub.

IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 778): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 269): No Patches
IOS13 (rev 273): No Patches
IOS14 (rev 520): No Patches
IOS15 (rev 1031): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 775): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 782): No Patches
IOS22 (rev 1037): No Patches
IOS28 (rev 1550): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3349): No Patches
IOS33 (rev 3091): No Patches
IOS34 (rev 3348): No Patches
IOS35 (rev 3349): No Patches
IOS36 (rev 3351): Trucha Bug ES Identify NAND Access
IOS37 (rev 3869): No Patches
IOS38 (rev 3867): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS53 (rev 5406): No Patches
IOS55 (rev 5406): No Patches
IOS56 (rev 5405): No Patches
IOS57 (rev 5661): No Patches
IOS60 (rev 6400): Stub
IOS61 (rev 5405): No Patches
IOS70 (rev 6687): No Patches
IOS222 (rev 65535): Trucha Bug ES Identify NAND Access USB 2.0 [Base 38]
IOS223 (rev 65535): Trucha Bug NAND Access USB 2.0 [Base 32]
IOS249 (rev 20): Trucha Bug NAND Access USB 2.0 [Base 57]
IOS250 (rev 65535): Trucha Bug NAND Access USB 2.0 [Base 38]
IOS254 (rev 65281): BootMii
BC v6
MIOS v10