3DS CIA Manager List all CIA files from a folder and display its ID. Leerz: Thread: 3DS to CIA converter Convert.3DS files to.CIA format CCI/CIA Command Builder (aka ROMTool GUI) TiniVi: Thread: Git: CIA Auto-Generator Script to speed up cia generation mmn: Thread: Cia to TitleID List all cia files from a folder and display its ID. Free download 3ds to cia converter v4 1 for android apk. Convert 3ds to cia. #####So what is it? It's a Windows program to convert 3DS roms to CIA files, those CIA files can then be used to install the converted 3DS rom on Gateway or Custom FirmWare (CFW) It can convert Multiple roms at 1 go:) #####Why a guide if it's so simple?
| makerom | |
| General | |
|---|---|
| Author(s) | 3dsguy |
| Type | PC utility |
| Version | 0.15 |
| Links | |
| Download | |
| Source |
3DS Hacks - Convert 3DS ROMs to.cia Nintendo 3DS games can often be found in the.3ds format, which is intended for emulators like Citra. Nintendo 3DS consoles cannot load.3ds ROM files, however they can be converted to.cia format which can be installed on hacked 3DS consoles with FBI. ☆┌─┐ ─┐☆ │ │ -│ │-│ - -─┬─inscreva-se em meu canal │ │ │ │┌┴─┴─┐-┘─┘ clica em gostei│ ┌──┘ │└┐ ┌┘ compartilha o.
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 By Rikukh3 3
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]
| NCCH | Required | Index |
|---|---|---|
| Executable image | YES | 0 |
| e-Manual archive | NO | 1 |
| DLP child CIA archive | NO | 2 |
| Update Data archive | NO | 7 |
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):
| NCCH | Required | Index |
|---|---|---|
| Executable image | YES | 0 |
| e-Manual archive | NO | 1 |
| DLP child CIA archive | NO | 2 |
System Applet/Module:
| NCCH | Required | Index |
|---|---|---|
| Executable image | YES | 0 |
System Data Archives:
| NCCH | Required | Index |
|---|---|---|
| Data archive | YES | 0 |
DLC:
The number of DLC data archives in DLC varies for each DLC.
| NCCH | Required | Index |
|---|---|---|
| DLC index archive | YES | 0 |
| DLC data archive | YES | Varies |
Using Makerom[edit]
Command line[edit]
General Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -f | 'ncch'/'cxi'/'cfa'/'cci'/'cia' | Specify the output file format. 'ncch'/'cxi'/'cfa' has no affect, probably parsed without error for legacy support. |
| -o | Valid file path. | Specify name/path for output file. Makerom will decided a name if this is not specified. |
| -v | not required | Enables verbose output. |
RSF Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -rsf | Valid file path | Specify the path to Rom Specification File(RSF). See below for creating RSF. |
| -D= | This is used to substitute where '$()' exists in the RSF files with ''. (Uppercase isn't a requirement) |
Crypto Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -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 | Any value between 0-255 (inclusive). | Overrides the default common key used to encrypt CIA title keys. |
| -showkeys | none | Dumps loaded key-chain to stdout. |
NCCH Build Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -elf | Valid file path | Specify ELF. See below for creating ELF. |
| -icon | Valid file path | Specify icon. |
| -banner | Valid file path | Specify banner. |
| -desc : | ='app'/'ecapp'/'demo'/'dlpchild'. ='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. |
| -exefslogo | none | Include logo in ExeFS. Required for usage on <5.0 systems. |
Arguments useful for rebuilding a NCCH file:
| Argument | Acceptable values | Notes |
|---|---|---|
| -code | Valid file path | Specify decompressed/plaintext exefs code binary. |
| -exheader | Valid file path | Specify plaintext exheader binary. |
| -logo | Valid file path | Specify logo. |
| -plainrgn | Valid file path | Specify NCCH plain-region. |
| -romfs | Valid file path | Specify an unencrypted RomFS binary. |
CCI Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -content : | =Valid file path. =Any value between 0-7 (inclusive) | Include a built NCCH file in the CCI container. '-i' can be used instead of '-content'. |
| -devcci | none | Build a debug CCI? |
| -nomodtid | none | Don't modify the TitleIds of NCCH files included to match NCCH0 |
| -alignwr | none | Align the offset for the Card2 writable region to the end of the last NCCH in the CCI. |
CIA Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -content :: | =Valid file path. =Any value between 0x0-0xFFFF (inclusive). =Any value between 0x0-0xFFFFFFFF (inclusive) | Include a built NCCH file in the CIA container. If isn't specified, it will be generated randomly. '-i' can be used instead of '-content'. |
| -major | Any value between 0-63 (inclusive) | Specify the version major for the title. This cannot be used with '-dver'. |
| -minor | Any value between 0-63 (inclusive) | Specify the version minor for the title. This cannot be used with '-dver'. |
| -micro | Any value between 0-15 (inclusive) | Specify the version micro for the title. |
| -dver | Any value between 0-4095 (inclusive) | Specify the or '-minor'. |
| -dlc | none | Specify this flag when building a DLC CIA. |
| -rand | none | Use 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
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.
.cia files) is a simple process using the FBI application, many homebrew applications also come in .cia format and will appear in the Home menu once installed. Homebrew applications in .3dsx format are not installed, instead, they must be copied to your SD card and loaded via the Homebrew Launcher. This guide will show you how to install backup games and homebrew applications from your SD card onto your hacked 3DS.Hacked (New) Nintendo 3DS (XL) Console
- A hacked 3DS with FBI and the Homebrew Launcher are required to install games and homebrew applications
- These are usually installed as part of the hacking process for 3DS
- Follow this guide (with pictures) or Plailect's guide on hacking your 3DS if you have not done so before
- An SD Card is required to store the exploit files and homebrew apps
- 32GB or more is recommended to store games
- The SD card must be formatted to FAT32
- MicroSD cards are compatible with Old 3DS consoles via a MicroSD to SD adapter
- Place any
.ciafiles you wish to install in the/cia/folder on your SD card - Insert your SD card into your 3DS and power it on
- Launch FBI and navigate to
SD->cia - Select your
.cia-> [Install and delete CIA] - Once installed, press [Home] your game can be found in the home menu
.3ds format, however this is not compatible with 3DS consoles and is generally intended for 3DS emulators such as Citra. .3ds files must be converted to .cia before they can be installed on your 3DS. Follow this guide on Converting 3DS ROMs to .cia with GodMode9.3DS Homebrew Application come in the form of .3dsx files and can be run via the Homebrew Launcher
- Place your
.3dsxfile in the/3ds/folder on your 3DS SD card - Insert your SD card into your 3DS and power it on
- Launch the Homebrew Launcher from the home menu
- Select your app from the list to launch it
Convert 3DS ROMs for Installation
- Use GodMode9 to convert your
.3dsROM's to.ciafiles that can be installed on your 3DS
Dump Cartridges to SD
- Play your games without the cartridge inserted by dumping them directly to your SD card with GodMode9
- Cartridges can be dumped as multiple formats:
.ciafor 3DS consoles,.3dsfor emulators or.ndsfor Nintendo DS games
Play DS Games with TWiLight Menu++
- Play Nintendo DS ROM's flawlessly using TWiLight Menu++
- The application also features a built-in cheats manager
3ds Simple Cia Converter By Rikukh3 2
Install Virtual Console Games (GBC, GBA, SNES etc)
3ds Simple Cia Converter By Rikukh3 1
- Convert ROM's to Virtual Console titles and install them directly to your Home menu using New Super Ultimate Injector
System Data Archives:
| NCCH | Required | Index |
|---|---|---|
| Data archive | YES | 0 |
DLC:
The number of DLC data archives in DLC varies for each DLC.
| NCCH | Required | Index |
|---|---|---|
| DLC index archive | YES | 0 |
| DLC data archive | YES | Varies |
Using Makerom[edit]
Command line[edit]
General Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -f | 'ncch'/'cxi'/'cfa'/'cci'/'cia' | Specify the output file format. 'ncch'/'cxi'/'cfa' has no affect, probably parsed without error for legacy support. |
| -o | Valid file path. | Specify name/path for output file. Makerom will decided a name if this is not specified. |
| -v | not required | Enables verbose output. |
RSF Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -rsf | Valid file path | Specify the path to Rom Specification File(RSF). See below for creating RSF. |
| -D= | This is used to substitute where '$()' exists in the RSF files with ''. (Uppercase isn't a requirement) |
Crypto Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -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 | Any value between 0-255 (inclusive). | Overrides the default common key used to encrypt CIA title keys. |
| -showkeys | none | Dumps loaded key-chain to stdout. |
NCCH Build Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -elf | Valid file path | Specify ELF. See below for creating ELF. |
| -icon | Valid file path | Specify icon. |
| -banner | Valid file path | Specify banner. |
| -desc : | ='app'/'ecapp'/'demo'/'dlpchild'. ='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. |
| -exefslogo | none | Include logo in ExeFS. Required for usage on <5.0 systems. |
Arguments useful for rebuilding a NCCH file:
| Argument | Acceptable values | Notes |
|---|---|---|
| -code | Valid file path | Specify decompressed/plaintext exefs code binary. |
| -exheader | Valid file path | Specify plaintext exheader binary. |
| -logo | Valid file path | Specify logo. |
| -plainrgn | Valid file path | Specify NCCH plain-region. |
| -romfs | Valid file path | Specify an unencrypted RomFS binary. |
CCI Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -content : | =Valid file path. =Any value between 0-7 (inclusive) | Include a built NCCH file in the CCI container. '-i' can be used instead of '-content'. |
| -devcci | none | Build a debug CCI? |
| -nomodtid | none | Don't modify the TitleIds of NCCH files included to match NCCH0 |
| -alignwr | none | Align the offset for the Card2 writable region to the end of the last NCCH in the CCI. |
CIA Arguments
| Argument | Acceptable values | Notes |
|---|---|---|
| -content :: | =Valid file path. =Any value between 0x0-0xFFFF (inclusive). =Any value between 0x0-0xFFFFFFFF (inclusive) | Include a built NCCH file in the CIA container. If isn't specified, it will be generated randomly. '-i' can be used instead of '-content'. |
| -major | Any value between 0-63 (inclusive) | Specify the version major for the title. This cannot be used with '-dver'. |
| -minor | Any value between 0-63 (inclusive) | Specify the version minor for the title. This cannot be used with '-dver'. |
| -micro | Any value between 0-15 (inclusive) | Specify the version micro for the title. |
| -dver | Any value between 0-4095 (inclusive) | Specify the or '-minor'. |
| -dlc | none | Specify this flag when building a DLC CIA. |
| -rand | none | Use 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
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.
.cia files) is a simple process using the FBI application, many homebrew applications also come in .cia format and will appear in the Home menu once installed. Homebrew applications in .3dsx format are not installed, instead, they must be copied to your SD card and loaded via the Homebrew Launcher. This guide will show you how to install backup games and homebrew applications from your SD card onto your hacked 3DS.Hacked (New) Nintendo 3DS (XL) Console
- A hacked 3DS with FBI and the Homebrew Launcher are required to install games and homebrew applications
- These are usually installed as part of the hacking process for 3DS
- Follow this guide (with pictures) or Plailect's guide on hacking your 3DS if you have not done so before
- An SD Card is required to store the exploit files and homebrew apps
- 32GB or more is recommended to store games
- The SD card must be formatted to FAT32
- MicroSD cards are compatible with Old 3DS consoles via a MicroSD to SD adapter
- Place any
.ciafiles you wish to install in the/cia/folder on your SD card - Insert your SD card into your 3DS and power it on
- Launch FBI and navigate to
SD->cia - Select your
.cia-> [Install and delete CIA] - Once installed, press [Home] your game can be found in the home menu
.3ds format, however this is not compatible with 3DS consoles and is generally intended for 3DS emulators such as Citra. .3ds files must be converted to .cia before they can be installed on your 3DS. Follow this guide on Converting 3DS ROMs to .cia with GodMode9.3DS Homebrew Application come in the form of .3dsx files and can be run via the Homebrew Launcher
- Place your
.3dsxfile in the/3ds/folder on your 3DS SD card - Insert your SD card into your 3DS and power it on
- Launch the Homebrew Launcher from the home menu
- Select your app from the list to launch it
Convert 3DS ROMs for Installation
- Use GodMode9 to convert your
.3dsROM's to.ciafiles that can be installed on your 3DS
Dump Cartridges to SD
- Play your games without the cartridge inserted by dumping them directly to your SD card with GodMode9
- Cartridges can be dumped as multiple formats:
.ciafor 3DS consoles,.3dsfor emulators or.ndsfor Nintendo DS games
Play DS Games with TWiLight Menu++
- Play Nintendo DS ROM's flawlessly using TWiLight Menu++
- The application also features a built-in cheats manager
3ds Simple Cia Converter By Rikukh3 2
Install Virtual Console Games (GBC, GBA, SNES etc)
3ds Simple Cia Converter By Rikukh3 1
- Convert ROM's to Virtual Console titles and install them directly to your Home menu using New Super Ultimate Injector
Luma3DS Cheats with Checkpoint
3ds Simple Cia Converter By Rikukh3 X
- Easily load game cheats with Checkpoint and activate them using the cheat manager in the Rosalina menu (Luma3DS)
