Tutorial Using Gateway on A9LH V2

Cosmic_Link

Well-Known Member
OP
Member
Joined
Jun 9, 2010
Messages
113
Trophies
0
Age
32
XP
1,546
Country
United Kingdom
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,

retrofan_k

Well-Known Member
Member
Joined
May 31, 2013
Messages
2,059
Trophies
1
Location
Caves
XP
2,248
Country
Belarus
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"

--------------------- MERGED ---------------------------

can someone explain me or send a link what's new in a9lh v2?

Bug fix and more space (extra bytes) for future payloads. V1 is perfectly fine, yet this is for those already on V2.
 
Last edited by retrofan_k,
  • Like
Reactions: Maximilious

Neo Draven

End Boss of the Entire Internet
Member
Joined
May 3, 2010
Messages
929
Trophies
0
XP
1,605
Country
United States
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?
 

Logan Pockrus

Knawledge is key.
Member
Joined
Jan 1, 2016
Messages
1,339
Trophies
0
XP
1,041
Country
United States
So, how can you tell if you have A9LH v2? I had no clue there were two versions before reading the OP.

EDIT: I'm a fool. Never mind the question I asked, I found the (obvious) answer.
 
Last edited by Logan Pockrus,

Cosmic_Link

Well-Known Member
OP
Member
Joined
Jun 9, 2010
Messages
113
Trophies
0
Age
32
XP
1,546
Country
United Kingdom
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?

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. ^_^
 

octopus

Custom Title
Member
Joined
Sep 6, 2013
Messages
411
Trophies
0
Location
/
XP
1,145
Country
Somalia
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.
 
Last edited by octopus,

retrofan_k

Well-Known Member
Member
Joined
May 31, 2013
Messages
2,059
Trophies
1
Location
Caves
XP
2,248
Country
Belarus
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?

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.

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.

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.
 
Last edited by retrofan_k,

retrofan_k

Well-Known Member
Member
Joined
May 31, 2013
Messages
2,059
Trophies
1
Location
Caves
XP
2,248
Country
Belarus
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

Member
Newcomer
Joined
May 11, 2016
Messages
7
Trophies
0
XP
24
Country
United States
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:


Where do I get the Gateway payload from?
 

Temptress Cerise

Miss Magic~ <3
Member
Joined
May 1, 2016
Messages
2,239
Trophies
1
Age
29
XP
2,104
Country
United States
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?
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.
 
  • Like
Reactions: cavinrocks

retrofan_k

Well-Known Member
Member
Joined
May 31, 2013
Messages
2,059
Trophies
1
Location
Caves
XP
2,248
Country
Belarus
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?

Do you have a9lh installed already? Their arm9loaderhax.bin (gw.bin) will not work otherwise.
 
Last edited by retrofan_k,
General chit-chat
Help Users
  • No one is chatting at the moment.
    Julie_Pilgrim @ Julie_Pilgrim: i use it when i want to post multiple images to reddit