;Each key can be defined using a section, like the example below. Section
;names must be ALL caps, and between "[]". Valid keys:
; * Common keys: KEY_A, KEY_B, KEY_X, KEY_Y, KEY_L, KEY_R, KEY_SELECT,
; KEY_START.
; * D-PAD: KEY_DUP, KEY_DDOWN, KEY_DLEFT, KEY_DRIGHT.
;You MUST set at least "path" for each section, and it is the ONLY option you
;should set in the majority of cases.
;You may pass a .3dsx file or a .dat/.bin payload, the file type is detect
;automatically based on extension. Double check the path, since it must be
;correct (including caps).
;[KEY_CPAD_LEFT] ;MUST BE ALL CAPS
;path = /And/Respect_Caps_in_Path.3dsx

;An important remark: the majority of CFWs set L button to show menu instead
;of autobooting. So it is generally a bad idea to set L button to CFW boot,
;or the CFW menu will be shown instead of booting directly to CFW.
;[KEY_L]

Put the Gateway payload on the root of the SD and name it "GW.bin"

Put the Luma payload on the root of the SD and name it "Luma.bin"

Put the Uncart payload on the root of the SD and name it "Uncart.bin"

Put the Emunand9 payload on the root of the SD and name it "Emunand9.bin"

Put the Hourglass9 payload on the root of the SD and name it "Hourglass.bin"

Links to these files will have been provided with Plailect's guide and the files will already be in the Luma folder if you followed that guide properly.

It works for me. Might not be for you, but will allow you to boot gateway by default and Luma with L or R for when you want to update the sysnand firmware and you can still access Luma settings with select should you need it.

Also, make sure the gateway LAUNCHER.DAT is on the root of the SD card too.

Like to add that this is good for a quick and simple way of getting GW to work on V2 a9lh instead of downgrading from V2 to V1, because at present there is no real reason to have the need to downgrade,

Once a9lh is installed, it is advisable to not tinker with it unless you know exactly what you are doing and have proper NAND recoveries, such as a "hard mod"

So, if I wanted to boot to Luma by default, with the ability to boot into Gateway Mode by holding R, I would just replace each of those .bin file names under DEFAULT, KEY_L and KEY_R?

Click to expand...

Yeah pretty much. I had it setup like this as I wanted a way to just use gateway as default as I am more likely to use my Gateway card than to use a retail cart and to still have the option to use Luma for anything else.

Gateway, HG, uncart, E9 are booting normally, but Luma R/L just stays on black screen (and the payload is not showing it bootmanager). However, it boots normally if I enter settings (select) first.
What could’ve gone wrong?
Moreover, NAND things like enjected FBI are not working in GW and when I booted back into Luma, they transformed into black squares. If I boot into GW, they are just not there anymore.

With that above, I boot Luma by default and have GW booting by pressing Down on the D-pad on boot and using L when booting GW, displays the GW menu as normal. The only thing I have noticed, is that trying to chainload other payloads like Decrypt9, Godmode9, etc, BootCTR throws an error, if you are using shortcuts like KEY_DLEFT, KEY_DRIGHT, so I kept those out the config.

Maybe it has to do with booting Luma by default, I dunno? but if you put those payloads like I mentioned in Luma's payload folder named "left_decrypt9"" and "right_godmode9" they work fine from a cold boot but not with BootCtr's config. Need to look into that more, yet this works great so far for my needs.

Gateway, HG, uncart, E9 are booting normally, but Luma R/L just stays on black screen (and the payload is not showing it bootmanager). However, it boots normally if I enter settings (select) first.
What could’ve gone wrong?
Moreover, NAND things like enjected FBI are not working in GW and when I booted back into Luma, they transformed into black squares. If I boot into GW, they are just not there anymore.

Click to expand...

FBI works fine here in Luma. On mine I get the "health & safety" icon in GW but it throws an error, if you try and load it, which is normal.

Try my simple edit above for defaulting into Luma and using "down" to boot into GW.

PLEASE NOTE: Do not update while in GW sysnand, as it does not have Firm protections like Luma does, so updating in GW mode will remove a9lh or brick on O3DS and brick a N3DS, which will put you on OFW if you do not brick, so be careful.

;Each key can be defined using a section, like the example below. Section
;names must be ALL caps, and between "[]". Valid keys:
; * Common keys: KEY_A, KEY_B, KEY_X, KEY_Y, KEY_L, KEY_R, KEY_SELECT,
; KEY_START.
; * D-PAD: KEY_DUP, KEY_DDOWN, KEY_DLEFT, KEY_DRIGHT.
;You MUST set at least "path" for each section, and it is the ONLY option you
;should set in the majority of cases.
;You may pass a .3dsx file or a .dat/.bin payload, the file type is detect
;automatically based on extension. Double check the path, since it must be
;correct (including caps).
;[KEY_CPAD_LEFT] ;MUST BE ALL CAPS
;path = /And/Respect_Caps_in_Path.3dsx

;An important remark: the majority of CFWs set L button to show menu instead
;of autobooting. So it is generally a bad idea to set L button to CFW boot,
;or the CFW menu will be shown instead of booting directly to CFW.
;[KEY_L]

Put the Gateway payload on the root of the SD and name it "GW.bin"

Put the Luma payload on the root of the SD and name it "Luma.bin"

Put the Uncart payload on the root of the SD and name it "Uncart.bin"

Put the Emunand9 payload on the root of the SD and name it "Emunand9.bin"

Put the Hourglass9 payload on the root of the SD and name it "Hourglass.bin"

Links to these files will have been provided with Plailect's guide and the files will already be in the Luma folder if you followed that guide properly.

It works for me. Might not be for you, but will allow you to boot gateway by default and Luma with L or R for when you want to update the sysnand firmware and you can still access Luma settings with select should you need it.

Also, make sure the gateway LAUNCHER.DAT is on the root of the SD card too.

Sorry I'm fairly new to all this. I downloaded the firmware .zip file which has the gw launcher.dat, but I don't see any .bin files in that .zip file. Which file am I supposed to rename to gw.bin?

Click to expand...

On the openly public Private Beta Program page, scroll all the way to the bottom. You should see the following section titled "» arm9loaderhax for users with existing a9lh installs" You download either of those two files.

A remake of the PlayStation Portable game Star Ocean: First Departure has been announced. Square Enix will be bringing the game, which sports a new R in its title, westward on both the Nintendo Switch...

Over 20 years have passed since Resident Evil 1 originally hit the scene, innovating the game industry for years to come with its unique blend of survival and horror elements. After getting a visual...

This is not what anyone would imagine a $99 3DS game would look like, or even that such a thing would ever exist at all.
But here it is in broad daylight, a hundred dollar game that's intended to be...