Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Ninfs 3DS: Difference between revisions

From GameBrew
No edit summary
No edit summary
Line 8: Line 8:
|version=2.0a6
|version=2.0a6
|license=Mixed
|license=Mixed
|download=https://dlhb.gamebrew.org/3dshomebrew/ninfv2.0a6.7z
|download=https://dlhb.gamebrew.org/3dshomebrews/ninfs.7z
|website=https://github.com/ihaveamac/ninfs
|website=https://github.com/ihaveamac/ninfs
|source=https://github.com/ihaveamac/ninfs
|source=https://github.com/ihaveamac/ninfs
}}
}}
<youtube>d6KZdaAcpO0</youtube>
== ninfs ==
ninfs (formerly fuse-3ds) is a FUSE program to extract data from Nintendo game consoles. It works by presenting a virtual filesystem with the contents of your games, NAND, or SD card contents, and you can browse and copy out just the files that you need.
ninfs (formerly fuse-3ds) is a FUSE program to extract data from Nintendo game consoles. It works by presenting a virtual filesystem with the contents of your games, NAND, or SD card contents, and you can browse and copy out just the files that you need.


Windows, macOS, and Linux are supported.
Requires Python 3.6.1+. Supports Windows (7 or later), macOS, and Linux.
 
https://dlhb.gamebrew.org/3dshomebrew/ciamount-mac.png
 
== Supported types ==
 
* Nintendo 3DS:
** CTR Cart Image (&quot;&quot;.3ds&quot;&quot;, &quot;&quot;.cci&quot;&quot;)
** CDN contents (&quot;&quot;cetk&quot;&quot;, &quot;&quot;tmd&quot;&quot;, and contents)
** CTR Importable Archive (&quot;&quot;.cia&quot;&quot;)
** Executable Filesystem (&quot;&quot;.exefs&quot;&quot;, &quot;&quot;exefs.bin&quot;&quot;)
** Nintendo 3DS NAND backup (&quot;&quot;nand.bin&quot;&quot;)
** NCCH (&quot;&quot;.cxi&quot;&quot;, &quot;&quot;.cfa&quot;&quot;, &quot;&quot;.ncch&quot;&quot;, &quot;&quot;.app&quot;&quot;)
** Read-only Filesystem (&quot;&quot;.romfs&quot;&quot;, &quot;&quot;romfs.bin&quot;&quot;)
** SD Card Contents (&quot;&quot;Nintendo 3DS&quot;&quot; from SD)
** 3DSX Homebrew (&quot;&quot;.3dsx&quot;&quot;)
* Nintendo DS / DSi
** Nintendo DSi NAND backup (&quot;&quot;nand_dsi.bin&quot;&quot;)
** Nintendo DS ROM image (&quot;&quot;.nds&quot;&quot;, &quot;&quot;.srl&quot;&quot;)
* Nintendo Switch
** Nintendo Switch NAND backup (&quot;&quot;rawnand.bin&quot;&quot;)
 
== Example uses ==


==Features==
* Mount a NAND backup and browse CTRNAND, TWLNAND, and others, and write back to them without having to extract and decrypt them first.
* Mount a NAND backup and browse CTRNAND, TWLNAND, and others, and write back to them without having to extract and decrypt them first.
* Browse decrypted SD card contents. Dump installed games and saves, or copy contents between two system's SD contents.
* Browse decrypted SD card contents. Dump installed games and saves, or copy contents between two system's SD contents.
* Extract a game's files out of a CIA, CCI (&quot;&quot;.3ds&quot;&quot;), NCCH, RomFS, raw CDN contents, just by mounting them and browsing its files. Or use the virtual decrypted file and start playing the game in [https://citra-emu.org Citra] right away.
* Extract a game's files out of a CIA, CCI (".3ds"), NCCH, RomFS, raw CDN contents, just by mounting them and browsing its files. Or use the virtual decrypted file and start playing the game in [https://citra-emu.org/ Citra] right away.
 
== Setup ==
 
For 3DS types, The ARM9 bootROM is required. You can dump it using boot9strap, which can be set up by [https://3ds.hacks.guide 3DS Hacks Guide]. To dump the bootROM, hold START+SELECT+X when you boot up your 3DS. It is checked in order of:


===Installation===
bootROM:
For 3DS types, The ARM9 bootROM is required. You can dump it using boot9strap, which can be set up by [https://3ds.hacks.guide 3DS Hacks Guide]. To dump the bootROM, hold Start+Select+X when you boot up your 3DS. It is checked in order of:
* <code>--boot9</code> argument (if set)
* <code>--boot9</code> argument (if set)
* <code>BOOT9_PATH</code> environment variable (if set)
* <code>BOOT9_PATH</code> environment variable (if set)
Line 59: Line 33:
<code>boot9_prot.bin</code> can also be used in all of these locations.
<code>boot9_prot.bin</code> can also be used in all of these locations.


&quot;&quot;<code>~</code>&quot;&quot; means the user's home directory. &quot;&quot;<code>~/3ds</code>&quot;&quot; would mean <code>/Users/username/3ds</code> on macOS and <code>C:\Users\username\3ds</code> on Windows.
"<code>~</code>" means the user's home directory. "<code>~/3ds</code>" would mean <code>/Users/username/3ds</code> on macOS and <code>C:\Users\username\3ds</code> on Windows.
 
CDN, CIA, and NCCH mounting may need [https://github.com/ihaveamac/3DS-rom-tools/wiki/SeedDB-list SeedDB] for mounting NCCH containers of newer games (2015+) that use seeds.<br />
SeedDB is checked in order of:


SeedDB:
CDN, CIA, and NCCH mounting may need [https://github.com/ihaveamac/3DS-rom-tools/wiki/SeedDB-list SeedDB] for mounting NCCH containers of newer games (2015+) that use seeds. SeedDB is checked in order of:
* <code>--seeddb</code> argument (if set)
* <code>--seeddb</code> argument (if set)
* <code>SEEDDB_PATH</code> environment variable (if set)
* <code>SEEDDB_PATH</code> environment variable (if set)
Line 71: Line 44:
* <code>~/3ds/seeddb.bin</code>
* <code>~/3ds/seeddb.bin</code>


Python 3.6.1+ and pycryptodomex are required. PySide2 is required for the GUI.
===Windows===
'''Using Installer:'''
* An installer is provided in releases. It includes both ninfs and WinFsp, which is installed if required.


* [https://github.com/fusepy/fusepy fusepy] is pre-included until [https://github.com/pleiszenburg/refuse refuse] has a fully stable release.
'''Using Standalone release:'''
 
* A standalone zip is also provided in releases. [http://www.secfs.net/winfsp/rel/ WinFsp] must be installed separately.
=== Windows ===
 
Windows 7 or later is required.
 
(GUI in progress of being re-created.) Python does not have to be installed, but [http://www.secfs.net/winfsp/download/ WinFsp] is still required.
 
==== Install with existing Python ====


'''Installing with existing Python:'''
* Install the latest version of [https://www.python.org/downloads/ Python 3]. The x86-64 version is preferred on 64-bit Windows.
* Install the latest version of [https://www.python.org/downloads/ Python 3]. The x86-64 version is preferred on 64-bit Windows.
** Alternatively, use [https://www.microsoft.com/en-us/p/python-37/9nj46sx7x90p Python 3.7 from the Microsoft Store]. Note that <code>python</code> or <code>python3</code> must be used, not <code>py -3</code>.
** Python from the Microsoft Store can also be used. If this is used, python3 must be used instead of py -3.
* Install the latest version of [http://www.secfs.net/winfsp/download/ WinFsp].
** This version has some limitations however, such as not being able to mount to directories.
* Install ninfs with <code>py -3 -m pip install --upgrade https://github.com/ihaveamac/ninfs/archive/master.zip</code>.
* Install the latest version of [http://www.secfs.net/winfsp/rel/ WinFsp].
** With GUI support: <code>py -3 -m pip install --upgrade https://github.com/ihaveamac/ninfs/archive/master.zip#egg=ninfs[gui]</code>
* Install ninfs with <code>py -3 -m pip install --upgrade <nowiki>https://github.com/ihaveamac/ninfs/archive/2.0.zip</nowiki></code>
 
=== macOS ===
 
(GUI in progress of being re-created.) Python does not have to be installed, but [https://osxfuse.github.io/ FUSE for macOS] is still required.
 
==== Install with existing Python ====


Versions of macOS supported by Apple are highly recommended. OS X Mavericks is the oldest version that should work.
===macOS===
Versions of macOS supported by Apple are highly recommended. macOS Sierra is the oldest version that should work. [https://osxfuse.github.io/ macFUSE] is required. No standalone build is available at the moment.


'''Installing with existing Python:'''
* Install the latest version of Python 3. The recommended way is [https://brew.sh Homebrew]. You can also use an installer from [https://www.python.org/downloads/ python.org] or a tool like [https://github.com/pyenv/pyenv pyenv].
* Install the latest version of Python 3. The recommended way is [https://brew.sh Homebrew]. You can also use an installer from [https://www.python.org/downloads/ python.org] or a tool like [https://github.com/pyenv/pyenv pyenv].
* Install the latest version of [https://github.com/osxfuse/osxfuse/releases/latest FUSE for macOS].
* Install the latest version of [https://github.com/osxfuse/osxfuse/releases/latest FUSE for macOS].
* Install ninfs with <code>python3 -m pip install --upgrade https://github.com/ihaveamac/ninfs/archive/master.zip</code>.
* Install ninfs with <code>python3 -m pip install --upgrade <nowiki>https://github.com/ihaveamac/ninfs/archive/2.0.zip</nowiki></code>
** With GUI support: <code>python3 -m pip install --upgrade https://github.com/ihaveamac/ninfs/archive/master.zip#egg=ninfs[gui]</code>


=== Linux ===
===Linux===
'''Arch Linux:'''
* (Note: git versions out of date while build process stabilizes.)
* ninfs is available in the AUR: [https://aur.archlinux.org/packages/ninfs/ normal], [https://aur.archlinux.org/packages/ninfs-gui/ with gui].


* Arch Linux: ninfs is available in the AUR: [https://aur.archlinux.org/packages/ninfs/ normal], [https://aur.archlinux.org/packages/ninfs-gui/ with gui], [https://aur.archlinux.org/packages/ninfs-git/ git], [https://aur.archlinux.org/packages/ninfs-gui-git/ git with gui]
'''Other distributions:'''
* Recent distributions should have Python 3.6.1 or later pre-installed, or included in its repositories. If not, you can use an extra repository (e.g. [https://launchpad.net/%7Edeadsnakes/+archive/ubuntu/ppa deadsnakes's PPA] for Ubuntu), [https://www.python.org/downloads/source/ build from source], or use a tool like [https://github.com/pyenv/pyenv pyenv].
* Recent distributions (e.g. Ubuntu 18.04 and later) should have Python 3.6.1 or later pre-installed, or included in its repositories. If not, you can use an extra repository (e.g. [https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa deadsnakes's PPA] for Ubuntu), [https://www.python.org/downloads/source/ build from source], or use a tool like [https://github.com/pyenv/pyenv pyenv].
* Most distributions should have fuse enabled/installed by default. Use your package manager if it isn't.
* Most distributions should have libfuse enabled/installed by default. Use your package manager if it isn't.
* Install ninfs with <code>python3 -m pip install --upgrade --user https://github.com/ihaveamac/ninfs/archive/2.0.zip</code>.
* Install ninfs with <code>python3 -m pip install --upgrade --user <nowiki>https://github.com/ihaveamac/ninfs/archive/2.0.zip</nowiki></code>
** <code>--user</code> is not needed if you are using a virtual environment.
** <code>--user</code> is not needed if you are using a virtual environment.
** With GUI support: <code>python3 -m pip install --upgrade --user https://github.com/ihaveamac/ninfs/archive/2.0.zip#egg=ninfs[gui]</code>
* You can add a desktop entry with <code>python3 -m ninfs --install-desktop-entry</code>. If you want to install to a location other than the default (<code>$XDG_DATA_HOME</code>), you can add another argument with a path like <code>/usr/local/share</code>.
* You can add a desktop entry with <code>python3 -m ninfs --install-desktop-entry</code>. If you want to install to a location other than the default (<code>$XDG_DATA_HOME</code>), you can add another argument with a path like <code>/usr/local/share</code>.
* To use the GUI, tkinter needs to be installed. On Debian-/Ubuntu-based systems this is <code>python3-tk</code>. On Fedora this is <code>python3-tkinter</code>.


== Usage ==
==User guide==
===Supported types===
{| class="wikitable" style="width: 480px;"
|-
! colspan="2"| Nintendo 3DS:
|-
|style="width: 45%;"| CTR Cart Image
| .3ds, .cci.
|-
| CDN contents
| cetk, tmd, and contents.
|-
| CTR Importable Archive || .cia.
|-
| Executable Filesystem || .exefs, exefs.bin
|-
| NAND backup || nand.bin
|-
| NCCH || .cxi, .cfa, .ncch, .app
|-
| Read-only Filesystem || .romfs, romfs.bin
|-
| SD Card Contents || Nintendo 3DS from SD
|-
| Installed SD Title Contents || *.tmd and *.app files
|-
| 3DSX Homebrew || .3dsx
|-
! colspan="2"|Nintendo DS / DSi
|-
| DSi NAND backup || nand_dsi.bin
|-
| Nintendo DS ROM image || .nds, .srl
|-
! colspan="2"|iQue Player
|-
| NAND backup
| (read-only) nand.bin
|-
! colspan="2"|Nintendo Switch
|-
| NAND backup
| rawnand.bin
|-
|}


=== Graphical user interface ===
===Graphical user interface===
* A GUI can be used by specifying the type to be <code>gui</code>. It controls mounting and unmounting. Examples:
** Windows: <code>py -3 -mninfs gui</code>
** *nix: <code>python3 -mninfs gui</code>.


A GUI can be used, if ninfs was installed with GUI support, by specifying the type to be <code>gui</code> (e.g. Windows: <code>py -3 -mninfs gui</code>, *nix: <code>python3 -mninfs gui</code>). The GUI controls mounting and unmounting.
===Command line===
'''Mounting:'''
* Run a mount script by using "<code>mount_<type></code>" (e.g. <code>mount_cci game.3ds mountpoint</code>).
* Use <code>-h</code> to view arguments for a script.
* If it doesn't work, the other way is to use <code><python-cmd> -mninfs <type></code>. Examples:
** Windows: <code>py -3 -mninfs cci game.3ds mountpoint</code>  
** *nix: <code>python3 -mninfs cci game.3ds mountpoint)</code>


=== Command line ===
Windows users can use a drive letter like <code>F:</code> as a mountpoint. Or use <code>*</code> and a drive letter will be automatically chosen.
 
Run a mount script by using &quot;&quot;<code>mount_&lt;type&gt;</code>&quot;&quot; (e.g. <code>mount_cci game.3ds mountpoint</code>). Use <code>-h</code> to view arguments for a script.
 
If it doesn't work, the other way is to use <code>&lt;python-cmd&gt; -mninfs &lt;type&gt;</code> (e.g. Windows: <code>py -3 -mninfs cci game.3ds mountpoint</code>, *nix: <code>python3 -mninfs cci game.3ds mountpoint</code>).
 
Windows users can use a drive letter like <code>F:</code> as a mountpoint, or use <code>*</code> and a drive letter will be automatically chosen.


Developer-unit contents are encrypted with different keys, which can be used with <code>--dev</code> with CCI, CDN, CIA, NANDCTR, NCCH, and SD.
Developer-unit contents are encrypted with different keys, which can be used with <code>--dev</code> with CCI, CDN, CIA, NANDCTR, NCCH, and SD.


==== Unmounting ====
'''Unmounting:'''
 
* Windows: Press Ctrl+C in the command prompt/PowerShell window.
* Windows: Press <kbd>Ctrl</kbd> + <kbd>C</kbd> in the command prompt/PowerShell window.
* macOS (two methods):
* macOS: Two methods:
** Right-click on the mount and choose "Eject "drive name"".
** Right-click on the mount and choose &quot;&quot;Eject “''drive name''”&quot;&quot;.
** Run from terminal: <code>diskutil unmount /path/to/mount</code>
** Run from terminal: <code>diskutil unmount /path/to/mount</code>
* Linux: Run from terminal: <code>fusermount -u /path/to/mount</code>
* Linux: Run from terminal: <code>fusermount -u /path/to/mount</code>


=== Examples ===
===Examples===
 
* 3DS game card dump:  
* 3DS game card dump:<br />
<code>mount_cci game.3ds mountpoint</code>
<code>mount_cci game.3ds mountpoint</code>
* Contents downloaded from CDN:<br />
* Contents downloaded from CDN:  
<code>mount_cdn cdn_directory mountpoint</code>
<code>mount_cdn cdn_directory mountpoint</code>
* CDN contents with a specific decrypted titlekey:<br />
* CDN contents with a specific decrypted titlekey:  
<code>mount_cdn --dec-key 3E3E6769742E696F2F76416A65423C3C cdn_directory mountpoint</code>
<code>mount_cdn --dec-key 3E3E6769742E696F2F76416A65423C3C cdn_directory mountpoint</code>
* CIA:<br />
* CIA:  
<code>mount_cia game.cia mountpoint</code>
<code>mount_cia game.cia mountpoint</code>
* ExeFS:<br />
* ExeFS:
<code>mount_exefs exefs.bin mountpoint</code>
<code>mount_exefs exefs.bin mountpoint</code>
* 3DS NAND backup with <code>essential.exefs</code> embedded:<br />
* 3DS NAND backup with essential.exefs embedded:
<code>mount_nandctr nand.bin mountpoint</code>
<code>mount_nandctr nand.bin mountpoint</code>
* 3DS NAND backup with an OTP file (Counter is automatically generated):<br />
* 3DS NAND backup with an OTP file (Counter is automatically generated):
<code>mount_nandctr --otp otp.bin nand.bin mountpoint</code>
<code>mount_nandctr --otp otp.bin nand.bin mountpoint</code>
* 3DS NAND backup with OTP and CID files:<br />
* 3DS NAND backup with OTP and CID files:
<code>mount_nandctr --otp otp.bin --cid nand_cid.bin nand.bin mountpoint</code>
<code>mount_nandctr --otp otp.bin --cid nand_cid.bin nand.bin mountpoint</code>
* 3DS NAND backup with OTP file and a CID hexstring:<br />
* 3DS NAND backup with OTP file and a CID hexstring:
<code>mount_nandctr --otp otp.bin --cid 7468616E6B7334636865636B696E6721 nand.bin mountpoint</code>
<code>mount_nandctr --otp otp.bin --cid 7468616E6B7334636865636B696E6721 nand.bin mountpoint</code>
* DSi NAND backup (Counter is automatically generated):<br />
* DSi NAND backup (Counter is automatically generated):
<code>mount_nandtwl --console-id 4E696E74656E646F nand_dsi.bin mountpoint</code>
<code>mount_nandtwl --console-id 5345445543454D45 nand_dsi.bin mountpoint</code>
* DSi NAND backup with a Console ID hexstring and specified CID hexstring:<br />
* DSi NAND backup with a Console ID hexstring and specified CID hexstring:
<code>mount_nandtwl --console-id 4E696E74656E646F --cid 576879446F657344536945786973743F nand_dsi.bin mountpoint</code>
<code>mount_nandtwl --console-id 5345445543454D45 --cid 576879446F657344536945786973743F nand_dsi.bin mountpoint</code>
* DSi NAND backup with a Console ID file and specified CID file:<br />
* DSi NAND backup with a Console ID file and specified CID file:
<code>mount_nandtwl --console-id ConsoleID.bin --cid CID.bin nand_dsi.bin mountpoint</code>
<code>mount_nandtwl --console-id ConsoleID.bin --cid CID.bin nand_dsi.bin mountpoint</code>
* Switch NAND backup<br />
* iQue Player NAND backup:
<code>mount_nandbb nand.bin mountpoint</code>
* Switch NAND backup:
<code>mount_nandhac --keys prod.keys rawnand.bin mountpoint</code>
<code>mount_nandhac --keys prod.keys rawnand.bin mountpoint</code>
* Switch NAND backup in multiple parts<br />
* Switch NAND backup in multiple parts:
<code>mount_nandhac --keys prod.keys -S rawnand.bin.00 mountpoint</code>
<code>mount_nandhac --keys prod.keys -S rawnand.bin.00 mountpoint</code>
* NCCH container (.app, .cxi, .cfa, .ncch):<br />
* Switch NAND encrypted partition dump:
<code>mount_nandhac --keys prod.keys --partition SYSTEM SYSTEM.bin mountpoint</code>
* NCCH container (.app, .cxi, .cfa, .ncch):
<code>mount_ncch content.cxi mountpoint</code>
<code>mount_ncch content.cxi mountpoint</code>
* RomFS:<br />
* RomFS:
<code>mount_romfs romfs.bin mountpoint</code>
<code>mount_romfs romfs.bin mountpoint</code>
* <code>Nintendo 3DS</code> directory from an SD card:<br />
* Nintendo 3DS directory from an SD card:
<code>mount_sd --movable movable.sed &quot;&quot;/path/to/Nintendo 3DS&quot;&quot; mountpoint</code>
<code>mount_sd --movable movable.sed "/path/to/Nintendo 3DS" mountpoint</code>
* <code>Nintendo 3DS</code> directory from an SD card with an SD key hexstring:<br />
* Nintendo 3DS directory from an SD card with an SD key hexstring:
<code>mount_sd --sd-key 504C415900000000504F4B454D4F4E21 &quot;&quot;/path/to/Nintendo 3DS&quot;&quot; mountpoint</code>
<code>mount_sd --sd-key 504C415900000000504F4B454D4F4E21 "/path/to/Nintendo 3DS" mountpoint</code>
* Nintendo DS ROM image (NDS/SRL, <code>mount_nds</code> also works):<br />
* Nintendo DS ROM image (NDS/SRL, mount_nds also works):
<code>mount_srl game.nds mountpoint</code>
<code>mount_srl game.nds mountpoint</code>
* 3DSX homebrew application:<br />
* 3DSX homebrew application:
<code>mount_threedsx boot.3dsx mountpoint</code>
<code>mount_threedsx boot.3dsx mountpoint</code>


== Useful tools ==
===Useful tools===
 
* wwylele's [[3DS_Save_File_Extraction_Tools|3ds-save-tool]] can be used to extract game saves and extra data (DISA and DIFF, respectively).
* wwylele's [https://github.com/wwylele/3ds-save-tool 3ds-save-tool] can be used to extract game saves and extra data (DISA and DIFF, respectively).
* wwylele's [https://github.com/wwylele/save3ds save3ds] is a tool to interact with 3DS save files and extdata. Extracting and importing works on all platforms. The FUSE part only works on macOS and Linux.
** wwylele's [https://github.com/wwylele/save3ds save3ds] is a FUSE mount for 3DS save files. Currently only supports macOS and Linux.
* [https://www.osforensics.com/tools/mount-disk-images.html OSFMount] for Windows can mount FAT12/FAT16/FAT32 partitions in NAND backups.
* [https://www.osforensics.com/tools/mount-disk-images.html OSFMount] for Windows can mount FAT12/FAT16 partitions in NAND backups.
 
== Related tools ==


===Related tools===
* roothorick's [https://gitlab.com/roothorick/busehac BUSEHAC] is a Linux driver for encrypted Nintendo Switch NANDs.
* roothorick's [https://gitlab.com/roothorick/busehac BUSEHAC] is a Linux driver for encrypted Nintendo Switch NANDs.
* Maschell's [https://github.com/Maschell/fuse-wiiu fuse-wiiu] can be used to mount Wii U contents.
* Maschell's [https://github.com/Maschell/fuse-wiiu fuse-wiiu] can be used to mount Wii U contents.
* koolkdev's [https://github.com/koolkdev/wfslib wfslib] has wfs-fuse to mount the Wii U mlc dumps and usb devices.
* koolkdev's [https://github.com/koolkdev/wfslib wfslib] has wfs-fuse to mount the Wii U mlc dumps and usb devices.


== License/Credits ==
==Media==
'''fuse-3ds demonstration with Pokémon Ultra Moon''' ([https://www.youtube.com/watch?v=d6KZdaAcpO0 ihaveamac]) <br>
<youtube>d6KZdaAcpO0</youtube>
 
==Credits==
ninfs is under the MIT license. fuse.py is under the ISC license (taken from [https://github.com/fusepy/fusepy/blob/b5f87a1855119d55c755c2c4c8b1da346365629d/setup.py setup.py]).


* <code>ninfs</code> is under the MIT license.
Special thanks to @Jhynjhiruu for adding support for iQue Player NAND backups.
** <code>fuse.py</code> is under the ISC license ([https://github.com/fusepy/fusepy/blob/b5f87a1855119d55c755c2c4c8b1da346365629d/setup.py taken from <code>setup.py</code>]).
** <code>hac/aes.cpp</code> and <code>hac/aes.hpp</code> are from @openluopworld's [https://github.com/openluopworld/aes_128 aes_128] commit <code>b5b7f55</code>, and uses the MIT License.
** <code>hac/_crypto.cpp</code> AES-XTS part by @luigoalma, based on @plutooo's [https://gist.github.com/plutooo/fd4b22e7f533e780c1759057095d7896 crypto module]; Python module implementation initially by me(@ihaveamac).


Special thanks to @Stary2001 for help with NAND crypto (especially TWL), and @d0k3 for SD crypto.
Special thanks to @Stary2001 for help with NAND crypto (especially TWL), and @d0k3 for SD crypto.
Line 202: Line 218:
OTP code is from [https://github.com/Stary2001/3ds_tools/blob/10b74fee927f66865b97fd73b3e7392e81a3099f/three_ds/aesengine.py Stary2001/3ds_tools], and is under the MIT license.
OTP code is from [https://github.com/Stary2001/3ds_tools/blob/10b74fee927f66865b97fd73b3e7392e81a3099f/three_ds/aesengine.py Stary2001/3ds_tools], and is under the MIT license.


Warning: Using the GUI on macOS 10.14.6 will crash WindowServer and force you back to the login screen. The issue can be followed here: [http://github.com/pyinstaller/pyinstaller/issues/4334 http://github.com/pyinstaller/pyinstaller/issues/4334]
==External links==
 
* GitHub - https://github.com/ihaveamac/ninfs
Changes since v1.6.1 SD: Properly decrypt contents of backup folder NANDHAC: Support &quot;&quot;raw&quot;&quot; partition-based emuMMC images with -R/--raw-emummc Display application name for CIA, CCI, and NCCH in mount title on macOS Allow assuming contents are decrypted for CCI and NCCH Major internal changes and rewriting Remove titledir mount - better tools will be coming later to search for installed titles Other things, probably Changes since v1.7b1 Display application name for CCI in mount title on macOS Allow assuming contents are decrypted for CCI and NCCH Interested in filling out a quick survey on how you use ninfs? Click here!
 
Important note This is not a full release, so some things may still be broken. Please file issues if this happens.
 
NAND and SD mounts allow writing. Keep backups before writing to these, in the event an unknown bug corrupts data.
 
There is a Windows tutorial for ninfs on GBAtemp. README also explains how to use it via command line and on non-Windows platforms. If you are unsure about something, you can ask at Nintendo Homebrew on Discord, or the GBAtemp thread.
 
The signatures are created with the PGP key 90725113CA578EAA.
 
Usage Windows and macOS users can download the standalone applications attached to this release, which works without needing Python installed. WinFsp for Windows or FUSE for macOS must still be installed.
 
Linux users (and users who prefer to use their installed Python) can install this release via pip, or by downloading the &quot;&quot;Source code&quot;&quot; archive. Python 3.6.1 or later is required. Read the README for more setup and usage details.
 
<syntaxhighlight>
 
'''Command line install'''
 
Windows
 
py -3 -mpip install --upgrade https://github.com/ihaveamac/ninfs/releases/download/v1.7b2/ninfs-1.7b2-src.zip
With GUI support: py -3 -m pip install --upgrade https://github.com/ihaveamac/ninfs/releases/download/v1.7b2/ninfs-1.7b2-src.zip#egg=ninfs[gui]
 
macOS
 
FUSE for macOS is required.
 
python3 -mpip install --upgrade https://github.com/ihaveamac/ninfs/releases/download/v1.7b2/ninfs-1.7b2-src.zip
With GUI support: python3 -m pip install --upgrade https://github.com/ihaveamac/ninfs/releases/download/v1.7b2/ninfs-1.7b2-src.zip#egg=ninfs[gui]
 
Linux
 
python3 -mpip install --upgrade --user https://github.com/ihaveamac/ninfs/releases/download/v1.7b2/ninfs-1.7b2-src.zip
--user is not required if you are using a virtualenv.
With GUI support: python3 -m pip install --upgrade --user https://github.com/ihaveamac/ninfs/releases/download/v1.7b2/ninfs-1.7b2-src.zip#egg=ninfs[gui]


</syntaxhighlight>
[[Category:3DS homebrew applications]]
[[Category:PC utilities for 3DS homebrew]]

Revision as of 02:44, 20 March 2022

Ninfs
File:Ninfs.png
General
Authorihaveamac
TypePC Utilities
Version2.0a6
LicenseMixed
Last Updated2021/06/22
Links
Download
Website
Source

ninfs (formerly fuse-3ds) is a FUSE program to extract data from Nintendo game consoles. It works by presenting a virtual filesystem with the contents of your games, NAND, or SD card contents, and you can browse and copy out just the files that you need.

Requires Python 3.6.1+. Supports Windows (7 or later), macOS, and Linux.

Features

  • Mount a NAND backup and browse CTRNAND, TWLNAND, and others, and write back to them without having to extract and decrypt them first.
  • Browse decrypted SD card contents. Dump installed games and saves, or copy contents between two system's SD contents.
  • Extract a game's files out of a CIA, CCI (".3ds"), NCCH, RomFS, raw CDN contents, just by mounting them and browsing its files. Or use the virtual decrypted file and start playing the game in Citra right away.

Installation

bootROM: For 3DS types, The ARM9 bootROM is required. You can dump it using boot9strap, which can be set up by 3DS Hacks Guide. To dump the bootROM, hold Start+Select+X when you boot up your 3DS. It is checked in order of:

  • --boot9 argument (if set)
  • BOOT9_PATH environment variable (if set)
  • %APPDATA%\3ds\boot9.bin (Windows-specific)
  • ~/Library/Application Support/3ds/boot9.bin (macOS-specific)
  • ~/.3ds/boot9.bin
  • ~/3ds/boot9.bin

boot9_prot.bin can also be used in all of these locations.

"~" means the user's home directory. "~/3ds" would mean /Users/username/3ds on macOS and C:\Users\username\3ds on Windows.

SeedDB: CDN, CIA, and NCCH mounting may need SeedDB for mounting NCCH containers of newer games (2015+) that use seeds. SeedDB is checked in order of:

  • --seeddb argument (if set)
  • SEEDDB_PATH environment variable (if set)
  • %APPDATA%\3ds\seeddb.bin (Windows-specific)
  • ~/Library/Application Support/3ds/seeddb.bin (macOS-specific)
  • ~/.3ds/seeddb.bin
  • ~/3ds/seeddb.bin

Windows

Using Installer:

  • An installer is provided in releases. It includes both ninfs and WinFsp, which is installed if required.

Using Standalone release:

  • A standalone zip is also provided in releases. WinFsp must be installed separately.

Installing with existing Python:

  • Install the latest version of Python 3. The x86-64 version is preferred on 64-bit Windows.
    • Python from the Microsoft Store can also be used. If this is used, python3 must be used instead of py -3.
    • This version has some limitations however, such as not being able to mount to directories.
  • Install the latest version of WinFsp.
  • Install ninfs with py -3 -m pip install --upgrade https://github.com/ihaveamac/ninfs/archive/2.0.zip

macOS

Versions of macOS supported by Apple are highly recommended. macOS Sierra is the oldest version that should work. macFUSE is required. No standalone build is available at the moment.

Installing with existing Python:

  • Install the latest version of Python 3. The recommended way is Homebrew. You can also use an installer from python.org or a tool like pyenv.
  • Install the latest version of FUSE for macOS.
  • Install ninfs with python3 -m pip install --upgrade https://github.com/ihaveamac/ninfs/archive/2.0.zip

Linux

Arch Linux:

  • (Note: git versions out of date while build process stabilizes.)
  • ninfs is available in the AUR: normal, with gui.

Other distributions:

  • Recent distributions (e.g. Ubuntu 18.04 and later) should have Python 3.6.1 or later pre-installed, or included in its repositories. If not, you can use an extra repository (e.g. deadsnakes's PPA for Ubuntu), build from source, or use a tool like pyenv.
  • Most distributions should have libfuse enabled/installed by default. Use your package manager if it isn't.
  • Install ninfs with python3 -m pip install --upgrade --user https://github.com/ihaveamac/ninfs/archive/2.0.zip
    • --user is not needed if you are using a virtual environment.
  • You can add a desktop entry with python3 -m ninfs --install-desktop-entry. If you want to install to a location other than the default ($XDG_DATA_HOME), you can add another argument with a path like /usr/local/share.
  • To use the GUI, tkinter needs to be installed. On Debian-/Ubuntu-based systems this is python3-tk. On Fedora this is python3-tkinter.

User guide

Supported types

Nintendo 3DS:
CTR Cart Image .3ds, .cci.
CDN contents cetk, tmd, and contents.
CTR Importable Archive .cia.
Executable Filesystem .exefs, exefs.bin
NAND backup nand.bin
NCCH .cxi, .cfa, .ncch, .app
Read-only Filesystem .romfs, romfs.bin
SD Card Contents Nintendo 3DS from SD
Installed SD Title Contents *.tmd and *.app files
3DSX Homebrew .3dsx
Nintendo DS / DSi
DSi NAND backup nand_dsi.bin
Nintendo DS ROM image .nds, .srl
iQue Player
NAND backup (read-only) nand.bin
Nintendo Switch
NAND backup rawnand.bin

Graphical user interface

  • A GUI can be used by specifying the type to be gui. It controls mounting and unmounting. Examples:
    • Windows: py -3 -mninfs gui
    • *nix: python3 -mninfs gui.

Command line

Mounting:

  • Run a mount script by using "mount_<type>" (e.g. mount_cci game.3ds mountpoint).
  • Use -h to view arguments for a script.
  • If it doesn't work, the other way is to use <python-cmd> -mninfs <type>. Examples:
    • Windows: py -3 -mninfs cci game.3ds mountpoint
    • *nix: python3 -mninfs cci game.3ds mountpoint)

Windows users can use a drive letter like F: as a mountpoint. Or use * and a drive letter will be automatically chosen.

Developer-unit contents are encrypted with different keys, which can be used with --dev with CCI, CDN, CIA, NANDCTR, NCCH, and SD.

Unmounting:

  • Windows: Press Ctrl+C in the command prompt/PowerShell window.
  • macOS (two methods):
    • Right-click on the mount and choose "Eject "drive name"".
    • Run from terminal: diskutil unmount /path/to/mount
  • Linux: Run from terminal: fusermount -u /path/to/mount

Examples

  • 3DS game card dump:

mount_cci game.3ds mountpoint

  • Contents downloaded from CDN:

mount_cdn cdn_directory mountpoint

  • CDN contents with a specific decrypted titlekey:

mount_cdn --dec-key 3E3E6769742E696F2F76416A65423C3C cdn_directory mountpoint

  • CIA:

mount_cia game.cia mountpoint

  • ExeFS:

mount_exefs exefs.bin mountpoint

  • 3DS NAND backup with essential.exefs embedded:

mount_nandctr nand.bin mountpoint

  • 3DS NAND backup with an OTP file (Counter is automatically generated):

mount_nandctr --otp otp.bin nand.bin mountpoint

  • 3DS NAND backup with OTP and CID files:

mount_nandctr --otp otp.bin --cid nand_cid.bin nand.bin mountpoint

  • 3DS NAND backup with OTP file and a CID hexstring:

mount_nandctr --otp otp.bin --cid 7468616E6B7334636865636B696E6721 nand.bin mountpoint

  • DSi NAND backup (Counter is automatically generated):

mount_nandtwl --console-id 5345445543454D45 nand_dsi.bin mountpoint

  • DSi NAND backup with a Console ID hexstring and specified CID hexstring:

mount_nandtwl --console-id 5345445543454D45 --cid 576879446F657344536945786973743F nand_dsi.bin mountpoint

  • DSi NAND backup with a Console ID file and specified CID file:

mount_nandtwl --console-id ConsoleID.bin --cid CID.bin nand_dsi.bin mountpoint

  • iQue Player NAND backup:

mount_nandbb nand.bin mountpoint

  • Switch NAND backup:

mount_nandhac --keys prod.keys rawnand.bin mountpoint

  • Switch NAND backup in multiple parts:

mount_nandhac --keys prod.keys -S rawnand.bin.00 mountpoint

  • Switch NAND encrypted partition dump:

mount_nandhac --keys prod.keys --partition SYSTEM SYSTEM.bin mountpoint

  • NCCH container (.app, .cxi, .cfa, .ncch):

mount_ncch content.cxi mountpoint

  • RomFS:

mount_romfs romfs.bin mountpoint

  • Nintendo 3DS directory from an SD card:

mount_sd --movable movable.sed "/path/to/Nintendo 3DS" mountpoint

  • Nintendo 3DS directory from an SD card with an SD key hexstring:

mount_sd --sd-key 504C415900000000504F4B454D4F4E21 "/path/to/Nintendo 3DS" mountpoint

  • Nintendo DS ROM image (NDS/SRL, mount_nds also works):

mount_srl game.nds mountpoint

  • 3DSX homebrew application:

mount_threedsx boot.3dsx mountpoint

Useful tools

  • wwylele's 3ds-save-tool can be used to extract game saves and extra data (DISA and DIFF, respectively).
  • wwylele's save3ds is a tool to interact with 3DS save files and extdata. Extracting and importing works on all platforms. The FUSE part only works on macOS and Linux.
  • OSFMount for Windows can mount FAT12/FAT16/FAT32 partitions in NAND backups.

Related tools

  • roothorick's BUSEHAC is a Linux driver for encrypted Nintendo Switch NANDs.
  • Maschell's fuse-wiiu can be used to mount Wii U contents.
  • koolkdev's wfslib has wfs-fuse to mount the Wii U mlc dumps and usb devices.

Media

fuse-3ds demonstration with Pokémon Ultra Moon (ihaveamac)

Credits

ninfs is under the MIT license. fuse.py is under the ISC license (taken from setup.py).

Special thanks to @Jhynjhiruu for adding support for iQue Player NAND backups.

Special thanks to @Stary2001 for help with NAND crypto (especially TWL), and @d0k3 for SD crypto.

OTP code is from Stary2001/3ds_tools, and is under the MIT license.

External links

Advertising: