Hacking Initialize USB Device...

[UltraSUPRA]

Yes, I'm one of those guys with the infamous issue of USB Loader GX crashing at this screen. I've dealt with this before, and normally just turning the Wii off and back on again would fix the issue.

This has not been one of those simpler times.

You see, the external HDD we have has a blue light. Whenever it's detecting a signal, it'll flash purple. Even when the thing froze before, the light would flash purple twice like normal, with the only main difference being the second flash is significantly longer than before.
It doesn't flash anymore. It stays a solid blue the whole way through. I've tried turning off the Wii, turning off the HDD, turning off both at the same time, unplugging the HDD, and switching out the cords, but nothing worked.
And before you tell me to use Syscheck, I did. I used one so old a screenshot could be mistaken for Command Prompt footage with the colors reversed. And guess what happened probably around halfway through?

The system booted to BootMii.

The wierd thing is that we have BootMii as an IOS. The Wii we got already had Boot2v4, which is really freaking stupid. There's no explanation why it would go to an area when its only real function would be to back up/reload our NAND...unless the program was trying to back up or reload it itself. Either that or I'm wasting my time and the drive has been killed off forever.

 

[Cyan]

And before you tell me to use Syscheck, I did. I used one so old

why using a "so old" version, instead of the correct version?

And before you tell me to use Syscheck, I did.

the purpose of syscheck is not to "use it", or just "try to" and give up if it doesn't work, but to post the result here, so people can see what you have in your console.
If the program crashed (command prompt reversed? you mean white text numbers on black screen right? it's not reversed, command prompt are usually white on black), and you know you used an outdated version, why did you keep using a non working version instead of trying a not "so old" one? It's like you are asking for problems.
here is the proper version of syscheck, with a guide : https://gbatemp.net/threads/300279/
post the result here.


I don't know why you got bootmii launched, the only tools launching bootmii are boot2, hbc, nswtich.
a crash report screen reboots the console after 20 seconds, so if you have bootmii in boot2, that's the reason it launched, nothing strange here.


you need 3 things to use USBLoaders :
- cIOS d2x v8 final, or v10 r52, base 57 in slot 249
- USBLoaderGX 1268 (or newer) (or newest release of wiiflow)
- plug HDD in bottom port.

then
- reset all settings in the loader
- go to settings > loader's settings > Loader's IOS : 58
reboot.

 

[UltraSUPRA]

why using a "so old" version, instead of the correct version?

1.6.1, I think. All I know is that it was the latest "official" version, as in the last one before HacksDen made their own version.

the purpose of syscheck is not to "use it", or just "try to" and give up if it doesn't work, but to post the result here, so people can see what you have in your console.

mmkay

(command prompt reversed? you mean white text numbers on black screen right? it's not reversed, command prompt are usually white on black)

No, it was actually black text on a white screen.

If the program crashed, and you know you used an outdated version, why did you keep using a non working version instead of trying a not "so old" one? It's like you are asking for problems.

Same reason I use WM instead of YAWMM, I prefer to use the originals.

here is the proper version of syscheck, with a guide : https://gbatemp.net/threads/300279/
post the result here.

I'll save that for the end of the post.

I don't know why you got bootmii launched, the only tools launching bootmii are boot2, hbc, nswtich.
a crash report screen reboots the console after 20 seconds, so if you have bootmii in boot2, that's the reason it launched, nothing strange here.

The Wii we got already had Boot2v4, which is really freaking stupid.

you need 3 things to use USBLoaders :
- cIOS d2x v8 final, or v10 r52, base 57 in slot 249
- USBLoaderGX 1268 (or newer) (or newest release of wiiflow)
- plug HDD in bottom port.

then
- reset all settings in the loader
- go to settings > loader's settings > Loader's IOS : 58
reboot.

I did all that, and now it recognizes the HDD but completely ignores initialization.

Now for that 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.0 running on IOS61

Hollywood v0x21
Console ID: 94753807
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v4
Found 190 titles.
Found 47 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): Trucha Bug, ES Identify, NAND Access
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-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 65535, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 12/03/2018.

 

[Cyan]

Thank you for your syscheck log.
Almost everything is fine :
- All your IOS are unpatched (good),
- You have v10 r52 in slot249/250 (semi good). don't use r53, this is a beta with HDD initialization issues.
- You have base 56 in slot 249 (default slot), which is less compatible than base 57 (in slot 250). either edit your loader's setting to use slot250 instead of 249, or swap the base (57 in 249 is all you need for best game compatibility, you don't really need base56 at all but you can install it in slot 250 if you really want)
- HBC has a problem, see below.

Homebrew Channel 1.1.0 running on IOS61

This is probably your problem.
the console has probably been softmoded in reverse : hbc first, IOS update second, no reinstall of HBC after IOS update.
Your Homebrew channel has been installed before IOS58. If you are missing IOS58 it's using IOS61 (even if you install IOS58 after HBC install it will not use it unless you reinstall HBC).
IOS58 is responsible for the HDD USB2.0 support, so if you use IOS61 it's not initialized properly.

To fix that : reinstall HBC
put the hackmii installer in sd:/apps/hackmii_installer/ folder and launch it from HBC (no need to do a game or banner or web exploit).
Now that you have IOS58 (listed in your syscheck), it will be selected by HBC's installer and used as default IOS for HBC with properr USB2.0 init.

The Wii we got already had Boot2v4, which is really freaking stupid.

Why are you saying that?
Do you think the boot2 version is responsible from preventing you to install bootmii in boot2 ?
boot2 v4 is working fine with bootmii@boot2, the one responsible for bootmii installed into the boot2 is the vulnerability in boot1 (which is NOT patchable).
All consoles released after 2008 have their boot1 vulnerability fixed and therefore can't install bootmii into boot2, whether you have boot2 v1 or v4 has no incidence, all 4 version are working with bootmii if you had your console manufactured BEFORE 2008.

Your wii is : 07.14.2008
likely to not be able to install bootmii into boot2, you can only install bootmii as IOS.




It's possible you'll still have Init issue, nothing is 100% certain until you test.
If you still have issues, let me know.

 

[UltraSUPRA]

This is probably your problem.
the console has probably been softmoded in reverse : hbc first, IOS update second, no reinstall of HBC after IOS update.
Your Homebrew channel has been installed before IOS58. If you are missing IOS58 it's using IOS61 (even if you install IOS58 after HBC install it will not use it unless you reinstall HBC).
IOS58 is responsible for the HDD USB2.0 support, so if you use IOS61 it's not initialized properly.

To fix that : reinstall HBC
put the hackmii installer in sd:/apps/hackmii_installer/ folder and launch it from HBC (no need to do a game or banner or web exploit).
Now that you have IOS58 (listed in your syscheck), it will be selected by HBC's installer and used as default IOS for HBC with properr USB2.0 init.

Still got problems. It still wouldn't initialize.
I decided to switch USBLGX back to slot 249, and it freezes once again. Like I said earlier, the HDD we have has a blue light that turns purple whenever it gets read, and now it's staying a solid blue.

 

[Cyan]

ok, so you reinstalled HBC, now it's saying IOS58 in the menu ? (press home menu in HBC to verify).

slot249 or 250 is not different for HDD compatibility, but for game compatibility (some game will work only with base57), so as long as you don't want to play such a game you can use slot249.


If it's still not initializing, is it only a problem with USBLoaderGX or with all other homebrew ?
did you try wiiflow, WiiMC, Wiixplorer, or any emulator? just to know if it's only a loader issue, or a general problem.

if it doesn't work with any homebrew, do you have a way to test your drive on another console?

 

[UltraSUPRA]

ok, so you reinstalled HBC, now it's saying IOS58 in the menu ? (press home menu in HBC to verify).

Yup.

slot249 or 250 is not different for HDD compatibility, but for game compatibility (some game will work only with base57), so as long as you don't want to play such a game you can use slot249.

mmkay

If it's still not initializing, is it only a problem with USBLoaderGX or with all other homebrew ?
did you try wiiflow, WiiMC, Wiixplorer, or any emulator? just to know if it's only a loader issue, or a general problem.

Snes9xGX can't even so much as detect it.

if it doesn't work with any homebrew, do you have a way to test your drive on another console?

If only. My Wii U is on the other side of the shelf and the systems are wired from behind it.

 

[Cyan]

thanks for the reply.
so, to me it seems the problem is either the device itself, or the USB Ports, because no homebrew can detect it.

as I know USBLoaderGX has some HDD detection issue, I didn't thought about other homebrew and only focused on that loader's common fixes.
but seeing other homebrew also have issues with that drive, we will need to verify if the problem is the drive or the console.

Do you have another HDD? or even a flash drive (they are very bad with the Wii/WiiU, so only test that in last resort)
check if any other device is working, HDD, flashdrive, even an SD card USB adapter or any phone or device which can be mounted as UMS (USB Mass Storage)

 

[UltraSUPRA]

thanks for the reply.
so, to me it seems the problem is either the device itself, or the USB Ports, because no homebrew can detect it.

This does not look good.

as I know USBLoaderGX has some HDD detection issue, I didn't thought about other homebrew and only focused on that loader's common fixes.
but seeing other homebrew also have issues with that drive, we will need to verify if the problem is the drive or the console.

mmkay

Do you have another HDD? or even a flash drive (they are very bad with the Wii/WiiU, so only test that in last resort)
check if any other device is working, HDD, flashdrive, even an SD card USB adapter or any phone or device which can be mounted as UMS (USB Mass Storage)

I never thought I'd see the day when I had to pull out the 16GB flashdrive I use for my Wii U and stick it into my father's Wii.

 

[UltraSUPRA]

Welp. I've gone and done it. I plugged it into the right spot (after reformatting it -- it wasn't that bad since I have Wii U USB Helper), turned on USB Loader GX (I tried it twice), and...it failed. Does this mean the problem is the USB ports? If so, can I fix it without getting a brand new Wii? I don't want to replace my dad's 2008 birthday present just so I can play Super Mario Galaxy.

 

[Illuminaticy]

Welp. I've gone and done it. I plugged it into the right spot (after reformatting it -- it wasn't that bad since I have Wii U USB Helper), turned on USB Loader GX (I tried it twice), and...it failed. Does this mean the problem is the USB ports? If so, can I fix it without getting a brand new Wii? I don't want to replace my dad's 2008 birthday present just so I can play Super Mario Galaxy.

Since you were just testing to see if the USB ports work, how did it fail? Was it still stuck at initialize USB? Did it detect the USB at all?

Try putting a homebrew app in the "apps" folder on the USB, then switch homebrew channel to USB view (press 1 or 2 at homebrew channel, can't remember which) If it's not detected that way, that narrows it down a bit more.

 

[UltraSUPRA]

Since you were just testing to see if the USB ports work, how did it fail? Was it still stuck at initialize USB? Did it detect the USB at all?

It got stuck.

Try putting a homebrew app in the "apps" folder on the USB, then switch homebrew channel to USB view (press 1 or 2 at homebrew channel, can't remember which) If it's not detected that way, that narrows it down a bit more.

Okay. I'll try Wiimmfi.

 

[UltraSUPRA]

I tried Wiimmfi and it worked. Does this mean it's a problem with the HDD?