3dbrew

Changes

3DS System Flaws (edit)

Revision as of 01:11, 13 December 2011

420 bytes removed ,  01:11, 13 December 2011
Removed some stuff. Added 'Current efforts' section with a link to the amazing RAM dumping setup neimod has been working on for a while. Breathtaking work, neimod!
Line 1: Line 1:  
Exploits are used to execute unofficial code (homebrew) on the Nintendo 3DS. This page is a list of known 3DS-mode exploits.
 
Exploits are used to execute unofficial code (homebrew) on the Nintendo 3DS. This page is a list of known 3DS-mode exploits.
   −
==List of 3DS Exploits==
+
==List of 3DS exploits==
 
There are currently no known 3DS-mode exploits.
 
There are currently no known 3DS-mode exploits.
   −
==Tips and info==
+
==Current efforts==
−
Information on the 3DS's internals is scarce, notably the following:
+
There are people working on finding exploits and documenting the 3DS. Here's a list of some current efforts being made to make homebrew on the 3DS possible:
   −
Flash encryption type/key(s)
+
* Neimod has been working on a RAM dumping setup for a little while now. He's desoldered the 3DS's RAM chip and hooked it and the RAM pinouts on the 3DS's PCB up to a custom RAM dumping setup. Recent photos show that the setup is working quite well, with the 3DS successfully booting up. Pictures of neimod's work can be found on [http://www.flickr.com/photos/neimod/ his Flickr stream].
−
Gamecard encryption key(s)
  −
Memory mappings
  −
Pica200 GPU registers and general programming info (commands, setup, etc.)
  −
Many other things
     −
What this means is if any exploits are found, it would be very difficult to do anything useful with them.
+
==Tips and info==
−
 
+
Information on the 3DS's internals is scarce. There is little information on programming the 3DS available, other than basic information found by taking the 3DS apart, leaks and reverse engineering.
−
There are similarities between the 3DS and it's predecessors that could be used to communicate with an outside device (PC, microcontroller, etc.), one of them being the WiFi chip, which is very similar between the 3DS and DSi. Theoretically, if you could launch some code on the 3DS via an exploit, you could initialize the WiFi chip in the 3DS, connect to an access point, then connect to some network connected device, and send and receive data from the 3DS to the network connected device. This would allow you to do memory dumps over WiFi, upload code to the 3DS, etc.
     −
Another method would be to dump the contents of the 3DS's RAM through a hardware modification. This can be done by soldering connections to the 3DS's RAM and connecting it to an FPGA or similar device. The 3DS would then be powered on and it would modify and use RAM as it normally would, and then the hacker can disengage the 3DS from it's RAM (through a switch, etc.) or access the RAM through the FPGA while the 3DS is still using it. A good example of this type of modification is scanlime's work with the DSi ([http://hackmii.com/2009/09/dsi-ram-hax/ link]).
+
What this means is if any exploits are found, it would be very difficult to do anything useful with them. Work is currently being done to find out how the 3DS ticks and to aid in finding exploits. See the [[#Current efforts | current efforts]] section of this page for examples and more information.
CHR15x94
34

edits

Retrieved from "https://www.3dbrew.org/wiki/Special:MobileDiff/1789"