|Initial||Unknown Repair Disc|
|Status||Private Corporate IOS|
IOS5 is a rare stub IOS present in some Wiis. No known functional version has ever been found, although it seems to be the first IOS with WiiConnect24 support, since the SDK refuses to initialize WiiConnect24 if the current IOS is less than or equal to 4 (IOS3 or IOS4) or is equal to 9 (IOS9). It is not known why this check does not include IOS254, although it is possible that IOS254 did not exist at the time.
v514 is not real; it is instead a copy of IOS21v514 that was posted online for unknown reasons, and may be found on Wiis bought from previous modders.
PatchMii's example also previously installed to this slot, since bushing claimed PatchMii installs to this slot, despite it actually installing into IOS254. The version installed by PatchMii is a copy of IOS37 with fakesigning and DVD video enabled.
It is not known whether the IOS5 stub was to target these hacks, or to prevent a functional version from being pirated the same way IOS16 was.
How to document this IOS
IOS5v65280 has currently not been analyzed due to its rarity.
Anybody who owns IOS5v65280 can document it by loading all files in /title/00000001/00000005/content/ onto their computer, in addition to /sys/uid.sys. There will most likely be two files: a title.tmd and a XXXXXXXX.app, where XXXXXXXX is some 8-digit hex number. If there are any other files (e.g. multiple .app files), please message with @Hallowiizer#1849 on Discord.
The XXXXXXXX.app should only be 64 bytes (if it is any other size, message @Hallowiizer#1849); running
xxd XXXXXXXX.app (or the Windows equivalent) should produce output in a similar format to the following:
00000000: 6669 726d 7761 7265 2e36 342e 3038 3038 firmware.64.0808 00000010: 3036 3131 3335 0000 0000 0000 0000 0000 061135.......... 00000020: 0000 0000 0000 0000 0000 0000 0102 0000 ................ 00000030: 7961 7375 682d 746f 4054 4f4e 4b41 5400 yasuh-to@TONKAT.
Pasting this output onto WiiBrew and referring to it as the "build file" is sufficient to document this; it can then be further processed by others.
title.tmd can be documented by downloading HallowTools and running
python hallowtools TMD title.tmd. This will print a report in a similar format to the following:
IOS11 Title ID: 00000001-0000000b Version: 256 System Version: 00000000-00000000 (Null 0) Index ID Type Size Hash 0 0000000a 0x1 64 93f38868e05f699c2dcb15eb39141fb61a22e7 1 0000000b 0x8001 46032 8c73829f8191852a647ca1bbdb23b235f85cba8f 2 0000000c 0x8001 116872 37ee170e9525fb0c273db64190ec5f5983a9a4
Paste the report onto this page as the "TMD info" and people can further analyze it from there.
Finally, to document uid.sys, run
python hallowtools UID uid.sys and paste the result on this page or in a DM to Hallowizer.
|Version||Signing bug?||/dev/flash access?||ES_Identify?||STM Release Exploit?||STM IOCTL overflow?||SDI register index bug?||Notes|
|v5||Yes||Yes||Yes||Yes||Yes||Yes||Never released; only known to exist because IOS11 is forked from here.|
|v6||Yes||Yes||Yes||Yes||Yes||Yes||Only known to exist because IOS11 through IOS22 have kernels built on 10/25/2006, but another version was built on 11/1/2006 as seen in MIOSv4.|
|v65280||No||No||No||N/A||N/A||N/A||Stub IOS. Not available on NUS.|