Hacking USB Loader GX

[sideskroll]

you said editing the settings back to 249 didn't edit the xml ?
reseting the full settings (from the reset menu) it probably not reseting the xml (I think I forgot to reset the xml too), but editing the IOS or the HDD menu should edit the xml.

But, that's a good think it didn't work for you, because that's my new suggestion :
- set the Loader's IOS to 249
- manually edit the XML to use 58 on boot.

on boot, it will use IOS58 to initialize the drive and spin it up, once loaded it will check the GXglobal config to check if you want to use a different IOS slot for the loader and will find 249, so it will reload to cIOS 249.
when reloading, it disconnect the partition's reference in memory but shouldn't shut down the drive completely, it will be already "spin up"'d so IOS249 shouldn't have issue starting the drive and can only mount the partition again.

58 -> spin up -> mount partition -> read cfg -> see 249 -> disconnect partition -> reload to 249 -> remount partition

if you (and all other users in the HDD freeze issue thread) have the same detection issue with this setup, then I don't know how to fix the issue.

Ok. Did it as per your instructions AND by just resetting everything to default from the loader.
Things just got weirder now.
This is the default meta file

<!--   // remove this line to enable arguments
        <arguments>
                <arg>--ios=250</arg>
                <arg>--usbport=0</arg>
                <arg>--mountusb=1</arg>
        </arguments>

This is my gxglobal file (the pertinent part at least):

LoaderIOS = 249
cios = 249

And this is my meta.xml file (AFTER explicitly selecting ios 249 as the loaders ios)

<arguments>
                <arg>--ios=58</arg>
                <arg>--usbport=0</arg>
                <arg>--mountusb=1</arg>
        </arguments>

Now these are my files with IOS 58 as default in the loader:

LoaderIOS = 58
cios = 249

<arguments>
                <arg>--ios=58</arg>
                <arg>--usbport=0</arg>
                <arg>--mountusb=1</arg>
        </arguments>

Same thing. Nothing changes.

The weirdest part is that, it works.
The ONLY time it doesn't launch is if I download a fresh install of USBLOADER GX and put it in the SD (which works fine on Wii) As soon as I change the ios to 58 (inside the settings, not manually), it starts working, even if I go and change it back to 249.
Why is 250 the default by the way? I guess it doesn't matter cause the arguments are commented out in the default meta file, but still...
What makes it weird is that the meta arguments never change apparently. (by the way it appears there's an issue in there cause it should, right?)
Any ideas?

 

[Retro_Mod_Gamer]

Actually, you only need slot 249. So you should be good. (Syscheck woukd be nice. Yeah)
Can you try with a different drive? Is it a thumbdrive or hdd?

I was going to ask about HDD compatibility, I'm using a WD1600AABB on this configuration, though I used a flash drive once and that didn't seem to work either. syscheck is as follows


sysCheck v1.6.2 by Erik Spyder

Region: NTSC-U
The system menu v513 is running under IOS58 (rev 6176)
Hollywood v0x21
Console ID: 86832164
Boot2 v4
Found 78 titles
Found 32 IOS on this console
Found 16 IOS Stubs on this console

IOS (revision),IOS Stub,Trucha Bug,ES Identify,Flash Access,NAND Access,Boot2 Access,USB 2.0
IOS3 (rev 65280),Yes,?,?,?,?,?,?
IOS4 (rev 65280),Yes,?,?,?,?,?,?
IOS9 (rev 1034),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS10 (rev 768),Yes,?,?,?,?,?,?
IOS11 (rev 256),Yes,?,?,?,?,?,?
IOS12 (rev 526),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS13 (rev 1032),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS14 (rev 1032),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS15 (rev 1032),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS16 (rev 512),Yes,?,?,?,?,?,?
IOS17 (rev 1032),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS20 (rev 256),Yes,?,?,?,?,?,?
IOS21 (rev 1039),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS22 (rev 1294),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS28 (rev 1807),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS30 (rev 2816),Yes,?,?,?,?,?,?
IOS31 (rev 3608),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS33 (rev 3608),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS34 (rev 3608),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS35 (rev 3608),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS36 (rev 3608),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS37 (rev 5663),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS38 (rev 4124),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS40 (rev 3072),Yes,?,?,?,?,?,?
IOS41 (rev 3607),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS43 (rev 3607),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS45 (rev 3607),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS46 (rev 3607),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS48 (rev 4124),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS50 (rev 5120),Yes,?,?,?,?,?,?
IOS51 (rev 4864),Yes,?,?,?,?,?,?
IOS52 (rev 5888),Yes,?,?,?,?,?,?
IOS53 (rev 5663),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS55 (rev 5663),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS56 (rev 5662),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS57 (rev 5919),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS58 (rev 6176),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS60 (rev 6400),Yes,?,?,?,?,?,?
IOS61 (rev 5662),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS70 (rev 6912),Yes,?,?,?,?,?,?
IOS80 (rev 6944),No,Disabled,Disabled,Disabled,Disabled,Disabled,Disabled
IOS222 (rev 65280),Yes,?,?,?,?,?,?
IOS223 (rev 65280),Yes,?,?,?,?,?,?
IOS236 (rev 65535),No,Enabled,Enabled,Disabled,Enabled,Disabled,Disabled
IOS249 (rev 65535),No,Enabled,Disabled,Disabled,Enabled,Disabled,Enabled
IOS250 (rev 65535),No,Enabled,Disabled,Disabled,Enabled,Disabled,Enabled
IOS251 (rev 65535),No,Enabled,Disabled,Disabled,Enabled,Disabled,Enabled
IOS254 (rev 65280),Yes,?,?,?,?,?,?


Report generated on 2016/01/07

 

[Retro_Mod_Gamer]

I am trying with a WDPCK500ABK-01, yes it works with that drive so I guess it is just a drive compatibility issue? I didn't factor this as it worked fine for loading GameCube games.

 

[tswntk]

The ONLY time it doesn't launch is if I download a fresh install of USBLOADER GX and put it in the SD (which works fine on Wii) As soon as I change the ios to 58 (inside the settings, not manually), it starts working, even if I go and change it back to 249.
Why is 250 the default by the way? I guess it doesn't matter cause the arguments are commented out in the default meta file, but still...
What makes it weird is that the meta arguments never change apparently. (by the way it appears there's an issue in there cause it should, right?)
Any ideas?

When you fresh install USBLOADER GX, did you overwrite the xml?
Yes, the default xml is ios250 probably because if anyone is to change the xml, they should know what they are doing so there is no point to keep it as 249, it is commented out anyway (just my guess).

I just did a test and change the ios in loaderIos setting to 250 and then to 58 and the xml changes accordingly (to 250 and then 58) which is what it is supposed to. I didn't manually change the xml since I only got a Wii and never have any problem with it.

I do notice there is a setting right below the ios setting: quick boot = off.
I don't know if that affects anything or if you already had the same setting. @Cyan should know better what it means.
Thats all I can think of for now...

 

[sideskroll]

When you fresh install USBLOADER GX, did you overwrite the xml?
Yes, the default xml is ios250 probably because if anyone is to change the xml, they should know what they are doing so there is no point to keep it as 249, it is commented out anyway (just my guess).

I just did a test and change the ios in loaderIos setting to 250 and then to 58 and the xml changes accordingly (to 250 and then 58) which is what it is supposed to. I didn't manually change the xml since I only got a Wii and never have any problem with it.

I do notice there is a setting right below the ios setting: quick boot = off.
I don't know if that affects anything or if you already had the same setting. @Cyan should know better what it means.
Thats all I can think of for now...

By fresh install I mean, delete the whole usbloader_gx folder from apps, and use the installer to re-download everything (yes, that includes a fresh meta.xml)
So my guess is as good as yours then. Not that it matters after all.
In my case, the arguments on the xml file didn't change (like you can see in my previous post) could that have something to do with this? After all, you're on a Wii (this HDD and the default setup work flawlessly on my Wii, is the Wii U the one that is given me issues.
Are you launching the loader from an SD or from the HDD? That could also affect the outcome. I have all my homebrew on the SD.
I THINK, the cIOS for vWii are not as well made (compatible?) as the ones for Wii (someone correct me if I'm wrong. Maybe the patch is exactly the same. In which case the issue would be the base ios...)

 

[tswntk]

By fresh install I mean, delete the whole usbloader_gx folder from apps, and use the installer to re-download everything (yes, that includes a fresh meta.xml)
So my guess is as good as yours then. Not that it matters after all.
In my case, the arguments on the xml file didn't change (like you can see in my previous post) could that have something to do with this? After all, you're on a Wii (this HDD and the default setup work flawlessly on my Wii, is the Wii U the one that is given me issues.
Are you launching the loader from an SD or from the HDD? That could also affect the outcome. I have all my homebrew on the SD.
I THINK, the cIOS for vWii are not as well made (compatible?) as the ones for Wii (someone correct me if I'm wrong. Maybe the patch is exactly the same. In which case the issue would be the base ios...)

I run everything except games from SD. Simpler to setup and backup.
I wouldn't want to risk writing any thing to the HDD not via the PC. I don't trust the Wii Lib that much and I have a few cases of corrupted SD. Can't imagine if that happens to the HDD. Call me paranoid

 

[sideskroll]

I run everything except games from SD. Simpler to setup and backup.
I wouldn't want to risk writing any thing to the HDD not via the PC. I don't trust the Wii Lib that much and I have a few cases of corrupted SD. Can't imagine if that happens to the HDD. Call me paranoid

I'll call you "guy who thinks like me".
Sadly, that takes the HDD out of the equation and leaves me (again) blaming the d2x patch for vWii as the culprit.

 

[GreyWolf]

I was going to ask about HDD compatibility, I'm using a WD1600AABB on this configuration, though I used a flash drive once and that didn't seem to work either. syscheck is as follows


sysCheck v1.6.2 by Erik Spyder

That version of SysCheck is very old. Use the one here (and put it in spoilers. )

I noticed you said you couldn't get WBFS files to work on FAT32 and mentioned splitting them at 4GB. Did you try checking the ones on your Wii drive with the ones on your PC with WBM and make sure the MD5s match? They may not have copied properly.

 

[Cyan]

If you change loader's ios to 58 in setting, it will (should) change the xml automatically, so the next boot will be:
xml ios58-> spin up -> mount partition -> read cfg -> see setting 58-> disconnect partition -> reload to 58-> remount partition

Almost correct.
I'm editing the meta.xml automatically to match the user setting because it speeds the startup process. if the loaded IOS at boot is the same than the user's setting, it prevent disconnecting/reloading IOS/reconnecting the drive. (2 seconds)

correct order is :
xml ios58-> spin up -> mount partition -> read cfg -> see setting 58 -> load GUI

before the xml was automatically edited, the user could set the loader's IOS in the settings, and it would keep the xml IOS on the old value.
Meaning that if the users had 250 is the XML, and set the loader to 249, it reloaded :
xml ios250-> spin up -> mount partition -> read cfg -> see setting 249-> disconnect partition -> reload to 249-> remount partition -> load GUI

maybe that's still not the best way to manage the xml.
Maybe there should be 3 settings in the loader :
boot IOS
loader IOS
game IOS


anyway, did you try loader IOS 249 while the XML is still on 58 ?
xml ios58-> spin up -> mount partition -> read cfg -> see setting 249-> disconnect partition -> reload to 58-> remount partition -> load GUI

if it doesn't work, does booting a game work while having the loader with IOS58 ?
meta 58
loader 58
game 249
when launching game, it reloads to cIOS

because its either a bug or @Cyan explicitly coded reset to default to NOT reset the meta file

it's neither a bug or done on purpose.
it's just that I forgot that the settings could be edited by using the reset option
I'll add the meta.xml reset at the same time.
Thanks for reporting that issue.

About the xml edited to 58 when you set the loader's IOS to 249, ... I don't trust it. sorry.
Probably a wrong user's manipulation.
the loader can't technically set a different number than the one you enter.

Maybe there's a bug, but I feel like there isn't any (because it worked fine for tswntk, and me)
I'll take a look, just to be sure. Don't want to leave a potential bug without checking it.

 

[tswntk]

Almost correct.
I'm editing the meta.xml automatically to match the user setting because it speeds the startup process. if the loaded IOS at boot is the same than the user's setting, it prevent disconnecting/reloading IOS/reconnecting the drive. (2 seconds)

ah, sorry, I just copy and paste your formula without too much thinking.
I know it will skip reloading the same ios.

 

[Clutz450]

@Cyan When I first hacked my Wii and was having this hard drive problem I was over at wiihacks.com and they were trying to help me out over there. It's a few years old but maybe something they said in there would help you figure out a solution. Here is the link the the thread.

http://www.wiihacks.com/showthread.php?t=99995

There was one thing that a member over there by the name of cjizzle had said which was,

"I have encountered a few cases where usb 3.0 drives have worked with the d2xv9 b49 cIOS. If you want to give that a try, download them from HERE and extract directly to the wad folder on your sd card, then install using MMM or WiiMod."

I never did try that advice so I'm wondering if it may work. Especially since @sideskroll thinks it's an issue with d2x. Maybe he can try installing that version. I am unable to try this out myself because I am getting ready to head to Japan for 3 weeks tomorrow and just don't have the time. But if you guys are still talking about this when I get back at the end of the month I will try using that version of d2x on my Wii and Wii U and see if anything changes.

 

[Cyan]

like you said, if it's old advice, and they said the beta d2x v9 fixed some HDD compatibility, then updating to d2x v10 will help even more.
no need to use old beta version, v10 is the same as v9.

v9 beta added both (some) HDD compatibility fixes, and Port1 support. but seeing Port1 support created an issue with emuNAND, v9 has been split in two version :

v10 = v8 + v9b HDD compatibility fixes
v10 alt = v8 + v9b HDD compatibility fixes + Port1 (but issues with EmuNAND)

but here, d2x v9b and d2x v10 don't help, because the issues is essentially on WiiU, and WiiU can only install v10 which already contains the fix that forum mentioned.

But thanks for trying to help
it could help a wii user who is on v8 and could update to v10 to fix HDD incompatibility.

I think what's needed is a new d2x update. (d2x v11 anyone?)

 

[Clutz450]

Well if you have the time try reading it over anyway. It's only a page and a half long and may clue you in to something we haven't thought of yet.

Also, I don't know if you saw my previous post but I offered to get you one of those drives that has issues to see if maybe you can figure something out if you are experiencing the issues first hand.

 

[Cyan]

ah, yes, I saw it.
thanks a lot of your offer, but I don't like receiving donation like this (I could pay for it, but in that case I can buy it myself too)
plus, if the drive needs an external power (not a yCable), it will not match french power cord.

maybe if you have the product reference or amazon page, I could check to find the same product in France.

 

[sideskroll]

ah, yes, I saw it.
thanks a lot of your offer, but I don't like receiving donation like this (I could pay for it, but in that case I can buy it myself too)
plus, if the drive needs an external power (not a yCable), it will not match french power cord.

maybe if you have the product reference or amazon page, I could check to find the same product in France.

http://www.amazon.fr/Western-Digita...F8&qid=1452292633&sr=8-1&keywords=wd+elements
That's mine. It's self powered (Y-cable so even if you bought it elsewhere it should be fine.( And I GUARANTEE you it will exhibit the same behavior that mine)

 

[sideskroll]

anyway, did you try loader IOS 249 while the XML is still on 58 ?
xml ios58-> spin up -> mount partition -> read cfg -> see setting 249-> disconnect partition -> reload to 58-> remount partition -> load GUI

I did. It is basically the same as I've been doing (selecting IOS 58 inside the loader, relaunching the loader and then resetting to defaults. Since reset to defaults doesn't translate the settings to the xml file. In practice is EXACTLY the same.I checked)
And yes. Like I said before: It does work that way. Albeit a bit slower but works. Kinda wonky though, it's hard to explain but I "feel" like the loader isn't as stable as it used to be. It does bug out sometimes. (which I'm attributing, again. To the cIOS compatibility issues with WD drives)
In the end, I honestly don't think these issues we're facing have anything to do with your code.
Let me give the results of my tests so far (the more important ones at least) I thought I'd give other cIOS a try to see if the base was the issue.

- Loader IOS 249 (base 56) [xml and cfg]: Doesn't work (works if I previously initialize the drive by X means, be it launching HBC and selecting USB or connecting the HDD while inside the system menu *WITH THE VWII ALREADY LOADED* basically)

- Loader IOS 250 (base 57) [xml and cfg]: ^^same as above ^^

- Loader IOS 251 (base 58) [xml and cfg]: Launches the loader fine (no need to initialize the disk beforehand) but doesn't even recognize there's a drive connected. Loads as expected and sits there without being able to mount the partition.

- Loader IOS 58 [xml and cfg]: Works. (mounts partition and can launch games. Though wonky like I said.)

- Loader IOS 249 [cfg] 58 [xml]: ^^Same as above^^

Again, the issues seem to be in the way cIOS 249 (or any other cIOS for that matter) initialize the drive. Which would explain why the freezes and/or bugs occur mostly when reloading the gui eg: coming out of a game, going into settings and back etc.

it's neither a bug or done on purpose.
it's just that I forgot that the settings could be edited by using the reset option
I'll add the meta.xml reset at the same time.
Thanks for reporting that issue.

You can add that it won't register any changes in the xml UNLESS you explicitly delete (clear) the actual IOS in settings and manually re-add it. (eg: if you reset to default, then go into settings-->LOADER IOS *should be IOS 249 after the restore* and hit accept/OK it won't register. You NEED to clear the ios and re-enter it. Then it works as expected)
That's why my changes weren't registering.

About the xml edited to 58 when you set the loader's IOS to 249, ... I don't trust it. sorry.
Probably a wrong user's manipulation.
the loader can't technically set a different number than the one you enter.

Maybe there's a bug, but I feel like there isn't any (because it worked fine for tswntk, and me)
I'll take a look, just to be sure. Don't want to leave a potential bug without checking it.

See my previous paragraph. You were right. It was user error (kinda) combined with a forgetful @Cyan

I've been toying with the idea of testing d2x rev 53. Just for shits and giggles. I'm not too concern about emuNAND compatibility since most of my stuff runs on neek.
But, would it help? COULD it help? Is it worth the trouble?

I'll run a syscheck on the Wii. I want to see if it is using d2x v10 or what (I didn't mod it) if it is then the issue could be with the installer mod by @FIX94 ?? Maybe? Cause AFAIK the patch is the same for Wii and vWii?
If it's running a different cIOS then I guess v10 has compatibility issues with certain drives (In which case i could test the Wii by installing v10 and seeing if the drive still works)
Sorry for the long ass post. I like to be as specific as I can.
And thanks for your time.

*EDIT/UPDATE* The Wii has the d2x v10 (r52) patch as well. AND like I said it works perfectly with the same HDD.
So, back to my original theory: it's either that the d2x patches are different for Wii and for vWii (and the one for vWii has issues initializing drives that the Wii doesn't have) or the installer does SOMETHING SOMEWHERE (not sure why, what or how and most likely I'm talking out of my ass here) that creates this issue.
It makes no sense that the same patch would work on one console but not on the other... That means that the HDD IS cIOS compatible. The issue lies somewhere else...

 

[GreyWolf]

Do you have one of those USB charging cubes for mobile phones? Try plugging the non-data plug of the Y-cable into it instead of the other USB port.

It's probably not the problem but just throwing that out there. FWIW my drive enclosure doesn't like d2x v8 and lower. It freezes while writing.

 

[sideskroll]

Do you have one of those USB charging cubes for mobile phones? Try plugging the non-data plug of the Y-cable into it instead of the other USB port.

It's probably not the problem but just throwing that out there. FWIW my drive enclosure doesn't like d2x v8 and lower. It freezes while writing.

I doubt that's the issue. But I'll try anyways.
Although I think it'll be easier to just plug the power lead into my xbox which is sitting right next to the Wii U. (the power lead is very, VERY short.)
Like I said, I would be fine with it IF the HDD would behave the same way on both consoles.
But as it stands right now, d2x v10 (r52) works fine on Wii but is unable to initialize on vWii.
That doesn't make sense. Unless the patches are different...
(BTW, please check you PM)

*EDIT* I was thinking that maybe. Patching the original base ios' externally and installing them as wads (ala modmii) could solve the problem? But then again, how does modmii build the cIOS'? I think it downloads em from Nintendo and patch them on the spot, right? What does it use to patch them? The original d2x installer? A mod of it? It could all be related to the installer mod by fix (although, again. I'm not really sure how or why it would "kinda work")
Fact is: d2x cIOS' built by modmii and installed as wads work 100%. And cIOS' patched by the installer don't. (At least for WD drives)
See why I'm losing my mind over this? I don't like it when things that should be working don't, "just because". Without any logical explanation.
Should I try rev53? I doubt it would help though, since the changelog doesn't state anything regarding hdd compatibility since v9...
Sorry for the possible typos. The edit was done from my phone...

*EDIT2* Tested with external power (xbox like I said).
Same results as above. Exactly the same (not that I expected a different outcome) It was worth the shot though.
Thanks for the suggestion.

 

[BlazeHeatnix]

I tried to install a lot of Gamecube banners by downloading them in the loader, but now it says "85 files not found on the server". There are several games that don't have banners when they should, such as Viewtiful Joe. I went to http://nintendont.gxarena.com/banners/ and the banners ARE there, but USBGX just isn't downloading them. Furthermore, games that do have banners sometimes don't have custom music.

 

[tswntk]

Fact is: d2x cIOS' built by modmii and installed as wads work 100%. And cIOS' patched by the installer don't. (At least for WD drives)
See why I'm losing my mind over this? I don't like it when things that should be working don't, "just because". Without any logical explanation.
Should I try rev53? I doubt it would help though, since the changelog doesn't state anything regarding hdd compatibility since v9...
Sorry for the possible typos. The edit was done from my phone...
.

Don't install wads built by Modmii on vWii, Modmii is not compatible with vWii.
rev53 and 52 have different compatibility, so may be its worth a shot.