Multiple Feature Requests about fastboot3ds HOT 2 CLOSED

Also, fastboot3DS appears to support A9LH payloads. I'll do a bit more research, but when I was selecting a firm to boot, I noticed that firm0 and firm1 backups that I had made some time ago were available to be used. Not sure if this is because it is a firm, just renamed to .bin (since firm0 and firm1 are .bin's), or if it actually work with A9LH payloads. Is there a difference between a .firm and a .bin besides extension?

from fastboot3ds.

Okay...

1. Doublecheck. You can already cancel NAND backups via the B, HOME or POWER buttons.
2. While not a bad idea per se, the current location is the same location as the location of the config file. It's simple, everyone knows where their NAND backups go, and thanks to the timestamp, everyone also knows the order of their NAND backups. You're also free to copy your NAND backups anywhere you like.
3. Ever heard about the hen-egg-problem? If the path of the config is a config item, where should fastboot3DS pull it from if it doesn't even know the config path before loading the config? No way around this, the config path needs to stay fixed.

Custom splashes are already in the current nightly and will make it to the next release. Also, a FIRM0 / FIRM1 backup is a .firm. No suprise it works.

from fastboot3ds.