3dbrew - User contributions [en]

Talk:SMDH

2012-04-09T11:47:36Z

Lazymarek9614: Created page with "Thanks for clearing this up, yellows8! I remember if I saw the SMDH magic in CIAs and wondered why its structure was in CIAs only...--~~~~"

Thanks for clearing this up, yellows8! I remember if I saw the SMDH magic in CIAs and wondered why its structure was in CIAs only...--[[User:Lazymarek9614|Lazymarek9614]] 15:47, 9 April 2012 (CEST)

Category:File formats

2012-03-28T10:36:14Z

Lazymarek9614: /* Applications ( any executable code ) */

The following is a list of known file formats used by the 3DS.

=== Applications ( any executable code ) ===

.[[CCI]] - Cart image. Burned into a ROM (or loaded by official debugging hardware). These are also the actual format of ROM dumps, and the response of read requests between a 3DS and a cartridge.

.[[CXI]] - Executable image. Similar to above. The difference is CXI applications are installed onto [thus ran from] NAND.

.[[CIA]] - (CTR Importable Archive) It is the application compiled into an archive, ready to be installed to a designated location. A .CIA file can be extracted to install applications to the, CTR NAND, TWL NAND (part of the NAND used by DSi applications), and the SD card.

.[[CCI|CSU]] - System Update. Format varies slightly with revisions.

.CFA - CTR File Archive - Externalized ROM-FS. CXI data and ROMFS data can be separated into a list of external files instead of compiled into just 1 CXI image (Normally not used). Lib states this is similar to a CIA, a little like an archive of a CIA. Fortunately lib has some info on this format. CFA files are basically multiple packed CIAs. CFAs are used when the CCI file includes the child device distributed with download play.

.NSA - Archive used by several of the communication protocols in the 3DS.

.RSF - Descriptive data used when outputting a CCI/CXI file. Specifies options such as: title, save type, and so on.

.AXF - Pre-assembled ARM code. before being linked into a CCI/CXI format. They're practically ARM specific ELF files.

.CDI - CTR Development Image. Lib did not have any documentation about what this format is, what it does, etc. I had to go digging through the compiler to find this format listed. Hopefully I'll find more soon. *Possibly* associated with the CTR Debugger but that's just a guess.

.CIP - CTR Initial Process. Unfortunately the circumstance is much like the CDI format, but it's in the lib compiler so it is some type of format used by the 3DS.

.[[BCWAV]] - CTR waveform file format

.[[CBMD]] - CTR binary banner model. Archive file before being made into a CTR banner for games or other applications.

=== Filesystem ===

The 3DS filesystem requires absolute paths. It can handle either short (8.3) and long (255 char maximum) file names.

== MPO (Multi-Picture Object Format) ==
Document describing the file format used in mpo files:
http://www.cipa.jp/english/hyoujunka/kikaku/pdf/DC-007_E.pdf

[[MPO|Nintendo's MPO Specifications]]

File talk:Pinout point.jpg

2012-03-19T15:36:47Z

Lazymarek9614: Created page with "Without the description of these numbers the photo is useless, please add them!--~~~~"

Without the description of these numbers the photo is useless, please add them!--[[User:Lazymarek9614|Lazymarek9614]] 17:36, 19 March 2012 (CET)

Talk:CiTRUS

2012-03-02T19:17:50Z

Lazymarek9614:

About the XBSF format, is it a Nintendo's file format? Will It include an executable image? Are there the sources of CITRUS?--[[User:Jocopoco|Jocopoco]] 08:08, 9 February 2012 (CET)

Not to downplay the usefulness of this program, but what purpose does it serve for people who don't get to play around with dev 3DSes? --[[User:Luigi2us|Luigi2us]] 22:58, 27 February 2012 (CET)

"it can be retail signed, provided the right RSA keys" Which is impossible, not even official devs have that retail RSA private key.(they send their titles to Nintendo to sign, like they *always* have) Therefore the output CXI *is* dev unit only. --[[User:Yellows8|Yellows8]] 03:36, 2 March 2012 (CET)

This application and the linked .CXI are complete crap. The .bcwav file in the application is a mutilated .WAV file, the .ctpk files are just a series of random 0x00 and 0xFF, the .cbmd is another mutilated file (I believe some image file), and the .cxi is complete crap (just look at the file in a hex editor and tell me that's not immediately ridiculous). Calling for deletion of this ridiculous page. --[[User:Trap15|trap15]] 05:59, 2 March 2012 (CET)

Well the files may be legit, but since there's no way to obtain other files than the ones he provided, this is mostly a toy. Have fun creating the same output file over and over again :/ --[[User:Luigi2us|Luigi2us]] 12:21, 2 March 2012 (CET)

Nintendo wouldn't use a bog-standard .WAV with changed header names. I can 100% guarantee you that. I am about 99% sure that this code, and [[User:Xcution|Xcution]] are Complete Bullshit™. --[[User:Trap15|trap15]] 19:12, 2 March 2012 (CET)
:They [http://www.feshrine.net/hacking/doc/nds-sdat.html did] and they do. --[[User:Elisherer|Elisherer]] 19:20, 2 March 2012 (CET)

Xcution Is there a way for decrypt your demo?--[[User:Jocopoco|Jocopoco]] 19:11, 2 March 2012 (CET)
:No. --[[User:Trap15|trap15]] 19:12, 2 March 2012 (CET)
Why? Is it a fake? --[[User:Jocopoco|Jocopoco]] 19:20, 2 March 2012 (CET)
:Yes. --[[User:Trap15|trap15]] 20:22, 2 March 2012 (CET)

Xcution, here you can find the reason why none will use your tool for creating homebrew: [[Talk:Homebrew_Format]].--[[User:Lazymarek9614|Lazymarek9614]] 21:17, 2 March 2012 (CET)

File talk:Exefs dec Xcution.png

2012-02-23T17:15:51Z

Lazymarek9614:

How did you get decrypted content? The 3DS keys haven't been dumped yet, and the encryption layer is atleast as complex as the DSi's. Or is that some kind of debug CXI that was encrypted with a simpler, insecure key? --[[User:Luigi2us|Luigi2us]] 18:59, 23 February 2012 (CET)
:hehe, Xcution has the SDK... btw is it legal to share the key?--[[User:Lazymarek9614|Lazymarek9614]] 19:15, 23 February 2012 (CET)

User talk:3DSmo-less-tor

2012-02-22T12:40:50Z

Lazymarek9614: go to gbatemp with your ideas

I'm not a dev, but I see potential for custom firmware of something like Priiloader on the Wii, It would be able to trick the bootloader to load to a specific point, bypassing the 3DS MENU security features. Tell me if this makes sence?
:I don't see the potential you are talking about. No, it does not make sense.--[[User:Lazymarek9614|Lazymarek9614]] 14:40, 22 February 2012 (CET)

User:PsyKopaT

2012-02-06T17:37:43Z

Lazymarek9614: answered

Hi, I am the maker of DSRO, and was wondering if you could help me.
I am looking for the file header structure for the 3DS files.
I saw that you have your own program, and was wondering if you could share me the file header structure, since the NDS one doesn't work for it.

Thank you in advance

:Please don't say 3DS files, they're [[CCI]]s.
:Actually we don't need another tool for parsing ROM dumps, we have enough IMO.--[[User:Lazymarek9614|Lazymarek9614]] 19:37, 6 February 2012 (CET)

Title list

2011-12-22T14:22:05Z

Lazymarek9614: /* 00040000 - eShop Titles */ added letter box

The Nintendo 3DS utilizes a similar title-based organization as seen in the Wii and DSi platforms. The same [http://nus.cdn.c.shop.nintendowifi.net/ccs/download/ update server] is being used as was with the DSi, however a new common key has been introduced.

The organization of Title IDs has not been documented fully yet. It's unknown how regions are determined in titleids if at all though there does appear to be evidence that the regions are sequential, similar to how Wii System Menu Updates are ordered: JPN USA EUR KOR and CHN (introduced with the DSi).

== 00000000 - Ext/Extra Data ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Region
! Description
! Versions
|-
| 000004aa
| USA
| Nintendo Video Extra Data
(Notes: This is where the video files are stored, and I assume the thumbnails, the descriptions, and some check sum files. There are always 9 files within the subdirectory "00000000" of this folder, even without any videos downloaded. The files are "00000001" - "00000009", and "00000003" - "00000008" have the same filesize of 50.7 MB. It is possible to restore the older videos by overwriting all the files within this directory. Provided of course you have made a backup of the files before hand, by copying all the files within this directory to your computer. As far I'm aware its not possible to mix and match the files in order to get certain videos in one grouping, ie. having all 3 Zelda orchestral recordings in one group of 4 Nintendo videos.)
| v0
|}

== 00040010 - System Applications ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Region
! Description
! Versions
! Status
|-
| 00020000
| JPN
| ?
| v0, v1027, v2062
| Active
|-
| 00021000
| USA
| ?
| v0, v1027, v2062
| Active
|-
| 00022000
| EUR
| ?
| v0, v1027, v2062
| Active
|-
| 00020100
| JPN
| ?
| v0, v1026
| Active
|-
| 00021100
| USA
| ?
| v0, v1026
| Active
|-
| 00022100
| EUR
| ?
| v0, v1026
| Active
|-
| 00020200
| JPN
| ?
| v0, v1026, v2054
| Active
|-
| 00021200
| USA
| ?
| v0, v1026, v2054
| Active
|-
| 00022200
| EUR
| ?
| v0, v1026, v2054
| Active
|-
| 00020300
| JPN
| ?
| v0
| Active
|-
| 00021300
| USA
| ?
| v0
| Active
|-
| 00022300
| EUR
| ?
| v0
| Active
|-
| 00020400
| JPN
| [[Nintendo 3DS Camera]]
| v0, v16, v1039
| Active
|-
| 00021400
| USA
| [[Nintendo 3DS Camera]]
| v0, v16, v1039
| Active
|-
| 00022400
| EUR
| [[Nintendo 3DS Camera]]
| v0, v16, v1039
| Active
|-
| 00020500
| JPN
| [[Nintendo 3DS Sound]]
| v0, v1027, v2049
| Active
|-
| 00021500
| USA
| [[Nintendo 3DS Sound]]
| v0, v1027, v2049
| Active
|-
| 00022500
| EUR
| [[Nintendo 3DS Sound]]
| v0, v1027, v2049
| Active
|-
| 00020700
| JPN
| ?
| v0, v1026
| Active
|-
| 00021700
| USA
| ?
| v0, v1026
| Active
|-
| 00022700
| EUR
| ?
| v0, v1026
| Active
|-
| 00020800
| JPN
| [[StreetPass Mii Plaza]]
| v0, v1027, v2048, v3087, v4096
| Active
|-
| 00021800
| USA
| [[StreetPass Mii Plaza]]
| v0, v1027, v2048, v3087, v4096
| Active
|-
| 00022800
| EUR
| [[StreetPass Mii Plaza]]
| v0, v1027, v2048, v3087, v4096
| Active
|-
| 00020900
| JPN
| [[eShop]]
| v4, v1026, 2058
| Active
|-
| 00021900
| USA
| [[eShop]]
| v4, v1026, v2058
| Active
|-
| 00022900
| EUR
| [[eShop]]
| v4, v1026, v2058
| Active
|-
| 00020A00
| JPN
| Web browser
| v4, v1035
| Active
|-
| 00021A00
| USA
| Web browser
| v4, v1035
| Active
|-
| 00022A00
| EUR
| Web browser
| v4, v1035
| Active
|-
| 00020B00
| JPN
| [[Nintendo Zone]]
| v0, v1034
| Active
|-
| 00021B00
| USA
| [[Nintendo Zone]]
| v0, v1034
| Active
|-
| 00022B00
| EUR
| [[Nintendo Zone]]
| v0, v1034
| Active
|-
| 00020D00
| JPN
| ?
| v0, v1028
| Active
|-
| 00021D00
| USA
| ?
| v0, v1028
| Active
|-
| 00022D00
| EUR
| ?
| v0, v1028
| Active
|-
| 00020E00
| JPN
| ?
| v0, v1027
| Active
|-
| 00021E00
| USA
| ?
| v0, v1027
| Active
|-
| 00022E00
| EUR
| ?
| v0, v1027
| Active
|-
| 00020F00
| JPN
| ?
| v0, v1024
| Active
|-
| 00021F00
| USA
| ?
| v0, v1024
| Active
|-
| 00022F00
| EUR
| ?
| v0, v1024
| Active
|-
| 00023000
| JPN
| Promotional video
| v0, v2048
| Stubbed
|-
| 00024000
| USA
| Promotional video
| v0, v2048
| Stubbed
|-
| 00025000
| EUR
| Promotional video
| v0, v2048
| Stubbed
|}

== 0004001B ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Description
! Versions
|-
| 00010002
| ?
| v0
|-
| 00010702
| ?
| v0
|}

== 00040020 - Game Trials ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Region
! Description
! Versions
|-
!00048101
!JPN
!Monster Hunter tri G
!v1
|-
|}

== 00040030 ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Region
! Description
! Versions
|-
| 00008202
| JPN
| ?
| v0, v1029, v4111
|-
| 00008402
| JPN
| ?
| v0, v1036
|-
| 00008602
| JPN
| ?
| v0, v1026, v2048
|-
| 00008802
| JPN
| ?
| v6, v1024
|-
| 00008A02
| All
| ?
| v0, v1025, v3072
|-
| 00008D02
| JPN
| ?
| v0, v1026, v3082
|-
| 00008E02
| JPN
| ?
| v0, v1029, v2054
|-
| 00008F02
| USA
| ?
| v0, v1027, v2049, v4111
|-
| 00009202
| USA
| ?
| v0, v1026, v1036
|-
| 00009302
| USA
| ?
| v0, v1026, v2048
|-
| 00009402
| USA
| ?
| v6, v1024
|-
| 00009602
| USA
| ?
| v0, v1026, v3082
|-
| 00009702
| USA
| ?
| v0, v1029, v2054
|-
| 00009802
| EUR
| ?
| v0, v1029, v4111
|-
| 00009902
| EUR
| ?
| v0, v1036
|-
| 00009B02
| EUR
| ?
| v0, v1036, v2048
|-
| 00009D02
| EUR
| ?
| v6, v1024
|-
| 00009F02
| EUR
| ?
| v6, v1024, v3082
|-
| 0000A002
| EUR
| ?
| v6, v1024, v2054
|-
| 0000C002
| JPN
| ?
| v0, v1026, v2053
|-
| 0000C102
| JPN
| ?
| v0, v1026
|-
| 0000C302
| JPN
| ?
| v0, v1024
|-
| 0000C502
| All
| ?
| v0, v1026, v2053
|-
| 0000C602
| JPN
| ?
| v5
|-
| 0000C802
| USA
| ?
| v0, v1026, v2053
|-
| 0000C902
| USA
| ?
| v0, v1026
|-
| 0000CB02
| USA
| ?
| v0, v1024
|-
| 0000CC02
| USA
| ?
| v3
|-
| 0000CD02
| All
| ?
| v1
|-
| 0000CE02
| USA
| ?
| v5
|-
| 0000D002
| EUR
| ?
| v0, v1026, v2053
|-
| 0000D102
| EUR
| ?
| v0, v1026
|-
| 0000D302
| EUR
| ?
| v0, v1024
|-
| 0000D602
| EUR
| ?
| v5
|}

== 0004009B ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Region
! Description
! Versions
|-
| 00010202
| All
| ?
| v0, v2050
|-
| 00010302
| All
| ?
| v0, v2052
|-
| 00010402
| All
| ?
| v0, v1024, v2050
|-
| 00010502
| All
| ?
| v0, v1024, v2048
|-
| 00010602
| All
| ?
| v2
|-
| 00011902
| JPN
| ?
| v0
|-
| 00011402
| USA
| ?
| v0
|-
| 00011202
| EUR
| ?
| v0
|-
| 00012102
| EUR
| ?
| v0, v1026, v2051
|-
| 00012202
| JPN
| ?
| v1026
|-
| 00012302
| USA
| ?
| v1026, v2053
|-
| 00012102
| EUR
| ?
| v1026, v2051
|-
| 00013102
| EUR
| ?
| v1024, v2049
|-
| 00013302
| USA
| ?
| v1024, v2051
|-
| 00016302
| USA
| ?
| v80
|-
| 00017302
| USA
| ?
| v3088
|}

== 000400DB ==

These ids can be found @ offset 0x320 in every CCI... (the region of the title is the region of the CCI).

(Maybe this is the loader title, like IOS on the Wii, and could be the value we need to change to get RegionFree...).

{| class="wikitable" border="1"
|-
! TitleID Low
! Region
! Description
! Versions
|-
| 00010302
| EUR
| ?
| v0, v1024, v2052
|-
| 00010502
| EUR
| ?
| v0, v1024, v2048
|-
| 00016102
| EUR
| ?
| v32, v48, v64, v80, v96
|-
| 00016202
| JPN
| ?
| v32, v48, v64, v80, v96
|-
| 00016302
| USA
| ?
| v32, v48, v64, v80, v96
|-
| 00017102
| EUR
| ?
| v2049, v2069, v3088
|-
| 00017302
| USA
| ?
| v2049, v2069
|}

== 00040130 - FIRMWARE ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Title Name
! Description
! Versions
|-
| 00001502
| FIRMWARE 02_15
|
| v0, v1026, v2053
|-
| 00001503
| FIRMWARE 03_15
|
| v0
|-
| 00001602
| FIRMWARE 02_16
| Camera - System applet
| v0, v1026, v2048
|-
| 00001702
| FIRMWARE 02_17
| Config - System applet
| v0, v1024, v2049
|-
| 00001703
| FIRMWARE 03_17
|
| v0
|-
| 00001802
| FIRMWARE 02_18
| Codec - system applet
| v0, v1025, v3072
|-
| 00001803
| FIRMWARE 03_18
|
| v0
|-
| 00001A02
| FIRMWARE 02_1A
| DSP - system applet.
| v0, v1024
|-
| 00001A03
| FIRMWARE 03_1A
|
| v0
|-
| 00001B02
| FIRMWARE 02_1B
|
| v0
|-
| 00001B03
| FIRMWARE 03_1B
|
| v0
|-
| 00001C02
| FIRMWARE 02_1C
|
| v0, v1040, v2049, v3075
|-
| 00001C03
| FIRMWARE 03_1C
|
| v0
|-
| 00001D02
| FIRMWARE 02_1D
|
| v0, v1025, v3072
|-
| 00001D03
| FIRMWARE 03_1D
|
| v0
|-
| 00001E02
| FIRMWARE 02_1E
| i2c - system applet.
| v0, v1024
|-
| 00001E03
| FIRMWARE 03_1E
|
| v0
|-
| 00001F02
| FIRMWARE 02_1F
|
| v0, v1026, v3072
|-
| 00001F03
| FIRMWARE 03_1F
|
| v0
|-
| 00002002
| FIRMWARE 02_20
| Microphone - system applet
| v0
|-
| 00002102
| FIRMWARE 02_21
|
| v0
|-
| 00002103
| FIRMWARE 03_21
|
| v0
|-
| 00002202
| FIRMWARE 02_22
|
| v0, v1026, v3075
|-
| 00002203
| FIRMWARE 03_22
|
| v0
|-
| 00002302
| FIRMWARE 02_23
| spi - system applet.
| v0, v1025
|-
| 00002303
| FIRMWARE 03_23
|
| v0
|-
| 00002402
| FIRMWARE 02_24
| Network - System Applet
| v0, v1024, v2052, v4101
|-
| 00002403
| FIRMWARE 03_24
|
| v0
|-
| 00002602
| FIRMWARE 02_26
| Messaging (NintendoZone) - System Applet
| v0, v1026, v3073
|-
| 00002702
| FIRMWARE 02_27
|
| v0, v1025
|-
| 00002703
| FIRMWARE 03_27
|
| v0
|-
| 00002802
| FIRMWARE 02_28
| DownloadPlay - System applet
| v0, v1026, v3078
|-
| 00002902
| FIRMWARE 02_29
| http - system applet
| v0, v1026, v4099
|-
| 00002903
| FIRMWARE 03_29
|
| v0
|-
| 00002A02
| FIRMWARE 02_2A
|
| v0
|-
| 00002A03
| FIRMWARE 03_2A
|
| v0
|-
| 00002B02
| FIRMWARE 02_2B
|
| v0, v1025, v2049
|-
| 00002C02
| FIRMWARE 02_2C
|
| v0, v1028, v2055
|-
| 00002C03
| FIRMWARE 03_2C
|
| v0
|-
| 00002D02
| FIRMWARE 02_2D
|
| v0, v1024, v2052, v4101
|-
| 00002D03
| FIRMWARE 03_2D
|
| v0
|-
| 00002E02
| FIRMWARE 02_2E
| Sockets - System applet
| v0, v1024, v2053, v3075

|-
| 00002E03
| FIRMWARE 03_2E
|
| v0
|-
| 00002F02
| FIRMWARE 02_2F
| SSL - System applet.
| v0, v1024, v3072
|-
| 00002F03
| FIRMWARE 03_2F
|
| v0
|-
| 00003102
| FIRMWARE 02_31
|
| v0, v1025
|-
| 00003103
| FIRMWARE 03_31
|
| v0
|-
| 00003202
| FIRMWARE 02_32
| FriendsList - System applet
| v0, v1028, v3072
|-
| 00003203
| FIRMWARE 03_32
|
| v0
|-
| 00003302
| FIRMWARE 02_33
|
| v0, v1026, v3072
|-
| 00003303
| FIRMWARE 03_33
|
| v0
|-
| 00003402
| FIRMWARE 02_34
| BOSS (SpotPass) System Applet
| v0, v1024, v2053, v4101
|-
| 00003502
| FIRMWARE 02_35
|
| v0, v1028, v3072
|-
| 00003702
| FIRMWARE 02_37
|
| v0
|-
| 00008002
| FIRMWARE 02_80
|
| v0, v1028, v3077
|-
| 00008003
| FIRMWARE 03_80
|
| v0
|}

== 00040138 ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Description
! Versions
|-
| 00000002
| [[Home Menu]]
| v432, v1472, v2516, v3553, v5647
|-
| 00000003
| ?
| v432, v5632
|-
| 00000102
| ?
| v432, v1489, 2565
|-
| 00000202
| ?
| v519
|}

== 00048005 ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Description
! Versions
|-
| 42383841(B88A)
| [[DS Internet]]
| v0, v1025, v2048
|-
| 484E4441(HNDA)
| [[Download Play]]
| v1024
|}

== 0004800F ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Description
! Versions
|-
| 484E4841(HNHA)
| [[Nintendo DS Cart Whitelist]]
| v0, v1026, v3072
|-
| 484E4C41(HNLA)
| Matches the DSi titleid low for [[Version Data]] but this title was never updated.(As of [[2.1.0-4]])
| v0
|}

== 00040000 - eShop Titles ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Region
! Description
! Versions
|-
| 00032600
| EUR/USA
| Pokédex 3D
| v0
|-
| 00034700
| ?
| ?
| v0
|-
| 00040800
| ?
| ?
| v16
|-
| 00040900
| ?
| ?
| v16
|-
| 00040A00
| ?
| ?
| v16
|-
| 00040B00
| ?
| ?
| v16
|-
| 00040E00
| ?
| ?
| v0
|-
| 00041000
| ?
| ?
| v0
|-
| 00041100
| ?
| ?
| v0
|-
| 00041300
| ?
| ?
| v0
|-
| 00041500
| ?
| ?
| v0
|-
| 00041800
| ?
| ?
| v0
|-
| 00041900
| EUR
| Kirby's Dream Land
| v0
|-
| 00041D00
| ?
| ?
| v0
|-
| 00041E00
| ?
| ?
| v0
|-
| 00041F00
| ?
| ?
| v0
|-
| 00042400
| ?
| ?
| v0
|-
| 00042600
| ?
| ?
| v0
|-
| 00042700
| ?
| ?
| v0
|-
| 00042800
| EUR
| Zelda: Link's Awakening DX
| v0
|-
| 00042900
| ?
| ?
| v16
|-
| 00042A00
| ?
| ?
| v0
|-
| 00042C00
| ?
| ?
| v0
|-
| 00042E00
| ?
| ?
| v0
|-
| 00043000
| ?
| ?
| v0
|-
| 00045C00
| JPN
| 3D Classics Excitebike
| v0
|-
| 00046C00
| EUR
| 3D Classics Excitebike
| v0
|-
| 00048900
| ?
| ?
| v0
|-
| 00049900
| ?
| ?
| v0
|-
| 00049D00
| ?
| ?
| v0
|-
| 0004A900
| ?
| ?
| v0
|-
| 0004AA00
| USA
| Nintendo Video
| v0
|-
| 0004AB00
| EUR
| Nintendo Video
| v0
|-
| 0004B400
| ?
| ?
| v0
|-
| 0004D500
| ?
| ?
| v0
|-
| 0004E700
| ?
| ?
| v16
|-
| 0004EF00
| ?
| ?
| v0
|-
| 0004F300
| ?
| ?
| v0
|-
| 0004FA00
| ?
| ?
| v0
|-
| 0004FD00
| ?
| ?
| v0
|-
| 00051800
| EUR
| Letter Box
| v0
|-
| 00052600
| ?
| ?
| v32
|-
| 00052700
| ?
| ?
| v16
|-
| 00052800
| ?
| ?
| v0, v1024
|-
| 00052900
| ?
| ?
| v32
|-
| 00052A00
| ?
| ?
| v0
|-
| 00052D00
| ?
| ?
| v16
|-
| 00054300
| USA
| 3D Classics Excitebike
| v0
|-
| 00054E00
| EUR
| 3D Classics Excitebike
| v0, v1024
|-
| 00055800
| ?
| ?
| v16
|-
| 00057700
| USA
| Netflix
| v0
|-
| 00059200
| ?
| ?
| v16
|-
| 0005AD00
| JPN
| Kid Icarus Uprising E3 Video
| v0
|-
| 0005AE00
| USA
| Kid Icarus Uprising E3 Video
| v0
|-
| 0005AF00
| JPN
| Paper Mario E3 Video
| v0
|-
| 0005B000
| USA
| Paper Mario E3 Video
| v0
|-
| 0005B100
| JPN
| Mario Kart E3 Video
| v0
|-
| 0005B200
| USA
| Mario Kart E3 Video
| v0
|-
| 0005B300
| JPN
| Animal Crossing E3 Video
| v0
|-
| 0005B400
| USA
| Animal Crossing E3 Video
| v0
|-
| 0005B500
| JPN
| Luigi's Mansion 2 E3 Video
| v0
|-
| 0005B600
| USA
| Luigi's Mansion 2 E3 Video
| v0
|-
| 0005B700
| JPN
| Zelda Ocarina of Time E3 Video
| v0
|-
| 0005B800
| USA
| Zelda Ocarina of Time E3 Video
| v0
|-
| 0005B900
| JPN
| Super Mario E3 Video
| v0
|-
| 0005BA00
| USA
| Super Mario E3 Video
| v0
|-
| 0005BB00
| JPN
| MGS Snake Eater 3D E3 Video
| v0
|-
| 0005BC00
| USA
| MGS Snake Eater 3D E3 Video
| v32
|-
| 0005BD00
| JPN
| Biohazard Revelations E3 Video
| v16
|-
| 0005BE00
| USA
| Resident Evil Revelations E3 Video
| v32
|-
| 0005BF00
| JPN
| Starfox 64 3D E3 Video
| v0
|-
| 0005C000
| USA
| Starfox 64 3D E3 Video
| v0
|-
| 0005EA00
| EUR
| Green Lantern 3D Trailer Video
| v0
|-
| 0005F000
| USA
| Green Lantern 3D Trailer Video
| v0
|-
| 0005F800
| ?
| ?
| v0
|-
| 0005F900
| ?
| ?
| v0
|-
| 0005FC00
| ?
| ?
| v0
|-
| 0005FD00
| ?
| ?
| v0
|-
| 00060000
| ?
| ?
| v0
|-
| 00062400
| EUR
| Kid Icarus Uprising E3 Video
| v0
|-
| 00062700
| EUR
| Paper Mario E3 Video
| v0
|-
| 00062A00
| EUR
| Mario Kart E3 Video
| v0
|-
| 00062B00
| ?
| ?
| v0
|-
| 00062C00
| ?
| ?
| v0
|-
| 00062D00
| EUR
| Animal Crossing E3 Video
| v0
|-
| 00063000
| EUR
|Luigi's Mansion 2 E3 Video
| v0
|-
| 00063300
| EUR
| Zelda Ocarina of Time E3 Video
| v0
|-
| 00063400
| ?
| ?
| v0
|-
| 00063500
| ?
| ?
| v0
|-
| 00063600
| EUR
| Super Mario E3 Video
| v0
|-
| 00063700
| ?
| ?
| v0
|-
| 00063800
| ?
| ?
| v0
|-
| 00063900
| EUR
| MGS Snake Eater 3D E3 Video
| v0
|-
| 00063C00
| EUR
| Resident Evil Revelations E3 Video
| v0
|-
| 00063D00
| ?
| ?
| v0
|-
| 00063E00
| ?
| ?
| v0
|-
| 00063F00
| EUR
| Starfox 64 3D E3 Video
| v0
|-
| 00064000
| ?
| ?
| v0
|-
| 00064100
| ?
| ?
| v0
|-
| 0006E500
| USA
| Super Mario Bros.
| v0
|-
| 0006E600
| EUR
| Super Mario Bros.
| v0
|-
| 0006EE00
| USA
| Metroid
| v0
|-
| 0006EF00
| EUR
| Metroid
| v0
|-
| 0006F100
| USA
| The Legend of Zelda
| v0
|-
| 0006F200
| EUR
| The Legend of Zelda
| v0
|-
| 0006F700
| USA
| Wrecking Crew
| v0
|-
| 0006F800
| EUR
| Wrecking Crew
| v0
|-
| 0006FA00
| USA
| NES Open Tournament Golf
| v0
|-
| 0006FB00
| EUR
| NES Open Tournament Golf
| v0
|-
| 00070000
| USA
| Donkey Kong Jr.
| v0
|-
| 00070100
| EUR
| Donkey Kong Jr.
| v0
|-
| 00070300
| USA
| Balloon Fight
| v0
|-
| 00070400
| EUR
| Balloon Fight
| v0
|-
| 00070600
| USA
| Ice Climber
| v0
|-
| 00070700
| EUR
| Ice Climber
| v0
|-
| 00070900
| USA
| Zelda II The Adventure of Link
| v0
|-
| 00070A00
| EUR
| Zelda II The Adventure of Link
| v0
|-
| 00071200
| USA
| Yoshi
| v0
|-
| 00071300
| EUR
| Yoshi
| v0
|-
| 00072400
| EUR
| Ambassador Certificate
| v0
|-
| 00072500
| USA
| Ambassador Certificate
| v0
|-
| 00079700
| USA
| Preview Video: ?
| v0
|-
| 00079800
| USA
| Preview Video: ?
| v0
|-
| 00079900
| USA
| Preview Video: ?
| v0
|-
| 00079A00
| USA
| Preview Video: ?
| v0
|-
| 00079B00
| USA
| Preview Video: ?
| v0
|-
| 00079C00
| USA
| Preview Video: Animal Crossing
| v0
|-
| 00079D00
| USA
| Preview Video: ?
| v0
|-
| 0007AB00
| EUR
| Eurosport (looks/acts like Nintendo Video)
| v0
|}

== 00040000 - Retail Titles ==
{| class="wikitable" border="1"
|-
! TitleID Low
! Region
! Description
! Versions
|-
| 00030700
| EUR
| Mario Kart 7
| v0
|-
| 00031D00
| EUR
| PilotWings Resort
| v0
|-
| 00033600
| EUR
| The Legend of Zelda - Ocarina of Time 3D
| v0
|-
| 00033800
| EUR
| Puzzle Bobble Universe
| v0
|-
| 00033900
| EUR
| Rayman 3D
| v0
|-
| 00033A00
| EUR
| Tom Clancy's Splinter Cell 3D
| v0
|-
| 00033B00
| EUR
| Ridge Racer 3D
| v0
|-
| 00033C00
| EUR
| Super Street Fighter IV - 3D Edition
| v0
|-
| 00037500
| EUR
| Tom Clancy's Ghost Recon - Shadow Wars
| v0
|-
| 00038900
| EUR
| Super Monkey Ball 3D
| v0
|-
| 00038A00
| EUR
| Dead or Alive - Dimensions
| v0
|-
| 00038C00
| EUR
| LEGO Star Wars III - The Clone Wars
| v0
|-
| 00038B00
| EUR
| Resident Evil - The Mercenaries 3D
| v0
|-
| 00049100
| EUR
| StarFox 64 3D
| v0
|-
| 00053F00
| EUR
| Super Mario 3D Land
| v0
|-
| 00056200
| EUR
| Doctor Lautrec and The Forgotten Knights
| v0
|}

Talk:Crappy Tiny Reader

2011-12-10T19:00:17Z

Lazymarek9614:

Clever name :). --[[User:Elisherer|Elisherer]] 17:35, 10 December 2011 (CET)
:lol, this programm really is very tiny!--[[User:Lazymarek9614|Lazymarek9614]] 20:59, 10 December 2011 (CET)

Talk:Crappy Tiny Reader

2011-12-10T18:59:57Z

Lazymarek9614:

Clever name :). --[[User:Elisherer|Elisherer]] 17:35, 10 December 2011 (CET)
lol, this programm really is very tiny!--[[User:Lazymarek9614|Lazymarek9614]] 20:59, 10 December 2011 (CET)

User talk:Xcution

2011-11-27T16:57:40Z

Lazymarek9614:

Hi.

Today I bring news of 2 developer applications which I did not see in "3DS Development Unit Software" :

CecLotCheckTool and WM Test

[[File:Ceclotchecktool.jpg|500px|thumb|right|CECLotCheckTool]]

[[File:Devmen2app.jpg|500px|thumb|right|Picture of WM Test (In DevMen)]]

CecLotCheckTool and WM Test tools do not appear to have an icon.

'''Info CecLotCheckTool :'''

First, you may wonder what "CEC" stands for. It means Chance Encounter Communication, AKA StreetPass. It is noted by lib that StreetPass is not possible between a dev unit and a retail system. CECLotCheckTool is used to check StreetPass info. Unfortunately, I only have 1 dev unit =p so I can't really do a whole lot with this, since it's only developer unit -> developer unit. I still think it's interesting though..

'''Info WM Test :'''

Unfortunately I do not have pictures of WM Test as it seems to freeze on my somewhat outdated rev although lib/sdk states it is a TWL program BUT lib states WM Test has 2 unique features :

It runs through DevMen in "TWL Compatibility" mode AND runs in "Noise mode"

And another unfortunate point to bring is I could not find so far information about these 2 modes, which is sort of a let down =/ but interesting that it notes those two things.

Are you Collosalpokemon from GBA Temp, because they look like his(or her) photos--[[User:3dsguy|3dsguy]] 02:54, 27 November 2011 (CET)

Also if you want to test streetpass between dev 3DSs, your best chance of doing this is at a nintendo public event where they are likly to have 3DS demos running on Dev 3DSs.--[[User:3dsguy|3dsguy]] 02:59, 27 November 2011 (CET)

Yes, that's why my pictures are the same. I thought I'd show some stuff that 3DBrew doesn't documented yet. Also I would avoid bringing this to a public event as this is my only copy of the developer 3ds, and if I was caught by a nintendo employee that wouldn't be great :p I came across an interesting format while digging through the lib, it wasn't even mentioned in nintendo's documentation lol so I'm still learning what it does exactly. I'll add my findings to the file format list here, just know it wasn't much yet--[[User:Xcution|Xcution]] 03:50 27 November 2011

Well thanks for the info on CECLotcheckTool, you gave me enough to get me started on working out on what it does, you should see my findings on my 3DS Development Unit Software page soon. Also WM Test is a wireless test app, more info should also appear on my page soon.--[[User:3dsguy|3dsguy]]

Ah, right. WM Test was for wireless according to lib. Also I updated the format list with 3 formats noted in the compiler, but hidden from documentation. I also found 1 more format which I did not list yet, called OLS. It seems to be something similar to a CIA but I remember seeing it somewhere documented in the lib so I'm checking it out. Also, I've figured out the format of RSF so maybe I'll add that to 3DBrew documentations soon.--[[User:Xcution|Xcution]]

[[User:Xcution|Xcution]], can you upload any files with an undocumented format (mentioned in [[File Formats]]) that we can document them successfuly? Maybe we are also able to find out their purpose.--[[User:Lazymarek9614|Lazymarek9614]] 11:29, 27 November 2011 (CET)

[[User:Lazymarek9614|Lazymarek9614]] unfortunately not all of them. The best I could get you guys would be CFA, NSA, RSF, AXF, BCWAV, and DESC files but not the few I've found in the lib. btw RSF and DESC are both in plain text. I could also make you guys some custom CXI's to see but I'm not sure how useful they would be to anyone. Lib references Common Header Keys also. I have successfully generated my own CXI file (Hello World), can I upload it here? It had to be made with a nintendo linker but I made the file so does it count as "copyrighted" by nintendo? they didn't approve of this work so I don't think so but I'd rather be safe than sorry.--[[User:Xcution|Xcution]]

I'm not sure about the copyright... Can you upload the other formats first (if you are allowed to) and wait until you're sure about the copyright stuff. Are the common header keys for 3ds test units only or for the public normal 3ds? I think not all formats are useful for us, but the CXI is.--[[User:Lazymarek9614|Lazymarek9614]] 12:06, 27 November 2011 (CET)

Ah. I'll see about those. The Common Header Keys are likely for both retail and dev 3ds because lib allows building for both retail and dev files using the same keys, however I don't know if they are dummy keys like the RSA are. I'll try to get the format BCWAV (3DS Audio Wave files) soon.--[[User:Xcution|Xcution]]

OK, so please look for the keys you can get & publish legal and upload some files.--[[User:Lazymarek9614|Lazymarek9614]] 16:18, 27 November 2011 (CET)
:I wouldn't recommend uploading anything to 3dbrew because it *might* be illegal. I recommend using the PM in gbatemp to ask. There are only few people here that would benefit from looking at these files (and by saying 'these' i don't mean any specific files). --[[User:Elisherer|Elisherer]] 17:03, 27 November 2011 (CET)
::Yes, it has to be legal! [[User:Xcution|Xcution]], maybe if you want to send me 'these' files, click on my username to see the e-mail contact and don't upload anything illegal on 3dbrew.--[[User:Lazymarek9614|Lazymarek9614]] 18:57, 27 November 2011 (CET)

User talk:Xcution

2011-11-27T14:18:41Z

Lazymarek9614:

User talk:Xcution

2011-11-27T10:06:25Z

Lazymarek9614:

User talk:Xcution

2011-11-27T09:29:44Z

Lazymarek9614: upload the unknown formats please!

User:Matyapiro31

2011-11-24T15:48:47Z

Lazymarek9614:

I'm Japanese.
Sorry,I cannot write smart English.
But I bring information written in japanese!
I bought a new one.
:A new 3DS for dumping stuff I guess...?--[[User:Lazymarek9614|Lazymarek9614]] 14:36, 23 November 2011 (CET)

Yes,of cource.
But before dump ram,i will be able to find more info about RAM!
:I also wanted to do a RAM dump, but the pinout on the board is unknown... Why have you bought a new 3DS when you don't know how to do a dump?--[[User:Lazymarek9614|Lazymarek9614]] 17:48, 24 November 2011 (CET)

User:Matyapiro31

2011-11-23T12:36:10Z

Lazymarek9614:

Talk:3DSExplorer

2011-11-22T15:24:58Z

Lazymarek9614:

Now I figured that I didn't explain the target of this app... It's suppose to be an Explorer like program to see inside the different filesystems that the 3ds has. Now it's the ExeFS, RomFS and SAVE. As knownledge keep flowing i'll continue to develop the application. With the goal of making a full functional drag&drop file explorer for image files. --[[User:Elisherer|Elisherer]] 18:35, 15 September 2011 (CEST)

It fails showing the tmd file content. Have you finshed working on this feature?--[[User:Lazymarek9614|Lazymarek9614]] 15:49, 20 September 2011 (CEST)
:No, I don't have time to work on it..it's not interesting enough --[[User:Elisherer|Elisherer]] 15:36, 21 September 2011 (CEST)
::Yeah, the 3DS doesn't care when the tmd file was modified... it's not useful for hacking.--[[User:Lazymarek9614|Lazymarek9614]] 21:09, 21 September 2011 (CEST)

I downloaded the sources,but I can't find Save.cs and reference "System.Development". Matyapiro31
:You are right... I fixed it.. notice that the source is not the released version it has some experimental stuff in it... --[[User:Elisherer|Elisherer]] 10:53, 30 September 2011 (CEST)

Do you know [http://monodevelop.com/ Mono Develop]?
You can release it as multi-patform,such as Linux,Machitosh,etc.
:I did not know that until now. But I don't have time to make the transition. I'm happy with VS2008 and it's relatively easy to make changes and new features for the app. The source is open and you can make a linux port if you want. --[[User:Elisherer|Elisherer]] 18:16, 30 September 2011 (CEST)
:You need no change.mono can run c# program like Java VM. Matyapiro31
::I tried to compile it,but That was old one,and there is "System.development."
:::[http://stackoverflow.com/questions/5865060/c-on-os-x-and-linux This] says that I need to fix stuff after I convert my project. and then work with the mono app which I don't find very convinient... and about the reference I don't know what it's about..I don't know a namespace called System.Development --[[User:Elisherer|Elisherer]] 17:42, 2 October 2011 (CEST) (P.s you can sign your messages with the quick signature button or 4 tildes: '~' 4 times)

lblBrew_Click() had no exception handler,

you have to change this method in fmExplorer.cs to
private void lblBrew_Click(object sender, EventArgs e)
{
try
{
System.Diagnostics.Process.Start(lblBrew.Text);
}
catch (Exception ex)
{
MessageBox.Show("Cannot open link that was clicled.\n"+ ex.Message);
}
}

Matyapiro31

The algorithm for the Image Hash might be either MD2 or MD4. I found out by using HxD and Notepad. --[[User:Kiddyshaq34|Kiddyshaq34]]
:Ok, but of what? (i know it's suppose to be 128 bit) And why not MD-5? --[[User:Elisherer|Elisherer]] 07:10, 9 October 2011 (CEST)
::Because MD5 is longer and the Image Hash has the same number of bytes as MD2 and MD4.
:::MD2, 4 & 5 are all 128bit which is 0x10 bytes... --[[User:Elisherer|Elisherer]] 20:28, 9 October 2011 (CEST)
::::Oh, I've forgotten about MD5. You are right.

3DS include RSA Securuty 's [http://www.rsa.com/node.aspx?id=1204 BSafe]

from 3DS manual. Matyapiro31
:Thanks Matyapiro31 but I think RSA is used for encryption and *not* hashing. So the RSA might be used for ROMs and WiFi... --[[User:Elisherer|Elisherer]] 14:48, 9 October 2011 (CEST)

あほ。RSA BSafe support all security method.See [http://www.rsa.com/japan/products/bsafe/CRYPTOCJ_DS_1101-J.pdf this.]

I cannot find English version,sorry.
Matyapiro31
:I guess if you mean [http://www.rsa.com/node.aspx?id=3063 this] then the digest algorithms are the ones that we know of..we havn't tried HMAC yet or CNG but from experience we see that nintendo uses regular digest algorithms like CRC16-Modbus and SHA-256. I'll add the HMAC ones to the brute force hash tool to see if it finds something... --[[User:Elisherer|Elisherer]] 22:36, 12 October 2011 (CEST)

I've tried to decrypt 'Super Mario 3D Land' but your tool shows me an 'Corrupt Save File' error.--[[User:Lazymarek9614|Lazymarek9614]] 18:36, 18 November 2011 (CET)
:Corrupted save file might be from 2 reasons: * Size is not right (128K or 512k) * CRC on wearleveling wrong. Both problems occur from NDS adapter plus malfunctioning...try blowing on the cart and the adapter and download the savefile again... --[[User:Elisherer|Elisherer]] 20:16, 18 November 2011 (CET)
::I actually don't use the useless NDS Adapter Plus, but I used DSM and I've tried it two times (always the same data).. I hope Nintendo doesn't use a new encryption now! Shall I send you the sav file?--[[User:Lazymarek9614|Lazymarek9614]] 20:27, 18 November 2011 (CET)
:::Yes please, I could check it within the application... --[[User:Elisherer|Elisherer]] 20:35, 18 November 2011 (CET)
::::Have you found anything?--[[User:Lazymarek9614|Lazymarek9614]] 21:25, 18 November 2011 (CET)
:::::No..it's seems that the key found isn't the right key (even that it appears 4 times in the file). we need to figure out how to decrypt the save files without searching blindly for the key. --[[User:Elisherer|Elisherer]] 21:33, 18 November 2011 (CET)
:::::I got an idea. Xor the image's 0x100-0x103 with every (0x200 block)'s 0x100-0x103 to see if it produces 'DISA' ..it should work with the already known files and might be faster to find. i'll try it tomorrow.. --[[User:Elisherer|Elisherer]] 21:40, 18 November 2011 (CET)
::::::Mind linking to a SM3DL save here so I could look at it?(Btw, you're not looking for a "key", you're looking for an AES-CTR xorpad.) --[[User:Yellows8|Yellows8]] 06:03, 22 November 2011 (CET)
:::::::I'll ask for permission. In the meanwhile, can we talk about it at n-dev.net? I made a [http://n-dev.net/showthread.php?tid=4 thread] there. --[[User:Elisherer|Elisherer]] 16:26, 22 November 2011 (CET)
::::::::Yes, you can share them!--[[User:Lazymarek9614|Lazymarek9614]] 17:24, 22 November 2011 (CET)

The Legend of Zelda: Ocarina of Time 3D

2011-11-22T15:23:29Z

Lazymarek9614:

You can edit about Zelda OoT 3D,put download '''links''' below.

You should read about [[Savegames#Filesystem|FST:3DS filesystem table]] before editing.

You may refer to [[CXI]]
My zelda was crashed when I fight with Ganon!

Sorry, did I get this right: your game was crashed and now you want a suitable savegame?--[[User:Lazymarek9614|Lazymarek9614]] 17:23, 22 November 2011 (CET)

Talk:Main Page

2011-11-20T15:43:02Z

Lazymarek9614:

So how about a [http://wiisixtyfour.webs.com/images/3dsbrew-bg4545.png logo]? --[[User:Bg4545|wiisixtyfour]] 06:59, 1 April 2011 (CEST)

Great one, let's put it as default logo ! --[[User:GeekShadow|GeekShadow]] 09:37, 1 April 2011 (CEST)

Here's one I made, which doesn't use any official artwork/photography: [http://dl.dropbox.com/u/1077900/Graphics/3dbrew.png PNG] [http://dl.dropbox.com/u/1077900/Graphics/3dbrew.svg SVG] --[[User:BHSPitMonkey|BHSPitMonkey]] 05:36, 7 April 2011 (CEST)

How about making the default skin [http://3dbrew.org/w/index.php?title=Main_Page&useskin=monobook MonoBook]?, I like the it better. --[[User:Elisherer|Elisherer]] 10:58, 6 October 2011 (CEST)

I want to dump RAM.What can I do now?How can I learn? --[[User:Matyapiro31|Matyapiro31]] 16:30, 20 November 2011 (CET)
:Sorry, this is not the correct page to talk about that. However, it's a good topic for our new forum! http://n-dev.net/index.php --[[User:Lazymarek9614|Lazymarek9614]] 17:43, 20 November 2011 (CET)

User talk:Jl12

2011-11-20T12:56:59Z

Lazymarek9614:

How do you think 3DS can hack or not?

I think it difficult now.

What and when do you think allows us to enjoy homebrew?[[User talk:Matyapiro31|Matyapiro]]

* We've only recently started documenting the 3DS.
* It's easier for those with debugging hardware to contribute findings but that will change eventually.

Hi Jl12, Can you tell us where did you get the decrypted extended header or how, or atleast give a copy of it...thanks. If you could send me it would be great.

(eli (dot) sherer (at) gmail (dot) com) --[[User:Elisherer|Elisherer]] 10:42, 8 September 2011 (CEST)

Has he answered already? (I'm interested in that too)--[[User:Lazymarek9614|Lazymarek9614]] 18:03, 14 September 2011 (CEST)

Hi Jl12, 3DS guy here with answers to your questions. No its not a kiosk unit its a test unit. Kiosk units are retail units with auto-booting demo games

*Q:Do you have a retail 3DS unit? I'm curious if your test unit will communicate with a retail 3DS unit. ( downloadplay, street-pass, etc. )
A:Yes I also have a retail 3DS unit and the two units do not communicate through streetpass, download play (tried with Steel Diver) or when trying to transfer Miis. I can't even exchange friend codes. As a note it communicates fine with a retail Wii and retail ds (or retail 3ds in ds mode)

*Q:Does it connect to (production) nusd update servers for any updates?
A:It tries to connect to retail update servers (found this out by using a proxy server) but it errors out.

*Q:Do you have any other software or hardware with it? ( firmware updates? rewritable CTR cards? etc. )
A:No i do not have any extra hardware or software except for a CTR card which has a game demo on it (made for test units and dev units and will not work on retail units)(I could take a picture if of it you like), though I am not sure if you can write to it as it is the same size as a retail cart not chunky like in some photos floating around. If I had the hardware to dump it, I would as I am assuming it has unsigned code on it(could be useful for analysis), as it has to be run from the dev menu.

*Q:Can you get more of them however/wherever you received yours from?
A:Not likely, it was hard to obtain. It is possible though.

*Q:Would you be willing to run pre-compiled apps imported through your dev menu on your test unit? [and if so do you have an email to send them to]
A:Yes I would love to (with in reason), they have to be in the .CIA format to be installed from the SD card. If you do make any, send the email with a description of what the application is suppose to do and any instructions. And if you want I can send screenshots and feedback I make about the applications you or others may send. You can send them to "devguy@hotmail.com.au". BTW message me at my talk page so I know to check for an email.

*Q:Would you be willing to lend or rent your unit out? I'm pretty sure you won't but it wouldn't hurt to ask.
A:No I don't really want to lend it out.

All the best--[[User:3dsguy|3dsguy]] 18:19, 27 October 2011 (CEST)

:I have already got an email to test 3 apps, just so you know. One DSi app and two 3DS apps. Keep them coming, I want to put my special 3ds to use. I'll probably make a page for this if I get enough apps to test. BTW I will not post any details or host any apps you send to me without your permission, it is your work after all. Except for the number of apps I test, so people know that I'm contributing to the scene.--[[User:3dsguy|3dsguy]] 13:12, 1 November 2011 (CET)

Jl12, can you create any files or do you have access to any file formats we haven't discovered yet?--[[User:Lazymarek9614|Lazymarek9614]] 14:56, 20 November 2011 (CET)

CXI

2011-11-20T12:54:32Z

Lazymarek9614: /* NCCH Header */

The following text tries to document the structure of the CTR Executable Image (CXI) format.

=== Overview ===
A CXI file contains the 'application' program code, which runs on a single ARM11 core. It can communicate through SVC calls with the other ARM11 core running the 'system' program code. For reasons of clarity, the ARM11 cores will sometimes be called the 'appcore' and 'syscore' respectively.

The CXI file format contains application ARM11 code, the menu icon, the menu 3D model, and an embedded read-only (ROM) filesystem for external filestorage. In fact, the application ARM11 code, menu icon, and menu 3D model are embedded into its own filesystem too, called the ExeFS.

More specifically, the CXI file format is structured in the following order:
* first an NCCH header,
* followed by an extended header,
* followed by a plain binary region,
* followed by an embedded executable filesystem (ExeFS),
* and finally followed by a read-only filesystem (RomFS).

The extended header contains additional information regarding access control.
The plain binary region is an area specifically stored in plaintext, mostly containing SDK library strings for identification.

The extended header, the ExeFS and the RomFS are encrypted using 128-bit AES CTR.

By default encrypted regions are compressed with an LZ77 variant, then encrypted. The spec allows for both unencrypted and uncompressed regions to exist. System titles expect a fixed system key.

=== NCCH Header ===
{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x000
| 0x100
| RSA-2048 signature of the NCCH header, using SHA-256.
|-
| 0x100
| 4
| Magic ID, always 'NCCH'
|-
| 0x104
| 4
| Content size, in media units (1 media unit = 0x200 bytes)
|-
| 0x108
| 8
| Partition ID
|-
| 0x110
| 2
| Maker code
|-
| 0x112
| 2
| Version
|-
| 0x114
| 4
| Reserved
|-
| 0x118
| 8
| Program ID
|-
| 0x120
| 1
| Temp flag
|-
| 0x121
| 0x2F
| Reserved
|-
| 0x150
| 0x10
| Product code
|-
| 0x160
| 0x20
| Extended header hash
|-
| 0x180
| 4
| Extended header size
|-
| 0x184
| 4
| Reserved
|-
| 0x188
| 8
| Flags: byte[5]-byte[7] indicate content type ( system update, application, manual, ... ) size of media unit ( 512*2^byte[6] ) and encryption.
|-
| 0x190
| 4
| Plain region offset, in media units
|-
| 0x194
| 4
| Plain region size, in media units
|-
| 0x198
| 8
| Reserved
|-
| 0x1A0
| 4
| ExeFS offset, in media units
|-
| 0x1A4
| 4
| ExeFS size, in media units
|-
| 0x1A8
| 4
| ExeFS hash region size, in media units
|-
| 0x1AC
| 4
| Reserved
|-
| 0x1B0
| 4
| RomFS offset, in media units
|-
| 0x1B4
| 4
| RomFS size, in media units
|-
| 0x1B8
| 4
| RomFS hash region size, in media units
|-
| 0x1BC
| 4
| Reserved
|-
| 0x1C0
| 0x20
| ExeFS superblock hash
|-
| 0x1E0
| 0x20
| RomFS superblock hash
|}

==== NCCH header example for Lego Starwars III ====
Signature: 720FF8F83F2A1E998322A026D1434165
ED19642ABC1CB2722135AA202BEAD60A
80BCD21C768C597B8268FEF2C64EA710
4C9BA5E12CFFBD1D0C619F4EF7B42CA7
DD8482CB4EB26720AD66CDA57ABCBCFB
D63268A6E2896A59B3B744E39E45B88A
ABB4C0980ACC6210818DCE6DAC838A10
95D0F66B352474D4B3DA4B333F49912D
29AF7EA58BC8C890B18C70B7D540A9FB
EBE24A5312055617D3353B28C3EB1D17
61021BEFF6AD22C384835B40BD44DFAD
981F6350F9458B17BCB5F768C92ABC93
2BCE9888855A8998F4CDE40C9543514A
C57B84EB75A680E7C742632614620D1D
A253284DF3DC01091EB3800C36FD62EE
BA15340F1FD498FAB67C0302E9CDA397
Magic: NCCH
Content size: 0x1cfef400
Partition id: 0004000000038c00
Maker code: 3436 ("46")
Version: 0002
Program id: 0004000000038c00
Temp flag: 00
Product code: CTR-P-ALGP
Extended header hash: 0C27E3C1DE7B2AE2D3114F32A4EEBF46
9AFD0CF352C11D4984C2A9F1D2144C63
Extended header size: 00000400
Flags: 0000030100000000
Plain region offset: 0x00004a00
Plain region size: 0x00000200
ExeFS offset: 0x00004c00
ExeFS size: 0x00143800
ExeFS hash region size: 0x00000200
RomFS offset: 0x00148400
RomFS size: 0x1ceab000
RomFS hash region size: 0x00000200
ExeFS Superblock Hash: 130C042615F647C4C63225EA9E67F8A2
7B15246B88FBC7A927257B84977B787B
RomFS Superblock Hash: A65BEE1060BB6A6821BBCEC600035B7E
64FB6EACA7F0960CFB1F5A37087728F7
Note: Offsets and sizes in media units have been converted to byte sizes.

==== Plain region example for Lego Starwars III ====
0004a00: 5b 53 44 4b 2b 4e 49 4e 54 45 4e 44 4f 3a 43 54 [SDK+NINTENDO:CT [SDK+NINTENDO:CTR_SDK-0_14_23_200_none]
0004a10: 52 5f 53 44 4b 2d 30 5f 31 34 5f 32 33 5f 32 30 R_SDK-0_14_23_20
0004a20: 30 5f 6e 6f 6e 65 5d 00 5b 53 44 4b 2b 4e 49 4e 0_none].[SDK+NIN [SDK+NINTENDO:Firmware-02_27]
0004a30: 54 45 4e 44 4f 3a 46 69 72 6d 77 61 72 65 2d 30 TENDO:Firmware-0
0004a40: 32 5f 32 37 5d 00 5b 53 44 4b 2b 4d 6f 62 69 63 2_27].[SDK+Mobic [SDK+Mobiclip:Deblocker_1_0_2]
0004a50: 6c 69 70 3a 44 65 62 6c 6f 63 6b 65 72 5f 31 5f lip:Deblocker_1_
0004a60: 30 5f 32 5d 00 5b 53 44 4b 2b 4d 6f 62 69 63 6c 0_2].[SDK+Mobicl [SDK+Mobiclip:ImaAdpcmDec_1_0_0]
0004a70: 69 70 3a 49 6d 61 41 64 70 63 6d 44 65 63 5f 31 ip:ImaAdpcmDec_1
0004a80: 5f 30 5f 30 5d 00 5b 53 44 4b 2b 4d 6f 62 69 63 _0_0].[SDK+Mobic [SDK+Mobiclip:MobiclipDec_1_0_1]
0004a90: 6c 69 70 3a 4d 6f 62 69 63 6c 69 70 44 65 63 5f lip:MobiclipDec_
0004aa0: 31 5f 30 5f 31 5d 00 5b 53 44 4b 2b 4d 6f 62 69 1_0_1].[SDK+Mobi [SDK+Mobiclip:MoflexDemuxer_1_0_2]
0004ab0: 63 6c 69 70 3a 4d 6f 66 6c 65 78 44 65 6d 75 78 clip:MoflexDemux
0004ac0: 65 72 5f 31 5f 30 5f 32 5d 00 00 00 00 00 00 00 er_1_0_2].......
0004ad0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0004ae0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

A tool for parsing this format is available [http://github.com/3dshax/ctr/tree/master/ctrtool here]

==== Example dependency list from the extended header ====
00850 41 50 54 3A 55 00 00 00 24 68 69 6F 46 49 4F 00 APT:U...$hioFIO.
00860 24 68 6F 73 74 69 6F 30 24 68 6F 73 74 69 6F 31 $hostio0$hostio1
00870 61 63 3A 75 00 00 00 00 62 6F 73 73 3A 55 00 00 ac:u....boss:U..
00880 63 61 6D 3A 75 00 00 00 63 65 63 64 3A 75 00 00 cam:u...cecd:u..
00890 63 66 67 3A 75 00 00 00 64 6C 70 3A 46 4B 43 4C cfg:u...dlp:FKCL
008A0 64 6C 70 3A 53 52 56 52 64 73 70 3A 3A 44 53 50 dlp:SRVRdsp::DSP
008B0 66 72 64 3A 75 00 00 00 66 73 3A 55 53 45 52 00 frd:u...fs:USER.
008C0 67 73 70 3A 3A 47 70 75 68 69 64 3A 55 53 45 52 gsp::Gpuhid:USER
008D0 68 74 74 70 3A 43 00 00 6D 69 63 3A 75 00 00 00 http:C..mic:u...
008E0 6E 64 6D 3A 75 00 00 00 6E 65 77 73 3A 75 00 00 ndm:u...<nowiki>news:u..</nowiki>
008F0 6E 77 6D 3A 3A 55 44 53 70 74 6D 3A 75 00 00 00 nwm::UDSptm:u...
00900 70 78 69 3A 64 65 76 00 73 6F 63 3A 55 00 00 00 pxi:dev.soc:U...
00910 73 73 6C 3A 43 00 00 00 79 32 72 3A 75 00 00 00 ssl:C...y2r:u...
00920 69 72 3A 55 53 45 52 00 6C 64 72 3A 72 6F 00 00 ir:USER.ldr:ro..
00930 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00940 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00950 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00960 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
... ...
009D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
009E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
009F0 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 02 . .............
00A00 5B 53 44 4B 2B 4E 49 4E 54 45 4E 44 4F 3A 43 54 [SDK+NINTENDO:CT

CCI

2011-11-20T12:53:47Z

Lazymarek9614: /* NCSD header */ flag for manual

This document is about the format of CTR cart images (CCI), which is also the format of 3DS ROM dumps.

=== Overview ===
CCI files start with a NCSD header, followed by up to a maximum of 8 NCCH blocks according to spec. The first block usually starts at 0x4000. In most carts the first block contains game code/data, the second block contains the download play "child" and the third block contains potential system updates. The exact contents of NCCH blocks can be determined by looking at the flags.

The NCCH blocks are in the same format as [[CXI]] files.

=== NCSD header ===
{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x000
| 0x100
| RSA-2048 signature of the NCSD header, using SHA-256 (needs to be confirmed)
|-
| 0x100
| 4
| Magic ID, always 'NCSD'
|-
| 0x104
| 4
| Size of the CCI image, in media units (1 media unit = 0x200 bytes)
|-
| 0x108
| 8
| Title/Program ID
|-
| 0x120
| 4
| Offset to the first NCCH in media units
|-
| 0x124
| 4
| Size of the first NCCH
|-
| 0x130
| 4
| Offset to the second NCCH
|-
| 0x134
| 4
| Size of the second NCCH
|-
| 0x158
| 4
| Offset to the third NCCH
|-
| 0x15C
| 4
| Size of the third NCCH
|-
| 0x188
| 8
| NCCH Flags: byte[5]-byte[7] indicate content type ( system update, application, manual, ... ) size of media units ( 512*2^byte[6] ) and encryption.
|-
| 0x190
| 8
| Partition ID of the first NCCH
|-
| 0x1A0
| 8
| Partition ID of the second NCCH
|-
| 0x1C8
| 8
| Partition ID of the third NCCH
|-
| 0x200
| 4
| Always 0xFFFFFFFF
|-
| 0x300
| 4
| Used ROM size in bytes
|-
| 0x320
| 16
| Unknown
|}

Parts of the first NCCH block's header are found around 0x1000 for whatever reason.

CCI images may not include all three NCCH blocks. For example, Ghost Recon: Shadow Wars lacks the second NCCH. Entries at 0x130, 0x134 and 0x1A0 in its NCSD header are zero.

Talk:3DSExplorer

2011-11-18T19:25:46Z

Lazymarek9614:

Talk:3DSExplorer

2011-11-18T18:27:47Z

Lazymarek9614:

Talk:3DSExplorer

2011-11-18T16:36:22Z

Lazymarek9614: decrypting doesn't work!

Games

2011-11-18T16:26:34Z

Lazymarek9614: added SM3L

This is a page to browse game title and data.
Feel free to write here.

If you want to know about games,go [http://www.nintendolife.com/ here.]

The other way to use this page, is hacking with the data.
{| class="wikitable" border="1"
|-
! width="32%" | Title
! width="23%" | Serial*
! width="5%" | EUR
! width="5%" |USA
! width="5%" |JPN
! width="5%" |ROM Size
! width="5%" |FLASH Size
! width="5%" |FLASH ID
! width="5%" |FLASH Chip #
! width="10%" | Get here
|-
| Asphalt 3D
| LNA-CTR-ASFE
| Yes
| Yes
| Yes
| ?
| 128kByte
| ?
| ?
| ?
|-
| Cubic Ninja
| LNA-CTR-AQNE
| Yes
| Yes
| Yes
| ?
| 128kByte
| ?
| ?
| ?
|-
| Dead or Alive - Dimensions
| LNA-CTR-ADDP
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Lego Star Wars III: The Clone Wars
| LNA-CTR-ALGP
| Yes
| Yes
| No
| 4GBit
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Nintendogs+Cats: French Bulldog & New Friends
| LNA-CTR-ADBP
| Yes
| Yes
| Yes
| ?
| 512kByte
| 0xC22213
| 25L4001
| ?
|-
| Nintendogs+Cats (kiosk demo)
| LNZ-CTR-ADAP
| Yes
| ?
| ?
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| One Piece: Unlimited Cruise SP
| LNA-CTR-ALFJ
| No
| No
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Pilotwings Resort
| LNA-CTR-AWAP
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Puzzle Bobble Universe
| LNA-CTR-ABBP
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| [[Raving Rabbids: Travel in Time 3D]]
| LNA-CTR-ARBJ
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| [http://dl.dropbox.com/u/7830918/3DS%20Upload/decrypted.bin de]/[http://dl.dropbox.com/u/7830918/3DS%20Upload/encrypted.bin en]
|-
| Ridge Racer 3D
| LNA-CTR-ARRP
| Yes
| Yes
| Yes
| 8GBit
| 512kByte
| 0xC22213
| 25L4001
| ?
|-
| Samurai Warriors - Chronicles
| LNA-CTR-A66P
| Yes
| Yes
| Yes
| ?
| 512kByte
| 0xC22213
| 25L4001
| ?
|-
| Splinter Cell 3D
| LNA-CTR-ASCP
| Yes
| Yes
| Yes
| 16Gbit
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Steel Diver
| LNA-CTR-ASDP
| Yes
| Yes
| Yes
| ?
| 512kByte
| 0xC22213
| 25L4001
| [http://dl.dropbox.com/u/32759832/3DS_saves/Steel_Diver/decrypted.sav de]/[http://dl.dropbox.com/u/32759832/3DS_saves/Steel_Diver/encrypted.sav en]
|-
| Super Street Fighter IV - 3D Edition
| LNA-CTR-ASSP
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Super Monkey Ball 3D NTSC
| LNA-CTR-ASME
| Yes
| Yes
| Yes
| 2GBit
| 128kByte
| ?
| ?
| ?
|-
| Super Monkey Ball 3D PAL
| LNA-CTR-ASMP
| Yes
| Yes
| Yes
| 2GBit
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| [[The Legend of Zelda: Ocarina of Time 3D]]
| LNA-CTR-AQEP
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| [http://dl.dropbox.com/u/32759832/3DS_saves/Zelda_OoT/decrypted.sav de]/[http://dl.dropbox.com/u/32759832/3DS_saves/Zelda_OoT/encrypted.sav en]
|-
| The Sims 3
| LNA-CTR-AS3P
| Yes
| Yes
| Yes
| 4GBit
| 512kByte
| 0xC22213
| 25L4001
| ?
|-
| Tom Clancy's Ghost Recon: Shadow Wars
| LNA-CTR-AGRP
| Yes
| Yes
| Yes
| 2GBit
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Super Mario 3D Land
| LNA-CTR-AREP
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
|}

Elisherer's Savefile collection: [http://sherer.co.il/saves http://sherer.co.il/saves]
== Serial structure ==

LN - Product type (Cartridges are LN, Game boxes are TS, Instruction manuals are MA, leaflets are FA, Quick-Start guides are MK)

A/Z - Retail / Demo

CTR - 3DS' Codename (Still unknown, similar to NDS's codename NTR=Nitro)

A/C/H - Unknown / (C used in update executables usually CTAP. Open a 3ds Rom with 3dsexplorer to see) / (H is used in some developer applications).

XX - Game's name (made from letters and digits)

E/P/J - English (US) / Pal (Europe/Australia) / Japanese (Japan)

== Product Code ==

This is similar to the serial structure, but this is how the 3DS internally identifies 3DS Applications. And follows this structure:

CTR - 3DS' Codename (Still unknown, similar to NDS's codename NTR=Nitro)

P/N - P Generally used for games (note: for retail and dev games this is the same) / N Generally used for developer applications

A/C/H - Unknown / (C used in update executables usually CTAP. Open a 3ds Rom with 3dsexplorer to see) / (H is used in some developer applications).

XX - Game's name (made from letters and digits)

E/P/J - English (US) / Pal (Europe/Australia) / Japanese (Japan)

So for example a Japanese copy of Ridge Racer 3D would have a Product Code of "CTR-P-ARRJ" and a Serial of "LNA-CTR-ARRJ"

CIA

2011-11-17T14:03:05Z

Lazymarek9614: /* Icons */

=== Overview ===
CIA stands for '''C'''TR '''I'''mportable '''A'''rchive. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NAND used by DSi applications) and on the SD card.

=== Format ===
The CIA format has a similar structure to the [http://wiibrew.org/wiki/Wad WAD format].

The file is represented in little-endian.

The data is aligned in 64 byte blocks (if a content ends at the middle of the block, the next content will begin from a new block).

== CIA Header ==

This is a 32 bytes long header (8 x uint32).

{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Archive Header Size (=0x2020 bytes) (Starts with 0x80 @ offset 0x0020)
|-
| 0x04
| 0x02
| Type
|-
| 0x06
| 0x02
| Version
|-
| 0x08
| 0x04
| Certificate chain size
|-
| 0x0C
| 0x04
| Ticket size
|-
| 0x10
| 0x04
| [[TMD]] file size
|-
| 0x14
| 0x04
| Banner size (0 if no banner)
|-
| 0x18
| 0x04
| APP file size
|-
| 0x1C
| 0x04
| 0x80000000
|}

The order of the sections in the header also is the order of them in the CIA file:
* certificate chain
* Ticket
* TMD file data
* APP file data
* banner
The APP data can be either encrypted or cleartext, retail [[Download Play]] CIAs' APP data is always encrypted.

== Banner ==
The banner starts with a 0xF0 large data block, whose purpose is currently unknown. Then at offset 0x400 into the banner section is the actual banner, which contains information about the creator, the first title and the second title (you can see them in the system settings):
{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Magic: 'SMDH'
|-
| 0x04
| 0x04
| Reserved = 0
|}
This small 'table' is immediately followed by a meta-data described like that:
* first title (0x80 bytes)
* second title (0x100 bytes)
* publisher name (0x80 bytes)
All encoded in UTF-16.
This order will repeat 11 times (each block for different language supported).

=== Icons ===

At offset 0x2400 into the banner (inside the Banner's meta-data) to the end, there are two icons:
A small- 24x24 (shown on top screen when pausing the app) & Large - 48x48 icon (the genral icon).

Both of the icons are encoded in RGB655 (havn't been checked for sure yet) meaning 16bpp.

There's a header of 0x40 bytes and then comes the raw data.

The data is encoded in tiles (starting from size 8x8).

If the buffer is like this:

{| class="wikitable" border="1"
|-
! 0
! 1
! 2
! 3
! 4
! 5
! 6
! 7
! 8
! 9
! 10
! 11
! 12
! 13
! 14
! 15
! 16
|-
|}

Then the image would look like this:

{| class="wikitable" border="1"
|-
! x=0
! x=1
! x=2
! x=3
! x=4
|-
| 0
| 1
| 4
| 5
| 16
|-
| 2
| 3
| 6
| 7
| ...
|-
| 8
| 9
| 12
| 13
|-
| 10
| 11
| 14
| 15
|-
|}

Main Page/Navigation

2011-11-13T18:47:14Z

Lazymarek9614: added link to CIA

{{Main page box|Navigation|Main Page/Navigation}}
<div style="margin: -.3em -1em -1em -1em;">
{| width="100%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
! width="33%" | '''General'''
! width="34%" | '''3DS hardware'''
! width="33%" | '''3DS software'''
|- valign="top" style="background: #F5FAFF;"
|
*[[3DS exploits]]
*[[Glossary]]
*[[FAQ]]
*[[Friend code]]
*[[Games]]
|
*[[Hardware]]
*[[Gamecards]]
|
*[[Nintendo Software]]
*[[3DS Development Unit Software]]
*[[CXI|CXI Format]]
*[[CIA|CIA Format]]
*[[File Formats]]
*[[Title list]]
*[[Title metadata]]
*[[SD Filesystem]]
*[[Flash Filesystem]]
*[[Bootloader]]
*[[Savegames]]
|}
</div>
{{box-footer-empty}}

Talk:CIA

2011-11-13T18:44:07Z

Lazymarek9614:

Good work Lazymarek9614, Now 3dsexplorer on the svn is 0.73 (you can download it from the beta link) supports cia. --[[User:Elisherer|Elisherer]] 21:34, 10 November 2011 (CET)
:@Elisherer where is that beta link?--[[User:3dsguy|3dsguy]] 02:39, 11 November 2011 (CET)
::[[3DSExplorer]], bottom of the bage. --[[User:Elisherer|Elisherer]] 08:09, 11 November 2011 (CET)

"Each section is cleartext for dev CIAs, for retail CIAs the APP data is encrypted."
: Dev/Production CIA use the same specification. So I'm not sure what you mean by this.
: The "ctrtool" on the CXI page already parses the CIA format, why re-invent the wheel?
"CIA files can be created with the Nintendo 3DS SDK and installed on the 3DS test units by the Dev Menu."
: Please keep the focus on documentation of the spec., we don't want to explain things from the perspective of SDK users- but for someone that knows (potentially) nothing about the 3DS. The SDK does not tell the whole story of most file formats, and most people don't need to know what the SDK can do for them but what they can do without the SDK. - [[User:Jl12|Jl12]]
::: "Dev/Production CIA use the same specification. So I'm not sure what you mean by this. " I originally worded it that way on the page because both CIAs [[User:3dsguy|3dsguy]] uploaded had cleartext APP data, thus I wasn't sure if CTR-SDK had an option for encrypting the dev CIAs. I don't get why [[User:Elisherer|Elisherer]] re-implements about everything ctrtool already does either... --[[User:Yellows8|Yellows8]] 05:26, 12 November 2011 (CET)
::::If you like working with the windows command line be my guest. I got more progress looking at the files with 3dsexplorer... (And i'm not re-inventing 3dsexplorer didn't support cia so I added it, I will continue fixing the structure to be as accurate it can be) --[[User:Elisherer|Elisherer]] 09:48, 12 November 2011 (CET)
:::::I personaly like a command line tool more, but it's really annoying to have for each format another tool. Shall I create a new page for the certs and tickets?--[[User:Lazymarek9614|Lazymarek9614]] 15:06, 13 November 2011 (CET)
::::::The format of the certs/tickets seem to be the same as before,(besides the new signature types already described on the TMD page) not really necessary to create pages for those.(Any info on what cert is used to sign what should be on a /sys/cert.sys page or so later IMO) [[User:Elisherer|Elisherer]], you're re-inventing the wheel aka re-implementing CXI/CIA code which ctrtool had for months, which is a waste of time IMO. --[[User:Yellows8|Yellows8]] 19:24, 13 November 2011 (CET)
:::::::[[User:Yellows8|Yellows8]], I didn't write any new code for the CXI/CCI/TMD/CIA opening, I just copied it from the ctrtool (as I mentioned when I just written the app). The rest (which is the SAVE flash) became the prime goal of the app and with it I discovered a lot of new information. I try implementing most of the file structures we know so it would be more accessible to everyone (Hoping it would help solving more mysteries). I know that now it's not clear why 3dsexplorer opens these sort of files but with time more information will come and it will grow to extract more important information. I hope you understand. --[[User:Elisherer|Elisherer]] 20:27, 13 November 2011 (CET)
::::::Sorry guys, this discussion doesn't really has anything to do with the CIA format. Please choose another page for this or stop it now. @ [[User:Yellows8|Yellows8]]: I think it's not important to create a new page for it too, only some links to the TMD format and wiibrew wiki are necessary.--[[User:Lazymarek9614|Lazymarek9614]] 20:44, 13 November 2011 (CET)

CIA

2011-11-13T13:11:44Z

Lazymarek9614: /* CIA Header */

=== Overview ===
CIA stands for '''C'''TR '''I'''mportable '''A'''rchive. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NAND used by DSi applications) and on the SD card.

=== Format ===
The CIA format has a similar structure to the [http://wiibrew.org/wiki/Wad WAD format].

The file is represented in little-endian.

The data is aligned in 64 byte blocks (if a content ends at the middle of the block, the next content will begin from a new block).

== CIA Header ==

This is a 32 bytes long header (8 x uint32).

{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Archive Header Size (=0x2020 bytes) (Starts with 0x80 @ offset 0x0020)
|-
| 0x04
| 0x02
| Type
|-
| 0x06
| 0x02
| Version
|-
| 0x08
| 0x04
| Certificate chain size
|-
| 0x0C
| 0x04
| Ticket size
|-
| 0x10
| 0x04
| [[TMD]] file size
|-
| 0x14
| 0x04
| Banner size (0 if no banner)
|-
| 0x18
| 0x04
| APP file size
|-
| 0x1C
| 0x04
| 0x80000000
|}

The order of the sections in the header also is the order of them in the CIA file:
* certificate chain
* Ticket
* TMD file data
* APP file data
* banner
The APP data can be either encrypted or cleartext, retail [[Download Play]] CIAs' APP data is always encrypted.

== Banner ==
The banner starts with a 0xF0 large data block, whose purpose is currently unknown. Then at offset 0x400 into the banner section is the actual banner, which contains information about the creator, the first title and the second title (you can see them in the system settings):
{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Magic: 'SMDH'
|-
| 0x05
| 0x04
| Reserved = 0
|}
This small 'table' is immediately followed by a 0x80 large block for the application name (first title) and then a 0x100 bytes large block for the second title (this title will be shown in the system settings). After that there's alway the same order:
* publisher name (aligned to 0x80 bytes)
* first title (aligned to 0x80 bytes)
* second title (aligned to 0x100 bytes)
The titles are UCS-2.
This order will repeat 10 times, thus there's a 0x1660 bytes large space for these information.

Talk:CIA

2011-11-13T13:06:55Z

Lazymarek9614:

CIA

2011-11-12T20:11:25Z

Lazymarek9614: /* CIA Header */ correcting with info from ctrtool

=== Overview ===
CIA stands for '''C'''TR '''I'''mportable '''A'''rchive. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NAND used by DSi applications) and on the SD card.

=== Format ===
The CIA format has a similar structure to the [http://wiibrew.org/wiki/Wad WAD format].

The file is represented in little-endian.

The data is aligned in 64 byte blocks (if a content ends at the middle of the block, the next content will begin from a new block).

== CIA Header ==

This is a 32 bytes long header (8 x uint32).

{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Archive Header Size (=0x2020 bytes) (Starts with 0x80 @ offset 0x0020)
|-
| 0x04
| 0x02
| Type
|-
| 0x06
| 0x02
| Version
|-
| 0x08
| 0x04
| Certificate chain size
|-
| 0x0C
| 0x04
| Ticket size
|-
| 0x10
| 0x04
| TMD file size
|-
| 0x14
| 0x04
| Banner size (0 if no banner)
|-
| 0x18
| 0x04
| APP file size
|-
| 0x1C
| 0x04
| 0x80000000
|}

The order of the sections in the header also is the order of them in the CIA file:
* certificate chain
* Ticket
* TMD file data
* APP file data
* banner
The APP data can be either encrypted or cleartext, retail [[Download Play]] CIAs' APP data is always encrypted.

== Banner ==
The banner starts with a 0xF0 large data block, whose purpose is currently unknown. Then at offset 0x400 into the banner section is the actual banner, which contains information about the creator, the first title and the second title (you can see them in the system settings):
{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Magic: 'SMDH'
|-
| 0x05
| 0x04
| Reserved = 0
|}
This small 'table' is immediately followed by a 0x80 large block for the application name (first title) and then a 0x100 bytes large block for the second title (this title will be shown in the system settings). After that there's alway the same order:
* publisher name (aligned to 0x80 bytes)
* first title (aligned to 0x80 bytes)
* second title (aligned to 0x100 bytes)
-2 bytes per character-
This order will repeat 10 times, thus there's a 0x1660 bytes large space for these information.

CIA

2011-11-12T20:00:47Z

Lazymarek9614: /* Banner */

=== Overview ===
CIA stands for '''C'''TR '''I'''mportable '''A'''rchive. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NAND used by DSi applications) and on the SD card.

=== Format ===
The CIA format has a similar structure to the [http://wiibrew.org/wiki/Wad WAD format].

The file is represented in little-endian.

The data is aligned in 64 byte blocks (if a content ends at the middle of the block, the next content will begin from a new block).

== CIA Header ==

This is a 32 bytes long header (8 x uint32).

{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Archive Header Size (=0x2020 bytes) (Starts with 0x80 @ offset 0x0020)
|-
| 0x04
| 0x04
| Reserved = 0
|-
| 0x08
| 0x04
| Certificate chain size
|-
| 0x0C
| 0x04
| Ticket size
|-
| 0x10
| 0x04
| TMD file size
|-
| 0x14
| 0x04
| Banner size (0 if no banner)
|-
| 0x18
| 0x04
| APP file size
|-
| 0x1C
| 0x04
| 0x80000000
|}

The order of the sections in the header also is the order of them in the CIA file:
* certificate chain
* Ticket
* TMD file data
* APP file data
* banner
The APP data can be either encrypted or cleartext, retail [[Download Play]] CIAs' APP data is always encrypted.

== Banner ==
The banner starts with a 0xF0 large data block, whose purpose is currently unknown. Then at offset 0x400 into the banner section is the actual banner, which contains information about the creator, the first title and the second title (you can see them in the system settings):
{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Magic: 'SMDH'
|-
| 0x05
| 0x04
| Reserved = 0
|}
This small 'table' is immediately followed by a 0x80 large block for the application name (first title) and then a 0x100 bytes large block for the second title (this title will be shown in the system settings). After that there's alway the same order:
* publisher name (aligned to 0x80 bytes)
* first title (aligned to 0x80 bytes)
* second title (aligned to 0x100 bytes)
-2 bytes per character-
This order will repeat 10 times, thus there's a 0x1660 bytes large space for these information.

CIA

2011-11-11T19:32:53Z

Lazymarek9614: /* Banner */

=== Overview ===
CIA stands for '''C'''TR '''I'''mportable '''A'''rchive. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NAND used by DSi applications) and on the SD card. CIA files can be created with the Nintendo 3DS SDK and installed on the 3DS test units by the Dev Menu.

=== Format ===
The CIA format based on [http://wiibrew.org/wiki/Wad WAD format], so the structure is very similar to the WAD structure.

The file is represented in little-endian.

The data is aligned in 64 byte blocks (if a content ends at the middle of the block, the next content will begin from a new block).

== CIA Header ==

This is a 32 bytes long header (8 x uint32).

{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Archive Header Size (=0x2020 bytes) (Starts with 0x80 @ offset 0x0020)
|-
| 0x04
| 0x04
| Reserved = 0
|-
| 0x08
| 0x04
| Certificate chain size
|-
| 0x0C
| 0x04
| Ticket size
|-
| 0x10
| 0x04
| TMD file size
|-
| 0x14
| 0x04
| Banner size (0 if no banner)
|-
| 0x18
| 0x04
| APP file size
|-
| 0x1C
| 0x04
| 0x80000000
|}

The order of the sections in the header also is the order of them in the CIA file:
* certificate chain
* Ticket
* TMD file data
* APP file data
* banner
The data of the files is decrypted.

== Banner ==
The banner starts with a 0xF0 large data block, whose purpose is currently unknown. Then at offset 0x400 into the banner section is the actual banner, which contains information about the creator, the first title and the second title (you can see them in the system settings):
{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Magic: 'SMDH'
|-
| 0x05
| 0x04
| Reserved = 0
|}
This small 'header' is immediately followed by a 0x80 large block for the application name (first title) and then a 0x100 bytes large block for the second title (this title will be shown in the system settings). After that there's alway the same order:
* publisher name (aligned to 0x80 bytes)
* first title (aligned to 0x80 bytes)
* second title (aligned to 0x100 bytes)
This order will repeat 10 times, thus there's a 0x1660 bytes large space for these information.

CIA

2011-11-11T19:00:28Z

Lazymarek9614: added banner info

=== Overview ===
CIA stands for '''C'''TR '''I'''mportable '''A'''rchive. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NAND used by DSi applications) and on the SD card. CIA files can be created with the Nintendo 3DS SDK and installed on the 3DS test units by the Dev Menu.

=== Format ===
The CIA format based on [http://wiibrew.org/wiki/Wad WAD format], so the structure is very similar to the WAD structure.

The file is represented in little-endian.

The data is aligned in 64 byte blocks (if a content ends at the middle of the block, the next content will begin from a new block).

== CIA Header ==

This is a 32 bytes long header (8 x uint32).

{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Archive Header Size (=0x2020 bytes) (Starts with 0x80 @ offset 0x0020)
|-
| 0x04
| 0x04
| Reserved = 0
|-
| 0x08
| 0x04
| Certificate chain size
|-
| 0x0C
| 0x04
| Ticket size
|-
| 0x10
| 0x04
| TMD file size
|-
| 0x14
| 0x04
| Banner size (0 if no banner)
|-
| 0x18
| 0x04
| APP file size
|-
| 0x1C
| 0x04
| 0x80000000
|}

The order of the sections in the header also is the order of them in the CIA file:
* certificate chain
* Ticket
* TMD file data
* APP file data
* banner
The data of the files is decrypted.

== Banner ==
The banner starts with a 0xF0 large data block, whose purpose is currently unknown. Then at offset 0x400 into the banner section is the actual banner, which contains information about the creator and title of the app (you can see them in the system settings):
{| class="wikitable" border="1"
|-
! START
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x04
| Magic: 'SMDH'
|-
| 0x05
| 0x04
| Reserved = 0
|}

CIA

2011-11-10T18:38:12Z

Lazymarek9614: /* CIA Header */

=== Overview ===
CIA stands for '''C'''TR '''I'''mportable '''A'''rchieve. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NAND used by DSi applications) and on the SD card. CIA files can be created with the Nintendo 3DS SDK and installed on the 3DS test units by the Dev channel.

=== Format ===
The CIA format based on [http://wiibrew.org/wiki/Wad WAD format], so the structure is very similar to the WAD structure.
The file is represented in little-endian.
== CIA Header ==
{| class="wikitable" border="1"
|-
! START
! END
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x03
| 0x04
| constant header size = 0x2020 bytes
|-
| 0x04
| 0x07
| 0x04
| Reserved = 0
|-
| 0x08
| 0x0B
| 0x04
| Certificate chain size
|-
| 0x0C
| 0x0F
| 0x04
| unknown (Ticket size?)
|-
| 0x10
| 0x13
| 0x04
| TMD file size
|-
| 0x14
| 0x17
| 0x04
| Banner size (0 if no banner)
|-
| 0x18
| 0x18
| 0x01
| 0 (reserved, flag?)
|-
| 0x19
| 0x1C
| 0x04
| APP file size
|-
| 0x1D
| 0x20
| 0x04
| unknown (0x80000000)
|}
The order of the sections in the header also is the order of them in the CIA file:
* certificate chain
* Ticket
* TMD file data
* APP file data
The data of the files is decrypted.

CIA

2011-11-10T15:31:05Z

Lazymarek9614: Created page with "=== Overview === CIA stands for '''C'''TR '''I'''mportable '''A'''rchieve. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NA..."

=== Overview ===
CIA stands for '''C'''TR '''I'''mportable '''A'''rchieve. These files contain a compiled application which can be installed on CTR NAND, TWL NAND (part of the NAND used by DSi applications) and on the SD card. CIA files can be created with the Nintendo 3DS SDK and installed on the 3DS test units by the Dev channel.

=== Format ===
The CIA format based on [http://wiibrew.org/wiki/Wad WAD format], so the structure is very similar to the WAD structure.
The file is represented in little-endian.
== CIA Header ==
{| class="wikitable" border="1"
|-
! START
! END
! SIZE
! DESCRIPTION
|-
| 0x00
| 0x03
| 0x04
| constant header size = 0x2020 bytes
|-
| 0x04
| 0x07
| 0x04
| Reserved = 0
|-
| 0x08
| 0x0B
| 0x04
| Certificate chain size
|-
| 0x0C
| 0x0F
| 0x04
| Ticket size
|-
| 0x10
| 0x13
| 0x04
| TMD file size
|-
| 0x14
| 0x17
| 0x04
| Banner size (0 if no banner)
|-
| 0x18
| 0x18
| 0x01
| 0 (reserved, flag?)
|-
| 0x19
| 0x1C
| 0x04
| APP file size
|-
| 0x1D
| 0x20
| 0x04
| unknown (0x80000000)
|}
The order of the sections in the header also is the order of them in the CIA file:
* certificate chain
* Ticket
* TMD file data
* APP file data
The data of the files is decrypted.

Friend code

2011-11-05T20:26:26Z

Lazymarek9614: add my FC

{| class="wikitable" border="1"
|-
! width="32%" | User
! width="20%" | Friend code
! width="8%" |Region
! width="30%" |Comment here
! |Mii image
|-
| Matyapiro31
| <nowiki>3351-4131-7014</nowiki>
| Japan
| Let's hack 3DS! But how?And please resize it small.I cannot do it with my 3DS.
| [[File:HNI 0019.JPG|120px]]
|-
| Crediar
| 2535-3625-3742
| Europe
| None
|
|-
| Kazuma
| 2277-6646-9164
| Europe
| None
|
|-
| SaltyPancakes
| 0044-2836-4738
| Europe
| None
|
|-
| Inspectah
| 3909-7495-9525
| Europe
| None
|
|-
| XanLoves
| 3995-6523-2805
| Europe
| None
|
|-
| muhkuh2005
| 2449-4689-9707
| Europe
| Germanfag
|
|-
| RHOPKINS13
| 4854-6450-1577
| USA
| None
| [[File:RHOPKINS13_Mii.JPG]]
|-
| fishuyo
| 2535-3630-0678
| USA
| None
|
|-
| marcosxd
| 0216-0901-5448
| Mexico
| Crediar add me please, I already added you :)
|
|-
| Mafril
| 5112-3460-1421
| USA
| None
| [[File:Mafril_Mii.JPG]]
|-
|Epicdude
|0130-1922-3022
|USA
|
|-
|David
|3553-9962-0973
|USA
|Add me
|
|-
| Muzer
| 3136-6762-5385
| Europe
| I have added everyone on this list who has a valid friend code (David and marcosxd don't) - so please add me if you get the chance.
| [[File:Muzer_Mii.jpg|120px]]
|-
| Rikku2000
| <nowiki>1461-6425-0347</nowiki>
| Germany
| None
|
|-
|Elisherer
|0001-3489-0550
|USA
|None
|[[File:Elisherer_Mii.JPG|120px]]
|-
|Liam87
|2664-2361-9358
|England
|Add me please, i have added everyone on here, thank you
|
|-
|Luishane
|1289-8459-2533
|Venezuela
|Add me...thanks
|
|-
|Immortal_no1
|0516-7257-0011
|UK
|Add me and PM me on gbatemp.net with yours or e-mail me on "immortal_no1@hotmail.com"
|
|-
|CrimsonΣ　(CrimsonSigma)
|5284-1673-1864
|Brazil
|Add me
|
|-
|E-Chan
|2062-9187-2394
|Spain
|Add me please~! Im up for online gaming of any sorts and discussing the scene!
|
|-
|Lazymarek9614
|1590-4676-4678
|Europe
|Online gaming SSF IV 3D, I try to add everyone here!
|
|-

User:Lazymarek9614

2011-11-05T17:40:03Z

Lazymarek9614:

-I'm not really lazy.-

*-Contact-
:If someone wants to send me something my email is:
:My username without "lazy" and "9614" then "." the domain name (3dbrew) without "3d" at hotmail.de
:(xxxxx.yyyy@hotmail.de)

User:Lazymarek9614

2011-11-05T17:38:50Z

Lazymarek9614: (added contact)

-I'm not really lazy.-

-Contact-
If someone wants to send me something my email is:
My username without "lazy" and "9614" then "." the domain name (3dbrew) without "3d" at hotmail.de
(xxxxx.yyyy@hotmail.de)

User:3dsguy

2011-11-05T16:20:24Z

Lazymarek9614:

Hi its me. Hello :)

I have a 3DS Test Unit, which is capable of installing 3DS/DSi applications compiled in the .cia format from an SD card. So while a way to install applications you create yourself, for normal 3DSs is not possible (i.e. homebrew for 3DS is not yet possible), I am willing to test them for you. If you do make any applications you want me to test, send them in an email with a description of what the application is suppose to do and any instructions. And if you want I can send screenshots and feedback (as detailed as I can) I make about the applications you or others may send. You can send them to "devguy@hotmail.com.au".

Please can you post a link to an uploaded example CIA fie?-[[User:Lazymarek9614|Lazymarek9614]] 13:30, 1 November 2011 (CET)

Do you mean one, that someone has sent me? As I do not have any of my own. By the way I will only post links to .cia files if the sender gives me permission.(I have sent an email asking for permission about 5 minutes ago, so I will or will not give a link depending on their response)--[[User:3dsguy|3dsguy]] 14:21, 1 November 2011 (CET)

Yes, that's exactly what I mean. Is there actually a way that I can create CIA files too?--[[User:Lazymarek9614|Lazymarek9614]] 15:54, 1 November 2011 (CET)

I do not know a way of creating .CIA files. its just that [[Jl12]] asked me as part of a set of questions on my talk page:
*"Would you be willing to run pre-compiled apps imported through your dev menu on your test unit? [and if so do you have an email to send them to]"
I said of course, and gave some details. Then, to my surprise, someone responded to that yesterday, emailing me 3 apps to test. This person on the other hand does know how to compile apps in the .cia format and appeared to have access to the DSi SDK from what i gathered from the email. I can tell you that they did not work once installed from the .cia file, but they did install which I was impressed about. But like I said before I'm waiting on a reply on whether I can distribute the .cia files he/she sent me.--[[User:3dsguy|3dsguy]] 22:37, 1 November 2011 (CET)
:This is the problem many people seem to have with the test units. From what I can tell, the only way to actually run some unsigned application (not created by Nintendo) is by programming it on a development flashcard. --[[User:Neimod|Neimod]] 01:11, 2 November 2011 (CET)
:I'm not sure why you deleted your previous post, but I agree that there are '''supposed''' to be different kinds of media (development flashcard, and copying from SD card to internal NAND) that allow running applications on a test unit. However, of these methods, only so far the development flashcard has proven to work with '''unsigned''' code. The problem lies in the fact that the unsigned development CXI image uses a dummy RSA private key to create the RSA signature, while official Nintendo development CXI images use the real deal. So as it stands, no developer can create proper CXI images for CIA importing. --[[User:Neimod|Neimod]] 14:11, 2 November 2011 (CET)
* I sent him 3 pre-compiled apps at first. ( all by Nintendo ). The first two don't boot because they're not compiled with the libs/firmware running on his test-unit. The 3rd TWL NAND app, doesn't have any icon/banner/title to identify itself after being installed, and although it imports/installs succesfully, it can't be selected or launched from Dev Menu or the Home Menu. Later, I sent him a self-built application ( one not by Nint. ), it installs, boots and runs properly and it just displays some information on the screens; those are the files and images he's linked to here. [the "Hello Galaxy!!!" test-application.]
* They're not unsigned. Dev/test units use a different set of keys then the retail/production units do.
* ''So as it stands, no developer can create proper CXI images for CIA importing.'' - What. I've sent self-built apps to test to 3dsguy and somebody else who owns a test unit running on a different firmware. They work fine. ( Although it's difficult to line up firmware revisions. )
* The one that runs was made (compiled/built) using the SDK/firmware revision matching his test-unit.
* He probably removed the 1st link because I asked him not to post anything with ( even potentially ) copyrighted contents for the sake of not getting this wiki associated with it, the binaries contained code from an e3 demo and the TWL/DSi SDK, we're not doing ourselves any benefit by posting it. The app that runs ( 'Hello Galaxy' ) is a self-compiled application, so it's probably not going to be mistaken for a game or another commercial application. [thus probably safe for wiki.] [[User:Jl12|Jl12]]
::Interesting. That's the first I hear about running self compiled CIA's on a test unit. And yes, sorry I said unsigned application, but I meant signed with the development RSA private key provided by the SDK. The official Nintendo development CIA's do not use keys from the SDK, but rather, a private one that is not distributed. --[[User:Neimod|Neimod]] 02:17, 4 November 2011 (CET)

I had a look at your previous post, 3dsguy, where you have posted a download link for a CIA file. We don't know much about CIA files so it was interesting to see a file and look into it. The actual data for the app/tmd/cmd files seems to be encrypted (expected that) there's only some plain text like "Root"", "CA00000004" and "Root-CA00000004" to name a few (...) which obviously are paths on the NAND FS. However, I've found out that the name of the files/directories (eg name of the app file:"ad7e6744") which are saved on the SD card after installing the archieve seem to be in the CIA file: Not as plain text, they're actually hex values. I'm not really sure about that. It would be nice if you could post another CIA file, 3dsguy, that we can compare them and find out more about it. Shall we actually create a new page about CIA files?--[[User:Lazymarek9614|Lazymarek9614]] 21:48, 2 November 2011 (CET)
: They're certificates.
: It's mentioned partially under "[[Download Play]]", because it's another use of the same file format. [[User:Jl12|Jl12]]

Yes I think we should create another page made for .CIA file and move some of this page to its discussion page. But I've got another .cia file and and boots. see [[http://121.215.146.1/3ds/more_cia_stuff.rar]] for everything you may want to know about it and perhaps from this we can start a new page.--[[User:3dsguy|3dsguy]] 07:52, 3 November 2011 (CET)
: I think this is more about getting our own code running on the 3DS/CTR then it is about CIA. [[User:Jl12|Jl12]]

Lazymarek9614, those "paths" are from the cert chain and the ticket. CIA is based on WAD. --[[User:Yellows8|Yellows8]] 16:25, 3 November 2011 (CET)
: If you are right and the format is based on WAD, then it might be little endian (unlike WAD). First there's an unknown byte (0x20) and then 4 bytes (0x20000000), which looks a lot like the header size in WAD (which is 'always' 32, in BE). So if this is the same field, I'm pretty sure it's LE. --[[User:Lesderid|lesderid]] 19:45, 3 November 2011 (CET)

@3dsguy - if the situation changes about being able to get any other test-units please let me know, thanks. [[User:Jl12|Jl12]]

@[[User:Jl12|Jl12]]: Do you have the Nintendo SDK? If so, can you upload it (correct me if this is a crime)?
: If I did, I wouldn't be posting it here, see bullet #5 above. -[[User:Jl12|Jl12]]
::Oops, sorry. Maybe can you upload some more CIA files which differs in some cases only like the title name, icon etc.?--[[User:Lazymarek9614|Lazymarek9614]] 18:20, 5 November 2011 (CET)
@--[[User:Lesderid|lesderid]]: "So if this is the same field, I'm pretty sure it's LE." I think it's HE. Is the header size actually 0x20 large? There's always a 0x80 byte after 0x20 bytes...--[[User:Lazymarek9614|Lazymarek9614]] 22:09, 4 November 2011 (CET)

Who ever has the ip "151.26.190.77" living in Campobasso, Italy, stop probing the website where I've hosted the files. There are no SDKs on that website so stop trying find something that does not exist.--[[User:3dsguy|3dsguy]] 13:13, 5 November 2011 (CET)

User:3dsguy

2011-11-04T20:09:13Z

Lazymarek9614:

Hi its me. Hello :)

I have a 3DS Test Unit, which is capable of installing 3DS/DSi applications compiled in the .cia format from an SD card. So while a way to install applications you create yourself, for normal 3DSs is not possible (i.e. homebrew for 3DS is not yet possible), I am willing to test them for you. If you do make any applications you want me to test, send them in an email with a description of what the application is suppose to do and any instructions. And if you want I can send screenshots and feedback (as detailed as I can) I make about the applications you or others may send. You can send them to "devguy@hotmail.com.au".

Please can you post a link to an uploaded example CIA fie?-[[User:Lazymarek9614|Lazymarek9614]] 13:30, 1 November 2011 (CET)

Do you mean one, that someone has sent me? As I do not have any of my own. By the way I will only post links to .cia files if the sender gives me permission.(I have sent an email asking for permission about 5 minutes ago, so I will or will not give a link depending on their response)--[[User:3dsguy|3dsguy]] 14:21, 1 November 2011 (CET)

Yes, that's exactly what I mean. Is there actually a way that I can create CIA files too?--[[User:Lazymarek9614|Lazymarek9614]] 15:54, 1 November 2011 (CET)

I do not know a way of creating .CIA files. its just that [[Jl12]] asked me as part of a set of questions on my talk page:
*"Would you be willing to run pre-compiled apps imported through your dev menu on your test unit? [and if so do you have an email to send them to]"
I said of course, and gave some details. Then, to my surprise, someone responded to that yesterday, emailing me 3 apps to test. This person on the other hand does know how to compile apps in the .cia format and appeared to have access to the DSi SDK from what i gathered from the email. I can tell you that they did not work once installed from the .cia file, but they did install which I was impressed about. But like I said before I'm waiting on a reply on whether I can distribute the .cia files he/she sent me.--[[User:3dsguy|3dsguy]] 22:37, 1 November 2011 (CET)
:This is the problem many people seem to have with the test units. From what I can tell, the only way to actually run some unsigned application (not created by Nintendo) is by programming it on a development flashcard. --[[User:Neimod|Neimod]] 01:11, 2 November 2011 (CET)
:I'm not sure why you deleted your previous post, but I agree that there are '''supposed''' to be different kinds of media (development flashcard, and copying from SD card to internal NAND) that allow running applications on a test unit. However, of these methods, only so far the development flashcard has proven to work with '''unsigned''' code. The problem lies in the fact that the unsigned development CXI image uses a dummy RSA private key to create the RSA signature, while official Nintendo development CXI images use the real deal. So as it stands, no developer can create proper CXI images for CIA importing. --[[User:Neimod|Neimod]] 14:11, 2 November 2011 (CET)
* I sent him 3 pre-compiled apps at first. ( all by Nintendo ). The first two don't boot because they're not compiled with the libs/firmware running on his test-unit. The 3rd TWL NAND app, doesn't have any icon/banner/title to identify itself after being installed, and although it imports/installs succesfully, it can't be selected or launched from Dev Menu or the Home Menu. Later, I sent him a self-built application ( one not by Nint. ), it installs, boots and runs properly and it just displays some information on the screens; those are the files and images he's linked to here. [the "Hello Galaxy!!!" test-application.]
* They're not unsigned. Dev/test units use a different set of keys then the retail/production units do.
* ''So as it stands, no developer can create proper CXI images for CIA importing.'' - What. I've sent self-built apps to test to 3dsguy and somebody else who owns a test unit running on a different firmware. They work fine. ( Although it's difficult to line up firmware revisions. )
* The one that runs was made (compiled/built) using the SDK/firmware revision matching his test-unit.
* He probably removed the 1st link because I asked him not to post anything with ( even potentially ) copyrighted contents for the sake of not getting this wiki associated with it, the binaries contained code from an e3 demo and the TWL/DSi SDK, we're not doing ourselves any benefit by posting it. The app that runs ( 'Hello Galaxy' ) is a self-compiled application, so it's probably not going to be mistaken for a game or another commercial application. [thus probably safe for wiki.] [[User:Jl12|Jl12]]
::Interesting. That's the first I hear about running self compiled CIA's on a test unit. And yes, sorry I said unsigned application, but I meant signed with the development RSA private key provided by the SDK. The official Nintendo development CIA's do not use keys from the SDK, but rather, a private one that is not distributed. --[[User:Neimod|Neimod]] 02:17, 4 November 2011 (CET)

I had a look at your previous post, 3dsguy, where you have posted a download link for a CIA file. We don't know much about CIA files so it was interesting to see a file and look into it. The actual data for the app/tmd/cmd files seems to be encrypted (expected that) there's only some plain text like "Root"", "CA00000004" and "Root-CA00000004" to name a few (...) which obviously are paths on the NAND FS. However, I've found out that the name of the files/directories (eg name of the app file:"ad7e6744") which are saved on the SD card after installing the archieve seem to be in the CIA file: Not as plain text, they're actually hex values. I'm not really sure about that. It would be nice if you could post another CIA file, 3dsguy, that we can compare them and find out more about it. Shall we actually create a new page about CIA files?--[[User:Lazymarek9614|Lazymarek9614]] 21:48, 2 November 2011 (CET)
: They're certificates.
: It's mentioned partially under "[[Download Play]]", because it's another use of the same file format. [[User:Jl12|Jl12]]

Yes I think we should create another page made for .CIA file and move some of this page to its discussion page. But I've got another .cia file and and boots. see [[http://121.215.146.1/3ds/more_cia_stuff.rar]] for everything you may want to know about it and perhaps from this we can start a new page.--[[User:3dsguy|3dsguy]] 07:52, 3 November 2011 (CET)
: I think this is more about getting our own code running on the 3DS/CTR then it is about CIA. [[User:Jl12|Jl12]]

Lazymarek9614, those "paths" are from the cert chain and the ticket. CIA is based on WAD. --[[User:Yellows8|Yellows8]] 16:25, 3 November 2011 (CET)
: If you are right and the format is based on WAD, then it might be little endian (unlike WAD). First there's an unknown byte (0x20) and then 4 bytes (0x20000000), which looks a lot like the header size in WAD (which is 'always' 32, in BE). So if this is the same field, I'm pretty sure it's LE. --[[User:Lesderid|lesderid]] 19:45, 3 November 2011 (CET)

@3dsguy - if the situation changes about being able to get any other test-units please let me know, thanks. [[User:Jl12|Jl12]]

@[[User:Jl12|Jl12]]: Do you have the Nintendo SDK? If so, can you upload it (correct me if this is a crime)?
@--[[User:Lesderid|lesderid]]: "So if this is the same field, I'm pretty sure it's LE." I think it's HE. Is the header size actually 0x20 large? There's always a 0x80 byte after 0x20 bytes...--[[User:Lazymarek9614|Lazymarek9614]] 22:09, 4 November 2011 (CET)

User:3dsguy

2011-11-02T19:48:13Z

Lazymarek9614:

Talk:Gamecards

2011-11-02T19:23:12Z

Lazymarek9614:

This could be confused for the augmented reality cards. I think they are called cartridges.--[[User:T3a|T3a]] 18:08, 8 April 2011 (CEST)

^ should at least be a redirect ( "Game Cartridges, Game Cart Hardware, Game Carts" )

* 90 00 00 00 00 00 00 00 ... => 45F80090 for SSFIV, C2FF0090 on Rayman3d.
* Is it just me or do these byte orders keep changing. 9000000000000000 corresponds with "C2FE0090" not "9000FEC2".
* ''"header command has some initial dummy bytes, and eventually responds with a 0x200 byte header."''. Dummy bytes, Where? The redundant A500 cmds? --[[User:Jl12|Jl12]]
:You need to endian swap the data. 9000xxxx is the correct form. The upper bits specify information about the intended platform for the gamecard, and the lower bits specify the media size of the card.
:There are dummy bytes in the response for each 16-byte command. In the wiki these dummy bytes have already been stripped. --[[User:Neimod|Neimod]] 17:41, 3 June 2011 (CEST)
Could you post the size of the original header reply with the dummy bytes. I'm trying to inject logic ( send raw commands ) with a 3DS card. It works well up to the 3E 00 00 00 00 00 00 00 command, I get 'data' returned from the header packet as well but only 00 bytes. --[[User:Jl12|Jl12]]
: The size depends on what speed you are clocking out. Just keep reading until you get something that is non-zero. Also, what device are you using for reading out the data? --[[User:Neimod|Neimod]] 09:09, 4 June 2011 (CEST)

http://pastebin.com/y22zZcZN - That's for 'Street Fighter IV 3D'. There's an NCCH header and cartridge ID. The same method returned x00 00... with a different cart, though. Not sure why there's a difference. I actually have it hooked up to a laptop, where a device over USB reads the pins and the 3DS cart is connected to it there. ( ie. the laptop acts as the 3DS. )

http://pastebin.com/38QxNGqn - That's the cart that was returning an empty header. ( "rayman 3D" ). Seems to work, now.

How did you actually decrypt the encrypted commands, Neimod?--[[User:Lazymarek9614|Lazymarek9614]] 21:06, 1 November 2011 (CET)
: Sorry, it is a little too soon to reveal that. --[[User:Neimod|Neimod]] 02:00, 2 November 2011 (CET)
::I think the 3dbrew members are one team, why do you want to hide it?--[[User:Lazymarek9614|Lazymarek9614]] 21:23, 2 November 2011 (CET)

Talk:Gamecards

2011-11-01T19:06:56Z

Lazymarek9614:

This could be confused for the augmented reality cards. I think they are called cartridges.--[[User:T3a|T3a]] 18:08, 8 April 2011 (CEST)

^ should at least be a redirect ( "Game Cartridges, Game Cart Hardware, Game Carts" )

* 90 00 00 00 00 00 00 00 ... => 45F80090 for SSFIV, C2FF0090 on Rayman3d.
* Is it just me or do these byte orders keep changing. 9000000000000000 corresponds with "C2FE0090" not "9000FEC2".
* ''"header command has some initial dummy bytes, and eventually responds with a 0x200 byte header."''. Dummy bytes, Where? The redundant A500 cmds? --[[User:Jl12|Jl12]]
:You need to endian swap the data. 9000xxxx is the correct form. The upper bits specify information about the intended platform for the gamecard, and the lower bits specify the media size of the card.
:There are dummy bytes in the response for each 16-byte command. In the wiki these dummy bytes have already been stripped. --[[User:Neimod|Neimod]] 17:41, 3 June 2011 (CEST)
Could you post the size of the original header reply with the dummy bytes. I'm trying to inject logic ( send raw commands ) with a 3DS card. It works well up to the 3E 00 00 00 00 00 00 00 command, I get 'data' returned from the header packet as well but only 00 bytes. --[[User:Jl12|Jl12]]
: The size depends on what speed you are clocking out. Just keep reading until you get something that is non-zero. Also, what device are you using for reading out the data? --[[User:Neimod|Neimod]] 09:09, 4 June 2011 (CEST)

http://pastebin.com/y22zZcZN - That's for 'Street Fighter IV 3D'. There's an NCCH header and cartridge ID. The same method returned x00 00... with a different cart, though. Not sure why there's a difference. I actually have it hooked up to a laptop, where a device over USB reads the pins and the 3DS cart is connected to it there. ( ie. the laptop acts as the 3DS. )

http://pastebin.com/38QxNGqn - That's the cart that was returning an empty header. ( "rayman 3D" ). Seems to work, now.

How did you actually decrypt the encrypted commands, Neimod?-[[User:Lazymarek9614|Lazymarek9614]] 21:06, 1 November 2011 (CET)

User:3dsguy

2011-11-01T13:54:32Z

Lazymarek9614:

User:3dsguy

2011-11-01T11:30:05Z

Lazymarek9614:

Talk:Homebrew Format

2011-10-26T16:39:23Z

Lazymarek9614:

It might be a bit early, but I think we can plan the homebrew format for the 3DS now.

Here we can discuss and plan the format (e.g:)
*file extension (.3ds?)
*structure of the format
:*header, banner (icon, 3d model, description...)
:*header and executable areas
...and so on.

I think we should make it similar to the CXI format, that flashcards can run both: commercial and homebrew files.--[[User:Lazymarek9614|Lazymarek9614]] 16:17, 11 September 2011 (CEST)

According to the decisions here I create a tool to create homebrew (3dstool?).--[[User:Lazymarek9614|Lazymarek9614]] 17:13, 11 September 2011 (CEST)
:Do you have any experience in making such files and tool? --[[User:Elisherer|Elisherer]] 19:02, 11 September 2011 (CEST)

::Well, I know about the elf, afx, bmp, 3ds, obj, nds format. I also have read the sources of tools like ndstool (used for creating nds files).

::Let's discuss the format!--[[User:Lazymarek9614|Lazymarek9614]] 19:33, 11 September 2011 (CEST)
:::Ok, i just wanted to know if it's somebody who knows what he talks about, You could never know... I was wondering, because I watch this wiki a lot maybe we wanna make this discussion on another forum like gbatemp so it won't notify us for every post. Because these wiki pages weren't made for big discussions, just on stuff that we aren't sure about... --[[User:Elisherer|Elisherer]] 20:04, 11 September 2011 (CEST)

:::Wouldn't we just use CXI or CCI? I don't see why we'd need to make a new format. Any flash carts made for the 3DS would boot files in the CXI or CCI format, since that's the format commercial ROM images use, and the primary goal of flash carts is to boot commercial pirated content (unfortunately). CXI is also the 3DS's native format, and has space reserved for code, the banner, etc. Not trying to be rude, but I don't think we need to make a new format for 3DS homebrew, or really discuss it for that matter. And we're spamming the crap out of the changelog, so... --[[User:CHR15x94|CHR15x94]] 21:00, 11 September 2011 (CEST)

:::.3ds is used as 3DCG file extension.I want homebrew like linux application. License would be GPL.we could update automatically via spot pass! --Matyapiro31
::::I Agree. it's imprtant that the format would be GPL because otherwise we will be called outlaws...the Wii's homebrew channel clearly was legal. We need to use a wrapper structure (like the CXI) to have an icon, 3d model (based on an existing one) & data (elf binary file). we can add stuff like structure version for future extensions... --[[User:Elisherer|Elisherer]] 08:30, 12 September 2011 (CEST)
:::::We can't deside that the person who make the first homebrew loader can deside that because if you have a format that nobody can lunch nobody will use it. I think the first will be an elf loader because you can just copy the code for loading the elf and lunching it. (http://en.wikipedia.org/wiki/Executable_and_Linking_Format) --[[User:ichfly|ichfly]]
:::::: "I Agree. it's imprtant that the format would be GPL because otherwise we will be called outlaws..." What? Nintendo's .srl/.nds format is used for DS(i) homebrew as well, and many other hb formats... --[[User:Yellows8|Yellows8]] 19:40, 12 September 2011 (CEST)

OK, to summarize the hole thing a bit:

*we have to think about a legal file extension (not .3ds!) and its GPL license
*the homebrew format will have a structure similar to CXI
*elf binary file for the executable area

What about the encryptions made in the CXI file? Will our format encrypted too and what about the model, icon and executable data, are those only file formats like obj /3ds, bmp and elf saved in the homebrew file?

I will start coding the "3ds homebrew tool" soon and publish it on my dropbox folder.
@[[User:ichfly|ichfly]]: The first loader will be sure an elf loader, but for the programmer made this loader it wouldn't be much of work to launch an executble area in the homebrew format (so far it will contain an elf).

Maybe we could use elf as-is and add the media stuff at the end. (every thing has offset so it wont clash with other elf loaders). we can also use the SHT_NOTE section to add the offset to the media_struct.. [http://www.skyfree.org/linux/references/ELF_Format.pdf Elf Format] --[[User:Elisherer|Elisherer]] 16:24, 12 September 2011 (CEST)

Don't waste your time writing a "3ds homebrew tool". Don't be concerned about the hb format, the people who write the first hax decide that. "What about the encryptions made in the CXI file?" CXI supports cleartext *FS etc, no need to encrypt those for a hb format. --[[User:Yellows8|Yellows8]] 19:40, 12 September 2011 (CEST)

:Do you think writing a hack would be more useful, [[User:Yellows8|Yellows8]]? However, before we can run hacks we have to find an exploit. Also writing a hack is complicated (for example we now zero about the GPU). What is your plan? @[[User:Elisherer|Elisherer]]: the link "[http://www.skyfree.org/linux/references/ELF_Format.pdf Elf Format]" seems to be dead.--[[User:Lazymarek9614|Lazymarek9614]] 20:35, 12 September 2011 (CEST)
::Sorry...fixed both links.. --[[User:Elisherer|Elisherer]] 20:51, 12 September 2011 (CEST)
:::"Do you think writing a hack would be more useful" Sure. "for example we now zero about the GPU" Homebrew doesn't *have* to use the PICA200 IMO, unless ds-mode gfx is disabled in 3ds-mode. "What is your plan?" Well, what I'm doing ATM is working on DSi stuff while waiting for someone to get a ramhax rig going, then RE 3DS code once that's possible. --[[User:Yellows8|Yellows8]] 21:45, 12 September 2011 (CEST)

::we must use UTF-8 and universal true type font.Various language can be expressed.

::x3d is not standard,I know...
3ds,stl are used almost softwares,so we can use more resources.
Matyapiro31

::I think we should give the homebrew format the .n3ds extension since I don't think it's used by any application. --[[User:Kiddyshaq34|Kiddyshaq34]]

Elisherer,why don't you make 3DSExlorer a IDE for homebrew until 3ds is hacked? --Matyapiro31 16:24, 26 October 2011 (CEST)
:But we don't have tools to make homebrew...So what will I work with? besides 3dsexplorer isn't a tool for that...maybe in the future we could make an enviroment in eclipse for development of homebrew. I can assure you that it'll be much better. --[[User:Elisherer|Elisherer]] 20:10, 26 October 2011 (CEST)
::What a little bit of googling can do [http://snipah.com/ snipah]. --[[User:Elisherer|Elisherer]] 20:22, 26 October 2011 (CEST)
:::I wanted to make a 3dstool which you can use to create 3ds homebrew files (see above). If you want to add something to my tool, please tell me!--[[User:Lazymarek9614|Lazymarek9614]] 20:39, 26 October 2011 (CEST)

Talk:3DS Development Unit Software

2011-10-19T16:52:02Z

Lazymarek9614:

Thanks, interesting stuff you have written here. --[[User:Neimod|Neimod]] 19:35, 17 October 2011 (CEST)

If hardwares are same as ordinary 3DS　perfectly and then we dump ram ,copy it to our 3DS,

we can use mine as development version. --Matyapiro31 14:24, 18 October 2011 (CEST)
:Dump the RAM? First we have to find out the pinout of it, then we can go ahead!--[[User:Lazymarek9614|Lazymarek9614]] 17:59, 18 October 2011 (CEST)

Sorry,3DS Flash,not RAM.
--Matyapiro31 18:15, 18 October 2011 (CEST)
:Ah, OK! Is the flash chip actually encrypted with a console unique key? If not, this could be a plan!--[[User:Lazymarek9614|Lazymarek9614]] 18:42, 18 October 2011 (CEST)
::But once we can obtain a method to obtain the console unique key, we could have a flash dump from every region of the 3DS as well as a dev 3DS flash dump. And then we could make a custom flash which, which plays all 3DS game regions as well as dev games and has dev programs.--[[User:3dsguy|3dsguy]] 10:13, 19 October 2011 (CEST)

The NAND image of a development 3DS as called here (it is actually a test unit, not development unit) cannot be flashed to a retail 3DS, as there are most likely hardcoded fuses identifying if debug unit, test unit, or retail unit. Not to mention that the NAND image will contain encrypted files coupled with the console ID of the development 3DS, and any other console will have a different ID. --[[User:Neimod|Neimod]] 13:24, 19 October 2011 (CEST)
:Okay, I'm now a bit confused why would Nintendo label the "development 3DS" which is in my possession that is actually a "Test Unit" with a sticker saying "Development Unit". Is Nintendo purposely trying to confuse everyone, or am I missing something? Also if you can, can you tell me the differences between a Test unit and a Development unit?(considering i don't actually have a development unit). And about the custom flash, I was only speculating about what we could do if we found a method to extract the unique console ID/key and i purposely left out the steps of decrypting and re-encrypting 3DS flashes as I was speculating. And you're probably right about there being a hardware flag distinguishing between Test, Dev and Retail units, no doubt for added un-hackability.--[[User:3dsguy|3dsguy]] 17:23, 19 October 2011 (CEST)
::This is the development "unit":
::[[Image:CTRDebugger.jpg|600px]]
::The unit you possess is given to testers. --[[User:Neimod|Neimod]] 18:24, 19 October 2011 (CEST)

Thanks for clearing this up, [[User:Neimod|Neimod]], from now on we will call [[User:3dsguy|3dsguy]]'s special 3DS "test unit".
I think we should focus a bit on getting the system unique key(s) now. I propose that we do a RAM dump, because it's possible that the 3DS (when starting up) pushes the key to RAM. Also we can get some information about the 3DS memory map. However, we don't know the pinout of the RAM, that's the problem...--[[User:Lazymarek9614|Lazymarek9614]] 20:52, 19 October 2011 (CEST)

Talk:3DS Development Unit Software

2011-10-18T14:42:07Z

Lazymarek9614: