Homebrew Some WADs on USBLoaderGX show the "An Error Has Occurred" screen.

[ZodiaKGalXy]

Greetings viewer!

I have used USBLoaderGX for two years and I've only seen this issue recently, I believe it was the beginning of July. When I load a WAD File that was already installed on USBLoader GX or a recently added WAD to the program using the EmuNAND Wad Manager, the Wii console flickers blue in the disc slot, and then shows a black screen with the following text:

An error has occurred.
Press the eject button, remove the Game Disc, and turn the power OFF.
Please read the Wii Operations Manual for more information.

Here is a video, recorded from my iPhone, converted into a GIF file showing the exact situation with the "Art of Balance" WAD, additionally with some of my other installed WADs in the background:

The strange part is that because it's a WAD file, there is no Game Disc to eject as it's not a disc! So how could something like a WiiWare title, or WAD file in general, cause an error meant for a game disc? This error even shows up if there wasn't a game disc already in the disc slot.

I've noticed that it wasn't just WiiWare titles that showed this error, but Wii Channels that weren't installed on my Wii Menu, which are the "Wii and the Internet" channels from Europe / Japan, and the Hulu Plus Download Assistant. The North American "Wii + Internet" channel still works, and it wouldn't mean that it's a region problem as the other two worked fine before the error occurred. Official Virtual Console titles, on the other hand, just show a black screen with no text. Some of the Virtual Console titles that I've created show the same message. WBFS Wii games don't show the error and work very well. GameCube games don't need any speculation as I play it off of Nintendont.

It's also worth noting that I haven't checked all of my 90 WAD Files stored on my USB Stick, as I don't really have the energy to force shutdown my Wii and load USBLoader GX over and over again just to check a single WAD file. So, I assume the majority of them show this error, with a few exceptional games and channels that were lucky to not show the error. I also know that the WADs aren't corrupt, as they work fine when installed on the Wii Menu (I use YAWM ModMii Edition).

Here are some technical specks:
1: I have USBLoader GX v3.0 Rev.1281 (e25c4e9).
2: I have 16.1GB of free space left on my 64GB Fat 32 Formatted USB Stick.
3: I have a stable mesh Wi-Fi connection optimized for best preforming internet on the Wii.
4: I have made a copy of a SYScheck report in advance, for anyone who wants to review it.

SYSCheck Info:

Spoiler

SysCheck ME v2.5.0 by blackb0x JoostinOnline Double_A R2-D2199 and Nano
...runs on IOS58 (rev 6176).

Region: NTSC-U
System Menu 4.3U (v513)
Priiloader installed
Drive date: 07.14.2008
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x21
Console ID: 99494143
Console Type: Wii
Shop Channel Country: Canada (18)
Boot2 v4
Found 146 titles.
Found 56 IOS on this console. 10 of them are stubs.

IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 54321): Trucha Bug
IOS10 (rev 768): Stub
IOS11 (rev 54321): Trucha Bug
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 54321): Trucha Bug ES Identify Flash Access NAND Access
IOS17 (rev 1032): No Patches
IOS20 (rev 54321): Trucha Bug
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 54321): Trucha Bug
IOS31 (rev 3608): Trucha Bug ES Identify NAND Access
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 54321): Trucha Bug ES Identify NAND Access
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 54321): Trucha Bug
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 54321): Trucha Bug
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 54321): Trucha Bug
IOS80 (rev 54321): Trucha Bug
IOS90 (rev 54321): Trucha Bug
IOS202[60] (rev 65535 Info: hermesrodries-v6): Trucha Bug NAND Access USB 2.0
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS224[57] (rev 65535 Info: hermesrodries-v6): Trucha Bug NAND Access USB 2.0
IOS236 (rev 54321): Trucha Bug ES Identify NAND Access Beer Ticket
IOS245[37] (rev 21008 Info: d2x-v8final): Trucha Bug NAND Access USB 2.0
IOS246[38] (rev 21008 Info: d2x-v8final): Trucha Bug ES Identify NAND Access
IOS247[53] (rev 21008 Info: d2x-v8final): Trucha Bug NAND Access USB 2.0
IOS248[55] (rev 21008 Info: d2x-v8final): Trucha Bug NAND Access USB 2.0
IOS249 (rev 65280): Stub
IOS250 (rev 65280): Stub
IOS251[58] (rev 21008 Info: d2x-v8final): Trucha Bug NAND Access USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 07/25/2024.

If anyone has experienced this error before and wants to share their ideas, theories, or solutions of how to solve, YOUR support will be very much appreciated!

Thanks in advance,
ZodiaKGalXy

 

[XFlak]

Your cios249 and 250 are stubbed. Drag and drop your syscheck.csv onto modmii.exe and it will tell you what to do

 

[ZodiaKGalXy]

Your cios249 and 250 are stubbed. Drag and drop your syscheck.csv onto modmii.exe and it will tell you what to do

Hey. So I took your advice and installed the WADs required from BootMii on my SD Card (and USB Stick just in case) and installed them and the STUBS with YAWM ModMii Edition. USBLoader GX is still operating. However, it doesn't recognize my FAT32 formatted USB Device whether I put it in Port 0 or 1. It then turns to the screen error stating: "USB Device Not Initialized, switching to channel list mode."

My WiiMote is unresponsive once that happens, but the good news is that I still can communicate with the application with a GameCube controller. However, no matter when I press A to enable SD Card mode, press B to cancel or wait for HDD, I get that message. Followed by a "Could not initialize DIP module!" error when pressing the OK button.

What are my next steps?

(Until the issue is resolved, I will use WiiFlow as an alternative option for now.)

 

[XFlak]

GX doesn't have the greatest compatibility with flash drives, Wiiflow and cfg usb loader may work better

Alternatively you can improve usb compatibility if u format it as wbfs instead of fat32, but it comes with a bunch of other cons that would be listed in your modmii usb loader setup wizard guide

And make sure you're using the latest version of your usb loader. If you use homebrew browser or drag and drop your USB or sd card onto modmii.exe it can help u check for updates

 

[ZodiaKGalXy]

GX doesn't have the greatest compatibility with flash drives, Wiiflow and cfg usb loader may work better

Alternatively you can improve usb compatibility if u format it as wbfs instead of fat32, but it comes with a bunch of other cons that would be listed in your modmii usb loader setup wizard guide

And make sure you're using the latest version of your usb loader. If you use homebrew browser or drag and drop your USB or sd card onto modmii.exe it can help u check for updates

Hello again. What I discovered is really interesting!

I did some experimenting with making a backup copy of all the files contained in the usbloader_gx folder onto my computer. Then I deleted all of the original content from my USBLoader GX on the USB Stick with a fresh one. I also tried it on my SD Card where data can still be stored on the USB. I will note again that it is USBLoader GX v3.0 Rev.1281 (e25c4e9), the latest update according to the GitHub page of the app. It worked on the SD Card without having trouble when preparing to load or giving errors mentioned before, and it seemed to initialize my USB Stick as well!

Redownloading a fresh USBLoader GX for the SD Card resolves the issue I once had. However, with that being said, transferring the files from the backup copy back to the fresh USBLoader GX gives the same error results from before.

I theorize based on my test results that it isn't the flash drive that was the issue, as nothing seems to be wrong with the FAT32 formatted drive. Rather it could be the files from the USBLoader GX backup folder or the EmuNAND Channel Folder that is causing the "USB Device Not Initialized" error and "Could Not Initialize DIP Module" error, or the previous "An error has occurred, Press the eject button, remove the Game Disc, and turn the power OFF" error. Some cause, bug, or corruption must have been executed inside the files from the backup usbloader_gx folder that gave me those two errors when it's on the USB Stick. Therefore the only solution to that problem was to get a new installation of the loader either on the USB Stick or SD Card, and that's why it worked.

To be sure that it was working from the SD Card I tested out a WBFS game (Mario Kart Wii Deluxe Green v8.1) and a WAD file (Art of Balance). They worked, no failures whatsoever!

The only issues I have is that the banners showing from the SD Card are blank. The USB Stick is still showing the "An error has occurred, Press the eject button, remove the Game Disc, and turn the power OFF" error. But I'll try to rerun the WADs from BootMii just in case. Or another system check. The Disc channel also seems to be asking for a Wii System Update after installing the WADs, is there anything I should know about when it does that?

Regardless, so long as it's working on the SD Card and that data is being saved to the USB Stick, I'll be happy for now. If anything, I can use the SD Card for WiiWare, and then the USB for Wii games. Or I can simply get another USB Stick and try to format the drive again.

Would you like me to attach the backup folder of my USBLoader GX for further inspection (unless that can be forwarded to someone else)? Or is everything all good by now?

Post automatically merged: Jul 27, 2024

Yk... This whole issue started because I was simply installing WADs to the program. Would removing every single WAD file from the original backup of USBLoader GX or EmuNAND Channel Folder end the issue as well. Or is the issue all based on stuff within the IOSs in my Wii?