3ds To Cia Converter On Pc

  1. 3ds Simple Cia Converter Pc
  2. 3ds To Cia Converter On Pc Free
  3. 3ds To Cia Converter On Pc Mac
  4. 3ds To Cia Converter On Pc Download

CIA files are limited to containing 65535 NCCH files and can be used to contain NCCH files for any title type. CIA files also contain signed data used by the 3DS for general title management and DRM. Installing custom CIA files on a 3DS which also uses eShop/SysUpdates is unwise as conflicts will likely occur. NCCH configurations for CIA. 3DSISO is a portal to download free 3DS CIA games, here you will find roms for both your 3DS console and games for CITRA an emulator with which you can play both PC and Android devices.The 3DS games on our site are from various regions such as EUR/USA/Japan. To enjoy them you just have to download the desired game from our 3DS games catalogue and unzip it, then transfer it to your R4 card.

makerom
General
Author(s)3dsguy
TypePC utility
Version0.15
Links
Download
Source
Free


makerom is a tool which can be used to create NCCH, CCI, and CIA files.

  • 1Format Overviews
    • 1.2CCI
    • 1.3CIA
  • 2Using Makerom
    • 2.1Command line

Format Overviews[edit]

NCCH[edit]

3ds Simple Cia Converter Pc

The native format storing code binaries and data archives for the 3DS is NCCH. NCCH files are comprised of:

  • code/exheader/plainregion (used for code execution) (plainregion just lists included SDK library add-ons)
  • icon (app title text, icon, homemenu settings, see here
  • banner (cbmd + cwav, i.e. the upper screen banner/sound shown on the homemenu)
  • logo (the splash screen displayed after an application is launched from the homemenu)
  • romfs (read-only filesystem used to store resources)

Typical uses for NCCH files include:

  • Executable image (code+exheader+icon+banner+logo+romfs)
  • e-Manual archive (accessed from homemenu) (romfs)
  • DLP child CIA archive (accessed from application) (romfs)
  • Update Data archive (romfs)
  • Standalone data archive (romfs)
  • DLC index archive (icon+romfs)
  • DLC archive (romfs)

CCI[edit]

The native format for gamecard images is CCI and is a NCCH container format. CCI files are limited to containing 8 NCCH files, and can contain NCCH files for applications titles only.

NCCH configuration for CCI[edit]

NCCHRequiredIndex
Executable imageYES0
e-Manual archiveNO1
DLP child CIA archiveNO2
Update Data archiveNO7

CIA[edit]

The native format for packaging NCCH files for install is CIA, which is also a NCCH container format. CIA files are limited to containing 65535 NCCH files and can be used to contain NCCH files for any title type. CIA files also contain signed data used by the 3DS for general title management and DRM. Installing custom CIA files on a 3DS which also uses eShop/SysUpdates is unwise as conflicts will likely occur.

NCCH configurations for CIA[edit]

Applications (Application/DlpChild/Demo/Patch/SystemApplication):

NCCHRequiredIndex
Executable imageYES0
e-Manual archiveNO1
DLP child CIA archiveNO2

System Applet/Module:

NCCHRequiredIndex
Executable imageYES0

System Data Archives:

NCCHRequiredIndex
Data archiveYES0

DLC:

The number of DLC data archives in DLC varies for each DLC.

NCCHRequiredIndex
DLC index archiveYES0
DLC data archiveYESVaries

Using Makerom[edit]

Command line[edit]

General Arguments

ArgumentAcceptable valuesNotes
-f <format>'ncch'/'cxi'/'cfa'/'cci'/'cia'Specify the output file format. 'ncch'/'cxi'/'cfa' has no affect, probably parsed without error for legacy support.
-o <path>Valid file path.Specify name/path for output file. Makerom will decided a name if this is not specified.
-vnot requiredEnables verbose output.

RSF Arguments

ArgumentAcceptable valuesNotes
-rsf <path>Valid file pathSpecify the path to Rom Specification File(RSF). See below for creating RSF.
-D<NAME>=<VALUE>This is used to substitute where '$(<NAME>)' exists in the RSF files with '<VALUE>'. (Uppercase isn't a requirement)

Crypto Arguments

Cia
ArgumentAcceptable valuesNotes
-target <target>'t'/'d'/'p'Specify key-chain. This affects encryption, signing and '-desc' template availability. t=test, suitable for homebrew. d=devkit(incomplete), suitable for devkits. p=retail(unusable), suitable for signing retail software?
-ckeyid <index>Any value between 0-255 (inclusive).Overrides the default common key used to encrypt CIA title keys.
-showkeysnoneDumps loaded key-chain to stdout.

NCCH Build Arguments

ArgumentAcceptable valuesNotes
-elf <file>Valid file pathSpecify ELF. See below for creating ELF.
-icon <file>Valid file pathSpecify icon.
-banner <file>Valid file pathSpecify banner.
-desc <apptype>:<fw><apptype>='app'/'ecapp'/'demo'/'dlpchild'. <fw>='kernel version minor'.Use a template for exheader/accessdesc. These are hard-coded, so not all firmwares have a template. A value from 1-7 can be used in place of 'kernel version minor'. A template shouldn't be used if the title needs 'special' permissions, the RSF must be configured fully.
-exefslogononeInclude logo in ExeFS. Required for usage on <5.0 systems.
3ds to cia converter for pc program

Arguments useful for rebuilding a NCCH file:

ArgumentAcceptable valuesNotes
-code <file>Valid file pathSpecify decompressed/plaintext exefs code binary.
-exheader <file>Valid file pathSpecify plaintext exheader binary.
-logo <file>Valid file pathSpecify logo.
-plainrgn <file>Valid file pathSpecify NCCH plain-region.
-romfs <file>Valid file pathSpecify an unencrypted RomFS binary.

CCI Arguments

ArgumentAcceptable valuesNotes
-content <path>:<index><path>=Valid file path. <index>=Any value between 0-7 (inclusive)Include a built NCCH file in the CCI container. '-i' can be used instead of '-content'.
-devccinoneBuild a debug CCI?
-nomodtidnoneDon't modify the TitleIds of NCCH files included to match NCCH0
-alignwrnoneAlign the offset for the Card2 writable region to the end of the last NCCH in the CCI.

CIA Arguments

ArgumentAcceptable valuesNotes
-content <path>:<index>:<id><path>=Valid file path. <index>=Any value between 0x0-0xFFFF (inclusive). <id>=Any value between 0x0-0xFFFFFFFF (inclusive)Include a built NCCH file in the CIA container. If <id> isn't specified, it will be generated randomly. '-i' can be used instead of '-content'.
-major <version>Any value between 0-63 (inclusive)Specify the version major for the title. This cannot be used with '-dver'.
-minor <version>Any value between 0-63 (inclusive)Specify the version minor for the title. This cannot be used with '-dver'.
-micro <version>Any value between 0-15 (inclusive)Specify the version micro for the title.
-dver <version>Any value between 0-4095 (inclusive)Specify the or '-minor'.
-dlcnoneSpecify this flag when building a DLC CIA.
-randnoneUse a random title key to encrypt CIA content.

Examples[edit]

General examples:

Create CXI

Create CFA

Create CCI

Create CIA


Makerom supports building a NCCH file and including it automatically (as index 0) into a NCCH container:

Create CCI and CXI at the same time and include a CFA

Create CIA and CXI at the same time and include a CFA

Rebuilding CXI:

Creating RSF files[edit]

Inspired by Nintendo's format for their makerom, a yaml configuration file is required for creating NCCH files. CIA/CCI can be created without using a RSF file, but default settings will be used.

For CXI, RSF files can be used to specify permissions, and access control settings. Makerom can use default settings by use of the '-desc' option, which removes the requirement for specifying them in the RSF file.

Sample RSF to be used with '-desc': download (link broken)

Sample RSF to be used without '-desc': download

Windows

Creating ELF files[edit]

The latest devkitARM used in conjunction with ctrulib can create ELF files compatible with makerom.

ELF files that are created using the official SDK are also supported by makerom.

Compiling Source[edit]

For Windows a MinGW-W64/MSYS build setup is required.

For Linux, gcc/g++/make must be installed.

All additional libraries used by makerom (polarssl/libyaml) are included in the source, and are linked statically.

Retrieved from 'https://www.3dbrew.org/w/index.php?title=Makerom&oldid=17471'

The below wiki article is based on user submitted content.
Please verify all hyperlinks and terminal commands below!

See a mistake? Want to contribute? Edit this article on Github

How to Transfer 3DS Save Data to Citra

There are multiple ways to transfer 3DS save data to Citra in a usable form, but the important thing to note is that whatever tool used to get the save data off of the 3DS supports exporting expanded save data. Save data lives in Citra’s emulated SD card directories (user/sdmc/Nintendo 3DS/000...0/000...0/title/[game-TID-high]/[game-TID-low]/data/00000001/).

threeSD

3ds To Cia Converter On Pc Free

threeSD is a tool written to help import data from your 3DS for Citra more conveniently.

Refer to threeSD Quickstart Guide for importing your installed titles, updates, DLCs, save data, extra data, system files, etc. Note that you’ll still need a hacked 3DS with GodMode9 to obtain your keys so that threeSD can decrypt the data on your SD card.

Checkpoint

As the supported way of transferring save data, Checkpoint is easy to install and use.

Required tools

3ds To Cia Converter On Pc Mac

3ds
  • A 3DS with boot9strap installed
  • Checkpoint.
  • SD card reader (preferred), or a way to use wireless file transfer

Installing Checkpoint

  1. Download Checkpoint from the link above.
  2. For cia installation, transfer the cia file to the SD card and install it with a cia installer such as FBI. For Rosalina-based Homebrew Launcher, transfer the 3dsx file to /3ds/ on the SD card. Hax-based Homebrew Launchers are not supported by Checkpoint.

Transferring Save Data

3ds To Cia Converter On Pc Download

  1. Open Checkpoint. If this is the first time launching Checkpoint, it may take a considerably longer than usual depending on the amount of installed titles.
  2. Highlight the game you want to dump by navigating to it with the D-pad.
  3. Press A and select Backup on the bottom screen. You will be prompted Yes or No. Select Yes by pressing A.
  4. You will have the option to name the save folder. Name it whatever you want or use the name given to it. Press OK on the bottom screen.
  5. The top screen will flash a message Success! Progress correctly saved to disk. Exit out of Checkpoint.
  6. Transfer all files located in /3ds/Checkpoint/saves/[Game Name]/[Folder created in Step 4] to the computer.
  7. Place the files in Citra’s emulated SD card’s save directory. You can open the save directory by right-clicking on a game in Citra and clicking “Open Save Data Directory”. If the directory doesn’t exist, start the game once and the directory will be created.
Example diagram showing the correct location of New Super Mario Bros. 2 save data in Citra’s User Directory.