--- title: "Installing boot9strap (Fredtool)" --- {% include toc title="Table of Contents" %} {% capture technical_info %} Technical Details (optional) 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 %}
{{ technical_info | markdownify }}
{: .notice--info} ### What You Need * Your `movable.sed` file from completing [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/latest) (`boot.nds`) * The latest release of [Luma3DS](https://github.com/LumaTeam/Luma3DS/releases/latest) (the Luma3DS `.zip` file) #### Section I - CFW Check {% include_relative include/cfw-check-fredtool.txt %} #### Section 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. Sett inn SD-kortet i konsollen igjen 1. Power on your device 1. Launch System Settings on your device 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. Slå av enheten #### 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. Sett inn SD-kortet i datamaskinen din 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. Navigate to `Nintendo 3DS` -> `` -> `` -> `Nintendo DSiWare` on your SD card + `` is the 32-letter folder name that you copied in [Seedminer](seedminer) + `` is a 32-letter folder inside of the `` 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. Copy `boot.firm` and `boot.3dsx` from the Luma3DS `.zip` to the root of your SD card + The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it 1. Copy `boot.nds` (B9STool) to the root of your SD card 1. Copy the `private` folder from the Frogminer_save `.zip` to the root of your SD card 1. Sett inn SD-kortet i konsollen igjen 1. Power on your device ![]({{ "/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. Launch System Settings on your device 1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png)) 1. Select the "Haxxxxxxxxx!" title 1. Select "Copy", then select "OK" 1. Return to main menu of the System Settings 1. Navigate to `Internet Settings` -> `Nintendo DS Connections`, then select "OK" ([image](/images/screenshots/fredtool/dsconnection.png)) 1. If the exploit was successful, your device will have loaded the JPN version of 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 + Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging + For the purpose of this guide, these settings will be left on default settings + If you boot to HOME Menu, [follow this troubleshooting guide](https://github.com/zoogie/b9sTool/blob/master/TROUBLESHOOTING.md) 1. Trykk (Start) for å lagre og starte på nytt {% 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. Navigate to `Nintendo 3DS` -> `` -> `` -> `Nintendo DSiWare` on your SD card 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. Sett inn SD-kortet i konsollen igjen 1. Power on your device 1. Launch System Settings on your device 1. Navigate to `Data Management` -> `DSiWare`-> `SD Card` ([image](/images/screenshots/bb3/dsiware-management.png)) 1. Select the "Nintendo DSi™" title 1. Select "Copy", then select "OK" ___ ### Continue to [Finalizing Setup](finalizing-setup) {: .notice--primary}