Installation is recommended though, for faster boot times. And it needs to be installed for the bootrom exploit to work.
Once properly set, I can't think of any reason to go back to boot9strap.
[+] It does boot a little faster.
[+] When quick boot is selected, it's non-intrusive (not a fan of boot-up splash screens). Works just like if you had boot9strap.
[+] (Start) still goes to GodMode9 and (Select) allows Luma3DS configuration.
[+] Dat button FIRM chainload. (Better remember which is which).
Minor complaints
[-] Despite the quick access to fastboot3ds holding the (HOME) button, any impatience tapping the (A) button during the splash sequence will automatically boot you into HOME Menu. Caught me by surprised after 5 or so times.
[-] Luma3DS game patching can be borked if you select the boot.firm found on CTRNAND instead of SD card. Oops.
The only reason I held out so long in trying this was that there wasn't a stable release until now. This definitely should get wider adoption, especially from novice users.
[+] It does boot a little faster.
[+] When quick boot is selected, it's non-intrusive (not a fan of boot-up splash screens). Works just like if you had boot9strap.
[+] (Start) still goes to GodMode9 and (Select) allows Luma3DS configuration.
[+] Dat button FIRM chainload. (Better remember which is which).
Minor complaints
[-] Despite the quick access to fastboot3ds holding the (HOME) button, any impatience tapping the (A) button during the splash sequence will automatically boot you into HOME Menu. Caught me by surprised after 5 or so times.
[-] Luma3DS game patching can be borked if you select the boot.firm found on CTRNAND instead of SD card. Oops.
The only reason I held out so long in trying this was that there wasn't a stable release until now. This definitely should get wider adoption, especially from novice users.
Last edited by TurdPooCharger,
I am pretty sure button presses override holding the home button and thus boots into that payload
I can't seem to replicate the second issue. I've tested Luma3DS from all forms of booting (CTRNAND, SD, and FIRM1) and found no issues with the patching.
The game that stopped working for me was Metroid II - Samus Return (USA) GB Virtual Console (0004000000050400).
This is what I have:
- luma/titles/0004000000050400/romfs/rom/DMGMEA-0.414
The patch was sourced here, exact version of the patch I can't remember (i'll have to backtrack).
***
Another explanation, I messed with fastboot3ds with both SD card in place and without it.
In one session with the SD card in place (before installing FB3DS on CTRNAND), I used (Start) button to go into Luma3DS chainloader, went into fastboot3ds, and selected boot.firm found on CTRNAND.
In another session without the SD card and after using OpenFirmInstaller to install fastboot3ds, I used (HOME) button to boot into fastboot3DS. I was greeted with an empty slot, so I selected boot.firm on CTRNAND.
After Metroid color patch stopped working.
3rd session with SD card in place, went into Fastboot3DS again (with HOME button), and reselected SLOT1 to point at the Luma3DS boot.firm found on my SD card. This is when colored metroid start working again.
***
I'm going to try moving the titles folder with the patch over to my CTRNAND and switch the setting back in fastboot3ds to see if the patch depends on where the boot.firm is located.
***
Edit - And here's what I found!
So I copied my folder :
- 0:/luma/titles
- 1:/rw/luma/titles
To determine if the boot.firm and titles patch must match the same NAND or SD card location, I deleted the titles folder on my CTRNAND.
Went back to Metroid, and the game went back to original black and white.
Last edited by TurdPooCharger,
Apparently this is deliberate, if you load luma from ctrnand it looks for all its folders (including the patching ones, splash, and config) there too. Still kinda dumb that you can't force a certain one in the config though.
Both of these are completely subjective. FB3DS does have a lot of features that Luma3DS doesn't have, like NAND backup/restore, on-the-fly payload switching (you can say change your auto-boot from Luma3DS to GM9 directly on the system itself) and a bootloader, booting payloads off FIRM1(via dev mode,) and several more features. Not everyone uses all of these features and may not find them useful nor better than the simple bootloader provided by Luma3DS.
Personally I suggest just trying FB3DS, you can run it without even needing to install it.
Last edited by The Catboy,
We just released fastboot3DS v1.2. This is new:
As you see, this is just a minor update, updating is recommenden. As always report bugs or make feature requests if you would like us to add a feature.
As you see, this is just a minor update, updating is recommenden. As always report bugs or make feature requests if you would like us to add a feature.
If anyone wants to know how to get into dev mode, go to the credits screen and enter the konami code. that should do it.fastboot3DS is a bootloader for the 3DS console, intended to be installed to the FIRM0 partition. It allows you to assign homebrew in .firm format to bootslots, and to chainload bootslots via either a bootmenu or a button combo of your choosing. fastboot3DS also contains basic tools for NAND backups and restores.
Instructions for installation are included in the readme. Hint: If you are afraid of a brick (won't happen) and / or just want to try fastboot3DS without a proper installation, you can also chainload it via your existing bootloader. If you have boot9strap installed, you'd just rename fastboot3DS.firm to boot.firm and copy it to the SD card root.
Release: https://github.com/derrekr/fastboot3DS/releases
Source / Readme: https://github.com/derrekr/fastboot3DS
There are some options (that I cannot think of off the top of my head) that require dev mode.
Dev Mode allows you to force restore NAND and flash firmware to FIRM1. The reason why the typical 3DS user shouldn't have any business messing with a forced NAND restore is because you can soft brick or destroy the custom firmware if your NAND image isn't perfect. The difference between Restore SysNAND (Safe) vs Restore SysNAND (Full -or Forced) is that (Safe) leaves alone FIRM1.
In a "good" firmware soft brick, you can't boot HOME Menu or maybe experience some hiccups launching certain titles like if you had a bad system update that unintentionally produced franken firmware. No worries, because you can still boot GodMode9 or Decrypt9WIP (as last resort) to repair the firmware with Restore SysNAND (Safe) and/or CTRTransfer.
Two scenarios where one might want to use forced/full is:
- You want to downgrade the custom firmware from boot9strap back to arm9loaderhax for a very niche game mod that doesn't work in modern CFW.
- Before the time of NTRboot and seed/steel/frog/fredminers, you performed a firmware 2.1.0 downgrade on a n3DS or n3DSXL in a failed custom firmware install. A hack job using o3DS/o2DS NCSD header from that downgrade is causing your system not to correctly boot to HOME Menu. This is something CTRTransfer in neither GodMode9 or Decrypt9WIP can fix, but a forced SysNAND restore will (if you kept a backup).
What are FIRM0 and FIRM1? I'm not entirely sure what these are, but FIRM0 is where boot9strap or fastboot3ds is installed on and is the default FIRM the 3DS first boots. FIRM1 is a backup in case FIRM0 fails to load. The invention of having two FIRMs stems from shortcomings from the days where Gateway bricks were considered unrecoverable or "fatal".
Edit - There are those who flash FIRM1 because they live dangerously.
Last edited by TurdPooCharger,
- Joined
- Jul 23, 2018
- Messages
- 6,051
- Trophies
- 1
- Age
- 29
- Location
- Lampukistan
- Website
- hmpg.net
- XP
- 6,163
- Country
Btw...i created a nand backup with godmode9 before i modded my console completely. Can i restore that backup with fastboot3ds if i brick my console`?
Yes. All(?) of d0k3's works are cross compatible for SysNAND Restore between GodMode9 (and derivatives see: https://d0k3.secretalgorithm.com/) and fastboot3ds.
Is there a site with bot that auto builds new versions of this one ?
I see the last stable was 1.2 on 23rd January 2019 but look's like the latest build 325e74e was April 2nd 2019
I'm not in a position to build myself, but have seen sites for other works where builds can be found
Currently still using B9S but fancy giving this a go to see how it is
I see the last stable was 1.2 on 23rd January 2019 but look's like the latest build 325e74e was April 2nd 2019
I'm not in a position to build myself, but have seen sites for other works where builds can be found
Currently still using B9S but fancy giving this a go to see how it is
- Joined
- Jul 23, 2018
- Messages
- 6,051
- Trophies
- 1
- Age
- 29
- Location
- Lampukistan
- Website
- hmpg.net
- XP
- 6,163
- Country
There's no build bot that I know of at the moment. We're willing to do a new release though, if a few people are willing to test.
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
@
Xdqwerty:
@realtimesave, hey there buddy chum pal friend buddy pal chum bud friend fella bruther amigo pal buddy friend chummy chum chum pal -
@
Xdqwerty:
@realtimesave, hey there buddy chum pal friend buddy pal chum bud friend fella bruther amigo pal buddy friend chummy chum chum pal
-
-
-
-
-
-
-
-
-
-
-
@
Sicklyboy:
@Xdqwerty, Osu! Tatakae! Ouendan! is the Japanese version of the game, different settings/characters/songs but otherwise identical mechanics. I played that before I knew about Elite Beat Agents lol. Both fantastic games https://en.wikipedia.org/wiki/Osu!_Tatakae!_Ouendan+1 -
-
-
