If you install a new system menu via Wad, then that is all it does. If you install a new system menu from the SM Menu(on the main menu) then it will check if you have the correct IOS required for that System menu. So when installing 4.3 it will check if you have IOS 80 and if not it will warn you and try to have you install the correct IOS first. It does NOT install all the IOSs that came with the system menu update, if you want to update the other IOSs that were updated but aren't "needed" by the system menu then you can go to the IOS menu and click Update(that option will not change the System menu).Toastbrot said:i'm on systemmenu 4.2 now. when i install systemmenu 4.3 with wiimod, will all my ©ios stay untouched or do i have to reflash them afterwards?
So how did you have the sd set up?mauifrog said:ABHPROT appears to work for me from HBC without networkIt does? It should have asked you what IOS you wanted to reload to avoid the no net crash. It would seem you have bypassed that, which begs the question are you sure you don't have network or are you sure it was working?
On a second note, I also tested bannerbomb. It does not reload ios when loading the app, but does not make ABHPROT available or make the app think it is.mauifrog said:downgrade issue to 3.2 running ios30-v1040What do you know about this issue? Do any of the other IOSs have problems with newer Wiis? I've read a little about this but never many details.
QUOTE(mauifrog @ May 18 2011, 01:16 AM)
Hmm well I'm not sure how you are not getting caught by the workaround but if you really are loading with AHBPROT and no net I would think the no net crash would happen, just a matter of when.mauifrog said:I do not have any network connections setup on the wii. When I load wiimod, it loads the the patches and says they work, the wii mod loads with ABHPROT enabled. However this does not always work, I have had a couple dsi exceptions at load, it has hung at patching, it has hung while viewing ios info, it has given the ret 1017 when uninstalling wads, and it has loaded fine and worked. Could just be my wii, only thing wierd about my wii is I recently bricked it with dop-ios mod 11.4. So perhaps a fresh nand and some more testing will clean up my issues.
Many newer wii's AKA lu64+ can not function with most 3.2 ios, not all newer wiis, some work. Specifically ios30-v1040, ios35-v1040, and ios36-v1042 have caused issue on newer wiis when the ios is downgraded. IOS30-v1040 is the system ios for 3.2, if the wii will not function with ios30-v1040 and the wii is downgraded to 3.2 running this ios, the wii will brick. Ios35 was used for many channels, newer wiis that downgrade to ios35-v1040 would get black screens when loading HBC, forwards, not an issue now as most use ios58. IOS36 was used to load most apps from HBC/preloader/priiloader, newer wii's that downgrade to ios36-v1042 would get a black screen when loading the app, not a real issue now since ios58 is mostly used. Another issue with downgraded ios30-36 on a newer wii is it will cause the hackmii installers to hang, the installer will try to load these older ios30 -36 and crash the installer. Any wii can safely downgrade to SM 1.0+, so long as the system ios is functional. Patching ios60-v6174 into ios slot 9, 11, 20, 30 will support sm 1.0-3.3 on all current wii models. This is why I test ios60-v6174 functionality on a wii before proceeding with the mod, if a wii is ever made that does not function on the 4.1 ios the install would crash preventing the downgrade brick. But I doubt there will ever be a new wii hardware with this issue, but who knows.
CaptainJackHarkness said:It seems Mauifrog does not reply on WiiHacks but only on GBA Temp mwa-haha.
Great thread. I read all 12 pages. Mauifrog, my friend - your guide is amazing but is god awful when it comes to explaining your reasoning to newbies who are interested, then again you have stated it is not meant
to educate but more of a simple guide on how to hack and quickly.
Reading everything here, it makes sense... 1OS236.wad, the IOS60 version check, for the downgrade...kudos...but yes...as for the topic:
AHBPROT is interesting, revolutionary, amazing. What I do..ummm what's the word
Ahgot it. What I do believeeeeeee AHBPROT is capable of is that direct access....IOS236 is amazing, not requiring IOS 15 downgrades to traditional DOP-IOS/Trucha Bug Restorer ...but like everyone has said: lack of knowledge to AHBPROT is typical. It took me forever to actually FIND information on it...and then TeamTwizzers wrote their thing, and it made SOME sense. As for AHBPROT - and the reason I dislike it is simple: it's confusing. It may show as active, when it might not be active, and no matter how you create an amazing program (such is WiiMod - which I believe is the successor to Multi Mod Manager) it does everything imagineable that I thought nothing could replace MMM..until I found WiiMod trying to google "AHBPROT" and u all discuss this AHB stuff...
As for System Menu WADs - do these install all the IOS updates? or are they SOLELY for system version and 1 IOS?
Changed how system menu region is detected
Added Region presets to any region changer
Fixed Channels and System menu install issue with receiving http 1.0 replies
Moved AHBPROT no net code, should catch in more cases
if AutoloadIOS is installed and it wasnt before, reload it if AutoLoadOnInstall is on
Changed the IOS menu around
Added new feature copy ios to another location and or change version and or patch perms
BC now dumps to RVL-bc-v[x].wad on any title manager
MIOS now dumps to RVL-mios-v[x].wad on any title manager
IOSs now dumps to IOS16-64-v[x].wad on any title manager
Channel Menu now display currently installed version.
Lots of code cleanup and bug fixes
Hmm... AHBPROT patches are a sensitive thing. Im really not sure as to why. After adding some of the features for 2.7, that in no way were related to the AHBPROT code, it started giving me that error as well and after some further changes mostly not related to it, it started working again. I guess not for all Wiis. I could add some debug to a test release if you'd like but it may not come up with anything. Im not really sure why unrelated code seems to affect those patches.airline38 said:@jskyboo, I got the "Identifying as SU...Error! ES_Identify (ret=-1017)"
again (same error as I used v2.4 or v2.5) when I tried to use v2.7
to test "Region Changer" under AHBPROT mode.
Everything is OK when I change back to v2.6.
Any idea ?
Unfortunately there still is no way around the AHBPROT no net bug, or at least to my knowledge no one has found a fix. If you look at the messages being printed there you will see it failed to apply the patches for AHBPROT that's because it no longer is in that mode. I believe that first part of the first line was it checking for net, when that failed it immediately switched IOS to avoid the no net crash. So at that point you don't have AHBPROT anymore and you can't get it back, however if you reload an IOS with nand patches you should be able to still use the rest of the app. But no you can't use AHBPROT, there is nothing inherently wrong with no net AHBPROT except for that bug that affects all apps that support AHBPROT, if a true fix for that bug is found then AHBPROT could work.hosigumayuugi said:I can't use AHBPROT mode if I don't set Internet setting in Wii Config.
WiiMod says "Failed to get titles." and didn't work well.
http://img713.imageshack.us/img713/2918/failedi.jpg
This screen shot is from my Japanese mod(sorry),
but I can't use AHBPROT mode with original v2.7, too.