Hacking cIOSX rev21d2x: Yet Another Hot Fix!!!!

[WiiPower]

@XFlak and dragbe:
When talking to davebaol about the easy cIOS base IOS identification, i realized that i was talking to the wrong person. He "only" provides the ios modules, i want the cIOS identifaction in the tmd, and the tmd is created by the installer.

How about an extra file in the folder with the .app files? Some human readable file(.xml?) with all info you want to provide. The installer(or ModMii) would take that + the base IOS + the install slot and write the info into the tmd starting at offset 0x20. And the info in the tmd could be in some structure like this:
typedef struct _iosinfo {
char magicword[0x10];
char shortname[0x10];
char longname[0x20];
char developer[0x20];
u32 version;
char versionstring[0x10]; // for betas
u32 iosbase;
u32 iosslot; // useless...
char builddate[8];
char reserved[40];
} __attribute__((packed)) iosinfo;

This way a loader could read the tmd and tell exactly what cIOS it is and wouldn't need to mess around with hashes to identify cIOSes.

Before you start writing code for this, let's discuss it 1st, i would want the 1st version to be final.

 

[Dr. Clipper]

@XFlak and dragbe:
When talking to davebaol about the easy cIOS base IOS identification, i realized that i was talking to the wrong person. He "only" provides the ios modules, i want the cIOS identifaction in the tmd, and the tmd is created by the installer.

How about an extra file in the folder with the .app files? Some human readable file(.xml?) with all info you want to provide. The installer(or ModMii) would take that + the base IOS + the install slot and write the info into the tmd starting at offset 0x20. And the info in the tmd could be in some structure like this:
typedef struct _iosinfo {
char magicword[0x10];
char shortname[0x10];
char longname[0x20];
char developer[0x20];
u32 version;
char versionstring[0x10]; // for betas
u32 iosbase;
u32 iosslot; // useless...
} __attribute__((packed)) iosinfo;

This way a loader could read the tmd and tell exactly what cIOS it is and wouldn't need to mess around with hashes to identify cIOSes.

Before you start writing code for this, let's discuss it 1st, i would want the 1st version to be final.

I'm all for something like this. It's silly that we have to get a new set of hashes each time when doing IOS detection. Some of the fields are a bit long, though. I would suggest a u32 for magicword, just one name is probably enough, especially if we keep the developer field. Basically, we want all the information that could be useful, but we shouldn't waste space where we don't need to. Keeping it simple and compact might be a better way to go.

Edit: although we should probably also add a reserved field to the end just so that we have room to expand if we think of something else to add at a later date.

 

[bnm81002]

@bnm81002
When do you get exactly the code dump?
Also, post a syscheck report. Maybe your system config is not fully supported by the installer for some reason.

when it says reloading IOS 236 then it code dumps,
here's my syscheck report, thanks

sysCheck GX v1.0.0 by Erik Spyder

sysCheck GX is running under IOS58 (rev 6175).

Console ID: 42871353.
Region: NTSC-U.
Hollywood v0x11.
Boot2 v2.
System Menu v289 (3.2U).
BC v2.
MIOS v5.
Blocks the GameCube Action Replay.

Found 375 titles.
Found 34 IOS on this console.
No IOS Stub on this console!

Priiloader is installed.


IOS 4 (rev 3): Trucha Bug, ES_Identify, FLASH Access, NAND Access
IOS 9 (rev 778): Trucha Bug
IOS 11 (rev 10): Trucha Bug, ES_Identify, FLASH Access, NAND Access
IOS 12 (rev 269): Trucha Bug
IOS 13 (rev 273): Trucha Bug
IOS 14 (rev 520): Trucha Bug
IOS 15 (rev 523): Trucha Bug
IOS 17 (rev 775): Trucha Bug
IOS 20 (rev 12): Trucha Bug, ES_Identify, FLASH Access, NAND Access
IOS 21 (rev 782): Trucha Bug
IOS 22 (rev 1037): Trucha Bug
IOS 28 (rev 1550): Trucha Bug
IOS 30 (rev 1040): Trucha Bug, ES_Identify, FLASH Access, NAND Access
IOS 31 (rev 3349): Trucha Bug
IOS 33 (rev 3091): Trucha Bug
IOS 34 (rev 3348): Trucha Bug
IOS 35 (rev 3349): Trucha Bug
IOS 36 (rev 3351): Trucha Bug, ES_Identify, NAND Access
IOS 37 (rev 3869): Trucha Bug
IOS 38 (rev 3867): Trucha Bug
IOS 53 (rev 5406): Trucha Bug
IOS 55 (rev 5663)
IOS 56 (rev 5662)
IOS 57 (rev 5661): Trucha Bug
IOS 58 (rev 6175): USB 2.0
IOS 61 (rev 5405)
IOS202 (rev 4): Trucha Bug, ES_Identify, NAND Access, USB 2.0
IOS222 (rev 4): Trucha Bug, ES_Identify, NAND Access, USB 2.0
IOS223 (rev 4): Trucha Bug, ES_Identify, NAND Access, USB 2.0
IOS224 (rev 65535): Trucha Bug, ES_Identify, NAND Access, USB 2.0
IOS236 (rev 65535): Trucha Bug, ES_Identify, NAND Access
IOS249 (rev 20): Trucha Bug, ES_Identify, NAND Access
IOS250 (rev 65535): Trucha Bug, ES_Identify, NAND Access
IOS254 (rev 65281)

Report generated on 2011-05-20.

for davebaol

 

[davebaol]

Don't know. Ask dragbe.

 

[dragbe]

I'm having problems trying to install the d2x cIOS using the d2x Installer 1.1, I get a code dump, I used IOS 236 installed from ModMii as the IOS, it reads as follows, help please, thanks?
Do you have devices (GC memory card, USB devices,...) plugged into your wii during d2x cios installer running ?
QUOTE(WiiPower @ May 21 2011, 06:45 PM) This way a loader could read the tmd and tell exactly what cIOS it is and wouldn't need to mess around with hashes to identify cIOSes.
Before you start writing code for this, let's discuss it 1st, i would want the 1st version to be final.

I agree with Dr. Clipper. Thus, in summary
typedef struct _iosinfo {
char magicword[0x10]; //OK with an integer type
char shortname[0x10]; //OK
char longname[0x20]; //useless
char developer[0x20]; //not necessarily useful
u32 version; //internal version can normally be determined on the fly
char versionstring[0x10]; //OK to identify the d2x cIOS (beta included)
u32 iosbase; //OK
u32 iosslot; //useless
char builddate[8]; //not necessarily useful
char reserved[40]; //...
} __attribute__((packed)) iosinfo;

 

[WiiPower]

So we could agree on this:

typedef struct _iosinfo {
u32 magicword;
char name[0x10]; //OK
u32 version; //internal version can normally be determined on the fly
char versionstring[0x10]; //OK to identify the d2x cIOS (beta included)
u32 iosbase; //OK
} __attribute__((packed)) iosinfo;

So use what as magic word?

Example:
magicword = 0x........
name = "d2x"
version = 5
versionstring = "beta1"
iosbase = 56

For the next beta with usb(wbfs) ios reload block?

 

[IceIceBird]

For the next beta with usb(wbfs) ios reload block?

I like that little hint about the next beta version

 

[dragbe]

OK for the version field, I had not understood it in this way.
magic word value=sizeof(magicword) + sizeof(name) + sizeof(version) + sizeof(versionstring) + sizeof(iosbase) for example

 

[R2-D2199]

@WiiPower:

I think that the version of the base IOS could be added.

@davebaol:

Great work on d2x cIOS.

One question:
Is the problem with the Yourshape CAM a cIOS problem?: http://gbatemp.net/t199353-your-shape-whit-cam-on-usb-loader
If it's a cIOS problem and if it's not too much work, could you fix that?

@dragbe:

Great work on the installer.

I have added the hermes cIOS to your installer.
You can create a "multi cIOS installer".
Here is the sourcecode: http://www.mediafire.com/?z4v23n1eddzztt1

I have made changes in the patchmii_core.c and CIOSMAPS.xml.

 

[WiiPower]

@WiiPower:

I think that the version of the base IOS could be added.
[...]

Right, i consider this useful. Could be displayed in those syscheck apps.

So right now it looks like this:

typedef struct _iosinfo {
u32 magicword;
char name[0x10];
u32 version; 
char versionstring[0x10]; // for betas
u32 baseios;
u32 baseiosversion;
} __attribute__((packed)) iosinfo;

And i would like something like magicword = 0xDeadBeef or similar


QUOTE(R2-D2199 @ May 22 2011, 02:09 PM) [...]
@davebaol:

Great work on d2x cIOS.

One question:
Is the problem with the Yourshape CAM a cIOS problem?: http://gbatemp.net/t199353-your-shape-whit-cam-on-usb-loader
If it's a cIOS problem and if it's not too much work, could you fix that?
[...]

Did you try d2x with IOS58 as base? Only that is supposed to work if any.

 

[digdug3]

@davebaol:
Could you add a USB dismount function to the CIOS so all harddrives will go to sleep properly when you shut down?

 

[R2-D2199]

[...]
@davebaol:

Great work on d2x cIOS.

One question:
Is the problem with the Yourshape CAM a cIOS problem?: http://gbatemp.net/t199353-your-shape-whit-cam-on-usb-loader
If it's a cIOS problem and if it's not too much work, could you fix that?
[...]

Did you try d2x with IOS58 as base? Only that is supposed to work if any.

I have tried it with cIOS58 d2xv4 and the xbox usb cam, the game gives me an error message that there is a problem with the cam.

 

[WiiPower]

Is the game supposed to work the xbox cam???

 

[R2-D2199]

Here said someone that the xbox cam is working:
http://gbatemp.net/t199353-your-shape-whit...t&p=2491545

And in the german board "gulli board" we tested this: http://board.gulli.com/thread/1495306-kame...=1#post12376536

 

[dtheo]

Hello,
I have an issue with the latest d2x because the disks I attach to wii are not recognized ( I have one genuine seagate freeagent desktop 1TB and one made from a 80GB Samsung HDD).
I have downloaded the last d2xv4 using modmii4.55 to use in 249 (base 56 and 58) and 250 (base 57). After update of 249 with either base - 56 or 58 - the disks are not seen in the system[/u].
All my programs seem to not get access to the disks attached to usb: USBloader GX, wiixplorer, wiimc.

After restoring the old CIOS 249 (d2xv3 , base 58) everything works again.

Keep the great work.
Dragos

 

[WiiPower]

Ok, NeoGamma's code for the cIOS identification is done.

typedef struct _iosinfo_t {
ÂÂÂÂu32 magicword;
ÂÂÂÂchar name[0x10];
ÂÂÂÂu32 version;
ÂÂÂÂchar versionstring[0x10]; // for betas
ÂÂÂÂu32 baseios;
ÂÂÂÂu32 baseiosversion;
} __attribute__((packed)) iosinfo_t;

[...]
ÂÂÂÂÂÂÂÂiosinfo = (iosinfo_t *)((u32)TMD+0x20);
ÂÂÂÂÂÂÂÂif (iosinfo->magicword == 0xbeeeeeef)
ÂÂÂÂÂÂÂÂ{
ÂÂÂÂÂÂÂÂÂÂÂÂsprintf(info, "%s%uv%u%s (%u)", iosinfo->name, iosinfo->baseios, iosinfo->version, iosinfo->versionstring, CIOS_VERSION);ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
ÂÂÂÂÂÂÂÂÂÂÂÂ// Example: "d2x56v5beta1 (249)"
ÂÂÂÂÂÂÂÂ} else
[...]

Just writing into the tmd at offset 0x20 seems to work fine as expected. The struct and the magic word are still not final, if anybody has any suggestions, please tell. Oh and i didn't sign the tmd afterwards.

So now we need to put that info into the cIOS. Easiest way would be a .txt with a line for each variable and the installer/ModMii reads it and writes the info into the tmd.

 

[pplucky]

So now we need to put that info into the cIOS. Easiest way would be a .txt with a line for each variable and the installer/ModMii reads it and writes the info into the tmd.

Does this mean that all the "old" cIOS will not be identified, only new ones built after these changes?

 

[WiiPower]

So now we need to put that info into the cIOS. Easiest way would be a .txt with a line for each variable and the installer/ModMii reads it and writes the info into the tmd.

Does this mean that all the "old" cIOS will not be identified, only new ones built after these changes?

This means that all new cIOS will be identified automatically without requiring an update of the loader. And the loader devs are free to use the old identification if there's no info found in the tmd. That is what NeoGamma will do btw.

 

[pplucky]

So now we need to put that info into the cIOS. Easiest way would be a .txt with a line for each variable and the installer/ModMii reads it and writes the info into the tmd.

Does this mean that all the "old" cIOS will not be identified, only new ones built after these changes?

This means that all new cIOS will be identified automatically without requiring an update of the loader. And the loader devs are free to use the old identification if there's no info found in the tmd. That is what NeoGamma will do btw.

OK, just wanted to confirm that. It makes sense to me...

 

[bnm81002]

I'm having problems trying to install the d2x cIOS using the d2x Installer 1.1, I get a code dump, I used IOS 236 installed from ModMii as the IOS, it reads as follows, help please, thanks?

Do you have devices (GC memory card, USB devices,...) plugged into your wii during d2x cios installer running ?

only my USB drive is connected, nothing else