Accessing Wii Shop Channel from PC
This page gives a how-to on accessing the Wii Shop Channel from your PC's web browser. The Wii Shop website is querying the entire Nintendo ecommerce database, this means that newer titles could technically appear on it. For example, Splatoon Testfire for the Wii U's page can appear on here.
What you need
- Certificate file, the password for it is
alpine - Browser that can change it's user agent to
Opera/9.30 (Nintendo Wii; U; ; 2077-4; Wii Shop Channel/21.0(A); en)
Google Chrome
- Go to
chrome://settings/certificatesand click Import - Press
Ctrl+Shift+I - Click on the three dots in the top right of the panel
- Hover on More tools
- Click on Network conditions, a panel will now open at the bottom
- Turn off Use browser default
- Set the option to Custom
- Use this user agent:
Opera/9.30 (Nintendo Wii; U; ; 2077-4; Wii Shop Channel/21.0(A); en)
Mozilla Firefox
- Go to
about:preferences#privacyand then scroll down until you see View Certificates, click on it and import the file - Go to
about:configand search forgeneral.useragent.override - Click on String and + and input
Opera/9.30 (Nintendo Wii; U; ; 2077-4; Wii Shop Channel/21.0(A); en)
Polyfilling WSC APIs for functionality
Normally the Wii Shop Channel provides several JS APIs. When opening the site on PC, since these APIs aren't present the site won't function properly. In order to fix this you can install this userscript to mock these APIs and navigate around the site properly. You might need a browser extension like Tampermonkey in order to install a userscript.
Pages
Extra URLs
| URL | Purpose |
|---|---|
| https://ecs.shop.wii.com/ecs/services/ECommerceSOAP | ECS SOAP Service |
| https://ias.shop.wii.com/ias/services/IdentityAuthenticationSOAP | IAS SOAP Service |
| https://cas.shop.wii.com/cas/services/CatalogingSOAP | CAS SOAP Service |
| https://nus.shop.wii.com/nus/services/NetUpdateSOAP | NUS SOAP Service |
| http://ccs.cdn.shop.wii.com/ccs/download | Cached Content Server—Downloading software |
| https://ccs.shop.wii.com/ccs/download | Uncached Content Server—Downloading software (seemingly slower than CCS) |
Authenticated pages
To access some pages, you need to include special parameters in the URL about your console. Generally, authenticated pages require the following parameters:
accountId- Your Wii Shop Channel account's IDdeviceId- Your Wii's device ID (not your serial)serialNo- Your Wii's serial number. This can be found on the bottom of your Wii's case.token- Your Wii Shop Channel account's "weak token". It's unknown exactly what this is.
To get the values for these parameters, you must capture logs from the shop in Dolphin containing them. To do so:
- Enable Dolphin's debugging UI by going into Config > Interface and toggling Enable Debugging UI on.
- Ensure that you have a NAND backup imported into Dolphin from your Wii.
- Open the Wii Shop Channel on Dolphin, ensuring you have the original, unmodified Wii Shop Channel installed.
- As soon as you see the initial "Wii" loading screen, pause the emulation.
- Go into the Code tab within the Debugging UI (you may have to enable it by opening the View menu and toggling on Code) and enter the address
80078610into the Search Address box. - Right click the instruction highlighted on the right hand side of the Debugging UI, and select Add function. Right click the instruction again, but select Rename symbol and enter
OSReportas the name. - Open the Symbols menu at the top of the program and select Patch HLE Functions.
- Switch to the Log Configuration tab within the Debugging UI (you may have to enable it like the Code tab) and ensure OSReport HLE is enabled in the list of log types near the bottom of the UI.
- Switch to the Log tab within the Debugging UI (you may have to enable it like the other two) and play the emulation. You should see logs populate in the large black text area. Wait until you load into the shop.
- Once loaded in, look through the logs to find your accountId, deviceId, and token. These values can be found in the various SOAP requests (XML blocks) throughout the logs. Save these somewhere.
- Finally, add the values you found into the URL of your desired authenticated page.
An example of valid authenticated URL structure:
https://oss-auth.shop.wii.com/oss/serv/H_01.jsp?accountId=[Your Account ID]&deviceId=[Your Device ID]&serialNo=[Your serial]&token=[Your weak token]