Hacking Homebrew app Strange issues with USB detection using Loader GX

[MaxBox]

I would try d2x v10 beta 52 with base 58 first, maybe also try hermes cios's 222-224. Look in modmii classic's download page 4. You could also try d2x CIOS of other bases, but I would start with what I mentioned above

I can't find the classic download page that you're referencing. Also, is there a chance I messed something up during the initial installation, and if so, should I over-write/reinstall? I made a NAND backup right after I did the initial ModMii installation.

The new drive/enclosure doesn't seem to be detected in either slot, now. It's not externally powered, and is a single USB cable.

Also, you listed v10 beta52 with base 58, but not the slots or revisions.

I'm trying to use d2x to retry the recommended cios files. V10b52 base 57 slot 249 rev65535 worked.

base 56 slot 250 downloads the metadata but gethostbyname times out with a -125 error.
Base 38 slot 251 gethostbyname fails with a -6 error immediately.

 

[XFlak]

Slots and version numbers don't really matter, but yeah, grab modmii, make sure you're running modmii (classic) not modmii skin, then from the main menu enter 4 for download page 4, or A for Advanced downloads

If you're worried you messed something up, just post a syscheck https://gbatemp.net/threads/posting-a-system-check.300279/

And/or drag and drop the syscheck.csv onto modmii.exe and it will analyze it and let u know if anything looks fishy

 

[MaxBox]

Slots and version numbers don't really matter, but yeah, grab modmii, make sure you're running modmii (classic) not modmii skin, then from the main menu enter 4 for download page 4, or A for Advanced downloads

If you're worried you messed something up, just post a syscheck https://gbatemp.net/threads/posting-a-system-check.300279/

And/or drag and drop the syscheck.csv onto modmii.exe and it will analyze it and let u know if anything looks fishy

Which of these are you referencing? I know I'm getting real nitty-gritty with specifics but it's how I operate. Plus it avoids any potential incorrect choices. Then I assume I use d2x to install them, is there a guide on how to manually provide the chosen files?

I'll do another syscheck to soothe the heart. edit: ModMii reported no errors and everything up to date with the sysfile.

 

[XFlak]

Enable the hermes cios option, then run the syscheck wizard again

 

[MaxBox]

Alright, I enabled option H in the settings. When running the wizard, it reported 5 files needed to be downloaded:
cIOS202[60]-v5.1R
cIOS222[38]-v4
cIOS223[37-38]-v4
cIOS224[57]-v5.1R
Yet Another WAD Manager Mod.

Using YAAMM, I installed all four successfully and rebooted the Wii. The HDD enclosure is connected to port0 (the one closest to the side of the wii), and has its power switch toggled on. At no point does the status LED turn on, nor do I hear the hard drive spinning.
Homebrew boots successfully but doesn't detect a USB drive. Launching GX Loader gives the "waiting for HDD" screen. Wii turned off, drive plugged into slot1. Same behavior. USB drive port setting changed from 0 to 1, rebooted, same behavior.

For the hell of it, I tried the ModMii USB Loader setup tool, and used FAT32. The drive was formatted again to FAT32. It did look like the gx loader files were edited more recently. I used Wii Backup Manager to transfer 2x wbfs game files. Both slot0 and slot1 had the same behavior as before.

 

[XFlak]

Now try adjusting your usbloader global settings to use IOS58, 222, 223, 224, 250, 251, and see if any detect your hdd

 

[MaxBox]

Now try adjusting your usbloader global settings to use IOS58, 222, 223, 224, 250, 251, and see if any detect your hdd

On all of them, the program reported waiting for my hard drive. The status LED never flickered.
To be clear, within loadergx's settings, I changed the Loader's IOS.

 

[blackb0x]

@MaxBox Does the loader ever say if it's loading your config files or reinitializing devices prior to the waiting?

 

[XFlak]

I'm not sure if it makes a difference, but try adjusting the bootios argument in the meta.xml. You may need to uncomment these arguments (as indicated within the meta.xml itself)

 

[blackb0x]

@XFlak Depending on how he replied, that would of been my suggestion.

I can't tell if he's still trying to use the Bipra HDD or if he's bought something else. But if he does see them messages then his HDD works but can't handle IOS reloads, so it'll have underlying issues no matter what he does.

Personally I'd want to return the USB HDD and buy something that works correctly right out of the box.

 

[MaxBox]

Thanks for the continued support. I returned the Bipra, and have been using the SABRENT 2.5-Inch SATA to USB 3.0 HDD Enclosure with a 160GB Fujitsu HDD I got out of my roommate's computer. It's perfectly accessible using my computer and laptop.

That being said, with the Bipra, the Wii could occasionally detect it and see the game files within. With the new enclosure, it's not been detected by homebrew or any other app.

Upon booting Gx Loader, the shown steps are as follows:
Initializing sd card
Initializing usb device1
Waiting for HDD: (Timer)
Loading Config Files
Reloaded into cIOS 251 R65535
Reinitializing devices
Checking Installed MIOS
Loading resources
<app then loads>

Also, with whatever configuration of cIOS I now have, attempting to play a vanilla disc game prompts me to update my Wii, and blocks me from returning to the home menu.

As for editing gx loader's XML file, the default was 250, and I additionally tried 224, and 222. If I should try others, please specify which, or at least a range. At no point during testing did the enclosure seem to have any activity.

Here's the sys check:

Spoiler: Syscheck

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: 07.14.2008
Homebrew Channel 1.1.2 running on IOS58
Hollywood v0x11
Console ID: 86923237
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v4
Found 93 titles.
Found 50 IOS on this console. 5 of them are stubs.
IOS3 (rev 65280): Stub
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
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[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
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[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
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[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
IOS51 (rev 4864): Stub
IOS52[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
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 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
IOS80[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access
IOS202[60] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[38+37] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS249[57] (rev 65535, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS250[56] (rev 65535, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS251[38] (rev 65535, Info: d2x-v10beta52): Trucha Bug, ES Identify, NAND Access
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 09/21/2021.

 

[blackb0x]

As for editing gx loader's XML file, the default was 250, and I additionally tried 224, and 222. If I should try others, please specify which, or at least a range. At no point during testing did the enclosure seem to have any activity.

So you're either not using my updated version of the loader or you only replaced the dol file.

Delete the usbloader_gx folder from sd:/apps/ and then try again with my version of the loader. It might work as long as you're using the correct port.

https://gbatemp.net/posts/8856063

I did take a look at Amazon though and I found one recent review that says that it doesn't work with their Wii. So maybe the manufacturer has released a new revision of the enclosure that uses a different chipset.

 

[XFlak]

You can also try slot 251, 202 & 223. If those don't work, you can try installing d2x with base 58 to an unused slot, like 248, then try that. If that doesn't work, you're unlikely to be able to get this hdd to work and you should try a different one

 

[MaxBox]

So you're either not using my updated version of the loader or you only replaced the dol file.

I started by using the original download found around the web, then I used the modmii installer to generate it. To my knowledge I've always been on the most up-to-date stuff, so if there's an issue there, I suggest people look into it so that no one else is downloading out-of-date software.

I downloaded the updated version and there was no change to behavior, aside from an actual notification popping up notifying me that "no hdd initialized, switching to channel list mode" which I had seen when initially testing a few weeks ago.

I assure you I've been attempting to use the correct port, however with the older HDD, the INCORRECT port was the only one in which it was detected.

At this point, I'm just going to try another enclosure that is reportedly working, so we can at least eliminate hardware from being an issue.

 

[MaxBox]

I got logged out and the forums just allowed me to type my message, then didn't give me a chance to save or sign in after posting. Soooo you get the image cuz I don't want to retype it all.

One other thing is that the "waiting for HDD" in Loader GX appears much later than it did before, to my naked eye it now appears at the very end of the sequence that I posted earlier.

 

[XFlak]

Apologies if this was mentioned already, but what new type of HDD did you get? Size, brand, etc.

 

[blackb0x]

Apologies if this was mentioned already, but what new type of HDD did you get? Size, brand, etc.

It's one that I recommended to him, since I have the same drive hooked up to another Wii and I know that it works well in just about every scenario.

If the HDD from the laptop isn't bad then I think his Wii might have blown fuses or a bad capacitor. So personally I'd suggest trying another donor HDD and then should that also fail maybe it'd be worth trying a USB Y cable or purchasing another Wii from eBay.

This Wii behaves a lot like a Wii U that's not supplying enough power to the HDD. And if the USB ports are faulty then I don't know if a Y cable would work, unless you could try to power it from another source e.g. a laptop or a USB port on your TV

 

[MaxBox]

"If the HDD from the laptop isn't bad then I think his Wii might have blown fuses or a bad capacitor. So personally I'd suggest trying another donor HDD and then should that also fail maybe it'd be worth trying a USB Y cable or purchasing another Wii from eBay."

As in, leave the enclosure, try a new HDD? It's a 160GB Fugetek I think, I mentioned it earlier in the thread. I guess I could purchase a USB Y cable, though it doesn't seem necessary for regular usage. At this point is it pretty definitive that it's not a software issue? I'll reiterate that I can't play regular CD games anymore, the Wii demands a system update. Maybe there's an issue there?

I also don't have the spare funds to go purchasing an entirely different console at this point. The first Bipra drive was "detected" by homebrew in both ports.

 

[blackb0x]

As in, leave the enclosure, try a new HDD?

Yes. If you can get another donor drive from somewhere then that'd be great.

I guess I could purchase a USB Y cable, though it doesn't seem necessary for regular usage.

I don't want to suggest buying more things, but you Wii does behave like a Wii U that isn't supplying enough power to the drive. So it might work as long as you get the correct USB Y cable for your enclosure.

At this point is it pretty definitive that it's not a software issue?

After 3 drives failing to either find your games or play them I think it's safe to say that it's not an issue with the homebrew. Especially now that you're using the same HDD enclosure as me.

I'll reiterate that I can't play regular CD games anymore, the Wii demands a system update. Maybe there's an issue there?

You could always restore your NAND backup and start over. Although maybe @XFlak will have a different suggestion, since you did use ModMii to install various IOS.

 

[MaxBox]

After 3 drives failing to either find your games or play them I think it's safe to say that it's not an issue with the homebrew. Especially now that you're using the same HDD enclosure as me.

But remember, WiiFlow is able to see both the drive and the games within. It just seems to crash upon launching them.