Hacks Guide Wiki - User contributions [en]

Template:SystemVersion

2026-03-17T13:08:50Z

Doge 2: Bump Switch firmware version to 22.0.0

<includeonly>{{#switch: {{{1}}}
| ctr = 11.17.0-50
| wup = 5.5.6
| hac = 22.0.0
| rvl = 4.3
| {{Error|1=Incorrect console type given to {{tl|SystemVersion}}. Correct ones are <code>ctr</code>, <code>wup</code>, <code>hac</code>, and <code>rvl</code>. Given: <code>{{{1}}}</code>}}{{#if: {{{nocat|}}} |  | [[Category:Pages with incorrect template use]] }}
}}</includeonly><noinclude>{{Documentation}}
</noinclude>

3DS:PKSM

2025-04-20T19:13:55Z

Doge 2: add universal-updater installation instructions

{{Page WIP|notes=
*Needs a feature list. Maybe this could just be copied from the github readme?
*Links to various parts of the github wiki would probably be helpful: https://github.com/FlagBrew/PKSM/wiki}}{{Infobox homebrew
| developers = FlagBrew
| for3ds = 1
| image = PKSM-Banner.png
| imagealt = PKSM banner on the Home Menu
| version = 10.1.1
| releasedate = 2024-4-3
| github = FlagBrew/PKSM
| githubtag = latest
}}
'''PKSM''' is a save manager and editor for Pokémon games. It supports generations 1 to 8.

== Features ==

* Generate Pokemon
* Legalize Pokemon
* Has a built in bank to move Pokemon from different generations
* Has an item editor

== Installation ==

<tabber>

|-|Nintendo 3DS - Universal-Updater=
<span>
# Power on your console
# Launch '''Universal-Updater''' from the HOME Menu, or from the Homebrew Launcher
# Select the magnifying glass on the bottom screen, then search for '''PKSM'''
# Press {{B|A}} while hovering over '''PKSM''' from the list of homebrew
# Choose <code>PKSM.cia</code> to install to the HOME Menu, or <code>PKSM.3dsx</code> to install to the Homebrew Launcher
# Wait until the app finishes installing
# Exit '''Universal-Updater'''
</span>

|-|Install with FBI=

{{FBI QR code
| name1 = CIA
| url1 = https://github.com/FlagBrew/PKSM/releases/latest/download/PKSM.cia
| name2 = 3DSX
| url2 = https://github.com/FlagBrew/PKSM/releases/latest/download/PKSM.3dsx
}}

|-|Manually as 3DSX=

<span>
* {{GitHub|FlagBrew/PKSM/releases/latest|Download the latest release}}
* Copy <code>PKSM.3dsx</code> to the <code>/3ds/</code> folder on your SD card
</span>

|-|Manually as CIA=

<p>
{{GitHub|FlagBrew/Checkpoint/releases/latest|Download the latest release}} and install it using a CIA installer such as [[3DS:FBI|FBI]].
</p>

</tabber>

== Usage ==

The [https://github.com/FlagBrew/PKSM/wiki PKSM wiki] documents how to use the application.

== Setting up missing saves ==
If your title is a 3DS game or official Virtual Console title, then your game should show up by default. If not, then some additional setup is required for PKSM to use your save. First, ensure that you have made an initial save in the missing title.

<tabber>

|-|Installed title(VC Inject)=

<span>
# Launch [[3DS:FBI|FBI]]
#* If you dont have [[3DS:FBI|FBI]] installed, do so now
# Select <code>Titles</code> and navigate to your missing game
# On the top screen you should see <code>TitleID:<16 digit number></code>, write this number down
# Close [[3DS:FBI|FBI]] and Launch PKSM
# Press {{B|X}} to open settings and select <code>Misc.</code> -> <code>Title IDs</code>
#* Note: some of settings can only be navigated with the touch screen
# Select the game you wish to add and enter <code>0x(16 digit TitleID)</code> in the text box
# Tap OK and exit out of settings
# Tap on "VC Games" and your title should now be present
#* If your save does not appear in the menu, restart PKSM
</span>

|-|ROM saves=

<span>
# Launch PKSM
# Press {{B|X}} to open settings and select <code>Misc.</code> -> <code>Extra Saves</code>
#* Note: some of settings can only be navigated with the touch screen
# Highlight your game from the menu, press {{B|A}}, then press {{B|A}} again on your game to add a save
# Navigate to your game save and select it, you should now see your game save on the list
# Exit out of settings and press {{B|Y}} to switch to absent games, your save should now be present
#* If your save does not appear in the menu, restart PKSM
</span>
</tabber>

[[Category:Pokémon]]
{{Pokémon}}
{{Short description|Pokémon homebrew save manager and editor for generations 1 to 8}}

3DS:Minecraft: New Nintendo 3DS Edition

2025-04-08T23:30:27Z

Doge 2: remove "Minecraft 3DS Community"

'''Minecraft: New Nintendo 3DS Edition''' is a sandbox game for the New Nintendo 3DS.

== Game-specific quirks ==

=== Extra Data only ===
{{3DS extdata only}}

== Mods ==

{| class="wikitable"
! Mod
! Features
! Notes
|-
| [https://www.minecraft3ds.org/mods/worlds/skyblock_1 Skyblock]
| Skyblock is a survival map where you expand your own world with limited resources
|}

== Guides ==

*[[/Custom Skins]]
*[[/Import Worlds]]
== Other resources ==

*[[wikipedia:Minecraft: New Nintendo 3DS Edition|Wikipedia article]]
*[[tcrf:Minecraft: New Nintendo 3DS Edition|TCRF page]]
*[https://gamebanana.com/games/6862 Minecraft: New Nintendo 3DS Edition GameBanana page]

[[Category:Nintendo 3DS games]]

Checkpoint

2025-04-01T19:38:12Z

Doge 2: bump both to 3.8.2

{{Infobox homebrew
| title = Checkpoint (Nintendo Switch)
| forwii = 0
| developers = FlagBrew
| for3ds = 0
| forwiiu = 0
| forswitch = 1
| image = Checkpoint-Banner.png
| imagealt = Checkpoint banner on the Home Menu
| version = 3.8.2
| releasedate = 2025-04-01
| github = FlagBrew/Checkpoint
| githubtag = v3.8.2
| forwindows = 0
| formac = 0
| forlinux = 0
| forjava = 0
}}{{Infobox homebrew
| title = Checkpoint (Nintendo 3DS)
| forswitch = 0
| forwii = 0
| developers = FlagBrew
| for3ds = 1
| forwiiu = 0
| image = Checkpoint-Banner.png
| imagealt = Checkpoint banner on the Home Menu
| version = 3.8.2
| releasedate = 2025-04-01
| github = FlagBrew/Checkpoint
| githubtag = v3.8.2
| forwindows = 0
| formac = 0
| forlinux = 0
| forjava = 0
}}

'''Checkpoint''' is a save manager for the Nintendo 3DS and Nintendo Switch.

== Features ==
<tabber>

|-|Nintendo 3DS=
<span>
* Exporting and importing saves, both 3DS and DS titles
* Creation of cheat files for various games
* Modifying Play Coin count
</span>
|-|Nintendo Switch=
<span>
* Exporting and importing saves
* Creation of cheat files for various games
</span>
</tabber>
== Installation ==

Checkpoint is installed as part of [[3dsguide:finalizing-setup|Finalizing Setup]] on [[3dsguide:get-started|our custom firmware installation guide]] for Nintendo 3DS consoles.

If you do not already have Checkpoint from Finalizing Setup (or have a Nintendo Switch), the possible methods to install it are as follows:

<tabber>
|-|Nintendo 3DS - FBI=

{{FBI QR code
| name1 = CIA
| url1 = https://github.com/FlagBrew/Checkpoint/releases/download/v3.7.4/Checkpoint.cia
| name2 = 3DSX
| url2 = https://github.com/FlagBrew/Checkpoint/releases/download/v3.7.4/Checkpoint.3dsx
}}

|-|Nintendo 3DS - Manually=
==== 3DSX (Homebrew Launcher) ====
<span>
# {{GitHub|BernardoGiordano/Checkpoint/releases/tag/v3.7.4|Download the latest Checkpoint.3dsx from the GitHub repository}}.
# Copy <code>Checkpoint.3dsx</code> to the <code>/3ds/</code> folder on your SD card.
# Open The Homebrew Launcher.
# Launch Checkpoint.
</span>

==== CIA (HOME Menu) ====
<span>
# {{GitHub|BernardoGiordano/Checkpoint/releases/tag/v3.7.4|Download the latest Checkpoint.cia from the GitHub repository}}.
# Install it using a CIA installer such as [[3DS:FBI|FBI]].
# Unwrap the newly installed app on your HOME menu, and open it.
</span>

|-| Nintendo Switch - Manually=
==== NRO (Homebrew Launcher) ====
<span>
# {{GitHub|BernardoGiordano/Checkpoint/releases/latest|Download the latest Checkpoint.nro from the GitHub repository}}.
# Copy <code>Checkpoint.nro</code> to the <code>/switch/</code> folder on your SD card.
# Open The Homebrew Menu and launch Checkpoint.
</span>
</tabber>
==Guides==

*[[3DS:Export saves]]

{{Short description|Save manager}}

3DS:Mario Kart 7/CTGP-7

2025-04-01T19:36:34Z

Doge 2: version bump to v1.5.31

{{#approvable_by: users = PabloMK7
{{outdated|notes=
* Course list is outdated for 1.5.X.}}
{{Infobox game mod
| image = CTGP-7-banner.png
| imagesize = 256px
| developers = PabloMK7, Fishguy ([https://github.com/PabloMK7/CTGP-7updates/blob/master/credits.txt List of credits])
| version = 1.5.31
| releasedate = 2025-04-01 
| website = https://ctgp-7.github.io ctgp-7.github.io
| releaseurl = https://ctgp7.page.link/cia_downloader
| universaldb = 3ds/ctgp-7-downloader
}}
'''CTGP-7''' is a mod pack for Mario Kart 7, featuring custom race tracks, playable characters, items, and other additions.

== Installation ==

=== Universal-Updater ===
[[udb:3ds/ctgp-7-downloader|CTGP-7]] is available on Universal-DB.

=== Manually ===

{{Info|text=CTGP-7 also provides official installation instructions as a {{GitHub|PabloMK7/CTGP-7updates/blob/master/CTGP-7_Intallation_Guide_EN.pdf|PDF}} or [https://www.youtube.com/watch?v=OV9ZmrHOy4c YouTube video].}}

<tabber>

|-|Using FBI=
CTGP-7 has a downloader app to install the modpack for you, which can be opened from either the HOME Menu or the Homebrew Launcher.

{{FBI QR code
| name1 = CIA
| url1 = https://ctgp7.page.link/cia_downloader
| name2 = 3DSX
| url2 = https://ctgp7.page.link/3dsx_downloader
}}

|-|Using a Computer=
# Download the latest CTGP-7 installer for your computer's operating system from the mod's [https://gamebanana.com/mods/50221 GameBanana page]
#* Native installers are only available for Windows and Ubuntu. The Python-based installer might be required instead on other operating systems, but will also need an up-to-date Python installation and the dependencies listed in the README file.
# Insert your console's SD card into your computer
#* Make sure the SD card is accessible before continuing
# Run the CTGP-7 installer you downloaded
# Choose the location of your console's SD card if it wasn't detected automatically
# Press the install button and wait for it to finish
# Eject the SD card and reinsert it into your console
# Launch FBI
# Navigate to <code>SD:/CTGP-7/cia/</code>
# Select the <code>CTGP-7.cia</code> file
# Select "Install CIA"
# Press {{B|A}} to confirm
# Wait for the installation to finish
# Return to the HOME Menu and close FBI

{{Success|CTGP-7 is now installed!}}

</tabber>

== Courses ==
{{Section WIP|notes=Screenshots are taken during the pre-game intro.}}
In addition to the original courses included in Mario Kart 7, CTGP-7 adds 18 new cups.
{| class="wikitable" style="text-align: center"
!Cup
!Course 1
!Course 2
!Course 3
!Course 4
|-
!Bell Cup
|{{CTGP-7 Course|Concord Town}}
|{{CTGP-7 Course|N64|Mario Raceway}}
|{{CTGP-7 Course|Galvarny Falls}}
|{{CTGP-7 Course|GBA|Sky Garden}}
|-
!Acorn Cup
|{{CTGP-7 Course|Autumn Forest}}
|{{CTGP-7 Course|GBA|Riverside Park}}
|{{CTGP-7 Course|SNES|Mario Circuit 1}}
|{{CTGP-7 Course|GBA|Bowser Castle 3}}
|-
!Cloud Cup
|{{CTGP-7 Course|Evergreen Crossing}}
|{{CTGP-7 Course|N64|Moo Moo Farm}}
|{{CTGP-7 Course|Archipelago Avenue}}
|{{CTGP-7 Course|N64|Frappe Snowland}}
|-
!Boo Cup
|{{CTGP-7 Course|Banshee Boardwalk 2}}
|{{CTGP-7 Course|Elemental Cave}}
|{{CTGP-7 Course|SNES|Ghost Valley 2}}
|{{CTGP-7 Course|DS|Cheep Cheep Beach}}
|-
!Spring Cup
|{{CTGP-7 Course|DS|Tick Tock Clock}}
|{{CTGP-7 Course|Melody Sanctum}}
|{{CTGP-7 Course|DS|Desert Hills}}
|{{CTGP-7 Course|Castle Of Time}}
|-
!Egg Cup
|{{CTGP-7 Course|DS|Yoshi Falls}}
|{{CTGP-7 Course|N64|Choco Mountain}}
|{{CTGP-7 Course|DS|Shroom Ridge}}
|{{CTGP-7 Course|CTR Crash Cove}}
|-
!Bullet Cup
|{{CTGP-7 Course|CTR Cortex Castle}}
|{{CTGP-7 Course|Revo Circuit}}
|{{CTGP-7 Course|SNES|Choco Island 2}}
|{{CTGP-7 Course|Star Slope}}
|-
!Blooper Cup
|{{CTGP-7 Course|Sandcastle Park}}
|{{CTGP-7 Course|DS|Mario Circuit}}
|{{CTGP-7 Course|GCN|Luigi Circuit}}
|{{CTGP-7 Course|Volcano Beach Ruins}}
|-
!Feather Cup
|{{CTGP-7 Course|GCN|Yoshi Circuit}}
|{{CTGP-7 Course|GBA|Peach Circuit}}
|{{CTGP-7 Course|Metro Madness}}
|{{CTGP-7 Course|GBA|Luigi Circuit}}
|-
!Fireball Cup
|{{CTGP-7 Course|SMO RC Challenge}}
|{{CTGP-7 Course|GBA|Bowser Castle 4}}
|{{CTGP-7 Course|SNES|Donut Plains 1}}
|{{CTGP-7 Course|Secret Slide}}
|-
!Bob-omb Cup
|{{CTGP-7 Course|DS|Wario Stadium}}
|{{CTGP-7 Course|Ermii Circuit}}
|{{CTGP-7 Course|GCN|Baby Park}}
|{{CTGP-7 Course|GCN|Bowser Castle}}
|-
!Cherry Cup
|{{CTGP-7 Course|SNES|Mario Circuit 3}}
|{{CTGP-7 Course|Big Blue}}
|{{CTGP-7 Course|GBA|Shy Guy Beach}}
|{{CTGP-7 Course|Bingo Party}}
|-
!Pickaxe Cup
|{{CTGP-7 Course|Stargaze Summit}}
|{{CTGP-7 Course|Sunset Raceway}}
|{{CTGP-7 Course|GBA|Broken Pier}}
|{{CTGP-7 Course|Glacier Mine}}
|-
!Mega Cup
|{{CTGP-7 Course|Flowerbed Fortress}}
|{{CTGP-7 Course|Seaside Palace}}
|{{CTGP-7 Course|DKR Star City}}
|{{CTGP-7 Course|Mushroom Mountain}}
|-
!Propeller Cup
|{{CTGP-7 Course|N64|Sherbert Land}}
|{{CTGP-7 Course|Block Island}}
|{{CTGP-7 Course|DS|Bowser Castle}}
|{{CTGP-7 Course|DKR Jungle Falls}}
|-
!POW Cup
|{{CTGP-7 Course|Retro Raceway}}
|{{CTGP-7 Course|Frozen Grotto}}
|{{CTGP-7 Course|GBA|Lakeside Park}}
|{{CTGP-7 Course|Dragon Burial Grounds}}
|-
!Rock Cup
|{{CTGP-7 Course|Warp Pipe Island}}
|{{CTGP-7 Course|Neo Metropolis}}
|{{CTGP-7 Course|Frosty Heights}}
|{{CTGP-7 Course|Gnasty Gnorc's Lair}}
|-
!Moon Cup
|{{CTGP-7 Course|RMX Vanilla Lake 1}}
|{{CTGP-7 Course|Cliffside Circuit}}
|{{CTGP-7 Course|Interstellar Laboratory}}
|{{CTGP-7 Course|Dark Matter Fortress}}
|-
!Coin Cup
|{{CTGP-7 Course|Doge Desert}}
|{{CTGP-7 Course|N64|Banshee Boardwalk}}
|{{CTGP-7 Course|GCN|Mario Circuit}}
|{{CTGP-7 Course|Miku's Birthday Spectacular}}
|-
!Rainbow Cup
|{{CTGP-7 Course|N64|Rainbow Road}}
|{{CTGP-7 Course|GBA|Rainbow Road}}
|{{CTGP-7 Course|RMX Rainbow Road 1}}
|{{CTGP-7 Course|Rainbow Road DX}}
|}

{{Short description|Mario Kart 7 modpack with custom tracks and characters}}
[[Category:Nintendo 3DS homebrew]]

FTPD

2025-02-24T22:40:36Z

Doge 2: swap infobox for text to match existing pages

{{short description|Wirelessly transfer files}}{{Infobox homebrew
| title = FTPD (Nintendo Switch)
| forswitch = 1
| developers = mtheall
| image = FTPDSwitch-icon.jpg
| imagealt = FTPD icon in the Homebrew Menu
| version = 3.2.1
| releasedate = 2024-11-17
| github = mtheall/ftpd
| githubtag = latest
}}{{Infobox homebrew
| title = FTPD (Nintendo 3DS)
| for3ds = 1
| developers = mtheall
| image = FTPD3DS-banner.png
| imagealt = FTPD banner on the HOME Menu
| version = 3.2.1
| releasedate = 2024-11-17
| github = mtheall/ftpd
| universaldb = 3ds/ftpd
| githubtag = latest
}}

FTPD is an FTP server for Nintendo DS, Nintendo 3DS, Nintendo Switch and Linux allowing you to use an FTP client to transfer files wirelessly with your console.

==Features==
* Graphical user interface using [https://github.com/ocornut/imgui Dear Imgui]
* Supports multiple simultaneous clients
* Emulation of a /dev/zero (/devZero) device for network performance testing
* Set username, password, and port with the GUI version of FTPD
* Toggle backlight by pressing SELECT on DS/3DS or MINUS on Switch
* Battery and Wi-Fi indicators

==Installation==

FTPD is installed as part of [[3dsguide:finalizing-setup|Finalizing Setup]] on [[3dsguide:get-started|our custom firmware installation guide for 3DS]], or [[switchguide:user_guide/all/sd_preparation|SD preperations]] on [[switchguide:|our Switch custom firmware installation guide]]. It is also on [[udb:3ds/ftpd|Universal-DB]] for Nintendo DS and Nintendo 3DS.

<tabber>

|-|Switch - Manually=

===What you need===
* The latest release of FTPD
** For a graphical user interface, download {{GitHub|mtheall/ftpd/releases/latest/download/ftpd.nro|ftpd.nro}}
** For a text based user interface, download {{GitHub|mtheall/ftpd/releases/latest/download/ftpd-classic.nro|ftpd-classic.nro}}

===Instructions===

# Power off your console
# Insert your SD card into your computer
# Copy the ftpd <code>.nro</code> to <code>sd:/switch/</code> on your SD card
#* Create the folder if it does not exist
# Safely eject your SD card and insert it in your console

|-|3DS - Universal-Updater=

<span>
===What you need===
* A working internet connection
* [[3DS:Universal-Updater|Universal-Updater]] installed on your console

===Instructions===
# Power on your console
# Launch '''Universal-Updater'''
# Select the magnifying glass on the bottom screen, then search for '''FTPD'''
# Press {{B|A}} while hovering over '''FTPD''' from the list of homebrew
# Choose <code>.cia</code> to install to the HOME Menu, or <code>.3dsx</code> to install to the Homebrew Launcher
#* For a graphical user interface choose <code>ftpd</code>
#* For a text based user interface choose <code>ftpd-classic</code>
# Wait until the app finishes installing
# Exit '''Universal-Updater'''
</span>
|-|3DS - FBI=

{{FBI QR code
| name1 = CIA
| url1 = https://github.com/mtheall/ftpd/releases/latest/download/ftpd.cia
| name2 = CIA-classic
| url2 = https://github.com/mtheall/ftpd/releases/latest/download/ftpd-classic.cia
| name3 = 3DSX
| url3 = https://github.com/mtheall/ftpd/releases/latest/download/ftpd.3dsx
| name4 = 3DSX-classic
| url4 = https://github.com/mtheall/ftpd/releases/latest/download/ftpd-classic.3dsx
}}

|-|3DS - Manually as 3DSX=

<span>
===What you need===
* The the latest release of FTPD
** For a graphical user interface, download {{GitHub|mtheall/ftpd/releases/latest/download/ftpd.3dsx|ftpd.3dsx}}
** For a text based user interface, download {{GitHub|mtheall/ftpd/releases/latest/download/ftpd-classic.3dsx|ftpd-classic.3dsx}}

===Instructions===
# Power off your console
# Insert your SD card into your computer
# Copy the ftpd <code>.3dsx</code> to <code>sd:/3ds/</code> on your SD card
#* Create the folder if it does not exist
# Safely eject your SD card and insert it in your console

</span>

|-|3DS - Manually as CIA=

<span>
===What you need===
* The latest release of FTPD
** For a graphical user interface, download {{GitHub|mtheall/ftpd/releases/latest/download/ftpd.cia|ftpd.cia}}
** For a text based user interface, download {{GitHub|mtheall/ftpd/releases/latest/download/ftpd-classic.cia|ftpd-classic.cia}}
* [[3DS:FBI|FBI]] installed on your console

===Instructions===
# Power off your console
# Insert your SD card into your computer
* Copy the ftpd <code>.cia</code> to <code>sd:/cias/</code> on your SD card
#* Create the folder if it does not exist
# Safely eject your SD card and insert it in your console
# Power on your console
# Launch '''FBI'''
# Select <code>SD</code> -> <code>cias</code> -> <code>ftpd.cia</code> -> <code>Install and delete CIA</code>
# Press {{B|A}} and wait for the CIA to install, then exit '''FBI'''
</span>

</tabber>

==Guides==
* [[3DS:FTP]]
* [[Switch:FTP]]

== Supported commands ==
{|
|
* ABOR
* ALLO (no-op)
* APPE
* CDUP
* CWD
* DELE
* FEAT
* HELP
* LIST
* MDTM
* MKD
* MLSD
* MLST
* MODE (no-op)
* NLST
* NOOP
* OPTS
* PASS (no-op)
* PASV
* PORT
|
* PWD
* QUIT
* REST
* RETR
* RMD
* RNFR
* RNTO
* SITE
* SIZE
* STAT
* STOR
* STRU (no-op)
* SYST
* TYPE (no-op)
* USER (no-op)
* XCUP
* XCWD
* XMKD
* XPWD
* XRMD
|}

=== SITE commands ===
* Show help: SITE HELP
* Set username: SITE USER
* Set password: SITE PASS
* Set port: SITE PORT
* Set getMTime*: SITE MTIME [0|1]
** getMTime only on 3DS. Enabling will give timestamps at the expense of slow listings.
* Save config: SITE SAVE

Checkpoint

2025-02-24T22:33:28Z

Doge 2: swap infobox for text to match existing pages

{{Infobox homebrew
| title = Checkpoint (Nintendo Switch)
| developers = FlagBrew
| forswitch = 1
| image = Checkpoint-Banner.png
| imagealt = Checkpoint banner on the Home Menu
| version = 3.8.0
| releasedate = 2021-11-13
| github = FlagBrew/Checkpoint
| githubtag = v3.8.0
}}{{Infobox homebrew
| title = Checkpoint (Nintendo 3DS)
| developers = FlagBrew
| for3ds = 1
| image = Checkpoint-Banner.png
| imagealt = Checkpoint banner on the Home Menu
| version = 3.7.4
| releasedate = 2019-12-09
| github = FlagBrew/Checkpoint
| githubtag = v3.7.4
}}

'''Checkpoint''' is a save manager for the Nintendo 3DS and Nintendo Switch.

== Features ==
<tabber>

|-|Nintendo 3DS=
<span>
* Exporting and importing saves, both 3DS and DS titles
* Creation of cheat files for various games
* Modifying Play Coin count
</span>
|-|Nintendo Switch=
<span>
* Exporting and importing saves
* Creation of cheat files for various games
</span>
</tabber>
== Installation ==

Checkpoint is installed as part of [[3dsguide:finalizing-setup|Finalizing Setup]] on [[3dsguide:get-started|our custom firmware installation guide]] for Nintendo 3DS consoles.

If you do not already have Checkpoint from Finalizing Setup (or have a Nintendo Switch), the possible methods to install it are as follows:

<tabber>
|-|Nintendo 3DS - FBI=

{{FBI QR code
| name1 = CIA
| url1 = https://github.com/FlagBrew/Checkpoint/releases/download/v3.7.4/Checkpoint.cia
| name2 = 3DSX
| url2 = https://github.com/FlagBrew/Checkpoint/releases/download/v3.7.4/Checkpoint.3dsx
}}

|-|Nintendo 3DS - Manually=
==== 3DSX (Homebrew Launcher) ====
<span>
# {{GitHub|BernardoGiordano/Checkpoint/releases/tag/v3.7.4|Download the latest Checkpoint.3dsx from the GitHub repository}}.
# Copy <code>Checkpoint.3dsx</code> to the <code>/3ds/</code> folder on your SD card.
# Open The Homebrew Launcher.
# Launch Checkpoint.
</span>

==== CIA (HOME Menu) ====
<span>
# {{GitHub|BernardoGiordano/Checkpoint/releases/tag/v3.7.4|Download the latest Checkpoint.cia from the GitHub repository}}.
# Install it using a CIA installer such as [[3DS:FBI|FBI]].
# Unwrap the newly installed app on your HOME menu, and open it.
</span>

|-| Nintendo Switch - Manually=
==== NRO (Homebrew Launcher) ====
<span>
# {{GitHub|BernardoGiordano/Checkpoint/releases/latest|Download the latest Checkpoint.nro from the GitHub repository}}.
# Copy <code>Checkpoint.nro</code> to the <code>/switch/</code> folder on your SD card.
# Open The Homebrew Menu and launch Checkpoint.
</span>
</tabber>
==Guides==

*[[3DS:Export saves]]

{{Short description|Save manager}}

3DS:CTRTransfer/Manual

2025-02-21T03:12:29Z

Doge 2: we can only paste out of a virtual path, not copy or move

{{hatnote|This is not the same as a CTRTransfer - it is harder to perform and not needed in most cases.<br>For instructions on a regular CTRTransfer, see [[3DS:CTRTransfer|the main CTRTransfer page.]]}}

A '''manual CTRTransfer''' is an advanced version of a CTRTransfer, used to restore more parts of the system software. It uses the same CTRTransfer images as the regular version, but overwrites the entire CTRNAND instead of just replacing the files that are most prone to damage.

{{critical|This is an advanced process that should only be used when all other options are exhausted.<br>It can be destructive if done incorrectly, so use caution.<br>If you run into any issues or do not understand something, join the [https://discord.gg/C29hYvh Nintendo Homebrew] Discord server and ask, in English, for help.}}

== Instructions ==

=== What You Need ===

* A 3DS console that can access [[3DS:GodMode9|GodMode9]]
* If console-unique files are missing but you have an external backup: The <code>essential.exefs</code> from this console
* A CTRTransfer image from [[3DS:CTRTransfer#What_You_Need|here]] that matches your model and region. This requires a torrent client such as [https://www.qbittorrent.org/download.php qBittorrent] or [https://dev.deluge-torrent.org/wiki/Download Deluge].
* The latest version of [https://raw.githubusercontent.com/nh-server/scripts/main/3DS/manual_transfer.gm9 manual_transfer.gm9]
** To download, right-click/long-press the link and select the <code>Save link as...</code> or similar, then rename the downloaded file to <code>manual_transfer.gm9</code> if it is not named exactly that)

=== Section I - Manual CTRTransfer ===

# Power off the console, remove the SD card, and connect it to your computer
# If you do not already have [[3DS:GodMode9|GodMode9]] on your SD card, take the time to get it now
# Once the CTRTransfer image is downloaded, place the CTRTransfer's <code>.bin</code> and <code>.bin.sha</code> files in <code>sd:/gm9/in</code>
# Copy the <code>manual_transfer.gm9</code> file you downloaded into <code>sd:/gm9/scripts</code>
# Put your SD card back into your console
# Hold {{B|START}}, and while holding {{B|START}}, power on your console. This will launch GodMode9
# Navigate into the drive <code>[S:] SYSNAND VIRTUAL</code>
# Move the cursor onto <code>essential.exefs</code> and press {{B|Y}} to copy it
# Go back out to the drive list, then go into <code>[0:] SDCARD</code>/<code>gm9/in</code>
# Press {{B|Y}}, then {{B|A}} to paste <code>essential.exefs</code>
# Press the {{B|HOME}} button, then go into <code>Scripts...</code> and select <code>manual_transfer</code>
#* You may choose yourself whether to restore optional data or not, unless you were linked to this by another page that says what to pick
# Wait for the script to complete, and then press {{B|A}} when it asks to reboot
# You should reach the HOME Menu without issues

{{success|The manual CTRTransfer has been completed.}}

{{info|If this did not fix your issue, you may have a hardware issue or serious software issue that will require further attention. Need some help? Ask us on Discord: [https://discord.gg/C29hYvh Nintendo Homebrew]}}

{{Short description|Advanced system restoration process}}

[[Category:Nintendo 3DS guides]]
[[Category:Nintendo 3DS troubleshooting]]

3DS:Mario Kart 7/CTGP-7

2025-02-20T03:23:55Z

Doge 2: 1.5.25

{{#approvable_by: users = PabloMK7
{{outdated|notes=
* Course list is outdated for 1.5.X.}}
{{Infobox game mod
| image = CTGP-7-banner.png
| imagesize = 256px
| developers = PabloMK7, Fishguy ([https://github.com/PabloMK7/CTGP-7updates/blob/master/credits.txt List of credits])
| version = 1.5.25
| releasedate = 2025-02-12 
| website = https://ctgp-7.github.io ctgp-7.github.io
| releaseurl = https://ctgp7.page.link/cia_downloader
| universaldb = 3ds/ctgp-7-downloader
}}
'''CTGP-7''' is a mod pack for Mario Kart 7, featuring custom race tracks, playable characters, items, and other additions.

== Installation ==

=== Universal-Updater ===
[[udb:3ds/ctgp-7-downloader|CTGP-7]] is available on Universal-DB.

=== Manually ===

{{Info|text=CTGP-7 also provides official installation instructions as a {{GitHub|PabloMK7/CTGP-7updates/blob/master/CTGP-7_Intallation_Guide_EN.pdf|PDF}} or [https://www.youtube.com/watch?v=OV9ZmrHOy4c YouTube video].}}

<tabber>

|-|Using FBI=
CTGP-7 has a downloader app to install the modpack for you, which can be opened from either the HOME Menu or the Homebrew Launcher.

{{FBI QR code
| name1 = CIA
| url1 = https://ctgp7.page.link/cia_downloader
| name2 = 3DSX
| url2 = https://ctgp7.page.link/3dsx_downloader
}}

|-|Using a Computer=
# Download the latest CTGP-7 installer for your computer's operating system from the mod's [https://gamebanana.com/mods/50221 GameBanana page]
#* Native installers are only available for Windows and Ubuntu. The Python-based installer might be required instead on other operating systems, but will also need an up-to-date Python installation and the dependencies listed in the README file.
# Insert your console's SD card into your computer
#* Make sure the SD card is accessible before continuing
# Run the CTGP-7 installer you downloaded
# Choose the location of your console's SD card if it wasn't detected automatically
# Press the install button and wait for it to finish
# Eject the SD card and reinsert it into your console
# Launch FBI
# Navigate to <code>SD:/CTGP-7/cia/</code>
# Select the <code>CTGP-7.cia</code> file
# Select "Install CIA"
# Press {{B|A}} to confirm
# Wait for the installation to finish
# Return to the HOME Menu and close FBI

{{Success|CTGP-7 is now installed!}}

</tabber>

== Courses ==
{{Section WIP|notes=Screenshots are taken during the pre-game intro.}}
In addition to the original courses included in Mario Kart 7, CTGP-7 adds 18 new cups.
{| class="wikitable" style="text-align: center"
!Cup
!Course 1
!Course 2
!Course 3
!Course 4
|-
!Bell Cup
|{{CTGP-7 Course|Concord Town}}
|{{CTGP-7 Course|N64|Mario Raceway}}
|{{CTGP-7 Course|Galvarny Falls}}
|{{CTGP-7 Course|GBA|Sky Garden}}
|-
!Acorn Cup
|{{CTGP-7 Course|Autumn Forest}}
|{{CTGP-7 Course|GBA|Riverside Park}}
|{{CTGP-7 Course|SNES|Mario Circuit 1}}
|{{CTGP-7 Course|GBA|Bowser Castle 3}}
|-
!Cloud Cup
|{{CTGP-7 Course|Evergreen Crossing}}
|{{CTGP-7 Course|N64|Moo Moo Farm}}
|{{CTGP-7 Course|Archipelago Avenue}}
|{{CTGP-7 Course|N64|Frappe Snowland}}
|-
!Boo Cup
|{{CTGP-7 Course|Banshee Boardwalk 2}}
|{{CTGP-7 Course|Elemental Cave}}
|{{CTGP-7 Course|SNES|Ghost Valley 2}}
|{{CTGP-7 Course|DS|Cheep Cheep Beach}}
|-
!Spring Cup
|{{CTGP-7 Course|DS|Tick Tock Clock}}
|{{CTGP-7 Course|Melody Sanctum}}
|{{CTGP-7 Course|DS|Desert Hills}}
|{{CTGP-7 Course|Castle Of Time}}
|-
!Egg Cup
|{{CTGP-7 Course|DS|Yoshi Falls}}
|{{CTGP-7 Course|N64|Choco Mountain}}
|{{CTGP-7 Course|DS|Shroom Ridge}}
|{{CTGP-7 Course|CTR Crash Cove}}
|-
!Bullet Cup
|{{CTGP-7 Course|CTR Cortex Castle}}
|{{CTGP-7 Course|Revo Circuit}}
|{{CTGP-7 Course|SNES|Choco Island 2}}
|{{CTGP-7 Course|Star Slope}}
|-
!Blooper Cup
|{{CTGP-7 Course|Sandcastle Park}}
|{{CTGP-7 Course|DS|Mario Circuit}}
|{{CTGP-7 Course|GCN|Luigi Circuit}}
|{{CTGP-7 Course|Volcano Beach Ruins}}
|-
!Feather Cup
|{{CTGP-7 Course|GCN|Yoshi Circuit}}
|{{CTGP-7 Course|GBA|Peach Circuit}}
|{{CTGP-7 Course|Metro Madness}}
|{{CTGP-7 Course|GBA|Luigi Circuit}}
|-
!Fireball Cup
|{{CTGP-7 Course|SMO RC Challenge}}
|{{CTGP-7 Course|GBA|Bowser Castle 4}}
|{{CTGP-7 Course|SNES|Donut Plains 1}}
|{{CTGP-7 Course|Secret Slide}}
|-
!Bob-omb Cup
|{{CTGP-7 Course|DS|Wario Stadium}}
|{{CTGP-7 Course|Ermii Circuit}}
|{{CTGP-7 Course|GCN|Baby Park}}
|{{CTGP-7 Course|GCN|Bowser Castle}}
|-
!Cherry Cup
|{{CTGP-7 Course|SNES|Mario Circuit 3}}
|{{CTGP-7 Course|Big Blue}}
|{{CTGP-7 Course|GBA|Shy Guy Beach}}
|{{CTGP-7 Course|Bingo Party}}
|-
!Pickaxe Cup
|{{CTGP-7 Course|Stargaze Summit}}
|{{CTGP-7 Course|Sunset Raceway}}
|{{CTGP-7 Course|GBA|Broken Pier}}
|{{CTGP-7 Course|Glacier Mine}}
|-
!Mega Cup
|{{CTGP-7 Course|Flowerbed Fortress}}
|{{CTGP-7 Course|Seaside Palace}}
|{{CTGP-7 Course|DKR Star City}}
|{{CTGP-7 Course|Mushroom Mountain}}
|-
!Propeller Cup
|{{CTGP-7 Course|N64|Sherbert Land}}
|{{CTGP-7 Course|Block Island}}
|{{CTGP-7 Course|DS|Bowser Castle}}
|{{CTGP-7 Course|DKR Jungle Falls}}
|-
!POW Cup
|{{CTGP-7 Course|Retro Raceway}}
|{{CTGP-7 Course|Frozen Grotto}}
|{{CTGP-7 Course|GBA|Lakeside Park}}
|{{CTGP-7 Course|Dragon Burial Grounds}}
|-
!Rock Cup
|{{CTGP-7 Course|Warp Pipe Island}}
|{{CTGP-7 Course|Neo Metropolis}}
|{{CTGP-7 Course|Frosty Heights}}
|{{CTGP-7 Course|Gnasty Gnorc's Lair}}
|-
!Moon Cup
|{{CTGP-7 Course|RMX Vanilla Lake 1}}
|{{CTGP-7 Course|Cliffside Circuit}}
|{{CTGP-7 Course|Interstellar Laboratory}}
|{{CTGP-7 Course|Dark Matter Fortress}}
|-
!Coin Cup
|{{CTGP-7 Course|Doge Desert}}
|{{CTGP-7 Course|N64|Banshee Boardwalk}}
|{{CTGP-7 Course|GCN|Mario Circuit}}
|{{CTGP-7 Course|Miku's Birthday Spectacular}}
|-
!Rainbow Cup
|{{CTGP-7 Course|N64|Rainbow Road}}
|{{CTGP-7 Course|GBA|Rainbow Road}}
|{{CTGP-7 Course|RMX Rainbow Road 1}}
|{{CTGP-7 Course|Rainbow Road DX}}
|}

{{Short description|Mario Kart 7 modpack with custom tracks and characters}}
[[Category:Nintendo 3DS homebrew]]

3DS:Why not to remove custom firmware

2025-02-08T12:39:13Z

Doge 2: online play for the 3ds and wii u are fully shut down now

Removing custom firmware (CFW) from a 3DS is not recommended for most cases.

== The Short Version ==
* It probably isn't why your game is broken.
* It probably isn't why some part of your console is broken.
* It isn't going to permanently break your console. The worst that would happen is Luma3DS needs updating (that's the {{code|boot.firm}} file on your SD card).
* It isn't going to delete all your saves; in fact, it provides tools to back up to make them extra safer than stock firmware can.
* It isn't going to cause you to get banned on its own. Don't cheat in online games.
* If you are selling the console, it might be a good idea to remove it then, but you should check first.
* If you are sending in the console to Nintendo for repair, it might also be a good idea.

__TOC__

== Fixing a broken game ==
Nearly all cases where a game doesn't work is not due to CFW alone. Most commonly, a corrupt game file or a corrupt save file. Removing CFW would it harder to diagnose the problems with a game. What Luma3DS does is expose more details about why a game doesn't work, allowing for more experienced people to figure it out, while stock would only show a generic "An error has occurred" screen.

Another possible case is due to a plugin or mod that is outdated or for the wrong version of the game. In this case, removing the plugin or mod would fix the game.

There are a few edge cases where games can break due to CFW settings. In particular, a few games crash on New 3DS if 804MHz and L2 cache are enabled. Usually these can be worked around by temporarily disabling the setting that is breaking the game.

== Fixing broken system applications ==
Sometimes a built-in part of the firmware might stop working for some reason. Assuming the system was not updated to a point where Luma3DS is currently not compatible, keeping CFW would mean you can fix the corruption, usually with a CTRTransfer. Removing CFW will probably keep the system in a broken state with no way to fix it without ntrboot.

== Concerns about bricks ==
CFW has become exceptionally safe to use on the 3DS over the years, both during and after setup. It is nearly impossible to brick on accident. GodMode9, the most common tool for interacting with the 3DS NAND, requires unlocking writing with a button combination when you are about to do something that could cause damage. The button combination requires deliberate inputs and is impossible to do by accident. (add something about corruption checks)

If Nintendo ever releases a new system update, there is a chance that Luma3DS will be incompatible with it. This is generally not regarded as a brick as it only breaks Luma3DS trying to boot into the firmware, it does not break running other tools such as GodMode9. Usually a new release is made in about a day and can be fixed by replacing {{code|boot.firm}} on the SD card.

The last update to break Luma3DS was 11.14.0-46, released 17 November 2020. The last one before that was 11.8.0-41, released 30 July 2018.

== Concerns about data loss ==
Like mentioned in the past section, CFW has very few risks associated with it, either when setting it up or using it. If you don't delete random files or titles using GodMode9, FBI, or similar tools, you are not likely to lose things such as game saves on the SD card.

CFW provides access to tools to make your own backups of your games, their saves, and the system's internal storage (aka NAND). These allow for better backups than what Nintendo normally allows. For example if your console is ever lost or broken, everything can be manually migrated to a replacement console. SD card data can be migrated if you have {{Code|movable.sed}} from the original console, which is inside {{Code|essential.exefs}} made during setup. NAND data (e.g. Friend List, Mii Maker, StreetPass Mii Plaza) can be transferred from a NAND backup.

== Concerns about bans ==
Nintendo most likely doesn't focus on 3DS security anymore. Thousands of people use custom firmware on their consoles without issue. The time where a ban is most likely is when cheats are used in public online rooms.

Nintendo has shut down online play and services for the 3DS on the 8th of April, 2024. There is be nothing to be banned from anymore.

In the past, there was one well-documented ban wave: when Pokémon Sun and Moon leaked online, some people downloaded it and used its online services before release. Bans were given to those who had done so.

== Selling console ==
This is often considered the only real case to remove custom firmware. A buyer may not be willing to accept any kind of homebrew, or the platform may remove listings for modified consoles. Notably, eBay does this if a mention of homebrew is on the listing.

Sometimes a workaround to prevent removal may be to not mention it, but include telltale signs of custom firmware in pictures (e.g. the "Sys" string in System Settings). You may not be willing to risk it however, so removing may be the best option. In this case, you should be careful to not leave remnants that can cause problems on stock, including modified system titles. In particular, make sure the following components work when the console is booted with stock firmware:
* Nintendo 3DS Camera app
* Health & Safety Information app
* DS Download Play
* DS Internet Settings
* DS Profile Settings (launching and attempting to enter in a name)

== Sending console in for repairs ==
Nintendo might not like receiving a console with boot9strap on it, so removing custom firmware temporarily would be a good idea. In this case you should make backups of the NAND in the event that Nintendo sends back a new console instead of repairing your existing one.

Keep in mind that Nintendo is slowly discontinuing repairs for 3DS models. As of February 24, 2022, Nintendo no longer repairs the Old 3DS, Old 3DS XL, or New 3DS (non-XL).

[[Category:Nintendo 3DS]]

Switch:TTD

2024-09-28T16:46:17Z

Doge 2: Redirect to Switch:Things_to_do

#REDIRECT [[Switch:Things to do]]

Open unsigned applications on macOS Sequoia and newer

2024-09-17T11:34:27Z

Doge 2: xattr -cr is much faster to type and achieves the same result

As of macOS Sequoia (15), Gatekeeper has tightened restrictions on running unsigned applications. The control-click and Open workaround no longer works. This guide demonstrates how to open these applications. Once an app has been opened once, it can be opened normally in the future.

== Through System Settings ==

#Try to open the app. A prompt saying '"My Unsigned App.app" Not Opened' may appear.<br>[[File:SequoiaGatekeeper-NotOpened.png|260px]]
#Go to System Settings -> Privacy & Security. Scroll down to find the app, and an option to "Open Anyway".<br>[[File:SequoiaGatekeeper-SystemSettings-PrivacyAndSecurity.png|715px]]
#Choose "Open Anyway".<br>[[File:SequoiaGatekeeper-OpenAnyway.png|260px]]
#Authenticate as an adminstrator.<br>[[File:SequoiaGatekeeper-AuthenticateApp.png|260px]]
#The app will now open.

== Through Terminal ==

Use the following command on the application:

<syntaxhighlight lang="bash">xattr -cr ./MyApp.app</syntaxhighlight>

[[Category:General guides]]

3DS:Error screens/Luma3DS exception screen

2024-09-06T00:54:17Z

Doge 2: undefined instruction at boot can sometimes mean corrupt sysmodules, not hardware

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

== Reading a Luma3DS exception screen ==

A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
** '''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
** '''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
** '''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
** '''prefetch abort''': Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
** '''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
** '''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
** '''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
* '''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
* '''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
** '''fs''': The filesystem, i.e. either the SD card or the NAND.
** '''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
** '''loader''': The service that opens apps, meaning the app most recently opened has an issue.
** '''nwm''': Networking services, almost always Wi-Fi.
** '''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
* '''Registers (R0-R12/SP/LR/PC/CPSR/FPEXC)''': Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
** If the value <code>000400??</code> (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
** If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting .

== Known Errors ==

In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===

Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue, or corrupted sysmodules. Try performing a [[3DS:CTRTransfer|CTRTransfer]] to see if it resolves the issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===

All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to recreate the error without the SD card inserted.<br>If the error stops after the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes that can appear here are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|the ErrDisp page]].
* <h6>prefetch abort (svcBreak)</h6>
**The LayeredFS or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* '''If not caused in Nintendo DS Profile:''' System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
* '''If caused in Nintendo DS Profile:''' Your NVRAM is either corrupted or damaged in hardware. Run [[3DS:ctrcheck|ctrcheck]] on <code>Full</code> - if it does not return <code>Critical: NVRAM is inaccessible</code>, then follow [[3DS:NVRAM|the Fix NVRAM guide]].

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>pm</h5>
* The software you have launched may be missing required files. If the value in R0 is <code>E0E01BF5</code>, this is extremely likely to be the cause.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
{{Short description|Guide to the CFW error handler}}

User:Doge 2

2024-09-01T00:19:12Z

Doge 2: +1 console

hey! i'm doge 2, i go by doge.2 on discord

i'm from ontario canada, and own every variation of the ds handheld family, from the original to new 2ds xl (finally!)

you can usually find me fucking around with any type of tech, mostly console modding

awooooo!

Formatting an SD card/Linux

2024-09-01T00:15:27Z

Doge 2: remove cfdisk, add guide for kde partition manager, do sd clean from beginning for fdisk

This is an add-on section for formatting an SD card to FAT32.

This page is for Linux users only. If you are not on Linux, check out the [[Special:MyLanguage/Formatting an SD card/Windows|Windows]] or [[Special:MyLanguage/Formatting an SD card/Mac|Mac]] pages.

== Instructions ==
{{warning|Before beginning these steps, copy all of your SD card's contents to a folder on your computer.}}

{{warning|The commands in this guide are case-sensitive. Enter them exactly as written, or there may be unintended consequences.}}
<tabber>
|-|fdisk=

<span>
# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Type <code>sudo umount /dev/<device name>*</code> (do not replace the <code>*</code>)
# Install the <code>fdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo fdisk /dev/<device name></code>
# Enter <code>o</code>, this will create a new MBR partition scheme
# Enter <code>n</code>, then press enter until you're returned to the prompt
#* The default values will work fine for all consoles
# Enter <code>t</code>, then enter <code>0c</code>
# Enter <code>a</code> and then <code>p</code> - observe the output, and make sure the device is now formatted correctly: {{#tag:syntaxhighlight|
Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x########

Device Boot Start End Sectors Size Id Type
/dev/<partition name> 8192 62333951 62325760 29.7G c W95 FAT32 (LBA)
|lang=text}}
# If there are no issues, enter <code>w</code> - this will save changes and exit the fdisk prompt
# Type <code>sudo mkfs.vfat /dev/<partition name> -s 64</code> to reformat the new partition
#* If the SD card is over 32GB in size, change <code>64</code> to <code>128</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# Copy your data back onto the SD card
</span>

|-|parted=

<span>
# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>parted</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo parted /dev/<device name> mklabel msdos</code>
# Type <code>sudo parted -a opt /dev/<device name> mkpart primary fat32 0% 100%</code>
# Type <code>sudo mkfs.vfat /dev/<partition name> -s 64</code> to reformat the new partition
#* If the SD card is over 32GB in size, change <code>64</code> to <code>128</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# Copy your data back onto the SD card
</span>

|-|KDE Partition Manager=

<span>
# Make sure your SD card is '''not''' inserted
# Open KDE Partition Manager, inputting your password as needed
# Insert your SD card and click <code>Refresh Devices</code>. The new device that shows up in the left pane is your SD card
# Click your SD card, then click the <code>New Partition Table</code> button at the top of the window
# When asked, choose <code>Ms-Dos</code>. Do '''NOT''' use <code>GPT</code>
#* [[File:KDE Partition Manager - MBR.png]]
# Right click the <code>unallocted</code> space in the right pane and select <code>New</code>
# When selecting your filesystem, choose <code>FAT32</code> from the drop down menu, it should look like this: [[File:KDE Partition Manager - New Partition.png]]
# Click <code>OK</code>, then click <code>Apply</code>, then <code>Apply Pending Operations</code>
# Eject and reinsert your SD card
# Copy your data back onto the SD card
</tabber>
{{hg imported|Guide_3DS}}

[[Category:General guides]]

File:KDE Partition Manager - MBR.png

2024-09-01T00:10:04Z

Doge 2: Screenshot highlighting MBR partition scheme in KDE Partition Manager.

== Summary ==
Screenshot highlighting MBR partition scheme in KDE Partition Manager.

File:KDE Partition Manager - New Partition.png

2024-09-01T00:05:47Z

Doge 2: Screenshot showing the new partition window in KDE Partition Manager.

== Summary ==
Screenshot showing the new partition window in KDE Partition Manager.

Formatting an SD card/Linux

2024-08-31T17:50:59Z

Doge 2: wip edit, still need to do something about cfdisk and eventually add gui options (gparted, kde partition manager)

This is an add-on section for formatting an SD card to FAT32.

This page is for Linux users only. If you are not on Linux, check out the [[Special:MyLanguage/Formatting an SD card/Windows|Windows]] or [[Special:MyLanguage/Formatting an SD card/Mac|Mac]] pages.

== Instructions ==
{{warning|Before beginning these steps, copy all of your SD card's contents to a folder on your computer.}}

{{warning|The commands in this guide are case-sensitive. Enter them exactly as written, or there may be unintended consequences.}}
<tabber>
|-|fdisk=

<span>
# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Type <code>sudo umount /dev/<device name>*</code> (do not replace the <code>*</code>)
# Install the <code>fdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo fdisk /dev/<device name></code>
# Enter <code>o</code>, this will create a new MBR partition scheme
# Enter <code>n</code>, then press enter until you're returned to the prompt
#* The default values will work fine for all consoles
# Enter <code>t</code>, then enter <code>0c</code>
# Enter <code>a</code> and then <code>p</code> - observe the output, and make sure the device is now formatted correctly: {{#tag:syntaxhighlight|
Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x########

Device Boot Start End Sectors Size Id Type
/dev/<partition name> 8192 62333951 62325760 29.7G c W95 FAT32 (LBA)
|lang=text}}
# If there are no issues, enter <code>w</code> - this will save changes and exit the fdisk prompt
# Type <code>sudo mkfs.vfat /dev/<partition name> -s 64</code> to reformat the new partition
#* If the SD card is over 32GB in size, change <code>64</code> to <code>128</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# Copy your data back onto the SD card
</span>

|-|cfdisk=

<span>
# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>cfdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo cfdisk /dev/<device name></code>
# Choose the <code>Delete</code> option and delete any existing partitions
# Choose the <code>New</code> option, keep partition size at the recommended size, and choose primary partition type
# Choose the <code>Type</code> option, scroll up until you see <code>c W95 FAT32 (LBA)</code> and select it
# Finally, choose the <code>Write</code> option.
# Choose the <code>Quit</code> option
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# Copy your data back onto the SD card
</span>

|-|parted=

<span>
# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>parted</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo parted /dev/<device name> mklabel msdos</code>
# Type <code>sudo parted -a opt /dev/<device name> mkpart primary fat32 0% 100%</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card.
# Copy your data back onto the SD card.
</span>
</tabber>
{{hg imported|Guide_3DS}}

[[Category:General guides]]

3DS:Alternate Exploits/Installing boot9strap (SSLoth-Browser)

2024-08-22T15:48:17Z

Doge 2: nevermind qr extension is better

==Technical Details==
In order to exploit the Browser application, we need to bypass the browser version check, which is designed to disallow the use of the browser without updating to the latest system version.

A public proxy server is available, which, with the help of the SSLoth exploit, can bypass this check.

Once the bypass is active, an exploit webpage will be accessible which will do the rest of the job.

For technical details on the exploits that you will be using on this page, see here (SSLoth) and here (universal-otherapp).

==Compatibility Notes==
SSLoth allows users on version 11.13.0 and below to bypass the browser version check, allowing the use of new-browserhax or old-browserhax (compatible with versions 11.4.0 through 11.13.0 in all regions), which can then be used in conjunction with universal-otherapp.

==What You Need==

*The latest release of [https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip SafeB9SInstaller] (direct download)
*The latest release of [https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip boot9strap] (direct download)
*The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] (the Luma3DS <code>.zip</code> file)
*The latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp] (<code>otherapp.bin</code>)

==Instructions==

====Section I - Prep Work====

#Power off your console
#Insert your SD card into your computer
#Copy <code>otherapp.bin</code> to the root of your SD card and rename it to <code>arm11code.bin</code>
#*The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
#*If you do not see the <code>.bin</code> extension, do not add it to the end of the filename
#Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Create a folder named <code>boot9strap</code> on the root of your SD card
#Copy <code>boot9strap.firm</code> and <code>boot9strap.firm.sha</code> from the boot9strap <code>.zip</code> to the <code>/boot9strap/</code> folder on your SD card
#Copy <code>SafeB9SInstaller.bin</code> from the SafeB9SInstaller <code>.zip</code> to the root of your SD card
#Reinsert your SD card into your console
#Power on your console

====Section II - SSLoth====

#Launch the System Settings application
#Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
#Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
#Set “Proxy Settings” to “Yes”, then click <code>Detailed Setup</code>
#Set the Proxy Server to <code>ssloth.nintendohomebrew.com</code>, and the Port to <code>8080</code>
#Click OK, then click Save
#When prompted, click “Test” to perform the connection test
#*The test should succeed
#Click “OK” to continue
#Press “Back” twice, then “Close” to go back to the HOME Menu

====Section III - Launching SafeB9SInstaller====

#On the HOME Menu, press the Left and Right shoulder buttons at the same time to open the camera
#*If you are unable to open the camera, open the Internet Browser and manually type the URL instead (<code><nowiki>https://zoogie.github.io/web/nbhax/</nowiki></code>)
#Tap the QR code button and scan this QR code
{{#qrlite:{{https://zoogie.github.io/web/nbhax/:{{nbhax}}}}|format=png|size=5|margin=5}}
#*If you get a crash or an error code, follow the troubleshooting guide at the bottom of the page
#*If you get a security certificate warning, press (A) to allow the connection
#Tap the “PROCEED TO HAXX” button
#If the exploit was successful, you will have booted into SafeB9SInstaller
#*If you get an error, follow the troubleshooting guide at the bottom of the page

====Section IV - Installing boot9strap====

#When prompted, input the key combo given on the top screen to install boot9strap
#*If a step on the lower screen has red-colored text, and you are not prompted to input a key combo, [[3dsguide:troubleshooting#issues-with-safeb9sinstaller|follow this troubleshooting guide]]
#Once it is complete, press (A) to reboot your console
#Your console should have booted into the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, '''leave these options on the default settings''' (do not check or uncheck anything)
#*If your console shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot

====Section V - Restoring default proxy====

#Launch the System Settings application
#Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
#Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
#Set “Proxy Settings” to “No”
#Click OK, then click Save
#When prompted, click “Test” to perform the connection test
#*The test should succeed
#Power off your console

At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.

-----

<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>

== Troubleshooting ==

=== Red/purple/pink and white screen after running Browserhax ===
This likely indicates that you already have custom firmware. You should [[3dsguide:checking-for-cfw|check for CFW]].

=== "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text) ===
The file <code>arm11code.bin</code> is missing or misplaced. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

=== "An error has occurred, forcing the software to close..." (white message box) ===
There may be an issue with your <code>arm11code.bin</code> file. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

You can also try resetting your browser save data:

# Launch the browser, then launch the browser settings
# Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)
# Return to Section III

=== Opening the browserhax QR code or URL crashes ===
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.

# Launch the browser, then launch the browser settings
# Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)
# Return to Section III

=== System Update prompt when opening browser ===
The SSLoth proxy was incorrectly configured. Re-do Section II on this page.

=== Error 032-0420 when opening browser ===
Follow these steps in order:

# Launch System Settings on your console
# Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
# Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
# Set “Proxy Settings” to “No”
# Click OK, then click Save
# When prompted, click “Test” to perform the connection test
#* The test should succeed
# Click “OK” to continue
# Press “Back” twice, then “Close” to go back to the HOME Menu
# Open the Internet Browser once
# If prompted about a system update, press OK
#* This won’t actually update the system
# Start again from Section II

=== Frozen on "Doing agbhax..." ===
There may be an issue with your <code>arm11code.bin</code> file. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

=== "PrepareArm9ForTwl returned error c8804631!" ===
Join [https://discord.gg/MWxPgEp Nintendo Homebrew on Discord] for assistance.

=== Failed to mount the SD card! ===
Back up your data and [[Formatting an SD card|reformat your SD card as FAT32]] with the recommended tool depending on your operating system. MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.

If this is unsuccessful, try using another SD card.
[[Category:Nintendo 3DS guides]]

User:Doge 2/Sandbox

2024-08-22T15:42:18Z

Doge 2: testing out qr stuff with rickrolls

{{#qrlite:{{https://www.youtube.com/watch?v=dQw4w9WgXcQ:{{frii gams!!!}}}}|format=png|size=10|margin=0}}

3DS:Alternate Exploits/Installing boot9strap (SSLoth-Browser)

2024-08-22T15:32:49Z

Doge 2: add missing QR code image

==Technical Details==
In order to exploit the Browser application, we need to bypass the browser version check, which is designed to disallow the use of the browser without updating to the latest system version.

A public proxy server is available, which, with the help of the SSLoth exploit, can bypass this check.

Once the bypass is active, an exploit webpage will be accessible which will do the rest of the job.

For technical details on the exploits that you will be using on this page, see here (SSLoth) and here (universal-otherapp).

==Compatibility Notes==
SSLoth allows users on version 11.13.0 and below to bypass the browser version check, allowing the use of new-browserhax or old-browserhax (compatible with versions 11.4.0 through 11.13.0 in all regions), which can then be used in conjunction with universal-otherapp.

==What You Need==

*The latest release of [https://github.com/d0k3/SafeB9SInstaller/releases/download/v0.0.7/SafeB9SInstaller-20170605-122940.zip SafeB9SInstaller] (direct download)
*The latest release of [https://github.com/SciresM/boot9strap/releases/download/1.4/boot9strap-1.4.zip boot9strap] (direct download)
*The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] (the Luma3DS <code>.zip</code> file)
*The latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp] (<code>otherapp.bin</code>)

==Instructions==

====Section I - Prep Work====

#Power off your console
#Insert your SD card into your computer
#Copy <code>otherapp.bin</code> to the root of your SD card and rename it to <code>arm11code.bin</code>
#*The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
#*If you do not see the <code>.bin</code> extension, do not add it to the end of the filename
#Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Create a folder named <code>boot9strap</code> on the root of your SD card
#Copy <code>boot9strap.firm</code> and <code>boot9strap.firm.sha</code> from the boot9strap <code>.zip</code> to the <code>/boot9strap/</code> folder on your SD card
#Copy <code>SafeB9SInstaller.bin</code> from the SafeB9SInstaller <code>.zip</code> to the root of your SD card
#Reinsert your SD card into your console
#Power on your console

====Section II - SSLoth====

#Launch the System Settings application
#Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
#Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
#Set “Proxy Settings” to “Yes”, then click <code>Detailed Setup</code>
#Set the Proxy Server to <code>ssloth.nintendohomebrew.com</code>, and the Port to <code>8080</code>
#Click OK, then click Save
#When prompted, click “Test” to perform the connection test
#*The test should succeed
#Click “OK” to continue
#Press “Back” twice, then “Close” to go back to the HOME Menu

====Section III - Launching SafeB9SInstaller====

#On the HOME Menu, press the Left and Right shoulder buttons at the same time to open the camera
#*If you are unable to open the camera, open the Internet Browser and manually type the URL instead (<code><nowiki>https://zoogie.github.io/web/nbhax/</nowiki></code>)
#Tap the QR code button and scan this QR code[[File:Nbhax.png|center|thumb]]
#*If you get a crash or an error code, follow the troubleshooting guide at the bottom of the page
#*If you get a security certificate warning, press (A) to allow the connection
#Tap the “PROCEED TO HAXX” button
#If the exploit was successful, you will have booted into SafeB9SInstaller
#*If you get an error, follow the troubleshooting guide at the bottom of the page

====Section IV - Installing boot9strap====

#When prompted, input the key combo given on the top screen to install boot9strap
#*If a step on the lower screen has red-colored text, and you are not prompted to input a key combo, [[3dsguide:troubleshooting#issues-with-safeb9sinstaller|follow this troubleshooting guide]]
#Once it is complete, press (A) to reboot your console
#Your console should have booted into the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, '''leave these options on the default settings''' (do not check or uncheck anything)
#*If your console shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot

====Section V - Restoring default proxy====

#Launch the System Settings application
#Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
#Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
#Set “Proxy Settings” to “No”
#Click OK, then click Save
#When prompted, click “Test” to perform the connection test
#*The test should succeed
#Power off your console

At this point, your console will boot to Luma3DS by default.

*Luma3DS does not look any different from the normal HOME Menu. If your console has booted into the HOME Menu, it is running custom firmware.
*On the next page, you will install useful homebrew applications to complete your setup.

-----

<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>

== Troubleshooting ==

=== Red/purple/pink and white screen after running Browserhax ===
This likely indicates that you already have custom firmware. You should [[3dsguide:checking-for-cfw|check for CFW]].

=== "An error has occurred. Hold down the POWER button to turn off the power..." (black screen with text) ===
The file <code>arm11code.bin</code> is missing or misplaced. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

=== "An error has occurred, forcing the software to close..." (white message box) ===
There may be an issue with your <code>arm11code.bin</code> file. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

You can also try resetting your browser save data:

# Launch the browser, then launch the browser settings
# Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)
# Return to Section III

=== Opening the browserhax QR code or URL crashes ===
Browser based exploits (such as this one) are often unstable and crash frequently, but they can sometimes be fixed by doing the following steps.

# Launch the browser, then launch the browser settings
# Scroll to the bottom and select “Reset Save Data” (it may also be called “Initialize Save Data” or “Clear All Save Data”)
# Return to Section III

=== System Update prompt when opening browser ===
The SSLoth proxy was incorrectly configured. Re-do Section II on this page.

=== Error 032-0420 when opening browser ===
Follow these steps in order:

# Launch System Settings on your console
# Navigate to <code>Internet Settings</code> -> <code>Connection Settings</code>
# Click on your network connection slot and navigate to <code>Change Settings</code> -> <code>Next Page (right arrow)</code> -> <code>Proxy Settings</code>
# Set “Proxy Settings” to “No”
# Click OK, then click Save
# When prompted, click “Test” to perform the connection test
#* The test should succeed
# Click “OK” to continue
# Press “Back” twice, then “Close” to go back to the HOME Menu
# Open the Internet Browser once
# If prompted about a system update, press OK
#* This won’t actually update the system
# Start again from Section II

=== Frozen on "Doing agbhax..." ===
There may be an issue with your <code>arm11code.bin</code> file. Download the latest release of [https://github.com/TuxSH/universal-otherapp/releases/latest universal-otherapp], place <code>otherapp.bin</code> on the root of your SD card and rename it to <code>arm11code.bin</code>. Do not add the <code>.bin</code> extension if you do not already see it.

=== "PrepareArm9ForTwl returned error c8804631!" ===
Join [https://discord.gg/MWxPgEp Nintendo Homebrew on Discord] for assistance.

=== Failed to mount the SD card! ===
Back up your data and [[Formatting an SD card|reformat your SD card as FAT32]] with the recommended tool depending on your operating system. MiniTool Partition Wizard and the HP formatting tool (HPUSBDisk) are known to cause issues with 3DS SD cards.

If this is unsuccessful, try using another SD card.
[[Category:Nintendo 3DS guides]]

Nintendo 3DS and Wii U online shutdown and homebrew FAQ

2024-04-09T01:03:50Z

Doge 2: fix typo and mention that wii u now supports running pretendo without needing hacks

{{Page WIP|notes=
* Needs more Wii U-focused info, as I am only knowledgeable about 3DS
}}This page answers frequently asked questions about the discontinuation of online services for the Nintendo 3DS and Wii U on April 8, 2024, and its relation to homebrew.

eShop funds can no longer be merged with a Nintendo Account. The deadline for merging funds was March 11th, 2024.

[https://en-americas-support.nintendo.com/app/answers/detail/a_id/63227/~/announcement-of-discontinuation-of-online-services-for-nintendo-3ds-and-wii-u Read the official announcement] on Nintendo Support.

== What specifically will be ending? ==
These services are discontinued:

* Online play for all software that uses Nintendo Network
* Nintendo Badge Arcade
* SpotPass

These services will continue working past the shutdown date:

* Nintendo eShop (for downloading game updates and past purchases)
** System Transfer will also continue to work<ref name="transfer">https://www.nintendolife.com/guides/when-does-3ds-and-wii-u-online-shut-down-nintendo-eshop-and-online-play-closure-guide#will-i-still-be-able-to-perform-a-3ds-system-transfer-after-the-online-shutdown</ref>
* Pokémon Bank and Poké Transporter - however it is recommended to transfer to Pokemon HOME as soon as possible as it is hinted at that it won't be up for very long.<ref name=":0" />

== Can I hack my console after the online shutdown? ==
Yes, current console modding methods are not affected by the shutdown, and will continue to work long after the shutdown.

== Can I still use the browser after the online shutdown? ==
Yes, you can still use the browser on both Nintendo 3DS and Wii U consoles after the shutdown, as these do not depend on the Nintendo Network in any way.

== Will homebrew let me continue to play online? ==
The official servers are down permanently for everyone, homebrew will not grant you access to them. Instead, an alternate network, [https://pretendo.network Pretendo Network], is in development.

== Can I use Pretendo Network without hacking? ==
Yes, but only on Wii U platforms. 3DS consoles still need to be homebrewed in order to use Pretendo Network.

== Will Pretendo Network work on Tiramisu? ==
No, Pretendo has ended support for Tiramisu. You will need to use the Aroma environment to install it.



== Can I still set up homebrew after the shutdown? ==
Yes, but certain exploits that depend on online services may not be available, such as Seedminer, which requires use of the Friend List. No Wii U exploits are affected by this.

== What happens to the eShop? ==
Nintendo eShop is likely to stay available for downloading game updates and past purchases for a long time. Similarly, the Wii Shop Channel and DSi Shop are still online to download purchases many years later.

== What about System Transfer? ==
The System Transfer feature will continue to work for the foreseeable future.<ref name="transfer" />

== Will I still be able to update? ==
Just like the eShop, update servers are most likely going to be still accessible after the shutdown. Consoles like the Wii are still able to be updated. It is still recommended to update if CFW is installed on the console.

== What about Pokémon Bank? ==
Pokémon Bank and Poké Transporter will still work after the shutdown, but it is recommended to transfer to Pokémon HOME as early as possible, as it may not stay available for long<ref name=":0">https://twitter.com/playpokemon/status/1709614360904004012 ([https://web.archive.org/web/20231005083547/https://twitter.com/playpokemon/status/1709614360904004012 archive])</ref>.

== References ==
<references />

Nintendo 3DS and Wii U online shutdown and homebrew FAQ

2024-04-08T15:39:38Z

Doge 2: add more faqs about console hacking and browser

{{Page WIP|notes=
* Needs more Wii U-focused info, as I am only knowledgeable about 3DS
}}This page answers frequently asked questions about the discontinuation of online services for the Nintendo 3DS and Wii U on {{Start date and age|2024|04|08}}, and its relation to homebrew.

eShop funds can no longer be merged with a Nintendo Account. The deadline for merging funds was March 11th, 2024.

[https://en-americas-support.nintendo.com/app/answers/detail/a_id/63227/~/announcement-of-discontinuation-of-online-services-for-nintendo-3ds-and-wii-u Read the official announcement] on Nintendo Support.

== What specifically will be ending? ==
These services will be discontinued:

* Online play for all software that uses Nintendo Network
* Nintendo Badge Arcade
* SpotPass

These services will continue working past the shutdown date:

* Nintendo eShop (for downloading game updates and past purchases)
** System Transfer will also continue to work<ref name="transfer">https://www.nintendolife.com/guides/when-does-3ds-and-wii-u-online-shut-down-nintendo-eshop-and-online-play-closure-guide#will-i-still-be-able-to-perform-a-3ds-system-transfer-after-the-online-shutdown</ref>
* Pokémon Bank and Poké Transporter - however it is recommended to transfer to Pokemon HOME as soon as possible as it is hinted at that it won't be up for very long.<ref name=":0" />

== Can I hack my console after the online shutdown? ==
Yes, current console modding methods will not be affected by the shutdown, and will continue to work long after the shutdown.

== Can I still use the browser after the online shutdown? ==
Yes, you can still use the browser on both Nintendo 3DS and Nintendo Wii U consoles after the shutdown, as these do not depend on the Nintendo Network in any way.

== Will homebrew let me continue to play online? ==
The official servers will be going down permanently for everyone, homebrew will not grant you access to them. Instead, an alternate network, [https://pretendo.network Pretendo Network], is in development.

== Can I use Pretendo Network without hacking? ==
No, homebrew is required to play on Pretendo Network or any unofficial servers.

== Will Pretendo Network work on Tiramisu? ==
No, Pretendo has ended support for Tiramisu. You will need to use the Aroma environment to install it.

== Is there something I can do to help Pretendo Network? ==
Pretendo needs network dumps for games, so that it can recreate the servers. You can capture network dumps using your 3DS or Wii U. https://pretendo.network/docs/network-dumps

== Can I still set up homebrew after the shutdown? ==
Yes, but certain exploits that depend on online services may not be available, such as Seedminer, which requires use of the Friend List. No Wii U exploits are affected by this.

== What happens to the eShop? ==
Nintendo eShop is likely to stay available for downloading game updates and past purchases for a long time. Similarly, the Wii Shop Channel and DSi Shop are still online to download purchases many years later.

== What about System Transfer? ==
The System Transfer feature will continue to work for the foreseeable future.<ref name="transfer" />

== Will I still be able to update? ==
Just like the eShop, update servers are most likely going to be still accessible after the shutdown. Consoles like the Wii are still able to be updated. It is still recommended to update if CFW is installed on the console.

== What about Pokémon Bank? ==
Pokémon Bank and Poké Transporter will still work after the shutdown, but it is recommended to transfer to Pokémon HOME as early as possible, as it may not stay available for long<ref name=":0">https://twitter.com/playpokemon/status/1709614360904004012 ([https://web.archive.org/web/20231005083547/https://twitter.com/playpokemon/status/1709614360904004012 archive])</ref>.

== References ==
<references />

Wii U:How to remove NNIDs

2024-04-01T13:18:32Z

Doge 2: Did you know it's really easy to hack your Wii U?

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
#

Sdunfuck

2024-03-27T14:20:33Z

Doge 2: redirecet

#REDIRECT [[SD Clean]]

Formatting an SD card

2024-03-26T01:18:02Z

Doge 2: make notices about android/chromeos and ios/ipados formatting more noticeable

The process to format an SD card to FAT32 is different for Windows, Linux and macOS.

{{OS selector|w=1|l=1|m=1}}

{{critical|text=ChromeOS and Android are not an option and formatting an SD card with its built-in formatter may result in it becoming unusable by consoles.}}

{{info|text=iOS/iPadOS cannot format SD cards.}}

=== Alternatives ===
* If you have a 3DS with custom firmware, you can instead use [[3DS:GodMode9 Usage#Format an SD card|GodMode9]].
* If you have an unpatched or modchipped Switch, you can instead use [[switchguide:user_guide/emummc/partitioning_sd|TegraExplorer]]
** Note: If you do not wish to create an emuNAND, e.g. for a sysCFW setup or for other consoles, select Only Fat32 instead of <code>Fat32 + EmuMMC</code>

----

If you already understand how to use the tools in the above guides, here are direct links to their pages:
* Windows: [https://www.sdcard.org/downloads/formatter/ SD Memory Card Formatter] + [http://ridgecrop.co.uk/index.htm?guiformat.htm guiformat]
* Mac: [https://support.apple.com/guide/disk-utility/format-a-disk-for-windows-computers-dskutl1010 Disk Utility]
* Linux: [https://github.com/dosfstools/dosfstools dosfstools]

[[Category:General guides]]

Wii U:Tiramisu

2024-03-13T21:03:53Z

Doge 2: change wii u guide link to tiramisu guide and make this page a stub

[https://tiramisu.foryour.cafe Tiramisu] is a coldboot custom firmware for the Wii U. Unlike previous coldboot haxx like Coldboot Haxchi, Tiramisu is free of cost and is much safer.

To run Tiramisu on your Wii U console, see [[wiiuguide:archive/tiramisu/sd-preparation|Wii U Hacks Guide]]

{{stub}}

[[Category:Wii U homebrew]]

Formatting an SD Card

2024-03-13T13:39:44Z

Doge 2: redirect to sd card format

#REDIRECT [[Formatting an SD card]]

Nintendo 3DS and Wii U online shutdown and homebrew FAQ

2024-03-11T12:51:12Z

Doge 2: maybe wait until march 12th to approve this? idk when it actually closes

{{Page WIP|notes=
* Needs more Wii U-focused info, as I am only knowledgeable about 3DS
}}This page answers frequently asked questions about the discontinuation of online services for the Nintendo 3DS and Wii U on {{Start date and age|2024|04|08}}, and its relation to homebrew.

eShop funds can no longer be merged with a Nintendo Account. The deadline for merging funds was March 11th, 2024.

[https://en-americas-support.nintendo.com/app/answers/detail/a_id/63227/~/announcement-of-discontinuation-of-online-services-for-nintendo-3ds-and-wii-u Read the official announcement] on Nintendo Support.

== What specifically will be ending? ==
These services will be discontinued:

* Online play for all software that uses Nintendo Network
* Nintendo Badge Arcade
* SpotPass

These services will continue working past the shutdown date:

* Nintendo eShop (for downloading game updates and past purchases)
* Pokémon Bank and Poké Transporter - however it is recommended to transfer to Pokemon HOME as soon as possible as it is hinted at that it won't be up for very long.<ref name=":0" />

== Will homebrew let me continue to play online? ==
The official servers will be going down permanently for everyone, homebrew will not grant you access to them. Instead, an alternate network, [https://pretendo.network Pretendo Network], is in development.

== Can I use Pretendo Network without hacking? ==
No, homebrew is required to play on Pretendo Network or any unofficial servers.

== Will Pretendo Network work on Tiramisu? ==
No, Pretendo has ended support for Tiramisu. You will need to use the Aroma environment to install it.

== Can I still set up homebrew after the shutdown? ==
Yes, but certain exploits that depend on online services may not be available, such as Seedminer, which requires use of the Friend List.

== What happens to the eShop? ==
Nintendo eShop is likely to stay available for downloading game updates and past purchases for a long time. Similarly, the Wii Shop Channel and DSi Shop are still online to download purchases many years later.

== Will I still be able to update? ==
Just like the eShop, update servers are most likely going to be still accessible after the shutdown. Consoles like the Wii are still able to be updated. It is still recommended to update if CFW is installed on the console.

== What about Pokémon Bank? ==
Pokémon Bank and Poké Transporter will still work after the shutdown, but it is recommended to transfer to Pokémon HOME as early as possible, as it may not stay available for long<ref name=":0">https://twitter.com/playpokemon/status/1709614360904004012 ([https://web.archive.org/web/20231005083547/https://twitter.com/playpokemon/status/1709614360904004012 archive])</ref>.

== References ==
<references />

3DS:Emulators

2024-03-04T20:20:32Z

Doge 2: rip citra :(

{{hatnote|3DS:EMU redirects here. For EmuNAND, see [[3DS:EmuNAND and RedNAND]].}}

An '''emulator''' is a piece of software that uses computing power to simulate another device, such as a video game console or a personal computer. As a general guideline, the original Nintendo 3DS is capable of emulating most popular home consoles up to around the {{iw|wikipedia|fourth generation of video game consoles}} (the SNES/Genesis era), while the New Nintendo 3DS series is (just barely) capable of emulating some of the {{iw|wikipedia|fifth generation of video game consoles|fifth generation}} (the N64/PS1 era).
<br>This is because emulation requires significantly more computing power than running the console natively - though even if it could run emulated games as efficiently as native playback, even a new model 3DS would still only be able to emulate the {{iw|wikipedia|sixth generation of video game consoles|sixth generation}} (the Xbox/PS2/Dreamcast era) and possibly the Wii.

The Nintendo 3DS has hardware that allows for native backwards compatibility with the Nintendo DS and Game Boy Advance, meaning such software can run at full speed as they would on the original hardware. While this is not actually emulation, methods that use this hardware will be included here due to the ubiquity of the term.

== Handheld video game consoles ==

=== Nintendo DS ===
{{Main|3DS:DS games}}

Nintendo DS software can be played natively using nds-bootstrap, a tool that allows NDS backups to be run from the SD card. In most cases, you will use either TWiLight Menu++ or NDS forwarders to launch the ROM, after which nds-bootstrap will do the hard work of getting it to run.

In the past, Nintendo DS flashcarts were a popular way to run Nintendo DS software. Because of nds-bootstrap's development over the years, they have become less and less necessary, but can still offer useful features like being able to use the flashcart on unmodded 3DS-family and DS-family consoles (depending on the cartridge).

=== Game Boy Advance ===
{{Main|3DS:GBA games}}

Game Boy Advance software can be played natively by leveraging AGB_FIRM, something built into every 3DS that allows for native playback of Game Boy Advance software. AGB_FIRM was only ever used officially as part of the Ambassador Program for early purchasers of the original Nintendo 3DS before its price was cut.

The current recommended way to run GBA software is [[3DS:open_agb_firm|open_agb_firm]] due to its drag-and-drop functionality and ease of save file access. open_agb_firm runs as a payload (similar to GodMode9), meaning it is not directly accessible from HOME Menu (requiring a reboot to enter/exit) unless an alternate bootloader such as [[3DS:fastboot3DS|fastboot3DS]] is combined with [https://gbatemp.net/download/open-agb-launcher.36828/ Open AGB Launcher].<br>
If you want to use another method but still want icons directly on your HOME Menu, you can create virtual console injects on a Windows device.

GBA games can also be emulated, the recommended emulator being [[udb:3ds/mgba|mGBA]]. This is the best option if you wish to use cheats and save-states, but performance will rarely be full-speed on old models and some games will not work correctly.

GBARunner2 is a middle ground between native playback and emulation, similar to Nintendont on the Wii - this means it has none of the emulator features and the reduced compatibility of an emulator.<br>
It is included with TWiLightMenu++ (which you may already be using for NDS software), but because of the other options available, it isn't recommended.

=== Game Boy Color / Game Boy ===
The Game Boy Color and Game Boy are old enough that all models of the 3DS (and even the DS) can run them at full speed. The historically popular GB(C) emulator has been [[udb:3ds/gameyob-3ds|GameYob]], but due to 3DS-specific issues the [[udb:ds/gameyob|DS version]] is preferred (ran through TWiLight Menu++).<br>
You can also create virtual console injects for GB/GBC games if you prefer individual icons on HOME Menu.

The multi-platform GB(C) emulator [https://github.com/RossMeikleham/PlutoBoy/actions PlutoBoy] is currently under active development. A GitHub account is required to download the automated builds.

=== WonderSwan ===
Possible through the Mednafen (WonderSwan) core on [[3DS:RetroArch|RetroArch]]. Performance has been reported to be slow on Old 3DS units.

== Home video game consoles ==

=== GameCube/Wii/Wii U/Switch ===
Not possible. While some 3DS games are ports of GameCube games, these consoles require too much computing power to be emulated by the 3DS.<br>
Also note that due to these computing power requirements, ports of Wii/Wii U/Switch games are also extremely unlikely.

=== PlayStation 1 ===
Possible through the PCSX ReARMed core on [[3DS:RetroArch|RetroArch]], with playable speeds on '''New 3DS only'''. A partial compatibility list can be found [https://docs.google.com/spreadsheets/d/1pl2bTkzTe736EOaQjk8FBWY9ixfgoNSYSitbm5Gnyqs/edit#gid=0 here], and optimal configuration can be found [https://www.reddit.com/r/3dshacks/comments/jvkotb/full_speed_psx_finally_here_on_new_3ds_new_2ds_xl/ here].

=== Nintendo 64 ===
''Barely'' possible on '''New 3DS only''' through [[udb:3ds/daedalusx64-3ds|DaedalusX64-3DS]]. A partial compatibility list can be found [https://wiki.gbatemp.net/wiki/DaedalusX64_3DS_Compatibility_List here]; most games are incompatible or run very slowly.

=== Super NES ===
Possible through [[udb:3ds/snes9x|Snes9x for Old 3DS]], which is optimized so that many SNES games can run well on an Old 3DS. New 3DS users can opt to use this emulator or to create virtual console injects that use Nintendo's official SNES emulator.

=== NES / Famicom Disk System ===
The NES is old enough that all models of the 3DS can run it at full speed. The recommended emulator is [[udb:3ds/virtuanes|VirtuaNES]].<br>
Virtual console injects can also be created if you prefer individual icons on HOME Menu.

=== Sega Genesis / CD / 32X / Master System ===
Possible through [[udb:3ds/picodrive|PicoDrive]], covering the Genesis / Mega Drive and its add-ons (the Sega CD and 32X) as well as the Sega Master System. It is apparently reasonably well-optimized for Old 3DS.

== Arcade cabinets ==
WIP

== Home computers ==

=== DOS / Win9x ===
Possible through {{GitHub|MrHuu/dosbox-3ds/releases/latest|DOSBox-3DS}}. Tested mostly on New 3DS. Windows 3.1 and 95 technically ''work'', albeit extremely slowly; this emulator is much more practical for older DOS games.

=== Commodore 64 ===
Possible through [[udb:3ds/vice3ds|Vice3DS]].

== Other ==

=== Calculators ===
''Omega'', a custom firmware for the Numworks graphing calculator, has a simulator available for the Nintendo 3DS. The latest available version (as of 2022/08/09) is available {{GitHub|Omega-Numworks/Omega/releases/download/O1.23.0-E15/simulator.3dsx|here}}.

[https://gbatemp.net/download/wabbitds.7859/ WabbitDS] is a TI-83 Plus emulator for the Nintendo DS. It ''might'' work on the 3DS under TWiLight Menu++ or through a DS flashcart.

== Overview chart ==
WIP

== Emulators that don't exist ==

These are consoles or devices that will not work on the 3DS, usually due to computing power requirements.

* PlayStation 2 and newer
* PlayStation Portable and Vita
* All Xbox consoles
* Dreamcast
* Windows NT (XP/Vista/7/etc)

== Emulating the 3DS itself ==

To emulate the 3DS on another platform, <s>[https://citra-emu.org Citra] is the recommended option.</s> Due to legal action taken by Nintendo, Citra can no longer be used. Other options include [https://mikage.app Mikage] and [https://github.com/wheremyfoodat/Panda3DS Panda3DS].

[[Category:Nintendo 3DS information]]

3DS talk:Wireless streaming

2024-02-15T19:11:16Z

Doge 2: /* NTR streamer fork */ Reply

== NTR streamer fork ==

There is a fork of NTR CFW claims to have optimized streaming so it has much better performance. Should this page be updated to use it instead? https://gbatemp.net/threads/rel-improved-hopefully-ntr-streamer-for-n3ds-xl-ll.644726/ (NTR: [https://github.com/xzn/ntr-hr/releases https://github.com/xzn/ntr-hr]; viewer: [https://github.com/xzn/ntrviewer-hr/releases https://github.com/xzn/ntrviewer-hr]) [[User:Ihaveahax|ihaveahax]] ([[User talk:Ihaveahax|talk]]) 02:20, 22 January 2024 (UTC)

:I don't see any issues adding this as an option to the wiki, it seems rather stable in my testing. (New 3DS LL, Pokemon Ultra Sun, quality 50, QoS 2.500 MBps) [[User:Doge 2|Doge 2]] ([[User talk:Doge 2|talk]]) 19:11, 15 February 2024 (UTC)

3DS:RTD

2024-02-10T17:05:32Z

Doge 2: redirect to rebuild title database

#REDIRECT [[3DS:Rebuild_Title_Database]]

3DS:Troubleshooting/Finalizing Setup (Manual)

2024-02-01T23:46:24Z

Doge 2: fix ftpd link with direct download to 3.1.0

==Required Reading==

This is a manual version of the [[3dsguide:finalizing-setup|Finalizing Setup]] section of the guide, for when all other options have been exhausted and the script does not work.

==What You Need==

*The latest release of {{GitHub|Steveice10/FBI/releases/latest|FBI}} (Both <code>FBI.3dsx</code> and <code>FBI.cia</code>)
*The latest release of {{GitHub|astronautlevel2/Anemone3DS/releases/download/v2.3.1/Anemone3DS.cia|Anemone3DS}} (direct download)
*The latest release of [https://github.com/mtheall/ftpd/releases/download/v3.1.0/ftpd.cia FTPD] (direct download)
*The v3.7.4 release of {{GitHub|BernardoGiordano/Checkpoint/releases/download/v3.7.4/Checkpoint.cia|Checkpoint}} (direct download)
*The latest release of {{GitHub|PabloMK7/homebrew_launcher_dummy/releases/download/v1.0/Homebrew_Launcher.cia|HBL Launcher Wrapper}} (direct download)
*The latest release of {{GitHub|Universal-Team/Universal-Updater/releases/download/v3.2.6/Universal-Updater.cia|Universal-Updater}} (direct download)
*The latest release of {{GitHub|d0k3/GodMode9/releases/download/v2.1.1/GodMode9-v2.1.1-20220322194259.zip|GodMode9}} (direct download)

==Instructions==

===Section I - Prep Work===

# Power off your device
# Insert your SD card into your computer
# Create the folder <code>sd:/3ds</code>
#* You may already have this from a earlier section in the guide.
# Place <code>FBI.3dsx</code> into <code>sd:/3ds/</code>
# Create the folder <code>sd:/cias/</code>
# Place <code>FBI.cia</code>, <code>Universal-Updater.cia</code>, <code>Anemone3DS.cia</code>, <code>ftpd.cia</code>, <code>hblauncher_loader.cia</code>, and <code>Checkpoint.cia</code> into <code>sd:/cias</code>
# Create the folder <code>sd:/luma/payloads/</code>
# Copy <code>GodMode9.firm</code> from the GodMode9 zip file into <code>sd:/luma/payloads/</code>
# Copy the <code>gm9</code> folder from the GodMode9 zip file to the root of your sd card
# Eject the SD card from your computer, then remove it
# Reinsert the SD card into your console

===Section II - CFW Check===

# Hold {{B|SELECT}}, and while holding {{B|SELECT}}, power on the console
#* If the check was successful, your console should have booted into the Luma3DS configuration menu
# Press {{B|START}} to save and reboot
# Power off your console
{{critical|text=If you do NOT boot into the Luma3DS configuration menu, custom firmware was not installed on your console. Join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help}}

=== Section III - Updating the System===

# Update your console by going to System Settings, then “Other Settings”, then going all the way to the right and using “System Update”
#* Updates while using B9S + Luma (what you have) are safe
#* The updater may display a message saying “Your system is up to date” instead of updating. This is normal if you are already up to date; continue to the next section
#* If this gives you an error, set both your DNS settings and Proxy settings to “Auto”
#* If this still gives you an error, follow [[3dsguide:troubleshooting#finalizing-setup|this troubleshooting guide]]

=== Section IV - RTC and DSP setup ===

# Close '''System Settings'''
# Press {{B|L|Down|SELECT}} at the same time to open the Rosalina menu
#* If one of these buttons is broken, download this [[3dsguide:assets/config.ini|config.ini]] and put it in <code>sd:/luma</code>, replacing the existing one. This will change the Rosalina menu key combination to {{B|X|Y}}
# Select “Miscellaneous options”
# Select “Dump DSP firmware”
# Press {{B|B}} to continue
# Select “Nullify user time offset”
# Press {{B|B}} to continue
# Press {{B|B}} to return to the Rosalina main menu
# Press {{B|B}} to exit the Rosalina menu

=== Section V - CIA Installation ===

# Open the '''Activity Log'''
# Press {{B|L|Down|SELECT}} at the same time to open the Rosalina menu
# Select “Miscellaneous options”
# Select “Switch the hb title to the current app”
# Press {{B|B}} to continue
# Press {{B|B}} twice to return to the Rosalina main menu
# Press {{B|B}} to exit the Rosalina menu
# Close '''Activity Log'''
# Reopen '''Activity Log'''
#* This should open the '''Homebrew Launcher'''
# Open '''FBI''' from the list of homebrew
# Select <code>SD</code>, then click <code>cias</code>
# Select the <code>Current directory</code> option, then choose to <code>Install and delete all CIAs</code>
# Close '''FBI'''
#* Six new applications should be on the home menu.

=== Section VI - NAND Backup and CTRNAND Luma/GM9 ===

# Power off your console
# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your console. This will launch GodMode9
#* If you do not boot into GodMode9, ensure that you copied <code>GodMode9.firm</code> into <code>sd:/luma/payloads/</code> and that the folders are not misnamed (e.g. luna, lumas, playloads, payload.)
#* If you are prompted to create an essential files backup, press {{B|A}} to do so, then press {{B|A}} to continue once it has completed.
#* If you are prompted to fix the RTC date&time, press {{B|A}} to do so, then set the date and time, then press {{B|A}} to continue.
# Press {{B|Home}} to bring up the action menu
# Select <code>Scripts…</code>
# Select '''GM9Megascript'''
# Select <code>Backup Options</code>
# Press {{B|A}} to confirm
#* The NAND backup process may take up to 20 minutes.
# Press {{B|B}} to exit to the main menu of '''GM9Megascript'''
# Select <code>Scripts from Plailect’s Guide</code>
# Select <code>Setup Luma3DS to CTRNAND</code>
# When prompted, press {{B|A}} to proceed
# Press {{B|A}} to unlock writing to SysNAND (lvl1), then input the key combo given
# Press {{B|A}} to continue
# Press {{B|B}} twice to exit '''GM9Megascript'''
# Hold {{B|R}} and press {{B|START}} to power off your console
# Insert your SD card into your computer
# Copy the contents of <code>sd:/gm9/out/</code> to a safe location on your computer
#* These files are critical backups and should be backed up to multiple locations (i.e. cloud storage) if possible
#* The two SysNAND files are your NAND backup and can be used to revert your console to a working state if it is bricked by a software issue
#* The <code>essentials.exefs</code> file contains your console’s system-unique files and can be used to recover your data in the event of a hardware failure
# If you still have them, delete the two SysNAND files from <code>sd:/gm9/out/</code> from your SD card
#* The <code>essential.exefs</code> file is small and may be kept on your SD card for ease of access

----

{{success|text=You’re done! Custom firmware is now fully configured on your console.}}

{{info|text=
<b>Information and Notes</b>
Here are some key combos that you should know:

*Holding {{B|SELECT}} on boot will launch the Luma3DS configuration menu.
*Holding {{B|START}} on boot will launch GodMode9, or if you have multiple payloads in <code>sd:/luma/payloads/</code>, the Luma3DS chainloader.
*By default, pressing {{B|L|Down|SELECT}} while in 3DS mode will open the Rosalina menu, where you can check system information, take screenshots, enable cheats, and more. This can be changed from the Rosalina menu.
**If you have a modified Luma config, this key combination may be {{B|X|Y}} instead.
*Holding {{B|START|SELECT|X}} on boot will make the notification LED show a color for debug purposes. See [[3DS:Boot9strap#LED_Status_Codes|here]] for what each color means.
}}
{{info|text=See [[3DS:Things to do|here]] for some suggestions on things to do with custom firmware.}}

{{info|text=For information on using GodMode9’s various features, check out the [[3DS:GodMode9/Usage|GodMode9 Usage]] and [[3DS:Dump titles and game cartridges|Dumping Titles and Game Cartridges]] pages.}}

3DS:Bmbt3DS

2024-02-01T17:32:41Z

Doge 2: change to redirect for bmbt3DS

#REDIRECT [[3DS:Bmbt3DS]]

3DS:Bmbt3DS

2024-01-31T19:40:39Z

Doge 2: add tabber for boot9strap, fastboot3DS, ntrboot, godmode9 and luma3ds chainloader (thanks for the suggestion blue!)

{{Infobox homebrew
| for3ds = 1
| forwiiu = 0
| forswitch = 0
| forwii = 0
| developers = Gruetzig
| version = bmbt3DS +1
| releasedate = 2023-06-07
| github = Gruetzig/bmbt3ds
| forwindows = 0
| formac = 0
| forlinux = 0
| forjava = 0
}}

BMBT3DS is a bare metal button testing <code>.firm</code> payload for the Nintendo 3DS. It can be used to test all buttons on the console, and to see if one is being held down or not.

==Instructions==

===What you will need===

*[[3DS:Boot9strap|boot9strap]], [[3DS:GodMode9|GodMode9]] or [[3DS:Fastboot3DS|fastboot3DS]] installed to the FIRM partition(s)
*[[3DS:Luma3DS|Luma3DS]]' <code>boot.firm</code> on the root of your SD card
*The latest release of [https://github.com/Gruetzig/bmbt3ds/releases/latest bmbt3DS] (the <code>bmbt3ds.firm</code> file)

===Section I - Running the test===
<tabber>
|-|boot9strap=

<span>
# Power off your console
# Remove the SD card from your console and insert it into your computer
# Copy <code>bmbt3ds.firm</code> to the root of your SD Card
# Rename <code>boot.firm</code> to <code>luma.firm</code>
# Rename <code>bmbt3ds.firm</code> to <code>boot.firm</code>
# Safely eject the SD card from your computer and reinsert it into your console
# Power on the console without pressing any buttons
{{Info|text=This payload does not show anything on either screens until a button is pressed. Refer to the attached image for what parts of the screen will light up for each button pressed.|image=[[File:Bmbt.png|384px]]}}
# Press each button once, verifying that the corresponding button shows up on the top screen. If it does not show up, the button pressed may be faulty. If you see a constant white square for one button and you are '''not''' holding the button down, that button may be stuck and could be the source of some issues.
# Once you are finished with the button tester, press the power button once to power off the console
# Remove the SD card from your console and insert it into your computer
# Delete <code>boot.firm</code> from the root of your SD card
# Rename <code>luma.firm</code> to <code>boot.firm</code>
# Safely eject the SD card from your computer and reinsert it into your console
# Power on your console
{{Success|text=If all went well, you have successfully tested the buttons on your console.}}
</span>

|-|fastboot3DS=

<span>
# Power off your console
# Remove the SD card from your console and insert it into your computer
# Copy <code>bmbt3ds.firm</code> to the root of your SD Card
# Safely eject the SD card from your computer and reinsert it into your console
# Power on the console while holding {{B|HOME}} to enter the fastboot3DS menu
# Select <code>[+]Boot from file...</code> -> <code>sdmc:</code> -> <code>bmbt3ds.firm</code>
{{Info|text=This payload does not show anything on either screens until a button is pressed. Refer to the attached image for what parts of the screen will light up for each button pressed.|image=[[File:Bmbt.png|384px]]}}
# Press each button once, verifying that the corresponding button shows up on the top screen. If it does not show up, the button pressed may be faulty. If you see a constant white square for one button and you are '''not''' holding the button down, that button may be stuck and could be the source of some issues.
# Once you are finished with the button tester, press the power button once to power off the console
# Remove the SD card from your console and insert it into your computer
# Delete <code>bmbt3ds.firm</code> from the root of your SD card
# Safely eject the SD card from your computer and reinsert it into your console
# Power on your console
{{Success|text=If all went well, you have successfully tested the buttons on your console.}}
</span>

|-|ntrboot=
{{warning|text=If you do not have a flashcart compatible with ntrboot, please choose another option.}}
<span>
# Power off your console
# Remove the SD card from your console and insert it into your computer
# Copy <code>bmbt3ds.firm</code> to the root of your SD Card
# Rename <code>boot.firm</code> to <code>luma.firm</code>
# Rename <code>bmbt3ds.firm</code> to <code>boot.firm</code>
# Safely eject the SD card from your computer and reinsert it into your console
# Insert the flashcart flashed with ntrboot into your console
# Put the magnet into position to trigger the lid sensor. Refer to [https://i.imgur.com/5e3lKe2.png this image for reference]
#* Note, 2DS users will not need a magnet, as their device cannot physically fold. Instead, move the sleep switch to the right
# Press and hold {{Key press|START|SELECT|X}}, then briefly press and hold the power button for 2 to 3 seconds
# Your console should now be booted into BMBT.
#* If it did not boot and instead booted into the HOME Menu or turned off immediately, power off your console and try again. You may need a few attempts to get the magnet positioning correct.
{{Info|text=This payload does not show anything on either screens until a button is pressed. Refer to the attached image for what parts of the screen will light up for each button pressed.|image=[[File:Bmbt.png|384px]]}}
# Press each button once, verifying that the corresponding button shows up on the top screen. If it does not show up, the button pressed may be faulty. If you see a constant white square for one button and you are '''not''' holding the button down, that button may be stuck and could be the source of some issues.
# Once you are finished with the button tester, press the power button once to power off the console
# Remove the SD card from your console and insert it into your computer
# Delete <code>boot.firm</code> from the root of your SD card
# Rename <code>luma.firm</code> to <code>boot.firm</code>
# Safely eject the SD card from your computer and reinsert it into your console
# Power on your console
{{Success|text=If all went well, you have successfully tested the buttons on your console.}}
</span>

|-|GodMode9=
{{warning|text=This section only applies to consoles with GodMode9 installed into FIRM0/1.}}
<span>
# Power off your console
# Remove the SD card from your console and insert it into your computer
# Copy <code>bmbt3ds.firm</code> to the <code>sd:/gm9/payloads</code> folder on your SD card
# Reinsert the SD card into your console
# Power on the console while holding {{Key press|R|LEFT}} to enter the GodMode9 bootloader menu
# Select <code>Select payload...</code> -> <code>bmbt3ds.firm</code>
{{Info|text=This payload does not show anything on either screens until a button is pressed. Refer to the attached image for what parts of the screen will light up for each button pressed.|image=[[File:Bmbt.png|384px]]}}
# Press each button once, verifying that the corresponding button shows up on the top screen. If it does not show up, the button pressed may be faulty. If you see a constant white square for one button and you are '''not''' holding the button down, that button may be stuck and could be the source of some issues.
# Once you are finished with the button tester, press the power button once to power off the console
{{Success|text=If all went well, you have successfully tested the buttons on your console.}}
</span>

|-|Luma3DS chainloader=

<span>
# Power off your console
# Remove the SD card from your console and insert it into your computer
# Copy <code>bmbt3ds.firm</code> to the <code>sd:/luma/payloads</code> folder on your SD card
# Reinsert the SD card into your console
# Power on the console while holding {{B|START}} to open Luma3DS chainloader
#* If you dont see Luma3DS chainloader, follow [[3dsguide:restoring-updating-cfw.html|Restoring / Updating CFW]] and try again
#* If you still don't see it, follow the boot9strap tab above instead
# Select <code>bmbt3ds.firm</code>
{{Info|text=This payload does not show anything on either screens until a button is pressed. Refer to the attached image for what parts of the screen will light up for each button pressed.|image=[[File:Bmbt.png|384px]]}}
# Press each button once, verifying that the corresponding button shows up on the top screen. If it does not show up, the button pressed may be faulty. If you see a constant white square for one button and you are '''not''' holding the button down, that button may be stuck and could be the source of some issues.
# Once you are finished with the button tester, press the power button once to power off the console
{{Success|text=If all went well, you have successfully tested the buttons on your console.}}
</span>
</tabber>{{Short description|Bare-metal button tester for the 3DS}}

3DS:Bmbt3ds

2024-01-29T13:37:45Z

Doge 2: redirect

#REDIRECT [[3DS:BMBT]]

3DS:Bmbt3DS

2024-01-29T13:33:25Z

Doge 2: initial commit

File:Bmbt.png

2024-01-29T13:25:28Z

Doge 2: bmbt3DS button layout

== Summary ==
bmbt3DS button layout

3DS:3dsgba

2024-01-24T16:00:43Z

Doge 2: redirect

#REDIRECT [[3DS:GBA games]]

3DS:GodMode9/Usage

2024-01-18T19:57:59Z

Doge 2: add notice about initialization errors

{{TOC right}}{{info|text=For information on dumping cartridges or SD card content, see [[3DS:Dump titles and game cartridges]].}}
{{info|text=For support (in English) with GodMode9, as well as help with scripting and to get updates and info, join [https://discord.gg/BRcbvtFxX4 GodMode9 on Discord].}}

[[3DS:GodMode9|GodMode9]] is a full access file browser for the Nintendo 3DS console, giving you access to your SD card, the FAT partitions inside your SysNAND and EmuNAND, and basically anything else. Among other functionality, you can copy, delete, rename files, and create folders.

Note that if you have any payload files other than <code>GodMode9.firm</code> in the <code>/luma/payloads/</code> folder on your SD card, holding {{B|Start}} on boot will display a "chainloader menu" where you will have to use the D-Pad and the {{B|A}} button to select "GodMode9" for these instructions.

GodMode9 is powerful software that has the capability to modify essentially anything on your console. Though many of these modifications are locked behind a permissions system, and it is impossible to accidentally perform dangerous actions without deliberately unlocking permissions, you should still follow instructions carefully and keep backups just in case.

== Updating GodMode9 ==
{{info|text=Some of the instructions below are only applicable to the latest version of GodMode9, and as such you should follow this section to update your copy before continuing. Overwrite any existing files.}}

=== What You Need ===
* The latest release of {{GitHub|d0k3/GodMode9/releases/latest|GodMode9}} (the GodMode9 <code>.zip</code> file)

=== Instructions ===

# Power off your device
# Insert your SD card into your computer
# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads</code> folder on your SD card
# Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
# Reinsert your SD card into your device

{{success|text=GodMode9 is now up to date.}}

== Creating a NAND Backup ==
# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Press {{B|Home}} to bring up the action menu
# Select "Scripts..."
# Select "GM9Megascript"
# Select "Backup Options"
# Select "SysNAND Backup"
# Press {{B|A}} to confirm
#* This process will take some time
#* If you get an error, make sure that you have at least 1.3GB of free space on your SD card
# Press {{B|A}} to continue
# Press {{B|B}} to return to the main menu
# Select "Exit"
# Press {{B|A}} to relock write permissions if prompted
# Hold {{B|R}} and press {{B|Start}} while still holding {{B|R}} to power off your device

{{success|text=Your NAND backup has been successfully created. You can find it in <code>/gm9/out/</code> under the name <code><date>_<serialnumber>_sysnand_###.bin</code>, along with its accompanying checksum (<code>.sha</code>) file. You will probably want to back up these files to somewhere safe, then delete them from your SD card to reclaim the space.}}

== Restoring a NAND backup ==
# Power off your device
# Insert your SD card into your computer
# Copy <code><date>_<serialnumber>_sysnand_###.bin</code> from your computer to the <code>/gm9/out/</code> folder on your SD card
# Reinsert your SD card into your device
# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Press {{B|Home}} to bring up the action menu
# Select "Scripts..."
# Select "GM9Megascript"
# Select "Restore Options"
# Select "SysNAND Restore (safe)"
# Select your NAND backup
# Press {{B|A}} to unlock SysNAND (lvl3) writing, then input the key combo given
#* This will '''not''' overwrite your boot9strap installation
#* This process will take some time
# Press {{B|A}} to continue
# Press {{B|B}} to return to the main menu
# Select "Exit"
# Press {{B|A}} to relock write permissions if prompted
# Hold {{B|R}} and press {{B|Start}} at while still holding {{B|R}} to power off your device

{{success|text=Your NAND backup has been successfully restored. You can now delete <code><date>_<serialnumber>_sysnand_###.bin</code> from your SD card.}}

== Injecting any .CIA app into Health & Safety ==

{{info|text=Note that you cannot inject something that is larger than Health & Safety. You'll only be able to install inject relatively small homebrew (no retail games).}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Navigate to the location of your <code>.cia</code> file
# Press {{B|A}} on the <code>.cia</code> file to select it
# Select "CIA image options..."
# Select "Mount image to drive"
# Press {{B|A}} on the <code>.app</code> file
# Select "NCCH image options
# Select "Inject to H&S"
# Press {{B|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
# Press {{B|A}} to continue
# Press {{B|A}} to relock write permissions if prompted

{{success|text=Your desired application has now been injected into Health & Safety.}}

== Restoring Health & Safety after injecting a .CIA app ==

{{info|text=This will only work if you performed the initial injection with GodMode9. If you've been following this page, then you did it with GodMode9.}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Press {{B|Home}} to bring up the action menu
# Select "More..."
# Select "Restore H&S"
# Press {{B|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
# Press {{B|A}} to relock write permissions if prompted

{{success|text=Health & Safety has been reverted to normal.}}

== Format an SD card ==

{{critical|text=This will erase the contents of your SD card!}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Press {{B|R|B}} to unmount the current SD card and insert the one you want to format{{Info|text=If GodMode9 shows an initialization error when inserting the SD Card to be formatted, it can safely be dismissed.}}
# Press {{B|Home}} to bring up the action menu
# Select "More..."
# Select "SD format menu"
# Select an EmuNAND option if you wish to use one
#* If you don't know what it is or have no legitimate use for it, select "No EmuNAND"
# Select "Auto"
# Press {{B|A}} to accept the label <code>GM9SD</code>
#* You can input a custom name if you want
# When prompted, input the key combo given to confirm the format

{{success|text=Your SD card has successfully been formatted for use with the 3DS.}}

== Removing an NNID without formatting your device ==

{{info|text=This process will only log you out of your NNID. You will still not be able to use the NNID on another console, as the NNID remains linked to the console.}}

# Press and hold {{B|Start}}, and while holding {{B|Start}}, power on your device. This will launch GodMode9
# Press {{B|Home}} to bring up the action menu
# Select "Scripts..."
# Select "GM9Megascript"
# Select "Scripts from Plailect's Guide"
# Select "Remove NNID"
# Press {{B|A}} to continue
# Press {{B|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
# Press {{B|A}} to continue
# Press {{B|B}} to return to the main menu
# Select "Exit"
# Press {{B|A}} to relock write permissions if prompted
# Press {{B|Start}} to reboot your device

{{success|text=You have now been logged out of your NNID.}}

{{hg imported}}

[[Category:Nintendo 3DS guides]]

Nintendo 3DS and Wii U online shutdown and homebrew FAQ

2023-12-09T20:42:41Z

Doge 2: minor grammar changes

{{Page WIP|notes=
* Needs more Wii U-focused info, as I am only knowledgeable about 3DS
}}{{ambox|text=Anyone is free to edit this draft!}}This page answers frequently asked questions about the discontinuation of online services for the Nintendo 3DS and Wii U in April 2024 and its relation to homebrew.

[https://en-americas-support.nintendo.com/app/answers/detail/a_id/63227/~/announcement-of-discontinuation-of-online-services-for-nintendo-3ds-and-wii-u Read the official announcement] on Nintendo Support.

== Will homebrew let me continue to play online? ==
The official servers will be going down permanently for everyone, homebrew will not grant you access to them. Instead, an alternate network, [https://pretendo.network Pretendo Network], is in development.

== Can I use Pretendo Network without hacking? ==
No, homebrew is required to play on Pretendo Network or any unofficial servers.

== Will Pretendo Network work on Tiramisu? ==
No, Pretendo has ended support for Tiramisu. You will need to use the Aroma environment to install it.

== Can I still set up homebrew after the shutdown? ==
Yes, but certain exploits that depend on online services may not be available, such as Seedminer, which requires use of the Friend List.

== What happens to the eShop? ==
Nintendo eShop is likely to stay available for downloading game updates and past purchases for a long time. Similarly, the Wii Shop Channel and DSi Shop are still online to download purchases many years later.

== Will I still be able to update? ==
Just like the eShop, update servers are most likely going to be still accessible after the shutdown. Consoles like the Wii are still able to be updated. It is still recommended to update if CFW is installed on the console.

== What about Pokémon Bank? ==
Pokémon Bank and Poké Transporter will still work after the shutdown, but it is recommended to transfer to Pokémon HOME as early as possible, as it may not stay available for long<ref>https://twitter.com/playpokemon/status/1709614360904004012 ([https://web.archive.org/web/20231005083547/https://twitter.com/playpokemon/status/1709614360904004012 archive])</ref>.

== References ==
<references />

Switch:Atmosphere

2023-12-03T03:40:51Z

Doge 2: initial commit, wip

Atmosphere is a work in progress custom firmware for the Nintendo Switch. It is extremely modular, has a built in cheat engine, and highly configurable.
{{Page WIP}}
==Installation==
{{Infobox homebrew
| image = Atmosphere logo.png
| imagealt = Atmosphere logo
| for3ds = 0
| forwiiu = 0
| forswitch = 1
| forwii = 0
| developers = ReSwitched Team
| version = 1.6.2
| releasedate = 2023-10-27
| github = Atmosphere-NX/Atmosphere
| forwindows = 0
| formac = 0
| forlinux = 0
| forjava = 0
}}

#Power off your Nintendo Switch and eject the microSD Card
#Insert the microSD card into your computer
#Download the latest release zip of [https://github.com/Atmosphere-NX/Atmosphere/releases/latest Atmosphere], along with the <code>fusee.bin</code> file
#*This file will be used to launch Atmosphere
#Extract the contents of the Atmosphere zip to the root of your microSD Card
#Eject the microSD Card from your computer and reinsert it into your Nintendo Switch

== Booting Atmosphere ==

# Put your Nintendo Switch into RCM mode using your preferred method of choice
#Push the <code>fusee.bin</code> payload using your payload launcher of choice
#You are now running Atmosphere!

File:Atmosphere logo.png

2023-12-03T03:22:26Z

Doge 2: Atmosphere logo

== Summary ==
Atmosphere logo

Switch:Hekate

2023-11-30T23:38:04Z

Doge 2: initial commit, wip

Hekate is a custom bootloader for the Nintendo Switch that allows you to perform various CFW related tasks.
{{Page WIP}}
{{Infobox homebrew
| image = Hekate.png
| imagealt = Hekate IPL Custom NX Bootloader
| for3ds = 0
| forwiiu = 0
| forswitch = 1
| forwii = 0
| developers = CTCaer
| version = 6.0.7
| releasedate = 2023-10-13
| github = https://github.com/CTCaer/hekate
| forwindows = 0
| formac = 0
| forlinux = 0
| forjava = 0
}}

==Installing/updating Hekate==

#Power off your Nintendo Switch
#Insert the microSD card into your computer
#Download the [https://github.com/CTCaer/hekate/releases/latest latest release] of Hekate. it should be named <code>hekate_ctcaer_x.x.x_Nyx_x.x.x.zip</code>
#Open the archive and extract the <code>bootloader</code> folder to the root of your microSD card, overwriting if asked. Then copy the <code>hekate_ctcaer_x.x.x.bin</code> to your computer
#Eject your microSD card from your computer and reinsert it into your Nintendo Switch

== Booting Hekate ==

# Put your Nintendo Switch into RCM mode using your preferred method
# Push the <code>hekate_ctcaer_x.x.x.bin</code> payload using your payload launcher of choice

3DS:Alternate Exploits/Old Finalizing Setup

2023-11-30T22:43:35Z

Doge 2: should probably put sd card in computer to replace firm and 3dsx

==Required Reading==
The file <code>boot.firm</code> is what is launched by boot9strap itself after it finishes loading off of NAND. In this case, we are using Luma3DS by LumaTeam to patch the console, allowing it to run homebrew software.

This guide will have you make critical system file backups and install the following homebrew programs:

*[[3DS:FBI|FBI]] ''(installs CIA formatted applications)''
*[[3DS:Anemone3DS|Anemone3DS]] ''(installs custom themes)''
*[[Checkpoint]] ''(backs up and restores save files for 3DS and DS games)''
*[[3DS:Universal-Updater|Universal-Updater]] ''(a homebrew app store for downloading homebrew from the 3DS over Wi-Fi)''
*[[3DS:GodMode9|GodMode9]] ''(multipurpose tool which can do NAND and cartridge functions)''
*'''Homebrew Launcher Loader''' ''(launches the Homebrew Launcher)''

==What You Need==
*The latest release of [https://github.com/astronautlevel2/Anemone3DS/releases/latest Anemone3DS] (the <code>.cia</code> file)
*The v3.7.4 release of [https://github.com/BernardoGiordano/Checkpoint/releases/latest Checkpoint] (the <code>.cia</code> file)
*The latest release of [https://github.com/PabloMK7/homebrew_launcher_dummy/releases/latest Homebrew Launcher Wrapper] (the <code>.cia</code> file)
*The latest release of [https://github.com/Universal-Team/Universal-Updater/releases/latest Universal-Updater] (the <code>.cia</code> file)
*The latest release of [https://github.com/Steveice10/FBI/releases FBI] ('''both''' the <code>.cia</code> and <code>.3dsx</code> files)
*The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9] (the GodMode9 <code>.zip</code> file)

==Instructions==

===Section I - Prep Work===
In this section, you will copy the files necessary to follow the rest of the instructions on this page.

#Power off your console
#Insert your SD card into your computer
#Create a folder named <code>cias</code> on the root of your SD card if it does not already exist
#Copy all of the CIA files (<code>Anemone3DS.cia</code>, <code>Checkpoint.cia</code>, <code>FBI.cia</code>, <code>Homebrew_Launcher.cia</code>, and <code>Universal-Updater.cia</code>) you downloaded earlier to the <code>/cias/</code> folder on your SD card
#Create a folder named <code>3ds</code> on the root of your SD card if it does not already exist
#*This folder stores homebrew applications and data; it is different from the <code>Nintendo 3DS</code> folder that the console automatically generates
#Copy <code>FBI.3dsx</code> to the <code>/3ds/</code> folder on your SD card
#Create a folder named <code>payloads</code> in the <code>luma</code> folder on your SD card if it does not already exist
#Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
#Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
#Reinsert your SD card into your console
#Power on your console

===Section II - Updating the System===
In this section, you will update your system to the latest version, which is safe to do with custom firmware.

#Update your console by going to System Settings, then “Other Settings”, then going all the way to the right and using “System Update”
#*Updates while using B9S + Luma (what you have) are safe
#*You may get a message saying “Your system is up to date” instead of updating. This is normal if you are already up to date; continue with the next section
#*If this gives you an error, ensure your DNS is set to "Auto-obtain", and Proxy Settings are set to “Do Not Use”
#*If this still gives you an error, [https://web.archive.org/web/20230319181423/https://3ds.hacks.guide/troubleshooting#finalizing-setup follow this troubleshooting guide]

===Section III - Homebrew Launcher===
In this section, you will temporarily replace Download Play with Homebrew Launcher (which we need to launch FBI). Download Play will automatically go back to normal once you reboot your console.

#Launch the Download Play application
#Wait until you see the <code>Nintendo 3DS</code> and <code>Nintendo DS</code> buttons
#Press {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} at the same time to open the Rosalina menu
#Select “Miscellaneous options”
#Select “Switch the hb. title to the current app.”
#Press {{Key press|B}} to continue
#Press {{Key press|B}} to return to the Rosalina main menu
#Press {{Key press|B}} to exit the Rosalina menu
#Press {{Key press|Home}}, then close Download Play
#Launch the Download Play application
#Your console should load the Homebrew Launcher
#*If your console is stuck on the loading splash screen or crashes to a screen with white text, you are missing <code>boot.3dsx</code> on the root of your SD card or it is not inserted into your console. To fix this, turn off your console, insert your SD card into your computer, download the latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] and extract <code>boot.firm</code> and <code>boot.3dsx</code> to the root of your SD card, overwriting if asked, and try again

===Section IV - RTC and DSP Setup===
In this section, you will sync your 3DS internal clock with the actual time and dump the sound firmware (which is necesssary for some homebrew software to use sound properly).

#Press {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} at the same time to open the Rosalina menu
#Select “Miscellaneous options”
#Select “Dump DSP firmware”
#Press {{Key press|B}} to continue
#Select “Nullify user time offset”
#Press {{Key press|B}} to continue
#Press {{Key press|B}} to return to the Rosalina main menu
#Press {{Key press|B}} to exit the Rosalina menu
===Section V - Installing CIAs===
In this section, you will install several useful homebrew applications to HOME Menu.

#Launch FBI from the list of homebrew
#Navigate to <code>SD</code> -> <code>cias</code>
#Select “<current directory>”
#Select the “Install and delete all CIAs” option, then press (A) to confirm
#Press {{Key press|Home}}, then {{Key press|X}} to close Download Play

===Section VI - CTRNAND Luma3DS===
In this section, you will use a script to copy some of Luma3DS’s files to internal memory so that they can be accessed, even without an SD card inserted.

#Power off your console
#Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
#* If you boot to Luma3DS Chainloader, select GodMode9
#** If you do not boot into GodMode9, ensure that <code>GodMode9.firm</code> is in <code>/luma/payloads/</code> and that <code>payloads</code> is correctly spelled
#If you are prompted to create an essential files backup, press {{Key press|A}} to do so, then press {{Key press|A}} to continue once it has completed
#If you are prompted to fix the RTC date&time, press {{Key press|A}} to do so, set the date and time, then press {{Key press|A}} to continue
#Press {{Key press|Home}} to bring up the action menu
#Select “Scripts…”
#Select “GM9Megascript”
#Select “Scripts from Plailect’s Guide”
#Select “Setup Luma3DS to CTRNAND”
#When prompted, press {{Key press|A}} to proceed
#Press {{Key press|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
#Press {{Key press|A}} to continue

===Section VII - Cleanup SD Card===
In this section, you will use a script to remove some unnecessary files from your SD card.

#When prompted, press {{Key press|A}} to proceed
#Press {{Key press|A}} to continue
#Press {{Key press|B}} to return to the main menu

===Section VIII - Backup Essential Files===
In this section, you will make backups of files that can be used to recover from software bricks or to recover data.

#Select “Backup Options”
#Select “SysNAND Backup”
#Press {{Key press|A}} to confirm
#*This process will take some time
#*If you get an error, look for your issue in the troubleshooting guide
#Press {{Key press|A}} to continue
#Press {{Key press|B}} to return to the main menu
#Select “Exit”
#Press {{Key press|A}} to relock write permissions if prompted
#Navigate to <code>[S:] SYSNAND VIRTUAL</code>
#Press {{Key press|A}} on <code>essential.exefs</code> to select it
#Select “Copy to 0:/gm9/out”
#*If you see “Destination already exists”, press {{Key press|A}} on “Overwrite file(s)”
#Press {{Key press|A}} to continue
#Press {{Key press|Home}} to bring up the action menu
#Select “Poweroff system” to power off your console
#Insert your SD card into your computer
#Copy <code><date>_<serialnumber>_sysnand_##.bin</code>, <code><date>_<serialnumber>_sysnand_##.bin.sha</code>, and <code>essential.exefs</code> from the <code>/gm9/out/</code> folder on your SD card to a safe location on your computer
#*Copy these backups to multiple locations (such as online file storage, an external hard drive, etc.)
#*These backups will save you from a brick and/or help you recover files from the NAND image if anything goes wrong in the future
#Delete <code><date>_<serialnumber>_sysnand_##.bin</code> and <code><date>_<serialnumber>_sysnand_##.bin.sha</code> from the <code>/gm9/out/</code> folder on your SD card after copying it
#*The other backup files are negligible in size and may be kept on your SD card for ease of access
#If you have it, copy the <code>/luma/backups/</code> folder on your SD card to a safe location on your computer
#Reinsert your SD card into your console
#Power on your console

----
{{success|text=You’re done! Custom firmware is now fully configured on your console.}}

{{info|text=
<b>Information and Notes</b>
Here are some key combos that you should know:

*Holding {{Key press|Select}} on boot will launch the Luma3DS configuration menu.
*Holding {{Key press|Start}} on boot will launch GodMode9, or if you have multiple payloads in <code>/luma/payloads/</code>, the Luma3DS chainloader.
*By default, pressing {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} while in 3DS mode will open the Rosalina menu, where you can check system information, take screenshots, enable cheats, and more. This can be changed from the Rosalina menu.
**If you have a modified Luma config, this key combination may be {{Key press|X}} + {{Key press|Y}} instead.
*Holding {{Key press|Start}} + {{Key press|Select}} + {{Key press|X}} on boot will make the notification LED show a color for debug purposes. See [[3DS:Boot9strap|here]] for what each color means.
}}
{{info|text=See [https://wiki.hacks.guide/wiki/3DS:Things_to_do here] for some suggestions on things to do with custom firmware.}}

{{info|text=For information on using GodMode9’s various features, check out the [[3DS:GodMode9/Usage|GodMode9 Usage]] and [[3DS:Dump titles and game cartridges|Dumping Titles and Game Cartridges]] pages.}}

3DS:Alternate Exploits/Old Finalizing Setup

2023-11-30T21:26:32Z

Doge 2: change 3ds-hbmenu for luma

==Required Reading==
The file <code>boot.firm</code> is what is launched by boot9strap itself after it finishes loading off of NAND. In this case, we are using Luma3DS by LumaTeam to patch the console, allowing it to run homebrew software.

This guide will have you make critical system file backups and install the following homebrew programs:

*[[3DS:FBI|FBI]] ''(installs CIA formatted applications)''
*[[3DS:Anemone3DS|Anemone3DS]] ''(installs custom themes)''
*[[Checkpoint]] ''(backs up and restores save files for 3DS and DS games)''
*[[3DS:Universal-Updater|Universal-Updater]] ''(a homebrew app store for downloading homebrew from the 3DS over Wi-Fi)''
*[[3DS:GodMode9|GodMode9]] ''(multipurpose tool which can do NAND and cartridge functions)''
*'''Homebrew Launcher Loader''' ''(launches the Homebrew Launcher)''

==What You Need==
*The latest release of [https://github.com/astronautlevel2/Anemone3DS/releases/latest Anemone3DS] (the <code>.cia</code> file)
*The v3.7.4 release of [https://github.com/BernardoGiordano/Checkpoint/releases/latest Checkpoint] (the <code>.cia</code> file)
*The latest release of [https://github.com/PabloMK7/homebrew_launcher_dummy/releases/latest Homebrew Launcher Wrapper] (the <code>.cia</code> file)
*The latest release of [https://github.com/Universal-Team/Universal-Updater/releases/latest Universal-Updater] (the <code>.cia</code> file)
*The latest release of [https://github.com/Steveice10/FBI/releases FBI] ('''both''' the <code>.cia</code> and <code>.3dsx</code> files)
*The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9] (the GodMode9 <code>.zip</code> file)

==Instructions==

===Section I - Prep Work===
In this section, you will copy the files necessary to follow the rest of the instructions on this page.

#Power off your console
#Insert your SD card into your computer
#Create a folder named <code>cias</code> on the root of your SD card if it does not already exist
#Copy all of the CIA files (<code>Anemone3DS.cia</code>, <code>Checkpoint.cia</code>, <code>FBI.cia</code>, <code>Homebrew_Launcher.cia</code>, and <code>Universal-Updater.cia</code>) you downloaded earlier to the <code>/cias/</code> folder on your SD card
#Create a folder named <code>3ds</code> on the root of your SD card if it does not already exist
#*This folder stores homebrew applications and data; it is different from the <code>Nintendo 3DS</code> folder that the console automatically generates
#Copy <code>FBI.3dsx</code> to the <code>/3ds/</code> folder on your SD card
#Create a folder named <code>payloads</code> in the <code>luma</code> folder on your SD card if it does not already exist
#Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
#Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
#Reinsert your SD card into your console
#Power on your console

===Section II - Updating the System===
In this section, you will update your system to the latest version, which is safe to do with custom firmware.

#Update your console by going to System Settings, then “Other Settings”, then going all the way to the right and using “System Update”
#*Updates while using B9S + Luma (what you have) are safe
#*You may get a message saying “Your system is up to date” instead of updating. This is normal if you are already up to date; continue with the next section
#*If this gives you an error, ensure both your DNS settings and Proxy are set to “auto”
#*If this still gives you an error, [https://web.archive.org/web/20230319181423/https://3ds.hacks.guide/troubleshooting#finalizing-setup follow this troubleshooting guide]

===Section III - Homebrew Launcher===
In this section, you will temporarily replace Download Play with Homebrew Launcher (which we need to launch FBI). Download Play will automatically go back to normal once you reboot your console.

#Launch the Download Play application
#Wait until you see the <code>Nintendo 3DS</code> and <code>Nintendo DS</code> buttons
#Press {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} at the same time to open the Rosalina menu
#Select “Miscellaneous options”
#Select “Switch the hb. title to the current app.”
#Press {{Key press|B}} to continue
#Press {{Key press|B}} to return to the Rosalina main menu
#Press {{Key press|B}} to exit the Rosalina menu
#Press {{Key press|Home}}, then close Download Play
#Launch the Download Play application
#Your console should load the Homebrew Launcher
#*If your console is stuck on the loading splash screen or crashes to a screen with white text, you are missing <code>boot.3dsx</code> from the root of your SD card. To fix this, download the latest [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] release and extract all files to the root of your SD card, overwriting if asked

===Section IV - RTC and DSP Setup===
In this section, you will sync your 3DS internal clock with the actual time and dump the sound firmware (which is necesssary for some homebrew software to use sound properly).

#Press {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} at the same time to open the Rosalina menu
#Select “Miscellaneous options”
#Select “Dump DSP firmware”
#Press {{Key press|B}} to continue
#Select “Nullify user time offset”
#Press {{Key press|B}} to continue
#Press {{Key press|B}} to return to the Rosalina main menu
#Press {{Key press|B}} to exit the Rosalina menu
===Section V - Installing CIAs===
In this section, you will install several useful homebrew applications to HOME Menu.

#Launch FBI from the list of homebrew
#Navigate to <code>SD</code> -> <code>cias</code>
#Select “<current directory>”
#Select the “Install and delete all CIAs” option, then press (A) to confirm
#Press {{Key press|Home}}, then {{Key press|X}} to close Download Play

===Section VI - CTRNAND Luma3DS===
In this section, you will use a script to copy some of Luma3DS’s files to internal memory so that they can be accessed, even without an SD card inserted.

#Power off your console
#Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
#* If you boot to Luma3DS Chainloader, select GodMode9
#** If you do not boot into GodMode9, ensure that <code>GodMode9.firm</code> is in <code>/luma/payloads/</code> and that <code>payloads</code> is correctly spelled
#If you are prompted to create an essential files backup, press {{Key press|A}} to do so, then press {{Key press|A}} to continue once it has completed
#If you are prompted to fix the RTC date&time, press {{Key press|A}} to do so, set the date and time, then press {{Key press|A}} to continue
#Press {{Key press|Home}} to bring up the action menu
#Select “Scripts…”
#Select “GM9Megascript”
#Select “Scripts from Plailect’s Guide”
#Select “Setup Luma3DS to CTRNAND”
#When prompted, press {{Key press|A}} to proceed
#Press {{Key press|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
#Press {{Key press|A}} to continue

===Section VII - Cleanup SD Card===
In this section, you will use a script to remove some unnecessary files from your SD card.

#When prompted, press {{Key press|A}} to proceed
#Press {{Key press|A}} to continue
#Press {{Key press|B}} to return to the main menu

===Section VIII - Backup Essential Files===
In this section, you will make backups of files that can be used to recover from software bricks or to recover data.

#Select “Backup Options”
#Select “SysNAND Backup”
#Press {{Key press|A}} to confirm
#*This process will take some time
#*If you get an error, look for your issue in the troubleshooting guide
#Press {{Key press|A}} to continue
#Press {{Key press|B}} to return to the main menu
#Select “Exit”
#Press {{Key press|A}} to relock write permissions if prompted
#Navigate to <code>[S:] SYSNAND VIRTUAL</code>
#Press {{Key press|A}} on <code>essential.exefs</code> to select it
#Select “Copy to 0:/gm9/out”
#*If you see “Destination already exists”, press {{Key press|A}} on “Overwrite file(s)”
#Press {{Key press|A}} to continue
#Press {{Key press|Home}} to bring up the action menu
#Select “Poweroff system” to power off your console
#Insert your SD card into your computer
#Copy <code><date>_<serialnumber>_sysnand_##.bin</code>, <code><date>_<serialnumber>_sysnand_##.bin.sha</code>, and <code>essential.exefs</code> from the <code>/gm9/out/</code> folder on your SD card to a safe location on your computer
#*Copy these backups to multiple locations (such as online file storage, an external hard drive, etc.)
#*These backups will save you from a brick and/or help you recover files from the NAND image if anything goes wrong in the future
#Delete <code><date>_<serialnumber>_sysnand_##.bin</code> and <code><date>_<serialnumber>_sysnand_##.bin.sha</code> from the <code>/gm9/out/</code> folder on your SD card after copying it
#*The other backup files are negligible in size and may be kept on your SD card for ease of access
#If you have it, copy the <code>/luma/backups/</code> folder on your SD card to a safe location on your computer
#Reinsert your SD card into your console
#Power on your console

----
{{success|text=You’re done! Custom firmware is now fully configured on your console.}}

{{info|text=
<b>Information and Notes</b>
Here are some key combos that you should know:

*Holding {{Key press|Select}} on boot will launch the Luma3DS configuration menu.
*Holding {{Key press|Start}} on boot will launch GodMode9, or if you have multiple payloads in <code>/luma/payloads/</code>, the Luma3DS chainloader.
*By default, pressing {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} while in 3DS mode will open the Rosalina menu, where you can check system information, take screenshots, enable cheats, and more. This can be changed from the Rosalina menu.
**If you have a modified Luma config, this key combination may be {{Key press|X}} + {{Key press|Y}} instead.
*Holding {{Key press|Start}} + {{Key press|Select}} + {{Key press|X}} on boot will make the notification LED show a color for debug purposes. See [[3DS:Boot9strap|here]] for what each color means.
}}
{{info|text=See [https://wiki.hacks.guide/wiki/3DS:Things_to_do here] for some suggestions on things to do with custom firmware.}}

{{info|text=For information on using GodMode9’s various features, check out the [[3DS:GodMode9/Usage|GodMode9 Usage]] and [[3DS:Dump titles and game cartridges|Dumping Titles and Game Cartridges]] pages.}}

File:Hekate screenshot.png

2023-11-30T21:15:48Z

Doge 2: Screenshot of the Hekate main menu

== Summary ==
Screenshot of the Hekate main menu

3DS:Alternate Exploits/Old Finalizing Setup

2023-11-30T21:14:34Z

Doge 2: whoops

==Required Reading==
The file <code>boot.firm</code> is what is launched by boot9strap itself after it finishes loading off of NAND. In this case, we are using Luma3DS by LumaTeam to patch the console, allowing it to run homebrew software.

This guide will have you make critical system file backups and install the following homebrew programs:

*[[3DS:FBI|FBI]] ''(installs CIA formatted applications)''
*[[3DS:Anemone3DS|Anemone3DS]] ''(installs custom themes)''
*[[Checkpoint]] ''(backs up and restores save files for 3DS and DS games)''
*[[3DS:Universal-Updater|Universal-Updater]] ''(a homebrew app store for downloading homebrew from the 3DS over Wi-Fi)''
*[[3DS:GodMode9|GodMode9]] ''(multipurpose tool which can do NAND and cartridge functions)''
*'''Homebrew Launcher Loader''' ''(launches the Homebrew Launcher)''

==What You Need==
*The latest release of [https://github.com/astronautlevel2/Anemone3DS/releases/latest Anemone3DS] (the <code>.cia</code> file)
*The v3.7.4 release of [https://github.com/BernardoGiordano/Checkpoint/releases/latest Checkpoint] (the <code>.cia</code> file)
*The latest release of [https://github.com/PabloMK7/homebrew_launcher_dummy/releases/latest Homebrew Launcher Wrapper] (the <code>.cia</code> file)
*The latest release of [https://github.com/Universal-Team/Universal-Updater/releases/latest Universal-Updater] (the <code>.cia</code> file)
*The latest release of [https://github.com/Steveice10/FBI/releases FBI] ('''both''' the <code>.cia</code> and <code>.3dsx</code> files)
*The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9] (the GodMode9 <code>.zip</code> file)

==Instructions==

===Section I - Prep Work===
In this section, you will copy the files necessary to follow the rest of the instructions on this page.

#Power off your console
#Insert your SD card into your computer
#Create a folder named <code>cias</code> on the root of your SD card if it does not already exist
#Copy all of the CIA files (<code>Anemone3DS.cia</code>, <code>Checkpoint.cia</code>, <code>FBI.cia</code>, <code>Homebrew_Launcher.cia</code>, and <code>Universal-Updater.cia</code>) you downloaded earlier to the <code>/cias/</code> folder on your SD card
#Create a folder named <code>3ds</code> on the root of your SD card if it does not already exist
#*This folder stores homebrew applications and data; it is different from the <code>Nintendo 3DS</code> folder that the console automatically generates
#Copy <code>FBI.3dsx</code> to the <code>/3ds/</code> folder on your SD card
#Create a folder named <code>payloads</code> in the <code>luma</code> folder on your SD card if it does not already exist
#Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
#Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
#Reinsert your SD card into your console
#Power on your console

===Section II - Updating the System===
In this section, you will update your system to the latest version, which is safe to do with custom firmware.

#Update your console by going to System Settings, then “Other Settings”, then going all the way to the right and using “System Update”
#*Updates while using B9S + Luma (what you have) are safe
#*You may get a message saying “Your system is up to date” instead of updating. This is normal if you are already up to date; continue with the next section
#*If this gives you an error, ensure both your DNS settings and Proxy are set to “auto”
#*If this still gives you an error, [https://web.archive.org/web/20230319181423/https://3ds.hacks.guide/troubleshooting#finalizing-setup follow this troubleshooting guide]

===Section III - Homebrew Launcher===
In this section, you will temporarily replace Download Play with Homebrew Launcher (which we need to launch FBI). Download Play will automatically go back to normal once you reboot your console.

#Launch the Download Play application
#Wait until you see the <code>Nintendo 3DS</code> and <code>Nintendo DS</code> buttons
#Press {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} at the same time to open the Rosalina menu
#Select “Miscellaneous options”
#Select “Switch the hb. title to the current app.”
#Press {{Key press|B}} to continue
#Press {{Key press|B}} to return to the Rosalina main menu
#Press {{Key press|B}}) to exit the Rosalina menu
#Press {{Key press|Home}}, then close Download Play
#Launch the Download Play application
#Your console should load the Homebrew Launcher
#*If your console is stuck on the loading splash screen or crashes to a screen with white text, you are missing <code>boot.3dsx</code> from the root of your SD card. You can redownload it [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]

===Section IV - RTC and DSP Setup===
In this section, you will sync your 3DS internal clock with the actual time and dump the sound firmware (which is necesssary for some homebrew software to use sound properly).

#Press {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} at the same time to open the Rosalina menu
#Select “Miscellaneous options”
#Select “Dump DSP firmware”
#Press {{Key press|B}} to continue
#Select “Nullify user time offset”
#Press {{Key press|B}} to continue
#Press {{Key press|B}} to return to the Rosalina main menu
#Press {{Key press|B}} to exit the Rosalina menu
===Section V - Installing CIAs===
In this section, you will install several useful homebrew applications to HOME Menu.

#Launch FBI from the list of homebrew
#Navigate to <code>SD</code> -> <code>cias</code>
#Select “<current directory>”
#Select the “Install and delete all CIAs” option, then press (A) to confirm
#Press {{Key press|Home}}, then {{Key press|X}} to close Download Play

===Section VI - CTRNAND Luma3DS===
In this section, you will use a script to copy some of Luma3DS’s files to internal memory so that they can be accessed, even without an SD card inserted.

#Power off your console
#Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your console. This will launch GodMode9
#** If you boot to Luma3DS Chainloader, select GodMode9
#*If you do not boot into GodMode9, ensure that <code>GodMode9.firm</code> is in <code>/luma/payloads/</code> and that <code>payloads</code> is correctly spelled
#If you are prompted to create an essential files backup, press {{Key press|A}} to do so, then press {{Key press|A}} to continue once it has completed
#If you are prompted to fix the RTC date&time, press {{Key press|A}} to do so, set the date and time, then press {{Key press|A}}) to continue
#Press {{Key press|Home}} to bring up the action menu
#Select “Scripts…”
#Select “GM9Megascript”
#Select “Scripts from Plailect’s Guide”
#Select “Setup Luma3DS to CTRNAND”
#When prompted, press {{Key press|A}} to proceed
#Press {{Key press|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
#Press {{Key press|A}} to continue

===Section VII - Cleanup SD Card===
In this section, you will use a script to remove some unnecessary files from your SD card.

#When prompted, press {{Key press|A}} to proceed
#Press {{Key press|A}} to continue
#Press {{Key press|B}} to return to the main menu

===Section VIII - Backup Essential Files===
In this section, you will make backups of files that can be used to recover from software bricks or to recover data.

#Select “Backup Options”
#Select “SysNAND Backup”
#Press {{Key press|A}} to confirm
#*This process will take some time
#*If you get an error, look for your issue in the troubleshooting guide
#Press {{Key press|A}} to continue
#Press {{Key press|B}} to return to the main menu
#Select “Exit”
#Press {{Key press|A}} to relock write permissions if prompted
#Navigate to <code>[S:] SYSNAND VIRTUAL</code>
#Press {{Key press|A}} on <code>essential.exefs</code> to select it
#Select “Copy to 0:/gm9/out”
#*If you see “Destination already exists”, press {{Key press|A}} on “Overwrite file(s)”
#Press {{Key press|A}} to continue
#Press {{Key press|Home}} to bring up the action menu
#Select “Poweroff system” to power off your console
#Insert your SD card into your computer
#Copy <code><date>_<serialnumber>_sysnand_##.bin</code>, <code><date>_<serialnumber>_sysnand_##.bin.sha</code>, and <code>essential.exefs</code> from the <code>/gm9/out/</code> folder on your SD card to a safe location on your computer
#*Copy these backups to multiple locations (such as online file storage, an external hard drive, etc.)
#*These backups will save you from a brick and/or help you recover files from the NAND image if anything goes wrong in the future
#Delete <code><date>_<serialnumber>_sysnand_##.bin</code> and <code><date>_<serialnumber>_sysnand_##.bin.sha</code> from the <code>/gm9/out/</code> folder on your SD card after copying it
#*The other backup files are negligible in size and may be kept on your SD card for ease of access
#If you have it, copy the <code>/luma/backups/</code> folder on your SD card to a safe location on your computer
#Reinsert your SD card into your console
#Power on your console

----
{{success|text=You’re done! Custom firmware is now fully configured on your console.}}

{{info|text=
<b>Information and Notes</b>
Here are some key combos that you should know:

*Holding {{Key press|Select}} on boot will launch the Luma3DS configuration menu.
*Holding {{Key press|Start}} on boot will launch GodMode9, or if you have multiple payloads in <code>/luma/payloads/</code>, the Luma3DS chainloader.
*By default, pressing {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} while in 3DS mode will open the Rosalina menu, where you can check system information, take screenshots, enable cheats, and more. This can be changed from the Rosalina menu.
**If you have a modified Luma config, this key combination may be {{Key press|X}} and {{Key press|Y}} instead.
*Holding {{Key press|Start}} + {{Key press|Select}} + {{Key press|X}} on boot will make the notification LED show a color for debug purposes. See [[3DS:Boot9strap|here]] for what each color means.
}}
{{info|text=See [https://wiki.hacks.guide/wiki/3DS:Things_to_do here] for some suggestions on things to do with custom firmware.}}

{{info|text=For information on using GodMode9’s various features, check out the [[3DS:GodMode9/Usage|GodMode9 Usage]] and [[3DS:Dump titles and game cartridges|Dumping Titles and Game Cartridges]] pages.}}

File:Hekate.png

2023-11-30T21:08:27Z

Doge 2: Hekate IPL Custom NX Bootloader

== Summary ==
Hekate IPL Custom NX Bootloader

3DS:Alternate Exploits/Old Finalizing Setup

2023-11-30T21:04:42Z

Doge 2: less dots periods, cleanup etc etc

==Required Reading==
The file <code>boot.firm</code> is what is launched by boot9strap itself after it finishes loading off of NAND. In this case, we are using Luma3DS by LumaTeam to patch the device, allowing it to run homebrew software.

This guide will have you make critical system file backups and install the following homebrew programs:

*[[3DS:FBI|FBI]] ''(installs CIA formatted applications)''

*[[3DS:Anemone3DS|Anemone3DS]] ''(installs custom themes)''

*[[Checkpoint]] ''(backs up and restores save files for 3DS and DS games)''

*[[3DS:Universal-Updater|Universal-Updater]] ''(a homebrew app store for downloading homebrew from the 3DS over Wi-Fi)''

*[[3DS:GodMode9|GodMode9]] ''(multipurpose tool which can do NAND and cartridge functions)''
*'''Homebrew Launcher Loader''' ''(launches the Homebrew Launcher)''

==What You Need==
*The latest release of [https://github.com/astronautlevel2/Anemone3DS/releases/latest Anemone3DS] (the <code>.cia</code> file)
*The v3.7.4 release of [https://github.com/BernardoGiordano/Checkpoint/releases/latest Checkpoint] (the <code>.cia</code> file)
*The latest release of [https://github.com/PabloMK7/homebrew_launcher_dummy/releases/latest Homebrew Launcher Wrapper] (the <code>.cia</code> file)
*The latest release of [https://github.com/Universal-Team/Universal-Updater/releases/latest Universal-Updater] (the <code>.cia</code> file)
*The latest release of [https://github.com/Steveice10/FBI/releases FBI] ('''both''' the <code>.cia</code> and <code>.3dsx</code> files)
*The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9] (the GodMode9 <code>.zip</code> file)

==Instructions==

===Section I - Prep Work===
In this section, you will copy the files necessary to follow the rest of the instructions on this page.

#Power off your device
#Insert your SD card into your computer
#Create a folder named <code>cias</code> on the root of your SD card if it does not already exist
#Copy all of the CIA files (<code>Anemone3DS.cia</code>, <code>Checkpoint.cia</code>, <code>FBI.cia</code>, <code>Homebrew_Launcher.cia</code>, and <code>Universal-Updater.cia</code>) you downloaded earlier to the <code>/cias/</code> folder on your SD card
#Create a folder named <code>3ds</code> on the root of your SD card if it does not already exist
#*This folder stores homebrew applications and data; it is different from the <code>Nintendo 3DS</code> folder that the device automatically generates
#Copy <code>FBI.3dsx</code> to the <code>/3ds/</code> folder on your SD card
#Create a folder named <code>payloads</code> in the <code>luma</code> folder on your SD card if it does not already exist
#Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
#Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
#Reinsert your SD card into your device
#Power on your device

===Section II - Updating the System===
In this section, you will update your system to the latest version, which is safe to do with custom firmware.

#Update your device by going to System Settings, then “Other Settings”, then going all the way to the right and using “System Update”
#*Updates while using B9S + Luma (what you have) are safe
#*You may get a message saying “Your system is up to date” instead of updating. This is normal if you are already up to date; continue with the next section
#*If this gives you an error, ensure both your DNS settings and Proxy are set to “auto”
#*If this still gives you an error, [https://web.archive.org/web/20230319181423/https://3ds.hacks.guide/troubleshooting#finalizing-setup follow this troubleshooting guide]

===Section III - Homebrew Launcher===
In this section, you will temporarily replace Download Play with Homebrew Launcher (which we need to launch FBI). Download Play will automatically go back to normal once you reboot your device.

#Launch the Download Play application
#Wait until you see the <code>Nintendo 3DS</code> and <code>Nintendo DS</code> buttons
#Press {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} at the same time to open the Rosalina menu
#Select “Miscellaneous options”
#Select “Switch the hb. title to the current app.”
#Press {{Key press|B}} to continue
#Press {{Key press|B}} to return to the Rosalina main menu
#Press {{Key press|B}}) to exit the Rosalina menu
#Press {{Key press|Home}}, then close Download Play
#Launch the Download Play application
#Your device should load the Homebrew Launcher
#*If your device is stuck on the loading splash screen or crashes to a screen with white text, you are missing <code>boot.3dsx</code> from the root of your SD card. You can redownload it [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]

===Section IV - RTC and DSP Setup===
In this section, you will sync your 3DS internal clock with the actual time and dump the sound firmware (which is necesssary for some homebrew software to use sound properly).

#Press {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} at the same time to open the Rosalina menu
#Select “Miscellaneous options”
#Select “Dump DSP firmware”
#Press {{Key press|B}} to continue
#Select “Nullify user time offset”
#Press {{Key press|B}} to continue
#Press {{Key press|B}} to return to the Rosalina main menu
#Press {{Key press|B}} to exit the Rosalina menu
===Section V - Installing CIAs===
In this section, you will install several useful homebrew applications to HOME Menu.

#Launch FBI from the list of homebrew
#Navigate to <code>SD</code> -> <code>cias</code>
#Select “<current directory>”
#Select the “Install and delete all CIAs” option, then press (A) to confirm
#Press {{Key press|Home}}, then {{Key press|X}} to close Download Play

===Section VI - CTRNAND Luma3DS===
In this section, you will use a script to copy some of Luma3DS’s files to internal memory so that they can be accessed, even without an SD card inserted.

#Power off your device
#Press and hold {{Key press|Start}}, and while holding {{Key press|Start}}, power on your device. This will launch GodMode9
#** If you boot to Luma3DS Chainloader, select GodMode9
#*If you do not boot into GodMode9, ensure that <code>GodMode9.firm</code> is in <code>/luma/payloads/</code> and that <code>payloads</code> is correctly spelled
#If you are prompted to create an essential files backup, press {{Key press|A}} to do so, then press {{Key press|A}} to continue once it has completed
#If you are prompted to fix the RTC date&time, press {{Key press|A}} to do so, set the date and time, then press {{Key press|A}}) to continue
#Press {{Key press|Home}} to bring up the action menu
#Select “Scripts…”
#Select “GM9Megascript”
#Select “Scripts from Plailect’s Guide”
#Select “Setup Luma3DS to CTRNAND”
#When prompted, press {{Key press|A}} to proceed
#Press {{Key press|A}} to unlock SysNAND (lvl1) writing, then input the key combo given
#Press {{Key press|A}} to continue

===Section VII - Cleanup SD Card===
In this section, you will use a script to remove some unnecessary files from your SD card.

#When prompted, press {{Key press|A}} to proceed
#Press {{Key press|A}} to continue
#Press {{Key press|B}} to return to the main menu

===Section VIII - Backup Essential Files===
In this section, you will make backups of files that can be used to recover from software bricks or to recover data.

#Select “Backup Options”
#Select “SysNAND Backup”
#Press {{Key press|A}} to confirm
#*This process will take some time
#*If you get an error, look for your issue in the troubleshooting guide
#Press {{Key press|A}} to continue
#Press {{Key press|B}} to return to the main menu
#Select “Exit”
#Press {{Key press|A}} to relock write permissions if prompted
#Navigate to <code>[S:] SYSNAND VIRTUAL</code>
#Press {{Key press|A}} on <code>essential.exefs</code> to select it
#Select “Copy to 0:/gm9/out”
#*If you see “Destination already exists”, press {{Key press|A}} on “Overwrite file(s)”
#Press {{Key press|A}} to continue
#Press {{Key press|Home}} to bring up the action menu
#Select “Poweroff system” to power off your device
#Insert your SD card into your computer
#Copy <code><date>_<serialnumber>_sysnand_##.bin</code>, <code><date>_<serialnumber>_sysnand_##.bin.sha</code>, and <code>essential.exefs</code> from the <code>/gm9/out/</code> folder on your SD card to a safe location on your computer
#*Copy these backups to multiple locations (such as online file storage, an external hard drive, etc.)
#*These backups will save you from a brick and/or help you recover files from the NAND image if anything goes wrong in the future
#Delete <code><date>_<serialnumber>_sysnand_##.bin</code> and <code><date>_<serialnumber>_sysnand_##.bin.sha</code> from the <code>/gm9/out/</code> folder on your SD card after copying it
#*The other backup files are negligible in size and may be kept on your SD card for ease of access
#If you have it, copy the <code>/luma/backups/</code> folder on your SD card to a safe location on your computer
#Reinsert your SD card into your device
#Power on your device

----
{{success|text=You’re done! Custom firmware is now fully configured on your device.}}

{{info|text=
<b>Information and Notes</b>
Here are some key combos that you should know:

*Holding {{Key press|Select}} on boot will launch the Luma3DS configuration menu.
*Holding {{Key press|Start}} on boot will launch GodMode9, or if you have multiple payloads in <code>/luma/payloads/</code>, the Luma3DS chainloader.
*By default, pressing {{Key press|L}} + {{Key press|Down}} + {{Key press|Select}} while in 3DS mode will open the Rosalina menu, where you can check system information, take screenshots, enable cheats, and more. This can be changed from the Rosalina menu.
**If you have a modified Luma config, this key combination may be {{Key press|X}} and {{Key press|Y}} instead.
*Holding {{Key press|Start}} + {{Key press|Select}} + {{Key press|X}} on boot will make the notification LED show a color for debug purposes. See [[3DS:Boot9strap|here]] for what each color means.
}}
{{info|text=See [https://wiki.hacks.guide/wiki/3DS:Things_to_do here] for some suggestions on things to do with custom firmware.}}

{{info|text=For information on using GodMode9’s various features, check out the [[3DS:GodMode9/Usage|GodMode9 Usage]] and [[3DS:Dump titles and game cartridges|Dumping Titles and Game Cartridges]] pages.}}