Hacking USB Loader GX (vWii) stopped working

[gamecaptor]

I renamed the GXGlobal.cfg to GXGlobal.old and low-and-behold USB Loader GX booted. I'm happy and sad at the same time!

THOUGH the EmuNand seems to be acting weird now (stuff I installed does not show up, can't uninstall things I don't need). I will rebuild it and try it again.

This seemed like a good time to do more testing to see if I could uncover anything else. So I went through all my hard drives to see how they would work:
My Passport Ultra v1.012 (FAT32) USB 3.0 using a Y-Cable
This is my primary drive. Worked with no problem after renaming the GXGlobal.cfg

WD My Passport v1.025 (NTSF) USB 3.0 using a Y-Cable
This booted just fine. I have a lot of stuff on this drive, so until I can move it off I'll test it as NTSF.

My Passport Studio v1.041 (FAT32) USB 2.0 using a Y-Cable
This booted just fine. I have to use the Y-Cable as the drive doesn't get enough power on it's own even though it's USB 2.0

Taking it a step further I went and renamed back the original GXGlobal.cfg file, the one that wasn't working with my My Passport Ultra drive originally, and sure enough it didn't load.

Ok, so once again I renamed the GXGlobal.cfg to GXGlobal.old (so it would create a new file) and tried to boot my My Passport Ultra drive originally and it still didn't load. So whatever happened with the first time I renamed the GXGlobal.cfg was a fluke.

I then took the My Passport Studio v1.041 and it booted just fine.

Tried the WD My Passport v1.025 again and it locked up.

At this point, I'm still leaning toward the drive(s). I'm going to revert back to beta53 this weekend and try this again but a little more incremental this time.

I'm also going to see if I can get my hands on another USB 2.0 drive just for curiosity sake.

 

[Cyan]

switching drives right before booting the loader is not a proper way to test if it boots fine, as the drive spinup and init itself right after you plug it to USB.
If you launch the loader when the drive is in initialization phase, the loader should load fine.
it's even a workaround of this issue "connect the drive only before or at loader's launch" and it should always work.

Did you try to launch the loader without HDD, and connect it at the 20sec countdown?

proper test would be :
shut down WiiU.
connect drive (only one drive, don't plug a WiiU drive or a second one at the same time for the test)
launch to vWii mode directly (press B on pad)
launch the loader right after entering vWii.

it's a long process to always reboot, but for the test it's better to do it always the same way, and boot the loader always after the same time. Doing it would always create consistent test (same method, same timing, etc.)


Also, I released a test build on previous page and asked you to tell me which is the latest message you see on screen. Did you use it? please tell me which is the last message and if it's always the same over all the test you do.

 

[gamecaptor]

I ALWAYS power down the Wii U before switching hard drives. I didn't ever think that the Wii U would be "hot swappable" and it seemed safer to me.

Let me know when you have the new build ready and I will test it next weekend with a new drive. Hopefully it uncovers something!

 

[Cyan]

All users with this issue : does it happen only on vWii or on Wii too?

Do you have the same issue with the forwarder on vWii + r1239?
be sure to install the v5.1Fix (not 5.1 .. which is 2.0)


it will init and mount USB's primary partitions, then load the boot.dol without shutting down the USB drive.
Let me know if it freeze in the forwarder or in the loader (you can detect when the forwarder shutdown and the loader launch because the logo disapear and reapear on screen, the loader has the loading text displayed)


Currently, there are a lot of reports but all of them are not well reported. Only half the informations are given "it doesn't boot, it freeze" etc.
no info on the console used, no info if launched from forwarder or HBC, no info on the port, no info if single or dual HDD connected, which revision of the loader, which setup or if deleted setup, cold boot or not, etc.

Thanks to gamecaptor for his implication (he went up to bought new HDDs just to test debugging this issue!).


and for everyone who downloaded the 1241beta :
The boot.dol test I released was downloaded more than 70 times and I got ... 0 report!
well, thank you beta testers, really helpful...
Why do you download beta tests (potentially dangerous and buggy) if it's not to report back and help me?
I wish I had official closed beta testers to not release tests build to end users who think last is better.

 

[pokeparadox]

Eep sorry, saw this at work earlier in the week but forgot to download it. I'll give it a go now... :x

OK From a fresh boot with my Wii HDD inserted only(In the top back port.) I went directly to VWii and Homebrew Channel and then to USBLoader GX.

It hangs on Initialising HDD: Step 4 - mounting USB 2.0 Success. <-- This is the message still displayed on the screen.

249 - 56 - beta53
250 - 57 - beta53
251 - 58 - beta53

 

[Cyan]

thank you, but there's no message telling "mounting USB2.0"
it's either USB0 or USB1 referring to the USB port where your drive is connected.

I guess it was USB0 then.
What's interesting is that it tells you "success".

I will make a new test build with more detailed informations from that step.

 

[gamecaptor]

And we are back for another round of testing!

Let me lay out the environment.

Installed IOS Versions
vIOS249[56] (rev 21010 Info: d2x-v10beta53-alt-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0

Hard Drives
WD My Passport Ultra (v1.012) USB 3.0 [1 TB]
WD My Passport (v1.025) USB 3.0 [2 TB]
WD My Passport Essential (v2.019) USB 2.0 [1 TB]
WD My Passport Studio (v1.041) USB 2.0 [2 TB]
All FAT32, 32 KB Cluster size, one partition
All using USB Y-Cable

USB Loader GX Versions
r1218
r1219
r1229
r1230
r1241b03

Notes
64 GB SD Card FAT32 (32 KB Cluster size) with ONLY apps/usbloader_gx on it.
Between each round of USB Loader GX version testing I would delete the entire usbloader_gx folder and copy over the new version. I would then load up the new version without a hard drive attached so it can create the new GXGlobal.cfg. I would then shut it down and begin the process of testing the various hard drives.

Here are my testing results
r1218
WD My Passport Ultra - OK
WD My Passport - OK
WD My Passport Essential - OK
WD My Passport Studio - OK

r1219
WD My Passport Ultra - Freezes
WD My Passport - Freezes
WD My Passport Essential - OK
WD My Passport Studio - OK

r1229
WD My Passport Ultra - Freezes
WD My Passport - Freezes
WD My Passport Essential - OK
WD My Passport Studio - OK

r1230
WD My Passport Ultra - Freezes
WD My Passport - Freezes
WD My Passport Essential - OK
WD My Passport Studio - OK

r1241b03
WD My Passport Ultra - Freezes
WD My Passport - Freezes
WD My Passport Essential - OK
WD My Passport Studio - OK

So from the looks of things something in r1219 broke the compatibility with USB 3.0 hard drives (or at least Western Digital USB 3.0 drives). I wish I had some none Western Digital hard drives to test, but I tend to gravitate towards them.

Cyan, I really hope this gives you some insight. Let me know what I can do next to test!

 

[gcunit]

I don't have much to contribute yet, but found this thread while researching my own issue:

I've got an Intenso 1tb USB 3.0 hdd. I've been using it on my Wii (just using a single usb cable) with USB Loader GX just fine.

Today my first usb-y cable arrived in the post. As such it is untested in terms of whether it supplies enough power from the Wii U.

Once in vWii I boot USBloaderGX from the HB channel. When it tries to find the usb device I get the full 20 second countdown with nothing happening, other than the activity light on my hdd being on/flashing. Then a couple of quick messages flash up at the end of the countdown before the message changes to 'Mounting to Port 1' (or similar). It then seems to freeze on that message and the console becomes unresponsive - I have to pull the power cord out to reset.

I'll have another look tonight to see which versions I'm on etc.

 

[Cyan]

thank you for the results.
I wished some of your test drives would freeze only at 1230, but it seems all of them freeze at 1219.
I will recompile a new revision 1218 (just to start on clean base, and see if either the current build environment or the revision is the issue)

All the test are from v10alt or v10 ?


I didn't work on adding SD loggin yet, sorry.
I worked on memory checking, but it broke the loader.

 

[gamecaptor]

I had this installed: vIOS249[56] (rev 21010 Info: d2x-v10beta53-alt-vWii): NAND Access USB 2.0

A friend has some Samsung USB 3.0 hard drives that I'll get my hands on tonight to test. See if yields any different results.

 

[Cyan]

yes, you have this installed, but you didn't tell which slot you used.
I guess the default one for all the tests, so slot249 (v10-alt).

Did you try with slot250 (v10 not alt)?
Some users fixed their issue by using beta52 instead of beta53.

 

[gamecaptor]

Ah, which version of USB Loader GX, yes, 249.

I did not try it with 250, but I can this evening. From my posts back on 1/28/15 beta52 worked just fine.

At this point I could just use a USB 2.0 hard drive and call it a day, but I'm trying to help gather information in hopes it will help you resolve the issue.

 

[Cyan]

no, I don't talk about the "dol version", but about the settings > loader settings > Loader's IOS : 250
or meta.xml > arguments > ios=250
or yes, the "dol version" 250 will work too if you don't have an SD card inserted (or else it will use the settings from the SD card as priority, and will load the settings located there, then reload to slot 249 if you didn't change the default setting, then try to mount USB with the cIOS installed in the slot 249)
or just install beta52 in slot249

USB3.0 should work as USB2.0 on wii (I don't know on vWii, but it should downgrade to 2.0 too), it's not a matter of USB version, but as connector's position (USB2.0 and 3.0 connectors are not located at the same place, if the console is not compatible with USB3.0 then the USB2.0 connectors are making contacts).
But if it's an issue with USB3.0, it wouldn't have work from the start.
the issue here is that a loader's revision which didn't touch USB init is affecting the compatibility. hardware shouldn't matter.


I know you help me resolve the issue.
I wanted to see result with beta52 and all your 4 drives, to see if all of them are working fine or if some drive have issue with beta52 too.
you can test with latest revision only, if all of them work that's enough no need to test previous revisions.

 

[gamecaptor]

Next round of tests.
Test 1
vIOS249[56] (rev 21010 Info: d2x-v10beta53-alt-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
Samsung HX-MTA50DA USB 3.0 [500 GB] (FAT32, 32 KB Cluster size, one partition)
r1241b03 [249; I am assuming this as there is no META.XLM file and it's not labeled]
Result: Does not see the drive at all? A little different error, but same result in a manner.

So I here is something interesting. I wanted to change the dol version in the XML files but there was not one with r1241b03 so I figured I would steal one from another version. I went to the R1230_IOS222-249-250\r1230_IOS249 folder to grab the XML from there. I looked at it real quick and it says:
<arg>--ios=250</arg>
<arg>--usbport=0</arg>
<arg>--mountusb=1</arg>

I then went to the R1230_IOS222-249-250\r1230_IOS250 folder and looked at the XML file and it showed:
<arg>--ios=250</arg>
< arg>--usbport=0</arg>
< arg>--mountusb=1</arg>

So if I understand you correctly if that is what determines the IOS that USB Loader GX tries to load. Back to my previous test from yesterday, there was no XML with r1218 or r1219 or r1241b03. There was with r1229 and r1230, both of which had that argument listed above. So in theory I already tested trying to load 250 with versions r1229 and r1230. But just in case:

Test 2
vIOS249[56] (rev 21010 Info: d2x-v10beta53-alt-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
WD My Passport Ultra USB 3.0 [1 TB] (FAT32, 32 KB Cluster size, one partition)
r1230 [250; deleted the XML]
Result: Freezes

So that didn’t seem to solve anything. Figured it was time to try beta52 in Slot 249 next.

Test 3
vIOS249[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
WD My Passport Ultra USB 3.0 [1 TB] (FAT32, 32 KB Cluster size, one partition)
r1230 [249; deleted the XML]
Result: Freezes

Test 4
vIOS249[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
WD My Passport Essential USB 2.0 [1 TB] (FAT32, 32 KB Cluster size, one partition)
r1230 [249; deleted the XML]
Result: OK

What’s next?

 

[Bug_Checker_]

Spoiler

switching drives right before booting the loader is not a proper way to test if it boots fine, as the drive spinup and init itself right after you plug it to USB.
If you launch the loader when the drive is in initialization phase, the loader should load fine.
it's even a workaround of this issue "connect the drive only before or at loader's launch" and it should always work.

Did you try to launch the loader without HDD, and connect it at the 20sec countdown?

proper test would be :
shut down WiiU.
connect drive (only one drive, don't plug a WiiU drive or a second one at the same time for the test)
launch to vWii mode directly (press B on pad)
launch the loader right after entering vWii.

it's a long process to always reboot, but for the test it's better to do it always the same way, and boot the loader always after the same time. Doing it would always create consistent test (same method, same timing, etc.)


Also, I released a test build on previous page and asked you to tell me which is the latest message you see on screen. Did you use it? please tell me which is the last message and if it's always the same over all the test you do.

Spoiler

I would recommend(just for testing purposes) to not use any other usb devices(microphones/ or hubs except for the 1 hard drive being tested.
So 3 out of 4 usb ports need to be open/empty and not connected or in use.

Next round of tests.
Test 1
vIOS249[56] (rev 21010 Info: d2x-v10beta53-alt-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
Samsung HX-MTA50DA USB 3.0 [500 GB] (FAT32, 32 KB Cluster size, one partition)
r1241b03 [249; I am assuming this as there is no META.XLM file and it's not labeled]
Result: Does not see the drive at all? A little different error, but same result in a manner.

So I here is something interesting. I wanted to change the dol version in the XML files but there was not one with r1241b03 so I figured I would steal one from another version. I went to the R1230_IOS222-249-250\r1230_IOS249 folder to grab the XML from there. I looked at it real quick and it says:
<arg>--ios=250</arg>
<arg>--usbport=0</arg>
<arg>--mountusb=1</arg>

I then went to the R1230_IOS222-249-250\r1230_IOS250 folder and looked at the XML file and it showed:
<arg>--ios=250</arg>
< arg>--usbport=0</arg>
< arg>--mountusb=1</arg>

So if I understand you correctly if that is what determines the IOS that USB Loader GX tries to load. Back to my previous test from yesterday, there was no XML with r1218 or r1219 or r1241b03. There was with r1229 and r1230, both of which had that argument listed above. So in theory I already tested trying to load 250 with versions r1229 and r1230. But just in case:

Test 2
vIOS249[56] (rev 21010 Info: d2x-v10beta53-alt-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
WD My Passport Ultra USB 3.0 [1 TB] (FAT32, 32 KB Cluster size, one partition)
r1230 [250; deleted the XML]
Result: Freezes

So that didn’t seem to solve anything. Figured it was time to try beta52 in Slot 249 next.

Test 3
vIOS249[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
WD My Passport Ultra USB 3.0 [1 TB] (FAT32, 32 KB Cluster size, one partition)
r1230 [249; deleted the XML]
Result: Freezes

Test 4
vIOS249[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS250[56] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
vIOS251[58] (rev 21010 Info: d2x-v10beta52-vWii): NAND Access USB 2.0
WD My Passport Essential USB 2.0 [1 TB] (FAT32, 32 KB Cluster size, one partition)
r1230 [249; deleted the XML]
Result: OK

What’s next?

It appears 1219 changed the way USBAutoMount was handled. Try starting there

Settings.USBAutoMount == ON

https://code.google.com/p/usbloader...source/StartUpProcess.cpp&r=1219&spec=svn1219

 

[gamecaptor]

Interesting observation Bug_Checker_. I'm looking at this issue from a high level, so things like that are missed by me.

Cyan, got any thoughts on that?

 

[Cyan]

Do not delete the meta.xml, it's required to get ahb_access at launch. (cIOS provides it too, but before reloading cIOS it's using ahb to mount SD card and read the setting file, or else it require mounting cIOS first)

the arguments are not used by default, they are commented out.
If you want to use arguments and force specific slot/port/mount at launch then you delete the two commented lines.
editing settings in the loader is automatically editing the meta.xml too.


Yes, the USB automount has been changed, but it's not the issue by itself as it correctly see the setting and try to mount at launch (or else it would only skip HDD detection entirely)
But it could be linked to the issue nevertheless, I'll revert all changes and try to put back changes step by step.

I can also add a SD logger for debug purpose to check where it really freeze.
from the reports I had, it freeze after the USB (port0 I guess) successfully initialized. so either it's in an endless loop waiting for port1 to init, or it's outisde of the init function but don't continue the launch process.

 

[gamecaptor]

Ok, let me know what you want the next setup environment to be and I will gladly do more testing.

 

[Cyan]

I'm starting the test builds.
You can find them here :
http://www.mediafire.com/folder/t2x95zd9rz3rc/USBLoaderGX
in the HDD Test folder

Instruction will be provided in the 7z file.
Test01 is svn r1218 rebuild today to ensure it works fine and we start from here.


Expecting results:
Test01 : works
Test02 : doesn't work
Test03 : works
Test04 : works
Test05 : let me know

 

[pokeparadox]

My results
Test01 :
Test02 :
Test03 :
Test04 :
Test05 :

I will try and set some time aside to test this. I'm pretty busy at the moment so will probably tomorrow night.
Just wanted to let you know I've seen this and will get you some results.