Tutorial  Updated

Using Luma3DS + Gateway on B9S


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:
    Code:
    [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:

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

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/







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



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
 

Attachments

  • v2gw.zip
    6.3 KB · Views: 12,152
  • v2gw-de-init.zip
    9.1 KB · Views: 3,293
Last edited by Temptress Cerise,

mdg

Member
Newcomer
Joined
Jan 6, 2009
Messages
14
Trophies
0
XP
189
Country
Then how on earth is your 3DS even booting? Without a NAND to boot, your 3DS wouldn't even work.

Anyways, it sounds like your using a SysNAND setup. Yeah. It'll work.


My error, I have followed your guide but i cannot seen to get it to work. I have set all the files up the correct way I downloaded v2gw.zip extract it to D:\luma\payloads and renamed it from arm9loaderhax.bin to v2gw.bin. And the same for GW's "arm9loaderhax.bin" renamed that to gateway.bin and placed in D:\luma\payloads

The GW's Launcher.dat I am using is v3.7.1 as this version i don't get the prompted to press 'L+R+SELECT' to boot SYSNAND popup.

Next I downloaded BootCTR9-firmv2.zip, extract it to D:\luma\payloads and renamed it from boot.firm to down_BootCTR9.firm. Then I extract the boot_config.ini and placed it on the root on my SD Card. I open it up the boot_config.ini in notepad and overwrite the text with just.

[BOOTCTR9]
key_delay = 1000

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

Save it then unmount the SD Card and place it back in my N3DS, while i power on while holden down i get the black srceen for a few secords but it just go's to my games home screen and not the gateway dragon screen..

Thanks on any help.
 

Attachments

  • 1.jpg
    1.jpg
    41.8 KB · Views: 190
  • 2.jpg
    2.jpg
    68.8 KB · Views: 184

Temptress Cerise

Miss Magic~ <3
OP
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
My error, I have followed your guide but i cannot seen to get it to work. I have set all the files up the correct way I downloaded v2gw.zip extract it to D:\luma\payloads and renamed it from arm9loaderhax.bin to v2gw.bin. And the same for GW's "arm9loaderhax.bin" renamed that to gateway.bin and placed in D:\luma\payloads

The GW's Launcher.dat I am using is v3.7.1 as this version i don't get the prompted to press 'L+R+SELECT' to boot SYSNAND popup.

Next I downloaded BootCTR9-firmv2.zip, extract it to D:\luma\payloads and renamed it from boot.firm to down_BootCTR9.firm. Then I extract the boot_config.ini and placed it on the root on my SD Card. I open it up the boot_config.ini in notepad and overwrite the text with just.

[BOOTCTR9]
key_delay = 1000

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

Save it then unmount the SD Card and place it back in my N3DS, while i power on while holden down i get the black srceen for a few secords but it just go's to my games home screen and not the gateway dragon screen..

Thanks on any help.
Your problem is using an outdated Launcher.dat.

iirc, only an actual private beta Launcher.dat was able to boot 11.0+ and didn't give the nag. The nag was added after that, because they don't protect the FIRM.
 

mdg

Member
Newcomer
Joined
Jan 6, 2009
Messages
14
Trophies
0
XP
189
Country
Your problem is using an outdated Launcher.dat.

iirc, only an actual private beta Launcher.dat was able to boot 11.0+ and didn't give the nag. The nag was added after that, because they don't protect the FIRM.

Right i updated the Launcher.dat from GATEWAY ULTRA 3.7.2 BETA which is really GW_Ultra_4.2_BETA. But it's the same power on while hold the down button it just go's to my games home screen.
 

Temptress Cerise

Miss Magic~ <3
OP
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
Right i updated the Launcher.dat from GATEWAY ULTRA 3.7.2 BETA which is really GW_Ultra_4.2_BETA. But it's the same power on while hold the down button it just go's to my games home screen.
Your pictures are confusing. Some of them show extensions, other's don't.
Properly configure your Windows Explorer: https://3ds.guide/file-extensions-(windows)

And check your extensions//names again.
 

bjaxx87

Well-Known Member
Member
Joined
Jun 17, 2011
Messages
448
Trophies
1
XP
1,274
Country
Germany
I'm a little confused where to start. I'm still dual-booting Gateway and Luma on a 9.2 SysNAND/11.2 EmuNAND Menuhax setup. While 3ds.guide is a great guide (I used it to install A9LH on a friend's console before B9S was a thing) it lacks explanation how to keep my EmuNAND and spare me the hassle of reinstalling 100+ games and reinjecting saves.

Should I...
- backup my SD card and EmuNAND partition
- clean my SD card from any contents including EmuNAND
- follow 3ds.guide in it's entirety except for updating the SysNAND
- reinject EmuNAND to my SD card using EmuNANDtool
- copy all backup content back to my SD card
- and then follow your guide to be able to actually boot it on my new B9S setup?
 

Temptress Cerise

Miss Magic~ <3
OP
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
Edit: General Update: I'm aware of the 1.1 B9S release, however, 3DS.Guide currently doesn't have any steps on updating to it. As such, I will not be checking whether or not this method still works on 1.1, until 1.1 is actually recommended and there are steps to update to it via 3DS.Guide. If you decide to update to 1.1 B9S, you're more than welcome to try this workaround and post here if it still works, but I won't be doing testing on it anytime soon.

I'm a little confused where to start. I'm still dual-booting Gateway and Luma on a 9.2 SysNAND/11.2 EmuNAND Menuhax setup. While 3ds.guide is a great guide (I used it to install A9LH on a friend's console before B9S was a thing) it lacks explanation how to keep my EmuNAND and spare me the hassle of reinstalling 100+ games and reinjecting saves.

Should I...
- backup my SD card and EmuNAND partition
- clean my SD card from any contents including EmuNAND
- follow 3ds.guide in it's entirety except for updating the SysNAND
- reinject EmuNAND to my SD card using EmuNANDtool
- copy all backup content back to my SD card
- and then follow your guide to be able to actually boot it on my new B9S setup?
I would backup your SD Card and EmuNAND, just to be safe.

As for removing any files of your SD Card. There really is no need. Especiall, if your using menuhax, but not autobooting, you could essentially just follow the guide from this point: https://3ds.guide/installing-boot9strap-(homebrew-launcher)
If you are autobooting, you probably did something with the boot.3dsx file, so you'd just have to replace it with the HBL one, found here: http://smealum.github.io/ninjhax2/starter.zip


After that, you'd want to ignore any steps that advise you on moving your EmuNAND. You can safely update your SysNAND though, if you want. However, if you're looking to continue using EmuNAND for both Luma3DS and Gateway3DS. Then you'll want to check off the Luma3DS config setting that says "Autoboot EmuNAND" in addition to what the guide tells you.

And that's really about it, I think.
 
Last edited by Temptress Cerise,
  • Like
Reactions: bjaxx87

Temptress Cerise

Miss Magic~ <3
OP
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
Sorry for the double post.

I have gone and tested this method with B9S 1.2 + Luma 8.0.

Works just fine.

Edit: As always, same warnings still apply. You should use an EmuNAND and all that jazz.
 
Last edited by Temptress Cerise,

zhdarkstar

Well-Known Member
Member
Joined
Jan 30, 2008
Messages
573
Trophies
1
XP
566
Country
United States
Sorry for the double post.

I have gone and tested this method with B9S 1.2 + Luma 8.0.

Works just fine.

Edit: As always, same warnings still apply. You should use an EmuNAND and all that jazz.
How did you get BootCTR9 to load with b9s 1.2 and Luma 8.0?
This is the screen I always get when attempting to run BootCTR9.
20170605_012752_0011.jpg
 

Temptress Cerise

Miss Magic~ <3
OP
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
How did you get BootCTR9 to load with b9s 1.2 and Luma 8.0?
This is the screen I always get when attempting to run BootCTR9.
20170605_012752_0011.jpg
If your using BootCTR9 as your main, then you're SOL. It's broken as the main boot.firm file. That's an issue you should be bringing up in BootCTR9's support thread, I guess.

It works just fine as being used as part of the chain to get GW to boot, with Luma3DS' boot.firm as the main.
 

Hihomaster

Well-Known Member
Member
Joined
Jun 25, 2008
Messages
184
Trophies
0
XP
486
Country
France
i have the same error doesn't work at all when i start my 3DS to go to GW but strangely the down_button works when you are in the system setting?

Edit : when launching with the start button from luma it's broken. when launched with the combination mode of luma 8 broken as well but when you are in system setting in luma and quit it does a reboot if you press the combination it boots to GW
 
Last edited by Hihomaster,

Temptress Cerise

Miss Magic~ <3
OP
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
i have the same error doesn't work at all when i start my 3DS to go to GW but strangely the down_button works when you are in the system setting?

Edit : when launching with the start button from luma it's broken. when launched with the combination mode of luma 8 broken as well but when you are in system setting in luma and quit it does a reboot if you press the combination it boots to GW
Not sure what to tell you. Recheck your files.

Working on my end. N3DS and o3DS.
Both on B9S 1.2 and Luma3DS 8.0
 

Reecey

Mario 64 (favorite game of all time)
Member
Joined
Mar 7, 2010
Messages
5,864
Trophies
2
Location
At Home :)
XP
4,453
Country
How did you get BootCTR9 to load with b9s 1.2 and Luma 8.0?
This is the screen I always get when attempting to run BootCTR9.
20170605_012752_0011.jpg
Mine does the same on v1.2B9S. What we need is an update version of BootCTR9.firm file and we are all good to go but I'm not sure how to compile the new files myself. I've asked some one in a thread to see if they would kindly do one they seem to know what they are doing.
 

Temptress Cerise

Miss Magic~ <3
OP
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
Give us your settings then, please.
It wont work until the dev bootctr9 has been updated, if you read the proper thread hes working on it ;)

I'm not sure what to tell any of you. It's working fine. Same exact settings and files as in the main post.

Again, this will only work being chainload of Luma3DS.

If you are using BootCTR9 as your main boot.firm, then it won't work. You have to wait for BootCTR9 to get proper B9S 1.2 support.

Also, if you somehow even managed to get this method working with messed up converted .bin to .firm files for GW's a9lh.bin and v2gw.bin, then that could also be it. I'm using the .bin files of those two.
 
  • Like
Reactions: tomx86

SonGoku78

Well-Known Member
Member
Joined
May 11, 2014
Messages
272
Trophies
0
Age
45
XP
886
Country
Gambia, The
I'm not sure what to tell any of you. It's working fine. Same exact settings and files as in the main post.

Again, this will only work being chainload of Luma3DS.

If you are using BootCTR9 as your main boot.firm, then it won't work. You have to wait for BootCTR9 to get proper B9S 1.2 support.

Also, if you somehow even managed to get this method working with messed up converted .bin to .firm files for GW's a9lh.bin and v2gw.bin, then that could also be it. I'm using the .bin files of those two.

Hey there, just a quick question to be sure. I managed successfuly to get this working thanks to your tutorial before B9S 1.2 and Luma 8 Update.
So i assume, i can leave all files as the are right now and just update B9S and Luma without the need of touching anything BootCTR9 related right ? I am using keypad down to boot into Gateway Emunand.
Thanks in advance
 

Temptress Cerise

Miss Magic~ <3
OP
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
Hey there, just a quick question to be sure. I managed successfuly to get this working thanks to your tutorial before B9S 1.2 and Luma 8 Update.
So i assume, i can leave all files as the are right now and just update B9S and Luma without the need of touching anything BootCTR9 related right ? I am using keypad down to boot into Gateway Emunand.
Thanks in advance
Yeah, there shouldn't be anything you need to change at all.
 
  • Like
Reactions: SonGoku78

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    AncientBoi @ AncientBoi: Imma make quesadillas for lunch :D +1