Hacking USB Loader GX: Stuck on Initializing USB device

[Cyan]

Let the loader edit the meta.xml automatically for you to be sure it's the correct format.
Also, editing only the meta is not always enough as it will edit only the launch IOS, not the loader's IOS.
Editing the meta is also not enough if you don't remove the commented lines.

go into USBLoaderGX settings > loader settings > Loader's IOS : 58
it should edit the meta automatically
reboot to see if it works.

 

[geheim]

Thanks @Cyan I did as you suggested, but it still freezes at Initializing USB Devices... The hdd worked perfectly with my old Wii, but now on vWii it always fails to initialize with USB Loader GX. Nintendont however can succesfully initialize it.

Is there something else I could try??

Thanks for your help!

 

[Cyan]

Do you have a Y-Cable ? or is it externally powered?
on vwii, you need Y-cable, but maybe you have it if it already work with nitendont.

Sorry, except trying IOS58 I don't have more fixes in mind.

 

[geheim]

Yes, I use a Y-cable. Hmm, I really don't know why it always freezes...
Could it be another problem with my cIOS? I followed the definitive vWii Hacking Guide in the Wii U section.

 

[Cyan]

you installed d2x r53 ?
I don't think it can help, but you could always try r52.

Though, if IOS58 doesn't help, then the hacking guide has nothing to do with it as it's an official Nintendo's IOS.


Or maybe the meta.xml is not properly edited and the loader is not using IOS58 ? did you check in the credit page to see if it's running on IOS58 ?
you can try to reinstall the loader on SD card too (or maybe on USB, to force HBC to init the drive instead of the loader)

 

[geheim]

@Cyan, I installed d2x r52 from the beginning.
I checked the credits page and on there in the upper right corner it shows IOS58.

BUT I noticed that while USB Loader GX is loading the screen always shows "Using IOS249"!!
After "Using IOS249" and manually connecting the HDD it continues loading and afterwars it says "Reloading IOS" and "Patching IOS58", which is the first time I see IOS58 written on screen.

Therefore I think it is not really using IOS58 to initialize the HDD. What could be wrong here?? IOS58 should work with my HDD (a WD Elements 2TB) because Nintendont also uses IOS58 if I'm not mistaken and with Nintendont there are no problems...

I tried changing the loader IOS to 251. Doing so changes nothing however. It still says "Using IOS249" and freezes.

Do you have any idea why it keeps using IOS249?? Perhaps I really should try to delete USB Loader GX and reinstall it on my SD while also deleting all config files.

Thanks!!

 

[Cyan]

if you see 249 when loading, it means the meta is not good (either wrong info, or badly formed text or tags).
the boot process is like this :

HBC or forwarder using IOS58> USBGX > read meta.xml arguments, if any > read meta.xml ios value or fallback to 249 > reload to selected IOS > mount devices (SD & USB) > read the user's GXglobal config file > read the Loader's IOS > reload to that IOS > load loader's menu interface.

So, if the meta fails to tell the loader to load 58, you can see that the loader will later reload to 58 if you have that slot set in "loader's IOS" setting.
Your issue is that it's not properly using IOS set in meta to mount the devices and fallback to 249.


Download a fresh meta.xml from here :
https://sourceforge.net/p/usbloadergx/code/HEAD/tree/trunk/HBC/meta.xml?format=raw

edit in a text editor and delete the full lines :
<!-- // remove this line to enable arguments
and
// remove this line to enable arguments -->

which will allows you to use arguments.
replace 250 to 58
save the file and put it in your usbloader_gx folder.

 

[geheim]

@Cyan Now it is working if I start USB Loader GX through HBC! Thats good.
However if I use the forwarder channel it still uses IOS249... Is there a way to boot the loader with IOS58 using the vWii forwarder channel??

 

[Cyan]

You probably installed an old vWii forwarder.
Asper did the Forwarder Wii->vWii conversion, but he used forwarder v2, instead of forwarder v5.1 (which reads the meta) and tagged it as "v5.1". Lot of users installed that version.
I converted the real v5.1 later and released it as "v5.1_fix".

get the new forwarder and install (replace, just install and overwrite the old one) with a wad manager:
https://sourceforge.net/projects/usbloadergx/files/Releases/Forwarders/

 

[geheim]

Cyan you are my hero for today
I installed the newest forwarder and now it works!!
Thanks so much for your help!!

 

[eriol33]

hi, I have a similar problem. I am also freezing on initialize USB device. usb loader gx somehow uses IOS247 (rev 21006). I can rectify this by temporarily dismount my hard drive and plugging it back when usb loader gx prompts to insert usb device. but it's not an ideal experience. can someone help me?

 

[Cyan]

if you see "21006" it means you have d2x v6.
it could be your issue, as v7 and v8 added better HDD compatibility. Also, with v6 some games will not work correctly.

maybe updating will not fix your need to unplug/replug, as it seems there's an issue with some WD Element drives not remounting correctly. but first try to install d2x v8, base56 or 57. (57 has better game compatibility, but lot of users prefer installing 56 due to VERY slightly faster loading time over game compatibility)

 

[eriol33]

if you see "21006" it means you have d2x v6.
it could be your issue, as v7 and v8 added better HDD compatibility. Also, with v6 some games will not work correctly.

maybe updating will not fix your need to unplug/replug, as it seems there's an issue with some WD Element drives not remounting correctly. but first try to install d2x v8, base56 or 57. (57 has better game compatibility, but lot of users prefer installing 56 due to VERY slightly faster loading time over game compatibility)

Hi Cyan thank you for the reply. I am still very noob over this ios things (I barely understand differences between one and another, like why you install this certain of software to that IOS but not another?)

so this is what I will do?

1. install d2x v8 final from this site: https://code.google.com/archive/p/d2x-cios/downloads
2. I choose the IOS 247 for the installation
3. and install this one? select cios slot: 247

 

[Cyan]

yes, that's good.
doing that will overwrite your v6 with v8 final.
it will be based on the original IOS 57 (from nintendo) with added features and patches for USBLoaders.
IOS57 is the most compatible IOS for all games.

After it's installed, your usbloader will still use the slot 247, but this time it will be a new "driver version" located there.


Usually, softmod guides let the users install the base57 in slot250 instead of 247. it's easier to help users when everyone has a "common" setup.
but as long as you know your own setup that's fine.
maybe you could install it in slot249 instead, as it's the default slot used by USBLoaders. It will prevent you from having to change the loader's settings to use the correct IOS version.

 

[eriol33]

I have installed on both IOS 247 and IOS 249, but it still freezes

did I choose the right IOS for installation? (I use IOS 247)

here's my system check result.

Spoiler

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
IOS236[36] (rev 65535, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS247[56] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS248[56] (rev 21006, Info: d2x-v6): Trucha Bug, NAND Access, USB 2.0
IOS249[57] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 08/08/2016.

EDIT:

okay this is weird, I think the problem is on my harddisk (NTFS) because most of my wii games are on ISO format, not WBFS.

I tested a 8 gb usb flash drive (fat 32) and put a WBFS game on it, and the usb is detected instantly. should I convert all my ISO files into WBFS?

EDIT 2:
converted my ISO files into WBFS with my hdd, still frozen

 

[Cyan]

maybe the issue is your drive and not the console or the settings.
seeing your flash drive is working I think it's a hdd detection issue.
You don't have another hdd to use or even just try to be sure it's an hdd issue?

what is your hdd model ? is it listed in the hdd compatibility list?
http://wiki.gbatemp.net/wiki/USB_Devices_Compatibility_List

 

[anthiflex]

Getting the same issue here, USB Loader GX gets stuck on "Initialize USB device", which is weird since it used to work before.
Ran a syscheck, here are the results:

Spoiler

sysCheck v2.1.0b19 par Double_A et R2-D2199, Nano
...tourne sous l'IOS58 (rev 6176).

Region: PAL
Menu Systeme 4.3E (v514)

Date de disque: 2007.02.13

HomebrewFilter ist nicht installiert
Hollywood v0x11
Identifiant de la console: 56422627
Boot2 v4
78 titres trouves.
48 IOS trouves sur cette console. 12 sont des stubs.

IOS4 (rev 65280): Stub
IOS9 (rev 1034): Pas de patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): Pas de patches
IOS13 (rev 1032): Pas de patches
IOS14 (rev 1032): Pas de patches
IOS15 (rev 1032): Pas de patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): Pas de patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): Pas de patches
IOS22 (rev 1294): Pas de patches
IOS28 (rev 1807): Pas de patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): Pas de patches
IOS33 (rev 3608): Pas de patches
IOS34 (rev 3608): Pas de patches
IOS35 (rev 3608): Pas de patches
IOS36 (rev 3608): Trucha Bug, ES Identify, Acces NAND
IOS37 (rev 5663): Pas de patches
IOS38 (rev 4124): Pas de patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): Pas de patches
IOS43 (rev 3607): Pas de patches
IOS45 (rev 3607): Pas de patches
IOS46 (rev 3607): Pas de patches
IOS48 (rev 4124): Pas de patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): Pas de patches
IOS55 (rev 5663): Pas de patches
IOS56 (rev 5662): Pas de patches
IOS57 (rev 5919): Pas de patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): Pas de patches
IOS62 (rev 6430): Pas de patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): Pas de patches
IOS202[60] (rev 65535, Info: Hermes-v55.1): Trucha Bug, Acces NAND, USB 2.0
IOS222[38] (rev 65535, Info: Hermes-v55.1): Trucha Bug, ES Identify, Acces NAND, USB 2.0
IOS223[37] (rev 65535, Info: Hermes-v55.1): Trucha Bug, Acces NAND, USB 2.0
IOS224[57] (rev 65535, Info: Hermes-v55.1): Trucha Bug, Acces NAND, USB 2.0
IOS249[37] (rev 21010, Info: d2x-v10beta52): Trucha Bug, Acces NAND, USB 2.0
IOS250[57] (rev 65535, Info: d2x-v10beta52): Trucha Bug, Acces NAND, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10 (DIOS MIOS 2.6.1+)

Rapport genere le 2016/08/09. [/spoilers]

Think it could be my HDD itself?

 

[eriol33]

I followed Cyan's tips. Luckily I have three HDD. The one that don't work are USB 3 type and I think the usb 2.0 HDD works just fine ( I am testing it at the moment)

Can it be that usb 3.0 HDD cause the problem?

Edit:

My Samsung 500 GB HDD is detected just fine, but it's crashed when playing the second level of new super bros Wii (when Mario enters the upper pipe on the second level just after the moving platform where you can control by tilting Wii mote). I will try to reproduce it.

Bad news: Nintendont crashed when using this HDD

 

[Cyan]

IOS249[37] (rev 21010, Info: d2x-v10beta52): Trucha Bug, Acces NAND, USB 2.0
IOS250[57] (rev 65535, Info: d2x-v10beta52): Trucha Bug, Acces NAND, USB 2.0

Your slot 249 is base 37 instead of base56.
it could be related to your issue, .. or not. but lot of games will require base56 or 57 (not 37).

Can it be that usb 3.0 HDD cause the problem?

yes, it's possible.
Other USB3.0 has been reported having issues (WD element)

If your hdd make games crashing, it's possible that it's the sleep timer issue.
some drives are forcing a shutdown (even if cIOS and nintendont should prevent it) after few seconds or minutes of inactivity.
there's no wake up command send by the game (the CD or DVD is not supposed to go to sleep).
Usually, the manufacturer is providing tools to edit the sleep timer, or disable it completely.

 

[eriol33]

a little update trying the usb loader GX with my samsung 500 gb hdd

- I tried to play super mario bros wii, last time I got black screen on a certain level, this time it worked just fine.
- trying super mario galaxy, and it gives me black screen from the start.

still crashes nintendont

now I am copying all files from my toshibago (1 TB) to seagate (1 TB) and will format the toshibaGo into fat 32