Guide_3DS/_pages/es_ES/installing-boot9strap-(fredtool).txt

---
title: "Installing boot9strap (Fredtool)"
---

{% include toc title="Tabla de contenidos" %}

{% capture technical_info %}
<summary><em>Technical Details (optional)</em></summary>

This method of using Seedminer for further exploitation uses your `movable.sed` file to decrypt any DSiWare title for the purposes of injecting an exploitable DSiWare title into the DS Internet Settings application.

This is a currently working implementation of the "FIRM partitions known-plaintext" exploit detailed [here](https://www.3dbrew.org/wiki/3DS_System_Flaws).

{% endcapture %}
<details>{{ technical_info | markdownify }}</details>
{: .notice--info}

### Qué necesitas

* Tu archivo `movable.sed` proveniente de haber completado [Seedminer](seedminer)
* The latest release of [Frogminer_save](https://github.com/zoogie/Frogminer/releases/latest) (`Frogminer_save.zip`)
* The latest release of [b9sTool](https://github.com/zoogie/b9sTool/releases/download/v6.1.1/release_6.1.1.zip) (direct download)
* The latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) (the Luma3DS `.zip` file)

#### Sección I - Verificación de CFW

{% include_relative include/cfw-check-fredtool.txt %}

#### Sección II - BannerBomb3

In this section, you will trigger the BannerBomb3 exploit using the DSiWare Management menu and copy the resulting file dump to your computer so that you can use it on the next section.

1. Reinserta tu tarjeta SD en tu consola
1. Enciende tu consola
1. Entra a Configuración de la consola
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
  + Your device should show the BB3 multihax menu
  + If this step causes your device to crash, [follow this troubleshooting guide](troubleshooting#installing-boot9strap-fredtool)
1. Use the D-Pad to navigate and press the (A) button to select "Dump DSiWare"
  + Your device will automatically reboot
1. Apaga tu consola
  
#### Section III - Prep Work

In this section, you will copy the files necessary to temporarily replace DS Connection Settings with Flipnote Studio, which is used to launch the boot9strap (custom firmware) installer.

1. Inserta tu tarjeta SD en tu computadora
1. Open the [DSIHaxInjector_new](https://jenkins.nelthorya.net/job/DSIHaxInjector_new/build?delay=0sec) website on your computer
1. Under the "Username" field, enter any alphanumeric name (no spaces or special characters)
1. Under the "DSiBin" field, upload your `42383841.bin` file from the root of your SD card using the first "Browse..." option
1. Under the "MovableSed" field, upload your `movable.sed` file using the second "Browse..." option
1. Under the "InjectionTarget" field, set the injection target to `DSinternet` (NOT memorypit)
1. Click "Build"
  + Wait a few seconds for the build process to complete
1. In the Build History section on the left, type the Username into the "Filter Builds" field
1. Click on the first search result
  + This result should have the latest timestamp
1. Click the "output_(name).zip" link
1. Ve a `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` en tu tarjeta SD
  + `<ID0>` is the 32-letter folder name that you copied in [Seedminer](seedminer)
  + `<ID1>` is a 32-letter folder inside of the `<ID0>` 
1. Delete `F00D43D5.bin` from your Nintendo DSiWare folder
1. Copy the `42383841.bin`  file from the `hax` folder of the downloaded DSiWare archive (output_(name).zip) to the `Nintendo DSiWare` folder
  ![]({{ "/images/screenshots/bb3/dsiware-location-4.png" | absolute_url }}){: .notice--info} 
1. Copia los archivos `boot.firm` y `boot.3dsx` desde el `.zip` de Luma3DS a la raíz de tu tarjeta SD
  + La raíz de tu tarjeta SD se refiere al primer directorio de la tarjeta, donde puedes ver la carpeta Nintendo 3DS pero no estás dentro de ella
1. Copy `boot.nds` (B9STool) from the release `.zip` to the root of your SD card
1. Copia la carpeta `private` contenida en el `.zip` de Frogminer_save a la raíz de tu tarjeta SD
1. Reinserta tu tarjeta SD en tu consola
1. Enciende tu consola

    ![]({{ "/images/screenshots/fredtool/fredtool-root-layout.png" | absolute_url }})
    {: .notice--info}

#### Section IV - Overwriting DS Connection Settings

In this section, you will copy the hacked DS Connection Settings DSiWare to internal memory, which will temporarily replace it with Flipnote Studio.

1. Entra a Configuración de la consola
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
1. Select the "Haxxxxxxxxx!" title
1. Selecciona "Copiar", luego "OK"
1. Regresa al menú principal de Configuración de la Consola
1. Navigate to `Internet Settings` -> `Nintendo DS Connections`, then select "OK" ([image](/images/screenshots/fredtool/dsconnection.png))
1. Si el exploit fue exitoso, tu consola habrá cargado la versión japonesa de Flipnote Studio

#### Section V - Flipnote Exploit

{% include_relative include/install-boot9strap-b9stool.txt method="dsinternet" %}

#### Section VI - Luma3DS Configuration

1. Press and hold (Select), and while holding (Select), power on your device. This will launch Luma3DS configuration
{% include_relative include/configure-luma3ds.txt %}

{% include_relative include/luma3ds-installed-note.txt %}

#### Section VII - Restoring DS Connection Settings

In this section, you will restore DS Connection Settings to the way it was before it was temporarily replaced with Flipnote Studio in Section IV.

1. Ve a `Nintendo 3DS` -> `<ID0>` -> `<ID1>` -> `Nintendo DSiWare` en tu tarjeta SD
1. Copy the `42383841.bin`  file from the `clean` folder of the downloaded DSiWare archive (output_(name).zip) to the `Nintendo DSiWare` folder, replacing the existing one
1. Reinserta tu tarjeta SD en tu consola
1. Enciende tu consola
1. Entra a Configuración de la consola
1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png))
1. Select the "Nintendo DSi™" title
1. Selecciona "Copiar", luego "OK"

___

### Continúa en [Finalizar instalación](finalizing-setup)
{: .notice--primary}