Hacking USB Loader GX Blackscreen on game load

[DrPork]

Im aware of the several other threads in the past years about this problem but i have tried the usual fixed suggested.
i tried both usb slots with both a usb stick and an external harddrive, both a wbfs partition and ntfs, and i tried a 2GB SD card and a 8GB SDHC card (SD from sandisk SDHC from hp).
if i try running any game stored on the usb device, or even just running a normal retail game disk through USB Loader GX results in a black screen.
Heres my syscheck:

sysCheck v2.1.0b13 by Double_A and R2-D2199
...runs on IOS58 (rev 6176).

Region: PAL
System Menu 4.3E (v514)
Priilaoder installed
Homebrew Channel 1.0.0 running on IOS0
Hollywood v0x11
Console ID: 45087386
Boot2 v4
Found 80 titles.
Found 46 IOS on this console. 15 of them are 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
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249[56] (rev 21010, Info: d2x-v10beta53-al): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21010, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65280): Stub
BC v6
MIOS v10

Report generated on 2018/10/03.

 

[Cyan]

thanks for posting a syscheck, and explaining what you already did.

set video mode correctly (disc default), or just reset the settings if not sure.
Don't play games from other region until you are sure your settings are good.
reinstall your slot249 with d2x v10 r52 (R53 is bad).
Try another loader, etc.


if not helping, there's obviously something you do wrong, even if you already tried a lot of different things, but we don't know what.
So I suggest you re-do everything from the beginning :

Format your SD, format your USB to FAT32 32k/cluster, don't use Flash drive, plug in correct USB Port 0 (trying both for fun is useless, just plug it in the correct one right away), reinstall the loader from zero on your SD (don't keep old settings, etc.), install the forwarder if you use it (use v5.1) and the games correctly (with proper tools, not manually), use component cable (not composite), try other loaders, set IOS slot to 250 in loader's setting (because your current 249 is wrong, your good slot is 250).

it's suppose to be very easy to setup and use, it shouldn't be harder than :

install HBC
install d2x r52 base57 (in 249, for even easier usage)
plug USB HDD (not flash) FAT32 in port 0
extract the latest version of the loader to SD and launch it. don't put homebrew on USB, keep usb for game, iso, roms, emunand only. not homebrew.
optional : if hdd has init issue, set loader's IOS to 58 in the settings.
insert a game disc and select "install", once installed, launch it. if you already have the iso or the wbfs, use wiibackupmanager, don't assume you know what you are doing when copying the game manually to HDD.


all black screens issues are because of random user's actions which seems not a problem, but are :
- NTFS compression is not compatible
- FAT32 file write protection is not compatible
- copying the game manually on the USB, in wrong folder or wrong filename or wrong path
- editing video mode randomly
- plugging the usb in the wrong port
- setting debug mode without a debugger hardware
- using d2x r53 in slot 249 without understanding why you installed this version

 

[DrPork]

thanks for posting a syscheck, and explaining what you already did.

set video mode correctly (disc default), or just reset the settings if not sure.
Don't play games from other region until you are sure your settings are good.
reinstall your slot249 with d2x v10 r52 (R53 is bad).
Try another loader, etc.


if not helping, there's obviously something you do wrong, even if you already tried a lot of different things, but we don't know what.
So I suggest you re-do everything from the beginning :

Format your SD, format your USB to FAT32 32k/cluster, don't use Flash drive, plug in correct USB Port 0 (trying both for fun is useless, just plug it in the correct one right away), reinstall the loader from zero on your SD (don't keep old settings, etc.), install the forwarder if you use it (use v5.1) and the games correctly (with proper tools, not manually), use component cable (not composite), try other loaders, set IOS slot to 250 in loader's setting (because your current 249 is wrong, your good slot is 250).

it's suppose to be very easy to setup and use, it shouldn't be harder than :

install HBC
install d2x r52 base57 (in 249, for even easier usage)
plug USB HDD (not flash) FAT32 in port 0
extract the latest version of the loader to SD and launch it. don't put homebrew on USB, keep usb for game, iso, roms, emunand only. not homebrew.
optional : if hdd has init issue, set loader's IOS to 58 in the settings.
insert a game disc and select "install", once installed, launch it. if you already have the iso or the wbfs, use wiibackupmanager, don't assume you know what you are doing when copying the game manually to HDD.


all black screens issues are because of random user's actions which seems not a problem, but are :
- NTFS compression is not compatible
- FAT32 file write protection is not compatible
- copying the game manually on the USB, in wrong folder or wrong filename or wrong path
- editing video mode randomly
- plugging the usb in the wrong port
- setting debug mode without a debugger hardware
- using d2x r53 in slot 249 without understanding why you installed this version

Hey thanks for the huge help! im already using wiibackupmanagerbtw, which converted the isos to wbfs and put them into a "wbfs" folder in the root of the harddrive, but indeed reinstalling r52 over r53-alt did solve all of the problems i was experiencing! keep up the good work.

 

[Cyan]

oh, so r52 fixed your issue ?
I went too far to find another possibility ahah

glad it works now
I still suggest you set your IOS to 250 in the loader settings :
settings > loader settings > Loader's IOS and game's IOS : 250

your slot250 is based on IOS57 which has better game compatibility.
or, if you installed d2x base57 in slot249 then you don't have anything to edit, the loader uses 249 by default.

 

[DrPork]

oh, so r52 fixed your issue ?
I went too far to find another possibility ahah

glad it works now
I still suggest you set your IOS to 250 in the loader settings :
settings > loader settings > Loader's IOS and game's IOS : 250

your slot250 is based on IOS57 which has better game compatibility.
or, if you installed d2x base57 in slot249 then you don't have anything to edit, the loader uses 249 by default.

i did install 47 on 249, is there some guide which explains what the bases and isos mean?

 

[Cyan]

I started a guide to explain the slots.
there's no guide (yet. there will be mine later) which explain the base.
there's a small explanation which explain the version on d2x website and softmod guides. (posted at the bottom of this post)


here is a quick recap:

Slot:
slots below 200 contains official nintendo IOS.
IOS contain modules which are responsible to communicate with the hardware (disc, usb, wiimote, network, wiki, bluetooth, NAND, etc.) but also for security (cryptology, access restriction, signature check, etc.)
nintendo decided to install different IOS with different features in new empty slots, instead of updating existing IOS. so, you can see some of the slot as different available features. (IOS58 adds USB2.0 for example). higher slots doesn't mean IOS are better than the one in lower slots. they are different.

First nintendo's IOS had a bug (the trucha bug), which was later fixed.
Hackers decided to re-add the bug by patching the IOS. to keep better compatibility with official games and system, the original IOS shouldn't be modified, so the patched IOS were installed in new empty slots that we knew nintendo wouldn't use : 200 and above.
Some hackers started to patch the existing IOS by replacing the existing ones in their current slots. but it created issues (because official games still used them, and it created problems) (CIOSCORPS/DARKCORPS/PimpMyWii ....)

read my guide for more detailed explanation on IOS and slots.

Base:
as said above, different IOS have different features. some games require specific IOS to function correctly.
cIOS (patched IOS) are "based on official existing IOS", which therefore contains the original IOS features (modules and functions), with added patches (redirect disc access to USB for USBLoaders for example).
the patched result is installed in any slot you choose, to not replace the "base" original IOS.
d2x v8 249 base56 = the slot 249 contains a copy of IOS56, with d2x v8 patches applied to it.

the base for cIOS were chosen semi randomly :
38 was the old base up to cIOS rev17. since rev18 it's possible to use other bases, 37, 38, 56, 57, ....people noticed 56 had a higher USB access speed when using it as base for the cIOS. so base56 was decided to be in default USBLoader slot (249).
some games crashed with 38, and worked fine with 56, so it was also decided 56 was better. 57 was a bonus and usually installed in slot250 for no real reason, except stop having duplicated IOS base for no real purpose.
later, some games were found to have issues with 56 and work only with 57 (call of duty, just dance, sing it), and while all other games also work with 57, I know suggest user to use 57 as default instead of 56, even if slightly slower to access USB.


version:
d2x v8 final : latest final/stable release.
d2x v9 beta : new features were tested, but never officially released as still in beta test phase : USB Port1 support, Plug & play support, but it created HDD init and compatibility issue (this is the problem you had!), and emuNAND issues.
WiiU was released before v9 development was completed, and a new update of IOS was needed to support vWii.
as v9 was still beta, and unstable, "v9" couldn't be released and used as "update of v8" for the vWii, so Davebaol decided to skip the v9 and number the updated v8 for vWii as "v10": v10 revision 52 is the exact same version as v8.
he also decided to release the "v9 beta" branch for vWii at the same time, as v10-alternative. v10 revision 53 is the exact same version as v9 (with the bugs !).
if d2x v10 was released, people would think v8 is old and they would want to update to v10, on Wii .... which would be disastrous.

So, 4 different version were released : both v10 and v10-alt were therefore release for Wii and vWii to look like the new update. v10 wii (re-release of v8, but numbered v10), v10vWii, v10-alt wii (re-release of v9 wii, but numbered v10), v10-alt vWii.
people thought "revision 53 is better because newer !" without understanding it was a beta version, with bugs.
a lot of guides (specifically CompleteSoftmodGuide) thought a good idea to randomly mix v10 r53 and r52, with base57 and base56.... without taking in account the bugs, the features, and the reason why the "v9/v10-alt" existed in the first place.

additional d2x-alt Cons (unknow at release date):
- no Wii games on SD support.
- HDD detection issue
- some games incompatibility (just dance work with r52, not r53, even if using IOS57 as base)


bonus: problem with old completeSoftmodGuide:
249: 10-alt base 57
250: 10 base56
by default it used alt, which was compatible with Port1, but had HDD issues. to fix the hdd issues, users could use slot250 but then only Port0 was possible and it had base56 that some games didn't like.
as a result : call of duty, or just dance, would work on neither slot, not usb port.

hopefully, that guide has finally be updated in 2018 ! years later after the ill was done to too many people.
we still noticed less users with compatibility issue thanks to the guide fix.