3dbrew - User contributions [en]

User:Nathan

2012-05-20T13:21:19Z

Nathan:

Hello, I am Nathan from [http://www.ds-scene.net/ DS-Scene].

'''Stuff I own'''
*3DS
*Cave Story 3D
*Cubic Ninja
*Kid Icarus: Uprising
*Mario Kart 7
*Resident Evil: Revelations
*Super Mario 3D Land
*Super Street Figher IV 3D
*The Legend of Zelda: Ocarina of Time 3D
*R4i SaveDongle

User talk:3dsguy

2012-05-20T13:19:44Z

Nathan:

Thanks,3dsguy.
How did you get it? Matyapiro31

As much as I'd like to say, I can't tell you where i got it. But i'm trying to post info as much about Dev 3DS as possible

Does your development 3DS appear to be same hardware as ordinary one? --Matyapiro31 16:10, 18 October 2011 (CEST)

Yes, Matyapiro31, it seems to be that way, i was surprised when i got it, that it did not have parts of the case in red like a panda dev unit, but it had the sticker on the back saying it was a "Development Unit". Also the FCC id does not differ between my Development Unit and a Retail Unit. This probably explains why in the Config menu, the "System Mode" (which I believe is memory allowance) is stuck on "Prod". For some reason Prod mode is 64mb. Why do you ask?

Hi 3dsguy, maybe you have something like a kiosk "demo unit" used at stores (like GameStop, etc.).

* 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. )
* Does it connect to (production) nusd update servers for any updates?
* Do you have any other software or hardware with it? ( firmware updates? rewritable CTR cards? etc. )
* Can you get more of them however/wherever you received yours from?
* 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]
* 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.
- [[User:Jl12|Jl12]]

No problem, I don't have a dev unit or anything so at least I can help out a little this way, lol. [[User:Nathan|Nathan]] 17:19, 20 May 2012 (CEST)

== 3DS Development System Talk ==

Quick link to a page on .CIA files, with sample .cia!!

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, Jl12 responded to that emailing me 3 apps to test. Jl12 on the other hand does know how to compile apps in the .cia format and appears to have access to the DSi SDK from what i gathered from the email.--[[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)

Just a simple question, 3dsguy. In the CIA page you uploaded a CIA example. Can you upload also the binary format uncrypted,please?--[[User:Jocopoco|Jocopoco]] 07:42, 18 November 2011 (CET)

@[[User:Jocopoco|Jocopoco]] - you should ask [[User:Jl12|Jl12]] for it, it's his app after all. If he asks you which one it is it's this one "JlTestApp - test_02.cia"--[[User:3dsguy|3dsguy]] 17:39, 18 November 2011 (CET)
:[[User:Jocopoco|Jocopoco]], that CIA isn't encrypted at all, just use ctrtool to extract the CXI and ExeFS.(and anything else) --[[User:Yellows8|Yellows8]] 18:44, 18 November 2011 (CET)
Sure? In the content folder there is a file named [''id''?].app it's encrypted I cant find anything, arm opcodes, text plain --[[User:Jocopoco|Jocopoco]] 19:09, 18 November 2011 (CET)
:That .app CXI is encrypted the same way as titles downloaded via eShop stored on SD card for retail 3DS,(besides different keys) the sample.cia is cleartext. --[[User:Yellows8|Yellows8]] 20:37, 18 November 2011 (CET)

User talk:3dsguy

2012-05-20T13:19:04Z

Nathan:

Thanks,3dsguy.
How did you get it? Matyapiro31

As much as I'd like to say, I can't tell you where i got it. But i'm trying to post info as much about Dev 3DS as possible

Does your development 3DS appear to be same hardware as ordinary one? --Matyapiro31 16:10, 18 October 2011 (CEST)

Yes, Matyapiro31, it seems to be that way, i was surprised when i got it, that it did not have parts of the case in red like a panda dev unit, but it had the sticker on the back saying it was a "Development Unit". Also the FCC id does not differ between my Development Unit and a Retail Unit. This probably explains why in the Config menu, the "System Mode" (which I believe is memory allowance) is stuck on "Prod". For some reason Prod mode is 64mb. Why do you ask?

Hi 3dsguy, maybe you have something like a kiosk "demo unit" used at stores (like GameStop, etc.).

* 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. )
* Does it connect to (production) nusd update servers for any updates?
* Do you have any other software or hardware with it? ( firmware updates? rewritable CTR cards? etc. )
* Can you get more of them however/wherever you received yours from?
* 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]
* 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.
- [[User:Jl12|Jl12]]

== 3DS Development System Talk ==

Quick link to a page on .CIA files, with sample .cia!!

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, Jl12 responded to that emailing me 3 apps to test. Jl12 on the other hand does know how to compile apps in the .cia format and appears to have access to the DSi SDK from what i gathered from the email.--[[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)

Just a simple question, 3dsguy. In the CIA page you uploaded a CIA example. Can you upload also the binary format uncrypted,please?--[[User:Jocopoco|Jocopoco]] 07:42, 18 November 2011 (CET)

@[[User:Jocopoco|Jocopoco]] - you should ask [[User:Jl12|Jl12]] for it, it's his app after all. If he asks you which one it is it's this one "JlTestApp - test_02.cia"--[[User:3dsguy|3dsguy]] 17:39, 18 November 2011 (CET)
:[[User:Jocopoco|Jocopoco]], that CIA isn't encrypted at all, just use ctrtool to extract the CXI and ExeFS.(and anything else) --[[User:Yellows8|Yellows8]] 18:44, 18 November 2011 (CET)
Sure? In the content folder there is a file named [''id''?].app it's encrypted I cant find anything, arm opcodes, text plain --[[User:Jocopoco|Jocopoco]] 19:09, 18 November 2011 (CET)
:That .app CXI is encrypted the same way as titles downloaded via eShop stored on SD card for retail 3DS,(besides different keys) the sample.cia is cleartext. --[[User:Yellows8|Yellows8]] 20:37, 18 November 2011 (CET)

No problem, I don't have a dev unit or anything so at least I can help out a little this way, lol. [[User:Nathan|Nathan]] 17:19, 20 May 2012 (CEST)

Video Capture

2012-05-20T08:11:16Z

Nathan: Nevermind, I'm an idiot.

{{stub}}
This page documents the procedure of capturing the video signal of the upper and lower screens of the 3DS.

The information on this page was found by 3DBrew User: [[User:Matyapiro31|Matyapiro31]]

[[File:Pinout_point.jpg|300px]]

== Lower Screen Dump ==

Test Points on the front of the board:
{| class="wikitable" border="1"
|-
! # || Name || TP || RED || # || Name || TP || GREEN || # || Name || TP || BLUE
|-
| '''10''' || CN2-31 || 184 || R0 || '''20''' || CN2-39 || 186 || G0 || '''24''' || CN1-34 || 188 || B0
|-
| '''12''' || CN2-32 || 178 || R1 || '''19''' || CN2-40 || 180 || G1 || '''18''' || CN1-33 || 182 || B1
|-
| '''13''' || CN2-33 || 172 || R2 || '''21''' || CN1-40 || 174 || G2 || '''17''' || CN1-32 || 176 || B2
|-
| '''11''' || CN2-34 || 166 || R3 || '''14''' || CN1-39 || above 180 || G3 || '''23''' || CN1-31 || 170 || B3
|-
| '''2''' || CN2-35 || 183 || R4 || '''22''' || CN1-38 || 185 || G4 || '''5''' || CN1-30 || 187 || B4
|-
| '''3''' || CN2-36 || 177 || R5 || '''16''' || CN1-37 || 179 || G5 || '''6''' || CN1-29 || 181 || B5
|-
| '''1''' || CN2-37 || 171 || R6 || '''15''' || CN1-36 || below 179 || G6 || '''7''' || CN1-28 || 175 || B6
|-
| '''4''' || CN2-38 || 165 || R7 || '''9''' || CN1-35 || 167 || G7 || '''8''' || CN1-27 || 169 || B7
|}

{| class="wikitable" border="1"
|-
! # || Name || TP || Description
|-
| '''25''' || CN2-30 || 189 || CLK
|-
| '''26''' || CN2-28 || 191 || VSYNC
|-
| '''27''' || CN2-27 || 190 || HSYNC
|}

This table (taken from the picture above) shows which TP (test-point) to get the bit of the corresponding color (R=red, G=green, B=blue).

And the TP to get Clock, Vertical-Sync and Horizontal-Sync.

== Links ==

* DS Version (DSCapture) : http://home.comcast.net/~olimar/DSCapture/
* DS Version(NisetroCaptureDS):http://katsukity.ocnk.net/product-list/1
* DSi Version(NisetroCaptureDSi):http://katsukity.ocnk.net/product-list/2
* Pics+Progress Updates (3DSCapture): http://home.comcast.net/~olimar/3DSCapture/dev/
* YouTube video of Loopy's Device (USB): http://www.youtube.com/watch?v=Wt5U4o-0hPE
* YouTube video of Loopy's Device (HDMI): http://www.youtube.com/watch?v=s99fUS68AB4

Video Capture

2012-05-20T07:56:54Z

Nathan: Lol mate, you need to pay a bit more attention to peeps removing all links and putting their own links there instead, this one was a shop.

{{stub}}
This page documents the procedure of capturing the video signal of the upper and lower screens of the 3DS.

The information on this page was found by 3DBrew User: [[User:Matyapiro31|Matyapiro31]]

[[File:Pinout_point.jpg|300px]]

== Lower Screen Dump ==

Test Points on the front of the board:
{| class="wikitable" border="1"
|-
! # || Name || TP || RED || # || Name || TP || GREEN || # || Name || TP || BLUE
|-
| '''10''' || CN2-31 || 184 || R0 || '''20''' || CN2-39 || 186 || G0 || '''24''' || CN1-34 || 188 || B0
|-
| '''12''' || CN2-32 || 178 || R1 || '''19''' || CN2-40 || 180 || G1 || '''18''' || CN1-33 || 182 || B1
|-
| '''13''' || CN2-33 || 172 || R2 || '''21''' || CN1-40 || 174 || G2 || '''17''' || CN1-32 || 176 || B2
|-
| '''11''' || CN2-34 || 166 || R3 || '''14''' || CN1-39 || above 180 || G3 || '''23''' || CN1-31 || 170 || B3
|-
| '''2''' || CN2-35 || 183 || R4 || '''22''' || CN1-38 || 185 || G4 || '''5''' || CN1-30 || 187 || B4
|-
| '''3''' || CN2-36 || 177 || R5 || '''16''' || CN1-37 || 179 || G5 || '''6''' || CN1-29 || 181 || B5
|-
| '''1''' || CN2-37 || 171 || R6 || '''15''' || CN1-36 || below 179 || G6 || '''7''' || CN1-28 || 175 || B6
|-
| '''4''' || CN2-38 || 165 || R7 || '''9''' || CN1-35 || 167 || G7 || '''8''' || CN1-27 || 169 || B7
|}

{| class="wikitable" border="1"
|-
! # || Name || TP || Description
|-
| '''25''' || CN2-30 || 189 || CLK
|-
| '''26''' || CN2-28 || 191 || VSYNC
|-
| '''27''' || CN2-27 || 190 || HSYNC
|}

This table (taken from the picture above) shows which TP (test-point) to get the bit of the corresponding color (R=red, G=green, B=blue).

And the TP to get Clock, Vertical-Sync and Horizontal-Sync.

== Links ==

* DS Version (DSCapture) : http://home.comcast.net/~olimar/DSCapture/
* Pics+Progress Updates (3DSCapture): http://home.comcast.net/~olimar/3DSCapture/dev/
* YouTube video of Loopy's Device (USB): http://www.youtube.com/watch?v=Wt5U4o-0hPE
* YouTube video of Loopy's Device (HDMI): http://www.youtube.com/watch?v=s99fUS68AB4

News

2012-05-15T16:28:09Z

Nathan: Grammar.

<noinclude>
==Adding an item==
* Log in to the wiki. Editing is disabled if you don't have an account.
* Add the news event to the top of the list, using this format for the date: <tt><nowiki>'''</nowiki>{{#time: d F y}}<nowiki>''' </nowiki></tt>. Please include the application's creator, version number, and a link to a page on 3DBrew about the application. No external links please.
* '''Move the last entry to the [[:News/Archive|news archive]]. There should be no more than 4 entrees in the list.'''

==Archives==
For older news, see the [[:News/Archive|news archive]].

=== News ===
</noinclude>
*'''15 May 12''' Nintendo released its first implementation of 3DS '[[Title list#0004000E - Add-on Content|Add-on Content]]' with the Mario Kart 1.1 update.
*'''14 May 12''' Nintendo released system update [[4.1.0-8]].
*'''24 April 12''' Nintendo released system update [[4.0.0-7]].
*'''08 February 12''' [[CiTRUS|CiTRUS v0.2]] updated by [[User:Xcution|Xcution]]

User:3dsguy

2012-03-04T13:35:43Z

Nathan:

Hi it's 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".

[[File:Sdk.png|600px]]

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)

Just a simple question, 3dsguy. In the CIA page you uploaded a CIA example. Can you upload also the binary format uncrypted,please?--[[User:Jocopoco|Jocopoco]] 07:42, 18 November 2011 (CET)

@[[User:Jocopoco|Jocopoco]] - you should ask [[User:Jl12|Jl12]] for it, it's his app after all. If he asks you which one it is it's this one "JlTestApp - test_02.cia"--[[User:3dsguy|3dsguy]] 17:39, 18 November 2011 (CET)
:[[User:Jocopoco|Jocopoco]], that CIA isn't encrypted at all, just use ctrtool to extract the CXI and ExeFS.(and anything else) --[[User:Yellows8|Yellows8]] 18:44, 18 November 2011 (CET)
Sure? In the content folder there is a file named [''id''?].app it's encrypted I cant find anything, arm opcodes, text plain --[[User:Jocopoco|Jocopoco]] 19:09, 18 November 2011 (CET)
:That .app CXI is encrypted the same way as titles downloaded via eShop stored on SD card for retail 3DS,(besides different keys) the sample.cia is cleartext. --[[User:Yellows8|Yellows8]] 20:37, 18 November 2011 (CET)

I didn't know you live in Tokyo!--Matyapiro31 15:38, 3 March 2012 (CET)

3dbrew:Community portal

2012-02-28T21:47:30Z

Nathan:

==Attention all noobs==
Go away.

==weird communication==
Hello all, I found some weird UDP communication coming from the 3ds to the internet (japan). Connection is made towards IP 203.180.85.77, 202.232.239.25, and contains a string.
String starts with afa1, then the number 1,4 or 6, then comes either a short or long string (can contain 00) and it ends with a 2-byte counter (b3 in my case). It seems to be repeated, but I cant reproduce it as of now. It happened after I tried to update the 3ds, but it could be related to video/spotpass (suggestions?)

Example:
af a1 44 00 00 00 00 00 00 00 00 b3

Any suggestions/ideas what it could be? --[[User:Mr seeker|Mr seeker]] 20:26, 8 December 2011 (CET)

==3ds dev unit==
Hey,Xcution,don't you release helloworld.cia?--Matyapiro31 15:40, 1 December 2011 (CET)

Nintendo Zone

2012-02-21T22:29:55Z

Nathan: I think you didn't pay attention in that one class about apostrophes mate. http://its-not-its.info/

'''Nintendo Zone''' is the successor to DS Download Stations, offering retailer exclusive content, game videos, screenshots, etc. As of February 6th 2012 demos are available for download, demos are downloaded from the eShop servers and installed to SD card. NZone demos are the same ones available on eShop, these are region-locked as trying to download them from other regions results in an error. USA Best Buy and some other retailers have NZone, this NZone seems to be significantly different from the DS(i) [http://dsibrew.org/wiki/Nintendo_Zone NZone]. Most content available at Best Buy is already available on eShop, like the screenshots/videos, game info etc. The OK Go video is available from NZone however. The OOT video on NZone server is the one from eShop launch like most of the other videos.

Like DSi, when an open 3DS detects NZone the hidden(always accessible for USA) NZone title appears and a notification about it appears. Like DSi this title is already stored on NAND, it's just not visible until you're in range of NZone.(doesn't disappear with sdcard removed) When NZone beacons are in range, 3DS only detects NZone when not connected to Internet already. Once connected to a NZone AP, the beacon payload is cached until disconnected from the AP.

When modified DSi nzone beacons are broadcasted with the 3DS Best Buy authentication param, DSi launcher won't blink the NZone title icon but the title will still semi-work. NZone title would connect to the server, with buttons for demos, Best Buy, and WFC config displayed, but NZone will display an error a while after selecting "Best Buy" service after a bit of loading.(probably unsupported html tags etc)

== Description ==

The NZone browser interface looks very similar to the main 3DS web browser, so it's probably the same as that browser except modified.(and with video support, presumably mobiclip) The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. The Best Buy NZone uses the same authentication parameter at all stores /w NZone. Accessing the server via curl does not work correctly, the server returns old content. This is likely because the NZone title sends new/different params to the server.

=== Beacon payload format ===
This seems to be identical to DS(i) NZone format except for the unknown fields, WPA2 isn't supported. 3DS NZone is not region-locked like DS(i).

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x00
| 32
| AP SSID.
|-
| 0x20
| 10
| Authentication parameter, required for connecting to the server. Server uses this to determine which third-party content to link to on the index page. First ASCII number char in this param is region, this is also used to determine which server to connect to. Regions: 0) JP 1) USA 2/3) EUR 4) KOR 5) China
|-
| 0x2a
| 2
| This u16 was always one in all dumps, unknown what this is. This isn't used by the client.
|-
| 0x2c
| 24
| Some UTF-16 retailer ID string can include the country, unknown what this is but it's not used by the client DS(i). "BestBuy"
|-
| 0x44
| 32
| AP crypto key, if any.
|-
| 0x64
| 1
| Unknown, not used by the DS(i) client. For 3DS this is 0x1, for DS(i) this is 0x0.
|-
| 0x65
| 1
| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152
|-
| 0x66
| 1
| Unknown flags, for 3DS this is 0x1e, for DS(i) this is 0x3. Bits 0 and 1 don't seem to be used by the client. The DS(i) client uses bit2 unknown what for though.
|-
| 0x67
| 5
| Padding.
|-
| 0x6c
| 2
| Unknown, with 3DS this is zero but for DS(i) this was 0x428.
|-
| 0x6e
| 2
| CRC16 over the whole payload excluding checksum offset, initval is 0.
|}

== Wi-Fi Hotspots ==

{| class="wikitable"
! SSID !! Channel !! Security !! Region || Source !! Usable remotely
|-
| Wayport_Access || ? || None || USA || McDonalds || Yes
|-
| attwifi || 1 || None || USA || AT&T || Yes
|-
| Boingo Hotspot || ? || None || USA || Boingo || Yes
|-
| SIMON WiFi || ? || None || USA || SIMON Malls || Yes
|-
| ibahn || ? || None || USA || iBAHN || Yes
|-
| [http://www.free-hotspot.com/ free-hotspot.com] || ? || None || EUR || free-hotspot.com || No
|-
| [http://webapp.7spot.jp/howtoconnect.html 7SPOT] || ? || None || JPN || 7-11 || LAN-only 7-11 hostname used
|-
| [http://www.tsutaya.co.jp/tc/game/deds/about.html TSUTAYA] || ? || None || JPN || TSUTAYA || Only with NZone beacon
|}

* These can be configured on you own router/laptop/phone to identify as a nintendo zone.
* You will need an available internet connection to be able to connect to the servers.
* After connecting the Wi-Fi network, the page displayed will be of the device's region. (Some regions, such as Australia, will not be redirected to a local Nintendo Zone page as there are no plans to introduce Nintendo Zone(s) to that region. If a 3DS has its region set to one of these regions where there are no plans to introduce a Nintendo Zone, they will be brought to the Nintendo Zone of the region of the SSID)
* If you intend to create a permanent, private, Nintendo Zone WiFi spot. It is recommended that you enable MAC address filtering to only allow your devices. As using any form of encryption will prevent the Nintendo Zone WiFi spot from working with your 3DS.

Nintendo Zone

2012-02-05T19:01:19Z

Nathan: Changed that 3dsblog link about free-hotspot.com to the actual site

'''Nintendo Zone''' is the successor to DS Download Stations, offering retailer exclusive content, game videos, screenshots, etc. This service does not have 3DS demos. USA Best Buy and some other retailers have NZone, this NZone seems to be significantly different from the DS(i) [http://dsibrew.org/wiki/Nintendo_Zone NZone]. Most content available at Best Buy is already available on eShop, like the screenshots/videos, game info etc. The OK Go video is available from NZone however. The OOT video on NZone server is the one from eShop launch like most of the other videos, none of the videos are in 3D.

Like DSi, when an open 3DS detects NZone the hidden NZone title appears and a notification about it appears. Like DSi this title is already stored on NAND, it's just not visible until you're in range of NZone.(doesn't disappear with sdcard removed) When NZone beacons are in range, 3DS only detects NZone when not connected to Internet already. Once connected to a NZone AP, the beacon payload is cached until disconnected from the AP.

When modified DSi nzone beacons are broadcasted with the 3DS Best Buy authentication param, launcher won't blink the NZone title icon but the title will still semi-work. NZone title would connect to the server, with buttons for demos, Best Buy, and WFC config displayed, but NZone will display an error a while after selecting "Best Buy" service after a bit of loading.(probably unsupported html tags etc)

== Description ==

The NZone browser interface looks very similar to the main 3DS web browser, so it's probably the same as that browser except modified.(and with video support, presumably mobiclip) The NZone beacon encryption is same as before, except some unknown fields in the cleartext was changed where 3DS will only "detect" NZone /w NZone icon blinking/enabled when the beacons' fields are set this way. DSi will not detect these beacons. 3DS can use DS(i) NZone, but only if the NZone title is already enabled. With DS(i) beacons, 3DS connects to Internet but the NZone icon will not blink. However the NZone title will still work once launched. The Best Buy NZone uses the same authentication parameter at all stores /w NZone. Accessing the server via curl does not work correctly, the server returns old content. This is likely because the NZone title sends new/different params to the server.

=== Beacon payload format ===
This seems to be identical to DS(i) NZone format except for the unknown fields, WPA2 isn't supported. 3DS NZone is not region-locked like DS(i).

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x00
| 32
| AP SSID.
|-
| 0x20
| 10
| Authentication parameter, required for connecting to the server. Server uses this to determine which third-party content to link to on the index page. First ASCII number char in this param is region, this is also used to determine which server to connect to. Regions: 0) JP 1) USA 2/3) EUR 4) KOR 5) China
|-
| 0x2a
| 2
| This u16 was always one in all dumps, unknown what this is. This isn't used by the client.
|-
| 0x2c
| 24
| Some UCS-2 retailer ID string can include the country, unknown what this is but it's not used by the client DS(i). "BestBuy"
|-
| 0x44
| 32
| AP crypto key, if any.
|-
| 0x64
| 1
| Unknown, not used by the DS(i) client. For 3DS this is 0x1, for DS(i) this is 0x0.
|-
| 0x65
| 1
| AP crypto key type: 0) Open 1) WEP-64 2) WEP-128 3) WEP-152
|-
| 0x66
| 1
| Unknown flags, for 3DS this is 0x1e, for DS(i) this is 0x3. Bits 0 and 1 don't seem to be used by the client. The DS(i) client uses bit2 unknown what for though.
|-
| 0x67
| 5
| Padding.
|-
| 0x6c
| 2
| Unknown, with 3DS this is zero but for DS(i) this was 0x428.
|-
| 0x6e
| 2
| CRC16 over the whole payload excluding checksum offset, initval is 0.
|}

== Wi-Fi Hotspots ==

{| class="wikitable"
! SSID !! Channel !! Security !! Region || Source !! Usable remotely
|-
| Wayport_Access || ? || None || USA || McDonalds || Yes
|-
| attwifi || 1 || None || USA || AT&T || Yes
|-
| [http://www.free-hotspot.com/ free-hotspot.com] || ? || None || EUR || free-hotspot.com || No
|-
| [http://webapp.7spot.jp/howtoconnect.html 7SPOT] || ? || None || JPN || 7-11 || LAN-only 7-11 hostname used
|-
| [http://www.tsutaya.co.jp/tc/game/deds/about.html TSUTAYA] || ? || None || JPN || TSUTAYA || Only with NZone beacon
|}

* These can be configured on you own router/laptop/phone to identify as a nintendo zone.
* You will need an available internet connection to be able to connect to the servers.
* After connecting the Wi-Fi network, the page displayed will be of the device's region.

News

2012-01-27T17:14:17Z

Nathan:

<noinclude>
==Adding an item==
* Log in to the wiki. Editing is disabled if you don't have an account.
* Add the news event to the top of the list, using this format for the date: <tt><nowiki>'''</nowiki>{{#time: d F y}}<nowiki>''' </nowiki></tt>. Please include the application's creator, version number, and a link to a page on 3DBrew about the application. No external links please.
* '''Move the last entry to the [[:News/Archive|news archive]]. There should be no more than 4 entrees in the list.'''

==Archives==
For older news, see the [[:News/Archive|news archive]].

=== News ===
</noinclude>
*'''26 January 12''' [[Crappy Tiny Reader|CTR - Crappy Tiny Reader v0.07]] updated by [[User:PsyKopaT|PsyKo]]
*'''05 January 12''' [[Crappy Tiny Reader|CTR - Crappy Tiny Reader v0.06]] updated by [[User:PsyKopaT|PsyKo]]
*'''21 December 11''' Nintendo released system update [[3.0.0-6]]
*'''21 December 11''' [[3DSExplorer|3DSExplorer v1.1.1]] updated by [[User:Elisherer|elisherer]]

File:Crappy-tiny-reader.png

2012-01-27T17:13:02Z

Nathan: uploaded a new version of "File:Crappy-tiny-reader.png": v0.06

CTR - Crappy Tiny Reader v0.05

Crappy Tiny Reader

2012-01-27T17:11:37Z

Nathan: /* Changelog */

{{Infobox homebrew
| title = CTR - Crappy Tiny Reader
| image =
| type = system tool
| author = PsyKo
| download = http://scene.releases.free.fr/tools/CTR.rar
| source = http://scene.releases.free.fr/index.php?page=tools
| version = 0.07
}}

Crappy Tiny Reader is a small Windows application for checking the basic header information of NDS/DSi/3DS dumps.

== Changelog ==

v0.07
* data size calculation bug fixed for 3DS ROMS bigger than 2Gb.
* experimental new tab to detect NDS roms with bad header (DSi not supported)
* lot of new "Maker Codes" added

v0.06
* Tool now supports NDS and DSi ROMS
* the ROM capacity calculation has been changed for 3DS
* bug with CRC32 fixed
* bug with locked files fixed
* Plain region infos now displayed for 3DS dumps
* textboxes black background bug fixed

== Screenshot ==

[[File:Crappy-tiny-reader.png]]

Crappy Tiny Reader

2012-01-27T17:11:22Z

Nathan:

News

2012-01-06T17:43:09Z

Nathan:

<noinclude>
==Adding an item==
* Log in to the wiki. Editing is disabled if you don't have an account.
* Add the news event to the top of the list, using this format for the date: <tt><nowiki>'''</nowiki>{{#time: d F y}}<nowiki>''' </nowiki></tt>. Please include the application's creator, version number, and a link to a page on 3DBrew about the application. No external links please.
* '''Move the last entry to the [[:News/Archive|news archive]]. There should be no more than 4 entrees in the list.'''

==Archives==
For older news, see the [[:News/Archive|news archive]].

=== News ===
</noinclude>
*'''05 January 12''' [[Crappy Tiny Reader|CTR - Crappy Tiny Reader v0.06]] updated by [[User:PsyKopaT|PsyKo]]
*'''21 December 11''' Nintendo released system update [[3.0.0-6]]
*'''21 December 11''' [[3DSExplorer|3DSExplorer v1.1.1]] updated by [[User:Elisherer|elisherer]]
*'''9 December 11''' [[Crappy Tiny Reader|CTR - Crappy Tiny Reader v0.05]] released by [[User:PsyKopaT|PsyKo]]

Crappy Tiny Reader

2012-01-06T17:40:08Z

Nathan:

{{Infobox homebrew
| title = CTR - Crappy Tiny Reader
| image =
| type = system tool
| author = PsyKo
| download = http://scene.releases.free.fr/tools/CTR.zip
| source = http://scene.releases.free.fr/index.php?page=tools
| version = 0.06
}}

Crappy Tiny Reader is a small Windows application for checking the basic header information of NDS/DSi/3DS dumps.

== Changelog ==

v0.06
* Tool now supports NDS and DSi ROMS
* the ROM capacity calculation has been changed for 3DS
* bug with CRC32 fixed
* bug with locked files fixed
* Plain region infos now displayed for 3DS dumps
* textboxes black background bug fixed

== Screenshot ==

[[File:Crappy-tiny-reader.png]]

Trash:R4i SaveDongle

2011-12-23T18:01:27Z

Nathan: Created page with "The R4i SaveDongle is a tool developed by the R4i-SDHC team, which makes it possible to backup and restore save files to DS, DSi (Enhanced) and 3DS game cartridges. [http://www...."

The R4i SaveDongle is a tool developed by the R4i-SDHC team, which makes it possible to backup and restore save files to DS, DSi (Enhanced) and 3DS game cartridges.

[http://www.r4i-sdhc.com/SaveDongle.asp Official site]

CIA-JPN

2011-12-23T17:54:15Z

Nathan:

I will interpret [[CIA]] later.

FAQ

2011-12-23T17:53:37Z

Nathan: /* General Questions */

===== General Questions =====

'''Q:''' Any progress?

'''A:''' See latest news on the main page. If there's any progress, it'll be right there.

'''Q:''' Has the NAND been dumped?

'''A:''' Yes, NAND dumping has been successful, but the image is encrypted. There is also a fake dump floating around on the internet, as an April Fools joke.

===== Contributions =====

'''Q:''' What can I do to help?

'''A:''' Try to keep information on this wiki up to date. Try to correct or clarify any unclear information. Try to document useful information about the Nintendo 3DS.

Circle Pad Pro

2011-12-23T17:50:45Z

Nathan:

Also known as CTR-009, it sends the commands to the console through the IR interface on the back of the console.

[http://what-games.golog.jp/archives/1350330.html Pictures of its contents].

== Usage Instructions ==

[[File:Circle pad pro instructions.jpg]]

Eurosport

2011-12-23T17:49:00Z

Nathan:

Eurosport is a service similar to [[Nintendo Video]]. Please refer to the [[Nintendo Video]] page for more information.

User:Nathan

2011-12-22T14:43:47Z

Nathan: Created page with "Hi, I am Nathan from [http://www.ds-scene.net/ DS-Scene]. '''Stuff I own''' *3DS *Cave Story 3D *Cubic Ninja *Mario Kart 7 *Super Mario 3D Land *Super Street Figher IV 3D *The L..."

Hi, I am Nathan from [http://www.ds-scene.net/ DS-Scene].

'''Stuff I own'''
*3DS
*Cave Story 3D
*Cubic Ninja
*Mario Kart 7
*Super Mario 3D Land
*Super Street Figher IV 3D
*The Legend of Zelda: Ocarina of Time 3D
*R4i SaveDongle

Crappy Tiny Reader

2011-12-22T13:39:45Z

Nathan:

Crappy Tiny Reader/FR

2011-12-22T13:38:38Z

Nathan:

{{Infobox homebrew
| title = CTR - Crappy Tiny Reader
| image =
| type = Utilitaire système
| author = PsyKo
| download = http://scene.releases.free.fr/tools/CTR.zip
| source = http://scene.releases.free.fr/index.php?page=tools
| version = 0.05
}}

Crappy Tiny Reader est une petite application Windows qui permet d'obtenir quelques informations basiques sur les header des dumps 3DS.

== Captures d'écran ==

[[File:Crappy-tiny-reader.png]]

News

2011-12-10T14:24:08Z

Nathan:

<noinclude>
==Adding an item==
* Log in to the wiki. Editing is disabled if you don't have an account.
* Add the news event to the top of the list, using this format for the date: <tt><nowiki>'''</nowiki>{{#time: d F y}}<nowiki>''' </nowiki></tt>. Please include the application's creator, version number, and a link to a page on 3DBrew about the application. No external links please.
* '''Move the last entry to the [[:News/Archive|news archive]]. There should be no more than 4 entrees in the list.'''

==Archives==
For older news, see the [[:News/Archive|news archive]].

=== News ===
</noinclude>
*'''9 December 11''' [[Crappy Tiny Reader|CTR - Crappy Tiny Reader v0.05]] released by PsyKo
*'''7 December 11''' Nintendo released system update [[3.0.0-5]].
*'''7 December 11''' [[3DSExplorer|3DSExplorer v0.96]] updated by [[User:Elisherer|elisherer]]
*'''4 September 11''' [[3DSViewer|3DSViewer v0.1]] released by [[User:Elisherer|elisherer]]
*'''1 August 11''' [[3DS Save DeEncrypter3DS|Save DeEncrypter v1.0]] released by [[User:Blite|Blite]]

Crappy Tiny Reader

2011-12-10T14:21:10Z

Nathan: Created page with "{{Infobox homebrew | title = CTR - Crappy Tiny Reader | image = | type = system tool | author = PsyKo | download = http://scene.releases.free.fr/tools..."

File talk:Crappy-tiny-reader.png

2011-12-10T14:19:56Z

Nathan: Created page with "(c) Triforce @ DS-Scene."

File:Crappy-tiny-reader.png

2011-12-10T14:18:17Z

Nathan: CTR - Crappy Tiny Reader v0.05

CTR - Crappy Tiny Reader v0.05