This method has been circulating around since yesterday. Presumably, it was discovered on a Chinese forum.

Using this method allows you to stay connected without DNS blocking, and therefore have complete access to Nintendo services.

There are some concerns floating around about this process. So here is a complete guide detailing the process.

Disclaimer:
The following guide tampers with your NAND. Use this with caution or there is a good chance you'll MESS UP your Wii U for good, or even BRICK!

Requirements:

• A Wii U & SD: Firmware and SD size doesn't matter as long as you satisfy the other conditions
• Mocha Or Haxchi
• HBL on SD card
• ftpiiu_everywhere (Haxchi) on SD card
• Access to HBL: Browserhax, Haxchi/CBHC, or any other form of entry point, are all fine. As long as you access it.
• A PC with FTP Client: Technically it doesn't have to be a PC. It can even be done on your phone with an FTP Client. I'm using the PC for the simplicity of it. FileZilla IS RECOMMENDED.
• Optional: Use Nand Dumper to back up your nand with all it's contents, as well as dumping the OTP and SEEPRPOM. By having those, you can unbrick your system with a hardmod at any point. Dumping MLC will require a 64GB SD card if your Wii U is 32GB, or 16GB SD card if your Wii U is 8GB.

1A) Using Haxchi/CBHC:

1. System Menu: Have Haxchi reboot to System menu.
2. System Menu: Launch HBL via Haxchi or browser.
3. HBL: Launch ftpiiu_everywhere.
4. Proceed to section "2)" of the guide to block updates. Proceed to section "3)" if you want to unblock them again.

1B) Using Mocha:

1. System Menu: Launch HBL via browser.
2. HBL: Start Mocha (Using default values are fine)
3. System Menu: Launch HBL via browser again.
4. HBL: Launch ftpiiu_everywhere.
5. Proceed to section "2)" of the guide to block updates. Proceed to section "3)" if you want to unblock them again.

2) Modifying your Nand, and blocking updates:

1. PC: Use an FTP client to connect to your Wii U using the IP address and port on your Wii U screen.
2. PC: Once connected, Navigate to: "storage_mlc/sys/"
3. PC: Locate "update" folder, right-click it and Pick "File Permissions". Make sure it's the same as the screenshot below. If it's not the same, then make note of that. You will need it if you want to enable updates later. If it's the Same, then proceed to the next Step.
   
4. PC: Delete “update” folder.
5. Wii U: Press "Home" button to get back to HBL, press it again to get back to Mii Maker.
6. Wii U: Exit Mii Maker, and click on system settings.
7. System Settings: Attempt to update your Wii U as Normal. A few seconds after it starts and the progress bar appears, it should give out this error code: 105-3012. If the progress bar actually continues to move, TURN OFF THE WII U IMMEDIATELY!! Recheck your steps, cause something went wrong.

3) Unblocking updates:

If for whatever reason, you would like to return the Wii U to it's original updating state, start by following "1A)" or "1B)" of the guide, then proceed to the next step of this section:

1. PC: Use an FTP client to connect to your Wii U using the IP address and port on your Wii U screen.
2. PC: Once connected, Navigate to: "storage_mlc/sys/"
3. PC: Right-click, and select "Create Directory". Create “update” folder. Once created, right-click again, and select "File Permissions".
4. PC: When you originally did section "2)", if your permissions were the same as the screenshot in that section, enter those same permissions here. If not, then you should have noted them down somewhere. Enter those values instead, then click ok.
5. Wii U: Press "Home" button to get back to HBL, press it again to get back to Mii Maker.
6. Wii U: Exit Mii Maker, and click on system settings.
7. System Settings: Attempt to update your Wii U as Normal. It should proceed to update normally.

Credits:
@fejich for being the first to notify us about a Chinese website doing this method in this thread
@Shaoxudong for translating the process, and testing it.

 

[OzKenny1983]

Thanks heaps for this! Have been using the DNS method for ages and have therefore not been able to do much official Nintendo stuff. Not too sure whether this has actually worked but I suppose we shall see (I tried to update but since I'm on latest firmware and no disc patches or anything else seem to be needed, that's what I was told).

 

[Cylent1]

I have been out of the WiiU scene for a couple of years now and don't quite remember everything, but
I am looking for a safe secure way to block system updates on my WiiU. Is this still a good tutorial to do so?
Or is the a safer better way?

This is what DNS is on my WiiU right now, Does this still work?
Primary: 081.004.127.020
Secondary: 168.235.092.108

 

[Madridi]

I have been out of the WiiU scene for a couple of years now and don't quite remember everything, but
I am looking for a safe secure way to block system updates on my WiiU. Is this still a good tutorial to do so?
Or is the a safer better way?

This is what DNS is on my WiiU right now, Does this still work?
Primary: 081.004.127.020
Secondary: 168.235.092.108

Nowadays, from what I understand, the browser exploit on the latest firmware is now reliable as the one we had on 5.5.1 (found here). Therefore, I would recommend updating to the latest firmware anyway. Maybe @Ryccardo can back me up on this, just in case I am missing an advantage for staying on a lower firmware.

While it's unlikely that a Wii U update will ever be released beyond 5.5.3, yes this tutorial is what you should follow. There is no reason to use the DNS anymore, and you can enjoy online services freely.

 

[Cyan]

I don't see any advantage anymore.
like you said, the advantage was the more stable browserhax exploit. once haxchi was installed, users could update to 5.5.3.
Now, even if you don't want haxchi or cbhc, you can keep using the browser as easy entry point.
I didn't test the new exploit yet, but all users report confirm it's working 100%

keeping the console on an old version is only problematic : you need to block NUS to stay on old firmware, being blocked you need to spoof the firmware version and use NNUpatcher every time you want to access eshop, some game won't boot if you don't update (requiring nnu patcher too).
Even the DNS on latest firmware version can be problematic and give some errors on game launch (not able to access eshop to get latest update, etc.)

Of course, you can keep using old version, just know that there is more steps in hacking and in using the console daily. I deleted the hacking part covering old firmwares in our main guide, and suggest everyone to update first.

 

[oslo83]

I was still using webhax and mocha with 5.5.0 spoofed to 5.5.3
So we can drop the 5.5.0 webexploit with a 80% success rate to a 5.5.3's with 100% success rate?
I just updated my spoof from 5.5.2 to 5.5.3 yesterday.

 

[Cyan]

if you have mocha, you can update.
If you have CBHC on a EUR console, you'll have to reinstall CBHC after updating to 5.5.3.

If you don't have any reason to update or issues using nnu patcher, you can continue with spoof 5.5.3.
there's no compatibility problem by staying on old 5.5.x, it's only easier to use without nnu.

the new browser exploit requires a payload on SD card, while previous browser exploit downloaded it directly from internet. that's the only difference.
I didn't see enough report to confirm it's 100%, but the few I saw said it worked on first try.

 

[huma_dawii]

if you have mocha, you can update.
If you have CBHC on a EUR console, you'll have to reinstall CBHC after updating to 5.5.3.

If you don't have any reason to update or issues using nnu patcher, you can continue with spoof 5.5.3.
there's no compatibility problem by staying on old 5.5.x, it's only easier to use without nnu.

the new browser exploit requires a payload on SD card, while previous browser exploit downloaded it directly from internet. that's the only difference.
I didn't see enough report to confirm it's 100%, but the few I saw said it worked on first try.

I can confirm the new exploit don't need anything in the SD card... Not that I know. Maybe it downloads it by itself?

 

[Cyan]

https://gbatemp.net/threads/more-stable-webhack-for-5-5-2-5-5-3-released.528757/
it says "grab the payload.elf"
so in my guide I also added this step. Like I said I didn't try yet so I'm not sure if it's downloading it if missing.

maybe if you have the payload on SD, it uses it and works better because it's doesn't have to wait for it? if you don't it downloads it (and can fail due to race exploit)?

 

[huma_dawii]

https://gbatemp.net/threads/more-stable-webhack-for-5-5-2-5-5-3-released.528757/
it says "grab the payload.elf"
so in my guide I also added this step. Like I said I didn't try yet so I'm not sure if it's downloading it if missing.
maybe if you have the payload on SD, it uses it and works better because it's doesn't have to wait for it? if you don't it downloads it (and can fail due to race exploit)?

I know for a fact I used the new webhack from loadiine.net and I have not downloaded anything on my SD regarding a new exploit.

 

[Madridi]

I know for a fact I used the new webhack from loadiine.net and I have not downloaded anything on my SD regarding a new exploit.

Like @Cyan, I have not tried the new webhack yet.

That said, the impressions he has about that is the same impressions I have got about the hack.

Also, I am getting the impression that you seem to think there is only one hack for 5.5.3, the one released like a year or so ago? The one with all the deltas? I am pretty sure that’s what you have tried, and that one had pretty bad success rates (around 40-50 percent)

This one was released about a month ago. As far as I understand, it uses a payload on the sd, just like cyan mentioned. It has a success rate close to 100%, and there are no deltas anymore.

If you are indeed talking about this one, then my apologies. I am just tryin* to clear the misunderstanding here

 

[huma_dawii]

Like @Cyan, I have not tried the new webhack yet.

That said, the impressions he has about that is the same impressions I have got about the hack.

Also, I am getting the impression that you seem to think there is only one hack for 5.5.3, the one released like a year or so ago? The one with all the deltas? I am pretty sure that’s what you have tried, and that one had pretty bad success rates (around 40-50 percent)

This one was released about a month ago. As far as I understand, it uses a payload on the sd, just like cyan mentioned. It has a success rate close to 100%, and there are no deltas anymore.

If you are indeed talking about this one, then my apologies. I am just tryin* to clear the misunderstanding here

Not rwreal I have tried the new one, not the Delta's one. Loadiine.ovh is on the way of getting rid of the Delta's system and gonna transition completely to the new type of briwerb hax. I know for a fact I have used the new one.

To be more precise, is this one:

 

[Madridi]

Not rwreal I have tried the new one, not the Delta's one. Loadiine.ovh is on the way of getting rid of the Delta's system and gonna transition completely to the new type of briwerb hax. I know for a fact I have used the new one.

To be more precise, is this one:

So you used it within a month and a half ago? Good to know.

In which case, it would be helpful if you post in that thread, clarifying where it states a payload is needed on the sd in the instructions. I am sure Cyan and I aren't the only ones who misunderstood this, if it is a misunderstanding to begin with

 

[huma_dawii]

So you used it within a month and a half ago? Good to know.

In which case, it would be helpful if you post in that thread, clarifying where it states a payload is needed on the sd in the instructions. I am sure Cyan and I aren't the only ones who misunderstood this, if it is a misunderstanding to begin with

I used like 1 week ago.

Will test on a different Wii U today

 

[Madridi]

I used like 1 week ago.

Will test on a different Wii U today

I finally had time to test this exploit, and I can for sure say that it does need a payload.elf on your sd card.

Do me a favor. Check your sd card. Open up the "wiiu" folder. You will see a bunch of folders. Do you see a payload.elf there?

If yes, then this means that you already had it from before.
If not, then @Cybernatus is using something different on loadiine.ovh

 

[huma_dawii]

I finally had time to test this exploit, and I can for sure say that it does need a payload.elf on your sd card.

Do me a favor. Check your sd card. Open up the "wiiu" folder. You will see a bunch of folders. Do you see a payload.elf there?

If yes, then this means that you already had it from before.
If not, then @Cybernatus is using something different on loadiine.ovh

I can't check until like next week xD

 

[Madridi]

I can't check until like next week xD

Not a problem, but please do so. We want to make sure there aren't actually 2 methods existing. That would be huge!

 

[Rathalos143]

I cant see any folders in storage_mlc maybe I don´t know how to reboot in system menu?

 

[Madridi]

I cant see any folders in storage_mlc maybe I don´t know how to reboot in system menu?

I need more info than that..

 

[Rathalos143]

I need more info than that..

Lets see, I go to the HBL, I run sygpatcher menu and it returns me to the WII U menu. Then I enter HBL again and run the ftp client but when I go to the directory it shows no folders nor files. I can access the SD with Filezilla tho just the console directories dont show me any folders, it even gives an error like "failed at recovering directory list"

 

[Madridi]

Lets see, I go to the HBL, I run sygpatcher menu and it returns me to the WII U menu. Then I enter HBL again and run the ftp client but when I go to the directory it shows no folders nor files. I can access the SD with Filezilla tho just the console directories dont show me any folders, it even gives an error like "failed at recovering directory list"

Where in the instructions did I mention sig patcher?

I suggest rereading the guide..