SYSNAND-ONLY USERS: DO NOT BOOT GW MODE ON 11.3+ - YOU WILL LOSE B9S AND BE LEFT ON A STOCK FIRMWARE
I highly advise against the use of GW on SysNAND-Only Setups.
GW currently DOES NOT support firmwares 11.3//11.4 - B9S does not change that!
If you're on 11.3+ - Don't even try to use GW. Use Luma3DS or any other CFW that has confirmed support for 11.3+ firmwares.

Setting up GW with Luma3DS' chainloader

Requirements: SysNAND or EmuNAND on 11.2 or lower!
Tested and working on B9S 1.2 (Luma3DS 8.0)

1. Download the v2gw.zip attached to this post.
2. Extract the "arm9loaderhax.bin" from v2gw.zip to your /luma/payloads/ folder.
3. Rename that very "arm9loaderhax.bin" you just extracted to "v2gw.bin" or to whatever you want. However, step 12 will assume v2gw.bin was used, you can edit that reference to meet whatever you decided to name it.
4. Download GW's ‘arm9loaderhax.bin.zip‘ file.
   • On their main home page. Under the post titled: "GATEWAY 4.0B PRIVATE BETA #2"
   • Or on their openly public Private Beta Program page, on this page it'll be under the "» arm9loaderhax for users with existing a9lh installs" section.
5. Extract GW's "arm9loaderhax.bin" file from their zip file to your /luma/payloads/ folder.
6. Rename that very "arm9loaderhax.bin" you just extracted to "gateway.bin"
7. Make sure you have the latest GW's Launcher.dat on the root of your SD Card.
8. This dev-build of BootCTR9: https://gbatemp.net/threads/release-the-bootctr9-release-thread.435347/page-3#post-7370533
9. Extract the "boot.firm" file from the BootCTR9-firmv2.zip to your /luma/payloads/ folder.
10. Rename that very "boot.firm" you just extracted to "down_BootCTR9.firm" or to whatever you want that is allowed by Luma3DS' payload chainloader.
    - Other button options: https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes#payload-chainloading
11. Extract the "boot_config.ini" file from from the BootCTR9-firmv2.zip to the root of your SD Card.
12. Open the "boot_config.ini" file and overwrite everything with the following:
    

    [BOOTCTR9]
    key_delay = 1000
    
    [DEFAULT]
    path = /luma/payloads/v2gw.bin

13. You are now done. If you followed this tutorial, holding DPAD-DOWN at boot time, will load up Gateway Mode.
    - SysNAND-Only Users on 11.2 will be prompted to press 'L+R+SELECT' to boot SYSNAND. DO NOT PRESS THE BUTTON PROMPT ON 11.3+
    - GW EmuNAND users will automatically boot into their GW EmuNAND.

FAQ

Q: How do I boot into the GW Menu?
A: Hold L+Select, as soon as you see the Dragon Logo.

Q: Can I use my GW Blue Card?
A: Yes, but only while using Luma3DS. It will not work in GW Mode.

Q: Can I play online while in GW Mode?
A: Yes, sort-of. But you have to either:

• Use CTR-HTTPWN: https://github.com/yellows8/ctr-httpwn/releases
• or use this guide

Q: I'm getting a black screen!? HELP!?
A: Multiple reasons for that below:

• Modified SecureInfo_A - GW does not patch this. You'll need an untouched donor file of this.
• Using a RedNAND - GW only supports GW EmuNAND, it cannot boot RedNAND. Use the GW Menu or GodMode9 to make one.
• On SysNAND-Only Setups - Not having properly removed EmuNAND//RedNAND. Use GodMode to properly format your SD Card. But I advise you set one up.
• Trying to boot an 11.3//11.4 EmuNAND - GW does not support anything higher than 11.2
• If it's not listed, then who knows. Do you have a modified Home Menu or font? Those might not work at all in GW Mode.

Credits

• @Hayleia for making v2gw.bin~!
• @RednaxelaNnamtra for BootCTR9~!
• @nedron92 for discovering this method~!

Many thanks to the above lovely people~ <3 ♥
Original posts:
Link: https://gbatemp.net/threads/using-gateway-on-a9lh-v2.431222/page-4#post-6464898
Link: http://gbatemp.net/threads/tutorial-using-luma3ds-with-gateway-on-v2-a9lh.431691/page-4#post-6472283
Link: https://gbatemp.net/threads/tutorial-booting-gw-with-b9s-and-some-help.471417/

Spoiler: Old Guide

I highly advise against the use of GW for SysNAND-Only setups.

11.3&11.4 Break GW. GW currently DOES NOT support 11.3 or 11.4. You will either brick or lose A9LH. More than likely it seems you will just lose A9LH.

Again, if you attempt to boot GW Mode, on a SYSNAND-Only Setup while on 11.3 or 11.4, you will lose A9LH. It does not matter if you safely updated to this firmware via another CFW that safely protects FIRM.

If you want to use 11.3+, you will not be able to use GW. Don't even try. Only use Luma3DS or other CFW that support 11.3+

If you are a Gateway3DS user, and have recently finished Plailect's A9LH Guide, then you should be on v2 A9LH. Unfortunately, at the time this thread was made, GW's a9lh.bin file is incompatible with Luma3DS' payload chainloading feature while on v2 A9LH.

So one way around this was to either forego using Luma3DS' payload chainloading, and use a boot manager that does work in initializing GW's a9lh.bin correctly. Like BootCTR9. Either you let BootCTR9 handle all payloads, or you set it up to chainload into Luma3DS and from there let Luma3DS do all the work.

Either way, some people might not like BootCTR9 (Big fan of BootCTR9, seriously thing is amazing~!)

So if you don't want to use the BootCTR9 method, then @Hayleia made a very stripped down boot manager that only loads /luma/payloads/gateway.bin. You still need GW's a9lh.bin in addition to this stripped down bootmanager, but that's all you need, these two files! No need for messy configs if you just want to stick with Luma3DS' payload chainloader.

Now on to the damn tutorials already~!​

~Choose your path~
Gateway Logo (Recommend for Everyone - SysNAND Only & GW EmuNAND Users)
No Gateway Logo (Not Recommend, especially NOT for SysNAND Only Users - Only for those allergic to the dragon logo - USE AT YOUR OWN RISK)
!~Important Note (DO NOTE UPDATE SYSNAND while in GW MODE)(PLEASE READ)
!~Getting Black Screen After Dragon Logo and After Following This Guide~! (PLEASE READ)
!~I want to use GW as Default~!
!~♥ Credits ♥~!
​

Gateway Logo

1. Download the v2gw.zip attached to this post.
2. Extract the "arm9loaderhax.bin" from v2gw.zip to your /luma/payloads/ folder.
3. Rename that very "arm9loaderhax.bin" you just extracted to "down_v2gw.bin" or to whatever you want that is allowed by Luma3DS' payload chainloader.
Other button options: https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes#payload-chainloading
4. Download GW's ‘arm9loaderhax.bin.zip‘ file.
You have to get this directly from Gateway's site. Which is either:
A) On their main home page.
B) Or on their openly public Private Beta Program page, on this page it'll be under the "» arm9loaderhax for users with existing a9lh installs" section.
5. Extract GW's "arm9loaderhax.bin" file from their zip file to your /luma/payloads/ folder.
6. Rename that very "arm9loaderhax.bin" you just extracted to "gateway.bin"
7. Make sure you have the latest GW's Launcher.dat on the root of your SD Card.
8. You are now done. If you followed this tutorial, holding DPAD-DOWN at boot time, will load up Gateway Mode.
However, if you are a SysNAND Only User, and on 11.1 and using the 4.2 Launcher.dat, you will be prompted to press 'L+R+SELECT' to boot SYSNAND.
GW EmuNAND users will automatically boot into their GW EmuNAND.

Notes: To Boot into the GW Menu: Hold L+Select, as soon as you see the Dragon Logo.
To Force a Manual Gateway3DS RedCard Update: Hold R+Select as soon as you see the Dragon Logo.



No Gateway Logo (Not Recommend - Only for those allergic to the dragon logo - USE AT YOUR OWN RISK)

Notes: This version will de-init the screen by default, and as such you won't see the Gateway Logo. Don't worry it'll init once you land on the Home. Due to how this works, only GW EmuNAND users should consider using this. This is because SysNAND users will land on the SysNAND prompt nag.

1. Download the v2gw-de-init.zip attached to this post.
2. Extract the "v2gw.bin" from v2gw-de-init.zip to your /luma/payloads/ folder.
3. Rename that very "v2gw2.bin" you just extracted to "down_v2gw.bin" or to whatever you want that is allowed by Luma3DS' payload chainloader.
Other button options: https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes#payload-chainloading
4. Download GW's ‘arm9loaderhax.bin.zip‘ file.
You have to get this directly from Gateway's site. Which is either:
A) On their main home page.
B) Or on their openly public Private Beta Program page, on this page it'll be under the "» arm9loaderhax for users with existing a9lh installs" section.
5. Extract GW's "arm9loaderhax.bin" file from their zip file to your /luma/payloads/ folder.
6. Rename that very "arm9loaderhax.bin" you just extracted to "gateway.bin"
7. Make sure you have the latest GW's Launcher.dat on the root of your SD Card.
8. You are now done. If you followed this tutorial, holding DPAD-DOWN at boot time, will load up Gateway Mode without the Gateway Logo.

Tested on N3DS and O3DS by me, 2DS by @Hayleia.
Should work on either screen-init or non-screen-init v2 A9LH.



Important Note: Never update your SysNAND in Gateway Mode. It does not matter what Launcher.dat version you use, if you go ahead and update while in SysNAND Mode, you will either brick or lose A9LH+CFW and be on the latest stock firmware. This is because GW Mode does not offer FIRM protection in A9LH. Updating your GW EmuNAND is fine and safe, and is what Gateway actually recommends you do and use even when using A9LH.



!~Getting Black Screen After Dragon Logo and After Following This Guide~! (PLEASE READ)
Sounds like someone hasn't properly removed their EmuNAND//RedNAND with EmuNAND9. The Black Screen problem is common to people who skipped doing it properly and used a third-party tool like EaseUS or any other partition manager.

Since EmuNAND//RedNAND wasn't removed properly, traces were leftover and GW by default sees it, and tries to boot into this non-existent EmuNAND//RedNAND and fails. So how do we fix it? We use EmuNAND9 to preperly remove traces of it.

Part 5, Section V of the old A9LH guide covers this. However, I will list all relevant steps here.
Link: https://github.com/Plailect/Guide_R...ax)#section-v---removing-rednand-from-your-sd

The new guide also sort of mentions if in this new page, and does show you how to setup EmuNAND9:
Link: https://plailect.github.io/Guide/move-emunand

Files we'll need:
Latest release of EmuNAND9: https://github.com/d0k3/EmuNAND9/releases/latest

1. Copy EmuNAND9.bin from the EmuNAND9.zip to the /luma/payloads/ folder on your SD card and rename EmuNAND9.bin to y_EmuNAND9.bin
2. Backup every file on your SD card to a folder on your computer, all files will be deleted in the following steps
3. Reinsert your SD card into your 3DS
4. Hold (Y) at boot time to open EmuNAND9
5. Go to "SD Format Options...", then select the "Format SD (no EmuNAND)" option, and wait for it to finish
6. Press (B) to return to the menu, then press Select to safely eject your SD Card
7. Put your SD card back into your computer, and copy all the files you backed up previously, back into your SD Card
8. Reinsert your SD card into your 3DS, then press (Start) to reboot



Additional Note: You will still have to look into BootCTR9 if for some reason you want GW to be the default, as opposed to Luma3DS. This tutorial is meant more for the people who want Luma3DS as their main//default, and want to use Luma3DS' payload chainloader to boot into GW Mode.
Go to the following link for the tutorial on setting up GW as your main with BootCTR9.
Link: https://gbatemp.net/threads/using-gateway-on-a9lh-v2.431222/


All credits to @Hayleia for making both of these~! Thank you~ <3 ♥
Original posts:
Link: https://gbatemp.net/threads/using-gateway-on-a9lh-v2.431222/page-4#post-6464898
Link: http://gbatemp.net/threads/tutorial-using-luma3ds-with-gateway-on-v2-a9lh.431691/page-4#post-6472283

 

[tNB]

You don't need an emunand in Luma + a9lh. You can use your previous emunand as your new sysnand, or just scrap it - your choice.

Would rather keep my 9.2 sysNAND intact

Waiting for a better solution now I guess.

 

[Temptress Cerise]

Does Luma let you update emunand to 11.3 and use it like normal?

You don't need an emunand in Luma + a9lh. You can use your previous emunand as your new sysnand, or just scrap it - your choice.

Luma will let you update your EmuNAND to 11.3 and continue to use it like normal. However, the A9LH guide does have a section on how to move over the EmuNAND to SysNAND if you want to.

If you're on 11.3, don't attempt to boot into GW Mode. Apparently, people have been bricking. IDK the actual details. Nor do I want to test the claims. Just wait until GW releases an update to support 11.3.

 

[tNB]

Luma will let you update your EmuNAND to 11.3 and continue to use it like normal. However, the A9LH guide does have a section on how to move over the EmuNAND to SysNAND if you want to.

If you're on 11.3, don't attempt to boot into GW Mode. Apparently, people have been bricking. IDK the actual details. Nor do I want to test the claims. Just wait until GW releases an update to support 11.3.

Do you mean 11.3 sysnand or 11.3 emunand? I don't think it matters since I'd have to update my 3ds to use a9lh anyway so that sucks.

 

[netovsk]

Would rather keep my 9.2 sysNAND intact

Waiting for a better solution now I guess.

After you get everything setup, considering you did the backups, even on Sys 11.3 you can just roll back to your previous sysnand, or downgrade as low as 2.1.

 

[tNB]

httpwn seems to be a decent temporary solution for those who want to keep using their current emunand setup. Yeah it's stubborn and has no benefits but I get to keep my special edition 3ds on its original firmware

 

[BabyHands84]

Hi everyone, I recently followed this guide last night and ran into a pretty serious issue. I got up to the point of booting into gateway mode where you see the dragon and then the screen went black. I then reset the system and noticed that all of my "hack" apps had disappeared. Luma, FBI, Freeshop, everything was gone.

I then followed the troubleshooting method for the black screen issue, but none of the payloads are working now. I'm at a loss here. Anyone have a clue where I went wrong?

 

[Temptress Cerise]

Hi everyone, I recently followed this guide last night and ran into a pretty serious issue. I got up to the point of booting into gateway mode where you see the dragon and then the screen went black. I then reset the system and noticed that all of my "hack" apps had disappeared. Luma, FBI, Freeshop, everything was gone.

I then followed the troubleshooting method for the black screen issue, but none of the payloads are working now. I'm at a loss here. Anyone have a clue where I went wrong?

The warning is clearly on the first post.

11.3.0-36 Breaks GW. As a reminder, do not update while in GW Mode on a SysNAND-Only Setup. You will either brick or lose A9LH. Update using Luma3DS. Since this update breaks GW. Don't update if you want to continue using GW Mode.

It means that if you even attempt to boot 11.3 on GW, you will lose A9LH. I guess I'll revise the first post to also say that it will cause A9LH to be lost. Or try to word it differently.

You'll need to get a hardmod or do the DSiWare method to restore an A9LH NAND Backup.

 

[BabyHands84]

The warning is clearly on the first post.

11.3.0-36 Breaks GW. As a reminder, do not update while in GW Mode on a SysNAND-Only Setup. You will either brick or lose A9LH. Update using Luma3DS. Since this update breaks GW. Don't update if you want to continue using GW Mode.

It means that if you even attempt to boot 11.3 on GW, you will lose A9LH. I guess I'll revise the first post to also say that it will cause A9LH to be lost. Or try to word it differently.

You'll need to get a hardmod or do the DSiWare method to restore an A9LH NAND Backup.

I definitely misunderstood the warning. I thought you meant don't update the SysNand firmware while in GW Mode. All I did was boot into GW Mode. I didn't know that was considered "updating".

Anyways, what's done is done. What can you tell me about the DSiWare method to restore a9lh?

 

[Temptress Cerise]

I definitely misunderstood the warning. I thought you meant don't update the SysNand firmware while in GW Mode. All I did was boot into GW Mode. I didn't know that was considered "updating".

Anyways, what's done is done. What can you tell me about the DSiWare method to restore a9lh?

If reworded the warning. I don't know how much clearer it can be at this point tho.

Also, the A9LH guide doesn't have it anymore. And I don't actually remember the steps.

Go ask in the 3DS Noob Paradise thread or something. Sorry, can't help you with that.

 

[Hayleia]

I think the danger is clear, but does it apply to sysNAND only or emuNAND too? From the way you write it, it seems like both are an issue (though yeah, even if a9lh doesn't disappear, GW still doesn't work on 11.3 anyway).

 

[Temptress Cerise]

I think the danger is clear, but does it apply to sysNAND only or emuNAND too? From the way you write it, it seems like both are an issue (though yeah, even if a9lh doesn't disappear, GW still doesn't work on 11.3 anyway).

I think it's only SysNAND only. But IDK. I haven't tried it. I don't exactly have a hardmodded console and while I could prep a system with the DSiware exploit (which I don't even remember the steps for) - I am too lazy to do.

But yeah, IDK. It's entirely possible it applies only to SysNAND. Buuuuut I am not testing it, because I am lazy, and cause well, I mean if an EmuNAND user even does update to 11.3, they still wouldn't be able to boot into it, since 11.3 breaks GW Mode.

So IDK.

 

[BabyHands84]

If reworded the warning. I don't know how much clearer it can be at this point tho.

Also, the A9LH guide doesn't have it anymore. And I don't actually remember the steps.

Go ask in the 3DS Noob Paradise thread or something. Sorry, can't help you with that.

Well, thanks for help. It's not the end of the world. I have a9lh on my N3DS that I use as my primary system. All of this occurred on my O3DS that I use as a guinea pig for these exact situations.

 

[mk.2]

You don't need an emunand in Luma + a9lh. You can use your previous emunand as your new sysnand, or just scrap it - your choice.

Please excuse me if my question sounds noobish, but isn't Gateway Emunand a requirement if I want to use Gateway card?

Can I still use Gateway card if I convert my current Gateway Emunand into Sysnand?

 

[Temptress Cerise]

Please excuse me if my question sounds noobish, but isn't Gateway Emunand a requirement if I want to use Gateway card?

Can I still use Gateway card if I convert my current Gateway Emunand into Sysnand?

On A9LH, it really isn't, but you'll get a nag when trying to boot into a SysNAND-Only environment. Since there is no FIRM protection. So GW recommends//encourages you setup an EmuNAND.

For any other methods, IDK. Never tried them.

 

[xstationbr]

PS:
Its not BRICK on 11.3 A9LH, this don't BRICK A9LH+GW,
i just updated from A9LH 11.2+GW and try to see what happens, and just see a GRAY screen before Dragon Logo and nothing about BRICK.
I have restored my 11.2 and continue using my A9LH+GW with no problem.
PS: I am using SYSNAND A9LH+GW.

 

[Hayleia]

PS:
Its not true, 11.3 dont BRICK A9LH+GW,
i just updated from A9LH 11.2+GW and try to see what happens, and just see a GRAY screen before Dragon Logo and nothing about BRICK.
I have restored my 11.2 and continue using my A9LH+GW with no problem.

Do you use an emuNAND?

 

[xstationbr]

Do you use an emuNAND?

nope.
Sysnand only.
Sorry, forget to say about it.

 

[Temptress Cerise]

nope.
Sysnand only.
Sorry, forget to say about it.

Interesting. IDK then. I mean the people who reported it seem to say they didn't update with GW. But IDK.

I'll just leave the warning as-is.

 

[danzou22]

Hi guys I wish I have read the warnings before. I opened gateway in 11.3 and now the 3DS only load sysnand but without luma or anything. And I cant load hourglass o start. Anyone have a solution for this?

 

[Temptress Cerise]

Hi guys I wish I have read the warnings before. I opened gateway in 11.3 and now the 3DS only load sysnand but without luma or anything. And I cant load hourglass o start. Anyone have a solution for this?

If you have a NAND backup, then you'll need to do a hardmod to restore that NAND backup.

If you have a second 3DS with CFW, you could do the DSiWare hax transfer method and flash back an old NAND backup.

Otherwise, no.