---
title: "DSiWare Downgrade"
permalink: /dsiware-downgrade.html
---
**If you are on 11.0.0 or 11.1.0, do NOT update to 11.2.0. A new update will be coming soon that allows for DSiWare NFIRM Downgrading _without_ a second 3DS or hardmod for versions under 11.2.0.**
{: .notice--primary}
{: .notice--success}
{% capture notice-old %}
If you already own one of the following games on **the source 3DS**, check out [the old version of this page](dsiware-downgrade-(old)):
+ **Fieldrunners**
+ **Legends of Exidia**
+ **Guitar Rock Tour**
+ **The Legend of Zelda: Four Swords**
{% endcapture %}
{{ notice-old | markdownify }}
If you are between versions 11.0.0 and 11.2.0, you must follow this guide to downgrade your NATIVE_FIRM using DSiWare and a second 3DS which has already has a Custom Firmware installed on it in order to dump and restore your NAND.
{: .notice}
If you are below 11.2.0 on either device, then you should do the ctr-httpwn steps (when prompted) on each device under 11.2.0 to allow you to System Transfer with them.
{: .notice--info}
This takes advantage of an oversight which allows DSiWare titles to read and write anywhere in NAND.
{: .notice--info}
This is a currently working implementation of the "FIRM partitions known-plaintext" exploit detailed [here](https://www.3dbrew.org/wiki/3DS_System_Flaws).
{: .notice--info}
This guide will assume the CFW 3DS is running arm9loaderhax and was setup with this guide, but will work (with slight modifications such as doing all SysNAND steps on EmuNAND) on systems running an EmuNAND. Note that the terms EmuNAND and RedNAND refer to slightly different implementations of [the same concept](http://3dbrew.org/wiki/NAND_Redirection).
{: .notice--info}
You can skip everything related to **Steel Diver: Sub Wars** and steelhax if you already have a working primary entrypoint (e.g: OOT3dHax, FreakyHax) for **the target 3DS**, and use that instead.
{: .notice--info}
{% capture notice-4 %}
This exploit requires you to [System Transfer](http://en-americas-support.nintendo.com/app/answers/detail/a_id/13996/) from a CFW 3DS to a stock 3DS as part of the steps. System Transfers will work in the following directions *only*:
+ New 3DS -> New 3DS
+ Old 3DS or 2DS -> Old 3DS or 2DS
+ Old 3DS or 2DS -> New 3DS
{% endcapture %}
{{ notice-4 | markdownify }}
Both systems MUST be from the same region.
{: .notice--warning}
The source 3DS's NNID will be stuck on the target 3DS unless you either system transfer back or call Nintendo! (details in the instructions)
{: .notice--danger}
System Transfers can only be performed once a week.
{: .notice--danger}
#### What you need
* Two 3DS systems
+ **The source 3DS**: the 3DS running some kind of custom firmware (arm9loaderhax or some form of EmuNAND/EmuNAND) *on the latest version*
+ **The target 3DS**: the 3DS on stock firmware *between 11.0.0 and 11.2.0*
* Purchase (or already own) a compatible DSiWare game from the eShop on **the source 3DS**
+ A pirated copy of the game will **not** work
+ For a list of compatible games, see the [DSiWare List](dsiware-list) page
* The sudokuhax injection `.zip` corresponding to your region
+ [`DSiWare_usa_sudokuhax_injection.zip`](torrents/DSiWare_usa_sudokuhax_injection.torrent) -