I noticed there's no one talking about this, so I'll talk about it! You can actually install Luma3DS directly to your FIRM0, replacing B9S with Luma3DS! This is not recommended for newbies and neither I nor the Luma3DS team are responsible for any possible damages that may happen.

Requirements

A 3DS running B9S or Fastboot3DS
Luma3DS
GodMode9
Your favorite beverage of choice.

Installation Process

Assuming you've already followed The Guide and you are already running the latest version of Luma3DS, I will just start what you need to do to get Luma3DS installed as your FIRM0. Please excuse the mess on my SD/CTRNAND, these screenshots were taken on Goat
1: Boot into GodMode9 either using Luma3DS or Fastboot3DS
2: Navigate to where you have your "boot.firm" store.

[0:] SDCARD (name of SD): boot.firm

[1:] SYSNAND CTRNAND: boot.firm

3: Press A on the "boot.firm"
4: Press A on the "FIRM image options..."

5: Navigate down to "Install FIRM" and press A

6: Press A on "Install to FIRM0" and follow the key prompt it should say "Install success (<A> to continue)

7: Reboot system, you now have Luma3DS installed as your FIRM0
8: Enjoy your beverage

F.A.Q.

Q: Why would I want to do this?
A: It cuts out a middleman exploit like B9S and boots directly into Luma3DS. If that's something that sounds beneficial to you, then give it a try.
Q: How can I update this setup?
A: Download the latest version of Luma3DS and follow through the Guide again. There's really not easy method setup for this as of writing this guide.
Q: What if another update like 11.8 happens? Can I fix that?
A: If another update like 11.8 happens, you can fix it by just following the same steps above. Luma3DS boots long before the NAND is even mounted, so you can still boot into your B9S payloads through Luma3DS.
Q: Can I still dump my boot9/boot11?
A: No, you will either need to reinstall B9S/Fastboot3DS to dump them or dump them before following this guide.
Q: How can I revert back B9S/Fastboot3DS?
A: Reinstalling B9S
Reinstalling Fastboot3DS. It's worth noting that the same process used to install Luma3DS can be used to reinstall Fastboot3DS.

 

[The Catboy]

This: https://github.com/SciresM/boot9strap
The payload they run from FIRM0 if they follow the guide.
Maybe we should update the guide for LUMA or GM9.

Also about homebrews: [They pollute the SD](https://redd.it/84lpyl).

My guide is focused on running Luma3DS from FIRM0, there's no reason include other payloads because that wasn't the point of this thread. I made this thread because a few people were interested in this process and wanted to know how do it. I can make more guides if people are interested in them, I work on requests not on personal interests. I don't divert from the intentional requests because that's simply not how I roll.

You do realize that you can move the Luma folder from your SD card to your CTRNAND by using GM9, right? Like you don't have to clutter your SD card if you don't want to. That being said, your issue does not relate to my guide and it's completely off topic.

 

[SirNapkin1334]

Cool, but who would want to do this? FB3DS / GM9 are far better.

 

[bendevnull]

I am not sure what this actually has to do with my thread. Would you like me to cover GM9 bootloader? Because I am not going to lie, GM9 bootloader is amazing.

I'd be interested in this. I had no idea GM9 even had a bootloader!

 

[SirNapkin1334]

I'd be interested in this. I had no idea GM9 even had a bootloader!

Yeah. I used it for a long time before d0k3 convinced me to switch over to fb3DS haha. Just do what you do here, but instead install GM9 to firm0/1. But you should really use fb3DS - it has basically all of the features of GM9 and more.

 

[The Catboy]

Cool, but who would want to do this? FB3DS / GM9 are far better.

As I said in the OP

It cuts out a middleman exploit like B9S and boots directly into Luma3DS. If that's something that sounds beneficial to you, then give it a try.

I really don't have nor know who's the target demagogic for this guide, maybe tinkers like me? I thought it was pretty cool when I first installed Luma3DS to my FIRM0 and played around with it. Whenever I test payloads/CFWs, I actually do test them all on B9S, Fastboot3DS, GM9, and Luma3DS to make sure they work on every method of FIRM0 booting.

I'd be interested in this. I had no idea GM9 even had a bootloader!

It's literally the same process as installing Luma3DS to the FIRM0. I personally ran SaltMode9 (GM9 bootloader, but it used the start button to disable autoboot and also didn't have a bootsplash,) before switching to FB3DS. I could make a brief write up about it since there are some differences in how the bootloader looks and operates verse how GM9 normally functions.

 

[trashfloozy]

Ey, nice! I actually honestly think this is pretty neat. Always nice to see new stuff 'round here

 

[Sayora]

Here's an alternate method using fastboot only without godmode9.
1. Enter the fastboot menu and go to miscellaneous then credits.
2. From there enter the konami code (up up down down left right left right b a).
3. You'll then be able to access the previously locked force restore nand and flash to firm1
4. Then go to nand tools then flash firmware to firm1.
5. Then select your firm file and press a and left to flash it.
6. Profit???
Also if you want to disable developer features you have to open the fastboot config in a text editor and change the line DEV_MODE = Enabled to DEV_MODE = Disabled. Or you could just delete the line.
Also if someone feels like testing this, if you were to install a firm file to it that doesn't work are you permanently bricked?

 

[The Catboy]

Here's an alternate method using fastboot only without godmode9.
1. Enter the fastboot menu and go to miscellaneous then credits.
2. From there enter the konami code (up up down down left right left right b a).
3. You'll then be able to access the previously locked force restore nand and flash to firm1
4. Then go to nand tools then flash firmware to firm1.
5. Then select your firm file and press a and left to flash it.
6. Profit???
Also if you want to disable developer features you have to open the fastboot config in a text editor and change the line DEV_MODE = Enabled to DEV_MODE = Disabled. Or you could just delete the line.
Also if someone feels like testing this, if you were to install a firm file to it that doesn't work are you permanently bricked?

I actually have this setup on my 3DS right now. I was testing different homebrews/CFW booting from FIRM1 and just left Luma3DS there because I just couldn't be bothered to change it. I still continue to update and run Luma3DS from my FIRM1 whenever I decide to mess around with Luma3DS.

 

[Sayora]

But if you were to flash one that doesn't work or doesn't have a bootloader, is there any way to recover?

 

[Ryccardo]

But if you were to flash one that doesn't work or doesn't have a bootloader, is there any way to recover?

ntrboot (or hardmod backup restores), of course

 

[ry755]

I actually have this setup on my 3DS right now. I was testing different homebrews/CFW booting from FIRM1 and just left Luma3DS there because I just couldn't be bothered to change it. I still continue to update and run Luma3DS from my FIRM1 whenever I decide to mess around with Luma3DS.

How does the 3DS know which FIRM to boot to? Does it just automatically boot FIRM1 if FIRM0 fails, or is there a way to choose which to boot from?

 

[The Catboy]

How does the 3DS know which FIRM to boot to? Does it just automatically boot FIRM1 if FIRM0 fails, or is there a way to choose which to boot from?

By default the system boots FIRM0 first and FIRM1 if FIRM0 fails to boot. The only way to get to system to boot into FIRM1 is to trigger another bootloader to boot through FIRM0 then 1. Or corrupt the FIRM0 to force the system to boot into FIRM1, which is not suggested (nor do I know how to do this/willing to test this.)
With my setup FB3DS is installed to the FIRM0 and then that is used to trigger FIRM1 boot to Luma3DS.

 

[Sayora]

Wait, so what is normally in firm1 is fastboot is in firm0? I had previously thought flashing things to firm1 replaced fastboot.

 

[The Catboy]

Wait, so what is normally in firm1 is fastboot is in firm0? I had previously thought flashing things to firm1 replaced fastboot.

Normally Fastboot3DS/B9S/GM9 are installed to both FIRM0 and FIRM1 to make sure the system can boot into their respective exploits in case the FIRM0 gets corrupted. Flashing anything to the FIRM1 only replaces that exploit for FIRM1, but the system can still boot another exploit through FIRM0. So right now for example my system is running FB3DS through FIRM0 and Luma3DS through FIRM1. If for some reason my FIRM0 gets corrupted, it would actually boot into Luma3DS off the FIRM1 instead of Fastboot3DS because Luma3DS has replaced Fastboot3DS that was on the FIRM1 before.

 

[Ryccardo]

Or corrupt the FIRM0 to force the system to boot into FIRM1, which is not suggested (nor do I know how to do this/willing to test this.)

GM9 has an hex editor and kernels must be signed, nuff said

(Each kernel partition - up to 8 ! - can also have a boot priority number set; but normally both are equal (0), and therefore they are tried in partition order

 

[The Catboy]

GM9 has an hex editor and kernels must be signed, nuff said

(Each kernel partition - up to 8 ! - can also have a boot priority number set; but normally both are equal (0), and therefore they are tried in partition order

Interesting, maybe I will corrupt my FIRM0 on my testing system later.

 

[Sayora]

Ah, that makes this seem a whole lot safer than what I originally thought. I'd imagine corrupted firm0 can also be fixed via ntrboot?

 

[Ryccardo]

Ah, that makes this seem a whole lot safer than what I originally thought. I'd imagine corrupted firm0 can also be fixed via ntrboot?

Yeah, just run GM9 and restore a backup or directly install a new kernel (or keep booting from a DS card forever, or use probably any other .firm installing homebrew, or....... )

 

[The Catboy]

Ah, that makes this seem a whole lot safer than what I originally thought. I'd imagine corrupted firm0 can also be fixed via ntrboot?

The only thing NTRBoot can't fix is an MCU brick.

 

[Sayora]

What's an mcu brick? Is there any other way to fix it?
Also kind of unrelated side note, but if you were to force restore a nand backup from another system that would still be fixable right? Just to be sure.