If your device loads into a “Download software via DS Download Play” menu, the test was successful.Launch the Download Play application ( ).If the screen stays black or appears to freeze, the test has failed and you will not be able to use the Fredtool method which requires a functioning DS Internet SettingsĭS Download Play Test (used for Frogtool).If your device loads into a “Nintendo Wi-Fi Connection Setup” menu, the test was successful.Go to System Settings, then “Internet Settings”, then “Nintendo DS Connections”.DS Internet Settings Test (used for Fredtool) There are two different methods for building on the Seedminer exploit (described in more detail at the bottom of this page), so even if one of these test fails you can still use another method as long as the other does not fail. While these tests are not strictly necessary to perform the Seedminer exploit, the follow-up exploits to this do require this test to be performed and it would be a waste of time and effort to perform Seedminer without the ability to use the other exploits. Instructions Section I - Compatibility Tests If you do not have access to one of these, there also exists several online helper services where a volunteer running automated software will do this for you. Note that this tool requires a PC with a powerful graphics card to break your device’s DSiWare encryption. For information on how Seedminer works, please see this presentation. Fortunately, the first half of the key ( movable_d) is actually mathematically related to your device’s Friend Code, allowing us to break the encryption. If this key were completely random, the encryption key would be impossible to break on current computing hardware.
We then use this DSiWare encryption key to decrypt a compatible DSiWare application and inject an exploit into it to run our own code (the exact exploit used will depend on your device’s region). To accomplish this, we use a tool called Seedminer to calculate the DSiWare encryption key ( d) for your device.
To install boot9strap on your device, we exploit an oversight in the security restrictions applied to “DSiWare” applications. DS Download Play Test (used for Frogtool).DS Internet Settings Test (used for Fredtool).We'd all also like to thank everyone who has been contributing to the 3DS scene in one way or another, including (but not limited to) : yuriks, Subv, sm, StapleButter, bunnei, WinterMute, neobrain, and, like, so many other people.If you appreciate this guide, I accept Donations. derlanalmeida, ThibG (icons on this page) GW (bringing attention to the webkit bug used by tubehax) In any case a lot of help was provided by the following people : basicshax and basehaxx were made by mrnbayoh. supermysterychunkhax and (v*)hax were done entirely by ShinyQuagsire. The vulnerability used for the original homemenuhax was discovered by yellows8 and exploited jointly by yellows8 and smea. Everything pertaining to smashbroshax, oot3dhax, browserhax, menuhax and stickerhax was made by yellows8. Most of the code for ninjhax, ironhax and tubehax was written by smea.