Hacking USB Loader GX

  • Thread starter Thread starter blackb0x
  • Start date Start date
  • Views Views 8,069,896
  • Replies Replies 30,226
  • Likes Likes 74
Hi, I have the same issue.
The earlier test version was giving me the stable message. I checked date and time and these were ok (or need the date and time be in a certain range?).
Then I checked the github and saw the new release of 4 hours ago, and installed that one. Now I see the colored bars as well. However I hear the music of the menu I configured, so apart from the screen it seems to get into USB Loader GX again.

I was having a similar issue, I just updated and got a black screen when booting a GameCube game but the audio was working, pressed the home button to go back to USB Loader but the screen remained black. I turned off the console, loaded USB Loader again, and went to Loader settings, the video mode for Nintendont was set to Auto, I changed it to System default and now the game boots like normal, but then I tried setting it back to Auto and it still works, so there's either some sort of issue with the video mode settings or with the Loader itself when booting for the first time. In any case my issue seems to be fixed.

I'm using a Wii U with an HDMI cable.
 
Just hooked my Wii via component and set it to 480p. Same result.
 

Attachments

  • PXL_20250625_182352645.jpg
    PXL_20250625_182352645.jpg
    2.4 MB · Views: 21
Are you also using a composite cable or scart cable?

I'm using a component and my Wii is set to 480p, so I don't see any issues. But I suspect that one of these commits is what's caused this.

https://github.com/devkitPro/libogc/commit/52c525a13fd1762c10395c78875e3260f94368b5
https://github.com/devkitPro/libogc/commit/cefe2928349645d709d21d74fd6f98d7c7b1d6f8
https://github.com/devkitPro/libogc/commit/78c8b46ef4c76a0575ef510a0c89f6c6281a7b50
https://github.com/devkitPro/libogc/commit/4b3240bde9c20371c5a044e51d2b1055ea05e454
https://github.com/devkitPro/libogc/commit/9bb07e55bd00ac94664363bba3580a2e524582f9

If I can find my composite cable I'll hopefully be able to recreate the issue. Then I can figure out what's causing it.

If you downgrade to r1281 for the time being you might need to go to Features Settings and select Reset Cached Titles. Otherwise your cached list of games might be showing garbage.
I only have an HDMI adapter and have already reseated it with same results.
 
Well, the good news is that I've found an old mini TFT gaming screen that shows the same issue. So I can debug this.

I've got a hell of a headache right now, but I'll try to get this fixed ASAP.
No worries dude, you have already done so much. Thank you for your work. r1281 will do just fine for the time being.
 
  • Like
Reactions: alcab and XFlak
Well, the good news is that I've found an old mini TFT gaming screen that shows the same issue. So I can debug this.

I've got a hell of a headache right now, but I'll try to get this fixed ASAP.
Good to hear you are able to reproduce. But get well soon first! No hurry.
 
Hey guys, I'm new to Homebrew / USBloadergx and I've been using it for a month now flawlessly until today. It says "Loading Please install the stable version" and Im running on r1282. I see you guys on here mentioning things going on but I want to make sure it's not just a me thing and I'm not going crazy.

EDIT: Just checked Homebrew and saw the update and it works so far with no problems. I'll respond back here if I find anything. Shout out blackB0x
 
Last edited by RentalMussel,
I ran into this problem just now as well 😭. I downloaded the stable version that was just uploaded today on the github. What I did was delete the usbloadergx folder in the app directory and replaced it with the new one from this github. Now when I load usbloadergx, I get an exception. Are there additional steps to doing the install?

Edit: Also tried updating it from the homebrew browser and it still crashes
 

Attachments

  • IMG_0277.jpeg
    IMG_0277.jpeg
    2.7 MB · Views: 23
Last edited by realpkmnmaster,
I ran into this problem just now as well 😭. I downloaded the stable version that was just uploaded today on the github. What I did was delete the usbloadergx folder in the app directory and replaced it with the new one from this github. Now when I load usbloadergx, I get an exception. Are there additional steps to doing the install?
The crash info seems to hint that it's got something to do a file or folder in your wbfs directory.

Is your drive using MBR with a single FAT32 partition? And if you temporarily rename your wbfs folder to something else does the loader boot correctly?
 
The crash info seems to hint that it's got something to do a file or folder in your wbfs directory.

Is your drive using MBR with a single FAT32 partition? And if you temporarily rename your wbfs folder to something else does the loader boot correctly?
Thanks for the reply! My wbfs folder is actually in my hdd. When I remove the hdd from the wii, it boots up correctly, so I think you’re onto something. My hdd is NTFS instead of FAT32 because I don’t have Gamecube games and I don’t want to deal with partitioning for Wii games over 4 gb. Could it be that? All I have in the hdd is my wbfs folder.

Renaming the wbfs folder to something else still crashes
 
Last edited by realpkmnmaster,
My hdd is NTFS instead of FAT32 because I don’t have Gamecube games and I don’t want to deal with partitioning for Wii games over 4 gb. Could it be that? All I have in the hdd is my wbfs folder
Are your file and folder names under 260 characters, like they would be with FAT32?

Ideally you should have a file layout like this...
Code:
/wbfs/Mario Kart Wii [RMCP01]/RMCP01.wbfs
You could try to copy a few files with short titles to a new wbfs folder, try the loader, and then repeat that until you weed out the problematic ones.

I plan to drop NTFS support when I release the next big update. And in it's place will be exFAT support.
 
Last edited by blackb0x,
The crash info seems to hint that it's got something to do a file or folder in your wbfs directory.

Is your drive using MBR with a single FAT32 partition? And if you temporarily rename your wbfs folder to something else does the loader boot correctly?
I also have the same issue. I get a crash within like 3 seconds of the actual user interface coming on . If my hdd isn’t plugged in the program will start. I have two partitions (, NTFS for Wii, Fat32 for GameCube) and it works on pervious versions decent. I’ve gone through removed usb loader and reinstalled it and reset defaults and same problem.
Post automatically merged:

The crash info seems to hint that it's got something to do a file or folder in your wbfs directory.

Is your drive using MBR with a single FAT32 partition? And if you temporarily rename your wbfs folder to something else does the loader boot correctly?
I also have the same issue. I get a crash within like 3 seconds of the actual user interface coming on . If my hdd isn’t plugged in the program will start. I have two partitions (, NTFS for Wii, Fat32 for GameCube) and it works on pervious versions decent. I’ve gone through removed usb loader and reinstalled it and reset defaults and same problem.
 

Attachments

Are your file and folder names under 260 characters, like they would be with FAT32?

Ideally you should have a file layout like this...
Code:
/wbfs/Mario Kart Wii [RMCP01]/RMCP01.wbfs
You could try to copy a few files with short titles to a new wbfs folder, try the loader, and then repeat that until you weed out the problematic ones.

I plan to drop NTFS support when I release the next big update. And in its place will be exFAT support.
Okay cool! It loads up normally when I add a few games with short names. I don’t see any folders/files with paths that are over 260 though. The longest would probably be maybe 60 characters. I’ll probably have to weed it out like you mentioned. Big thanks for the help!
 
If either of you are able to pin point the issue then I'll try to replicate it and release a hotfix.

If longer than normal paths don't seem to be the issue then what about empty folders or files with the wrong file extensions assigned?

I've got to get some more sleep, but I'll check for replies later.
 
  • Like
Reactions: jeannotte and XFlak
If my wii is not connected to the internet, how did the app knew there was a new stable release? i downloaded it like 2 months ago. Did you plan the release date as early as you made the beta public and programmed the app to show the message on june 25?
 

Site & Scene News

Popular threads in this forum