Hacking USB Loader GX will not find HDD

[meretuil83]

Good evening all,
I have tried googling and searching this forum, but i have not been able to resolve my issue.
I figured that the best source would be here instead of all of the random out-dated youtube videos that all say something different.
The process worked great when i first hacked my Wii (a few months ago), I am not sure what changed, but now no matter what i change my settings to - my HDD is not detected.
I am using a 2TB WD Elements USB HDD and below is my system check

Spoiler

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: NTSC-U
System Menu 4.3U (v513)
Priiloader installed
Drive date: 12.07.2010
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x21
Console ID: 170961531
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v4
Found 134 titles.
Found 48 IOS on this console. 15 of them are stubs.

IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249[56] (rev 65535, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 65535, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS251[58] (rev 65535, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 11/28/2018.
[Spolier]

Can anyone give me any tips/feedback that might help with this?

 

[Cyan]

reinstall d2x v10 r52 base 57 into slot 249.
It'll replace your slot which currently contains r53, beta, not good.

OR

go to your loader's setting and replace all references of 249 to 250 (your slot 250 already contains d2x v10 r52 base57!)

 

[meretuil83]

Thank you! I will try this after work and let you know if it works

 

[meretuil83]

reinstall d2x v10 r52 base 57 into slot 249.
It'll replace your slot which currently contains r53, beta, not good.

OR

go to your loader's setting and replace all references of 249 to 250 (your slot 250 already contains d2x v10 r52 base57!)

Good evening Cyan - It does not look like the steps above fixed the issue are there any settings in the loader that could be the issue (I know there are alot) ? Thank you for your help.

 

[Cyan]

that was only half what you had to do.
now you hae a correct cIOS version.

go to usbloadergx settings > loader's settings > loader's IOS : replace the number with 58, restart the loader.

it should fix the issue now.

 

[Deleted User]

if you are using an hdd then you need a y cable. if you are on wii u then you need to connect it on the rear usb port

 

[meretuil83]

Cyan - i did the steps provided and still nothing - would it help if i sent you screenshots of my settings?

Missingphy - thank you for the tip but, if my hdd needed a Y cable - would it have come with my drive? (not meant to be smart - new to this)
the drive was working before with no issues (started in Aug. 2018).

 

[Deleted User]

Cyan - i did the steps provided and still nothing - would it help if i sent you screenshots of my settings?

Missingphy - thank you for the tip but, if my hdd needed a Y cable - would it have come with my drive? (not meant to be smart - new to this)
the drive was working before with no issues (started in Aug. 2018).

well if your hard drive plugs into the wall current then plug it. if your hdd doent have a y cable slot then you need to replace it with one like this one: https://www.amazon.com/dp/B0751BPL26/ref=twister_B07C3CLKB6?th=1

--------------------- MERGED ---------------------------

well if your hard drive plugs into the wall current then plug it. if your hdd doent have a y cable slot then you need to replace it with one like this one: https://www.amazon.com/dp/B0751BPL26/ref=twister_B07C3CLKB6?th=1
check the 4th image and see if your hdd has that kind of slot

 

[Cyan]

the Y-cable is needed on WiiU (not provided by the drive as it's not needed on PC, or other hardware, only on WiiU).
it shouldn't be needed on Wii, and you posted on the wii section and your syscheck reports a Wii, so I suppose you shouldn't need the y-cable.
If you need it, you usually know because your drive is making clicking noises, or bipping sound, or flashing leds instead of properly lighted led.


how are you launching the loader ?
Priiloader, forwarder, or HBC ?

Using IOS58 usually fix the HDD detection issue.
the IOS I made you replace is just a fix for compatibility, not for drive detection.
You settings should be like that :

slot 249 : d2x v10 r52 base57
USBLoaderGX Loader's IOS : 58
USBLoaderGX Game's IOS : 249 (or 250)
USB Plugged into the bottom USB Port (USB Port 0)

Launch the loader from HBC, or from the forwarder 5.1 (previous version of forwarder didn't init the hdd properly).

 

[meretuil83]

Good morning Cyan - i was able to get it working!
I ended up reformatting and partitioning my drive again - working like a charm now.

I am not 100% what the issue was:
I did have other rom files on the same partition (did not know better) and maybe there were too many actions going on?
or it could have just been file corruption, but either way thank you so much for your help and patience!