Hacking USB Loader GX

[xaxa]

Ok, so I've tried everything now. I removed IOS249 and reinstalled cIOS38 rev14 because I had rev16 before. This hasn't helped either, uloader is still working perfectly in every single way, but I can not use any other USB loaders at all, this makes no sense to me.

Am I missing something??? Is there something other loaders need that uloader doesn't?

Check the settings. Make sure the ios used is not set to 249. I picked 222 and it's working fine so far.

 

[TiMeBoMb4u2]

Okay... I know this has probably been answered a thousand times, but I'm having trouble finding the "official" USB Loader GX answer...

I have the QwiiF release of New Super Mario Bros. Wii, and I would like to know what I need to do, to play it. Some posts are saying that I need a .BCA file, some are saying to patch the ISO, and some are saying that I don't need to do anything when using USB Loader GX.

If possible, I would like to keep the ISO I have "clean" (I'd prefer not to patch it.)
If I need a .BCA file, how do I create, or where do I get it?
If I need to do nothing, just say, "Do nothing and play it, dumbass!"

 

[giantpune]

Do nothing and play it, dumbass

 

[TiMeBoMb4u2]

Do nothing and play it, dumbass

Thanks, giantpune!

 

[TiMeBoMb4u2]

So, for future reference, what is the method for creating .BCA files?

 

[r-win]

but PAL is still different than NeverTheSameColor

Another NTSC lover. I love to live in the Netherlands (in Europe at least)

 

[r-win]

Ok, so I've tried everything now. I removed IOS249 and reinstalled cIOS38 rev14 because I had rev16 before. This hasn't helped either, uloader is still working perfectly in every single way, but I can not use any other USB loaders at all, this makes no sense to me.

Am I missing something??? Is there something other loaders need that uloader doesn't?
Check the settings. Make sure the ios used is not set to 249. I picked 222 and it's working fine so far.

That is indeed the solution, but he cannot access the settings

uLoader uses cios 222, while USB GX and Wiiflow uses 249 by default. It seems that 249 doesn't support you HDD. You should change the default cios to 222. Open /config/GXGlobal.cfg in a decent editor (not notepad) and search for the line cios = 0. Change the 0 to 1, save, and try again.

Posts merged

QUOTE(TiMeBoMb4u2 @ Jan 2 2010, 02:51 AM)

So, for future reference, what is the method for creating .BCA files?

We have no method yet, since it's not needed yet. I guess we will implement a BCA ripper in the loader when we are up to it.

 

[TiMeBoMb4u2]

So, for future reference, what is the method for creating .BCA files?

We have no method yet, since it's not needed yet. I guess we will implement a BCA ripper in the loader when we are up to it.

That would be AMAZING!
Just have the loader rip the BCA file to the designated BCA directory!

 

[nanoblade]

That is indeed the solution, but he cannot access the settings

uLoader uses cios 222, while USB GX and Wiiflow uses 249 by default. It seems that 249 doesn't support you HDD. You should change the default cios to 222. Open /config/GXGlobal.cfg in a decent editor (not notepad) and search for the line cios = 0. Change the 0 to 1, save, and try again.

Thanks buddy, I've done that for wiiflow now, and the 222 version works fine. However, since GX loader can't start with my HDD the GXGlobal.cfg file hasn't been generated on my SD Card, I've tried copying and pasting someone elses file text from this forum but that doesn't work. Any other suggestions, or could someone PM me their config file zipped up??

Thanks

 

[karl10247]

Hi all im having a problem with getting the game information to display when you press the 2 button over a game. Nothing but the one liner appears "if you dont have wifi click 1......" Got wifi of course and downloading covers is no problem

Im on r881 and got both wiitdb.zip and titles.txt in USB/config.

Got r881 channel installed and using that normally, disc information doesnt show up if i launch through this or through HBC.


Can anyone help please?

 

[wrettcaughn]

That is indeed the solution, but he cannot access the settings

uLoader uses cios 222, while USB GX and Wiiflow uses 249 by default. It seems that 249 doesn't support you HDD. You should change the default cios to 222. Open /config/GXGlobal.cfg in a decent editor (not notepad) and search for the line cios = 0. Change the 0 to 1, save, and try again.

Thanks buddy, I've done that for wiiflow now, and the 222 version works fine. However, since GX loader can't start with my HDD the GXGlobal.cfg file hasn't been generated on my SD Card, I've tried copying and pasting someone elses file text from this forum but that doesn't work. Any other suggestions, or could someone PM me their config file zipped up??

Thanks

try just making a txt file named GXglobal.cfg and add the line : cios = 1

save it and put it in a folder named config on the root of your SD

let us know if it works for you.

 

[lithium210]

anyone know the coords for the parental lock icon which was recently added??

 

[tonybologna]

I love USB Loader GX. This program rocks!

 

[wimu]

A simple question is the forwader channel also can load USBGX from a usb drive or not (usb:/apps/usbloader_gx/boot.dol)?

 

[deakphreak]

anyone know the coords for the parental lock icon which was recently added??

Check this thread http://wii.spiffy360.com/forum/thread-505-post-1245.html which may help you out.

 

[giantpune]

yes. the forwarder channel checks for the settings file from the actual program. if it finds the file, it uses the updatepath you defined it the main program to try to load. if it does not find that settings file, it checks the sd card for /apps/usbloader_gx/boot.dol and boot.elf. then it checks the first FAT partition of the usb drive for the same paths. if it still comes up empty handed, it exits back to the system menu.

so, if you have a settings file that says the updatepath is on the sd card, it will not ever bother to check the usb drive.

 

[Dteyn]

I'm having a bit of trouble setting up a FAT32 hard drive with USB Loader GX (rev 874, cIOS249 rev16) on a buddy's Wii. Everything is good up until the point of trying to install games on the Wii using the loader. I insert a disc, after clicking install there is about a 5-10 second delay before the Wii freezes and gives a DSI code dump error.

The DVD drive does have a modchip (not sure what kind, it was installed by someone else well before the time of USB loaders), and it doesn't seem to make a difference whether I use original discs or burned backups.

Is this a problem related to the modchip? Or is there still an issue with FAT32 support at the moment?

Edit: Just noticed rev881 is the most recent rev (according to the Google code site), gonna try it and see if the issue has been resolved.

Edit 2: Nope, rev881 still has the same problem.

 

[dun4cheap]

If I am correct in saying, that GX Loader will only backup games on to a WBFS Formated drive, not a FAT32 of NTFS drive.

 

[Dteyn]

Some of the posts I'd read seemed to indicate that installing games (via the Wii using the loader) is possible with WBFS and FAT32, just not NTFS. When I had the drive partitioned as NTFS, it wouldn't allow me to install or delete games, however with FAT32 I was successfully able to delete a game. It's just installing games that seems to have an issue.

Can any of the developers confirm whether USB Loader GX supports installing games to FAT32 drives?

It would be helpful to list a bit more details about the filesystem support in the features list for USB Loader GX. For instance when I initially read the features list, I saw that it supports WBFS, FAT32, and NTFS and had assumed that it supported installing to all three. I'm sure it would be helpful to others to know that NTFS is read-only without having to discover it on their own.

BTW please don't take this as a criticism, just a friendly suggestion. As I mentioned earlier I'm setting this Wii up for a friend, he wants the ability to store multiple file types as well as use the Wii to install games (without needing to use multiple partitions). Since NTFS write support isn't implemented, it looks like FAT32 is the best option for him. I personally despise FAT32 after many frustrating experiences losing data stored on FAT32 partitions. Although the Linux geek inside me wishes that ext2 was a more popular filesystem, the realist inside me realizes that read only NTFS support is the most I will personally ever need in a USB loader. Sorry for rambling.. keep up the good work guys!

 

[giantpune]

yes, it is possible to install a game to a FAT partition with the usb loader, but that is currently broken in our program. it came about around the time loading games from different folders popped up and just hasnt been corrected.

specifically, heres where shit goes bad (getting the size of the game) its probably like 5 lines of code,but ill let r-win mess with it when he gets the time.

Spoiler

MenuInstall()
ÂÂÂÂdisc inserted....opened...is a wii game...is not already installed
ÂÂÂÂget free space:188
ÂÂÂÂget gamesize


ÂÂÂÂException (DSI) occurred!
ÂÂÂÂGPR00 00022E40 GPR08 00000001 GPR16 00000000 GPR24 80EF1078
ÂÂÂÂGPR01 80FFC4D0 GPR09 00000000 GPR17 00000000 GPR25 80E91B9C
ÂÂÂÂGPR02 80ED61C8 GPR10 FBE00000 GPR18 00000000 GPR26 80FFC5B0
ÂÂÂÂGPR03 00000000 GPR11 00000001 GPR19 00000000 GPR27 00000000
ÂÂÂÂGPR04 00000014 GPR12 17200000 GPR20 80EF0000 GPR28 00008000
ÂÂÂÂGPR05 80FFC490 GPR13 80EF0CA0 GPR21 80E91ADC GPR29 90373700
ÂÂÂÂGPR06 903739A0 GPR14 00000000 GPR22 80EF1050 GPR30 80FFC508
ÂÂÂÂGPR07 00000001 GPR15 00000000 GPR23 80EF0000 GPR31 00000000
ÂÂÂÂLR 80BCFC48 SRR0 80bcfc7c SRR1 00008032 MSR 00000000
ÂÂÂÂDAR 00000004 DSISR 06000000

ÂÂÂÂSTACK DUMP:
ÂÂÂÂ80bcfc7c --> 80bcfc48 --> 80b5e68c --> 80b5c508 -->
ÂÂÂÂ80b003cc --> 80c4e12c --> 80c4e0cc

ÂÂÂÂCODE DUMP:
ÂÂÂÂ80bcfc7c:ÂÂ919F0004 917F0000 80010034 7F63DB78
ÂÂÂÂ80bcfc8c:ÂÂ83810020 7C0803A6 8361001C 83A10024
ÂÂÂÂ80bcfc9c:ÂÂ83C10028 83E1002C 38210030 4E800020

ÂÂÂÂReloading in 5 seconds

ÂÂÂÂReload

also, it is a widely accepted fact that getting the size for a FAT partition takes more time the bigger the partition is. this is why we dont show the free space for people using a fat partition. (and probably the reason they decided not to let windows create huge fat partitions), but it is something that must be done before trying to install a game. so this whole log would normally take about 2 seconds, but because it checks the free space, it adds like 30 seconds. even when the fat installing is working again, this will still be the case