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,155
  • v2gw-de-init.zip
    9.1 KB · Views: 3,296
Last edited by Temptress Cerise,
  • Like
Reactions: SylverReZ, StevenLexon, Hinz90 and 62 others
Click to expand...
Temptress Cerise

Temptress Cerise

Miss Magic~ <3
OP
Member
Level 11
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,337
Country
United States
The Real Jdbye said:
I named it gatewait.bin and placed it on the root. Does the folder really matter?
Click to expand...
I still have no idea what file you are referring to.

v2gw.bin is just a stripped down boot-manager that loads /luma/payloads/gateway.bin.

So yeah, gateway.bin at that location, must exist, to be able to load anything.
 
  • Like
Reactions: The Real Jdbye
The Real Jdbye

The Real Jdbye

*is birb*
Member
Level 23
Joined
Mar 17, 2010
Messages
23,333
Trophies
4
Location
Space
XP
13,908
Country
Norway
Temptress Cerise said:
I still have no idea what file you are referring to.

v2gw.bin is just a stripped down boot-manager that loads /luma/payloads/gateway.bin.

So yeah, gateway.bin at that location, must exist, to be able to load anything.
Click to expand...
I took the arm9loaderhax.bin from Gateway's page and renamed it gatewait.bin.
That might actually be my mistake. I assumed it was the same file as the v2gw.bin. Will try with the other one now, but I'm not expecting much.
Edit: That actually made it worse. Now it just powers off when loading the default payload. GodMode9 and Luma still work, but the v2gw payload makes it power off.
 
Last edited by The Real Jdbye,
The Real Jdbye

The Real Jdbye

*is birb*
Member
Level 23
Joined
Mar 17, 2010
Messages
23,333
Trophies
4
Location
Space
XP
13,908
Country
Norway
Temptress Cerise said:
I still have no idea what file you are referring to.

v2gw.bin is just a stripped down boot-manager that loads /luma/payloads/gateway.bin.

So yeah, gateway.bin at that location, must exist, to be able to load anything.
Click to expand...
It was my mistake. Several troubleshooting steps later I realized v2gw.bin and Gateway's arm9loaderhax.bin were NOT the same file as I had assumed. Yet more steps later I realized I might need both of them to make it work. Even more steps later I realized I had forgot to rename Gateway's arm9loaderhax.bin to gateway.bin...
It works now. Nevermind me :P
I've actually never used the v2gw method of booting Gateway before, and always assumed it was just a workaround using BootCtr9, not a completely different a9lh payload. My fault.
My A9LH setup predated that, and was using a multi-stage2 payload A9LH setup that could load both the homebrew A9LH payload and GW's gimped one. (in other words, I never used Gateway's arm9loaderhax.bin payload, which soon after stopped working, and I was still on A9LH v1)
 
Last edited by The Real Jdbye,
Temptress Cerise

Temptress Cerise

Miss Magic~ <3
OP
Member
Level 11
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,337
Country
United States
The Real Jdbye said:
It was my mistake. Several troubleshooting steps later I realized v2gw.bin and Gateway's arm9loaderhax.bin were NOT the same file as I had assumed. Yet more steps later I realized I might need both of them to make it work. Even more steps later I realized I had forgot to rename Gateway's arm9loaderhax.bin to gateway.bin...
It works now. Nevermind me :P
I've actually never used the v2gw method of booting Gateway before, and always assumed it was just a workaround using BootCtr9, not a completely different a9lh payload. My fault.
My A9LH setup predated that, and was using a multi-stage2 payload A9LH setup that could load both the homebrew A9LH payload and GW's gimped one. (in other words, I never used Gateway's arm9loaderhax.bin payload, which soon after stopped working, and I was still on A9LH v1)
Click to expand...
Nah, the old guide, which is still up there for reference. Was used on v2+ A9LH forks with Luma3DS, so that it would work. Back then, your option was use v2gw.bin or BootCTR9.

Now the solution is to use both.
 
  • Like
Reactions: The Real Jdbye
The Real Jdbye

The Real Jdbye

*is birb*
Member
Level 23
Joined
Mar 17, 2010
Messages
23,333
Trophies
4
Location
Space
XP
13,908
Country
Norway
Temptress Cerise said:
Nah, the old guide, which is still up there for reference. Was used on v2+ A9LH forks with Luma3DS, so that it would work. Back then, your option was use v2gw.bin or BootCTR9.

Now the solution is to use both.
Click to expand...
I meant my setup predated 3ds.guide, it was from back when it was on GitHub, and the guide was a lot more primitive, and before Gateway ever released their arm9loaderhax.bin payload. But thanks for the hint, I might not have figured it out if it weren't for you :)
 
RandomUser

RandomUser

Rosalina in Plush Form
Member
Level 7
Joined
May 9, 2010
Messages
967
Trophies
1
XP
1,042
Country
United States
The Real Jdbye said:
I tried this.
My config:


Yes the file is named gatewait.bin on root of SD. It seems to boot, the screen turns on the backlight, then turns it off, and stays that way (with a black screen all the way through), which seems consistent with my old setup, only the Gateway logo never appears.
What am I doing wrong?

Edit: For the record, both GodMode9 and Luma boot correctly with the relevant keypresses. Only Gateway refuses to boot.

I've set BootCtr9 as my primary payload, but that shouldn't matter, right? It should boot other payloads equally regardless of how it's booted.
Click to expand...
I have got GW working thanks for your config files. I did indeed did something wrong with the config file. I had to make some changes to your config file to get gateway to work, or else you will get a stack dump error.
as fallows:
Code: 
---this part may not be necessary, I didn't have this a9nc.bin---
;Section to allow a9lh net companion payload auto booting
#[COMPANION]
#path = /a9nc.bin
#delay = 100
#offset = 0
#payload = -1
---End of this part may not be necessary, I didn't have this a9nc.bin---

[DEFAULT]
path = /luma/Payloads/Bootgateway.firm
#screenBrightness = 0x30
#screenEnabled = 1
delay = 1000
enablePathFix = 1

[KEY_A]
path = /luma/Payloads/Bootgateway.firm
#screenBrightness = 0x30
#screenEnabled = 1
delay = 1000
enablePathFix = 1
anyway you need the firm version of gateway, also the gateway.bin (the GW arm9loaderhax.bin from gateway themselves). Since the firm does not exist in the wild yet, I built my own by converting the bin to firm format. They both need to be in /luma/Payloads/.
Remember without the firm, gateway will never work on B9S due to the requirement.
Attachment for easy drag and drop, it contains both GW files that is needed.

Edit:
@Temptress Cerise the firm file is the v2gw version of the bin for loading GW. It should work directly from luma if you want to skip using bootCTR9
 

Attachments

  • GatewayB9S.7z
    10.7 KB · Views: 212
Last edited by RandomUser,
Temptress Cerise

Temptress Cerise

Miss Magic~ <3
OP
Member
Level 11
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,337
Country
United States
RandomUser said:
I have got GW working thanks for your config files. I did indeed did something wrong with the config file. I had to make some changes to your config file to get gateway to work, or else you will get a stack dump error.
as fallows:
Code: 
---this part may not be necessary, I didn't have this a9nc.bin---
;Section to allow a9lh net companion payload auto booting
#[COMPANION]
#path = /a9nc.bin
#delay = 100
#offset = 0
#payload = -1
---End of this part may not be necessary, I didn't have this a9nc.bin---

[DEFAULT]
path = /luma/Payloads/Bootgateway.firm
#screenBrightness = 0x30
#screenEnabled = 1
delay = 1000
enablePathFix = 1

[KEY_A]
path = /luma/Payloads/Bootgateway.firm
#screenBrightness = 0x30
#screenEnabled = 1
delay = 1000
enablePathFix = 1
anyway you need the firm version of gateway, also the gateway.bin (the GW arm9loaderhax.bin from gateway themselves). Since the firm does not exist in the wild yet, I built my own by converting the bin to firm format. They both need to be in /luma/Payloads/.
Remember without the firm, gateway will never work on B9S due to the requirement.
Attachment for easy drag and drop, it contains both GW files that is needed.
Click to expand...
The reason I don't provide or link GW's A9LH.bin is because we don't know if it contains any copyrighted code. And it's really not that hard to find from my instructions.

Also, converting to .firm isn't needed. BootCTR9 will work with the .bin file of v2gw.

So I'm not sure what this post was for.

Also, the config you made could be even simpler:

Code: 
[DEFAULT]
path = /luma/Payloads/Bootgateway.firm
delay = 1000

[KEY_A]
path = /luma/Payloads/Bootgateway.firm
delay = 1000
enablePathFix = 1 is only used for Luma3DS.
 
  • Like
Reactions: Joel16
RandomUser

RandomUser

Rosalina in Plush Form
Member
Level 7
Joined
May 9, 2010
Messages
967
Trophies
1
XP
1,042
Country
United States
Temptress Cerise said:
The reason I don't provide or link GW's A9LH.bin is because we don't know if it contains any copyrighted code. And it's really not that hard to find from my instructions.

Also, converting to .firm isn't needed. BootCTR9 will work with the .bin file of v2gw.

So I'm not sure what this post was for.

Also, the config you made could be even simpler:

Code: 
[DEFAULT]
path = /luma/Payloads/Bootgateway.firm
delay = 1000

[KEY_A]
path = /luma/Payloads/Bootgateway.firm
delay = 1000
enablePathFix = 1 is only used for Luma3DS.
Click to expand...
Okay my bad then, before I was booting GW straight from Luma, as I couldn't get this bootctr9 to work properly. My guess was I keep clucking up the config file when removing and editing things within it, so it worked better commenting out some stuff as apposed to deleting them, again it could be that I was not properly editing the config file.
Edit:
Also forgot to mention that I am new to bootctr9. I haven't had any al9h hax until just recently, then B9S.
Thank you for letting me know.
 
Last edited by RandomUser,
The Real Jdbye

The Real Jdbye

*is birb*
Member
Level 23
Joined
Mar 17, 2010
Messages
23,333
Trophies
4
Location
Space
XP
13,908
Country
Norway
RandomUser said:
I have got GW working thanks for your config files. I did indeed did something wrong with the config file. I had to make some changes to your config file to get gateway to work, or else you will get a stack dump error.
as fallows:
Code: 
---this part may not be necessary, I didn't have this a9nc.bin---
;Section to allow a9lh net companion payload auto booting
#[COMPANION]
#path = /a9nc.bin
#delay = 100
#offset = 0
#payload = -1
---End of this part may not be necessary, I didn't have this a9nc.bin---

[DEFAULT]
path = /luma/Payloads/Bootgateway.firm
#screenBrightness = 0x30
#screenEnabled = 1
delay = 1000
enablePathFix = 1

[KEY_A]
path = /luma/Payloads/Bootgateway.firm
#screenBrightness = 0x30
#screenEnabled = 1
delay = 1000
enablePathFix = 1
anyway you need the firm version of gateway, also the gateway.bin (the GW arm9loaderhax.bin from gateway themselves). Since the firm does not exist in the wild yet, I built my own by converting the bin to firm format. They both need to be in /luma/Payloads/.
Remember without the firm, gateway will never work on B9S due to the requirement.
Attachment for easy drag and drop, it contains both GW files that is needed.

Edit:
@Temptress Cerise the firm file is the v2gw version of the bin for loading GW. It should work directly from luma if you want to skip using bootCTR9
Click to expand...
enablepathfix is only for Luma.
I'm just using v2gw.bin and gateway.bin (both being in luma\payloads) with BootCtr9, and it's working fine.
Anyway, I heard everywhere that converting GW's arm9loaderhax.bin to .firm didn't work, it's good to know that it was easy getting it to work with BootCtr9, I suppose it should be an easy fix for devs. @Aurora Wright?
 
Aurora Wright

Aurora Wright

Well-Known Member
Member
Level 14
Joined
Aug 13, 2006
Messages
1,550
Trophies
3
XP
4,499
Country
Italy
The Real Jdbye said:
enablepathfix is only for Luma.
I'm just using v2gw.bin and gateway.bin (both being in luma\payloads) with BootCtr9, and it's working fine.
Anyway, I heard everywhere that converting GW's arm9loaderhax.bin to .firm didn't work, it's good to know that it was easy getting it to work with BootCtr9, I suppose it should be an easy fix for devs. @Aurora Wright?
Click to expand...
It's up to gw to update their payload, it didn't work even on late a9lh versions (probably some start.s thing on their end)
 
The Real Jdbye

The Real Jdbye

*is birb*
Member
Level 23
Joined
Mar 17, 2010
Messages
23,333
Trophies
4
Location
Space
XP
13,908
Country
Norway
Aurora Wright said:
It's up to gw to update their payload, it didn't work even on late a9lh versions (probably some start.s thing on their end)
Click to expand...
Well, according to that guy, GW payload works when converted to .firm if using BootCtr9, but for some reason it doesn't work loaded from Luma 7.1.
So it should just be a matter of finding out how BootCtr9 loads payloads differently from Luma by comparing, right?
 
Aurora Wright

Aurora Wright

Well-Known Member
Member
Level 14
Joined
Aug 13, 2006
Messages
1,550
Trophies
3
XP
4,499
Country
Italy
The Real Jdbye said:
Well, according to that guy, GW payload works when converted to .firm if using BootCtr9, but for some reason it doesn't work loaded from Luma 7.1.
So it should just be a matter of finding out how BootCtr9 loads payloads differently from Luma by comparing, right?
Click to expand...
I think it's a matter of start.s. For some reason the crt0 of Luma/new a9lh doesn't work with the gw payload, it would be easy to fix their payload having sources
 
T

Thelonewolf88

Well-Known Member
Member
Level 3
Joined
Jun 11, 2016
Messages
304
Trophies
0
Age
35
XP
333
Country
United States
Hi guys/girls. Just to confirm that if I follow this guide on my (b9s) 11.4 sys/11.2 emunand and enable autoboot "emunand" in luma, this will work fine? Or do I just leave Luma to boot 11.4 sys, yet will launching the GW payload automatically load my 11.2 emunand?

Tia:)
 
Temptress Cerise

Temptress Cerise

Miss Magic~ <3
OP
Member
Level 11
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,337
Country
United States
Thelonewolf88 said:
Hi guys/girls. Just to confirm that if I follow this guide on my (b9s) 11.4 sys/11.2 emunand and enable autoboot "emunand" in luma, this will work fine? Or do I just leave Luma to boot 11.4 sys, yet will launching the GW payload automatically load my 11.2 emunand?

Tia:)
Click to expand...
GW and Luma3DS are independent of each other.

You can setup Luma3DS to boot your SysNAND or EmuNAND, it's really all up to you.

GW will always load EmuNAND, if there is one to load.
 
  • Like
Reactions: Thelonewolf88
P

petspeed

Well-Known Member
Member
Level 9
Joined
Nov 13, 2009
Messages
1,144
Trophies
1
Age
49
XP
1,757
Country
Denmark
Thelonewolf88 said:
Hi guys/girls. Just to confirm that if I follow this guide on my (b9s) 11.4 sys/11.2 emunand and enable autoboot "emunand" in luma, this will work fine? Or do I just leave Luma to boot 11.4 sys, yet will launching the GW payload automatically load my 11.2 emunand?

Tia:)
Click to expand...
Gateway doesn't support 11.4. It says in the OP to now even try to use gateway on that FW version. Just a warning!
 
RandomUser

RandomUser

Rosalina in Plush Form
Member
Level 7
Joined
May 9, 2010
Messages
967
Trophies
1
XP
1,042
Country
United States
The Real Jdbye said:
enablepathfix is only for Luma.
I'm just using v2gw.bin and gateway.bin (both being in luma\payloads) with BootCtr9, and it's working fine.
Anyway, I heard everywhere that converting GW's arm9loaderhax.bin to .firm didn't work, it's good to know that it was easy getting it to work with BootCtr9, I suppose it should be an easy fix for devs. @Aurora Wright?
Click to expand...
Yeah, I did not realized to use bootctr9 for gateway, the firm file isn't needed. I should have read the first page better, I guess my mind is or was on the fritz. Sorry for the run around, but at least with the firm file, I am able to load GW direct from Luma without any problem, thereby bypassing the need for bootctr9. I guess I am special as it seems I'm the only one who can run GW using Luma directly and I am using Luma 7.1, perhaps it's because of my avatar?:ha: Also to clarify, the firm file is made from v2gw, so both the gateway arm9loaderhax.bin and the v2gw firm is used when using Luma as a payload launcher.
Also thank you for letting me know that enablepathfix is just for Luma, I didn't read too much into bootctr9 as this is my first time ever using bootctr9.
 
B

b17bomber

Well-Known Member
Member
Level 10
Joined
Jun 15, 2009
Messages
602
Trophies
1
XP
2,103
Country
United States
I just followed the new pialect guide and have godmode 9 and 11.4 I'd like to go back to gateway, or at least have a dual boot. Will this help me?
Can I have a sysnand 11.4 and emunand 11.2? I have a backup o fmy old emunand
 
The Real Jdbye

The Real Jdbye

*is birb*
Member
Level 23
Joined
Mar 17, 2010
Messages
23,333
Trophies
4
Location
Space
XP
13,908
Country
Norway
b17bomber said:
I just followed the new pialect guide and have godmode 9 and 11.4 I'd like to go back to gateway, or at least have a dual boot. Will this help me?
Can I have a sysnand 11.4 and emunand 11.2? I have a backup o fmy old emunand
Click to expand...
You can, but be very careful to never boot GW on sysNAND, or it will wipe your B9S.
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Hacking Homebrew  A new way to experience StreetPass

Hacking Hardware  New Nintendo 3DS XL Louvre

Emulation  i have citra, i have my aes keys installed, how do i get the home menu

Hardware  Why does my 3DS take so long to turn off?

What's the best 3DS emulator (especially after Citra's shutdown)?

Tutorial  How to fix 007-2001

can't download system files on citra because im "not connected to the internet"

gacube emeleter

General chit-chat
Help Users
    Psionic Roshambo @ Psionic Roshambo: https://www.youtube.com/watch?v=8FFQ_g8OoQM&list=RD8FFQ_g8OoQM&start_radio=1