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.

 

[Madridi]

So isn't the DNS block safer than this? You noted that this could brick but all it does it change access permission to prevent writing to the system so updates won't download.

Read again, it deleted a folder. Not permission access.

Also, define safer? Is dns safer in terms of Lessing the likelihood of your Wii U accidentally updating? Definitely not
Is it safer in terms of user error in cases of bricking? Definitely!. The user is responsible for whatever they do to their nand.

The process itself isn't dangerous. Messing up the process is

 

[Yudowat]

This looks really good! I'll probably try it myself next time I'm doing WiiU work which will probably be FAT32 Mocha.

 

[Madridi]

Instead of deleting what about renaming to let's say update2?
This should accomplish the same thing but you can easily restore it by renaming it back.
The update code probably only checks if the update folder exists and otherwise errors out

Sure, that's the first thing that came to mind. But it was explained in my first reply in this topic that renaming doesn't work, nor does removing permissions. So the only thing we can do is delete

 

[BullyWiiPlaza]

Sure, that's the first thing that came to mind. But it was explained in my first reply in this topic that renaming doesn't work, nor does removing permissions. So the only thing we can do is delete

Ohh, nevermind. I was skimming too fast

 

[Madridi]

You can go about blocking updates with DNS, that's perfectly fine. This is just an alternate method for those who like to tinker with their system. It's completely optional and pretty cool in my opinion. It's all up to you whether or not to make use of this method or not.

It's worth mentioning that:
- DNS always has the chance of it being down at any point of time, even possibly years from now, leaving you completely vulnerable to imminent update (assuming Nintendo services still work for the Wii U by then lol)

- Without blocking DNS, you get all Nintendo services back!

 

[retrofan_k]

In Section 3: 3. Create Directory

Is the folder renamed "update" after a reboot or when a system update is initiated by the console? I'm just curious, as manual renaming a folder is not allowed from what I hear when using FTP access.

 

[Madridi]

In Section 3: 3. Create Directory

Is the folder renamed "update" after a reboot or when a system update is initiated by the console? I'm just curious, as manual renaming a folder is not allowed from what I hear when using FTP access.

I don't get it, where are you renaming anything? There is no rename involved :/

Edit: Ah ok I think I just understood your question. Yeah, renaming a folder doesn't work. But creating a folder with that name after that folder was deleted works. Does that answer your question?

 

[MattKimura]

In Section 3: 3. Create Directory

Is the folder renamed "update" after a reboot or when a system update is initiated by the console? I'm just curious, as manual renaming a folder is not allowed from what I hear when using FTP access.

Just tested creating a new folder, but this time using WinSCP (A different FTP Client that I love using personally). WinSCP also has file permissions so when I was creating a new directory, I was able to turn on file permission and by default, they're the same as Filezilla. Named it updates and hit okay, it created the folder no problem. I rebooted my console and went back to FTP, and the folder is still there.

EDIT: Even without using file permissions, it created the folder just fine

Edit 2: Jut tried launching smash bros with DNS disabled, and it tells me "A system update is required before a software update can download"

 

[Madridi]

EDIT: Even without using file permissions, it created the folder just fine

Yeah, creation works without permission, which is why the permission step might be optional. Being that the original folder had those permissions though, it's best having them on the newly created folder as well.

See what I meant when I said that I am tending to believe those reports were user errors? :/

 

[MattKimura]

Yeah, creation works without permission, which is why the permission step might be optional. Being that the original folder had those permissions though, it's best having them on the newly created folder as well.

See what I meant when I said that I am tending to believe those reports were user errors? :/

Major update:

So after finally deleting the update folder, disabling the DNS, and testing the system update, the error code came as expected.

So I went to carry on like normal and load up Smash Bros so I can update it. And I got a popup message says "A system update is required before the software update can be downloaded"

So I went and enabled the DNS setting to block updates then turned off the system. I turned it back on, enabled NNU Patcher and launched Smash Bros and it updated like normal without complaining.

This isn't the first time I seen the system ask to be on the latest update for something. Someone couldn't play Zelda Botw because it would pop up saying to update before he can play it. It would seem that setting up the DNS again actually fixes it. So basically I gotta use DNS again but thats okay, I have double the protection now. DNS, plu sno updates folder lol

The DNS seems to be doing a little more than just blocking updates. It's also preventing their servers from checking if you're on the latest update since their servers are blocked.

 

[Madridi]

Major update:

So after finally deleting the update folder, disabling the DNS, and testing the system update, the error code came as expected.

So I went to carry on like normal and load up Smash Bros so I can update it. And I got a popup message says "A system update is required before the software update can be downloaded"

So I went and enabled the DNS setting to block updates then turned off the system. I turned it back on, enabled NNU Patcher and launched Smash Bros and it updated like normal without complaining.

This isn't the first time I seen the system ask to be on the latest update for something. Someone couldn't play Zelda Botw because it would pop up saying to update before he can play it. It would seem that setting up the DNS again actually fixes it. So basically I gotta use DNS again but thats okay, I have double the protection now. DNS, plu sno updates folder lol

DNS has nothing to do with this afaik. It has to do with NNU patcher.

Try the following test:
Disable DNS, connect to the internet normally, run NNU patcher, play game

Edit: To clarify, deleting update folder and disabling DNS only achieves update blocking. You are still on a lower fw though, so you need something like NNU patcher for eshop.

 

[MattKimura]

DNS has nothing to do with this afaik. It has to do with NNU patcher.

Try the following test:
Disable DNS, connect to the internet normally, run NNU patcher, play game

Edit: To clarify, deleting update folder and disabling DNS only achieves update blocking. You are still on a lower fw though, so you need something like NNU patcher for eshop.

I can't seem to reproduce the error. I disabled the DNS setting again and everything just works fine. Without loading NNU Patcher, Loading Smash Bros works and going online. Loading Zelda Botw works just fine. It only came up when I tried updating the game. I'm gonna keep the DNS off and updates folder deleted until I can come across such a message again, and I'll take your NNU Pacher advice.

EDIT: Entering Eshop brings me back this "You must update to use this software" message

 

[Madridi]

I can't seem to reproduce the error. I disabled the DNS setting again and everything just works fine. Without loading NNU Patcher, Loading Smash Bros works and going online. Loading Zelda Botw works just fine. It only came up when I tried updating the game. I'm gonna keep the DNS off and updates folder deleted until I can come across such a message again, and I'll take your NNU Pacher advice.

You said it was updating the game. The game update uses eshop. Eshop needs NNU patcher on a lower fw than the latest. DNS has nothing to do with it

 

[MattKimura]

You said it was updating the game. The game update uses eshop. Eshop needs NNU patcher on a lower fw than the latest. DNS has nothing to do with it

OOH Okay I completely understand where you're coming from. Basically updating games and Eshop both require 5.5.2, but NNU Patcher bypasses that. When I got to Eshop with DNS disabled, I get the "You must update the system" message. Running NNU Patcher allows it to work.

WHat's odd is that the NNU Patcher page on wiiubrew states that on top of NNU Patcher, you must also spoof to access eshop. That's not the case it seems these days.
So basically NNU Patcher will continue to be needed. You should add this to the main post as well as a heads up.

 

[Madridi]

OOH Okay I completely understand where you're coming from. Basically updating games and Eshop both require 5.5.2, but NNU Patcher bypasses that. When I got to Eshop with DNS disabled, I get the "You must update the system" message. Running NNU Patcher allows it to work.

WHat's odd is that the NNU Patcher page on wiiubrew states that on top of NNU Patcher, you must also spoof to access eshop. That's not the case it seems these days.
So basically NNU Patcher will continue to be needed. You should add this to the main post as well as a heads up.

Correct. I was surprised you did to figure it out yourself, seeing that you have a guide about NNU patcher

I don't know about spoofing being required to use NNU patcher. The Wii U OS was not updated. I would think spoofing will make you access eshop without nnu patcher. It's also too early to tell, sometimes the first couple of days after an update, everything works well on a lower update before they update their servers to lock you out.

I won't be adding it to the guide. This guide is about blocking updates on any firmware (not just 5.5.1). Dealing with NNU patcher is part of troubles of being on a lower fw. It has no place in this guide. Or else, why would anyone ever update

It's also mentioned in one of the first replies in the first page

 

[retrofan_k]

I don't get it, where are you renaming anything? There is no rename involved :/

Edit: Ah ok I think I just understood your question. Yeah, renaming a folder doesn't work. But creating a folder with that name after that folder was deleted works. Does that answer your question?

Yeah, basically when you create a new directory, it's named "new folder" by default, so then you would have to rename it "update", since the console would not know where to look for the update files.

 

[Madridi]

Yeah, basically when you create a new directory, it's named "new folder" by default, so then you would have to rename it "update", since the console would not know where to look for the update files.

Well, until you click ok, you didn't actually create folder with the name "new folder". That's just the proposed name for it by the client.

If you click ok on the "new folder" name and then try to rename it, it won't work. It works by giving it the name "update" when creating a folder.

Hope that clarifies it

 

[vgmoose]

Wow this is pretty cool!

I'd say it's riskier than DNS obviously when first doing it, but if done successfully looks safer long term.

Also it's worth noting, that I think the FTP permissions functionality could be added to FTPiiU everywhere, right now it's just unimplemented. Might be interesting to see what happens when the permissions of the updates folder are changed over wupclient/wupclient gui. (I can't recommend anyone try it though unless they're feeling lucky).

 

[C0mm4nd_]

Wow this is pretty cool!

I'd say it's riskier than DNS obviously when first doing it, but if done successfully looks safer long term.

Also it's worth noting, that I think the FTP permissions functionality could be added to FTPiiU everywhere, right now it's just unimplemented. Might be interesting to see what happens when the permissions of the updates folder are changed over wupclient/wupclient gui. (I can't recommend anyone try it though unless they're feeling lucky).

Yeah, wupclient chmod should work (used it when I installed haxchi for the first time)

 

[Madridi]

Wow this is pretty cool!

I'd say it's riskier than DNS obviously when first doing it, but if done successfully looks safer long term.

Also it's worth noting, that I think the FTP permissions functionality could be added to FTPiiU everywhere, right now it's just unimplemented. Might be interesting to see what happens when the permissions of the updates folder are changed over wupclient/wupclient gui. (I can't recommend anyone try it though unless they're feeling lucky).

I'd think it would still not accept the changes, as I think that's how the files on the nand work. But who knows