![]() ![]() Basically you would run browser exploit that would then do homebrew channel "install" and take you back to menu, and for duration of the console staying on you could access homebrew launcher. I said this earlier in thread but this was actually what was done in early, no cold boot hax, no CFW, browser exploits only, destination Mii Maker. I could be wrong but essentially, a very old method of running homebrew launcher is "installed" into your memory, which will be gone when the console is turned off, and run when specific thing happens (Mii Maker). Well, not really but there is some code running in background which says "Mii Maker will be mine" - and when you open Mii Maker, it will boot into homebrew launcher instead. My over simplified explanation about the 50_HBL_INSTALLER file is that it is essentially older style system patch, which makes homebrew launcher run in background. But your homebrew channel in wii mode is wii mode thing, it should stay it should work no matter what you do on Wii U side except brick the console. I am over simplifying this because there is things like Wii U homebrew to boot into Wii menu, and nintendo's official methods of booting Wii mode with Wii U features like gamepad play and so on and SO ON. Wii menu's homebrew channel is not linked to Wii U's at all, your Wii and Wii U are essentially "two different consoles in one" - in sense. Homebrew Launcher channel will work as it does, as will also forwarders and such. If you have homebrew launcher as a wii u app/forwarder that works/worked before tiramisu, deleting the file is fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |