Hacking USB Loader GX

  • Thread starter Thread starter blackb0x
  • Start date Start date
  • Views Views 8,061,947
  • Replies Replies 30,225
  • Likes Likes 74
The weirdest part is that it didn't use to be a problem before I tried to update the loader or use an SSD drive, something seems to have started the issue, between those two things.
If the loaders located on an SD card delete the apps/usbloader_gx folder and install a fresh copy.

I'll send you a copy of the latest test version, just in case one of my recent fixes ends up resolving the issue for you.
 
It'll work now. I'd just got busy working on a few things.


You did see this part and created the new EmuNAND via the loader, right?



I created a new EmuNAND, installed the WAD file through the loader, and everything is working as expected with the loaders default settings.

castlevania-png.491356


Make sure these settings are correct...
  • Video Mode: Disc Default
  • Dol Video Patch: OFF
  • Game Language: Console Default
  • Game IOS: Auto
  • EmuNAND Save Mode: OFF or Partial
  • EmuNAND Channel Mode: Full

When it's setup and working correctly, it's compatibility is so good that it can play some games that neek/sneek can't.
Yeah I dumped the nand with USBLoader. I checked the settings above and the only difference was the emunand save mode, which I had set to FULL. I now changed it to partial (what does that mean anyway?). But Castlevania still doesn't run. I just get a black screen after the Konami logo. Paper Mario N64 also doesn't work.
I even tried a fresh third nand dump, but no luck.
That only things I can imagine that is problematic might be that the wads are for US consoles and I have a PAL one. But other US games work. And for Paper Mario I tried both US and EUR installs with no difference: It say I need the classic controller and after a while the console just hangs and I have to turn it off.
Strange.
 
But Castlevania still doesn't run. I just get a black screen after the Konami logo. Paper Mario N64 also doesn't work.
Ah, it seems like you've missed an important step. Notice it says this in the first post...

I highly recommend updating to d2x-v11-beta3, as it drastically improves WiiWare and Virtual Console game compatibility, especially when your games are installed to an EmuNAND.
And both of the games you mentioned are ones that don't work with d2x-v11-beta1 and older.

https://github.com/wiidev/d2x-cios/releases
 
I've updated everything according to the first post. 248,249,250 and 251 have dx2-v11-beta3 installed.
Please share a SysCheck.

I downgraded to d2x-v1-beta1 and that's when I was able to replicate the exact issue, where the game froze after the Konami logo. But with d2x-v11-beta3 installed into all 4 slots it worked.
 
Here you go:
SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: PAL
System Menu 4.1E (v450)
Priiloader installed
Drive date: 05.26.2006
Homebrew Channel 1.1.0 running on IOS58

Hollywood v0x11
Console ID: 68456528
Console Type: Wii
Shop Channel Country: Germany (78)
Boot2 v4
Found 166 titles.
Found 54 IOS on this console. 5 of them are stubs.

IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40[60] (rev 65535, Info: rev 6174): Trucha Bug
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[60] (rev 65535, Info: rev 6174): 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 65535, Info: rev 6174): Trucha Bug
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS80[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS202[60] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 65535, Info: hermes-v5.1): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[37] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS236[36] (rev 65535, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
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[38] (rev 65535, Info: d2x-v11beta3): Trucha Bug, ES Identify, NAND Access
IOS249[56] (rev 65535, Info: d2x-v11beta3): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 65535, Info: d2x-v11beta3): Trucha Bug, NAND Access, USB 2.0
IOS251[58] (rev 65535, Info: d2x-v11beta3): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10 (DIOS MIOS Lite 2.11+)
Report generated on 07/12/2025.
 
  • Like
Reactions: blackb0x
If the loaders located on an SD card delete the apps/usbloader_gx folder and install a fresh copy.

I'll send you a copy of the latest test version, just in case one of my recent fixes ends up resolving the issue for you.
I tried deleting the usbloader_gx folder and installing a fresh copy of the latest test version you sent me. This one seems more stable than the regular r1283, similar to the regular r1281.

I'm almost positive that it only crashes if I use the banners menu.
 
Last edited by KungBore,
Here's the problem:
Code:
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
Castlevania requests IOS53 and you've got a cIOS with an exact match, so the loaders selecting it.

If you install Wii Mod Lite and select IOSs then you can delete slot 245, 246 and 247.

And I was talking to XFlak about this privately a while ago, but I should probably add a setting that restricts automatic cIOS selection to slots 248, 249, 250, and 251 by default. That way the loaders less likely to select outdated cIOS.

I'm almost positive that it only crashes if I use the banners menu.
The problem there is that I didn't change any banner code in any meaningful ways. And it'd be a widespread issue if it was buggy.

While using the new test build please try to get a picture of the crash.
 
  • Like
Reactions: ecto and XFlak
Here you go:
SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: PAL
System Menu 4.1E (v450)
Priiloader installed
Drive date: 05.26.2006
Homebrew Channel 1.1.0 running on IOS58

Hollywood v0x11
Console ID: 68456528
Console Type: Wii
Shop Channel Country: Germany (78)
Boot2 v4
Found 166 titles.
Found 54 IOS on this console. 5 of them are stubs.

IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40[60] (rev 65535, Info: rev 6174): Trucha Bug
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[60] (rev 65535, Info: rev 6174): 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 65535, Info: rev 6174): Trucha Bug
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS80[60] (rev 65535, Info: rev 6174): Trucha Bug
IOS202[60] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 65535, Info: hermes-v5.1): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[37] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS236[36] (rev 65535, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
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[38] (rev 65535, Info: d2x-v11beta3): Trucha Bug, ES Identify, NAND Access
IOS249[56] (rev 65535, Info: d2x-v11beta3): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 65535, Info: d2x-v11beta3): Trucha Bug, NAND Access, USB 2.0
IOS251[58] (rev 65535, Info: d2x-v11beta3): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10 (DIOS MIOS Lite 2.11+)
Report generated on 07/12/2025.
I'm guessing your cios 245-247 may be interfering with GX's auto ios setting/selection. You could manually set the game ios, but better to just erase what you have in those slots and try again. U can CAREFULLY do this manually using Wiimod lite or any title deleter, but easier to just drag and drop your syscheck.csv onto modmii.exe and it will tell you what to do. Modmii will also help u update a few other things, like update your hbc (which is also outdated)

Edit: blackb0x beat me to it by 1 minute! Lol
 
  • Like
Reactions: blackb0x and ecto
Here's the problem:
Code:
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
Castlevania requests IOS53 and you've got a cIOS with an exact match, so the loaders selecting it.

If you install Wii Mod Lite and select IOSs then you can delete slot 245, 246 and 247.

And I was talking to XFlak about this privately a while ago, but I should probably add a setting that restricts automatic cIOS selection to slots 248, 249, 250, and 251 by default. That way the loaders less likely to select outdated cIOS.


The problem there is that I didn't change any banner code in any meaningful ways. And it'd be a widespread issue if it was buggy.

While using the new test build please try to get a picture of the crash.
I tried the regular r1283 again and can confirm that it only crashes if I change to the banner menu. I'll get a pic of the crash.

Edit:

1752344010178.png
 
Last edited by KungBore,
If you've already got an older version of the USB loader GX (UNEO) forwarder installed then the update would replace it. So no, you don't need to uninstall it.
well, i already have the usb gx forwarder, but...what does it means "UNEO" ? Please can you tell me how to understand if my forwarder has this specification?
thanks!
 
I went for the Modmii route and deleted all outdated IOSs.
I can say that everything is now working perfectly (without any neek)! Thanks @XFlak and @blackb0x!
One thing I noticed: when I start Paper Mario PAL everything is fine. When I start the US version I have to set the video mode to Force NTSC or otherwise the sound will play choppy.
 
  • Like
Reactions: blackb0x and XFlak
is the freeze on the "reinitializing devices" caused by the hard drive or the enclosure? i'm using a wd blue 500gb drive and a gloway g21u3 enclosure
 
hi, i have just almoest completed the update to the latest version.

I have'nt updated the USB loaded forwarder yet. I already have the usb gx forwarder as i used it with the older USB loader version. I read that i can simply overwrite it using the latest wad file, right? Well, running YAWMM, the first screen i see is this:
https://i.postimg.cc/rmtBW6rZ/Whats-App-Image-2025-07-13-at-10-10-06.jpg
and then:
https://i.postimg.cc/vTFptP7Y/Whats-App-Image-2025-07-13-at-10-10-06-1.jpg
and:
https://i.postimg.cc/8zPx4fv6/Whats-App-Image-2025-07-13-at-10-10-06-2.jpg

Are the settings in my screenshots correct? Considering that i have all my Gamcube and Wii games into my SD card, so i'm using USB GX loader loading games from that support. Or do i need to change any settying before to overwrite the .wad file?

Thank you very much
 
Last edited by legolas119,
@blackb0x

Thanks for adding support for the notorious Metafortress protected Driver San Francisco, I can now finally play it without no loading hangs (completing the parking lot tutorial) instead of using the original disc.
 
Its caused by the enclosure WD blue drives have always worked for me.
I was able to get into USB Loader GX without plugging in the HDD. Then, I initialized the HDD through the settings in version 1281 and it worked. But I had to redo the process every time I wanted to launch the loader. However, after updating to v1283, that method no longer works... Do you have any idea on this?
Post automatically merged:

Its caused by the enclosure WD blue drives have always worked for me.
By the way, which enclosure are you using? I've ordered an Orico 2139U3, but I'm still skeptical about the auto-sleep feature.
 
That's going to be a problem, since the crash happens in libogc, with nothing tracing back to the loader.

Do you have any custom Wii games on your drive? If you do then I'd start by removing them to see if it fixes the issue.

If that doesn't work, I'd suggest renaming your current wbfs folder, then creating a new one, moving a few games over at a time and then trying the loader. And if you do it in alphabetical order, it will be easier to roll back changes once the crashes start again.

well, i already have the usb gx forwarder, but...what does it means "UNEO" ? Please can you tell me how to understand if my forwarder has this specification?
Go into Loader Settings, select Return To and see if UNEO is listed there.

Well, running YAWMM, the first screen i see is this
You'd be better off using YAWM-ME.

But yeah, them settings would work.

Thanks for adding support for the notorious Metafortress protected Driver San Francisco, I can now finally play it without no loading hangs (completing the parking lot tutorial) instead of using the original disc.
You're welcome :)

I was able to get into USB Loader GX without plugging in the HDD. Then, I initialized the HDD through the settings in version 1281 and it worked. But I had to redo the process every time I wanted to launch the loader.
It sounds like your USB enclosure has a buggy controller, so when the cIOS attempts to perform a read for the first time it'll return something unexpected.

With the drive disconnected, go into Loader Settings and set Loaders IOS to 250, 251, or 58. Then exit the app, reconnect your USB drive, and try it out.

My suggestion might help, but some games might not boot correctly with automatic cIOS selection enabled due to your buggy controller. And using IOS 58 might cause issues if you let the loader idle and your drive goes to sleep.

By the way, which enclosure are you using?
Any cheap enclosure with a JMS578 chipset is guaranteed to work with the cIOS, and I believe the Orico 2139U3 you've ordered uses that exact chipset.

EDIT: Orico changes the chipsets used in their enclosures over time. So if you order a 2139U3, it might not come with the JMS578 chipset.

Maybe look on AliExpress or Amazon for something that specifically says it uses the JMS578 chipset, or just take a gamble on something else.
 
Last edited by blackb0x,
It sounds like your USB enclosure has a buggy controller, so when the cIOS attempts to perform a read for the first time it'll return something unexpected.

With the drive disconnected, go into Loader Settings and set Loaders IOS to 250, 251, or 58. Then exit the app, reconnect your USB drive, and try it out.

My suggestion might help, but some games might not boot correctly with automatic cIOS selection enabled due to your buggy controller. And using IOS 58 might cause issues if you let the loader idle and your drive goes to sleep.


Any cheap enclosure with a JMS578 chipset is guaranteed to work with the cIOS, and I believe the Orico 2139U3 you've ordered uses that exact chipset.
thanks so much for your help! i'll wait for my package to arrive and test it
 
  • Like
Reactions: XFlak
Go into Loader Settings, select Return To and see if UNEO is listed there.


You'd be better off using YAWM-ME.

But yeah, them settings would work.
Done! Well, it works, but i'm trying some Wii games, and they have issues (my games are into the SD), for example:

Mario kart Wii: black screen when i select it, and then it returns to the Wii menu. I'm quite sure that it worked with the previous USB loader gx version.

Klonoa: when i load the game, it appears a black screen and the console freezes. I have to remove the power... I know that i have to set PATCH VIDT = ON, it worked into the previous version, but with the new one no...does it require a specific settings?

Is it available a repository with the recommended settings for games that require them?
I still have my previous USB LOADER GX folder, is it possible to understand the specific settings for games that i had?
 

Site & Scene News

Popular threads in this forum