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

[TheLiNkMan]

@FIX94:
Thanks a lot, i'll wait then

@davebaol:
Sorry

, i didn't know that about alt.dols. Thanks for reply

.

 

[TrapperKeeperX]

I tested on my FAT32 USB Loader

Results For Metroid Games

Metroid Prime 1 New Play Control NTSC-J Works Perfectly with d2x v6beta1 IOS 56 & d2x v6beta1 IOS 38

Metroid Prime 2 Dark Echoes New Play Control NTSC-J Works Partially But It won't Load Game & Multilayer with d2x v6beta1 IOS 56,d2x v6beta1 IOS 38, d2x v6beta1 IOS 37

Metroid Prime Trilogy NTSC-U Shows Wii Strap info then Black Screen on IOS 56, on Wii Strap info then Metroid Prime Trilogy Now Loading. then Black Screen IOS 38 & IOS 37 with d2x v6beta1 IOS 56,d2x v6beta1 IOS 38,d2x v6beta1 IOS 37

I used Block IOS Reload on these games Metroid Prime 1 New Play Control NTSC-J works perfectly. Then Metroid Prime 2 Dark Echoes New Play Control NTSC-J works but it won't load the Game & Multilayer, and Metroid Prime Trilogy NTSC-U won't boot the game.

This is my report on FAT32 USB Loader. Hopefully this issue will be fixed in beta2 or final.

I recommend you check your dumps. MPT works perfectly here with base 56. Just like the retail game.

I've re-dumped Metroid Prime Trilogy it works now and I also re-dumpe Metroid Prime 2 Dark Echoes New Play Control and it works aswell Only Multilayer Mode Thanks Hielkenator!

 

[dexter222]

@davebaol

I tested with cfg v69a6 as requested. It crashed with the following:

 

[FIX94]

@FIX94:
Thanks a lot, i'll wait then

Oggzee said that he will probably add the new identification tomorrow, then you will never need to wait again

 

[anttaz]

Help Please,

So using this method and modmii how do i make cIOS247[37]d2x5 and cIOS248[56]d2x5?

I managed to make cIOS250[57]-v21d2x5.wad and cIOS249[38]-v21d2x5.wad no problems

In fact using modmiis advanced feature all i manged to make was cIOS249[37]-v21d2x5slot247.wad and cIOS249[56]-v21d2x5slot248.wad but dont think this is correct method?

 

[NutNut]

Actually, everything is identical except the content 0000000.app wich is different between base and between version of cIOS

Ah makes sense. Well in the interest of learning I guess, how does that get patched?

I don't understand if you want to know "how" (with which tool) content 00000000.app is patched or "where I can find the right patch to put in the ciosmap.xml" so I will answer to both questions.

When you build cIOS with Modmii, it create content 00000000.app with "normal patches" + "new cIOS identification method". Then, it packs the others contents into wad file.

In order to know how to well patch the cIOS to integrate the identification method we have to compare decrypted contents.
So extract content from the cIOS wad file with ShowMiiWads and take the 00000000.app then download the base IOS with NUSD (tick the case decrypt content). The file 00000000.app is only 1ko size so the corresponding content from the base is the only one which is also 1ko size.

Now you have 2 .app file, one from the base IOS (original) and the other from the cIOS well patched by ModMii.
To reveal differences you just have to use command line in cmd.exe (Windows)
FC b/ "path to base IOS content" "path to 00000000.app"

Now you can write the patch "balise" with offset/originalbytes/newbytes

KEEP IN MIND THAT EACH 00000000.app IS DIFFERENT !! So if you need patch for another base IOS don't forget to change the cIOS and extract its proper 00000000.app

Everything else you can copy/past from older version because identification method is just in this file.

I hope you understand, french people are bad at english, aren't they ?

 

[XFlak]

FYI, check out the spoiler in my post HERE for a list of which content is the 00000000.app

also note that all the 00000000.app files are 64bytes, and it doesn't matter what content is in those bytes it will not interfere with the cIOS (as long as it is 64 bytes, no more, no less). So instead of patching the 0000000.app file, u can just create it from scratch according to the convention mentioned in the thread I just linked to (same convention ModMii uses)

Help Please,

So using this method and modmii how do i make cIOS247[37]d2x5 and cIOS248[56]d2x5?

I managed to make cIOS250[57]-v21d2x5.wad and cIOS249[38]-v21d2x5.wad no problems

In fact using modmiis advanced feature all i manged to make was cIOS249[37]-v21d2x5slot247.wad and cIOS249[56]-v21d2x5slot248.wad but dont think this is correct method?

That is correct

 

[NutNut]

FYI, check out the spoiler in my post HERE for a list of which content is the 00000000.app

also note that all the 00000000.app files are 64bytes, and it doesn't matter what content is in those bytes it will not interfere with the cIOS (as long as it is 64 bytes, no more, no less). So instead of patching the 0000000.app file, u can just create it from scratch according to the convention mentioned in the thread I just linked to (same convention ModMii uses)

We don't patch directly 00000000.app, we create it by patching the corresponding original content.
I don't understand well, you mean each 00000000.app just contain the md5 ?

Edit: I don't have the source code under eyes right now, i'm on iPhone but i think you mean the 00000000.app Start with md5 @ offset 0x00 right ?

 

[davebaol]

Great!
I just realized that now this topic is stickied.

 

[anttaz]

FYI, check out the spoiler in my post HERE for a list of which content is the 00000000.app

also note that all the 00000000.app files are 64bytes, and it doesn't matter what content is in those bytes it will not interfere with the cIOS (as long as it is 64 bytes, no more, no less). So instead of patching the 0000000.app file, u can just create it from scratch according to the convention mentioned in the thread I just linked to (same convention ModMii uses)

Help Please,

So using this method and modmii how do i make cIOS247[37]d2x5 and cIOS248[56]d2x5?

I managed to make cIOS250[57]-v21d2x5.wad and cIOS249[38]-v21d2x5.wad no problems

In fact using modmiis advanced feature all i manged to make was cIOS249[37]-v21d2x5slot247.wad and cIOS249[56]-v21d2x5slot248.wad but dont think this is correct method?

That is correct

So cIOS249[37]-v21d2x5slot247.wad and cIOS249[56]-v21d2x5slot248.wad are infact cIOS247[37]d2x5 and cIOS248[56]d2x5? I did not think it would of been the case, but was all I could make using modmii's advanced featue also when downloaded as a ciso pack they never look like them outputs I achieved

 

[kylster]

So it was mentioned that ripping games was broken since d2x v4. Is this only if CFG uses IOS249 to boot or can you just use IOS222 instead when loading CFG?

 

[Hielkenator]

So it was mentioned that ripping games was broken since d2x v4. Is this only if CFG uses IOS249 to boot or can you just use IOS222 instead when loading CFG?

No problem here ripping to FAT 32.

 

[cambric]

So cIOS249[37]-v21d2x5slot247.wad and cIOS249[56]-v21d2x5slot248.wad are infact cIOS247[37]d2x5 and cIOS248[56]d2x5? I did not think it would of been the case, but was all I could make using modmii's advanced featue also when downloaded as a ciso pack they never look like them outputs I achieved

Hi Davebaol,

this is example of why you should change the naming of the cIOS avoiding the use of the slot at the beginning (cIOS249 I mean)... people is getting confused...
cIOS249[37]-v21d2x5slot247.wad and cIOS247[37]d2x5 are not clear.... it does not sound like the same cIOS installed in different slots...
better be cIOS-d2x-v5-base37-slot247 since actually the cIOS is identified by just cIOS-d2x-v5, then the base and slot are chosen by the user...

 

[Hielkenator]

So cIOS249[37]-v21d2x5slot247.wad and cIOS249[56]-v21d2x5slot248.wad are infact cIOS247[37]d2x5 and cIOS248[56]d2x5? I did not think it would of been the case, but was all I could make using modmii's advanced featue also when downloaded as a ciso pack they never look like them outputs I achieved

Hi Davebaol,

this is example of why you should change the naming of the cIOS avoiding the use of the slot at the beginning (cIOS249 I mean)... people is getting confused...
cIOS249[37]-v21d2x5slot247.wad and cIOS247[37]d2x5 are not clear.... it does not sound like the same cIOS installed in different slots...
better be cIOS-d2x-v5-base37-slot247 since actually the cIOS is identified by just cIOS-d2x-v5, then the base and slot are chosen by the user...

This only occurs when building a CUSTOM d2x from modmii. regular users will have no problem indentifiing.

 

[cambric]

This only occurs when building a CUSTOM d2x from modmii. regular users will have no problem indentifiing.

I think the use of the term "regular" is not suitable...
users are free to install the cIOS in the slot they prefer...
the fact that a user choses a slot different from mine does not mean that he is not "regular"...
for example, I install the cIOS in slot 246, but I do not feel "not regular"...
moreover, why use the name cIOS249 if you can install it also in slot 247...

 

[Hielkenator]

This only occurs when building a CUSTOM d2x from modmii. regular users will have no problem indentifiing.

I do not like the use of the term "regular"...
users are free to install the cIOS in the slot they prefer...
the fact that a user choses a slot different from mine does not mean that he is not "regular"...
for example, I install the cIOS in slot 246, but I do not feel "not regular"...
moreover, why use the name cIOS249 if you can install it also in slot 247...

I agree with you about the naming. It's a bit akward.
I was only trying to point out it's a modmii isseu.
You pointed your post to davebaol.

Also if you want to give your custom build cios a different name you can always rename afterwards yourself.
I really do not see why it is confusing.
And to say something about "regular".
You were not referring to the Installation"itself, but to the naming format.
People can decide themself in what slot they want to install.

But , why are you using slot 246 for this cios?
I can imagine it's for testing purposes, but that would defeat your initial post, would'nt it? ( being regular )

You'de only need 2 cios slots occupied with d2x. One with base 56 and one with base 57.
This will give you 100% Compatibilty as for now.
No matter how it's named. Or what slot you want to use.

 

[XFlak]

FYI, check out the spoiler in my post HERE for a list of which content is the 00000000.app

also note that all the 00000000.app files are 64bytes, and it doesn't matter what content is in those bytes it will not interfere with the cIOS (as long as it is 64 bytes, no more, no less). So instead of patching the 0000000.app file, u can just create it from scratch according to the convention mentioned in the thread I just linked to (same convention ModMii uses)
We don't patch directly 00000000.app, we create it by patching the corresponding original content.
I don't understand well, you mean each 00000000.app just contain the md5 ?

Edit: I don't have the source code under eyes right now, i'm on iPhone but i think you mean the 00000000.app Start with md5 @ offset 0x00 right ?


no, the 000000.app contains the following:

CODE

typedef struct _iosinfo_t {
u32 magicword; //0x1ee7c105
u32 magicversion; // 1
u32 version; // Example: 5
u32 baseios; // 56
char name[0x10]; // Example: d2x
char versionstring[0x10]; // Example: alpha2
} __attribute__((packed)) iosinfo_t;

"d2x56v5alpha2"

In a hexedit it would look like this:
1EE7C105 00000001 00000005 00000038
64327800 00000000 00000000 00000000
61706C68 61320000 00000000 00000000

and:
.çÁ............8
d2x.............
alpha2..........

 

[oggzee]

@davebaol

I tested with cfg v69a6 as requested. It crashed with the following:

Spoiler

Uh that's weird:

Spoiler

c_default_exceptionhandler
??:0
c_default_exceptionhandler
??:0
default_exceptionhandler
??:0
c_default_exceptionhandler
??:0
default_exceptionhandler
??:0
c_default_exceptionhandler
??:0
default_exceptionhandler
??:0
c_default_exceptionhandler
??:0
default_exceptionhandler
??:0

unfortunately it doesn't help much

Do you have a usb gecko?
You could enable debug_gecko=1 and then post the log from the gecko... that might give more info.

 

[cambric]

But , why are you using slot 246 for this cios?
I can imagine it's for testing purposes, but that would defeat your initial post, would'nt it? ( being regular )
You'de only need 2 cios slots occupied with d2x. One with base 56 and one with base 57.
This will give you 100% Compatibilty as for now.
No matter how it's named. Or what slot you want to use.

Thanks for your answer,

the discussion on the denomination to be used for this cIOS is something started days ago... in this light you can understand why I addressed my comment to davebaol.
Of course, .wad for d2x cIOS are created by ModMii, hence in the specific the comment goes to xflak too...
obviously, renaming a file on a PC is very easy... my comments are aimed only to have more clear stuff in the future (following the previous discussion), expecially for people not deeply involved in the softmod wii world...

I use IOS236, cIOS d2x base56 in slot246 and base 57 in slot247... two cIOS like you...
Why in slots 246-247? in order to separate the softmod and the nintendo system....
In this way there is no intersection between the slots used by the softmod and the IOS by Nintendo (stub or not)... as a consequence, I have no problems with system updates or something like that... this is very useful expecially when you softmod your friends' wii...

thanks again

 

[Hielkenator]

But , why are you using slot 246 for this cios?
I can imagine it's for testing purposes, but that would defeat your initial post, would'nt it? ( being regular )
You'de only need 2 cios slots occupied with d2x. One with base 56 and one with base 57.
This will give you 100% Compatibilty as for now.
No matter how it's named. Or what slot you want to use.

Thanks for your answer,

the discussion on the denomination to be used for this cIOS is something started days ago... in this light you can understand why I addressed my comment to davebaol.
Of course, .wad for d2x cIOS are created by ModMii, hence in the specific the comment goes to xflak too...
obviously, renaming a file on a PC is very easy... my comments are aimed only to have more clear stuff in the future (following the previous discussion), expecially for people not deeply involved in the softmod wii world...

I use IOS236, cIOS d2x base56 in slot246 and base 57 in slot247... two cIOS like you...
Why in slots 246-247? in order to separate the softmod and the nintendo system....
In this way there is no intersection between the slots used by the softmod and the IOS by Nintendo (stub or not)... as a consequence, I have no problems with system updates or something like that... this is very useful expecially when you softmod your friends' wii...

thanks again

Cool, I see.
But I thought the Cios made with modmii are update save? Aren't the Versions maxed out ?
Also there's priiloader, to prevent accidentally updating.

And you can't look in the future, those slots you mention could just as well be patched.
So why do it the difficult way, I wonder.

Well everybody has his way, I suppose.