Hacks Guide Wiki - User contributions [en]

3DS:Troubleshooting/WinError 234

2024-06-28T02:15:11Z

Crudefern: english be a bit weird, somewhat fixed now

When injecting MSET9 on Windows 10 and up, the script sometimes crashes with this error:

<code>OSError: [WinError 234] More data is available: '[X]:\\Nintendo 3DS/################################/\uffff\ufaff餑䠇䚅敩 ꄈ∁䬅䞘䙨䙙ꫀᰗ䙃䰃䞠䞸退ࠊꁱࠅ캙ࠄsdmc退ࠊb9'</code>

This seems to happen because of the in-beta UTF-8 support in Windows. Instructions to disable it are as follows:

# Open Settings
# Navigate to "Time and Language" --> "Language and Region" --> "Administrative language settings"
# In the new dialog that pops up, select "Change system locale...."
# Ensure that "Beta: Use Unicode UTF-8 for worldwide language support is disabled"
# Press OK.
# If prompted to restart your computer, do so.

The injection should now work properly.

User:Botman/3ds Assistance Regular Guide

2024-04-12T00:21:13Z

Crudefern: Oi botman here’s the edit (added broken NAND as a reason to use a emuNAND)

{{#approvable_by: users = Botman}}
Welcome to the 3DS assistance guide! If you're reading this, you most likely want to be better at helping in the Nintendo Homebrew Discord, but don't know where to start. This guide should serve as a helpful glossary and FAQ for those purposes.

== General Advice ==
* Don't try to solve an issue if you have no idea how to fix it.
** Having only enough info to make educated guesses is fine, you're not expected to instantly find a solution. That's sometimes how it works even for the helpers.
* You don't have to keep helping if someone's getting on your nerves. There will always be other people to find that person's issue.
* Don't assist people in DMs. It is against the server rules, as we cannot monitor it.
* Don’t expect anything for helping out. Ideally, the helping should be its own reward anyway.
** That isn't an excuse to get burnt out, though. There's a difference between being selfless and being self-destructive.

== Difference between software, firmware and hardware ==
* Hardware is the console's physical parts, such as the RAM and CPU. This also includes things like the n3DS' NFC touchpoint.
* Software is the 'encoded instructions' that cause the hardware to do specific things. This includes games, homebrew apps, system apps, etc.
* Firmware is any software that runs directly on top of the hardware, such as its operating system. Despite its name, 'custom firmware' usually only patches the existing firmware rather than being an entirely new one.

== Basic info on SOAP transfers ==
All information on SOAP transfers can be found under [[3DS:cleaninty|cleaninty's page.]]

You almost always need donor files from an unusable console to do SOAP transfers, so if you need a SOAP for your console, don't try to do it yourself. Ask on the Nintendo Homebrew Discord, and one of the people with a large number of donors will be able to help.

== Command list ==
[https://docs.google.com/spreadsheets/d/1Bz-8qddZqubr7toWiW402C-WWp3R_RpsX1njt1rO46M/edit?usp=sharing This Google Doc] contains a list of every single command relating to 3ds assistance.

== Useful Keywords ==
Below is a list of keywords that are nice to know.

sysNAND: The console's internal file storage. CFW can be safely installed to this without any notable risks.

emuNAND: Short for emulated NAND. Used to be the way CFW was separated from the "stock" NAND, but this is no longer required. emuNANDs' only practical uses now are for Korean games' fonts or a broken NAND chip.
* redNAND: An improved type of emuNAND that doesn't take up as much space on the SD. Otherwise identical.

CTR: Short for Citrus and/or Centrair, the code names for the 3DS.
* Examples include: [[3DS:ctrcheck|'''ctr'''check]], [[3dsguide:ctrtransfer|'''ctr'''transfer]] and the '''CTR'''NAND.

NTR: Short for Nitro, the code name for the DS.
* Examples include: [[3DS:ntrboot|'''ntr'''boot]] and '''NTR''' CFW.

TWL: short for Twilight, the code name for the DSi.
* Examples include: '''TWL'''Fix, '''TW'''i'''L'''ightMenu++, and the '''TWL'''NAND.

== Useful Programs ==
The following are apps or scripts that are commonly used or have extremely useful functionality for damaged consoles.
 Apps that are packaged with [[3dsguide:finalizing-setup|Finalizing Setup]] will be listed first.

[[3DS:Anemone3DS|Anemone3DS]]: A theme and splash screen manager.

[[Checkpoint]]: A save file and cheat manager.

[[3DS:FBI|FBI]]: A file explorer and title manager with significantly less safety checks than GodMode9.

[[3DS:GodMode9|GodMode9]]: The Swiss Army Knife of the 3DS world. Mainly used as a file explorer, game dumper, title manager, and to create/restore NAND backups.

[[3DS:Luma3DS|Luma3DS]]: The sole remaining CFW for the 3DS. Has [[3DS:Luma3DS/Configuration|several]] useful features and a [[3DS:Luma3DS/Rosalina|built-in menu]].

[[3DS:Universal-Updater|Universal-Updater]]: Homebrew browser and updater.

[[3DS:FTP|FTPD]]: used to transfer files from your 3ds to your PC wirelessly.

----

[[3DS:faketik|faketik]]: Creates new tickets for installed apps that lost theirs. Doesn't work if the apps themselves were deleted.

[[3DS:rverse|rverse]]: A third-party revival of Miiverse.

[[3DS:rehid|rehid]]: Allows remapping of the buttons and touchscreen based on specific inputs, and can be configured to run differently based on what game is being played.

[[3DS:TWiLightMenu|TWiLightMenu++]]: A DSi Menu upgrade/replacement, mainly used on the 3DS to play dumps of NDS games [[3DS:DS|directly from the SD card.]]

[[3DS:TWPatch|TWPatch]]: Enhances TWiLightMenu++'s visual capabilities, most notably by allowing for widescreen support.

[[3DS:ctrcheck|ctrcheck]]: A GodMode9 script that checks the NAND for damage. Cannot detect most hardware issues.

[[3DS:Hardware test|3ds_hw_test]]: A <code>.firm</code> payload that checks for RAM issues.

== Common troubleshooting situations ==
Some of the problems here are not actually "common" per se, but are instead included because they have a common cause and well-known solution.

{{info|1=Above all else, always remember to check [[3DS:ERR]] if you don't know what an error means - one of those pages is relatively likely to have it. If it doesn't and the error is either a stock error code or an ErrDisp, try using <code>.err</code> through Kurisu.}}
* If the SD card is the problem, it may be worth it to reinsert the SD card to see if that works.
* If an error is occurring on boot and there is no known cause, see whether it keeps happening (including whether the error changes) if the SD is taken out. If it does, the issue is with the NAND.
* If an error with the code <code>0xd900458b</code> is happening when opening a game, use [[3DS:FCG]].
* If someone has Parental Controls enabled and wants to remove it, direct them to [[udb:3ds/3ds-parentalunlock|3DS-ParentalUnlock]] if they have CFW, or [https://mkey.eiphax.tech mkey.eiphax.tech] if they don't. (not salthax - it was never updated to work on the latest system version).
* If an <code>0xC8804478</code> error happens when opening anything that uses DS mode (a fast way to test is by opening Download Play -> Nintendo DS), link the <code>.twlfix</code> command (which is itself a redirect to [[3DS:TWLFix]]).
* If a helpee has more than 1 ID0, tell them to do [[3DS:MID0]].
* If any '''one''' of the following things is happening to a console, link [[3DS:Hardware test|the hardware test]] and have the helpee send the contents of <code>hwtest.log</code> after it finishes. This will test the RAM for errors.
*# The console repeatedly fails to boot and the notification LED is either [[3DS:boot9strap#LED_Status_Codes|red or magenta]] when it fails.
*# The console randomly and inconsistently crashes, regardless of whether the SD is inserted or not.
*# GodMode9 crashes.

== Info on Older Setups ==
[[3DS:boot9strap|B9S]] is the newest of a long list of homebrew/CFW setups. Below is a list of all the mainstream older setups, in mostly chronological order, and instructions on how to upgrade from them to B9S.

{{info|text=Setups marked with an (E) use an [[3DS:EmuNAND and RedNAND|emuNAND]]. emuNANDs are unnecessary under boot9strap, as they were only used on these setups because modifying the sysNAND with homebrew was considered unsafe at the time. 

If you are upgrading from one of these setups to B9S, it is advised to [[3ds:Move EmuNAND|move the emuNAND]] into your sysNAND.}}

{{info|text=If a setup is marked as N/A, it only means there's no easier way to migrate to boot9strap. If you were using a setup marked with N/A, you can still go to [[3dsguide:index|our guide to 3DS custom firmware]] and insert your system version to install CFW normally.}}

# '''Userland''': Any exploit that allowed non-persistent Homebrew Launcher access, such as by running a modified save file from a cartridge game.
#* Upgrade to boot9strap: Depends on your system version. If 11.15.0 or below, follow [[3ds:Alternate Exploits/Installing boot9strap (uloader)|uloader]]; if 11.16.0 or above, follow [[3ds:Alternate Exploits/Installing boot9strap (nimdsphax)|nimdsphax]].
# '''Gateway''' (E): Gateway's first attempt to take control of the 3DS homebrew scene. Uses a old/downgraded sysNAND combined with one of multiple exploits to load the Gateway Menu, from which an emuNAND on a newer version (known as Gateway Mode) is used for most homebrew functionality.
#* Upgrade to boot9strap: [[3dsguide:ntrboot|Flash NTRBoot to the blue cartridge and install boot9strap via NTRBoot.]]
# '''Sky3DS''': Gateway's second attempt to take control. A piracy-focused [[3DS:Flashcarts|flashcart]] that spoofs a legitimate game, letting it run 3DS games directly from the HOME Menu on any firmware version without installing an exploit. Has an enormous ban risk unless you add a file that can only be extracted via CFW, and is thus obsolete.
#* Upgrade to boot9strap: N/A
# '''Stargate''': Gateway’s last attempt to take control. A piracy-focused flashcart that can run 3DS games the same way Sky3DS does, but also can run DS games and ntrboot. Has the same ban risk as Sky3DS when running 3DS games.
#* Upgrade to boot9strap: Usually N/A, but if you used their Easy CFW Mode pack, wipe the console's SD card and then follow [[3dsguide:Updating B9S|Updating B9S]].
# '''Menuhax''' (E): A set of secondary exploits that all triggered on Home Menu startup, allowed HBL access when opening Home Menu settings, and used a emuNAND. It was sometimes also used as an entrypoint for Gateway Mode.
#* Upgrade to boot9strap: Follow [[3ds:Migrate from menuhax|Migrate from menuhax]].
# '''[[3DS:arm9loaderhax|A9LH (arm9loaderhax)]]''': The direct predecessor to boot9strap - also a coldboot CFW, but with reduced functionality and safety because of how it's implemented. Supports Luma3DS versions up to 7.0.5.
#* Upgrade to boot9strap: Follow [[3dsguide:A9LH To B9S|A9LH to B9S]].
# '''B9S 1.0-1.3''': Just older versions of boot9strap. Very few practical differences aside from the older versions not having [[3DS:boot9strap#LED Status Codes|LED status codes]].
#* Upgrade to (latest) boot9strap: Follow [[3dsguide:Updating B9S|Updating B9S]]
#'''[[3DS:Fastboot3DS|FB3DS (fastboot3ds)]]''': An alternate bootloader option to B9S, trading out LED status codes for an interactive on-boot menu, FCRAM boot (useful for {{GitHub|SUOlivia/That-Shortcut-Thingy|That-Shortcut-Thingy}}), a chainloader with more flexibility and power than [[3DS:Luma3DS|Luma3DS]], and a system for backups of critical system files. Mainly useful for power users.
#* Return to boot9strap: Follow [[3dsguide:Updating B9S|Updating B9S]].

Wii U:How to remove NNIDs

2024-04-08T19:41:08Z

Crudefern: Fix the FTPiiU link and capitalization on FTPiiU

If you have recently bought a Wii U and find yourself with an account or two that is password locked, this is how you can delete them without acquiring the passcode.

==Instructions==

# Download the latest release of [https://github.com/wiiu-env/ftpiiu_plugin/releases FTPiiU]
# Extract the contents of the zip to the root of your SD card
# Download an FTP client of your choice(Filezilla, WinSCP, .etc)
# Insert the SD card back into your Wii U and boot up Aroma
# Open the plugin menu, navigate to the FTPiiU tab and your IP should show.
#* Take note of this, you will need it later
#Set system files access to true.
#Boot up your preferred FTP client.
#* Your console and PC must be on the same network.
# Input your IP address, leaving the port blank, then hit connect.
#You should see a list of directories.
#Navigate to <code/>storage_mlc/usr/save/system/act</code> and There should be either one or multiple 800000X folders. These are the accounts.
# Open one and you will find an account.dat file. drag this file to your desktop and open it in notepad as this will tell you whose account it belongs to.
#Once you've figured it out, delete the entire folder or folders.
#Disconnect the client and then shut down the console(do not force power off).
#Boot up the Wii U again, and if done successfully, the account(s) should be gone.

Wii:Nintendont

2023-10-09T02:28:59Z

Crudefern: Fix some link embeds

{{Infobox homebrew
| developers = FIX94
| forwii = 1
| image =
| imagealt = Nintendont Logo
| imagesize = 256px
| version = 4.431+
| releasedate = 2016-12-18
| website = https://oscwii.org/library/app/nintendont oscwii.org/library/app/nintendont
| github = FIX94/Nintendont
}}

Nintendont is a Wii-mode homebrew application that can be used to play GameCube games, as well as Triforce arcade dumps. Nintendont is an interesting app in that it is like a hybrid between an emulator and a virtual machine - while still running GameCube games near exactly at native quality and performance. Further info can be read [https://gbatemp.net/threads/nintendont.349258/ here].

{{info|text=To play games, you are advised to use a large SD card or an external hard drive, flash drives are very sporadic in functionality. See [https://wii.hacks.guide/faq#storage-device-faq storage FAQ].}}

{{info|text=Make sure your storage device is formatted as FAT32. Do not format it to other file systems like NTFS, exFAT, or WBFS.}}

__TOC__

=== Requirements ===

* A modded Wii
* An SD card or USB device
* [https://oscwii.org/library/app/Nintendont Nintendont]

=== Installation ===

# Download Nintendont and extract it to the root of your SD card or USB drive.
# Insert your SD card or USB device into your Wii, and launch Nintendont from the Homebrew Channel.

=== Quick Start Guide ===

==== Key Features ====

* You can use various input devices to play GameCube games. These include GameCube controllers (even via a USB adapter), Wii Remote + Nunchuk, Classic Controllers, Wii U Pro Controllers, DK Bongos, USB HID controllers, and potentially more. Game Boy Advance consoles are supported on backward compatible systems if native control is enabled.
* Games can be forced to progressive and widescreen output, similar to Dolphin's widescreen hack.
* Nintendont has support for virtual memory cards that are saved to an external storage device, from sizes of 51 blocks up to 1019 blocks. Despite this, the recommended max size is 251 blocks per virtual card for maximum compatibility.
* Backward compatible systems can use retail game discs and/or real memory cards alongside emulated controllers, broadband adapter, memory cards, etc.
* Broadband adapter and ASCII Keyboard Controller emulation with standard USB ethernet/wifi and USB keyboards. These can be used with custom server patches for online multiplayer in certain games. Ethernet is recommended for LAN multiplayer.
* Nintendont can be leveraged in either [https://wii.hacks.guide/usb-loaders#wiiflow-lite WiiFlow Lite] or [https://wii.hacks.guide/wii-loaders#usb-loader-gx USB Loader GX] for the loading of GameCube games.
* Triforce arcade games are supported.

==== User Interface ====

[[File:Nintendont-ui.png]]

Nintendont uses a user interface that is mainly controllable and navigable using a controller.

==== Properly Launching Games ====

Games in Nintendont have to be launched from an external device with a specific folder structure. USB storage and SD cards are supported, but USB is recommended for faster speeds.

Single-disc games can simply be placed inside the games folder:

* <code>device:/games/(game name).iso</code>

The expected structure for multi-disc games is as follows:

* <code>device:/games/(game name)/game.iso</code>
* <code>device:/games/(game name)/disc2.iso</code> (so on and so forth)

Here is an example using The Legend of Zelda: The Wind Waker on a USB hard drive:
* <code>USB:/games/The Legend of Zelda: The Wind Waker [GZLE01].iso</code>

==== BIOS Setup ====

You can use an original GameCube BIOS in Nintendont if you have legally obtained one.

# Rename the BIOS file <code>iplusa.bin</code>/<code>ipljap.bin</code>/<code>iplpal.bin</code> based on its region.
# Copy it to the root of the storage device where Nintendont is installed on.
# Go into Nintendont settings and verify that `Load IPL` is turned ON.

==== Using a HID USB controller with Nintendont ====

By default, Nintendont selects a controller configuration from an internal list of already mapped controllers. If yours does not automatically work, make sure to check the supported controller list in the article at the top of the page. If you still want to check anyway, you can use [https://oscwii.org/library/app/HIDTest HIDTest] to determine whether or not your controller will be detected and work with Nintendont.

==== Button combinations for Nintendont in-game ====

Restart: Resets the game and returns to game's title screen.

Shutdown: Exits Nintendont and returns to the loader.

Some games may have native button combinations to reset.

'''GameCube Controller:'''

* Restart: R+Z+Start
* Shutdown: R+Z+B+Down (D-pad)

'''Wiimote + Nunchuck:'''

* Shutdown: HOME button on the Wiimote

'''USB HID controller or adapter:'''

You can define the Shutdown button's combination yourself.

The Power button is defined in the controller.ini or in the correct controllers/PID_VID.ini file used by your gamepad.

Most commonly used combo with default HID settings:

* Shutdown: L+R+Z+Start

Wii

2023-10-05T14:25:21Z

Crudefern: Fix latest system version

{{Page WIP}}{{Infobox console|image=Wii-Console.png|caption=An RVL-001 revision Nintendo Wii and Wii Remote|aka={{plainlist|
* Revolution/RVL (codename)
}}|systems={{plainlist|
* Nintendo Wii
* Nintendo Wii Family Edition
* Nintendo Wii mini
}}|version={{SystemVersion|rvl}}|guide=[[wiiguide:index|wii.hacks.guide]]|namespace=Wii:|title=Nintendo Wii|imagesize=300px|recommended=Varies by console}}

The {{Iw|wikipedia|Nintendo Wii}} is a home video game console released by Nintendo in 2006. In its release lifecycle, three different console revisions were produced; the original RVL-001 model with GameCube ports, the Family Edition RVL-101 model without GameCube ports, and the mini RVL-201 model with a complete internal revision. All Wii revisions run the same system software, however internal differences and region differences could lead to accidental bricks if not paying attention to correct homebrew methods. The console was succeeded by the [[Wii U]] in 2012 and is now discontinued.
{| style="table-layout: fixed;"
| style="vertical-align: top; width: 50%;" class="collapse-on-mobile" |
== Getting started ==
{{Warning|text=Never use video guides as those can get outdated quickly and can contain mistakes or modified files.}}
The recommended setup route varies by console based on differences by revision.

Instructions on setting up homebrew and custom firmware on your console can be found on wii.hacks.guide.

<div class="center">{{Clickable button 2|wiiguide:index|Go to Wii Hacks Guide|class=mw-ui-progressive}}
| style="vertical-align: top; width: 50%;" class="collapse-on-mobile" |
== Use homebrew ==
Looking for things to do with your newly homebrewed console? Here are some ideas:

* Turn your Wii into a media center
* Install a USB loader to launch backups from an external storage device
* Restore online functionality
* Patch disc contents to load game mods

<div class="center">{{Clickable button 2|Wii:Things to do|See the full list of things to do|class=mw-ui-progressive}}
|}

==Get help==
Having an issue setting up homebrew, or using it? Maybe your console is doing something weird?

First, try searching for your issue. If you cannot find the right information or don't understand it, you can [[Get support|'''ask someone for help''']].<inputbox>
type=search
placeholder=Enter a description of your issue...
namespaces=Main**,Wii**
width=70
</inputbox>

3DS:Game plugins/3GX

2023-08-01T18:42:26Z

Crudefern: Update luma3ds links due to 3GX fork being merged

{{shortcut|3DS:3GX|3GX}}
{{Page WIP|notes=
*Usage notes (if any) are missing.
}}
The 3GX file format is an evolution of the old PLG file format that is used in newer game plugins. You can run them by using a fork of Luma3DS that has a plugin loader built-in.

== Installation ==

<tabber>
|-|Universal Updater=
==== What you need ====

* [[3DS:Universal-Updater|Universal-Updater]]

==== Installation ====

# Search for <code>Luma3DS</code> in Universal Updater, and download the <code>boot.firm</code> file
# Reboot your system
# In the Luma configuration screen, select any options you need, then press START
#* Hint: If you don't know what the options are, you don't need any

|-|Manually=

==== What you need ====

* [https://github.com/LumaTeam/Luma3DS/releases/latest The latest Luma3DS with 3GX support]

==== Installation ====

* Copy the <code>boot.firm</code> from the 3GX loader fork of Luma to the root of the SD card, replacing the <code>boot.firm</code> already there
* Insert the SD card into your system and power it on
* On the Luma Configuration screen, enable any options that you need, then press Start
** Hint: If you don't know what the options are, you don't need them
</tabber>
== Using 3GX plugins ==

=== Plugin location ===
The 3GX plugin loader will look for plugins in the <code>luma</code> -> <code>plugins</code> directory. Each plugin must be inside a folder named with the game's Title ID. Inside the folder, place your <code>.3gx</code> file.
* You can get the game's title ID from [http://3dsdb.com/ here] (cartridges), [https://hax0kartik.github.io/3dsdb/ here] (digital games), or from the <code>FBI -> Titles</code> menu. For example, Taiko no Tatsujin: Dokodon! Mystery Adventure's title ID is <code>0004000000190E00</code>, so if you wanted to use a plugin for that game, you'd create a folder named <code>0004000000190E00</code>
* The creator of the plugin may have already created a folder with the correct name for you, in which case you can just copy the title ID folder from the plugin's zip/rar/7z archive to the <code>plugins</code> folder
* If you want the plugin to run for ''all'' games (for example, for the CTRPluginFramework blank plugin), rename the plugin to <code>default.3gx</code> and just leave it in the <code>plugins</code> folder

An example directory for a plugin affecting one game would be <code>luma</code> -> <code>plugins</code> -> <code>0004000000190E00</code> -> <code>plugin.3gx</code>.

An example directory for a plugin affecting all games would be <code>luma</code> -> <code>plugins</code> -> <code>default.3gx</code>.

=== Using 3GX plugins ===

# Open the Rosalina menu ([Left Shoulder] + [Down D-Pad] + [Select] by default)
# Scroll down to the plugin loader option, then press (A) to enable it
# Exit the Rosalina menu by pressing (B) a couple of times
# Open your game of choice
#* The screen should flash another color to indicate that the plugin has successfully loaded
# Look at the information on the plugin's webpage/README for usage instructions - usage will differ for each plugin

=== Usage notes ===
WIP