Tutorial
Updated
Using Gateway on A9LH V2
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.
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.
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.
;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]
;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.
Last edited by Cosmic_Link,