Separate names with a comma.
Discussion in 'Wii - Hacking' started by JoostinOnline, Dec 29, 2011.
Questions answered, move along.
besides being pointless there are downsides
Things like further (in memory) patching dont work - afaik riivolution does this
hashes are different - afaik used by hbc installer to choose an iso
who knows if the patching is done correctly - in cioscrap it wasn't, don't know about the others
it may caused unintendet sideeffects noone thought about
Yeah, the Hackmii installer refuses to work if the IOS it uses is patched. That's a result of Team Twiizers actions, not the patches.
What do you mean "correctly"?
You could say that about anything, lol. You could easily say that Nintendo's patches to block the vulnerabilities could cause unintended side effects.
Nope. The patch used most commonly, often referred to as "trucha bug patch" or whatever, does NOT patch in the trucha bug. It completely removes the signature check.
Riivolution has to patch stuff in memory to work - this won't work with an already patched IOS, because the stuff needing patched could be different.
And TT took those actions because 90% of the bug reports they were getting for their software was a result of patched IOS conflicting with it. Patched IOS are unnecessary, and so it is not worth the extra effort to support them, and as they don't work properly with TT's software as-is, they block them.
the patch could be applied incorrectly - patching too much, not enough, wrong place...
No you couldn't. Their patch simply returns the Wii to the way it was intended. All they changed was a memcpy to a strncpy. In the "homebrew" patch, the function is removed. And there are numerous other "homebrew" patches that Nintendo have not patched officially (obviously, since they are patches which add/remove stuff, not which restore old bugs).
Thanks, that cleared up a lot of questions I had.
I'm still fine with patching the SM IOS and even IOS36 since they are beneficial (36 not so much anymore).