Hacking USB Loader GX wont recognize USB

[Alexander1970]

Hello.

Thank you for your Update.
Great to hear it works for you.

So it seems to be working right now on IOS58 for the Loader, but what confuses me is that I appear to have 1271. I thought 1272 switches to IOS58.

THAT only knows our USBLoader GX Wizard........our always helpful and friendly @Cyan .

 

[Cyan]

huu, I didn't read previous page, I only answer based on that quote:

all version use the "last set" setting.
1272 use IOS58 by default, if you don't have an existing GXGlobal.cfg file

if you do, it uses the config, whether you update or downdate.
if you ever set loader's IOS to 58, it won't be removed by not using 1272.
if you ever set to loader's IOS to 249 and update to 1272, it won't be changed to 58, as the settings exists and user wanted to use 249.

replacing existing settings when changing the revision would be wrong, unless it's a very strickly required fix to be forced into! (like preventing HDD corruption, etc.)

 

[Bwangster12]

huu, I didn't read previous page, I only answer based on that quote:

all version use the "last set" setting.
1272 use IOS58 by default, if you don't have an existing GXGlobal.cfg file

if you do, it uses the config, whether you update or downdate.
if you ever set loader's IOS to 58, it won't be removed by not using 1272.
if you ever set to loader's IOS to 249 and update to 1272, it won't be changed to 58, as the settings exists and user wanted to use 249.

replacing existing settings when changing the revision would be wrong, unless it's a very strickly required fix to be forced into! (like preventing HDD corruption, etc.)

That was a little over my head, lol... but at some pt I did update to 1272 and started noticing issues with my harddrive initializing. I did switch it to IOS 58 and it seemed to work. I kept tinkering cause I wasn't sure and went back to 1271. Now, on 1271, I'm using IOS 58 and its working. Sounds like I'm okay to keep it as is?

 

[Cyan]

keep it with 1271/IOS58 if it works best for you
1271 is better (as 1272 has reported memory and freeze issues)
use IOS58 if HDD init and disc dumping works fine with it.

if possible, using cIOS instead of IOS58 (the same than the game's IOS) boost the game's launch speed as it doesn't need to reload IOS.
also, using cIOS is required if you use any channel launched method (crap/WiiGSC), or priiloader direct booting without AHB access.

 

[Bwangster12]

keep it with 1271/IOS58 if it works best for you
1271 is better (as 1272 has reported memory and freeze issues)
use IOS58 if HDD init and disc dumping works fine with it.

if possible, using cIOS instead of IOS58 (the same than the game's IOS) boost the game's launch speed as it doesn't need to reload IOS.
also, using cIOS is required if you use any channel launched method (crap/WiiGSC), or priiloader direct booting without AHB access.

How do I use cIOS instead of IOS58? Before it was set to IOS249 and I was having issues.

 

[jeannotte]

How do I use cIOS instead of IOS58? Before it was set to IOS249 and I was having issues.

Hello,

put either 249 or 058 in usb loader gx (procedure):

Go to "parameters", then "loader parameters", then "loader IOS", then put 249 or 058.

 

[Bwangster12]

Hello,

put either 249 or 058 in usb loader gx (procedure):

Go to "parameters", then "loader parameters", then "loader IOS", then put 249 or 058.

Right, that's what I did with 58 and its working... but based on comments here that cIOS works better, is 249 cIOS and 58 is not?

 

[jeannotte]

Right, that's what I did with 58 and its working... but based on comments here that cIOS works better, is 249 cIOS and 58 is not?

On my wii usb loader gx is set to 249 and everything is functional.

Then everyone has to see which one works best

 

[Cyan]

if you don't have problems, don't try to fix it !
keep 58, and forget it.

 

[Bwangster12]

Just wanted to circle back on this for those in my situation... not sure if it was tied to updating to 1272 or not, seems like it probably was, but I think I have remedied the issue for now.

I took my external HD to my Windows PC and ran error checking (there was none) and then did the disk optimization. I was reading on Reddit that some were saying that unplugging your HD from your PC without clicking to eject it was causing some issues/errors and putting them in the same situation with their harddrive not initializing. I switched the Loader back to 249 and it seems to be working now.