Guide_3DS/_pages/sr_SP/installing-boot9strap-(dsiware).txt

67 lines
3 KiB
Text
Raw Normal View History

2017-05-21 22:39:40 +02:00
---
2017-05-28 01:39:48 +02:00
title: "Installing boot9strap (DSiWare)"
2017-05-21 22:39:40 +02:00
---
2017-07-11 23:15:50 +02:00
There are two different methods of installing boot9strap using DSiWare on 11.5.0.
2017-05-21 22:39:40 +02:00
{: .notice--info}
One of these methods only works with four specific games that are no longer sold on the eShop, while the other works with quite a few games still sold on the eShop.
{: .notice--info}
2017-07-11 23:15:50 +02:00
Both of these methods require two devices. One 3DS (or 2DS) must be running some kind of custom firmware (such as boot9strap or arm9loaderhax) and is referred to as the *source 3DS*, while the other 3DS (or 2DS) is on stock 11.5.0 and referred to as the *target 3DS*.
2017-05-21 22:39:40 +02:00
{: .notice--info}
Both systems MUST be from the same region.
{: .notice--warning}
Both of these methods will assume that the 3DS running custom firmware is using boot9strap or arm9loaderhax and has completed this guide. While it is possible to do these methods with some other kind of custom firmware, that is out of the scope of this guide.
{: .notice--info}
Both of these methods use a combination of the "FIRM partitions known-plaintext" exploit detailed [here](https://www.3dbrew.org/wiki/3DS_System_Flaws), and an oversight that allows DSiWare titles to read and write to anywhere in encrypted NAND.
{: .notice--info}
{% capture notice-4 %}
Both of these methods require 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*:
2017-06-19 02:59:47 +02:00
+ New 3DS or New 2DS -> New 3DS or New 2DS
+ Old 3DS or Old 2DS -> Old 3DS or Old 2DS
+ Old 3DS or Old 2DS -> New 3DS or New 2DS
2017-05-21 22:39:40 +02:00
{% endcapture %}
<div class="notice--warning">{{ notice-4 | markdownify }}</div>
In both of these methods, the source 3DS's NNID will be stuck on the target 3DS unless you either system transfer back or call Nintendo! (details can be found in the instructions)
{: .notice--danger}
System Transfers can only be performed once a week per NNID.
{: .notice--danger}
___
{% capture notice-1 %}
[Installing boot9strap (DSiWare Save Injection)](installing-boot9strap-(dsiware-save-injection))
<br><br>
This method requires that the source 3DS already legitimately owns one of the following games:
+ "Fieldrunners"
+ "Legends of Exidia"
+ "Guitar Rock Tour"
+ "The Legend of Zelda: Four Swords"
A pirated copy of the game will *not* work, and all of these games have been pulled from the eShop.
{% endcapture %}
<div class="notice--primary">{{ notice-1 | markdownify }}</div>
{% capture notice-1 %}
[Installing boot9strap (DSiWare Game Injection)](installing-boot9strap-(dsiware-game-injection))
<br><br>
This method requires that the source 3DS buys or already legitimately owns one of the games listed on the [Installing boot9strap (DSiWare Game Injection List)](installing-boot9strap-(dsiware-game-injection-list)) page.
<br><br>
A pirated copy of the game will *not* work.
{% endcapture %}
<div class="notice--primary">{{ notice-1 | markdownify }}</div>