Hacking System Menu questions/thoughts

[WiiPower]

I didn't read everything, so: "What the h... are you doing?" You want to overwrite your system menu with a patched one? If you do, you should ask Forsaekn how he bricked his Wiis, i guess something unexpected happens if you overwrite your system menu. If you really want to patch the system menu to recognize backups, why don't you put the cIOS36rev7 dip into IOS30?

I recommend NOBODY to do this as it will most likely brick your Wii(if you really want to do this, read everything i have written and understand it!):
To put the backup dip into IOS30, you need to dump an installed cIOS36rev7 from NAND. 00000001.app should be the dip module in both your dumped cIOS36 and in IOS30. In theory you only have to replace the one in IOS30 with the one from the cIOS. The problem is that inside the tmd or the ticket(or both) is some data stored which doesn't match with the data from your new 00000001.app. If you don't generate a new tmd and ticket, in the best case this cIOS30 won't install. In the worst case it will install, but don't work. Maybe you can change the installation location to another slot and test your cIOS30 with the rebooter before you overwrite your IOS30. A big problem will be: The system menu won't accept a fake signed IOS, so you have to patch trucha inside the system menu. Where the next problem could start: Does whatever starts the system menu, accept a fake signed system menu? Even if you solve all of this, i guess there's something i have overseen and this will brick your wii if you try it, so don't blame me.

 

[IronMask]

So the action is not stored into the RAM after enabling it?? So I am screwed? Just when it finished dumping

What next!? Any ideas?

 

[WiiPower]

Oh and i have to add: If something is wrong with the system menu or the IOS used by it (IOS30 for 3.2, IOS50 for 3.4), the Wii is really bricked, and starfall doesn't help.

 

[ether2802]

We have only patched the SysMenu to be readen by IOS249, it would be the same if we add the DIP to IOS30, the games are going to still want to be readen by their corresponding IOS, we need to incorporate what the rebooter does, into the DIP, before patching it into any IOS...!!!

BTW: 1000 yay..!!

 

[IronMask]

So this is basically an impossible path to complete unless someone else decides they know exactly what WiiPower is saying and not afraid of the brick chance... I guess I will wait another week or so until the almighty Gurus figure something out with cSM or something...

It was worth a shot... I guess this idea wouldn't be so bad for if all you want was backups to play on a novices Wii that you softmodded. With the patched 249 .isos to go along with it... Move the homebrew somewhere and that way...all the same region games they have will play through the disc channel so they won't be calling me back saying that these games don't load in the disc channel because they didn't know what the backup channel even was....blah blah

Thanks for helping Nicksasa and WiiPower... I guess I am still a kamakaze wii warrior.. with a patched menu still on 249...

 

[WiiCrazy]

I didn't read everything, so: "What the h... are you doing?" You want to overwrite your system menu with a patched one? If you do, you should ask Forsaekn how he bricked his Wiis, i guess something unexpected happens if you overwrite your system menu. If you really want to patch the system menu to recognize backups, why don't you put the cIOS36rev7 dip into IOS30?

I recommend NOBODY to do this as it will most likely brick your Wii(if you really want to do this, read everything i have written and understand it!):
To put the backup dip into IOS30, you need to dump an installed cIOS36rev7 from NAND. 00000001.app should be the dip module in both your dumped cIOS36 and in IOS30. In theory you only have to replace the one in IOS30 with the one from the cIOS. The problem is that inside the tmd or the ticket(or both) is some data stored which doesn't match with the data from your new 00000001.app. If you don't generate a new tmd and ticket, in the best case this cIOS30 won't install. In the worst case it will install, but don't work. Maybe you can change the installation location to another slot and test your cIOS30 with the rebooter before you overwrite your IOS30. A big problem will be: The system menu won't accept a fake signed IOS, so you have to patch trucha inside the system menu. Where the next problem could start: Does whatever starts the system menu, accept a fake signed system menu? Even if you solve all of this, i guess there's something i have overseen and this will brick your wii if you try it, so don't blame me.

On a 3.2 system menu, you just change the tmd of the system menu,
1. unpacking the menu wad
2. changing the boot index in the tmd to the custom ios installed
3. repacking the wad
4. installing over the system menu

1,2,3 could be simplified by ios patcher tool previously mentioned... so there is no big catch here... still this should only be tried by those who knows what goes in and out of their wii...

 

[ether2802]

IOS30 doesn't pack with a 01.app:

 

[WiiPower]

IOS30 doesn't pack with a 01.app:

Then look for a .app with this size, but maybe the dip is totally different. It seems you don't need this, i just posted my thought about this idea.

 

[ether2802]

On a 3.2 system menu, you just change the tmd of the system menu,
1. unpacking the menu wad
2. changing the boot index in the tmd to the custom ios installed
3. repacking the wad
4. installing over the system menu

1,2,3 could be simplified by ios patcher tool previously mentioned... so there is no big catch here... still this should only be tried by those who knows what goes in and out of their wii...

We have already patched the SysMenu.wad to IOS249 and installed it succesfully without brick, but when you start a game in the Disc Channel, the game recall his corresponding IOS, we need to make the Disc Channel force them to be readen by IOS249, all of the DVD's, the original copies can be read like normal, but the DVD's has to be forced to IOS249..!!!

 

[WiiPower]

On a 3.2 system menu, you just change the tmd of the system menu,
1. unpacking the menu wad
2. changing the boot index in the tmd to the custom ios installed
3. repacking the wad
4. installing over the system menu

1,2,3 could be simplified by ios patcher tool previously mentioned... so there is no big catch here... still this should only be tried by those who knows what goes in and out of their wii...

We have already patched the SysMenu.wad to IOS249 and installed it succesfully without brick, but when you start a game in the Disc Channel, the game recall his corresponding IOS, we need to make the Disc Channel force them to be readen by IOS249, all of the DVD's, the original copies can be read like normal, but the DVD's has to be forced to IOS249..!!!

If you mess around with your system you could overwrite all normal game IOS with the backup cIOS. This isn't nice, but it should work.

 

[ether2802]

yes we tought already that, but you are the only coder capable of modify Multi_cIOS installer..!!

 

[WiiPower]

yes we tought already that, but you are the only coder capable of modify Multi_cIOS installer..!!

You are kidding, right? You tell me you can't change a 33 in the source to 9 and recompile it?

 

[WiiBlaster]

For those that got errors when re-packing the IOS with app.1 file
well with good news i have been successful into patching a IOS30 into a CIOSIOS30 and have fully tested it on a Auto Wad Manager patched to IOS30

By using a certain set of packing tools i was able to rip the App1 file out and inject it into the IOS30 and made it a CIOS, I first took the Wad Manager auto and tried to play it with the Org IOS30 and it didn't work, but after i patched the IOS30 The disc was able to play

 

[ether2802]

I actually looked for it, but couldn't find it, I was too tired last night, and besides my devkit isn't compiling I don't know why..!!

 

[WiiPower]

I actually looked for it, but couldn't find it, I was too tired last night, and besides my devkit isn't compiling I don't know why..!!

You should update it if you haven't done it lately. Just search the 33 limitation in the source, it's not that hard to find.

 

[WiiBlaster]

with these set of packing tools you should be able to patch every IOS in the wii, and not worry about patching the system menu, Just patch the IOS's and thats it, Should be able to play all of your Wii 1:1 without patching to IOS249, I will upload the set of tools I have for people to try out, I dont remember exactly were i got them so i just re-load them, I will remove the common.key first so, I can give the link if anyone wants to test

And if you want to test out the CIOS30 just PM me, with this you shouldn't have to patch the system menu wad just install this IOS30 you will need to be on system 3.2 though, But you will still have to patch the wii iso to ISO 249 until I finish Patching the rest of the IOS's if i can that is


Edit Ok here is the set of Tools

removed

These are common Packing tools nothing special, Just Unpack your CIOS rev 7 wad and RIP out the app.1 file and then UNpack your IOS and Inject the app.1 file into it and then Re-pack, your IOS will now be a CIOS I didn't get any errors when re-packing the IOS, and i've already installed and tested it out on a Wad Manager ISO patched to IOS30 I've only tested this on IOS30

 

[ether2802]

but wait did you patch the IOS'es to IOS249 or only added the 01.app to all of them???

 

[WiiBlaster]

I only added the app1 file and re-packed, Its acting just has a CIOS would, i've already test it on, a Autoboot wad manger iso patched to IOS30, which with the Org IOS30 wont play but with doing the Inject app1 file and re-packing it and installing it its now able to work, So i'm guessing it worked

 

[FGOD]

could you try on 1:1 backups and original games?

 

[WiiBlaster]

Ok i can do that, i have a unpatched Wii Music Game does anyone know what IOS if runs off of

Iron Mask is going to test out my CIOS30, So you all will know it works or not