Hacking SignCheck marks EVERYTHING as Trucha after official 4.1 update

[kzch]

My Wii was 3.2U downgraded from 3.4U, with bootmii(boot2), HBC(on IOS51), cios38rev14(on IOS249) cios38rev13b(on IOS250), IOS222/223, IOS38/53/55/61 and new shopping channel, Softchip, usbloader GX, etc, installed. Yesterday, I decided to upgrade to 4.1U through official update. Before update, I did a bootmii nand backup, and ran signcheck to keep a record of my old IOS status. After upgrade to 4.1U thru nintendo, HBC stopped working. I had to reinstall HBC (on IOS61 now). Then I ran signcheck again.

To my surprise, all the IOSs are marked as Trucha bug enabled, even IOS60. It seems some low IOSs are removed (IOS11,12,15,16,20,21,30,50), most of the others are upgraded. What else do I need to do to get the wii fulled softmodded again?? I want to use usbloader gx most of the time, plus softchip.

Forgive me for my ignorance, since I am a little lost here. I also read about Waninkoko's 4.1 Firmware updater being recommended as a safer way of upgrading, while keeping all the IOSs at older Trucha bugged versions. But if Nintendo's official update could still keep the Trucha bug enabled while upgrading IOSs to higher versions, what is the purpose of the 4.1 Firmware updater?

This is the new signcheck file after 4.1U update thru nintendo:

IOS number "Trucha bug" "Flash access" "Boot2 access" "Usb2.0 IOS tree"
IOS250 (ver 65535) Enabled Disabled Disabled Enabled
IOS249 (ver 14) Enabled Disabled Disabled Enabled
IOS223 (ver 3) Enabled Enabled Disabled Disabled
IOS222 (ver 3) Enabled Enabled Disabled Disabled
IOS61 (ver 4890) Enabled Disabled Disabled Disabled
IOS60 (ver 6174) Enabled Disabled Disabled Disabled
IOS55 (ver 5149) Enabled Disabled Disabled Disabled
IOS53 (ver 5149) Enabled Disabled Disabled Disabled
IOS38 (ver 3610) Enabled Disabled Disabled Disabled
IOS37 (ver 3612) Enabled Disabled Disabled Disabled
IOS36 (ver 3094) Enabled Disabled Disabled Disabled
IOS35 (ver 3092) Enabled Disabled Disabled Disabled
IOS34 (ver 3091) Enabled Disabled Disabled Disabled
IOS33 (ver 2834) Enabled Disabled Disabled Disabled
IOS31 (ver 3092) Enabled Disabled Disabled Disabled
IOS28 (ver 1293) Enabled Disabled Disabled Disabled
IOS22 (ver 1293) Enabled Disabled Disabled Disabled
IOS17 (ver 1293) Enabled Disabled Disabled Disabled
IOS14 (ver 1293) Enabled Disabled Disabled Disabled
IOS13 (ver 1293) Enabled Disabled Disabled Disabled

This is the signcheck file for the 3.2U before update:

IOS number "Trucha bug" "Flash access" "Boot2 access" "Usb2.0 IOS tree"
IOS250 (ver 65535) Enabled Disabled Disabled Enabled
IOS249 (ver 14) Enabled Disabled Disabled Enabled
IOS223 (ver 3) Enabled Enabled Disabled Disabled
IOS222 (ver 3) Enabled Enabled Disabled Disabled
IOS61 (ver 4890) Enabled Disabled Disabled Disabled
IOS55 (ver 4633) Enabled Disabled Disabled Disabled
IOS53 (ver 4113) Enabled Disabled Disabled Disabled
IOS51 (ver 4633) Enabled Disabled Disabled Disabled
IOS50 (ver 4889) Enabled Disabled Disabled Disabled
IOS38 (ver 3610) Enabled Disabled Disabled Disabled
IOS37 (ver 2070) Disabled Disabled Disabled Disabled
IOS36 (ver 1042) Enabled Enabled Disabled Disabled
IOS35 (ver 1040) Enabled Enabled Disabled Disabled
IOS34 (ver 1039) Enabled Enabled Disabled Disabled
IOS33 (ver 1040) Enabled Enabled Disabled Disabled
IOS31 (ver 3092) Enabled Disabled Disabled Disabled
IOS30 (ver 1039) Enabled Enabled Disabled Disabled
IOS28 (ver 1288) Enabled Enabled Disabled Disabled
IOS22 (ver 7) Enabled Enabled Disabled Disabled
IOS21 (ver 7) Enabled Enabled Disabled Disabled
IOS20 (ver 7) Enabled Enabled Disabled Disabled
IOS17 (ver 7) Enabled Enabled Disabled Disabled
IOS16 (ver 257) Enabled Enabled Disabled Disabled
IOS15 (ver 7) Enabled Enabled Disabled Disabled
IOS14 (ver 7) Enabled Enabled Disabled Disabled
IOS13 (ver 7) Enabled Enabled Disabled Disabled
IOS12 (ver 6) Enabled Enabled Disabled Disabled
IOS11 (ver 7) Enabled Enabled Disabled Disabled

Thanks.

 

[SifJar]

yeah its a bug.

 

[madtamski]

A bug where?

The update process, or signcheck?

 

[xzxero]

A bug where?

The update process, or signcheck?

l would say the update process.
you should have used waninkoko's updater to get to 4.1
Nintendo updates overwrite some IOS's and it patches the trucha bug.
try using IOS downgrader.

 

[SifJar]

SignCheck. In 4.1, it doesn't work properly and says every IOS has trucha bug, where it really doesn't. Its because signatures changed or something, and SignCheck hasnt been updated yet, but the developer is working on it I believe.

 

[kzch]

Nintendo updates overwrite some IOS's and it patches the trucha bug.

I understand that is what was supposed to happen, according to you and many other people. But my Nintendo update actually KEPT the trucha bug in ALL IOS's when overwriting some IOS's to higher versions. If this is a bug of Nintendo's update process, isn't that a good thing for us all, and would make Waninkoko's updater pointless? I mean at least before Nintendo fixes this.

BTW, xzxero, I did learn a lot from you online guide. Thanks.

 

[kzch]

SignCheck. In 4.1, it doesn't work properly and says every IOS has trucha bug, where it really doesn't. Its because signatures changed or something, and SignCheck hasnt been updated yet, but the developer is working on it I believe.

Thanks. This make sense.

Now my next question is: what should I do next? I understand I should run trucha bug restorer to reinstall IOS36 w trucha bug. Since I already have cios38r14 installed at ios249, I guess I could just use that instead of downgrading ios15.

But which version is the IOS36 installed by the TBR? Is it an older version?

Instead of running trucha bug restorer, can I simply use DOP IOS to get trucha bug enabled on all the current (latest) versions of IOS's, IOS36,37,51,53,55, 60, 61, etc? Isn't that better than restoring to the older versions?

 

[SifJar]

You could use dop-IOS to install trucha bugged IOS.

 

[mattjd]

Use Dop - IOS downgrade all IOS's 36 and below and upgrade all IOS's 37 and above and enable trucha bug if the option is there.

 

[spacedkadet]

i used dop-ios to upgrade and trucha every ios except for ios60 (didnt wanna mess with that one heh) on my system last night and everything still works fine

 

[kzch]

Use Dop - IOS downgrade all IOS's 36 and below and upgrade all IOS's 37 and above and enable trucha bug if the option is there.

Thanks for your tip. But would you explain why downgrade all IOS's below and including 36?

Edit: it seems for IOS

 

[0M39A]

haha, this tricked me too a couple weeks ago when i updated to 4.1. was like "wtf? this is awesome!" but then tested and found out that its was just a bug.

[edit]

as i already had a few cios's installed, and updated via nintendo, i just used dop-ios to patch ios60 and thats it. everything works fine for me.

 

[john1010_ma]

Can someone confirm if not having flash access for IOS 222 & 223 does not affect the Wii in any way? What does flash access do anyway?

CODE"IOS number", "Trucha bug", "Flash access", "Boot2 access", "Usb2.0 IOS tree"

"IOS250 (ver 65535)", Enabled, Disabled, Disabled, Enabled
"IOS249 (ver 14)", Enabled, Disabled, Disabled, Enabled
"IOS223 (ver 4)", Enabled, Disabled, Disabled, Disabled
"IOS222 (ver 4)", Enabled, Disabled, Disabled, Disabled

 

[urherenow]

you only need to mess with 2 IOSs.
IOS61-> Install latest with NO PATCHES
IOS30-> Install old version

This is so
1)Hackmii installer will run without complaining and
2)HBC won't end up upside-down.

Everything else can be the latest and patched all you want.

But just to make this idiot proof I should say one thing... if you feel the need to download the latest IOS versions manually to install them as WAD files, then you'll end up installing stubs (which you DON'T want to do if you're sticking with 4.1 or below) make sure your .wad files are actually a MB or more in size. The tiny ones are almost surely stubs.

And disclaimer 2: You SHOULD manually install IOS 70 after running it through freethebug in case you update to 4.2 and want to continue using preloader

 

[john1010_ma]

you only need to mess with 2 IOSs.
IOS61-> Install latest with NO PATCHES
IOS30-> Install old version

This is so
1)Hackmii installer will run without complaining and
2)HBC won't end up upside-down.

Everything else can be the latest and patched all you want.

But just to make this idiot proof I should say one thing... if you feel the need to download the latest IOS versions manually to install them as WAD files, then you'll end up installing stubs (which you DON'T want to do if you're sticking with 4.1 or below) make sure your .wad files are actually a MB or more in size. The tiny ones are almost surely stubs.

And disclaimer 2: You SHOULD manually install IOS 70 after running it through freethebug in case you update to 4.2 and want to continue using preloader

You clearly do not understand my previos post. My question is about why is the flash access for IOS222/223 disabled as shown in SignCheck and what does flash access do.

 

[Det1re]

Can someone confirm if not having flash access for IOS 222 & 223 does not affect the Wii in any way? What does flash access do anyway?

CODE"IOS number", "Trucha bug", "Flash access", "Boot2 access", "Usb2.0 IOS tree"

"IOS250 (ver 65535)", Enabled, Disabled, Disabled, Enabled
"IOS249 (ver 14)", Enabled, Disabled, Disabled, Enabled
"IOS223 (ver 4)", Enabled, Disabled, Disabled, Disabled
"IOS222 (ver 4)", Enabled, Disabled, Disabled, Disabled

Flash access means, that your IOS is able to read/write to your NAND filesystem.
Not sure, if this is a bug, but i expect it is a mistake; since WAD Manager can write to NAND fs with IOS249...

 

[john1010_ma]

Can someone confirm if not having flash access for IOS 222 & 223 does not affect the Wii in any way? What does flash access do anyway?

CODE"IOS number", "Trucha bug", "Flash access", "Boot2 access", "Usb2.0 IOS tree"

"IOS250 (ver 65535)", Enabled, Disabled, Disabled, Enabled
"IOS249 (ver 14)", Enabled, Disabled, Disabled, Enabled
"IOS223 (ver 4)", Enabled, Disabled, Disabled, Disabled
"IOS222 (ver 4)", Enabled, Disabled, Disabled, Disabled

Flash access means, that your IOS is able to read/write to your NAND filesystem.
Not sure, if this is a bug, but i expect it is a mistake; since WAD Manager can write to NAND fs with IOS249...

Thank you for clarifying!!