[MMM] Multi-Mod Manager (a collection of tools)

Discussion in 'Wii - Hacking' started by Wiiwu, Feb 11, 2010.

  1. burritoboy9984

    burritoboy9984 GBAtemp Advanced Fan

    Member
    2
    Jan 24, 2009
    United States
    Lookin forward to it [​IMG]

    -Erik
     
  2. Wiiwu
    OP

    Wiiwu GBAtemp Regular

    Member
    1
    Jan 21, 2009
    Hong Kong
    Asia
    I have released v13.4 which will bring it in-sync with Nintendo's Sep 7 System updates.


    Download homepage: Multi-Mod-Manager


    [Changelog for v 13.4 - Sep 20, 2010]

    Install & Patch IOS36:
    - upgraded to support Nintendo's Sep7 IOS updates
    - installs patched IOS36 as IOS36 & IOS236
    - IOS36-64-v3608.wad used as base IOS

    IOS Manager
    - updated IOS information database to Sep7

    Others
    - added new on-the-fly patches to active IOS via AHBPROT mode (if available)

    *Important Note*
    If your Wii has a non-working internet connection setup, a bug in Homebrew Channel 1.07 & 1.08 will crash any homebrew apps (including MMM) within seconds after launch. This affects apps launched in AHBPROT mode.

    To disable AHBPROT mode, delete the "no_ios_reload" line from meta.xml file in MMM apps folder.
     
  3. xzxero

    xzxero ♥bong milk does good for the brain♥

    Member
    3
    Jul 18, 2008
    United States
    SB
    OMG you da best of the best!!

    update yo sig buddy!
     
  4. Abkarino

    Abkarino GBAtemp Regular

    Member
    1
    Sep 14, 2009
    Egypt
    Thank you Wiiwu for this great update [​IMG]
    also hope to have ELF version as my last request [​IMG]
     
  5. burritoboy9984

    burritoboy9984 GBAtemp Advanced Fan

    Member
    2
    Jan 24, 2009
    United States
    thx for the update! Perhaps in the future get rid of the 36 patching, and only keep the 236? Now we just need the hbc updated [​IMG]

    -Erik
     
  6. Abkarino

    Abkarino GBAtemp Regular

    Member
    1
    Sep 14, 2009
    Egypt
    Thank you man the ELF version also is available in your 4shared page [​IMG]
     
  7. petspeed

    petspeed GBAtemp Advanced Fan

    Member
    3
    Nov 13, 2009
    Thanks for this great update.

    Does this make it able to install unsigned wad's without a patched IOS? Like a WAD Manager using AHBPROT instead of a patched IOS / CIOS. If not would that be possible? That would be really cool.
     
  8. XFlak

    XFlak Wiitired but still kicking

    Member
    9
    Sep 12, 2009
    Canada
    Ontario
    It should allow that,

    but be careful, because of the bugs in the HBC when launching no_ios_reload apps, if u attempt to install a vital wad (like SM or SM IOS) and u don't have wifi on the wii and it freezes at the wrong moment, it could lead to a brick

    if the app doesn't freeze within the first 60 seconds of it being launched, it should be safe to use.
     
  9. burritoboy9984

    burritoboy9984 GBAtemp Advanced Fan

    Member
    2
    Jan 24, 2009
    United States
    Doesn't sound like it uses AHBPROT to install wads... I think he just updated the trucha installation...

    -Erik
     
  10. Yuan

    Yuan GBAtemp Maniac

    Member
    3
    Oct 1, 2007
    Brazil
    If you change IOS after launching MMM (or through mmmconfig.txt) does it disable AHBPROT?
     
  11. XFlak

    XFlak Wiitired but still kicking

    Member
    9
    Sep 12, 2009
    Canada
    Ontario
    reloading the IOS would disable AHBPROT, this applies to all apps

    I'm not sure how wiiwu has set up MMM to handle mmmconfig when AHBPROT patches are applied... if it reloads the IOS, then u would lose AHBPROT patches

    @burritoboy9984... u can't give ahbprot rights to some features of an app and not others (AFAIK)... the only way your statement is possible is if when the app is loaded with ahbprot rights, the only option available is to install a patched IOS236... if all the other options are available, like the Wad Manager for example, then it too would use ahbprot. Basically, until the IOS is reloaded, ahbprot rights affect everything done by the app. WiiWu could have disabled all his other features entirely if using ahbprot patches until the IOS is reloaded... but I doubt he would've chosen to do that.
    edit: everywhere I said ahbprot rights, i meant ahbprot rights + on the fly patched IOS

    fyi, for those without wifi, if u wait in the HBC for 30 seconds before launching any no_ios_reload app, u will have a much higher success rate
     
  12. Wiiwu
    OP

    Wiiwu GBAtemp Regular

    Member
    1
    Jan 21, 2009
    Hong Kong
    Asia
    HBC really need to fix this nasty bug asap.
     
  13. tueidj

    tueidj I R Expert

    Member
    7
    Jan 8, 2009
    Maybe if you used a copy of libogc that wasn't from November last year, you'd see the bug has been fixed there already.
     
  14. Wiiwu
    OP

    Wiiwu GBAtemp Regular

    Member
    1
    Jan 21, 2009
    Hong Kong
    Asia
    Yes if you change/reload to another IOS, the new IOS will reset AHBPROT back to its default disabled mode.
     
  15. pretender13

    pretender13 GBAtemp Regular

    Member
    1
    Apr 18, 2009
    Canada
    btw thanks for this great app Wiiwu, works great [​IMG]

    FYI for those that want to check if AHBPROT is enabled within MMM
    If you goto the information screen.

    AHBPROT=000000 (Disabled)
    AHBPROT=FFFFFF (Enabled)
     
  16. tueidj

    tueidj I R Expert

    Member
    7
    Jan 8, 2009
    Wiiwu did you come up with the IOS patching code all by yourself? Or if I look at the binary am I going to see the same GPL code from ftpii/dop-mii/priiloader that everyone else is using?
     
  17. Wiiwu
    OP

    Wiiwu GBAtemp Regular

    Member
    1
    Jan 21, 2009
    Hong Kong
    Asia
    If your mmmconfig has it set to reload to a preferred IOS then it won't do any AHBPROT patching which is logical.

    And I personally haven't found a reliable time to wait in HBC to ensure a higher success rate. The best is to ensure the Wii has a working network connection setup.

    BTW priiloader author also did extensive testing and blog on this HBC bug in more technical detail at http://www.dacotaco.com/about-the-priiloader-0-5-removal
     
  18. Wiiwu
    OP

    Wiiwu GBAtemp Regular

    Member
    1
    Jan 21, 2009
    Hong Kong
    Asia
    I missed that in the readme, thanks for mentioning it [​IMG]
     
  19. XFlak

    XFlak Wiitired but still kicking

    Member
    9
    Sep 12, 2009
    Canada
    Ontario
    I've personally confirmed on 3 Wii's with no wifi settings (I deleted them for this purpose) that if u wait 30 seconds from when u start the homebrew channel, approx. 85-95% of the time the app works as intended... compared to an approximate success rate of 15% when launched immediately from the homebrew channel.

    edit: also, 100% of the time I experienced errors in my testing, the errors occurred within 40 seconds of the app being launched (I tested probably 50 times on 3 different wii's)

    This following part is just speculation... but to me its as if when the homebrew channel first starts, it sets in motion Event X which is to occur 30-60 seconds later (maybe calling home? I dunno), and if another app is loaded with ahbprot rights (w/ latest possibly buggy library) before Event X takes place when this timer hits zero the app crashes... apparently only the HBC can recover from or compensate for Event X... or maybe the Event doesn't occur if an app isn't loaded right away, I dunno.... anyways, this is all my personal speculation, I am no expert on this, and I'm sure the real brains behind the scene will come through as usual... eventually.

    edit2: this is link explains my testing and speculation perfectly! It is a million times better than the 'laymans terms' speculation I gave above.
    http://www.dacotaco.com/about-the-priiloader-0-5-removal

    thx wiiwu for linking to this... I don't know how I missed it
     
  20. tueidj

    tueidj I R Expert

    Member
    7
    Jan 8, 2009
    No, it still doesn't explain it properly.

    All IOS communication is done via IPC requests. Each IPC request has a magic word, so the response can be identified. Unfortunately libogc used to always use a single constant magic word for every single IPC requests, so when a late response arrives for HBC's request to initialize the network (which can't be cancelled unless IOS is reloaded) the running app thinks it's valid and tries to run the callback.
    The fix for libogc is to make each app use a random magic word generated when the app starts/IPC subsystem is initialized. That way it will simply ignore any IPC responses that it didn't request.
    If you're still getting crashes I strongly suggest double-checking that the right libogc build is being linked in, and learn how to debug using the exception dump to trace where the crash happens.
     
Quick Reply
Draft saved Draft deleted
Loading...