Homebrew Haxchi Crashes After Opening Twice in a Row

thomadash

Active Member
OP
Newcomer
Joined
Mar 1, 2018
Messages
33
Trophies
0
Age
17
XP
207
Country
United States
I installed Haxchi so opening the Homebrew Launcher wouldn't be a coin flip with the browser exploit. I want to apply mods to games, which involves opening the HBL, running an application, causing it to close the HBL, then opening the HBL again and opening another application, which closes the HBL and applies the mods. However, after trying to open Haxchi a second time after running the application, it crashes the system. Why does this happen and is there a way I can bypass this? I'm using SDCafiine and Mocha to attempt to run the mods, just in case using different applications would be the solution.
 

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,651
Trophies
2
Age
44
Location
Engine room, learning
XP
15,213
Country
France
in order to launch HBL, the first launched application (haxchi or browser) need to patch the firmware to allow userland code execution. then it can launch the HBL.
If you re-run the exploit, it crashes the console because the system is already patched.

To prevent having to check if the system is already patched and re-patch it while not needed, HBL is temporarilly placed in MiiMaker channel (before the real MiiMaker app) so you can launch it without doing a re-patch (and freeze) of the system.

Haxchi or Browser -> [userland system patch (not kernel CFW patch) -> put HBL in MiiMaker -> Run Miimaker ->] HBL
All the [ ] part is unseen by the end user so you think haxchi launches HBL


If you want to launch HBL again, you need to launch MiiMaker.
if you want to really access MiiMaker, launch it and exit HBL, it'll continue the execution of the real MiiMaker.



If you install the HBL Channel, it's an unsigned channel and you'll need kernel level CFW signature patch to launch it.
Haxchi can do it, launch haxchi with A button pressed (default config) to patch the system menu and return to system menu. it looks like nothing happened, but you are now in CFW :)
you can now launch any unsigned app/homebrew channels until you shutdown the console or access vWii.

The HBL app is inside the HBL channel. no more MiiMaker involved, and you can launch HBL channel as many time as you want.
the CFW patch must be done only once (haxchi + A for CFW, or haxchi + no button for userland and HBL in miimaker). running the same type of patches (user or full cfw) more than once freeze/crashes (haxchi/cbhc/mocha/sigpatch2xx/etc.) use only one type until reboot.
 
Last edited by Cyan,

thomadash

Active Member
OP
Newcomer
Joined
Mar 1, 2018
Messages
33
Trophies
0
Age
17
XP
207
Country
United States
in order to launch HBL, the first launched application (haxchi or browser) need to patch the firmware to allow userland code execution. then it can launch the HBL.
If you re-run the exploit, it crashes the console because the system is already patched.

To prevent having to check if the system is already patched and re-patch it while not needed, HBL is temporarilly placed in MiiMaker channel (before the real MiiMaker app) so you can launch it without doing a re-patch (and freeze) of the system.

Haxchi or Browser -> [userland system patch (not kernel CFW patch) -> put HBL in MiiMaker -> Run Miimaker ->] HBL
All the [ ] part is unseen by the end user so you think haxchi launches HBL


If you want to launch HBL again, you need to launch MiiMaker.
if you want to really access MiiMaker, launch it and exit HBL, it'll continue the execution of the real MiiMaker.



If you install the HBL Channel, it's an unsigned channel and you'll need kernel level CFW signature patch to launch it.
Haxchi can do it, launch haxchi with A button pressed (default config) to patch the system menu and return to system menu. it looks like nothing happened, but you are now in CFW :)
you can now launch any unsigned app/homebrew channels until you shutdown the console or access vWii.

The HBL app is inside the HBL channel. no more MiiMaker involved, and you can launch HBL channel as many time as you want.
the CFW patch must be done only once (haxchi + A for CFW, or haxchi + no button for userland and HBL in miimaker). running the same type of patches (user or full cfw) more than once freeze/crashes (haxchi/cbhc/mocha/sigpatch2xx/etc.) use only one type until reboot.
Thank you so much! This helped me out a lot! Just a little thing on my mind, though: why did you choose Mii Maker instead of something like the Health & Safety app?
 
  • Like
Reactions: Neo127

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,651
Trophies
2
Age
44
Location
Engine room, learning
XP
15,213
Country
France
because it's the only app with necessary permissions (SD access !).

There's also an alternative to get SD access : the game disc app, but it depends which game you launch (Smash bros has SD access to store stages, etc.)
very few games have SD access permission, and that's the small game list used by Loadiine to get game redirection from disc to SD card, either miimaker or specific games grant SD access.
without SD access, no homebrew seen on SD.

you might wonder why not use an app or game with USB access?
USB driver used by Nintendo doesn't have FAT32 support. it's using WiiFS encrypted format, not easy to manage (but possible), but no homebrew used that method to store/launch homebrew.

Dimok tried to patch the USB driver to add the Nintendo's SD fat32 driver support in it (Mocha 0.2beta), but it's a very bad (or locked on purpose) driver and it doesn't achieve correct usb speed to be useful. FAT32 SD is better than FAT32 USB homebrew/speed wise.
everybody moved from loadiine to "wup installed" apps to use native WiiFS USB driver instead.
 
Last edited by Cyan,
General chit-chat
Help Users
  • No one is chatting at the moment.
    Sonic Angel Knight @ Sonic Angel Knight: Veho should eat a cookie :P