Hacking USB Loader GX problems.

[Eguin]

So I've been using USB Loader GX for about a year and usually everything goes smoothly and I'm able to play games fine.

I recently tried playing Monster Hunter Tri and it's a bit weird. I know there's been a lot of threads that say to switch to ios 222 or 223 and I've tried that and still it's not working.

The issue I'm having is that the channel for Monster Hunter is blank even though all the other ones have images of the game. If I keep the cursor over it it says the game's monster hunter tri but there's no image and no sound when i click the channel. If I try to play the game is just sends me back to the homebrew channel.

I've tried playing the game with wanikoko's 249, d2x, hermes 222 and 223 and nothings worked. I think the problem might be different then the wrong ios since the channel isn't loading correctly.

The Monster Hunter wbsf I think is good since I'm able to play it on dolphin.

Does anybody know any fixes? Thanks in advance

 

[GreyWolf]

MH3 should work just fine with d2x v8 or v10 with base 56. (Make sure you aren't using v10-beta53-alt!)

Not having a banner would point towards it being a bad rip or otherwise corrupted disc image. Wii Backup Manager has a SHA1 calculating feature that can tell you if the game partition is good. When it's done a green title indicates it's good, red means it's bad.

 

[Eguin]

Thanks for getting back to me!

Ok so previously I had d2x v6 installed with base 37 (I think)
I just switched to d2x v10 beta 52 rev21010 on ios 249 and the same problem is still there. To make sure the ios worked I did test it with a few other games and they work fine.

In terms on Wii Backup Manager: since I have a Mac I wasn't able to find Wii Backup Manager for it. I got an app called witgui, and when i verified the wbfs it said that it was successful. I'm not sure if this matters but I'm also able to play the wbfs on dolphin.

Do you have any more suggestions? Thanks!

 

[GreyWolf]

Hmm. Maybe @Cyan might have an idea why it's not reading the banner from the disc image. Can you check and make sure the wbfs file isn't marked as read-only, maybe?

 

[Eguin]

I didn't even know wbfs could be read only.
I'm able to move the file to the trash and delete it, so I don't think it's read only...

Thanks

 

[Cyan]

if the loader displays a black animated banner, it's usually symptom of a corrupted game.
if you have Wit, you can check the game's checksum, or Sha1 to verify it's good or corrupted.

I think Eguin in using a WBFS partition, not a FAT32+wbfs files, so there's no read-only problem.
if you use FAT32, then be sure the game file's attribute is not set to read only.


As for the IOS to use, you need a IOS based on IOS56 (or probably 57 too).
so, update d2x if you still use old cIOS rev17 to 21.
use d2x v8 final base56 in slot 249 to prevent the game from freezing after the intro.

 

[Eguin]

Thanks for all the replies!

using witgui (which uses wit) I verifies the wbfs and the iso it came from and they were both good, so I don't think it's that (though maybe I'm wrong, I clicked verify and it said "everything seems to be fine")

I actually am using fat32 (meaning by usb is formatted to fat32) and wbfs files, but I double checked the files the wbfs it's in and the wbfs itself and I can read and write both of them

I still need to switch to to d2x v8 rev 21, I'll try that when I get back home

 

[Eguin]

Ok so I installed the cios (d2x v8 rev 21 base 56) and it didn't help the problem.

Any other suggestions? the channel of it is still blank

 

[Cyan]

the animated banners are cached on your SD or USB to load faster.
it's extracting a binary file the first time it sees a new game, then uses the file from your /apps/usbloader_gx/bnr_cache/ (or a name like that)
So, maybe it didn't extract the banner correctly.

You can :
- delete the cached banner manually (go to that folder and delete the file with the titleID of monster hunter)
or
- disable banner caching option in the settings>Banner menu and reboot. see if it can read the banner when read directly from the game's wbfs file. but don't forget to set it back to ON or it will re-extract all your banners from ISO every time.


Though, I still think your game ISO is wrong, because you have two issues :
the banner AND the game not working.
if it was only a caching issue, the game would work.
If it was a setting, it would boot but freeze or crash. What you have is "reboot to system menu" which is a symptom of "file can't be found or opened".


How did you verified that the file and folder were in read/write mode?
the folder, I understand, but did you check the file's attribute? (both of them if you have more than one)

 

[Eguin]

I tried both your suggestions (first I deleted it on the SD card and it didn't work, then I tried disabling Cache BNR Files and rebooting) and neither of them helped.

I see where you're coming from with the iso being wrong, is that possible? I tried the iso with dolphin and it worked, and I also verified it with wit. I'll try it with a new iso and see how that goes.
And when i say iso I mean the iso that i converter to wbfs, I never use iso's on by usb (it's too big a file for fat32, though I'm not opposed to reformatting)

In terms for making sure the file is in read/write mode, there's a little thing on the bottom of the get info on folders that says the permissions. I checked the USB, the WBFS folder, the MH3 Folder, and the wbfs file itself (there's only 1), and they all say it's read and write.

 

[Cyan]

that's not the read/write you should care of.
That one is for folder network sharing permission, not FAT32 file access attribute.
your option affects folders only, what you need to verify is the file's attribute.

on Windows, when you right-click on a file (or folder to affects all files in that folder), you can choose "properties"
in the properties windows, you have two option called :
- Read only
- Hidden files
(there's another for Archives or system, probably in "advanced..." option)
example with the file "hosts" :

Spoiler

For macOS : https://apple.stackexchange.com/questions/248333/how-to-change-fat32-file-attributes-under-os-x
https://superuser.com/questions/656826/command-line-tool-to-edit-fat-fat32-attributes-on-mac-os-x

Last time someone had issue with the read-only option enabled, I think the game just stayed on a black screen, the console didn't reboot to sysmenu.
But maybe it's another possible symptom.
At least, if you can verify that file's attribute then we can exclude that from the possible cause.

 

[Eguin]

Ok I understand what you're saying now.

I have no idea how to do it on a mac but my friend let me borrow his windows, so I did what you said, it didn't have read only clicked

I also clicked the advanced settings, I don't really know what it means, I assume "ready for archiving" is good, but I'll post it also in case there's an issue with that.

Assuming everything there is ok, do you know of any other possible causes?

 

[tswntk]

to eliminated other possible causes, lets go back to the basis:
1. post a syscheck log of your system to verify you really have the correct cios setup - you can find a tutorial from Cyan's signature
2. take a photo of the USB Loader GX's credit page to see if you are using the correct versions and cios
3. Dolphin is an emulator, it work differently from the real console so that doesn't really count but can you see the proper game icon from its browser list of the game (from the sane storage device you used on the Wii)? Right click the game>select "properties">"Filesystem">right click partition 1>select "check partition integrity". Anything wrong points to your wbfs being bad

 

[Eguin]

Thanks for helping!

1. Ok here's the system check

Spoiler

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

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

Hollywood v0x11
Console ID: 51179892
Console Type: Wii
Shop Channel Country: Venezuela (52)
Boot2 v4
Found 108 titles.
Found 59 IOS on this console. 4 of them are stubs.

IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 16174): Trucha Bug, NAND Access
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 (rev 16174): Trucha Bug, NAND Access
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 16174): Trucha Bug, NAND Access
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 16174): Trucha Bug, NAND Access
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 14889): Trucha Bug, NAND Access
IOS51 (rev 4864): Stub
IOS52 (rev 15661): Trucha Bug, NAND Access
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 16174): Trucha Bug, NAND Access
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 16174): Trucha Bug, NAND Access
IOS80 (rev 16174): Trucha Bug, NAND Access
IOS200[58] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS201[37] (rev 21, Info: d2x-v4): Trucha Bug, NAND Access, USB 2.0
IOS202[57] (rev 65535, Info: hermes-v5.0): Trucha Bug, NAND Access, USB 2.0
IOS203[38] (rev 65535, Info: d2x-v4): Trucha Bug, ES Identify, NAND Access
IOS222[38] (rev 65535, Info: hermes-v5.0): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[37] (rev 65535, Info: hermes-v5.0): Trucha Bug, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermes-v5.0): Trucha Bug, NAND Access, USB 2.0
IOS236[36] (rev 65535, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS246[37] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS247[37] (rev 21007, Info: d2x-v7final): Trucha Bug, NAND Access, USB 2.0
IOS248[57] (rev 21007, Info: d2x-v7final): Trucha Bug, NAND Access, USB 2.0
IOS249[56] (rev 21, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS250[38] (rev 21006, Info: d2x-v6): Trucha Bug, ES Identify, NAND Access
IOS251[53] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS252[55] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS253[56] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
IOS255[57] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
BC v6
MIOS v10
Report generated on 04/25/2018.

2. I included the picture of the credits page

3. I can't find file system under the properties of the game (I assume you mean the wbfs). Am i doing something wrong? (I posted a picture of the properties of the wbfs also)

 

[tswntk]

1 & 2 look OK. Make sure your per game setting (wasn't it monster hunter tri. not Mario Kart?) is also set to use cios 249 or
Global (since your other cios slots are still a bit outdated. But as long as you are not setting your game cios to them, they should be ok for now)

3. I can't find file system under the properties of the game (I assume you mean the wbfs). Am i doing something wrong? (I posted a picture of the properties of the wbfs also)

I mean inside Dolphin. In browser view, you should see the list of games you have and each should have an icon representation of the games. If not, its either an icon caching problem or the game is really bad. Likewise if it failed the partition integrity test, the game is bad.

 

[Cyan]

like he said, be sure the global AND individual game setting are not using any other slot than 249.

try to launch the game with another loader (usually, people prefer Wiiflow, but you can also try CFG Loader). be sure to use slot249 (not 250, which uses base38 and doesn't work with that game)
you'll see if the game launches (in that case, it's a loaderGX problem) or has the same problem which means the issue is your game or hdd.

When you said you tried the game on dolphin, did you load the game directly from your USB, or from your computer?
same question when you verified it with Wit, it's the one on USB, or the "original" on your computer?

you tried to overwrite it/copy it again to usb?
Try another USB device if you have one. maybe the issue is the device with corrupted sectors?

 

[Eguin]

I'll start off by saying thank you guys for all your help!!! I tried it on Wiiflow and it worked! I'm fine playing in on Wiiflow every time I want to play, so thanks!!!

If you're still interested in why it didn't work though (cause I kinda am), I'll show you what I found in what you guys suggested

1 & 2 look OK. Make sure your per game setting (wasn't it monster hunter tri. not Mario Kart?) is also set to use cios 249 or
Global (since your other cios slots are still a bit outdated. But as long as you are not setting your game cios to them, they should be ok for now)



I mean inside Dolphin. In browser view, you should see the list of games you have and each should have an icon representation of the games. If not, its either an icon caching problem or the game is really bad. Likewise if it failed the partition integrity test, the game is bad.

Whoops, sorry about that, I wanted to see check mario kart to see if it didn't have file system on all wbfs's or just mh3 (when i thought you meant to right click in the file explorer)
I checked dolphin and it said everything was fine (doing what you said with checking partition 1's integrity)

Spoiler

like he said, be sure the global AND individual game setting are not using any other slot than 249.

try to launch the game with another loader (usually, people prefer Wiiflow, but you can also try CFG Loader). be sure to use slot249 (not 250, which uses base38 and doesn't work with that game)
you'll see if the game launches (in that case, it's a loaderGX problem) or has the same problem which means the issue is your game or hdd.

When you said you tried the game on dolphin, did you load the game directly from your USB, or from your computer?
same question when you verified it with Wit, it's the one on USB, or the "original" on your computer?

you tried to overwrite it/copy it again to usb?
Try another USB device if you have one. maybe the issue is the device with corrupted sectors?

I tried both of them on the file on my USB, I double checked just now with the one on my USB to be sure

I double checked to make sure I was running it on 249, both the global settings, and the specific settings for MH3 are on 249 on USB Loader

Spoiler

Here's the global settings


Here's the MH3 settings

I assume there's no reason to copy it to my USB again if it works on wiiflow?

 

[Cyan]

oh, so it's a problem only in USBLoaderGX ? interesting.
thanks for testing and reporting with wiiflow.

it's the only game with that problem, right? I wonder what it could be.

 

[GreyWolf]

I don't know what the problem could be, either. I have the NTSC-U MH3 and the banner and game work fine.

 

[tswntk]

I don't know what the problem could be, either. I have the NTSC-U MH3 and the banner and game work fine.

RMHE08, same here. I didn't really played it but at least the banner is fine and it boots