Hacking USB Loader GX (vWii) stopped working

  • Thread starter Thread starter gamecaptor
  • Start date Start date
  • Views Views 66,561
  • Replies Replies 269
no, you can't use subfolders #-z, you need to follow the conventions.
if your game files are uniquely named, move them all to x:\wbfs (don't know if big, splited game file will work)
of if each game already have its own folder, move those folders to x:\wbfs (works for all games)

Then use WiiBackupManager (PC program), select the drive as drive 1 and choose tools->FAT32/NTFS->update storage convention

edit. In options->FAT32/NTFS, there are 4 options for the folder naming. Title [GameID] being the most common, don't know if it was the default.
 
Last edited by tswntk,
no, you can't use subfolders #-z, you need to follow the conventions.
if your game files are uniquely named, move them all to x:\wbfs (don't know if big, splited game file will work)
of if each game already have its own folder, move those folders to x:\wbfs (works for all games)

Then use WiiBackupManager (PC program), select the drive as drive 1 and choose tools->FAT32/NTFS->update storage convention

edit. In options->FAT32/NTFS, there are 4 options for the folder naming. Title [GameID] being the most common, don't know if it was the default.


Thanks for the confirmation that this cannot be done. It is not a big deal. I tested a few games and everything loads just fine. I still can't believe all of this was just a stupid line change in an xml file. But it works and it was worth it as USBLoaderGX is definitely a whole lot better than I remember it was years ago :)
 
Your meta.xml should look like this by the way. Just figured I'd add the code so people know what I am talking about.


Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <app version="1">
        <name> USB Loader GX</name>
        <coder>USB Loader GX Team</coder>
        <version>3.0 r1260</version>
        <release_date>20160102155330</release_date>
     
        <arguments>
                <arg>--ios=58</arg>
                <arg>--usbport=0</arg>
                <arg>--mountusb=1</arg>
        </arguments>

        <ahb_access/>
        <short_description>Loads games from USB-devices</short_description>
        <long_description>USB Loader GX is a libwiigui based USB iso loader with a wii-like GUI. You can install games to your HDDs and boot them with shorter loading times.
The interactive GUI is completely controllable with WiiMote, Classic Controller or GC Controller.
Features are automatic widescreen detection, coverdownload, parental control, theme support and many more.

Credits:
Coding: Cyan, Dimok, nIxx, giantpune, ardi, Hungyip84, DrayX7, Lustar, r-win, WiiShizzza
Artworks: cyrex, NeoRame
Validation: Cyan and many others
Issue management: Cyan
WiiTDB / Hosting covers: Lustar
USBLoader sources: Waninkoko, Kwiirk, Hermes
cIOS maintenance: davebaol, xabby666, XFlak and Rodries
Languages files updates: Kinyo and translaters
Hosting themes: Deak Phreak

Libwiigui: Tantric
Libogc/Devkit: Shagkur and Wintermute
FreeTypeGX: Armin Tamzarian.

Links:
USB Loader GX Project Page
https://sourceforge.net/projects/usbloadergx/
Support Site:
http://gbatemp.net/index.php?showtopic=149922
Help Website:
http://usbloadergx.koureio.net/
WiiTDB Site:
http://wiitdb.com
Themes Site:
http://wii.spiffy360.com
Languages Translaters Page:
http://gbatemp.net/index.php?showtopic=155252

Libwiigui Website:
http://wiibrew.org/wiki/Libwiigui/
FreeTypeGX Project Page:
http://code.google.com/p/freetypegx/
Gettext Official Page:
http://www.gnu.org/software/gettext/gettext.html
        </long_description>
    </app>
 
Last edited by zektor,
I just realized after pouring through this thread that Cyan mentioned way back in one of the posts to try exactly what I did with the meta.xml and nobody replied to it and performed it. So it is working when using IOS58 to init the hard drive but I guess the issue is why is it not working when attempting to use IOS250 to init. Does anyone know what IOS Wiiflow is using for HDD initialization?

I am having zero issues at this point mind you, but just curious as to why it will not init on the IOS it is supposed to be initializing on.
 
You know that you don't need to edit the meta.xml manually ?
You asked for an option to use 58 at launch, and it's inside the settings>loader settings>Loader's IOS : replace 249 with 58.
Done.

it will automatically edit the meta.xml and removes the commented lines to tell the loader to use 58 at launch.

And like you said, the issue is understanding why cIOS are not working.
I could force 58 to init the drive, but some users don't have 58 (on wii !! old softmod, etc.), or some drives don't work very well with 58, or has a different priority (port 1 before port 0 when multiple drives are connected resulting in different partition order and config path issues)
forcing 58 is not the best solution right now. I'll check what the issue is and if it can be solved without reloading IOS multiple times.


Oh, and, NO, I didn't try the HDD yet.
I was busy with loadiine recent release, and other private stuff I have to deal with.
I'll tell you guy when I start looking at it.
 
You know that you don't need to edit the meta.xml manually ?
You asked for an option to use 58 at launch, and it's inside the settings>loader settings>Loader's IOS : replace 249 with 58.
Done.

it will automatically edit the meta.xml and removes the commented lines to tell the loader to use 58 at launch.

And like you said, the issue is understanding why cIOS are not working.
I could force 58 to init the drive, but some users don't have 58 (on wii !! old softmod, etc.), or some drives don't work very well with 58, or has a different priority (port 1 before port 0 when multiple drives are connected resulting in different partition order and config path issues)
forcing 58 is not the best solution right now. I'll check what the issue is and if it can be solved without reloading IOS multiple times.


Oh, and, NO, I didn't try the HDD yet.
I was busy with loadiine recent release, and other private stuff I have to deal with.
I'll tell you guy when I start looking at it.



Yup, I am fully aware there is an option to change the setting within USBLoaderGX, but in order to do that I would need to:

1. Disconnect the hard drive so it does not freeze
2. Launch USBLoaderGX and change the setting
3. Exit the loader and reconnect the hard drive
4. Load USBLoaderGX again

A little faster to edit the meta.xml and run it without disconnecting anything wouldn't you say? What I meant by an option at launch is just that. When you first launch GX an option to choose the HDD init IOS *before* it tries to initialize it (before the GUI) so that the freeze can be avoided from the get go for people.

In any case, I guess it is working now although not as officially intended. Also, I did not ask you to try a HDD...unless you are replying to another member?

I'd like to add that I had the opportunity to try another 2TB (same model) drive the other day. This time I formatted it to FAT32 and installed Beta52. USBLoaderGX worked out of the box the first time using default settings. But on second launch it froze again and I had to edit the meta.xml back to IOS 58. Really strange.
 
Last edited by zektor,
yes, I replied to other members (or anticipated their questions), as a lot of them are waiting for my tests to fix that issue.
I still haven't done it, I have another project to fix too.

As temporary fix, I could force a IOS58 reload. We did it on previous release (v2.3) but some users had issues with 58 at launch, so we reverted it.
 
Great, thank you for all of the assistance you have been providing us. Bar none this is the best loader today. I will gladly test any updated versions that utilize IOS 58 reload by default. I think the only users that are going to have any problems are ones that are not up to date to the latest/last firmware...and in my opinion they should be at this point. vWii users would not have to worry about that as they are all on v4.3 anyway. Thanks again for the hard work!
 
I know this is old but I'm having an issue with gx it wont detect my drive but homebrew channel finds it perfect and nintendont everything works with it except gx and wiiflow
 
I know this is old but I'm having an issue with gx it wont detect my drive but homebrew channel finds it perfect and nintendont everything works with it except gx and wiiflow
modify your meta.xml file.
I'm willing to bet that's your issue.
Change from ios 250 to 58.
You know what, even better. Replace the one you have now with the one I'm attaching.
(Make a backup of the original JUST IN CASE, even though it shouldn't do any harm even if it doesn't work)
Let me know if it does though :)
 

Attachments

  • Like
Reactions: kiwiis
I know this is old but I'm having an issue with gx it wont detect my drive but homebrew channel finds it perfect and nintendont everything works with it except gx and wiiflow
Are using a Y cable when connecting your HDD to the Wii (I had the same issue this week)
 
Yes I'm using y cable I'll try the meta file when I get home I'm visiting with my dad at the nursing home

I changed the meta file and it didn't do any good it still comes up waiting for hdd then it shows no usb device

ps I got it to read the drive if I hook it up right when it says looking for drive it will detect it so I'm thinking it don't like my enclosure
 
Last edited by wolf_,
Using a WD Passport with a Y cable on the vWii. Have tried pretty much everything this thread and others have suggested (the meta.xml modification, different cIOS, different ports etc) and it is still giving me the freeze on the "Initialise usb device" screen. Driving me up the wall. I'm guessing at this point it's down to the drive or cable but I know the drive works and the normal Wii U is okay with it. Also I've followed the vWii hacking guide to the letter (so formatted to FAT32 using Bootice etc etc).

Any help is appreciated.
 
Using a WD Passport with a Y cable on the vWii. Have tried pretty much everything this thread and others have suggested (the meta.xml modification, different cIOS, different ports etc) and it is still giving me the freeze on the "Initialise usb device" screen. Driving me up the wall. I'm guessing at this point it's down to the drive or cable but I know the drive works and the normal Wii U is okay with it. Also I've followed the vWii hacking guide to the letter (so formatted to FAT32 using Bootice etc etc).

Any help is appreciated.

FYI, there is technically a "write and wrong" way for a Y-Cable.

You should post your SysCheck results. That info is often enlightening.
 
You know all I did was not boot wiiflow or USB loader using their forwarders. Now it works fine from the homebrew channel
 
Bit of a long shot but do u think this new wii u update will have any affect on getting this working with people who cant seem to get it working? Or are there intentions just to try and block the hack? Or is this just a usb loader GX issue?
 
Wow, a new version of USB Loader GX! Merry Christmas to all!

So it's been sometime since I've visited this issue but if I remember correctly the problem I had was loading a FAT32 USB 3.0 HD with USB Loader GX in vWii. Are you saying this should be fixed now?

And as I've been removed from this scene for a while can we now have a Wii U HD and a Wii HD both connected to the Wii U at once? If so does they need to be plugged into specific ports (front vs back)? And does the Wii HD need to be hidden?

P.S. Happy Holidays @Cyan !
 
Wow, a new version of USB Loader GX! Merry Christmas to all!

So it's been sometime since I've visited this issue but if I remember correctly the problem I had was loading a FAT32 USB 3.0 HD with USB Loader GX in vWii. Are you saying this should be fixed now?

And as I've been removed from this scene for a while can we now have a Wii U HD and a Wii HD both connected to the Wii U at once? If so does they need to be plugged into specific ports (front vs back)? And does the Wii HD need to be hidden?

P.S. Happy Holidays @Cyan !
You can, and yes the Wii HDD needs to be hidden because the Wii U side will not let you do anything when you have 2 drives connected and detected.
Ninrendont needs the FAT32 drive to be the first one detected though IIRC.
 

Site & Scene News

Popular threads in this forum