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.

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

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,
I'm surprised still no one made this.

Here's a file that should (if it works, and though I'd say it does, don't hold me responsible if you brick by using this) load the Gateway a9lh file named "gateway.bin" in /luma/payloads/.
So just call that something like "down_v2gw.bin" or something, then put it in /luma/payloads/, put GW's a9lh file in /luma/payloads/ too and name it "gateway.bin" and you should be able to run GW with Luma by holding down at boot without having to use another boot manager.

I only tested this on my 2DS though, and I only tested normal boot (I didn't try to go to System Settings or booting a GBA game and stuff).
 

Attachments

Last edited by Hayleia,
I'm surprised still no one made this.

Here's a file that should (if it works, and though I'd say it does, don't hold me responsible if you brick by using this) load the Gateway a9lh file named "gateway.bin" in /luma/payloads/.
So just call that something like "down_v2gw.bin" or something, then put it in /luma/payloads/, put GW's a9lh file in /luma/payloads/ too and name it "gateway.bin" and you should be able to run GW with Luma by holding down at boot without having to use another boot manager.

I only tested this on my 2DS though, and I only tested normal boot (I didn't try to go to System Settings or booting a GBA game and stuff).
Wait, wait, a second. Someone made a compatible v2 GW a9lh.bin?
 
Wait, wait, a second. Someone made a compatible v2 GW a9lh.bin?
Erm, if you're talking about me, then no :P
I made a very stripped down boot manager that only loads /luma/payloads/gateway.bin (so you still need GW's bin). But it should run it correctly and doesn't need any configuration file.
So if you put it in /luma/payloads/ with the name you want, you should be able to run Gateway without any hassle (if it works as intended).
 
  • Like
Reactions: leonmagnus99
Erm, if you're talking about me, then no :P
I made a very stripped down boot manager that only loads /luma/payloads/gateway.bin (so you still need GW's bin). But it should run it correctly and doesn't need any configuration file.
So if you put it in /luma/payloads/ with the name you want, you should be able to run Gateway without any hassle (if it works as intended).
OHH! I misread your post, as I am replying and all over the place. Being a dumby right now. But I see what it does now. I'll test it in a bit then.
 
  • Like
Reactions: Hayleia
I'm surprised still no one made this.

Here's a file that should (if it works, and though I'd say it does, don't hold me responsible if you brick by using this) load the Gateway a9lh file named "gateway.bin" in /luma/payloads/.
So just call that something like "down_v2gw.bin" or something, then put it in /luma/payloads/, put GW's a9lh file in /luma/payloads/ too and name it "gateway.bin" and you should be able to run GW with Luma by holding down at boot without having to use another boot manager.

I only tested this on my 2DS though, and I only tested normal boot (I didn't try to go to System Settings or booting a GBA game and stuff).

It works~! Used an N3DS with Luma3DS with v2 A9LH (Set this up today ^_^), and did as instructed. So in my case I held DPAD-Down, and it booted GW Mode. I launched a romhack of Omega Ruby and everything seems to be working fine. Though I think GBA and the rest of the stuff will still be broken on a SysNAND only setup. Used Launcher.dat 4.0a
 
  • Like
Reactions: Hayleia
It works~! Used an N3DS with Luma3DS with v2 A9LH (Set this up today ^_^), and did as instructed. So in my case I held DPAD-Down, and it booted GW Mode. I launched a romhack of Omega Ruby and everything seems to be working fine. Though I think GBA and the rest of the stuff will still be broken on a SysNAND only setup. Used Launcher.dat 4.0a
Thanks for testing :)
I'd test it on my other setups but I don't have them with me at the moment...
 
I'm surprised still no one made this.

Here's a file that should (if it works, and though I'd say it does, don't hold me responsible if you brick by using this) load the Gateway a9lh file named "gateway.bin" in /luma/payloads/.
So just call that something like "down_v2gw.bin" or something, then put it in /luma/payloads/, put GW's a9lh file in /luma/payloads/ too and name it "gateway.bin" and you should be able to run GW with Luma by holding down at boot without having to use another boot manager.

I only tested this on my 2DS though, and I only tested normal boot (I didn't try to go to System Settings or booting a GBA game and stuff).

I am a bit confused. So, this file is still named armloader9hax.bin. Do I use this to replace the one I currently have on the root of my SD card? I already renamed the Gateway one I downloaded directly from their site to Down_GW.bin and that is in the Luma/payloads folder.

I have to be missing some simple step here.
 
I am a bit confused. So, this file is still named armloader9hax.bin. Do I use this to replace the one I currently have on the root of my SD card? I already renamed the Gateway one I downloaded directly from their site to Down_GW.bin and that is in the Luma/payloads folder.

I have to be missing some simple step here.
You rename Hayleia's a9lh.bin file to something like "down_v2gw.bin" and put it inside the /luma/payloads/ folder.
You then take your GW a9lh.bin file, and rename it to gateway.bin.

From my understanding, Hayleia's a9lh.bin file is a stripped down boot manager that loads only loads /luma/payloads/gateway.bin - It won't do anything else if doesn't find this file.

It probably has the necessary patches to initialize GW's A9LH.bin payload, which BootCTR9 is able to do correctly.
 
  • Like
Reactions: CraddaPoosta
Where do I put the Gateway.bin? The root of my SD? That must be the step I've been missing.|

EDIT: Nevermind. It was supposed to go into the Luma/payloads folder.

Folks, this method WORKS! It's the first thing that has actually done the trick, and the only method I have seen outside of BootCTR that does it.

THANK YOU!
 
Last edited by CraddaPoosta,
Where do I put the Gateway.bin? The root of my SD? That must be the step I've been missing.
I'm sorry. I thought I was being clear. You must place it in the /luma/payloads/ - Hayleia explained this in his//her original post. I am just rephrasing what he//she said.

I'm surprised still no one made this.

Here's a file that should (if it works, and though I'd say it does, don't hold me responsible if you brick by using this) load the Gateway a9lh file named "gateway.bin" in /luma/payloads/.
So just call that something like "down_v2gw.bin" or something, then put it in /luma/payloads/, put GW's a9lh file in /luma/payloads/ too and name it "gateway.bin" and you should be able to run GW with Luma by holding down at boot without having to use another boot manager.

I only tested this on my 2DS though, and I only tested normal boot (I didn't try to go to System Settings or booting a GBA game and stuff).
 
  • Like
Reactions: CraddaPoosta
  • Like
Reactions: WiiHoney
I'm surprised still no one made this.

Here's a file that should (if it works, and though I'd say it does, don't hold me responsible if you brick by using this) load the Gateway a9lh file named "gateway.bin" in /luma/payloads/.
So just call that something like "down_v2gw.bin" or something, then put it in /luma/payloads/, put GW's a9lh file in /luma/payloads/ too and name it "gateway.bin" and you should be able to run GW with Luma by holding down at boot without having to use another boot manager.

I only tested this on my 2DS though, and I only tested normal boot (I didn't try to go to System Settings or booting a GBA game and stuff).

many thanks, this is perfect!
 
  • Like
Reactions: Hayleia
I'm surprised still no one made this.

Here's a file that should (if it works, and though I'd say it does, don't hold me responsible if you brick by using this) load the Gateway a9lh file named "gateway.bin" in /luma/payloads/.
So just call that something like "down_v2gw.bin" or something, then put it in /luma/payloads/, put GW's a9lh file in /luma/payloads/ too and name it "gateway.bin" and you should be able to run GW with Luma by holding down at boot without having to use another boot manager.

I only tested this on my 2DS though, and I only tested normal boot (I didn't try to go to System Settings or booting a GBA game and stuff).
It works like a charm(tested on N3DS/O3DS). I was sticking with A9LH v1 because personally I preferred using Luma3DS' built-in bootloader, so this motivated me to finally update to A9LH v2. Thank you for making this.
 
Last edited by Emenaria,
Anyone know where I can find the 2.1.0J(Full).zip file? its not on that iso site, and I cant find it anywhere, if someone could PM me that would be great :)
 
Hi Is there a way to set the L option to not have any effect? Or to have L be the same as a normal Boot into luma sys? so either w/ or w/o the L I can still get into normal LumaSysnand?
 

Site & Scene News

Popular threads in this forum