Hacking Wii Mod

XFlak · Jan 5, 2011

@jskyboo, just curious, how does your any region changer work? It's not like the original any region changer that simultaneously downgrades to 3.2 when region changing right? If so, its very possible it could brick new Wii's (unless IOS60v6174 is installed to slot 30 beforehand), instead you should consider basing your work on "Anyregion changer mod06 for 4.1 by QK". Also, when your app is region changing Korean Wii's, make sure that if installing another region 4.2 or 4.3 System Menu that IOS60v6174 is installed to slot 70/80 respectively otherwise it will result in 003 error.

btw, weren't u and wiiwu working together at one point? Do you think you guys going to team up again and combine this project with MMM?

jskyboo · Jan 6, 2011

My region changer is just that, a region changer. It doesn't do the other steps of installing IOSs to other locations to make sure you can run a system menu and installing a new system menu, it just changes the region settings. So if someone were to want to downgrade to 3.2 it won't make sure you have downloaded IOS 60 as IOS 30 it just warns you if your region doesn't match what system menu you have installed. The system menu install tho does check if you have the IOS installed that is required to run, so if you install system menu 3.2 it would check that you had an IOS 30 but it doesn't check if it is IOS 60 installed to IOS 30 or even IOS 30 installed to IOS 30, it just checks if the IOS number and rev number are correct. So someone could go to the IOS menu install IOS 60 over 30, then install 3.2, and if they changed region then goto the region changer menu and change it. Same for the Korean wiis, you can install 60 to 70/80 but it doesn't make sure you do. That is mainly why there are soo many warnings in the region changer menu, the program can't stop you from bricking( or semi bricking) your Wii but it does try to warn you.

Me and Wiiwu were never a team. When I first started modifying dop-ios and he was one of the first to notice my work and brought more attention to it. Later he started making MMM which started out as modifications of my code. Occasionally I would update my code and then he would roll in some of my changes and so forth. So we weren't a team but his code has some of mine in it I would assume. After seeing some of the changes he made I thought some of them were good changes and so I replicated them, I've never seen any of the code for MMM so any features Wiiwu introduced I had to re-implement. As for whether Wiiwu will continue MMM, I can't say, me and Wiiwu don't talk outside of this forum so I don't know anything you can't read on these forums yourself.

XFlak · Jan 6, 2011

So, as I understand it, the region changing process using your app goes something like this: region change to w/e other region, then manually install the new region system menu and system menu IOS (if not already installed). So if a dumb user were to exit the app half way through the process, they would brick (or semi-brick) correct?

QUOTE said:
so if you install system menu 3.2 it would check that you had an IOS 30 but it doesn't check if it is IOS 60 installed to IOS 30 or even IOS 30 installed to IOS 30, it just checks if the IOS number and rev number are correct.

Hmmm, I don't know if I like that. I install IOS60v6174 to slot 30 and change the version number to 16174 (so its greater than the IOS30 stub version #)... it sounds like your app would not allow me to install a 3.2 system menu because the version number is not equal to the latest non-stubbed IOS30... is that the case, or would it just warn me and allow me to do it anyways? What I think would you should do instead, is allow the user to install the system menu as long as the system menu IOS version is not equal to a stubbed version, if it is greater than the stubbed version, it has likely been modified by some1 like myself to survive ninty updates. But yea... isn't there a more sophisticated way to check if an IOS is stubbed? Maybe look at yawmm source code for its extra protection, cwstjdenobs did an AMAZING job with it, and even wiiwu decided to incorporate it into MMM. I believe it even has code that will determine whether a Wii will brick by installing a true non-stubbed IOS30 as its system menu IOS... and it will only allow older Wii's to safely install that IOS as its 3.2 system menu IOS.

Anyways, I really like what you're doing with your app. The ppl have been in need of a easy to use region changing app for some time now. Keep up the great work!

jskyboo · Jan 6, 2011

@XFlak you're pretty close to understanding it right just a little off. If you install a system menu for a region other than your currently set region and exit the program, you will semi brick. If you change the region to one not supported by your current system menu without installing a new system menu, it will warn you but won't stop you and you will semi brick. That is the reason for all the notices before allowing you to change the region. The region changing process I would recommend (but I can't enforce) is to first install the system menu you want to have( doing a special IOS install first if needed like installing IOS 60 to IOS 30s spot ) and then changing the region. As changing the region takes very little time while the installing the system menu takes a LONG time and if it messes up it takes a while to find out it failed and then your region is already changed to a system menu you don't have. While installing the system menu first if it messes up in its long process oh well you haven't changed your region yet, but if it succeeds well then it only takes a sec to go change the region.

When you install a system menu it checks if you have the required IOS, first it checks if the IOS is installed, then it checks if the current rev >= the rev needed by the system menu, if the currently installed is greater than the required it checks if it is a rev number marked as stub( if it were installed from nintendo ), if you dont pass these checks it will offer the option to install the IOS. So in your case it would allow you to install the system menu. If however it is the same rev as a known stub say your IOS 30 was not really the stub but you change the rev to 2816 then it would mark it as you need to install a new IOS. Figuring if an IOS is a stub is very difficult as there isn't just a single hash or a simple thing to check for, that is shared by all stubs and also unique only to them. If someone has found a good method for identifying them with low false positives and low misses I can look into it but all the ones I have seen until now have problems. So currently the program only knows if an IOS might be a stub is if the rev number equals the one used by nintendo. That's how it knows which nintendo IOSs are safe to install and which aren't I have hard coded the rev number as safe to install or not.

Btw when I say it checks if you have the required IOS, I am basing that off of the list at http://wiibrew.org/wiki/System_Menu if that isn't complete or is incorrect/incomplete or if you notice the program not following the list then let me know and I'll correct it.

XFlak · Jan 6, 2011

sounds good! I'll definitely keep this app in my back pocket

btw, I think u should change the config file from "wm_config" to something else. The wm_config file is used by other wad managers, and your arguments are different than theirs so it could cause some issues for ppl using yawmm, wad manager multi-mod, etc.

jskyboo · Jan 6, 2011

XFlak said:
btw, I think u should change the config file from "wm_config" to something else. The wm_config file is used by other wad managers, and your arguments are different than theirs so it could cause some issues for ppl using yawmm, wad manager multi-mod, etc.

I have thought about changing it. At this point it should cause no harm. If the settings I use are added to the config you already have there should be no issue. My program only looks for the arguments it supports and the same goes for the other wad managers(unless they have diverged from the original code). So my program will ignore the arguments used by yawmm and if it hasn't changed it yawmm should ignore mine.

XFlak · Jan 6, 2011

sweet, good to know that the settings can co-exist without conflicting with one another, but it will still require manually merging the 2 config files for each app... which is no problem for me now that you've explained how it works. But I think most ppl will just copy the files to the SD card and overwrite the other wad manager config file without even realizing what they're doing.

Anyways, its not a huge deal, but I still think it should be changed eventually... besides, don't u want ur own config file? wiimod.txt sounds pretty sweet!

Cheers.

Lenneth · Jan 6, 2011

Cool, because I'm using Wad Manager 1.7 MOD1 By WiiNinja and it use a wm_config file too, but now I know what I have to do (simply merge the 2 in 1), thanks

(Excuse my damn belgian english speaking/writing again)

NOTE: I deleted my "libwiigui.a" file without taking care (i'm stupid...) and I can't find it on google or on libwiigui website >_<
Anyone can brough me a link to download it please ? (mediafire, megaupload or something like that...)
This file is in "devkitPro\libogc\lib\wii\" folder, thanks again

jskyboo · Jan 7, 2011

You guys should know if you aren't changing the settings from the defaults, you don't even need the options. The options I have included with the releases is what the program defaults to even if you don't have the settings file. The options are more for changing from this default behavior. And if any of these options does not follow that well then that would be an error and I'll fix it if anyone is seeing anything like that.

xfcrowman · Jan 7, 2011

I just tested thia app this morning and it's great - thanks jskyboo.

I did notice some bugs:

-When you go to the IOS list (in AHBPROT mode), it will indicate that some IOS's have trucha/nand permissions/etc when they actuall do not have those permissions. For example, on my wii IOS70 and 250 are both stubs, but they were reported as having the trucha bug enabled etc.

-In ahbprot mode, the wad manager will install wads, but it will not uninstall wads. This problem also exists in MMM.

Thanks again for continuing to work on this.

jskyboo · Jan 8, 2011

@xfcrowman Can you post your wiimod.csv? The program shouldn't ever check stubbed IOSs. Are you sure 70 and 250 are stubs? As for wad manager, is it only while in AHBPROT mode? I mean if you use a patched IOS does it do the same? Does it display an error? What wad are you using(don't post a link to it just the name and description)?

scooby74029 · Jan 8, 2011

NOTE: I deleted my "libwiigui.a" file without taking care (i'm stupid...) and I can't find it on google or on libwiigui website >_<
Anyone can brough me a link to download it please ? (mediafire, megaupload or something like that...)
This file is in "devkitPro\libogc\lib\wii\" folder, thanks again
[/quote]

@lenneth

here man i got that one for you here https://code.google.com/p/qjob/downloads/de...%3AType-Archive

scooby74029

Lenneth · Jan 8, 2011

It's "libgui.a" and I need "libwiigui.a" (it's not the same file).
Thanks anyway (you're the only one who answering me)

NOTE: Sorry for my bad english (i'm from Belgium)

jskyboo · Jan 8, 2011

Im not answering the question because Wii Mod does not use that lib and so I really don't know the answer. What are you trying to compile that is giving that error? Where did you get the lib originally?

Lenneth · Jan 8, 2011

No problem

I didn't remember where I found this file originally

It's only to don't have some warning when I'm compiling a newest revision of USB Loader GX (I don't like to have some warning when I compile something, I want to have a "100% clean" compilation).
But hopefully it didn't affect the homebrew in the end (but I'm maniac with all my compilations, I hate to see a warning line lol)

(Belgian English speaking/writing Powered©)

jskyboo · Jan 9, 2011

I noticed a couple bugs while looking into the issues people have mentioned hopefully this fixes some of them. Here is v1.7

Download:http://www.mediafire.com/?cgplln1inmv68ga

Changelog since 1.6 :

Code:

Changed check IOSs to reload original IOS before outputting csv, should cause fewer errors.
Changed how IOS revs were grabbed in a few places, should cause fewer errors in deleting IOSs, checking IOSs and a few other places.
Changed Config to sd:/wad/wiimod.txt

Lenneth · Jan 9, 2011

Thanks for this versions and to the change of wm_config.txt in wiimod.txt, it's helpful for the novices

xfcrowman · Jan 9, 2011

jskyboo said:
@xfcrowman Can you post your wiimod.csv? The program shouldn't ever check stubbed IOSs. Are you sure 70 and 250 are stubs? As for wad manager, is it only while in AHBPROT mode? I mean if you use a patched IOS does it do the same? Does it display an error? What wad are you using(don't post a link to it just the name and description)?

Sorry I didn't get back to you sooner, I have been busy the past few days.

To answer your questions:

IOS70 and 250 are definitely stubs, I did a NAND dump to be sure and they were stubs. This happened in AHBPROT mode, but I don't know if this would happen if I reloaded with a cIOS.

With wad manager, this problem only happened when in AHBPROT mode. The wads I was trying to uninstall were cIOS's (IOS222-224, hermes 5.1). However, installation of wads worked just fine while in AHBPROT mode.

I will try to post the .csv later today - sadly I've had a lot of work to do over this weekend.

Thanks again for your continued work on this project!

EDIT: Just saw the newest version. I will give that one a try and see if these issues have been resolved.

kylster · Jan 11, 2011

you seem to have a boot.elf and boot.dol both with different file sizes does it matter which one you use to boot up v1.7?

Shano56 · Jan 11, 2011

kylster said:
you seem to have a boot.elf and boot.dol both with different file sizes does it matter which one you use to boot up v1.7?

when in doubt, use boot.dol

Hacking Wii Mod

Wiitired but still kicking

Well-Known Member

Wiitired but still kicking

Well-Known Member

Wiitired but still kicking

Well-Known Member

Wiitired but still kicking

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

wanttabe dev

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

mich weich töten

noobie

Similar threads

Popular threads in this forum