Hacking System Menu questions/thoughts

  • Thread starter Thread starter OSW
  • Start date Start date
  • Views Views 168,135
  • Replies Replies 1,572
There's no way to bypass the updates without GeckoOS?
frown.gif

Does the Wii brickblocker (removes the update) work with this? Say I remove the update and load the game from this new menu, will it still ask for an update?
 
Just Install Starfall!!!

this thread is getting ridiculous. could a mod try and tidy it up a bit?
Btw keep trying to get that patch into the sysmenu it will be really helpful
smile.gif
 
ether answering...
wow.. my finger felt on the floor..
smile.gif


I have the feeling you are fed up with some questions. I am really sorry if I am part of the people who could make you mad. it is not the point.
I am simply trying to learn... and from :

ether2802 said:
We always need cIOS36_r7 wich get installed in the place of IOS249, ok?

ok so I was not totally crazy when asking David432 to mention it...
me happy
smile.gif
smile.gif
wink.gif


but still this one is "pending"
QUOTE(ether2802 @ Jan 12 2009, 05:57 PM) IOS30 is not used by any game, but is the principal IOS in 3.2 because that one is used by the SYSTEM MENU, wich have all of the properties of our Wii's, if IOS30 is not there, SysMenu can function at all and you'll have a nice 250 usd paper weight next to your TV unable to be fixed, ok?
if SysMenu is not there, is easier to fix, but it have the properties of making your underpants kind of brownish, ok??

that is totally clear to me... and I hope to all the other who READ the whole thread.
the only question is a matter of experience.. would you advise to keep cios30 for the last as it is the most sensible (I fully understand it is not used by games, and only by SM, and that's what makes me think I should keep it for the last....) if something wrong happens with the other cios we always have access to wadmanager.
but on the other hand , correct me if I am wrong, another option is to test with cios33 as per Wiipower's advise, and then put cios30... this way we can have (with starfall) the possibility of autowadmanager....
mmm which one will I eat first ??? the meat or the meat ?? lol

don't mean to ask stupid questions.. just to open people's mind (including mine) to the different choices we have. if you feel it has nothing to do in this thread feel free to tell me, I will try to keep it to the minimum..
unfortunately I do not have enough coding knowledge to be really helpful.

you are really doing an amazing job.. and I really like what I am learning. i hope one day I can be of help...
R.
 
I think it's a great idea to let cIOS30 and the very end of the installation process, and I forgot to tell at the end of the other post: ERGO we don't need to patch SysMenu to IOS249 and install it anymore, since cIOS30 would do the same, and it is a little bit safer, still is riky to do this, but if you have installed 10 different .wads already, what can be wrong installing cIOS30.wad, right??
 
I installed cIOS30 last on two wiis and it made me feel much safer because there hadnt been a single error in all of the other ios'
 
ether2802 said:
I think it's a great idea to let cIOS30 and the very end of the installation process, and I forgot to tell at the end of the other post: ERGO we don't need to patch SysMenu to IOS249 and install it anymore, since cIOS30 would do the same, and it is a little bit safer, still is riky to do this, but if you have installed 10 different .wads already, what can be wrong installing cIOS30.wad, right??

ether,
ok... the boss have talked.. better follow his advice
wink.gif


but once again you got me confused... duh... things seems so clear for you but trust me it is hard... and the more noobs (like me) asks you question, the less your communication is clear... lol
tongue.gif
:P:P

QUOTEERGO we don't need to patch SysMenu to IOS249 and install it anymore, since cIOS30 would do the same
I will definitely not patch SysMenu to IOS249.. you guys were clear enough that it is not needed thanks to the WAD.
"but we don't need to install IT anymore ???? "... that part confused me... we do not need to install CIOS36_rev7 as ios249 ???

just kiding
smile.gif
couldn't hold this one.......

for the ones who did not get it.. we do not need to install a patched version of SysMenu anymore (which was the previous method to be able to replace IOS30 by CIOS30 as it was locked)



one more thank for you Ether..
if you ever need a disciple.. I am free and available

R.
 
As per my post in the other thread, i'm gonna stop working on this since no one can respect the overall decision to wait on a tutorial until the video/out of region issue was fixed. I may decide to release what i've got as soon as i get it working with all out of region games, as right now my fix idea only works for games that were capable of being forced anyway.
 
About the preloader 0.25, you can apply and add your own patches to the system menu with it, so if we find out how menupatcher or menurebooter patches the sysmenu to use IOS 249 and forces games to use IOS 249. We can then just install CIOS 249 and set the patch in preloader 0.25.
 
The CIOSPACK should install with wadinstaller, am i wrong ?

So with TP Hack + wadinstaller with all wads from the pack on the root af the sd card should do the job ?


Edit: For the region and video patch i guess i can find the solution on the wiibrew reverse engineering forum, they have a System Menu sub-forum... i'll take a look to that tonight.
 
jespertje said:
About the preloader 0.25, you can apply and add your own patches to the system menu with it, so if we find out how menupatcher or menurebooter patches the sysmenu to use IOS 249 and forces games to use IOS 249. We can then just install CIOS 249 and set the patch in preloader 0.25.

Forcing the use of IOS 249 is what was causing compatabiliy issues, by patching all the IOS we have eliminated the issues as games still get to use their ios and we don't need to rely on "on-the-fly" patching, which is where i think alot of game errors came from, even the 002 error is gone with this method. All games will run without problems now (excluding bad burns and out of region/video issue).
 
digitydogs said:
As per my post in the other thread, i'm gonna stop working on this since no one can respect the overall decision to wait on a tutorial until the video/out of region issue was fixed. I may decide to release what i've got as soon as i get it working with all out of region games, as right now my fix idea only works for games that were capable of being forced anyway.
................................
 
There is no danger in this. The only chance of danger would be from a bad wad, seeing as over 100 people have tested this without error i can say the brick chance is under 1%. that 1% being user error or stupidity. The entire homebrew scene is a brick risk.
 

Site & Scene News

Popular threads in this forum