There's loads of exploits now which work with any of system menus, including 3.2.
Just saying...
Just saying...
He was talking about Wii Mod v3.2.There's loads of exploits which work across all of system menus, including 3.2.
What problem? Did I miss a post somewhere?my only problem is the the TBR one click mode...
What is the point of TBR when you have AHBPROT and cboot2?for me ...wii mod is still best...
my only problem is the the TBR one click mode...
I prefer a cIOS over AHBPROT, since a cIOS has proven far more reliable.
Go back to the wiibrew forums.I prefer a cIOS over AHBPROT, since a cIOS has proven far more reliable.
PIRATE
Go back to the wiibrew forums.I prefer a cIOS over AHBPROT, since a cIOS has proven far more reliable.
PIRATE
still, there is no situation that would require tbr over ahbprot or cboot2 methods of resoring cios. TBR is never needed regardless of system menu version or exploit. Just saying that tbr is an unneeded outdated step adding extra time to the mod process.im loading the app on exploit on multiple wiis...
btw im a console modder and i mod many wiis a day in differrent versions, so AHBPROT is not soothable for way
AHBPROT and a cboot2 can't do everything a properly patched IOS36 can, plus nobody uses cboot2 since it requires replacing the bootmii folder (unless you have cboot252).
I do too, AHBPROT just seems to have quirky issues at times, but since SetAHBPROT it has become more useful and yet it also has seemed to bring more issues.I prefer a cIOS over AHBPROT, since a cIOS has proven far more reliable.
More or less, it is just taking an IOS and patching it, but instead of saving it to the nand for reuse you recreate it on the fly after a reload IOS.I consider AHBPROT a "cIOS lite", or as giantpune would probably call it,"pussyCIOS""pussieCIOS"
So is there a problem in the TBR code, I don't think I have heard of one yet. But if there is let me know and I'll add it to the list.What problem? Did I miss a post somewhere?my only problem is the the TBR one click mode...
Not to mention an AHBPROT patched IOS lacks essential modules for backup loading.More or less, it is just taking an IOS and patching it, but instead of saving it to the nand for reuse you recreate it on the fly after a reload IOS.I consider AHBPROT a "cIOS lite", or as giantpune would probably call it,"pussyCIOS""pussieCIOS"
Not to mention an AHBPROT patched IOS lacks essential modules for backup loading.More or less, it is just taking an IOS and patching it, but instead of saving it to the nand for reuse you recreate it on the fly after a reload IOS.I consider AHBPROT a "cIOS lite", or as giantpune would probably call it,"pussyCIOS""pussieCIOS"
Eh that's mostly just which base IOS is used and which patches are applied. Theoretically you could patch the d2x patches in on the fly, although I don't think anyone is doing that yet.Not to mention an AHBPROT patched IOS lacks essential modules for backup loading.
That is not what I meant, I am not saying not to install and use a patched ios36, you should use a patched ios36 (236) for everything. I just don't see a use for tbr anymore, downgrade ios15, patch ios36, etc. You should be able to load wiimod with AHBPROT on any wii and install your patched ios36 with the ios manager or wad manager.AHBPROT and a cboot2 can't do everything a properly patched IOS36 can, plus nobody uses cboot2 since it requires replacing the bootmii folder (unless you have cboot252).