Right now I love the new splash function, however it goes a bit too quick for a custom splash with keybinds. Could there be a setting to extend or shorten the splash display time? (like luma nightly, but maybe more precise)

It has been a year and a half since the last release. A lot of those 55 commits look really important, and people can't simply build the current tree and install with OFI, without adding the key. Please post a new build and label it as beta, or provide the key info in a text file. I have to ask myself what the point is, of using a key (and requirement for that key) for two entirely open-sourced projects. It's just an annoyance.

Got a New 3DS XL black and it gets shown as New 3DS XL (RED).
Installed it on FIRM0.

How can i open the menu if my home button is broken?

Bad Quality Footage: https://www.youtube.com/watch?v=P7UmNO2lLVc

I tried to unzip the file. the Fastboot.firm file will not unzip. it says this:
Arg_NotSupportedException. I do not know what to do. I downloaded every one of the fastboot3ds files on here, it gave me the same message all across the board. What am I doing wrong?

I am VERY AWARE that this is probably the dumbest issue or question anyone will ever post here, but I just don't care at this point. I just want to get the ROM from Ocarina of Time 3D onto my computer so I can play it on Citra. I am not a computer person. I only know how to follow instructions.
I have downloaded the .zip file for fastboots3DS provided. The first instruction in the README is the following:
"Have fastboot3DS.firm inside the sdmc:/ofifolder on your SD card."
I have no idea where this "fastboots3DS.firm" file is. I have searched the folder for this, and can find no such file. Is this referring to the whole extracted folder? I am incredibly confused and do not want to risk bricking my 2DS by doing this trial and error.
Thanks.

i have selected a firm and set it to quiet boot but upon startup my 3ds does not boot that firm????? please help

Built from latest commit. Sometimes it fails to verify, sometimes it just blackscreens. v1.2 works fine with the same payloads. Sorry I didn't provide much more info.

I haven't been able to figure out if this is even possible, failing left and right, at dumping the same files that boot9strap can dump when pressing and holding certain buttons at boot. I can't be sure if it seems like it would be required, but since it is a feature in the original b9s, could this be included to make a more inclusive bootloader?

I had a few feature requests that I posted on the fastboot3DS thread on the temp, but I think they went unnoticed, so I'll just repost them here where they will be noticed.

1. We should be able to cancel NAND backups. I know, this isn't top-priority, but when I tested the NAND backup feature and found that I couldn't cancel it like GM9. Of course, if you cancel it, it'd better delete the file, because a half-NAND backup would be a horrible thing to have on your SD.
2. We should be able to change the NAND backup output path. I don't like the current SD:/3ds/ output, so I think we should be able to change it, perhaps via the config,
3. We should be able to change the config location. I think the config should be located on the root of the SD, but perhaps it should be changeable on first boot.
   Custom splashes without compiling? It'd be nice, perhaps having a file on the SD card like with Luma splashes.
   Well, that was it. Keep working on this great program!

Does this work with 11.8? I seem to be unable to boot at all after updating to 11.8. Complete black screen. No splashes.

can you add support to boot directly dsx files from boot slot, line unlaunch on dsi

I'm trying to reset all modifications without reflashing the NAND. Is there a way to remove Fastboot3DS, safely?

I would like to request that support for gm9's bonus drive be added to fastboot3ds.

I use multiple SD Cards and I'd like not having to set up the boot settings on first switch.

I'm requesting a PIN feature with optional usage for certain things. For example, being able to choose to have a PIN just to access the fastboot3DS menu, or even require it just to boot (both PIN modes being options found on most modern BIOSes).

These are my suggested uses for a PIN:

1. Booting the 3DS
2. Booting into the fastboot3DS menu
3. Booting specific boot slots rather than every single boot slot as 1. would do
4. Booting from specific files
5. Making NAND backups/restores
6. Flashing a firmware to FIRM1
7. Updating fastboot3DS with a new update

Before using fastboot3DS, I had Luma3DS's PIN feature enabled for both SD and NAND booting to prevent unauthorized access to my 3DS should it be stolen (without proper knowledge of how to delete the PIN file or swap boot.firm, of course, so it's not exactly that secure). However, with fastboot3DS replacing boot9strap and having an interface that can appear before Luma3DS and allow modifications to the system, I feel just a little less sane about leaving my 3DS around, as even if someone picks it up and doesn't know what they're doing, they can still do something they shouldn't.

I also apologize if the Issues section is not a proper location for a feature request, but I saw nothing in the README stating there was a specific location for them.

My 3DS bricked today because i updated to 11.9
I dont know why, i hacked a 3DS yesterday and nothing happened(used b9s for that console)

Tried updating boot.firm
Tried EVERYTHING!

;(

I have a Retail Old2DS with Fastboot3DS v1.2, Luma3DS v10.2 and Nintendo System Software 11.13.0-45E.
I setted 12 boot slots: 6 for NAND and 6 for SDMC. I have following trouble from September 12th (a day after I installed Fastboot3DS) : GodMode9 (booted with [START] key) sometimes starts and other times Luma3DS Chainloader Menu is started. Other payloads, such as Decrypt9 (booted with [A+B+X+Y] keycombo) don't start anymore.
SDMC config file:

BOOT_MODE = Quick
BOOT_OPTION1 = sdmc:/firm_linux_loader.firm
BOOT_OPTION2 = sdmc:/luma/payloads/godmode9.firm
BOOT_OPTION2_BUTTONS = START
BOOT_OPTION3 = sdmc:/luma/payloads/Decrypt9WIP.firm
BOOT_OPTION3_BUTTONS = A + B + X + Y
BOOT_OPTION4 = sdmc:/luma/payloads/ntrboot_flasher.firm
BOOT_OPTION4_BUTTONS = UP + R + L
BOOT_OPTION5 = sdmc:/boot.firm
BOOT_OPTION6 = sdmc:/luma/payloads/OpenFirmInstaller.firm
BOOT_OPTION6_BUTTONS = START + UP + R + L
BOOT_OPTION1_BUTTONS = SELECT + START

NAND Config file:

BOOT_MODE = Quick
BOOT_OPTION1 = sdmc:/boot.firm
BOOT_OPTION2 = nand:/rw/luma/payloads/GodMode9.firm
BOOT_OPTION2_BUTTONS = START
BOOT_OPTION3 = nand:/rw/luma/payloads/Decrypt9WIP.firm
BOOT_OPTION3_BUTTONS = A + B + X + Y
BOOT_OPTION4 = nand:/rw/luma/payloads/ntrboot_flasher.firm
BOOT_OPTION4_BUTTONS = UP + R + L
BOOT_OPTION5 = nand:/boot.firm
BOOT_OPTION6 = sdmc:/luma/payloads/SafeB9SInstaller.firm
BOOT_OPTION6_BUTTONS = A + B + R + L + X + Y

This files are completely created by Fastboot3DS (I didn't edit them manually).
I tried to reinstall Fastboot3DS using its update utility, GodMode9 FIRM0 installer and OpenFirmInstaller.firm (I used it to install Fastboot3DS for the fist time), but I didn't resolve this trouble.

I'd like to put a few utilities on my NAND's bonus drive and boot from there, however I can't seem to find it in 1.2 stable despite it being formatted, visible and read/write in GM9. Would there be a way to add this support or am I just missing it?

Similar to how boot9strap checks sdmc:/boot.firm, but can fall back to nand:/boot.firm if the first one fails. I accidentally moved my boot.firm off of my SD card instead of copying it, and I was surprised to see it didn't fall back to the copy on CTRNAND. This is with the first two slots being configured to autoboot, slot 1 being sdmc:/boot.firm and slot 2 being nand:/boot.firm of course.

The title says it all. This is mostly to have a smooth transition between Luma3DS splashes and FB3DS splashes (Luma3DS clears it so you wouldn’t worry about OS interference)

Basically as the title says. I've tested it with all of my DSi games and every time I exit to the home menu they crash.

I'm trying to compile a clean fastboot3ds and I believe I have all the requirements, but I get this error.
C:/Users/willi/Desktop/fastboot3DS-1.0/fastboot3DS-1.0/arm9/../source/arm9/firmwriter.c:166:28: error: expected expression before '<<' token
if(vers < ((u32)VERS_MAJOR<<16 | VERS_MINOR)) return UPDATE_ERR_DOWNGRADE;
^~
make[2]: *** [/opt/devkitpro/devkitARM/base_rules:85: firmwriter.o] Error 1
make[2]: *** Waiting for unfinished jobs....
C:/Users/willi/Desktop/fastboot3DS-1.0/fastboot3DS-1.0/arm9/../thirdparty/fatfs/ff.c: In function 'f_setlabel':
C:/Users/willi/Desktop/fastboot3DS-1.0/fastboot3DS-1.0/arm9/../thirdparty/fatfs/ff.c:5062:2: warning: this 'for' clause does not guard... [-Wmisleading-indentation]
for (slen = 0; (UINT)label[slen] >= ' '; slen++) ; /* Get name length /
^~~
C:/Users/willi/Desktop/fastboot3DS-1.0/fastboot3DS-1.0/arm9/../thirdparty/fatfs/ff.c:5082:2: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'for'
{ / On the FAT/FAT32 volume */
^
make[1]: *** [Makefile:112: build] Error 2
make: *** [Makefile:31: checkarm9] Error 2

help would very much be appreciated ^^

Right now the behavior seems to be:

• If SD is present, load and save there
  • If there's no existing config, look for one on the NAND
    • Save to SD even if loaded from NAND
• If SD is not present, load and save on the NAND instead

That way I cannot force it to use the NAND even if an SD card is present.

Can the behavior be changed so that it saves to the NAND if the config was loaded from the NAND?

I am currently trying to modify FB3DS. I want to disable FB3DS to write config files to NAND even if installed to firm0, but if there is a file (self created) it should be able to boot from it. I should not lose any functionality.
So can i just delete source/arm11/config.c#L176 to source/arm11/config.c#L179
without breaking anything? Is this the only nand autowrite?

I have tried restoring a corrupt nand which is now not installed. ( My o3ds I gave to a friend came back with no nand on it?) So I have a nand backup just no way to restore it. A dedicated feature to force restore a nand would be nice.

Version of FastBoot3ds: Release 1.2

Issue: Attempting to dump Boot9.bin and Boot11.bin using FastBoot3ds's built in setting says it succeeds, yet doesn't actually dump the bootrom. (Proven by searching through every single directory on the SD Card after dumping)

System Tested on (not including the two systems in NH Discord):

New Nintendo 3ds - FB3ds 1.2+Luma 10.2 and SysNand 11.13.0-45U.

Using ubuntu bash, the build errors out with:

Error opening key file fastboot3DS_priv.key
139948605310616:error:02001002:system library:fopen:No such file or directory:bss_file.c:398:fopen('fastboot3DS_priv.key','r')
139948605310616:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
unable to load key file
0+0 records in
0+0 records out
0 bytes copied, 0.001844 s, 0.0 kB/s
make: 7z: Command not found
Makefile:57: recipe for target 'release' failed
make: *** [release] Error 127

See title. I have multiple .firm's to choose from, but the names are not fully displayed because the display width is limited. There is enough space on the screen though. Please widen this display.

Hi, I see last release almost 4 years old but many commit since this time. It's recommend for compile for self?

Thx

Steps to Reproduce:

1. Delete fastbootcfg.txt from SD
2. Turn on 3DS
3. Turn off 3DS (or run any mode that forces the 3DS to reboot)
4. Fastboot3DS menu opens
5. Open a File Manager and see that a blank fastbootcfg.txt has been created in the proper location

What I think is happening:

1. Fastboot3DS boots the 3DS normally
2. Reads the config from NAND
3. Makes a config on the SD Card (as if it didn't exist on NAND or SD)
4. Continues the boot process
5. Upon rebooting it sees the blank config on SD and enters the menu

Additional info can be provided if required.

It has been a year since the last release, and there have been many new commits, will you consider making a new official release?

Thanks!

I don't know if it is normal but after installing fastboot3ds the boot9.bin and boot11.bin just disappeared

after swapping sd cards to a larger one fastboot keeps giving me this error saying that a directory that one of my boot slots is set to does not exist though when looking at my fastboot settings there is no boot slot setup there and its basically just telling me that it cant find a firm where I never told it to look I tried just launching luma from there and I just get a black screen after launching deleting the settings file from the sd card did not help

Instead of always showing boot, only show boot images/splashes on cold boots...

The commit (474eb30) on Luma3DS dose not boot on fastboot3DS but dose on B9S and GM9 (according to @AuroraWright).

I have a N3DS on system 11.9 as well as fastboot3ds 1.2 stable

Thanks for reading, I just wanted to inform the developers about compatibility issues

UPDATE: This issue has been fixed on luma's end in this
LumaTeam/Luma3DS@4e5f6e1

sdmc:/3DS/ is where things like HBL payloads and homebrew app data goes, it would clutter up the folder further. I would propose a system as such:
NAND backups: sdmc:/backups/
boot*/otp dumps: sdmc:/dumps/

source/arm9/firmwriter.c
166:28 error: expected expression before '<<' token
if(vers < ((u32)VERS_MAJOR<<16 | VERS_MINOR)) return UPDATE_ERR_DOWNGRADE;
^~
make[2]: *** [/opt/devkitpro/devkitARM/base_rules:84: firmwriter.o] Error 1

I use a forwarder to put NDS games onto my 3ds. Fastboot3ds messes with the loading of larger games though, as it'll flash the Fastboot3ds logo and take me to the screen where you turn off the system. I have found no workaround, and it'd really suck if I'm unable to continue with my playthroughs because of this;;

Hi!

I have a problem installing FastBoot3DS with a GodMode9 Script.

I know that the best option is install It with OpenFirmInstaller but I need a way to install It directly to the firm1 partition with my GM9 script.

I tried to install It directly with GodMode9 and It works but I tried several times to inyect It directly to the firm1 with my script and It always throw the blue screen.

Anyways, thanks for this amazing proyect, it's a good Boot9strap alternative

This happens at least on commit c417a8a, though i do not know if it happens in ef732dc, the latest commit at the moment.

I would add an image, but I do not have a means of such at the moment

It says "New 3DS XL (RED)" But mine is a New 3DS XL Metal Blue

After the system crashes, luma3ds boots, loads the splash screen, but then it's just a black screen and never boots to the home menu. I have tested this with boot9strap and luma3ds boots up correctly after a crash, which leads me to believe it's related to fastboot3ds. In order to boot back up again, I have to boot into the fastboot menu and manually select "continue boot."

Godemode9 freezes when launched by key combo. New 2ds XL, 11.6, USA. Boot9strap

(Originally posted at GBATemp)

OK, so my original SD card got corrupted, and I didn't want to go through and replace the CFW and homebrew software and I found this: 3ds CFW: Restoring functionality on a new SD card. Put it all on my SD card, and all worked fine.

After a few days, I wanted to update B9S. So I, being the naive person that I am, decided to launch OPENFIRMINSTALLER instead of SafeB9SInstaller. They looked the same to me, and at the time I didn't know Fastboot3DS was on the SD card. I installed it, and now I am stuck on the Fastboot3DS screen, with NO WAY OF LAUNCHING LUMA3DS! Not to mention that the SD card will not mount, and every time I try to get into the NAND, it freezes up completely.

So, yeah. I'm stuck.

TL;DR: I need help.

If the autoboot slot fails to load on quiet mode, this is how the error message displays for me: