Black screen when loading Wii System Menu (4.3U)

seoulgamer · 05-22-2017, 03:41 AM #1

As the title states, I cannot load the Wii system menu even after installing the appropriate WAD file. I am using a development build, 5.0-3817, with the OpenGL backend and a GTX 1050 Ti GPU.

I have no idea what I'm doing wrong or where to begin troubleshooting.

**JosJuice** · 05-22-2017, 04:00 AM #2

Did you install the right IOS too?

seoulgamer · 05-24-2017, 04:12 AM #3

(05-22-2017, 04:00 AM)JosJuice Wrote: Did you install the right IOS too?

I'm not trying to install any channels, just get the System Menu working, so I didn't install any IOS. Do I need one?

**leolam** · 05-24-2017, 04:29 AM #4

No IOS should be *required* to use the System Menu, because we HLE IOS.

IOSes *must* be installed if you want Dolphin to handle requests from the emulated software properly though. This is because they can ask for information about installed system software, so even though we cannot actually run the IOSes yet, we still need the titles themselves to be installed to have that metadata available.

You will definitely need at least the System Menu IOS for online updates. (4.3's IOS is IOS80 and can be downloaded from NUS using NUS Downloader.)

I'm not sure why you're getting a black screen. Is your language setting correct? Are you sure you've installed the correct version?

seoulgamer · 06-13-2017, 07:54 AM #5

(05-24-2017, 04:29 AM)leolam Wrote: No IOS should be *required* to use the System Menu, because we HLE IOS.

IOSes *must* be installed if you want Dolphin to handle requests from the emulated software properly though. This is because they can ask for information about installed system software, so even though we cannot actually run the IOSes yet, we still need the titles themselves to be installed to have that metadata available.

You will definitely need at least the System Menu IOS for online updates. (4.3's IOS is IOS80 and can be downloaded from NUS using NUS Downloader.)

I'm not sure why you're getting a black screen. Is your language setting correct? Are you sure you've installed the correct version?

Hello again,

I have no idea. I've tried everything. Simply downloading and installing the WAD for System Menu 4.3U doesn't work. I've concluded that the current development builds have broken the System Menu, since it works fine on Dolphin 5.0

**leolam** · 06-13-2017, 07:56 AM #6

Have you tried a clean Dolphin profile? It's very much possible that something is wrong with your NAND.

seoulgamer · 06-16-2017, 09:13 AM #7

OK, so it turns out you can't install the WAD for System Menu with any developer build of Dolphin or it breaks when you try to run it, but if you use a stable build like 5.0, it works fine.

So all I had to do was uninstall the developer build, install Dolphin 5.0, install the WAD, then reinstall the latest developer build and it worked fine. But the System Menu can't be installed using a developer build at the moment. I'm sure Dolphin's developers have more interesting things to work on, but it would be cool if someone could look in to this at some point.

**leolam** · (This post was last modified: 06-16-2017, 11:54 PM by leolam.)

If you can't install it, that means your WAD is bad. The install WAD option was fixed to reuse our emulation code, so it now fails if it detects any hash mismatch during import.

At this point, you could consider 5.0 wildly inaccurate for Wii operating system emulation stuff.

Edit: You are likely using a fake signed WAD, one that incorrectly sets the common key index to "1" (Korean). This tells Dolphin to decrypt the contents using the Korean key. Obviously, the System Menu WAD is supposed to use the normal common key, not the Korean one.

* The install code is designed to be accurate now, so it will detect the issue and fail on purpose.
* The boot code still hasn't been fixed yet, so it will allow you to boot the WAD but decrypt the WAD using the wrong key (because of an accuracy change).

5.0 just doesn't care about any of that and always uses the normal common key, which works around your particular issue, but is obviously inaccurate.
Dolphin failing instead of letting you use this broken WAD is the correct behaviour. It even matches IOS on a real Wii.

seoulgamer · 06-19-2017, 05:33 PM #9

OK, that makes sense. I don't know how I ended up with a bad WAD since I used NUSdownloader to obtain it, but perhaps I made a mistake. I could have sworn it was 4.3U I downloaded.

Anyway, if I was in fact installing a dodgy WAD file, I think it would have been helpful to have an error message. I can see why you would want it to fail if the WAD is the wrong type, but it leaves users in the dark about what's happening if there's no warning (like "incorrect key index" or something).

Thank you very much for all your help!

**leolam** · (This post was last modified: 06-19-2017, 05:44 PM by leolam.)

No problem. We should really print a warning for any hash mismatch. For now, if you get any weird errors, just enable logging (for the IOS_ES type) and in most cases, that will be more than enough to figure out what the issue is.

By the way, there's no way to distinguish the "incorrect key index because some tool decided to change it" case from a legitimate use of the Korean common key, sadly. We do already warn and fall back to the normal common key for any invalid value (different from 0 and 1), but if it happens to be exactly 1 (Korean), there's nothing we can do.