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

 

[danzou22]

If you have a NAND backup, then you'll need to do a hardmod NAND restore. 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.

But will the hardmod work in 11.3? I have 9.2 sysnand and 11.1 i think emunand backup that were made with hourglass9 during the a9lh process, but none like 11.2 with a9lh. I know it is better to have one, but with a9lh and zero problems I was careless and didn't do any backup

In my case, the 3DS didn't bricked, it is more like I lose a9lh because I cant load luma, hourglass9 or any payload.

 

[Temptress Cerise]

But will the hardmod work in 11.3? I have 9.2 sysnand and 11.1 i think emunand backup that were made with hourglass9 during the a9lh process, but none like 11.2 with a9lh. I know it is better to have one, but with a9lh and zero problems I was careless and didn't do any backup

In my case, the 3DS didn't bricked, it is more like I lose a9lh because I cant load luma, hourglass9 or any payload.

Hardmods still work for restoring NAND backups.

What was patched out was the downgrade method that hardmods used to be able to do.

 

[danzou22]

Hardmods still work for restoring NAND backups.

What was patched out was the downgrade method that hardmods used to be able to do.

But am I not doing a downgrade if I have 11.3 and i am going to install a 9.2 or 11.1/2 backup? I dont have a backup of a sysnand with a9lh, only have 9.2 and 11.2 i think without a9lh

 

[Temptress Cerise]

But am I not doing a downgrade if I have 11.3 and i am going to install a 9.2 or 11.1/2 backup? I dont have a backup of a sysnand with a9lh, only have 9.2 and 11.2 i think without a9lh

NAND backups//restores via hardmod still work. Doesn't matter if your on 11.3.

Yes, those backups will be flashable.

If you don't have A9LH on any of those backups then you'll have to follow 3ds.guide again.

 

[raynor_ni]

Is it only firm 11.3.0-36 that breaks GW? I have 11.2.0-35E Luma3ds a9lh and I want to convert my GW saves over and not use GW anymore,
but I don't want to lose my a9lh.

Apologies if it's a dumb question!

 

[Temptress Cerise]

Is it only firm 11.3.0-36 that breaks GW? I have 11.2.0-35E Luma3ds a9lh and I want to convert my GW saves over and not use GW anymore,
but I don't want to lose my a9lh.

Apologies if it's a dumb question!

Only 11.3.

 

[rocknard]

¿Can i use "blue card" (for play nds games) from GW when i install Arm9lh + Lum 3DS (ver. 11.3) on SysNAND and GW on EmuNAND (ver. 10.7)? I read something here about that, but not sure. Play with blue card on EmuNAND 10.7 GW payload, obviously.

I found it:

Spoiler

Now, since you want to use your Blue Card, since it's the thing that plays NDS Roms, then you'll need only the contents insidde of the Blue Card R4i folder. The blue card fix is for some outdated thing and it will actually break Luma3DS if you install it. Once you have the contents of the Blue Card R4i folder on your Blue Card's microSD, that's it! You don't need anything else, apart from your DS Roms on it. You boot into Luma3DS and just insert the blue card. And you play it.

I don't understand one thing: if i have Arm9lh + Luma 3DS on sysnand 11.3 and Emunand GW on 10.7 and i start sysnand (11.3 arm9lh-luma3ds), won't i never can use gateway to brick sysnand, won't i? It's only for people with only sysnand with arm9lh and GW and load GW on 11.3.

Do i need unninstall MSET 4.5 exploit on Emunand GW (to avoid conflict) or there isn't problem with him?

Thank you for this guide.

 

[Arnold101]

please help

Gateway Logo (Recommend for Everyone - SysNAND Only & GW EmuNAND Users)


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.



i have black screen only. i don't have an emunand. only sysnand with luma. but i cannot return gateway back to work, i tried even to boot the gw menu and gateway mode after that but still black screen

 

[Arnold101]

i have downgraded to firmware 10 and now works, but gw.3dsx from hbl does a black screen. how i can start gw mode from hbl?

 

[sethyboy]

Sorry if this is a nooby question, but I'd just like to make sure that I can do this right. I'd like to install A9LH+Luma so I can play GBA/DSiWare, but would also like to keep using my Gateway red card.

Plailect's guide says I should do a system update after restoring my backup, but since GW doesn't work on 11.3, should I just skip this step for now? Or if I do have to install the update, can I restore the old backup again (keeping A9LH) with Hourglass9 after I've finished the guide? Will I have to inject FBI again? I just want to make sure this step is really required or not; I'm very cautious about ruining anything.

I have 4.5 sysNAND with a 9.9 GW emuNAND. Thanks!

 

[tomx86]

11.3.0-36 Breaks GW. GW currently DOES NOT support 11.3. 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, while on 11.3, you will lose A9LH or brick.

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.

As a reminder, update using Luma3DS. Since this update breaks GW. Don't update to 11.3 if you want to continue using GW Mode.


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 (Recommend for Everyone - SysNAND Only & GW EmuNAND Users)

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 GW's Launcher.dat on the root of your SD Card. If you are 11.1, only the latest 4.2//3.7.2 (They're the same file) Launcher.dat works.

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, especially NOT for SysNAND-Only Users - 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 GW's Launcher.dat on the root of your SD Card. If you are 11.1, only the latest 4.2//3.7.2 (They're the same file) Launcher.dat works.

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.
If you are a SysNAND-Only User, perform any System Updates while using//booting Luma3DS.






!~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

Can you make a version of v2gw.bin that boots to the Gateway menu when the Gateway flash card is not detected, like it was in the original, please?

 

[Temptress Cerise]

Can you make a version of v2gw.bin that boots to the Gateway menu when the Gateway flash card is not detected, like it was in the original, please?

Think you'd have to talk to GW about that.

 

[tomx86]

Think you'd have to talk to GW about that.

Oh so it's gateway.bin fault, ok Thanks.

 

[LetGoMyLegHo]

Hey guys, followed the steps in the guide and even deleted whatever Emunand was still on my SD card. Whenever I boot while holding D-pad down, I just get a black screen. I'm able to boot into Sysnand and Emunand via Luma just fine. Anything else I should try out or did I miss a step somewhere?

EDIT:
After some fiddling, it seems that I've deleted my EmuNAND and I'm unable to update my SysNAND from 2.1.0-4U.

 

[Temptress Cerise]

Hey guys, followed the steps in the guide and even deleted whatever Emunand was still on my SD card. Whenever I boot while holding D-pad down, I just get a black screen. I'm able to boot into Sysnand and Emunand via Luma just fine. Anything else I should try out or did I miss a step somewhere?

EDIT:
After some fiddling, it seems that I've deleted my EmuNAND and I'm unable to update my SysNAND from 2.1.0-4U.

If you're on a SysNAND-Only setup. I advise you not to continue using GW. GW does not officially support 11.3 or 11.4. Booting into GW Mode while on a 11.3 or 11.4 SysNAND will remove A9LH from your system and leave you on a stock only console. It does not matter how you updated to 11.3 or 11.4.

As for your other issue of being on 2.1.0-4U SysNAND. I suggest you look at the 3ds.guide for troubleshooting that.

 

[tomx86]

Think you'd have to talk to GW about that.

!UPDATE!
Looks like it was Luma's v6.6 fault, cause ever since I updated luma to v7.0.1 I can now go to the GATEWAY menu (L+SELECT) without the flash card in the game slot, but don't know what made it work.

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

Hey guys, followed the steps in the guide and even deleted whatever Emunand was still on my SD card. Whenever I boot while holding D-pad down, I just get a black screen. I'm able to boot into Sysnand and Emunand via Luma just fine. Anything else I should try out or did I miss a step somewhere?

EDIT:
After some fiddling, it seems that I've deleted my EmuNAND and I'm unable to update my SysNAND from 2.1.0-4U.

Try ctr-transfer to 9.2 on 3ds.guide, and make a new eumuNAND, and update it to 11.2 with "sysDowngrader_2_0_2" to use gateway.

 

[themadsinger]

Hi

I have an o3ds which I was running on 4.5 with gateway. I have followed the 3ds.guide instructions to install A9LH and luma (6.6 I think).

When it said do an update after restoring my 4.5 backup, I updated to 11.2 using sysupdater. prior to starting the process, I had done a GW emunand update which put it on 11.3 so wouldnt boot from the the GW menu as laucnher.dat compatible with 11.3 not yet available.

Everything above warns about Sysnand 11.3 and GW. My understanding is that I am on Sysnand 11.2. I dont have an emunand set up apart from the 11.3 on GW which doesnt boot at the moment. Before following the procedure set out on page 1 of this thread, I just want to double check I am safe to do so and wont risk my A9LH and luma installations. Also, does this boot me into the GW menu from where I can format etc the GW emunand?

Many thanks

 

[Temptress Cerise]

Hi

I have an o3ds which I was running on 4.5 with gateway. I have followed the 3ds.guide instructions to install A9LH and luma (6.6 I think).

When it said do an update after restoring my 4.5 backup, I updated to 11.2 using sysupdater. prior to starting the process, I had done a GW emunand update which put it on 11.3 so wouldnt boot from the the GW menu as laucnher.dat compatible with 11.3 not yet available.

Everything above warns about Sysnand 11.3 and GW. My understanding is that I am on Sysnand 11.2. I dont have an emunand set up apart from the 11.3 on GW which doesnt boot at the moment. Before following the procedure set out on page 1 of this thread, I just want to double check I am safe to do so and wont risk my A9LH and luma installations. Also, does this boot me into the GW menu from where I can format etc the GW emunand?

Many thanks

If your EmuNAND is on 11.3. Then you will just black screen. If GW sees an EmuNAND, it will boot into that first and always. Regardless of what your SysNAND is at.

To get into the GW Menu you will have to hold L+Select as soon as you see the dragon logo.

Also, the latest Luma3DS version is 7.0.2. I advise you update to it.

As for your SysNAND. Since you have an EmuNAND. GW won't care about it. Since again, it will always boot the EmuNAND if it sees one.

You can create a new one by booting into the GW Menu and formatting it and creating one based on your SysNAND which is at 11.2, so you'll end up creating a new EmuNAND that's on 11.2.

However, this means you will have to unlink the NANDs with something like TinyFormat. You will also, lose anything that was on your old EmuNAND. Such as .CIA based saves and stuff.

 

[desrone2]

If your EmuNAND is on 11.3. Then you will just black screen. If GW sees an EmuNAND, it will boot into that first and always. Regardless of what your SysNAND is at.

To get into the GW Menu you will have to hold L+Select as soon as you see the dragon logo.

Also, the latest Luma3DS version is 7.0.2. I advise you update to it.

As for your SysNAND. Since you have an EmuNAND. GW won't care about it. Since again, it will always boot the EmuNAND if it sees one.

You can create a new one by booting into the GW Menu and formatting it and creating one based on your SysNAND which is at 11.2, so you'll end up creating a new EmuNAND that's on 11.2.

However, this means you will have to unlink the NANDs with something like TinyFormat. You will also, lose anything that was on your old EmuNAND. Such as .CIA based saves and stuff.

Hey, just a question, I stupidly updated my system whilst in gateway mode thinking it was fine (as long as i'm IN gateway/cfw mode), but now further attempts to boot gateway fail, another member on here told me to go for luma 3ds, and the 3ds.guide is kinda lengthy.. is it true that gateway is releasing an update soon-ish? Should I just wait if I can?

 

[themadsinger]

If your EmuNAND is on 11.3. Then you will just black screen. If GW sees an EmuNAND, it will boot into that first and always. Regardless of what your SysNAND is at.

To get into the GW Menu you will have to hold L+Select as soon as you see the dragon logo.

Also, the latest Luma3DS version is 7.0.2. I advise you update to it.

As for your SysNAND. Since you have an EmuNAND. GW won't care about it. Since again, it will always boot the EmuNAND if it sees one.

You can create a new one by booting into the GW Menu and formatting it and creating one based on your SysNAND which is at 11.2, so you'll end up creating a new EmuNAND that's on 11.2.

However, this means you will have to unlink the NANDs with something like TinyFormat. You will also, lose anything that was on your old EmuNAND. Such as .CIA based saves and stuff.

That. That is very helpful. So I cannot affect anything by following the procedure when on 11.2

Excuse my ignorance but can you clarify what you mean about the NANDs being linked? IS that because I will have created the emunand based on the sysand, so the two will be linked so that if I update one I automatically update the other? If that is correct, can I create the emunand based on 11.2 update files which I used for the sysupdater so avoid the two being linked?

Thanks again