Hacking Possible "Safe" System Menu 3.4?

[WB3000]

As of now, the general rule is that 3.2 is the optimal System Menu version to be using. It is the latest one with absolutely no hacks disabled. The main reason why 3.4 is avoided is that it brings along a whole array of patched IOS modules with it, as well as making the TP hack harder to use and disabling Trucha discs. Supposed automatic updates are also a concern.

However, if these issues were all eliminated, and a safe collection of patches were created, it would make the Menu 3.4 itself safe to have.

These are the primary issues keeping users away from 3.4 (Green if currently fixable; Red if not):

Trucha-signed discs are blocked.
Correct me if I'm wrong, but IOS50 (the core of 3.4) can be patched to include the bug again.

Twilight Hack is "blocked".
Not an issue with the latest Hack, but a full patch would be nice.

Loads of patched IOS modules are installed.
The assumed method of installation would be via WAD. This also solves most issues outside of the Menu itself.

Automatic Updates.
A disc update patch would be needed, along with research into whether or not the Menu itself takes control during online updates as suggested.

Right now, I'm blanking on any more issues. I'm sure there are more, but I'll leave it at that. It would be nice to see an effort to add "safety" features to this menu, particularly with the Automated Updates problem.

 

[Forsaekn]

search Forsaekn cSM for details. I had the thread closed because it was getting offtopic while I developed, but perusing some of the posts you'll get some information. All of these issues have been tackled, and the patches are modular, in that they can be applied to a future system menu with little effort. Of course, new protection mechanics would have to be approached when they are released, but this should not take more than a week at best. This is already a project in the works with a beta coming soon.

Fors

 

[Miles]

I was under the impression that we included all of the new features 3.4 has into 3.2

 

[Don Killah]

no need to get 3.4 since all the best ideas were including into 3.2 + all the other patches are done by Starfall/Preloader.

 

[Untouchable757]

what are the features of 3.4 thats not in 3.2

 

[wolffangalchemist]

what are the features of 3.4 thats not in 3.2

faster sd read speeds and auto/evil updates. nothing much else

 

[mcj]

In regards to the auto updates .. are you speaking of Nintendo's change to the EULA that says they "may" automatically update the Wii? I still think it's just a scare tactic. Simple solution is to turn off the Wii Connect feature.

 

[Jacobeian]

staying at 3.2 is considered safer because patching system menu and IOS used by the system menu is not considered as being safe, that's all

but theorically, you could disassemble/hack/patch everything you want

 

[Untouchable757]

those updates sound like sony updates on the psp

 

[Arm the Homeless]

For the last time, there is NO CODE in the system menu that can allow it to auto-update.

 

[UranusKiller]

For the last time, there is NO CODE in the system menu that can allow it to auto-update.

Don't know why you bother answering to these idiots, they all take the piss and don't read, search or understand...
this scene is like NO OTHER.........one word ready? PATHETIC
it's turned out too dam childs play!

 

[Golfman560]

For the last time, there is NO CODE in the system menu that can allow it to auto-update.

Well if Nintendo installed a demodulator into the next update people would be forced to auto-update. Those flange widgets that Nintendo have are pretty hard to get past.

 

[tj_cool]

As long as they don't release a new update, your wii can't update
so now problem for now
(and if they release an update, there's still no problem)