Код ошибки 199 9999 wii u

Whenever I try to launch Woomïnstaller from the Wii U Menu, I receive error 199-9999. A popup screen shows up, but all it says is «An error has occurred. If this error persists, contact Nintendo repairs technician» etc.

In most cases reported on the GBATemp forums, error 199-9999 is related to signature mismatches. Though I do indeed have signature checks disabled, as Woomïnstaller is only present on my redNAND setup (using Mocha btw), and I was able to successfully open the Homebrew Launcher RPX from my menu, not to mention the installation of Woomïnstaller itself succeeded, all within the same boot cycle.

If you’re interested, I installed Woomïnstaller on my console by downloading your Git repo, building it (100 or so warnings, probably related to me compiling it with devkitPPC r28 and all of its changed type declarations. 😜) and then copying the FST contents to my SD Card, which I installed on my console using WUPInstaller Y Mod.

The received error message that I mentioned above was very vague about the problem, though I may have found more valuable information in my system log. (Thanks to VinsCool for showing me this trick). I have attached an exert from said logs (/vol/system_slc/usr/logs/28.log I believe it was), which were extracted from my console by rebooting after the 199-9999 error, booting my redNAND and then launching FTPiiU Everywhere.

The log I have provided begins from the point I launched Mocha redNAND, walks through with me as I launch HBL, launch WUPInstaller, use it to install Woomïnstaller’s FST data, close it and return to HBL, close it and return to the Wii U Menu and finally attempt to launch Woomïnstaller, which results in error 199-9999.

syslog.zip

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Hacking Installed wup installer gx2 channel, error code 199-9999


  • Thread starter

    Filo97


  • Start date

    Mar 9, 2017


  • Views
    21,904

  • Replies
    13

Filo97

  • #1

When i boot the channel, it gives me the error code 199-9999, every other app works fine.
I am using CBHC 1.6 on a 5.5.1 EUR wiiu. help?

  • #2

Is it installed to NAND or USB?
If on USB try installing to NAND

Filo97

  • #3

Is it installed to NAND or USB?
If on USB try installing to NAND

it is installed to NAND.

Deleted User

Guest

  • #5

Try using loadiine.ovh to install it or HBL channel version to install it.
In my case, installing it by launching browserhax [Launching HBL from browser then using Wup Installer Mod Y] fixed my problem.

Filo97

  • #6

Try using loadiine.ovh to install it or HBL channel version to install it.
In my case, installing it by launching browserhax [Launching HBL from browser then using Wup Installer Mod Y] fixed my problem.

I will try both.

——————— MERGED —————————

installing to USB did the trick. the browserhax one didn’t, but the USB one did, thanks a lot @xtheman166!

  • #7

Sorry to bump this, but why can’t it be installed to the NAND? Does anyone happen to know? I’m getting this error as well and I’m just curious, and I’m also kinda wanting to keep all homebrew on the NAND.

  • #8

Sorry to bump this, but why can’t it be installed to the NAND? Does anyone happen to know? I’m getting this error as well and I’m just curious, and I’m also kinda wanting to keep all homebrew on the NAND.

Try what Felek said. I have mine installed to nand just fine. I used the HBL channel then WUP Installer GX2 to install the channel

EclipseSin

  • #9

199-9999 usually means you forgot to run CFW/Sigpatcher first.

Joined
Jun 3, 2017
Messages
3
Trophies
0
Age
36
XP

43

Country
Gambia, The

  • #10

199-9999 usually means you forgot to run CFW/Sigpatcher first.

got the same error even with CFW (mocha)…any advice?

lukands

  • #11

I actually got the same error also. But not a big deal I guess, I just went through the HBL instead.

EDIT…on USB I believe?

Joined
Jun 3, 2017
Messages
3
Trophies
0
Age
36
XP

43

Country
Gambia, The

  • #12

I actually got the same error also. But not a big deal I guess, I just went through the HBL instead.

EDIT…on USB I believe?

…oh that was a good idea…through HBL it does work…without HBL I only had the option:

1. with USB drive connected —> does not work
2. without USB drive connected —> does work

—> deadlock :(

  • #13

1. with USB drive connected —> does not work
2. without USB drive connected —> does work

I have exactly the same issue. It’s impossible to launch the channel version from NAND when the HDD is attached. It always results in 199-9999.

Is there really no fix for this aside from installing it to USB or using the .elf version? ..which is not really a fix for the actual problem.

Similar threads

crispyfriedKFCrat

K3N1

@

K3N1:

https://www.nytimes.com/2023/05/27/nyregion/avianca-airline-lawsuit-chatgpt.html

15 minutes ago

Whenever I try to launch Woomïnstaller from the Wii U Menu, I receive error 199-9999. A popup screen shows up, but all it says is «An error has occurred. If this error persists, contact Nintendo repairs technician» etc.

In most cases reported on the GBATemp forums, error 199-9999 is related to signature mismatches. Though I do indeed have signature checks disabled, as Woomïnstaller is only present on my redNAND setup (using Mocha btw), and I was able to successfully open the Homebrew Launcher RPX from my menu, not to mention the installation of Woomïnstaller itself succeeded, all within the same boot cycle.

If you’re interested, I installed Woomïnstaller on my console by downloading your Git repo, building it (100 or so warnings, probably related to me compiling it with devkitPPC r28 and all of its changed type declarations. 😜) and then copying the FST contents to my SD Card, which I installed on my console using WUPInstaller Y Mod.

The received error message that I mentioned above was very vague about the problem, though I may have found more valuable information in my system log. (Thanks to VinsCool for showing me this trick). I have attached an exert from said logs (/vol/system_slc/usr/logs/28.log I believe it was), which were extracted from my console by rebooting after the 199-9999 error, booting my redNAND and then launching FTPiiU Everywhere.

The log I have provided begins from the point I launched Mocha redNAND, walks through with me as I launch HBL, launch WUPInstaller, use it to install Woomïnstaller’s FST data, close it and return to HBL, close it and return to the Wii U Menu and finally attempt to launch Woomïnstaller, which results in error 199-9999.

syslog.zip

Whenever I try to launch Woomïnstaller from the Wii U Menu, I receive error 199-9999. A popup screen shows up, but all it says is «An error has occurred. If this error persists, contact Nintendo repairs technician» etc.

In most cases reported on the GBATemp forums, error 199-9999 is related to signature mismatches. Though I do indeed have signature checks disabled, as Woomïnstaller is only present on my redNAND setup (using Mocha btw), and I was able to successfully open the Homebrew Launcher RPX from my menu, not to mention the installation of Woomïnstaller itself succeeded, all within the same boot cycle.

If you’re interested, I installed Woomïnstaller on my console by downloading your Git repo, building it (100 or so warnings, probably related to me compiling it with devkitPPC r28 and all of its changed type declarations. 😜) and then copying the FST contents to my SD Card, which I installed on my console using WUPInstaller Y Mod.

The received error message that I mentioned above was very vague about the problem, though I may have found more valuable information in my system log. (Thanks to VinsCool for showing me this trick). I have attached an exert from said logs (/vol/system_slc/usr/logs/28.log I believe it was), which were extracted from my console by rebooting after the 199-9999 error, booting my redNAND and then launching FTPiiU Everywhere.

The log I have provided begins from the point I launched Mocha redNAND, walks through with me as I launch HBL, launch WUPInstaller, use it to install Woomïnstaller’s FST data, close it and return to HBL, close it and return to the Wii U Menu and finally attempt to launch Woomïnstaller, which results in error 199-9999.

syslog.zip

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Hacking Installed wup installer gx2 channel, error code 199-9999


  • Thread starter

    Filo97


  • Start date

    Mar 9, 2017


  • Views
    21,113

  • Replies
    13

Filo97

  • #1

When i boot the channel, it gives me the error code 199-9999, every other app works fine.
I am using CBHC 1.6 on a 5.5.1 EUR wiiu. help?

  • #2

Is it installed to NAND or USB?
If on USB try installing to NAND

Filo97

  • #3

Is it installed to NAND or USB?
If on USB try installing to NAND

it is installed to NAND.

Deleted User

Guest
  • #5

Try using loadiine.ovh to install it or HBL channel version to install it.
In my case, installing it by launching browserhax [Launching HBL from browser then using Wup Installer Mod Y] fixed my problem.

Filo97

  • #6

Try using loadiine.ovh to install it or HBL channel version to install it.
In my case, installing it by launching browserhax [Launching HBL from browser then using Wup Installer Mod Y] fixed my problem.

I will try both.

——————— MERGED —————————

installing to USB did the trick. the browserhax one didn’t, but the USB one did, thanks a lot @xtheman166!

  • #7

Sorry to bump this, but why can’t it be installed to the NAND? Does anyone happen to know? I’m getting this error as well and I’m just curious, and I’m also kinda wanting to keep all homebrew on the NAND.

  • #8

Sorry to bump this, but why can’t it be installed to the NAND? Does anyone happen to know? I’m getting this error as well and I’m just curious, and I’m also kinda wanting to keep all homebrew on the NAND.

Try what Felek said. I have mine installed to nand just fine. I used the HBL channel then WUP Installer GX2 to install the channel

EclipseSin

  • #9

199-9999 usually means you forgot to run CFW/Sigpatcher first.

Joined
Jun 3, 2017
Messages
3
Trophies
0
Age
35
XP

33

Country

Gambia, The

  • #10

199-9999 usually means you forgot to run CFW/Sigpatcher first.

got the same error even with CFW (mocha)…any advice?

lukands

  • #11

I actually got the same error also. But not a big deal I guess, I just went through the HBL instead.

EDIT…on USB I believe?

Joined
Jun 3, 2017
Messages
3
Trophies
0
Age
35
XP

33

Country

Gambia, The

  • #12

I actually got the same error also. But not a big deal I guess, I just went through the HBL instead.

EDIT…on USB I believe?

…oh that was a good idea…through HBL it does work…without HBL I only had the option:

1. with USB drive connected —> does not work
2. without USB drive connected —> does work

—> deadlock

  • #13

1. with USB drive connected —> does not work
2. without USB drive connected —> does work

I have exactly the same issue. It’s impossible to launch the channel version from NAND when the HDD is attached. It always results in 199-9999.

Is there really no fix for this aside from installing it to USB or using the .elf version? ..which is not really a fix for the actual problem.

Similar threads

You may also like…

  • No one is chatting at the moment.

    K3N1

    @

    K3N1:

    https://youtube.com/shorts/8q-CNsOreKE?feature=share

    Today at 6:30 AM


    Go to wiiu


    Hello, first time being here and it’s cause I have a question. So, about 6 hours ago my younger brother was going to use our wii u, (we’ve had it for about 6-8 years, we replace the disc reader and cleaned the fans a year ago) and wanted to play lego dimensions (a discontinued game incase you didn’t know) and it kept not working which I kinda just brushed it to the side cause are wii u has trouble reading disc’s. It kept giving us the stereotypical «the disc couldn’t be read» error and with the error code to go with it (didn’t look it up cause I had seen is 1,000 time’s) so, I cleaned the disc with cleaner and everything but the time we put it back in after cleaning it, didn’t work so we pulled it out again and it had a huge ????? No idea? Just a large tan line on it almost looked like spilt food. We wiped it off and dusted off the front of the thing you put the disc in (by blowing on it) and then I went back to the game I was playing on my computer, and I wasn’t looking and I heard my brother make a joke saying «error code 199-9999, that’s alot of nines» and of course curious I look and see the error code he mentioned, and since this was such a weird error code that I had never seen before I looked it up, but I didn’t really get a clear awnser besides «it has issues updating the software» which I was 100% sure that wasn’t my issue since lego dimensions is discontinued. Does anyone know why this happend? And if you know how to fix it please let me know. If you need anymore information to tell me I’ll be happy to provide.

    When using your Wii U, you may be receiving an error code 199-999 that indicates that your Wii isn’t connected to the internet. If you see this message, it may be because you don’t have a valid WiFi password or the Wii is unable to access your network. Fortunately, this error can be easily fixed. Here are a few ways to fix Wii U error codes.

    Changing Wii’s MAC filter or firewall settings

    The error code 199-999 on the Wii means that your WEP/PA security key is wrong. To change this setting, go to Wii’s system settings and find the entry for security type. Change the password and try connecting again. If you still experience problems connecting, try disabling Wii’s MAC filtering. This may also fix the problem.

    If you still haven’t found the fix for this error, then it’s worth contacting Nintendo tech support. Their customer service is ready and willing to assist you with any issues you may be experiencing. If you purchase a Wii U, you’ll also get a warranty, so you’re covered. If your problem still persists, you can also try changing your Wii’s firewall and MAC filter settings.

    Changing Wii’s security type

    Changing the Wii’s security type can resolve issues related to network security. Wii users can change the security type of the network by pressing the Wii button on the remote or by using the system settings menu. Changing the Wii’s security type will allow you to connect your console to a Wi-Fi network or to any Wi-Fi hotspot. You should ensure that your Wii’s security key matches the one on your router or system settings.

    The Wii has four basic methods for communicating with the environment, including Wi-Fi and Bluetooth. The Wii security type must protect these methods from unauthorized use. It uses different types of encryption, but there are similarities. Generally, Wii users should use AES-128-CBC encryption, which is a symmetric cipher. This means that you will need to protect your Wii’s secret key to prevent unauthorized access.

    If a Wii user cannot connect to the internet, try power cycling the console and then try again. The security type you have selected may have been set incorrectly during the initial setup. Try again with the same security type and see if the error is resolved. If not, repeat the process until you find the right security type. This is a relatively simple procedure that can fix internet connectivity issues. In addition to changing the security type, you can also power cycle your router, which should fix the error.

    Using Haxchi to hack games

    The first step to hacking games with Haxchi is to download the game. If the game is digital, you can download it through the Nintendo eShop. But if you prefer physical discs, you can download it from the Wii U’s shop. You can also install Haxchi in a different way, by rebranding it. Afterward, you should remove it by reinstalling the game.

    The first step is to insert a micro SD card into the Wii U. The system will crash if the SD card is not present. If the SD card is not present, you can fix this error by holding the power button for five seconds and then unplugging the Wii U’s AC adapter. Once the SD card is properly inserted, Haxchi will begin hacking games. Afterward, the system will boot normally, with the game working as intended.

    Next, download Haxchi from the Homebrew Launcher App. If you can’t find this application, go to the WiiU’s main menu and select it. You should now see the Haxchi icon where the DS title used to be. Once you’ve installed Haxchi, you can download other games to your console. Another step is to download the Homebrew Launcher App, but it’s really not necessary.

    Возможно, вам также будет интересно:

  • Код ошибки 197 камаз 5490
  • Код ошибки 1d161 3
  • Код ошибки 1962 на компьютере
  • Код ошибки 1c223 4
  • Код ошибки 195 фотошоп

  • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии