Hacking USB Loader GX

  • Thread starter Thread starter blackb0x
  • Start date Start date
  • Views Views 8,066,558
  • Replies Replies 30,226
  • Likes Likes 74
1234-mod in my sig is stable for you?
it's very stable here and I can use the DS3 just fine along with all other controllers
I tested it using DS3 2 wiimotes and 1 GC controller and everything worked as expected
the banners are showing just fine and game launching works too.
Are you sure about DS3 thing, can you please redownload and test it again


I get the same text corruption from your 1234mod as I did with official 1235 build. In the past week I've had my 2tb drive get corrupted twice using 1235 having to format and transfer files back over. So as soon as I saw the corrupted text on your mod I quickly reverted back to official 1233, which seems to be stable for me.


On a seperate note, I've noticed a bug (1233 at least) when launching a GC game with nintendont with 4 GC controls attached and native controls disabled nintendont will freeze on 'init di' whereas with 1-3 controls, games will load just fine. You can even launch with 3 and connect a 4th after the game is running and it will function fine. Enabling native controls will fix this but disables the shutdown/return combo. Launching nintendont through homebrew channel does not cause this issue, so it appears to be a usbloader gx bug.
 
I'm using an NTSC USA Mios Wii here, using the GC bios on Nintendont, when I lunch a PAL game with Nintendont I get a blue screen with only the audio, if I run the same game strait from the Nintendont loader I get it running just fine, if I remove the PAL IPL then the games run fine, just wanted to report this bug.

I hope a future update will add an option per game to enable and disable the GC bios, this will more than likely fix many games that have issues with the bios files, wither Nintendont will add an option or not is beyond me but I think USBLGX should regardless, maybe make it delete (move/rename) the IPL file temporarily then put it back (move it back/rename it) for the other games, thanks.
 
I get the same text corruption from your 1234mod as I did with official 1235 build. In the past week I've had my 2tb drive get corrupted twice using 1235 having to format and transfer files back over. So as soon as I saw the corrupted text on your mod I quickly reverted back to official 1233, which seems to be stable for me.


On a seperate note, I've noticed a bug (1233 at least) when launching a GC game with nintendont with 4 GC controls attached and native controls disabled nintendont will freeze on 'init di' whereas with 1-3 controls, games will load just fine. You can even launch with 3 and connect a 4th after the game is running and it will function fine. Enabling native controls will fix this but disables the shutdown/return combo. Launching nintendont through homebrew channel does not cause this issue, so it appears to be a usbloader gx bug.
what do you mean by text corruption? screenie?
 
what do you mean by text corruption? screenie?
In the HDD info display at the bottom it will replace numbers with letters or other characters (same numbers get same new character.. Example, all 0's turn to r's) as well as the total number of games changes from load to load. IMG_20150117_020345.jpg
 
AbdallahTerro you broke the reset button and hold up to scroll in your 1234 mod, that's all I can see wrong
In the HDD info display at the bottom it will replace numbers with letters or other characters (same numbers get same new character.. Example, all 0's turn to r's) as well as the total number of games changes from load to load. View attachment 14471
can you please test this mod: https://dl.dropboxusercontent.com/u/101209384/ds3/usbloader-gui-read-only-1234mod-v2.rar
 
Thanks for testing, looks like GX is reaching it's memory limits...
Hopefully Cyan can figure out the problem via debugging
Could this be why I been having some random issues with USBLGX recently like if I scroll through game channels using the L and R button quickly? I thought it was my HDD but I backed it up, formatted it, then reinstalled the games, the issue seems to still occur randomly, it doesn't happen with the other loaders and homebrews, I noticed it after the latest update.
 
Could this be why I been having some random issues with USBLGX recently like if I scroll through game channels using the L and R button quickly? I thought it was my HDD but I backed it up, formatted it, then reinstalled the games, the issue seems to still occur randomly, it doesn't happen with the other loaders and homebrews, I noticed it after the latest update.

It definitely has something to do with it- when I was doing that wierd stuff was happening like banners appearing in wrong places- try setting the grid scroll speed to something like 38px/f in the banner settings- and using r1235test3 until Cyan figures it out.
 
  • Like
Reactions: sonictopfan
I tested someone's 1234 mod (abdallah I think) and it had corruption in the homebrew browser too : displaying wrong colors and part of graphics which shouldn't be there.

I'll do more test today.
I just don't know where to start. I'll probably release a version which fix nintendont detection without additional controllers and push it in internal update so at least all users can update it for nintendont.
Then I'll do more test from there.

I'm now reading nintendont thread to catch all missed posts for a week... 50pages, damn



I noticed something else:
if PS3 controller is powered, reset the loader (home>reset), at reboot the controller has rumble going crazy while no rumble signal is sent.
maybe the controller is not properly de-init before shutting down USB or reloading IOS and creates memory leaks.
 
It definitely has something to do with it- when I was doing that wierd stuff was happening like banners appearing in wrong places- try setting the grid scroll speed to something like 38px/f in the banner settings- and using r1235test3 until Cyan figures it out.
Thanks, I'll try that!

Cyan good luck and thank you for the quick response!
 
I tested someone's 1234 mod (abdallah I think) and it had corruption in the homebrew browser too : displaying wrong colors and part of graphics which shouldn't be there.

I'll do more test today.
I just don't know where to start. I'll probably release a version which fix nintendont detection without additional controllers and push it in internal update so at least all users can update it for nintendont.
Then I'll do more test from there.

I'm now reading nintendont thread to catch all missed posts for a week... 50pages, damn



I noticed something else:
if PS3 controller is powered, reset the loader (home>reset), at reboot the controller has rumble going crazy while no rumble signal is sent.
maybe the controller is not properly de-init before shutting down USB or reloading IOS and creates memory leaks.

Why you don't start from r1235_v3 as base? No one has reported problems with this rev so far, going back again seems like much extra work.
 
I would prefer v6 (only PS3 removed, but keeping the aspect ratio fixer).

I made a new version:
v07 : no changes, just make sure to use clean libogc1.8.12
v08 : v07+ removed PS3's USB init/deinit code, letting the loader manage USB ports.
v09 : placed PS3 library inside loader's sources instead of using linked library.
v10 : v07+ removed PS3 controller support + removed Aspect ratio switcher in features menu
v11 : v10+WiiU aspect ratio switcher


boot_r1235_vxx
01 : recompile exactly the same as 1235; but make sure to compile libsicksaxis and libwupc with PPCRev26.
02 : 01 + removed auto aspect fixer and aspect fixer feature.
03 : 02 + removed PS3 support
04 : 03 + use clean libogc1.8.12
05 : 04 + removed libwupc support
06 : 01 + removed PS3 + use official libogc 1.8.12.
07 : 01 + official libogc 1.8.12
08 : 07 + remove USB init/deinit from PS3 wrapper

Could you test v8?
https://www.mediafire.com/folder/t2x95zd9rz3rc/USBLoaderGX
I don't have hdd size text issue. my game order seems fine. I didn't get invisible banners but didn't made lot of tests.

Something I noticed:
PS3 is correctly initialized and ready to use only if USB HDD is connected.

- disconnect HDDs
- connect PS3 controller to port1
- launch USBGX
- once loader is on main screen, you can't press PS button to synch the pad. You need to disconnect/reconnect the usb cable to PS3 controller, now you can press PS button.

If you have USB HDD connected, you don't need to disconnect usb before pressing PS button.
 
just tell me if the hdd size's text is corrupted (or any other text, it can happen anywhere) and if you see any instability or issues with game listing.
If I had those issues myself, it would be easier and faster to test.
 
Report r1235_v8

-upon first boot it doesn't show free space, but no corrupted text of any kind.
-controllers working fine (wiimote/cc/wupc).
-second try, it showed free space, but it stack dump on me after some page scrolls, it didn't back to Wiimenu after 20 seconds, have to plug out the power cable.
-third try, still doesn't show free space, go to settings, then back to channels menu it shows free space, seems to be everything in order.
-fourth try, shows free space, but stack dump a few seconds later.
 
  • Like
Reactions: Cyan
I'll fix it, is reset broken with all kinds of controllers?
also can you go down in menus with d-pads or wiimotes aiming?

the physical Reset button is not working
Scrolling down by holding down on the CC dpad works but to go up you have to press up on the d-pad for each item
 
I'm starting to think that the issue is not PS3 related but an old memory leak issue.
It's only happening now because PS3 support is using more memory and overlaping existing memory area.

OriginalHamster
Maybe I could find the real issue with your code dump.
But I didn't keep the .elf file needed to debug, so I'll make a new one.


Could you test v10 please?
This version should work fine (no PS3 support).
I'll release it as 1237 if everything works fine.
 
I'm starting to think that the issue is not PS3 related but an old memory leak issue.
It's only happening now because PS3 support is using more memory and overlaping existing memory area.

Maybe I could find the real issue with your code dump.
But I didn't keep the .elf file needed to debug, so I'll make a new one.


Could you test v10 please?
This version should work fine (no PS3 support).
I'll release it as 1237 if everything works fine.


I'll give v10 a test, do you have a compiled link?
 

Site & Scene News

Popular threads in this forum