bannerbomb3: inline bb3-prep

No longer used anywhere except here, since we killed legacy
This commit is contained in:
lifehackerhansol 2023-07-21 00:25:36 -07:00
parent 7c2ce73215
commit bad0f9485d
No known key found for this signature in database
GPG key ID: 80FB184AFC0B3B0E
2 changed files with 24 additions and 25 deletions

View file

@ -31,7 +31,30 @@ If you have a Taiwanese console (indicated by a T after the system version), fol
#### Section I - Prep Work
{% include_relative include/bb3-prep.txt %}
In this section, you will copy the files needed to trigger the BannerBomb3 exploit onto your console's SD card.
1. Power off your console
1. Insert your SD card into your computer
1. Open [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen) on your computer
1. Upload your movable.sed using the “Choose File” option
1. Click “Build and Download”
+ This will download an exploit DSiWare called `F00D43D5.bin` and a payload called `bb3.bin` inside of a zip archive (`DSIWARE_EXPLOIT.zip`)
1. Copy `bb3.bin` from `Release_v3.0.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
+ This file does not need to be opened or extracted
![]({{ "/images/screenshots/bb3/bb3-root-layout.png" | absolute_url }}){: .notice--info}
1. Copy `Launcher.dat` from the folder for your model and region inside the Release `.zip` to the root of your SD card
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` on your SD card
+ `<ID0>` is the 32-letter folder name that you copied in [Seedminer](seedminer)
+ `<ID1>` is a 32-letter folder inside of the `<ID0>`
+ If you have multiple `<ID1>` folders, follow the instructions [here](troubleshooting#bannerbomb3)
![]({{ "/images/screenshots/bb3/dsiware-location-1.png" | absolute_url }}){: .notice--info}
1. Create a folder named `Nintendo DSiWare` inside of the `<ID1>`
+ If you already had the folder *and* there are any existing DSiWare backup files (`<8-character-id>.bin`) inside, copy them to your PC and remove them from your SD card
1. Copy the `F00D43D5.bin` file from `DSIWARE_EXPLOIT.zip` to the `Nintendo DSiWare` folder
![]({{ "/images/screenshots/bb3/dsiware-location-2.png" | absolute_url }})
{: .notice--info}
#### Section II - BannerBomb3

View file

@ -1,24 +0,0 @@
In this section, you will copy the files needed to trigger the BannerBomb3 exploit onto your console's SD card.
1. Power off your console
1. Insert your SD card into your computer
1. Open [Bannerbomb3 Injector](http://3dstools.nhnarwhal.com/#/bb3gen) on your computer
1. Upload your movable.sed using the “Choose File” option
1. Click “Build and Download”
+ This will download an exploit DSiWare called `F00D43D5.bin` and a payload called `bb3.bin` inside of a zip archive (`DSIWARE_EXPLOIT.zip`)
1. Copy `bb3.bin` from `Release_v3.0.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
+ This file does not need to be opened or extracted
![]({{ "/images/screenshots/bb3/bb3-root-layout.png" | absolute_url }}){: .notice--info}
1. Copy `Launcher.dat` from the folder for your model and region inside the Release `.zip` to the root of your SD card
1. Navigate to `Nintendo 3DS` -> `<ID0>` -> `<ID1>` on your SD card
+ `<ID0>` is the 32-letter folder name that you copied in [Seedminer](seedminer)
+ `<ID1>` is a 32-letter folder inside of the `<ID0>`
+ If you have multiple `<ID1>` folders, follow the instructions [here](troubleshooting#bannerbomb3)
![]({{ "/images/screenshots/bb3/dsiware-location-1.png" | absolute_url }}){: .notice--info}
1. Create a folder named `Nintendo DSiWare` inside of the `<ID1>`
+ If you already had the folder *and* there are any existing DSiWare backup files (`<8-character-id>.bin`) inside, copy them to your PC and remove them from your SD card
1. Copy the `F00D43D5.bin` file from `DSIWARE_EXPLOIT.zip` to the `Nintendo DSiWare` folder
![]({{ "/images/screenshots/bb3/dsiware-location-2.png" | absolute_url }})
{: .notice--info}