hacks-guide / guide_wiiu-old Goto Github PK

I've decided to pull all the issues into one post that I've gathered over time. Be prepared to read a lot. Consider it a documentation, something I kept editing as time went on. The issues are the main things to tackle, the suggestions below are just optional ideas.

Text updated 8-17-17

Issues

Issue # 1 - 5.5.2 users Need Haxchi
This one was already reported recently, but I'll explain anyways. 5.5.2 users were once hopeless with no way to access Homebrew. Now that there's a new exploit, it's so unstable that it's only worth using for installing Haxchi. But the guide does not prepare the user for Haxchi installation for 5.5.2 users. If you boot into HBL on 5.5.2 without a DS VC game and Haxchi files on the SD, you've basically wasted your time. They need Homebrew Launcher, the Haxchi setup files, and a DS VC game like Brain Age (USA) ($6.99) or Dr Kawashima (EUR) (6.29£) installed on NAND. By default Eshop installs games to USB if one is inserted. Also if they have DNS setup beforehand, they won't be able to get into Eshop on 5.5.2. So the first step is to buy the DS VC game from Eshop, then the 5.5.2 exploit to install Haxchi, and finally setup the DNS.

Issue # 2 - 5.5.2 CBHC users cannot use loadiine.ovh to install Homebrew Launcher Channel
This issue is referring to the Homebrew Launcher Channel section of the guide. Basically when you have CBHC, you're gonna need HBL Channel to enter Homebrew Launcher. But using the browser to install that on 5.5.2 wouldn't be ideal since loadiine.ovh doesn't work. Instead, during the bootup process when "Autobooting" is displayed on the gamepad, they must press HOME. Then they can simply choose Homebrew Launcher from the CBHC menu and then use Wup installer GX2 to install the HBL Channel. The guide currently has users use the browser to go to loadiine.ovh but doesn't take account of 5.5.2 users. In general, it's easier to not use the browser and just use the CBHC menu to get into Homebrew Launcher. Believe it or not, you can actually launch the "DO NOT TOUCH ME!" Icon and that will also launch the CBHC menu where you can load up Homebrew Launcher just the same.

Issue # 3 - Incorrect title for one of the compatible DS VC games for Haxchi
I've noticed the abscense of Brain Age on the list of compatible games, the cheapest DS VC for USA users. Meanwhile Dr Kawashima's Brain Training, the EUR version surely is on the list. Instead there's "Big Brain Training" Which is a game that doesn't even exist. It seems like you've mixed up "Big Brain Academy", "Brain Age", and "Dr Kawashima's Brain Training" into one name. Users would be unsure what game to buy in USA and often ask while confused.

Issue # 4 - No Homebrew Launcher download in vWii guide
So the vWii guide has you download Wuphax for use on the Wii U Homebrew Launcher. But it doesn't provide a download to Homebrew Launcher itself. Not even on the Homebrew Launcher page that's linked at the start of the vWii guide. You cannot boot up Wuphax without having Homebrew Launcher on the SD card. It should be listed as a download right alongside Wuphax.

Issue # 5 - vWii guide doesn't instruct users to install the HBC Forwarder
It's been known since as far back as 2012, that when you launch Homebrew Channel it will display in 4:3 aspect ratio because vWii thinks it's a VC game. But there's a Homebrew Channel Forwarder, which is a .wad you can install which has 16:9 support. This has always been the final touch of all previous vWii guides. You can find the forwarder channel HERE
The user also needs YAWMM (Yet Another Wad Manager) to install the wad file.
It's completely up to you if you want to add another section for this in the vWii guide. Else people will have to deal with the 4:3 homebrew channel.

Ideas/Suggestions (These are optional suggestions to consider)

Idea/suggestion # 1 - Create a portal after "Get Started" to pick a firmware
There can be a portal similar to 3ds.guide which would display a pool of different firmware ranges, leading to different things depending on their firmware. Like for example, there can be a 1.0 - 5.4 section that will lead to a page showing how to update to 5.5.1 via disc update with certain games. Then a 5.5.1 section and a 5.5.2 section. The first step of the 5.5.2 section would be to get a DS VC and setup haxchi. While the 5.5.1 section would use the guide as usual.

Idea/suggestion # 2 - Add a Q&A
It would be really useful if there were an Q&A section that answers many basic questions. This can be linked on top and even at the end of the guide for the user to learn some things if they choose to.

Idea/Suggestion # 3 - Need a guide to remove the update folder to futureproof users
This can be added as an additional guide such as your A9LH to B9S guide that sits on top of the page. Deleting the system's update folder has proven to prevent any form of system updates. The update folder can be recreated at any time just like any ordinary folder. I just think it's extremely useful to create a worry free setup where the user cannot possibly mess up later on. Basically you just need Ftpiiu Everywhere and an FTP client, and CFW enabled. If using Mocha, get Diimok's Ftpiiu Everywhere and if using Haxchi/CBHC, get FIX94's release. Once connected to the wii u through FTP, the user can browser to "root/storage_mlc/sys/" and delete the update folder. I know what you're thinking, "Users are too dumb and they can't be trusted with a simple task such as deleting one empty folder". It's literally the easiest thing to do and it's super effective.

Extra notes

• WUP Installer GX2 has a random chance of crashing with a "Dsi Exception has occured" error screen. This is a very small chance of happening and it should be noted to shut down the console and try again if this occured while using WUP Installer GX2 (Or any WUP Installer really)

• It would seem that opening the browser's curtains helps the success rate of the 5.5.2 exploit.

• Another thing to note is the HIGH amount of reports of users getting FSGetMountSource Failed. There could be anoher reminder during the 5.5.2 exploit that the SD needs to be FAT32 and inserted properly. And if using a micro SD card, the adapter may be faulty. This is a common issue aside from 5.5.2 users, and it's the biggest headache for users to deal with especially when it comes to using the 5.5.2 exploit. Imagine trying over 20 times just to finally get the exploit working, but you get FSGetMountSource Failed

So earlier today someone wanted to hack vWii, and has never done any Wii U hacking. So I'm like here you go, wiiu.guide's vWii hacking guide. So I take a look at it and it doesn't explain how to get to Homebrew Launcher. It just says "Go to Homebrew Launcher".
(Also that "Patched sysnand" thing confuses me and many others. Just say with CFW enabled.You don't need CFW enabled, as Wuphax initiates iosuhax. http://prntscr.com/g4l6yn )

Basically some users go straight to vWii and your guide assumed they've hacked Wii U beforehand which isn't the case for everyone. It needs more details for it to be it's own guide without any Wii U hacking knowledge. All you gotta do is run the browser, loadiine.ovh for HBL, then run Wuphax. Which is really the only thing you gotta do on the Wii U side of things. Then again to restore mii channel.

Update: Instead of making a new issue I decided to add this here. The vWii hacking guide ALSO fails to explain how to setup DNS. Someone the other day went straight to the vWii hacking guide and during the setup, their wii u got updated to 5.5.2 automatically. They didnt know anything about DNS. vWii is a separate entity and should be treated as it's own thing.

We've had a mass amount of users get confused by the wording "Copy and merge" with every step in the file preperations section. There could be an easier way to word it so that users know what to do. Like maybe Copy and replace, or just plain "Copy the files to the SD card". This confusion leads to users missing files later on in the guide.

This can be added as an additional guide such as your A9LH to B9S guide on 3ds.guide that sits on top of the page. Deleting the system's update folder has proven to prevent any form of system updates and is more futureproof than using DNS. The update folder can be recreated at any time just like any ordinary folder. I just think it's extremely useful to create a worry free setup where the user cannot possibly mess up later on. Basically you just need Ftpiiu Everywhere and an FTP client, and CFW enabled. If using Mocha, get Diimok's Ftpiiu Everywhere and if using Haxchi/CBHC, get FIX94's release. Once connected to the wii u through FTP, the user can browser to "root/storage_mlc/sys/" and delete the update folder which has nothing in it. I know what you're thinking, "Users are too dumb and they can't be trusted with a simple task such as deleting one empty folder". It's literally the easiest thing to do and it's super effective.

How the Wii U system updates works is it downloads the update files into this update folder, before it can apply the update to the system. But since it won't have a folder to store the files, it simply will never update until that folder is back. The folder isn't recreated automatically after rebooting.

This says to use an allocation size of 32K, but this says 64KB.

Going through this and noticing a few things:

• On page "Get Started", there's no mention of placing the homebrew_launcher.elf in the wiiu/apps/homebrew_launcher directory. This is kind of important, as it makes loading the homebrew launcher from loadiine.ovh impossible.

• On the "Homebrew Launcher" page:

  Ensure that the drop down box shows “Homebrew Launcher…”, then press “Submit”

  This should note that it needs to match the version of Homebrew Launcher.elf you have on the SD card, else it fails.

• On both of the "Mocha CFW" pages, the following options aren't in the Mocha menu in v0.2 (latest):

  SEEPROM redirection: on
  OTP redirection: on
  Use syshax.xml (coldboothax): off
  

In https://wiiu.guide/get-started , the link for hid_to_vpad takes you to only the source code of the latest release.

As Matt Kimura appointed in the Discord channel, it should use instead the link https://github.com/Maschell/hid_to_vpad/releases

On the get started page near the top of the page, it suggests using 64K allocation size. Looks like you missed one. Also since the guide suggests using Guiformat, say to use 32768 allocation size since that's exactly how it shows up on the program. It often confuses users when we say 32k but that doesn't show up that way in the program. It's actually the default setting so nothing has to be changed in Guiformat after launching it.

So on the very first page on the bottom where it says 32k, make it into 32768 or "32k (32768)"

The get started page mentions to download Wup installer GX2 hombrew launcher, and channel version. However the download to both of these is a zip file with the same exact file name so it confused someone who pointed it out to me. its hard to distinguish both of them.

(The following text is just a personal opinion about wup installer gx2 channel)

As a side note, I really don't think the channel version is necessary enough to warrant having users follow it as a necessary step in the guide. I always see users become confused by it when it comes to setting it up, or even using it once installed since it requires CFW. To me its more of a CBHC thing rather than regular haxchi or mocha users. For the majority of homebrew apps you'll be launching them from homebrew launcher anyways. It's not that much more of a shortcut, plus you can always add wup installer as a button shortcut to the haxchi config which wouldn't require cfw to use. Overall the channel version of wup installer just adds extra steps, is usually confusing to newcomers, and it's not much of a difference of just launching it from HBL like everything else. Why have a shortcut for one app when there isnt a shortcut for other apps. Regular haxchi users don't always have cfw enabled so its kinda needless to launch cfw just to boot wup installer when you can just boot HBL then wup installer. If the user even needs CFW for installing content in wup installer, its pretty much pirated content such as DLC.

Here's how you hack a Wiiu:
Method A - Put files on SD, Buy DS VC game and install haxchi over it and you're done you now have an entrypoint with haxchi.
Method B - Put files on SD card and you're done, the browser is your entrypoint but not recommended.

CFW isn't something that the user always needs enabled, and it's not the ultimate end goal of setting up a wiiu. Setting up a homebrew entrypoint is the end goal rather than CFW so once you do that you are done. Wup installer gx2 channel isn't a needed step in the process imo. Which is why I'd save that only for CBHC users, people who use CFW constantly. Also a personal gripe, calling it patched sysnand as if trying to differentiate from rednand but rednand isnt used anymore. A newcomer does not know what sysnand is. End of rant

On the Homebrew Launcher channel page, it mentions a bug about Wup Installer GX2 Channel not functioning unless its installed to USB drives. This is no longer the case as its been updated to fix that bug for a long while now. The latest wup installer gx2 channel is what caused its zip contents to be named differently.

On the getting started page in the file prep section step 9, there's another common road block there that confuses users. It says "Copy config.txt to the /haxchi/ folder on your SD card"
This makes sense and all, but what confuses users is that there already exists a config.txt file and they wonder why they had to download a config.txt file. So it would be good to add a little more words to the step to indicate that they need to replace the existing file. As if the guide expects there to be an existing config.txt in the haxchi folder already.

"Copy config.txt to the /haxchi/ folder on your SD card and overwrite the existing config.txt file"

I've seen people ask about this at least more than once on reddit. A simple fix to prevent users from scratching their head.

The download to mocha only includes an elf, which is alright. But why not get the link from wiiubru just as you do for wup installer GX2.
https://www.wiiubru.com/appstore/#/app/mocha

It includes the icon and description like all other apps. Wiiubru always updates their apps and mocha hasnt been updated in close to 2 years now so there's no worry of it being outdated in the longrun.

Been seeing a lot of people ask the same question about a specific step on the guide. Here's what someone said
"So i'm on the get-started portion step 12 and it's asking me to copy the WUP_Installer_GX2 folder from the ZIP but it's not the same file name, is it ok?"

So they're referring to the wup installer gx2 channel. The folder within the zip is renamed these days and the guide mentions a slightly different name. It actually gets people stuck more often than I'd think. Thought I'd submit this to put a stop to it.

First lets talk about config.ini. Clicking on it leads to "Page not found", and right clicking it and choosing save link as leads to "file not found on server".

Next lets talk about config.txt. This one could be downloaded if you right click it and save link as. But the guide doesn't instruct this so a newcomer won't know how to save this file. Clicking on it just opens the .txt and would lead to confusion.

A solution could be to add them into zips, or maybe even one zip for both. That way it's an easy download. If you don't do the zip idea, you could add text on the side that says (Right click, save link as) to make it more clear how to obtain the file.

On the Get Started page, the install instructions for the Homebrew App Store no longer apply the the ZIP file that it's released in.

You should add a warning on the CBHC page saying that you should not install a pirated version of the DS Virtual Console Game used to install Haxchi, due to the pirated version of the DS VC game overwriting the existing Legit version and since you need CFW to launch Pirated Games, CBHC will be unable to launch causing a Brick.

Basically the fsgetMountSource Failed error occurs when the user is trying to boot into homebrew launcher but no SD card is detected. This is either because they need to turn it off and reinsert the SD card, or the SD isn't formatted to FAT32, or if they're using a micro SD card the adapter can be faulty and should try another one (Micro SD cards can be tricky because of the adapter)

So in the homebrew launcher section of the guide it mentions freezing during the browser exploit as one of the possible mishaps. But it doesn't mention the fsgetMoutnSource Failed error that users commonly get from time to time.

The same can be applied to the haxchi section. Running Haxchi to get into Homebrew Launcher would once again run into this error if their SD card isn't right.

5.5.2 Users
Same for 5.5.2 users, once they do the unstable exploit and eventually succeed and boot into Homebrew Launcher, they can be greeted with the fsgetMountSource failed error instead if their SD card isn't good. To save the user from retrying the unstable exploit just to get the same error, this error can be noted and it's causes.
Note: I added this 5.5.2 note in case the 5.5.2 hacking process becomes it's own thing.

Just a small change for the get started page. When you click on config.txt or config.ini, it brings you to the text file itself and doesn't offer to download it. I know how to download it myself, but newcomers will be confused by this and not realize that you can right click and save link as. What can be done is have a bit of text on the side that reminds users that they need to right click and save link as. Trust me, there are some really dense people that don't know how to do something as simple as that. I got the idea when someone asked about it on discord a few mins ago.

As the guide stands now, it suggests that users format their SD card with 64 kb allocation size. But that is known to cause issues when installing larger sized backups. Wup Installer GX2 will freeze during installation due to this. On the assistance channel we always recommend 32 KB allocation size, much like the 3DS. Users no longer have this issue in the end, there is no need for 64 KB allocation size for the wiiu SD card.

According to Flump on Discord and with my own experience with a user, beta 53 has a known bug for SD card when it comes to loading Wii games. What'll happen if the user uses beta 53 is that when you launch the Wii game, it will return to the home menu. As soon as you reinstall cIOS with beta 52, the games launch just fine from SD. Some users like to have a USB HDD for Wii U, while using their SD card for vWii which is a nice setup where you never have to remove anything.

It shoud be noted to use beta 52 instead if using an SD card. I'm not sure what beta 53 offers or if it affects USB HDD's. But with what Flump said, it's an issue with SD card.

See #170

Aftet you've changed u.drg.li to tiny.cc/wiiu , the steps below still mention that you need to choose a different number. But tiny.cc/wiiu chooses the best number for you so there's no numbers to choose from. Here's a screenshot of the text:

https://media.discordapp.net/attachments/337110340364009482/431903978146496554/unknown.png

"then try a different number"
"You may need to try all exploit numbers more than once before it works"

Hi, just a suggestion, but I think that a NAND backup should be recommended before installing coldboot haxchi. If I recall correctly, coldboot haxchi is the only step with any real possibility of bricking (although only due to user error) and if following the guide step by step, if someone stuffs up their coldboot haxchi install they have no NAND backup to restore to.

Whoops never mind, false alarm.

Here, the page says Hombebrew.

It was an old fix back then and it still stands as a better way to use homebrew launcher, especially for the 5.5.2 exploit. 1.3 reduces the errors users get about "homebrew_launcher.elf" missing but they do have it setup properly. It functions the same as 1.4 does once launched so it may as well be a default in the guide. Homebrew hasn't been updated in the longest time so 1.3 still stands as the most reliablle.

Relating to the last issue I made about Wup Insteller GX2 Channel no longer having a bug, some bit of text should be removed.

Step 8 says:
If you plan to install games to a USB HDD, select “USB” as the destination; if you do not plan to use a USB HDD, select “NAND” as the destination

Since Wup Installer GX2 no longer has that bug that made you install it to a USB if one existed, you could install the channel anywhere now so step 8 is irrelevant.

The link you provided for homebrew launcher is broken, I nearly didnt spot the difference til someone told me that the v in v1.3 is missing in the link. Overall the link doesn't currently work.

On the beginning of the CBHC guide it gives brick warnings. But the last one is false. It states:

You must remove all USB devices before installing or you may BRICK!

This does not actually cause the system to brick. The CBHC installer just has a small chance of freezing during installation in which the user can turn it off and try again.

I have 100% success rate if I

• wait for all screen animations to finish before doing the next step
• use dpad rather than touch screen

Example

1. load internet channel
   (wait for blue progress bar to finish)
2. tap bookmark
   (wait for blue progress bar to finish)
3. open curtains
   (wait for popup confirmation to disappear)
4. dpad down to highlight button
   (wait for highlight to move)
5. A to click button
   (wait for screen to fade)

The downloads of wup-installer and nnupatcher both include manifest.install and info.json files that, when following the guide, will ask the person following the guide if they want to overwrite these files. These files aren't needed and can either be just overwritten or deleted but the guide doesn't mention anything about them. Adding something like "If you get asked to replace the manifest.install and info.json files, replace or delete them as they aren't needed".

In the guide, it has the user install Wup Installer GX2 to the NAND. But does not mention that if the user is using a USB HDD, to install to that instead. Wup Installer GX2 will not launch if it's not installed on a USB HDD if one is connected. Other than that if no USB HDD is plugged in, it'll work from NAND.

Here's the step: https://wiiu.guide/homebrew-launcher-(channel)

Also having a channel for Wup Installer is something completely optional and shouldn't be a requirement. It even needs CFW before you can use it in which it would mostly benefit CBHC users. Non CBHC users are not gonna launch CFW just to use the Wup Installer GX2 channel. It does not take long to boot up Homebrew Launcher and Wup Installer GX2 at all.

If I'm reading this correctly, going from NAND Backup to Haxchi, the user isn't instructed to go back into the Homebrew Launcher.

Additionally, for safety, it should be specified here to open the Haxchi Installer, and not the Coldboot Haxchi Installer.

https://gbatemp.net/threads/more-stable-webhack-for-5-5-2-5-5-3-released.528757/

Tested with 5.5.1 and 5.5.3, should work with 5.5.x.

This now loads a payload.elf from sd card, and using homebrew launcher 1.4 instead of 1.3.

Important:
You need to start the exploit by clicking on a link, otherwise it'll crash.

The guide doesn't tell users who are trying to hack their Wii U that's on 5.5.2, that they need to buy a Haxchi-compatible DS VC game before they attempt to run a 5.5.2 browser exploit for the first time. The reason I would like to bring this to your attention, is because the browser exploit for 5.5.2 is extremely unstable and unreliable, therefore users won't be able to run Mocha cfw easily (as they will have great difficulty entering the Homebrew launcher through a browser exploit). So, this leaves them with having to buy a Haxchi-compatible game in order to run the Homebrew launcher with an almost 100% guaranteed launch rate. They would also need Haxchi, so they can receive signature patches and whatnot.
My proposed solution is to tell users on 5.5.2 to deactivate their DNS blocking and then buy a Haxchi compatible game from the eshop before attempting to run the Homebrew launcher through one of the 5.5.2 browser exploits. Users would also need Haxchi installer files on their sd cards. After they purchase and install the game, they would be able to install Haxchi once they get into the homebrew launcher through one of the 5.5.2 browser exploits.
I apologize if the wording is strange; I'm writing this at 12:30 in the morning.
Be sure to check out: #80 for further elaboration (more issues are also there).

Flump created another useful file for the community that we use now.
Some users go the Haxchi-less route (A few do at least) and so their only use of CFW would be Mocha. But Mocha brings the user back to the home menu after being launched which can be troublesome since the 5.5.2 browser exploit still isn't perfect. The user could also launch mii maker to get back into homebrew launcher, but there's a better pre-made mocha config that we use in the assistence channel now. With this config, it brings the user back into homebrew launcher after launching mocha. It also removes the need to ever see the config menu so you won't have to tell the user what config options to choose. This config can be provided in the file prep section which would go in SD:/wiiu/apps/mocha/

You can get the config here: https://www.dropbox.com/sh/gxkf72jia1adpyg/AADkYkaqVP-nf68Ng8Lvga6ha/CONFIGS%20FOR%20HAXCHI%20%26%20MOCHA/Mocha/config.ini?dl=0

A mention of a "payload zip" is made here; but which one of the 11 zips is it? The word "payload" doesn't appear earlier.

One of the annoying issues people tend to have with the guide when it comes to installing haxchi is that they don't realize that the guide uses its very own config.txt. So what happens is they don't follow the instructions properly on the first page of setting up files and more often then not, they end up not copying the custom config.txt that you provide. So a good fix for this would be either to include the config.txt again on the haxchi section, or remind users again that they should have the custom config.txt by now and replaced over the original. A lot of times they wonder why haxchi doesn't function the way the guide does. That is, default is CFW and holding A is homebrew launcher.
For me to leave this message here is a relief as its been a long time issue and only now I thought of adding it. The guide does double check if the users have the compatible game, so it may as well also double check if they have the proper files.

Wup installer gx2 has better interface and better folder support.

Did the URL change? I was on wiiu.hacks.guide a few minutes ago and now it's down. I'm assuming it has to do with this last commit.

On this page, the downloads for NNUPatcher, WUP Installer GX2, and Mocha are fetched from the 4TU Homebrew Appstore, and as such, the structure of the ZIPs includes an info.json and manifest.install at the root of the ZIPs. The page should be modified with this in mind (e.g. instruct to only copy the wiiu directory from the ZIP.).

The Coldboot Haxchi page explains that Coldboot Haxchi will launch CFW, and that Mocha is unnecessary, which isn't necessarily the case. A distinction should be made between the minimal CHBC CFW, and the more customizable Mocha CFW. Most importantly, this line should be changed:

Boot Mocha CFW -> Boots into Mocha CFW (no reason to use this with CBHC)

This one isn't due to recent changes to the guide, I noticed this one for quite a while and someone pointed it out.
Take a look here: http://prntscr.com/ga786t

So basically this tells the user that it can only ever be installed to a USB. What it means to say is "It must be installed to your USB device if you have one inserted, else it can be installed to NAND"

Something along those lines. Wup Installer GX2 channel works on NAND, but it must be on USB IF you have a USB.

If WUP Installer GX2 is installed as a Channel, it can only install games to USB if it has been moved to USB storage in data management. If it is installed to NAND, it will give error 199-9999.

There has been an update pushed to the Wii U, and on 5.5.2, the browser exploit was patched. This renders the guide useless.

Holding the Home Button on boot doesn't seem to take you to CBHC settings, you have to tap home while CBHC is "Booting..."

Otherwise, excellent guide!

There's been a change and tiny.cc/wiiu doesn't work anymore. We need to change the old URL's back for the browser exploit.

5.5.1 users: loadiine.ovh
5.5.2 users: u.drg.li

This change needs to be done asap so people wont get stuck at a road block.

One of our best helpers, Flump, has created a more reliable web exploit that he added to his github and also created a simple URL that users can type into their wiiu browser. The URL is tiny.cc/wiiu
It's what we use now on the assistence channel. here's how to use it:
You'd type in the URL and once the page is up, choose "Run Homebrew Launcher". It simplifies the process by providing only one choice, and giving you the best exploit automatically.

This same URL works for 5.5.1 users, it automatically detects your region and update. It'll simply redirect you to loadiine.ovh.

We've decided that the exploit is actually more reliable when you're not using any DNS blocking. So its best to enable DNS blocking after installing Haxchi. Not to mention, having the DNS enabled and buying a DS VC game will likely result in the game being stuck on "pending" in download manager (In which the fix to that is to unplug the system from the back, wait 10 seconds, replug it and the download will resume). Overall the DNS can actually prohibit the user if applied before the whole process is finished with installng Haxchi.

I'd like to suggest that you include backing up your NAND as a step.
There has already been some criticism that your guide lacks it:
https://gbatemp.net/threads/guide-hacking-the-wii-u-without-a-gamepad.469275/#post-7279701

NAND dumper:
https://gbatemp.net/threads/nand-dumper-create-full-dumps-of-the-nand.465680/
https://github.com/koolkdev/wiiu-nanddumper/releases

And some minor thing I noticed:
On the Haxchi installation page you state that

Haxchi is an exploit that allows us to launch Mocha CFW directly from the system menu without using the Homebrew Launcher.

We don't need Mocha anymore when we install Haxchi.

Keep up the great work!