Hacking USB Loader GX (vWii) stopped working

Cyan · Feb 25, 2015

Thanks,
I would have liked consistent tests.

If you do the new method, do it with 1218/1219 too.
if you test older version, do the tests the same way as before.
Please, at least test 1180 with the previous method to know if it's affected or not. Users want to boot the console and play, not boot>delete SD>reboot>reconnect>etc.

Here, only r1217 had both method tested :
old one freeze, new one works.

I think connecting the HDD while in vWii is fixing the issue by itself.
The issue is probably because you have latest WiiU version which shutdown all non-WiiU connected HDD at launch.

I expect that even 1180 won't work, because it's not an issue in the loader but a behavior of the console.
I don't know why it affects only some HDD.
I can try to always force IOS58 at launch on vWii and reload to cIOS after HDD init if requested.

I also asked a test previously, but I don't remember if you did it or not.
so, I will re ask here:
anyone with the freezing issue can test it:
r1241
edit meta.xml
remove commented lines
set -ios=58
launch the loader

it should use IOS58 and mount the HDD correctly, as 1218 does.
I want to be sure using IOS58 is fixing the issue. it should ini and mount the drive correctly.

ryanstein · Feb 26, 2015

Cyan said:
Thanks,
I would have liked consistent tests.

If you do the new method, do it with 1218/1219 too.
if you test older version, do the tests the same way as before.
Please, at least test 1180 with the previous method to know if it's affected or not. Users want to boot the console and play, not boot>delete SD>reboot>reconnect>etc.

Here, only r1217 had both method tested :
old one freeze, new one works.

I think connecting the HDD while in vWii is fixing the issue by itself.
The issue is probably because you have latest WiiU version which shutdown all non-WiiU connected HDD at launch.

I expect that even 1180 won't work, because it's not an issue in the loader but a behavior of the console.
I don't know why it affects only some HDD.
I can try to always force IOS58 at launch on vWii and reload to cIOS after HDD init if requested.

I also asked a test previously, but I don't remember if you did it or not.
so, I will re ask here:
anyone with the freezing issue can test it:
r1241
edit meta.xml
remove commented lines
set -ios=58
launch the loader

it should use IOS58 and mount the HDD correctly, as 1218 does.
I want to be sure using IOS58 is fixing the issue. it should ini and mount the drive correctly.

Well thanks for the suggestions to try, but none of them are working. I tried plugging it in when vWii launches, no dice. I modified the arguments to try IOS 58, 249, 250, and 251 and none of them worked. I tried formatting a flash drive as FAT32 with 32kb clusters, and it wasn't recognized either. It's baffling to me that HBC can use it no problem and all my other apps and the loader refuses.

Cyan · Feb 26, 2015

I would like to be sure everyone is reporting the same issue.
what does it do?

It's not detected at all and after 20second it loads without USB, or do you have the same issue than explained in the thread?
The current issue is that hard drives ARE correctly detected, it doesn't wait 20 second in the mounting screen as it's detected quickly, but then freeze on that screen and doesn't complete launching process.

Does it freeze too?
Does 1218 work fine?
Does 1180 work fine? if it does, which one broke the detection?

If none works, do you have up to date WiiU or an old version?

cutterjohn · Feb 26, 2015

gamecaptor said:
(Thank you remote access) The USB Hard Drive at my work is a WD My Passport v1.025 and is on the latest firmware. I'll bring it home on Monday to test with anyways.

It's USB Loader GX. The USB code is apparently borked, or borked in a new way since 1218.

hdd fw change is EXTREMELY unlikely to have ANYTHING to do with this.

So far I've tried a Seagate 1TB(FAT32 32kB clusters) and one that I put together using an enclosure that was listed as working(theoretically, amazon claimed same model # but Amazon's been known to play fast and loose with model numbers before as well as masters of tech spec vagueness) w/a 2.5" WD Blue drive again FAT32 32kB cluster.

Neither worked 1241, although I did get the Seagate to kind of work, by waiting for the countdown and THEN plugging it in(didn't try this with the other enclosure) as it still wouldn't load backups, hanging on a black screen and never getting to the generic warning screen at all. (I'd assumed that the new enclosure would just behave the same).

In between double checked drive format(500GB drive/enclosure) and contents(they were fine) and SD card.

Checked syscheck whatsisden one but v2.3.0 as the original site appears to be down(<whatsis>den) same log as OP.

So further reading through page 1 and about 2/3 of page 2 decided to try 1218. BINGO! Works!

...and that's as far as I'm getting today unless I check the USB info for both enclosures, but I think that there's something broken in the USB initialization code personally as the drives demonstrably are functional and will work. I think that this is further backed up by the fact that not plugging in the 1TB USB (Seagate) until the USB check countdown starts would be a dead giveaway. My guess would be something right at the start of the USB hdd code either just before or after where it would normally start the countdown if no drive detected... although that might not be the entirety as even plugging in late does not allow full functionality apparently, although I'll admit to not testing it exhaustively as I already had the second enclosure and drive on the way, and couldn't find my other enclosure that I should have kicking around here...

(Pretty amazing as it's this hideous electric blue color... also have a 4th enclosure that I could try as well, but ATM I'm trying to recover a drive with it but am about to give up on it... another 2.5" enclosure I think a rosewill not sure what the hideous blue one is, the one using the 500GB drive is a Kingwin and obviously the 1TB is seagate(no idea the ODM of the enclosure though as I'm sure Seagate didn't design it(i.e. they just supplied the drive and assembled/boxed it) and that's it...)

[EDIT]
BTW: the Seagate USB enclosure is a SINGLE connector, mini -> standard
The Kingwin is a dually, mini->2 standard(1 extra power) y cable
[/EDIT]

Cyan · Feb 26, 2015

like I said many times, r1218 is a unique version, I edited it to not reload cIOS and use IOS58. Previous and newer version are using cIOS to mount HDD.
Did you try older version ? (r1217 and lower)

Testing only 1218 is not very useful for me as I know it's working, and as users reported that using 1241 and setting IOS to 58 doesn't fix the issue, so the IOS to use is not the problem.
r1218 doesn't have anything different in the HDD init sequence. (it only doesn't reload to cIOS before initializing the drive and that's all there is different)

I released test builds, that only one user reported the result.
Could you take the time to test them and report your results too?
thank you

cutterjohn · Feb 26, 2015

Cyan said:
like I said many times, r1218 is a unique version, I edited it to not reload cIOS and use IOS58. Previous and newer version are using cIOS to mount HDD.
Did you try older version ? (r1217 and lower)

Testing only 1218 is not very useful for me as I know it's working, and as users reported that using 1241 and setting IOS to 58 doesn't fix the issue, so the IOS to use is not the problem.
r1218 doesn't have anything different in the HDD init sequence. (it only doesn't reload to cIOS before initializing the drive and that's all there is different)

I released test builds, that only one user reported the result.
Could you take the time to test them and report your results too?
thank you

Yep. But probably not until tomorrow or over the weekend. I just came back to edit my prior post to mention that I was going back to read the rest of the thread now.

I was merely trying to eliminate the drives/enclosures as problems since the wiki theoretically listed the 2nd bare enclosure that I purchased as working, but it didn't(w/1241) but did w/1218(as above). Next I was going to double check the product #s and pull the USB vendor/device IDs and other info off linux later as I need to be booted into windows right now to take care of some other things and I don't believe that I've found any USB utils that give as much info as I can pull under linux, or at least it's easier/faster for me to check info like that under linux.

[EDIT]
I'm brand new to the Wii U/wii hacking(well vwii for me) as I just picked this up the other week, so if you want specific things you'll probably have to be extra explicit as to what to do as I only have vague idea about cios and all that stuff ATM, along with avoid WADS for vwii...(and no bootmii)...
[/EDIT]

Cyan · Feb 26, 2015

ok, that's no a problem. Thank you for being here and wanting to help.
at least I have a second user who can test and reports the results.

I also don't have a lot of time to work on fixing this issue.
Proper debugging and step by step log would help, but I'll have to code this option in the loader.

for cIOS information :
there are two cIOS for vWii : r52 (work only with USB port0 located at the top rear), r53 (work with all USB Ports)
This issue seems to happen only when using r53 (which a lot of guide suggest to install, even if it's known to have different issues over r52)
what's strange is that users report that using IOS58 is not helping, while using a different cIOS is.
using r1218 is working, which is also using IOS58.

So, there's a lot of contradictories.
sometime I end doubting if the users are correctly testing/settings the loader. Not having the issue myself is hard to debug it with random results.

cutterjohn · Feb 27, 2015

Cyan said:
ok, that's no a problem. Thank you for being here and wanting to help.
at least I have a second user who can test and reports the results.

I also don't have a lot of time to work on fixing this issue.
Proper debugging and step by step log would help, but I'll have to code this option in the loader.

for cIOS information :
there are two cIOS for vWii : r52 (work only with USB port0 located at the top rear), r53 (work with all USB Ports)
This issue seems to happen only when using r53 (which a lot of guide suggest to install, even if it's known to have different issues over r52)
what's strange is that users report that using IOS58 is not helping, while using a different cIOS is.
using r1218 is working, which is also using IOS58.

So, there's a lot of contradictories.
sometime I end doubting if the users are correctly testing/settings the loader. Not having the issue myself is hard to debug it with random results.

Thanks for the updates/help too.

OK. I read through all of the thread and see that you recommend against the alt version of the cios installation and even more to the point really only using the (58 one), but I also see it looks like removing already installed might be dicey and I followed truth's guide in the guide forum, so I did all 3 and his recommended alt(2 USB) option.

Would you like me to switch from v53-alt to the non-alt option when I test? (I'm guessing that 2 USB ports just means for data xfer and that ports will still provide power if not data? (for y cable enclosure)

Try both? (I followed truth's guide...)

Oh, since you probably know and will save me searching, I didn't do the IOS backup, apparently missed it and didn't notice it until last night. Is it still possible to get a good semi-brick recoverer now that I've installed the cios(?) or am I already SOL?

Also if I have time I can pull another 2.5" drive from a notebook(finished project but haven't removed extra drive and put odd back in yet) and a third(rosewill) enclosure. Wii U's a bit of a PITA to get to and when it freezes it's only escapable(that I've found) by power cycle(power cord), so it'll take me a while to try combos but I'll start with the 500GB FAT32/32kB cluster/single part drive and go from there unless you want me to try older cios too...

gamecaptor · Feb 27, 2015

Hurray for cutterjohn for getting into the mix! Your help testing is appreciated!

Cyan · Feb 27, 2015

You can still use Y-cable for power source with r52.
(unless WiiU is switching the port's power OFF because there's no WiiU disc connected at boot?)

You can extract/dump your IOS now. these steps were added recently, that's probably why you missed them.

Instead of deleting an IOS slot's content, you can keep it if you don't use it, or replace it with another one if you need a different version.

I think the current issue (loader freezing at USB Init sequence) is happening only with v10-alt (r53).
You can try to install v10 (r52, non alt) with a base IOS 56 in your slot 249 and try again to see if it fixes the issue.
If it works with r52 but doesn't work with r53, then you have the same issue as the one described in this thread.

Currently, we are only trying to narrow the issue and find what's going wrong. I didn't create specific builds with USB access and HDD initialization log.

We are only testing different "things" and note what's good or wrong to narrow and exclude possibilities.
r1219 (or any other than 1218)
- Test a different cIOS version (r52<->r53): reinstall cIOS with the other version, same base.
- Test a different IOS base (56, 57, 58) : you should have these base already installed if you followed the softmod guides, just set the meta to use slot249/250/251
- Test a different IOS (IOS58) : Set the meta to use IOS58
- Test launching from the forwarder 5.1fix instead of HBC :

r1218 :
- Test using a cIOS : Nobody tried this yet. To do this, edit the meta.xml and remove the commented lines. Edit the -ios= to set it to 249
It will force r1218 to use cIOS instead of IOS58 for HDD init. I would like to know if that will trigger the freeze too.

What I gathered so far on this issue :
WiiU vWii only (doesn't affect Wii)
Dependent on current WiiU system version ? (it affects only users with latest WiiU update)
d2x cIOS v10-alt only
USB3.0 only? (at least, the tested drives were all USB3.0)
Western Digital only?
It works fine with r1218 which use IOS58
It doesn't work with older or newer revision, even when using IOS58 (that's the weirdest thing ever!), why does users never reported this issue for two years? probably linked to latest WiiU update.
the drive works fine with nintendont and HBC.

gamecaptor · Feb 27, 2015

Hey Cyan,

remember I'm NOT using d2x-alt and it's still breaking for me.

Current cIOS setup
vIOS249[56]: d2x-v10beta52
vIOS250[57]: d2x-v10beta52
vIOS251[58]: d2x-v10beta52

I'll be doing some more testing this weekend.

gamecaptor · Feb 28, 2015

I returned to my original method of testing, which is:

Delete the contents in the usbloader_gx folder on the SD card and put in the version listed, insert it into the Wii U and turn on the Wii U.
Boot up ULGX (via HBC) once WITHOUT the hard drive attached (so it can create the config file and I can verify the version number).
Power down the Wii U (via ULGX). Plug in the hard drive and turn the Wii U on and launch ULGX (via HBC).
After it loads or locks-up I would power down the Wii U (either via ULGX or pulling the power plug), eject the SD card and unplug the hard drive and repeat from step 1.

And as a reminder this is my current cIOS setup:
vIOS249[56]: d2x-v10beta52
vIOS250[57]: d2x-v10beta52
vIOS251[58]: d2x-v10beta52

So this round of testing is VERY weird. I’m back to my original test methods with only one change in environment. I replaced my 3 ft. USB 3.0 Y-cable with a 1 ft. USB 3.0 Y-cable. I’m having a really hard time imagining this would have any effect on the outcome, needless to say, it seems to have.

r1180
WD My Passport Ultra USB 3.0: Freezes
WD My Passport Essential USB 2.0: ULGX loaded but it reported no USB device was found?

r1200
WD My Passport Ultra USB 3.0: Freezes
WD My Passport Essential USB 2.0: ULGX loaded but it reported no USB device was found?

r1218
WD My Passport Ultra USB 3.0: Freezes
WD My Passport Essential USB 2.0: ULGX loaded but it reported no USB device was found?

Wildly different outcome then I expected to see here. I was starting to wonder if maybe the SD card was an issue. I reformatted the SD card (FAT32/32 kb clusters) and did another test, this time with the USB 2.0 hard drive first.

r1218
WD My Passport Essential USB 2.0: OK
WD My Passport Ultra USB 3.0: Freezes

So this makes no sense what so ever. r1218 should have booted the USB 3.0 drive just fine. That was the version that was confirmed working.

I will go back to my 3 ft. USB 3.0 Y-cable and try it again another day.

Also worth (re)mentioning, the SD card I am using is for testing purposes only; it has nothing on it besides USB Loader GX. And both of the hard drives (USB 2.0 & 3.0) are setup the same way (duplicate files on both).

I really hope more people will jump in and do some testing

Cyan · Feb 28, 2015

thank you again for all your time spending on this issue.
Just note that you don't need to run the loader once to create the setting file. You can connect the drive directly without the setting file.
If there's no setting file, it's using default settings (which are the same than the created file).
It will prevent you waste a reboot every time.

Are you "quick booting" to vWii?
or launching wiiU and select vWii?

Are you using the WiiU sleep mode to quick boot?

I wished that issue was more logical.
It's hard to understand the issue when it's random.

for your info : I tested the version I gave you with my HBC (Wii) and it's detected correctly. I can launch it and it works fine.
I don't know why it didn't show up in your HBC.
but even if it works for me, now I'm afraid of users having issues I don't have

I don't want to release revision with random issue, but without enough beta users, it's hard to tell.
I'll probably release it and just hope users won't have issues.

ryanstein · Feb 28, 2015

Cyan said:
You can still use Y-cable for power source with r52.
(unless WiiU is switching the port's power OFF because there's no WiiU disc connected at boot?)

You can extract/dump your IOS now. these steps were added recently, that's probably why you missed them.

Instead of deleting an IOS slot's content, you can keep it if you don't use it, or replace it with another one if you need a different version.

I think the current issue (loader freezing at USB Init sequence) is happening only with v10-alt (r53).
You can try to install v10 (r52, non alt) with a base IOS 56 in your slot 249 and try again to see if it fixes the issue.
If it works with r52 but doesn't work with r53, then you have the same issue as the one described in this thread.

Currently, we are only trying to narrow the issue and find what's going wrong. I didn't create specific builds with USB access and HDD initialization log.

We are only testing different "things" and note what's good or wrong to narrow and exclude possibilities.
r1219 (or any other than 1218)
- Test a different cIOS version (r52<->r53): reinstall cIOS with the other version, same base.
- Test a different IOS base (56, 57, 58) : you should have these base already installed if you followed the softmod guides, just set the meta to use slot249/250/251
- Test a different IOS (IOS58) : Set the meta to use IOS58
- Test launching from the forwarder 5.1fix instead of HBC :

r1218 :
- Test using a cIOS : Nobody tried this yet. To do this, edit the meta.xml and remove the commented lines. Edit the -ios= to set it to 249
It will force r1218 to use cIOS instead of IOS58 for HDD init. I would like to know if that will trigger the freeze too.

What I gathered so far on this issue :
WiiU vWii only (doesn't affect Wii)
Dependent on current WiiU system version ? (it affects only users with latest WiiU update)
d2x cIOS v10-alt only
USB3.0 only? (at least, the tested drives were all USB3.0)
Western Digital only?
It works fine with r1218 which use IOS58
It doesn't work with older or newer revision, even when using IOS58 (that's the weirdest thing ever!), why does users never reported this issue for two years? probably linked to latest WiiU update.
the drive works fine with nintendont and HBC.

Remember I tried on r1241 with 58, 249, 250, and 251 by editing meta.xml. None of them worked for me. I have a Wii U disk in the drive, too. I also changed from v10-beta53-alt to v10-beta52 and that did not help.

ryanstein · Feb 28, 2015

Cyan said:
I would like to be sure everyone is reporting the same issue.
what does it do?

It's not detected at all and after 20second it loads without USB, or do you have the same issue than explained in the thread?
The current issue is that hard drives ARE correctly detected, it doesn't wait 20 second in the mounting screen as it's detected quickly, but then freeze on that screen and doesn't complete launching process.

Does it freeze too?
Does 1218 work fine?
Does 1180 work fine? if it does, which one broke the detection?

If none works, do you have up to date WiiU or an old version?

For me, it loads correctly and I can do everything in HBC including emulators, Nintendont, etc. Until I launch a loader, that is. Then it waits the 20 seconds, and loads into channel mode where I can launch any vWii channel (though it doesn't load previews) but nothing else. At this point, no loader version will work for me that I've tried. All 5 test versions failed.

Cyan · Feb 28, 2015

Your issue is different, as it continue loading after the 20 seconds, which means HDD has not been detected at all.
The problem in this thread is that it freezes at the HDD detection screen and stay there indefinitely. It doesn't launch the loader in channel mode.

ryanstein · Feb 28, 2015

Cyan said:
Your issue is different, as it continue loading after the 20 seconds, which means HDD has not been detected at all.
The problem in this thread is that it freezes at the HDD detection screen and stay there indefinitely. It doesn't launch the loader in channel mode.

Sorry for congesting the thread, I thought this was a related issue, it sure sounded similar. What could be the cause of not detecting the HDD in a loader but correctly everywhere else? Anything I should check for to fix it?

Cyan · Feb 28, 2015

I would say you need Y-cable, but you already have it.
Are you using HUB? hubs are not working with cIOS.
though, IOS58 should work with hub but you said it didn't help.

Is your cable too long? try another cable, try another HDD to see if it's an hardware issue or a software setting.

ryanstein · Feb 28, 2015

Cyan said:
I would say you need Y-cable, but you already have it.
Are you using HUB? hubs are not working with cIOS.
though, IOS58 should work with hub but you said it didn't help.

Is your cable too long? try another cable, try another HDD to see if it's an hardware issue or a software setting.

No hub, I'm plugging directly into the Wii U with a Y-cable (I used to use it all the time without a y-cable but I switched to it when I started running into problems.) That cable was less than a foot, so that's not it. I also tried it with that flash drive which didn't work at all either, so I think it is probably more to do with however it detects drives.

cutterjohn · Mar 3, 2015

Sorry guys no time over the weekend as it turned out and I got my copy of Xenoblades today, so... but I'll still try at least with alt and what I have and then move on(? down?)wards...

[EDIT]
Since the topic of a hub came up, and it's unclear from my prior posts, I am NOT USING a hub with any testing that I do...

...and there is a possibility that I MAY be able to acquire an actual wii as IIRC my sister and brother-in-law bought one for some reason (never saw them use it) and last I saw it it looked mint... just need to ask, ah offtopic/I digress... :/
[/EDIT]

[EDIT2]
so as to not double post and this isn't all that important again I'll likely have no time to try again until friday-weekend and well weekend is looking to be "balmy" 30sF (and sunny) so I'll probably be outdoors... if only this had shown up a month ago... good excuse to avoid (10F highs, -20sF windchill, -10sF lows...)
[/EDIT2]

Hacking USB Loader GX (vWii) stopped working

GBATemp's lurking knight

Member

GBATemp's lurking knight

Well-Known Member

GBATemp's lurking knight

Well-Known Member

GBATemp's lurking knight

Well-Known Member

R.I.P. Densetsu. Legends never die!

GBATemp's lurking knight

R.I.P. Densetsu. Legends never die!

R.I.P. Densetsu. Legends never die!

GBATemp's lurking knight

Member

Member

GBATemp's lurking knight

Member

GBATemp's lurking knight

Member

Well-Known Member

Similar threads

Popular threads in this forum