This is a list of games and applications, collectively known as DSiWare, for the Nintendo DSi handheld game console, available for download via the DSi Shop.An update released for the Nintendo 3DS in June 2011 added support for the Nintendo eShop service, which contained the DSi Shop's full library of DSiWare games (at the time) with the exception of certain games and applications. Due to reports of abuse, we have added verification tests before we give out the full code details. We found out that some users are selling the codes they get for free from this site. Codes are limited and we want to give it to those who really want to play the game. Tests are easy and can be completed under 2 minutes. Thank you for understanding. For Nintendo 3DS on the 3DS, a GameFAQs message board topic titled 'EU: How to get free DSiWare on your 3DS.'
I was always interested in free Dsi codes and I finally found a way to get them for the Dsi and Dsi XL. Why spend hundreds of dollars a year on virtual handheld content? Instead why not get get it off a genuine website that is dedicated to giving out codes for your Nintendo Dsi.
During this moment that your reading this I will be teaching you how to get a free dsi code.
Important: Follow these steps carefully or else your not going to get your free codes.
Please select the value of the code
Now click the big red button below.
If your having trouble downloading, please click here.
This is a 3DS homebrew application for installing DSiWare savedata exploits, for DSiWare titles which you already have installed. This is intended as a .3dsx which requires access to SVCs which are normally not accessible(arm11kernelhax/'cfw' required). Regarding kernelhax: from the beginning this application was designed to be used with kernelhax which run under a completelyseperate and standalone kernelhax-app, the proper way to handle it(when using kernelhax at all). This was never meant to bunded with any kernelhax in the application build.
This application itself does not use any exploits during installation that could be fixed.
When there's any input savefiles on SD where the DSiWare doesn't use those savefiles, AMPXI will be used to write those files to NAND with the *.new filenames. This involves svcBackdoor. After doing so, a hw-reboot will be enabled when exiting the app. This is intended for DSiWare exploit(s) which load from *.new filename(s) due to not enough space in the main savedata. With the v1.1 release and if you don't add any extra savefiles, this won't be used unless the banner.sav files from v1.0 are left on SD.
This can be used for general DSiWare saveimage import/export as well.
Before using this, you should have DSiWare export(s) from System Settings Data Management on SD for the target titles(in case you ever need to import the original later).
Dsiware Games
The release-archive includes the following:
- The exact same exploit saveimages(plaintext) from when the exploits were released for DSi. This includes sudokuhax, even though it's not really useful on 3DS anyway(since the original title-version isn't officially available for 3DS).
- 4swordshax for 'The Legend of Zelda: Four Swords Anniversary Edition', only USA/EUR regions are supported.
The source for these DSiWare exploits is available here.
This section can be ignored if you just want to install dsiwarehax with the release-archive.
Nintendo Dsiware Downloads
The input size for the *.sav files must be <=0x100000.
The input data for DSiWare is located under the 'dsiware/' directory where the .3dsx runs from. Then under this directory there's directories for each title using the titleID-low, for example: '4B464445'. Under each title directory is the actual input data:
Dsiware Bin Files
- 'info': Required, the directory won't be detected on SD otherwise. Contains the display-text for this entry, normally the exploit name. This shouldn't contain any newlines(any text following newlines won't be displayed).
- 'public.sav': Required, the actual savedata image.
- 'banner.sav' Optional data to use for banner.sav instead of what's used during import, if the DSiWare uses it.
- 'private.sav' Optional data to use for private.sav instead of what's used during import, if the DSiWare uses it.
- 'public_original.sav' Output file written during installation, contains the original data for public.sav that would have been written to NAND during import.
- 'banner_original.sav' Same as above except for banner.sav.
- 'private_original.sav' Same as above except for private.sav.