Hacking USB Loader GX

  • Thread starter Thread starter blackb0x
  • Start date Start date
  • Views Views 8,065,725
  • Replies Replies 30,226
  • Likes Likes 74
yes, that's the same file from the zip and from the internal/computer installer.
there's no r1235 dol (unless someone compile it now, it will be r1235 but without any changes, r1235 is only released file upload to svn)

Check this out. This is EVERYTHING I have on the drive right now. And you can see the used space as well.
There's something obviously wrong in there...

*EDIT* Something I just noticed as well. The name of the drive USED to be WII. And now, as you can see it's "Local Disk".
It would APPEAR to have been formatted but how come the files are still occupying the space?
 

Attachments

  • 2.jpg
    2.jpg
    14.8 KB · Views: 206
  • 1.jpg
    1.jpg
    4.4 KB · Views: 191
if you put the hdd on wii and use wiixplorer, it's the same result?

users with hdd size and strange settings behavior, could you try to revert back to 1232-1233 and tell me if it fix it?
also, does your setting file correctly set or is it messed up with random settings?

For the moment, please don't use r1234-1235


edit:
I don't know how it could have been formated.
The only format function inside the loader is a WBFS partition formater, not a FAT32 formater.
It would mean that it actually formated it silently without crashing, and selecting correct settings (FAT32, cluster size, etc.) due to a memory bug issue?
I find it very unlikely, but I really don't understand what happened, sorry.

There's also no partition table editor (except WBFS formater), so the loader couldn't change the partition size, location, name, etc. without formating it fully to wbfs.


Edit 2 :
It's hard to find what's wrong when I don't have these issues myself :(
when I tested my builds before releasing it, everything was fine.
I'll check if the svn uploaded file is correct and not corrupted....

nope, checksum matches with my own build. svn file is correctly uploaded.
 
if you put the hdd on wii and use wiixplorer, it's the same result?

users with hdd size and strange settings behavior, could you try to revert back to 1232-1233 and tell me if it fix it?
also, does your setting file correctly set or is it messed up with random settings?

For the moment, please don't use r1234-1235


edit:
I don't know how it could have been formated.
The only format function inside the loader is a WBFS partition formater, not a FAT32 formater.
It would mean that it actually formated it silently without crashing, and selecting correct settings (FAT32, cluster size, etc.) due to a memory bug issue?
I find it very unlikely, but I really don't understand what happened, sorry.

Well, I haven't tried wiixplorer yet. But recuva (recovering software) shows me this after running a deep scan: (attached image)
Which would indicate corruption.
Thing is, how did it happen? There was no error or nothing. Everything just "disappeared" after trying to install the wad...
 

Attachments

  • Untitled.jpg
    Untitled.jpg
    76.6 KB · Views: 182
Sorry, I think there's no way to recover these files.
Usually, you see these filenames on your drive. it's the first time I don't see at least one corrupted name.

I don't know what corrupted the drive, it could be an issue with the FatLib (if there's a memory issue with my compiled version), or just your HDD which didn't write the content correctly or completed it correctly before you shutdown/power off.
But seeing the recent reports about weird memory/settings issues, there's a chance it's a fatlib issue and I'm really sorry :(

I just don't know how to fix it or prevent it as I don't have the issue myself.
I'll try to disable features one by one and post builds here.
If someone can report if it fix the recent issue that would be great help.

I'll start by disabling WiiU Auto-asper fixer.
 
Sorry, I think there's no way to recover these files.
Usually, you see these filenames on your drive. it's the first time I don't see at least one corrupted name.

I don't know what corrupted the drive, it could be an issue with the FatLib (if there's a memory issue with my compiled version), or just your HDD which didn't write the content correctly or completed it correctly before you shutdown/power off.
But seeing the recent reports about weird memory/settings issues, there's a chance it's a fatlib issue and I'm really sorry :(

I just don't know how to fix it or prevent it as I don't have the issue myself.
I'll try to disable features one by one and post builds here.
If someone can report if it fix the recent issue that would be great help.

I'll start by disabling WiiU Auto-asper fixer.

F************KKKKKKKKK MEEEEEEE!!!!... :(
Guess I'll start from scratch then... :(
I think the worst part is not even the wii games but the roms I've collected and categorized over time.... Custom music, themes and whatnot... damnit.
I'll hold on to the corrupted drive for a day or so. Just in case anyone gets the same issue and is somehow able to resolve it :(
 
I've just blocked internal/computer updater to use 1235 and redirect to 1234 instead.

There's probably a way to recover your files, the data is not corrupted, only the partition table.
But I don't know any program to copy files one by one (it won't have correct names so it's hard to find which file is what)

For games it will be easy (hexedit and you will see the GameID in the 4 first bytes), or place files in folder and use WBackupManager to analyze the file.
For roms, using ROM renamers etc. (that will be hard and long to do)

External HDD for use on console should not be your main storage HDD.
use a reserved one for console and keep all your files on another one.


Ok, so I will make some test build:
sorry to pass by the forum but I don't have other beta testers elsewhere.
https://www.mediafire.com/folder/t2x95zd9rz3rc/USBLoaderGX
there's a beta test folder, I'll upload them step by step.
please test them in numbering order and report if you see a fix.


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 <--- My own test : banner preview issue still present on vWii + SD only + 1 gameCube on SD card + use default banner.
04 : 03 + use clean libogc1.8.12 <--- My own test : banner preview issue still present on vWii + SD only + 1 gameCube on SD card + use default banner.
05 : 04 + removed libwupc support
 
users with hdd size and strange settings behavior, could you try to revert back to 1232-1233 and tell me if it fix it?
Back to r1233 (airline WUPC mod) it display free space correctly, the channels banners now read title name from the ISO itself, in correct order.
I'm on Wii U btw, maybe the HDD problems isolated to that system only?
 
is my official 1233 fine?
just want to be sure my devkit is fine.
Yes, it loads banners correctly, shows free space.


It has the same problems as Cyan's r1235-36, in my first try it code dump when scrolling through channels, in my second try it booted fine, but it didn't show free space, in my third try it didn't show the free space, it did "hide" some games randomly, it got fixed when I went to settings then channels got refreshed. Overall was pretty inestable.

It must be Sixaxis thing what is causing this, airline build worked fine with WUPC, and it didn't have the Sixaxis library included.
 
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 <--- My own test : banner preview issue still present on vWii + SD only + 1 gameCube on SD card + use default banner.
04 : 03 + use clean libogc1.8.12 <--- My own test : banner preview issue still present on vWii + SD only + 1 gameCube on SD card + use default banner.
05 : 04 + removed libwupc support

Working great on my end, shows correct free space, channels banner correctly displayed and placed :)
Wii U Pro Controller and Wii Classic Controller both works flawlessly, I see you manage to make the boxart preview compatible with WUPC nice.
Just for the sake of being nitpicking, R/ZR and L/ZL on both WUPC and WiiCC doesn't scroll pages, only d-pad is enabled for that task.

P.D.: this release seems inestable though, when testing and stressing the app to show boxart previews, download cover menu, back to settings, etc... it's prolly to get a code dump. It must got short of memory or something... Next will test v03, if the lack of sixaxis support helps to slow down the workload.
 
so, full 1235 is fixed with just a recompile? that's nice :)
but I wonder what was the issue. Maybe mixing libraries compiled with different PPC revisions?
but you said it's still instable, I'll wait for your other test without PS3 support then.

My LibOGC I used for few months was 1.8.12 with libz and libfat added (don't remember which homebrew used them, maybe nintendont?). USBLoaderGX doesn't use that libfat library, it's using its own "libfatcustom" from the sources/libs/ folder so it's not what caused the HDD issue.


Yes, L/R doesn't work in all menus, I couldn't fix it !
I don't know why when I add Wupc L/R it broke all L/R from all controllers :(
I tried to add WiiUpro in all menus, the only place I couldn't fix is BoxArt Grab+Move.

WiiUPro has a different calibration and speed, I didn't manage to find how to correctly catch the cover and make it move at the same speed than the cursor. I decided to left it out, I can bind it to Dpad instead.
 
I'm running version 1235 from the internal updater while it was still available. I'm not having any issues with banners, free space, or anything. It's working great for me and seems perfectly stable. I'm on vWii.
 
  • Like
Reactions: Cyan
Well, I haven't tried wiixplorer yet. But recuva (recovering software) shows me this after running a deep scan: (attached image)
Which would indicate corruption.
Thing is, how did it happen? There was no error or nothing. Everything just "disappeared" after trying to install the wad...

you tried to write in a corrupted sector it's always best to install wads on the computer, it's happened to me when loading a game had to format even using a recovery program didn't solve the issue
 
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 <--- My own test : banner preview issue still present on vWii + SD only + 1 gameCube on SD card + use default banner.
04 : 03 + use clean libogc1.8.12 <--- My own test : banner preview issue still present on vWii + SD only + 1 gameCube on SD card + use default banner.
05 : 04 + removed libwupc support

Just tested v03 and it seems more stable to me, having hard stressing I didn't experience any problem, just 1 green screen after about 1 minute of hard stress tests, it shouldn't green screen under normal use.
Correct channel display, correct HDD free space display, CC and WUPC working both fine.
 
  • Like
Reactions: Cyan
thank you for your tests :)

So it seems PS3 library is the issue, but you didn't test 02?
I can make a version without PS3 but with aspect ratio fixer.
please test v06 and v07.
if v07 works, it would be great.


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

Edit:
something strange, since I restored official 1.8.12 (v04+) the filesize is bigger.
Maybe I had an issue with libogc.


note:
my test with missing banner has no issue if I select Wii games + Gamecube games.
it only happen if I select Gamecube Games alone.
another strange behavior...
 
thank you for your tests :)

So it seems PS3 library is the issue, but you didn't test 02?
I can make a version without PS3 but with aspect ratio fixer.
please test v06 and v07.
if v07 works, it would be great.

No problem, glad to help :), just notice that I hand't tested the one with PS3 support throughfully, I don't have a PS3 controller for starters :P.
Will test more revs. later, but I can confirm without doubts that v03 is the one worked best for me until now (at least like previous r1233).
 

Site & Scene News

Popular threads in this forum