Just a quick guide for people who may be having trouble with getting Gateway to work with A9LH V2 after following Plailect's Guide.

I posted this in another thread and has helped a few people, so thought I would post it here for others to see and hope it helps somebody else too.

Download BootCTR from here: https://github.com/hartmannaf/BootCtr9/releases/tag/v0.4.1-alpha_

And put all the files onto the root of your SD card.

Replace the text in the boot_config.ini with the text in the below spoiler.

Spoiler: boot_config.ini

;Comments starts with ";" or "#", so you need to remove it first to the
;line actually do something.
[BOOTCTR9]
screenEnabled = 1
screenLog = 0
fileLog = 0
key_delay = 1000
boot_splash = 3
boot_splash_image = /arm9loaderhax/image2.bin
screenBrightness = 0xFF

[DEFAULT]
path = /GW.bin
delay = 100
offset = 0
payload = -1
splash = 1

[KEY_L]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
splash = 1

[KEY_R]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
screenEnabled = 1
splash = 1

[KEY_SELECT]
path = /Luma.bin
delay = 1000
offset = 0
payload = -1
screenEnabled = 1
splash = 1

[KEY_X]
path = /Uncart.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

[KEY_Y]
path = /Emunand9.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

[KEY_START]
path = /Hourglass.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1


;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


;Boot examples for almost every CFW out there.
;You can use both .3dsx files or binary (.bin, .dat) payloads
;[KEY_A]
;path = /rxTools/sys/code.bin
;[KEY_B]
;path = /Cakes.dat
;[KEY_X]
;path = /3ds/GW/GW.3dsx
;[KEY_Y]
;path = /ReiNand.dat

;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.

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 and put you on OFW, so be careful.

 

[MelodySongz]

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.

It's also found on the main page's website.

Thank you.

Do you have a9lh installed already? Their arm9loaderhax.bin (gw.bin) will not work otherwise.

Yes, I have a9lh installed and recently updated to v2. I got the arm9loaderhax.bin. Thanks for the clarification.

 

[noctis90210]

Yeah, I just did a quick edit and have mine like this but keeping R and L free:


[DEFAULT]
path = /Luma.bin
delay = 100
offset = 0
payload = -1
splash = 1

[KEY_DDOWN]
path = /GW.bin
delay = 1000
offset = 0
payload = -1
splash = 1

[KEY_X]
path = /Uncart.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

[KEY_Y]
path = /Emunand9.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

[KEY_START]
path = /Hourglass.bin
delay = 1000
offset = 0
payload = 1
splash = 3
screenEnabled = 1

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.



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.

With these settings, which L and R and settings buttons are free... It means it will boot luma as same as using the original luma a9lh?

 

[retrofan_k]

With these settings, which L and R and settings buttons are free... It means it will boot luma as same as using the original luma a9lh?

L & R are not used in that config, as they are omitted from it, as you can see. The original config by the OP boots GW by default, I just changed it so Luma defaults instead and removed L & R and you can alter it in anyway you want yourself.

 

[Temptress Cerise]

L & R are not used in that config, as they are omitted from it, as you can see. The original config by the OP boots GW by default, I just changed it so Luma defaults instead and removed L & R and you can alter it in anyway you want yourself.

And to add to this, you don't have to have your a9lh.bin payloads on the root of your SD card. You could throw them into a payloads folder, or any folder for that matter, so long as you tell BootCtr9 where it is.

 

[retrofan_k]

And to add to this, you don't have to have your a9lb.bin payloads on the root of your SD card. You could throw them into a payloads folder, or any folder for that matter, so long as you tell BootCtr9 where it is.

Strange that D9 and Godmode would only boot from the luma/payloads folder and not from the root of the sd card, even though I told Ctr where to search them from and made sure they were on the root.

Still haven't figured out why those particular ones caused an error??

 

[Temptress Cerise]

Strange that D9 and Godmode would only boot from the luma/payloads folder and not from the root of the sd card, even though I told Ctr where to search them from and made sure they were on the root.

Still haven't figured out why those particular ones caused an error??

Odd. Did you have the / in front? Anyways. I don't have mine on the root. That's terribly messy and annoys me to no end. I have mine inside /k9lh/payloads I also have CtrBootManager9 on my BootCtr9 config, so when I want to look at a GUI menu for my payloads.

 

[retrofan_k]

Odd. Did you have the / in front? Anyways. I don't have mine on the root. That's terribly messy and annoys me to no end. I have mine inside /k9lh/payloads I also have CtrBootManager9 on my BootCtr9 config, so when I want to look at a GUI menu for my payloads.

For example I had Decrypt9 labeled as "D9.bin" on the root and told Ctr that it was [KEY_X] path = /D9.bin, yet holding X on boot, threw an error and the system would shutdown. So i tested it with the other buttons and the same results but if I put say, Safe9installer on X, that would work and so a few others.

 

[Temptress Cerise]

For example I had Decrypt9 labeled as "D9.bin" on the root and told Ctr that it was [KEY_X] path = /D9.bin, yet holding X on boot, threw an error and the system would shutdown. So i tested it with the other buttons and the same results but if I put say, Safe9installer on X, that would work and so a few others.

Just tested this. Works fine on my end on root. However, I am using the latest released dev build, that was posted in the ARM9Loader Discussion thread.
Link: https://gbatemp.net/threads/arm9loader-technical-details-and-discussion.408537/page-200#post-6373015

My config.

[BOOTCTR9]
screenEnabled = 1
screenLog = 0
fileLog = 0
key_delay = 1000
boot_splash = 1
boot_splash_image = /k9lh/images/ctrbootmgr9_top.bin
screenBrightness = 0xFF
enableAutosoftboot = 0
enableSoftbootSplash = 0

;BootAnim9 into Corbenik <3
[DEFAULT]
path = /k9lh/payloads/BootAnim9.bin
delay = 200
offset = 0
payload = -1
screenBrightness = 0xFF
enableSoftbootSplash = 0

;CtrBootManager9 for Recovery Payloads + Luma3DS
[KEY_DUP]
path = /k9lh/payloads/CtrBootManager9.bin
delay = 200
offset = 0
payload = -1
screenEnabled = 1
screenBrightness = 0xFF

;BrickWait Mode
[KEY_DDOWN]
path = /k9lh/payloads/GW9.bin
delay = 200
offset = 0
payload = -1
screenEnabled = 1
screenBrightness = 0xFF

;Decrypt9WIP test on Key X
[KEY_X]
path = /D9.bin
delay = 200
offset = 0
payload = -1
screenEnabled = 1
screenBrightness = 0xFF

 

[retrofan_k]

lol @ brickwait mode.

 

[noctis90210]

@retrofan_k just want to ask, im using no init a9lh, but using bootctr9, the backlight still blinks upon boot?
any tips to turn it off?

 

[Temptress Cerise]

@retrofan_k just want to ask, im using no init a9lh, but using bootctr9, the backlight still blinks upon boot?
any tips to turn it off?

Set "screenEnabled = 1" to "screenEnabled = 0" and see if that works. Otherwise, no clue. As it does do it's own screen-initialization for payloads that do need it. Especially GW, which needs it.

 

[noctis90210]

Set "screenEnabled = 1" to "screenEnabled = 0" and see if that works. Otherwise, no clue. As it does do it's own screen-initialization for payloads that do need it. Especially GW, which needs it.

still with backlight blink upon boot...

set screenBacklight = 0
still with baclught blink upon boot...
:-(

 

[Temptress Cerise]

still with backlight blink upon boot...

I don't know, could look over the documentation for BootCTR9.
Link: https://github.com/hartmannaf/BootCtr9

Can't help you really. I use non-screen-init, but I actually just use BootAnim9 at boot, so it doesn't bother me one bit.

 

[retrofan_k]

@noctis90210 I use screen-init a9lh and have the brightness @ 1x, so not really looked into that. I only tested the non-screen version to see if it worked.

 

[CraddaPoosta]

Everything I have seen says that if you use BootCTR, you can no longer play GBA or DSiWare games because of how much RAM the boot manager requires. That's not worth it for me to have Gateway mode.

 

[Temptress Cerise]

Everything I have seen says that if you use BootCTR, you can no longer play GBA or DSiWare games because of how much RAM the boot manager requires. That's not worth it for me to have Gateway mode.

What? Where did you hear that? You should still be able to play GBA, DSiWare and games like Super Smash Bros. on Luma3DS while using BootCTR9. I am not sure about GW Mode, as we need a CFW that has reboot patches on o3DS. But on N3DS you really shouldn't have this problem in GW mode.

 

[TheBroCode]

Everything I have seen says that if you use BootCTR, you can no longer play GBA or DSiWare games because of how much RAM the boot manager requires. That's not worth it for me to have Gateway mode.

You just need to follow this extra step at the bottom of https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-Upgrade

then you can play GBA/DSi on Luma

 

[CraddaPoosta]

But if I can't even get the GW.3dsx file to boot from the HBL or from any other method, is there something I missed along the way? So far, nothing I've tried has given me anything but a black screen.

I've tried both GW 3.71 and 4.0b2. I've tried replacing the armloader9hax.bin completely, tried renaming the GW payload to down_GW.bin and placing it in the Luma payloads folder, tried using the go-gateway-3ds.com site; nothing even lets me see the Gateway splash. No clue what I am doing wrong.

 

[Temptress Cerise]

But if I can't even get the GW.3dsx file to boot from the HBL or from any other method, is there something I missed along the way? So far, nothing I've tried has given me anything but a black screen.

I've tried both GW 3.71 and 4.0b2. I've tried replacing the armloader9hax.bin completely, tried renaming the GW payload to down_GW.bin and placing it in the Luma payloads folder, tried using the go-gateway-3ds.com site; nothing even lets me see the Gateway splash. No clue what I am doing wrong.

I'll assume you are on v2 A9LH. In which case, you have to use BootCTR9 as this guide describes.

Now if you don't want to use BootCTR9, and you want to use Luma3DS' chainloader for this, then you have to downgrade to v1 A9LH, or use a compatible v2 A9LH build.
For a compatible v2 A9LH build, you have to compile it yourself.
Link: https://gbatemp.net/threads/safea9lhinstaller.419577/page-29#post-6432075

As for downgrading, your on your own for that.

 

[retrofan_k]

But if I can't even get the GW.3dsx file to boot from the HBL or from any other method, is there something I missed along the way? So far, nothing I've tried has given me anything but a black screen.

I've tried both GW 3.71 and 4.0b2. I've tried replacing the armloader9hax.bin completely, tried renaming the GW payload to down_GW.bin and placing it in the Luma payloads folder, tried using the go-gateway-3ds.com site; nothing even lets me see the Gateway splash. No clue what I am doing wrong.

Both of Gw's launcher.dat work when placed on the root using a 11.0 Luma sysnand i.e a cloned updated emunand to sysnand. Do you have a rednand/emunand setup, as there are supposedly problems using a emunand from what I saw, yet I never used a emunand on my setup because it's not needed really.

If you want to downgrade to V1, flash the SysNand_Original.bin without keeping A9lh via Decrypt9 and start from there, since you have the OTP to do a V1 install. Use V1 (Data_input & Payload_input) files with Safea9lhinstaller 1.52.

Imo, it is better do that above than actually uninstalling V2 and then installing V1 files.