Hacking USB Loader GX

  • Thread starter Thread starter blackb0x
  • Start date Start date
  • Views Views 8,066,697
  • Replies Replies 30,226
  • Likes Likes 74
Cyan,

Thanks for your response.

With the official 3.0 release and the original MIOS, I've never had a problem. With rev 1198 or higher I occasionally have some problems with Skyward Sword and with DIOS MIOS 2.2 and 2.4 added (I may have also tried 2.0, can't remember off hand). I always have a problem. So it seems something in the upper revs may cause some glitches, but DIOS MIOS seems to make the glitches worse.

I have tried it with Config USB Loader and Skyward Sword worked just fine. That's why I posted here in the USB Loader GX forum.
 
MIOS is not accessed or loaded when using a Wii game, as the Wii isn't spinning the disc drive fast enough (which is the whole basis of the "Gamecube mode" and "Wii mode" thing).

You're using the beta version of GX-- which has more compatibility with DM(L), which could be the cause. What IOS are you using to load Skyward Sword, and what IOS are you using to use GX with?
 
I am loading GX from 249 and I have tried Skyward Sword from 248 249 and 250.

Overall it is the same result. On occasion it works but generally it hangs. Since I have the originals of all my GC games it is no big deal for me to have GX at the official release and not use Dios Mios. It is just a problem I have had so I wanted to try to work it out. As of today I have removed DM and have rev 1201 of GX installed. Will retest Skyward Sword later today when I get home.
 
did the usb detection code change in any way in the newer beta revs? a friend of mine never had a problem with gx locating and playing his games from usb, but since he updated to the newest beta, the loader either hangs at initializing the usb drive or on loading any game, be it a gamecube or a wii game. we've thought about if it could be a cios issue, but seeing how it always worked before with the installed cios, we don't think that cios is the problem. he also tried updating to the newest d2x cios, no joy, so he went back to the previously installed d2x v8. I've looked at a syscheck of his wii and found nothing unusal. I have hacked many wiis in the past and his setup is exactly like all those other wiis I hacked, which work fine until this very day even after updating to the newest gx beta. I know a lot about the wii and wii hacking itself, but I just can't find the root of the problem this time. Since everything accept gx is working fine with the usb drive, could the loader be the source of the error?
 
did you try to revert back to the working version of the loader?
does it fix the problem?

Some users reported problem with newer version of the loader, but couldn't confirm whci version broke it, neither if it's the loader or the drive or cios, etc.
At least if you can find the exact revision which broke it, it could help debug and fix the problem.
 
yeah he also tried that, but no joy. We decided to rehack his wii from scratch and see if the problem would be fixed in the process. However, we have not yet found the time to do so. I'm gonna report back when we are done.
 
rehacking is not required.
You wii only need the homebrew channel and 2 IOS (58 for HBC, 249 for USBloaders)
rehacking it = reinstalling a new cIOS in slot249, that's all.

The loader use IOS58 on boot if you are using the <no_ios_reload/> tag in the meta, before reloading to 249 once the drive is mounted.
Or reloading 249 at launch (or just after, but before mounting the drive) if you don't use that tag.
Did you try enabling/disabling that tag? maybe since he use IOS58 to boot and access the HDD he has problem to init the drive? and when he used 249 at boot it was better?


What I don't understand is how the HDD could be affected by the loader if reverting to an old version doesn't fix the problem?
if it really is the loader's faults, it would means that it permanently affected it, but the loader doesn't touch the partitions, it only write new games of config files to it.

I can't check the problem if I don't have a specific version where the problem rise. which working version did he use before updating to the newest beta?
 
Hi, I want to report in the latest release you can´t install a game from disc without splting it in 2 files (game.wbfs and game.wbfs1)
Even changing the hard disc drive settings to "no spliting", the install of whatever disc always will have at least 2 wbfs files.

It´s not a big deal really, but I felt like it is worth reporting =)
 
That's a limitation of the file format FAT32, it can only handle files of approx 4GB and files that go over that size need to be split.

On an NTFS formatted drive it shouldn't split.
 
That's a limitation of the file format FAT32, it can only handle files of approx 4GB and files that go over that size need to be split.

On an NTFS formatted drive it shouldn't split.
Well, that's the problem, the partition where the games are is NTFS, my primary partion is FAT32 though.
 
Are there any precompilled versions of GX that load IOS222 at boot?
Yeah, usually when you download it will have a folder with a 222 version in it, a folder with a 249 version in it and one with a 250 version in it you can choose from. If you want it to STAY on that cIOS after that, just make sure that it's also the cIOS set in the settinsg.
 
Thank you for the bug report about the split file on NTFS.
I'll look at it (well at the code only, I don't use NTFS partition, you will have to test it for me hehe)


@pbullet:

The IOS222 doesn't support ES/NAND access natively, and you need to use the <no_ios_reload/> tag in your meta to load everything with IOS58 before reloading to 222 if you want to use the Channel layout which require NAND access on boot.
The AHBPROT rights will not be kept after reloading to 222 and will not be passed to other IOS (like passing the rights to devolution).

This is just in case you don't understand why some menu/features doesn't work correctly.
If it's only for Wii games and dual port support, then there's no problem for you.
 
I wanted to leave an update about my previous posts about Skyward Sword. The issue now seems to revolve around using emunand. I generally have emunand set to full in USB Loader GX, so I turned it off for Skyward Sword and now it is working. Could this be due to a bad nand dump through USB Loader, or is it just that this game wont work with emunand?
 
Cyan, a few pages back you mentioned Metal Gear Twin Snakes doesn't offer to save before disk swap. I wasn't aware NMM worked with Twin Snakes, or did you mean with memory cards?
 

Site & Scene News

Popular threads in this forum