By entering this site you need to consent to the use of cookies and their functional use according to this privacy policy. Cookies help us to provide the functional services of the website. Kindly read the below message of use and consent to the use.
The following cookies are stored and shared when accessing this website:
- Internal cookies for the MediaWiki site. This is used for user authentication and article modifications.
- Third-party cookies from Google providing services for Google AdSense and Google Analytics
We will never use data collected outside of the above scope.
Added tips and info section. If you feeling this isn't wiki material, or is wrong, remove it and/or put it in the 3DS exploits:talk page
Line 4:
Line 4:
There are currently no known 3DS-mode exploits.
There are currently no known 3DS-mode exploits.
−
but do not give up hacking.
+
==Tips and info==
−
First we must
+
Information on the 3DS's internals is scarce, notably the following:
−
know more about CXI,CCI,TMD,CMD,FST,and checksums.
+
+
Flash encryption type/key(s)
+
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.
+
+
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.