Talk:3DS Development Unit Software

From 3dbrew
Revision as of 14:10, 1 November 2011 by 3dsguy (talk | contribs)
Jump to navigation Jump to search

Thanks, interesting stuff you have written here. --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!--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!--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.--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. --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.--3dsguy 17:23, 19 October 2011 (CEST)
This is the development "unit":
The unit you possess is given to testers. --Neimod 18:24, 19 October 2011 (CEST)

Thanks for clearing this up, Neimod, from now on we will call 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...--Lazymarek9614 20:52, 19 October 2011 (CEST)

Just putting this out there, as 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 yet 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, compile them in the .cia format and 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 "". --3dsguy 12:52, 1 November 2011 (CET)

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.