Hacking Homebrew app CustomizeMii Forwarder Issues

[Dainslaif]

Hello! I'm trying to create a forwarder channel for an emulator that I already have the DOL for on my SD card, and from what I can tell CustomizeMii is the right tool for the job, but I'm running into two issues;

1: Despite using a working source WAD as a base and just updating the file path, the channel I create in CustomizeMii will not process the meta.xml file. If I run the DOL manually from Homebrew Channel, it loads the additional arguments inside it.

2: There is a black loading screen that takes a few seconds to process, which doesn't appear for any other homebrew channels I've used over the years (including the RunningSnakes WAD I used to set this up). I've taken a screenshot for reference.

Are there options I'm missing, or is another tool needed to iron these out?

 

[XFlak]

Grab modmii, start modmii classic, go to the advanced downloads page, select the option to build a forwarder dol. Then inject the resultant output dol into your wad using customize mii

 

[Dainslaif]

Grab modmii, start modmii classic, go to the advanced downloads page, select the option to build a forwarder dol. Then inject the resultant output dol into your wad using customize mii

That worked perfectly - thank you!

(and thanks for all your work on modmii over the years)

 

[ReveriePass]

Anyone have any further instructions for this? Creating a DOL file using ModMii and injecting it into my WAD using CustomizeMii isn't working.

 

[XFlak]

Should be working, if it’s not it could be you made a mistake, or it could be that app being forwarded to doesn’t like this forwarder. To test the latter, try forwarding to a known working app like usbloader_gx. So for example let’s say you built a forwarder for app\appname\boot.dol and it’s not work, renaming appname to something different, then rename the usbloader_gx folder to appname (temporarily just to test). So then when you launch your forwarder it will still be pointing to app\appname\boot.dol, but the dol it’s finding is for GX. If you can load GX, but not the app in question, you could try taking the pre-compiled v14 forwarder dols (ModMii builds v12 dols) from here (https://gbatemp.net/threads/pre-compiled-tested-v14-forwarder-dols-for-loaders-apps-emus.339944) and hex editing them with a new path. The v14 dols have 2 flavours of forwarders (Waninkoko and Comex), try both (I don’t recall which was used for v12, but you may have luck with the other). When hex editing, be sure that the new path is either equal or less than the number of characters of the old path, and just nul out any extra characters left over from the old path.

Another thing you could try is just loading the forwarder dol via the hbc (i.e. before injecting it into a channel) to confirm whether or not the issue is with the dol or the channel.

Good luck!

 

[SaulFabre]

Should be working, if it’s not it could be you made a mistake, or it could be that app being forwarded to doesn’t like this forwarder. To test the latter, try forwarding to a known working app like usbloader_gx. So for example let’s say you built a forwarder for app\appname\boot.dol and it’s not work, renaming appname to something different, then rename the usbloader_gx folder to appname (temporarily just to test). So then when you launch your forwarder it will still be pointing to app\appname\boot.dol, but the dol it’s finding is for GX. If you can load GX, but not the app in question, you could try taking the pre-compiled v14 forwarder dols (ModMii builds v12 dols) from here (https://gbatemp.net/threads/pre-compiled-tested-v14-forwarder-dols-for-loaders-apps-emus.339944) and hex editing them with a new path. The v14 dols have 2 flavours of forwarders (Waninkoko and Comex), try both (I don’t recall which was used for v12, but you may have luck with the other). When hex editing, be sure that the new path is either equal or less than the number of characters of the old path, and just nul out any extra characters left over from the old path.

Another thing you could try is just loading the forwarder dol via the hbc (i.e. before injecting it into a channel) to confirm whether or not the issue is with the dol or the channel.

Good luck!

@XFlak Agreed.

Another thing you could try is making an new forwarder DOL and inject into an correct WAD compatible with AHBPROT. You could try also changing the Nandloader used in the WAD.

You can read the points THIRD STEP – MAKING THE DOL FORWARDER WITH meta.xml SUPPORT and SIXTH STEP – INSERTING THE .dol FORWARDER DOL AND CUSTOMIZING/EDITING THE FORWARDER WAD in this tutorial: https://gbatemp.net/threads/how-to-...ls-of-your-favorite-retro-games-d-wii.602640/

Greetings